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

Client Platform Specifications:

• Windows or macOS
• 4 Cores
• 8 GB RAM
• Web browser: IE11 and higher, Firefox, Chrome, and Safari

Cisco Device Support – SNMP & Flow

ASR 9000 Series Router Cisco AnyConnect Network Visibility Module on Windows and Mac OS X Platforms Cisco ASA 5500 Series Firewalls Cisco Catalyst Series Switches 2900, 3650, 3850 & 4500-X 6500, 6800, 9000 are supported.** (Limited LiveNX QoS Monitor support on Layer 3-routable interfaces and VLANs depending upon Cisco hardware capabilities.) Cisco ISR Series Routers: 800, 900, 1700, 1800, 1900, 2600, 2600XM, 2800, 2900, 3600, 3700, 3800, 3900, 4200, 4300, 4400, 4500, 7200, 7600**, ASR 1001x, 1002x Series Routers, CSR 1000V**

Cisco Meraki MX Security Appliance Cisco Nexus Switches (Nexus 3000, 7000, 6000 & 9000 Series) Cisco NetFlow Generation Appliance • Cisco SD-WAN vEdge, Cisco IOS XE SD-WAN Edge Devices**Recommend IOS versions 12.3 or higher or 15.0 or higher for use with the software (IOS XE 2.6.0 or higher for ASR 1000 series). Earlier IOS versions may also work but are not officially supported. General-release IOS versions are recommended, although early-and limited-release versions will also work with LiveNX.

Multi-Vendor Device Support – Flow

Adtran NetVanta Series Routers Alcatel-Lucent Routers Barracuda Firewall Brocade Series Routers Checkpoint Firewall Citrix NetScaler Load Balancer Extreme Network Switches F5 Load-Balancer Gigamon GigaSMART Hewlett-Packard Enterprise Procurve Series Switches

Ixia’s Network Visibility Solution Juniper MX Series Routers Ntop nProbe Palo Alto Networks Firewalls • Riverbed SteelHead WAN Optimization Controllers • Silver Peak WAN Optimization Controllers Sophos Firewall Ziften ZFlow

Download LiveNX SPEC PDF

LiveSP Deployment Requirement

Component	Sizing Tool *
Hardware	LiveSP can be deployed on a single server or a distributed infrastructure. I/O is optimized for random data access, Data storage is implemented on the physical machine with SSD. The other components can be virtualized.
Operating System	The current supported and validated Linux distribution are (Debian, Red hat, Ubuntu) with Kernel version greater than 3.10. Kernel version 3.16 onwards is recommended for higher performance data access.
Browser	Service providers, administrators, operation team and end-customers access LiveSP through support web browsers. Supported web browsers are IE 11, Mozilla Firefox (latest), Google Chrome (latest, Safari (latest)

LiveSP Sizing Guide

Component	Sizing Tool *
Link (Bandwidth)	Bandwidth = Average flow size * Flow count at this max traffic * Predicted max aggregated traffic.   Typical enterprise network with 10000 live interfaces, static template = 200 Mbps
Hardware (Storage)	Storage = Client profiles * Data retention rule * Predicted average aggregated traffic   Virtual Environment Proxy: 1 * 4 CPU, 4 GB RAM, 1 SAW 20 GB Collect: 2 * 8 CPU, 16 GB RAM, SAS 1TB Services: 4 * 8 CPU, 8 GB RAM, 1 SAS 200 GB Physical Environment 2 * [20 CPU, 128 GB RAM, 3 TB SSD disk/ 3 TB Backup]

 

* LiveSP sizing tool is designed to help size Link and Storage. It is based on observations on large networks, but could vary on traffic profile. Please contact LiveSP support for details analysis.

Flow Information

Flexible NetFlow FNF V9: (IPv4&6 compatible) Version v9 has brought FNF capability, which makes Netflow a highly versatile protocol. Its flexibility makes it particularly more relevant for complex reporting and heterogeneous data.

• Flexible key field aggregation
• variable number of data fields.
• unidirectional or bidirectional
• sampled or not
• multi-vendor (430 standardized fields, thousands vendor-specific fields)
• aggregated, synchronized or not for exports

 

IPFIX: (“IP Flow Information eXport”) also referred to as NFv10, IPFIX is the industry standardized version of Netflow. It builds on NFv9 for most of the features, and brings additional flexibility (variable-length fields, sub -application extracted fields, options-data).

Note: Netflow version 9 and IPFIX are the export protocols of choices for AVC, because they can accommodate flexible record format and multiple records required by Flexible Netflow infrastructure. IPFix is recommended.

If service providers choose a centralized collection, they must size the collection link properly. Link sizing recommendation depends on:

• IWAN features enabled: More features = more data to export.
• Bandwidth per site repartition: headquarter with 500 employees will have more variety (=more export) than a small office with 20 employees)
• The time traffic distribution: the CPEs don’t have their max traffic at the same time.

 

A Typical 10000 CP enterprise SP IWAN network required a 200 Mbps bandwidth Collection Link Max Speed = Average Flow Size * Predicted Max Aggregated Traffic * Flow Count at this Max Traffic

Download LiveSP PDF