Specifications for LiveNX

LiveNX Deployment

Deployment Options

LiveNX components can be deployed via the following methods: Virtual, Physical, and Cloud. The Virtual Deployment Specifications, as well as the Cisco and Multi-Vendor Device Support lists, are provided below.

If you are interested in deploying LiveNX in a Physical, Cloud (Azure, AWS, & Google Cloud), Hyper-V, or KVM environment, please contact LiveAction sales (sales@liveaction.com) for the specifications appropriate for those environments and your needs.

Virtual Deployment Specifications

The LiveNX Server is primarily deployed as a VMware .OVA appliance and is fully operational right out of the box. The server operating system runs on a Linux (TinyCore or Ubuntu) platform.

Server Platform Specifications:

  • VMware ESXi v5.0 or higher – VMware Hardware Version 8 (vmx-8)
  • Network Hardware – At least two Physical NICS on ESXi
    – Support up to 10 Gbps
    – Virtual NICs on OVA are utilizing E100

LiveActiion LiveNX specs

LiveNX Network Protocol Requirements

Below is a list of required network protocols for normal operation of the LiveNX platform. This can be used as the basis for any firewall rules required.

ProtocolPort NumberDirectionDescription
TCP7000Java Client to NX ServerJava Client Access to Platform
TCP443Web Browser to NX ServerUser Access to Web UI of Platform
TCP7026Server to Node (Bidirectional)Server <-> Node Communication
UDP2055Network devices to nodesNetflow Export
UDP161NX Node/Server to Network DevicesSNMP Polling of Network Devices

Table 2: LiveNX Protocol/Port Requirements

LiveNX requires READ-ONLY access to network devices, the platform supports both versions 2c and 3, table below details the configuration required on Cisco devices to enable SNMP v2c or v3.

v2csnmp-server community RO
v3snmp-server group v3 auth read access snmp-server user v3 auth md5 priv aes 128

Table 3: SNMP Config (Cisco)

LiveNX Semantics Data Requirements

In addition to the information and prerequisites required for LiveNX to discover devices and add them to the inventory, there are other pieces of data required; semantic data. The network/device semantics allows LiveNX to provide maximum insight into the network both in terms of visualization and reporting.

Semantic DataPurpose
Sites to which devices belongAllows devices to associated with sites for visualization within Java Client
Address of the sites – street, city, postcode, countryAllows sites to represented on a map from Web UI
IP Subnet’s associated with the respective sitesAllows LiveNX to run site to site reports based upon IP Address/Subnet
Any differentiators between circuits e.g. MPLS/INET or Service ProviderA tag allowing LiveNX to build reports based
Bandwidth capacity of WAN facing interfaces/circuitsAllows Live NX to calculate utilization rates per WAN interface – 95/99th percentiles

Table 4: Semantic Data Requirements

The collection of Netflow data is a key component of the LiveNX platform, it allows users to both visualize and report upon traffic through the network. LiveNX is a platform that supports several different ‘flavors’ of Netflow: IPFIX, Version 5, Version 9, Flexible Netflow (FNF).