Specifications

LiveNX 7 Specifications

LIVENX 7 DEPLOYMENT OPTIONS

LiveNX 7.x components can be deployed via the following method: OVA packages

Component Virtual Appliance Option
Server All-in-one Server OVA
Client Client software for Mac OS, Win 32-bit and 64-bit
Node (optional) Node OVA
LiveSensor (optional) LiveSensor OVA
LiveAnalytics Node (optional) LiveAnalytics OVA

All-in-One Server & Platform OVA, Node OVA and Hyper-V Deployments

 

Custom Deployment Small Deployment Medium Deployment Large Deployment
Used for less than 25 devices or less than 25k flows/sec. Used for less than 100 devices or lesser than 100k flows/sec Used for 100 to 500 devices or less than 200k flows/sec Used for 500 to 1000 devices or greater than 200k flows/sec
Installation for non-server installations (Laptops, Desktops, etc.).
(size not available for Node OVA)
Installation for server environments with Hyper-V Manager/VMware Hypervisors/ESX(i) Installation for server environments with Hyper-V Manager/VMware Hypervisors/ESX(i) Installation for server environments with Hyper-V Manager/VMware Hypervisors/ESX(i)
Specifications: Specifications: Specifications: Specifications:
2vCPU Xeon or i7
4GB RAM
LiveNX Server Max Heap Size 2GB
250GB Data Disk*
8vCPU Xeon or i7
16GB RAM
LiveNX Server Max Heap Size 8GB
2TB Data Disk*
16vCPU Xeon or i7
32GB RAM
LiveNX Server Max Heap Size 16GB
4TB Data Disk*
32vCPU Xeon or i7
64 GB RAM
LiveNX Server Max Heap Size 31GB
8TB Data Disk*

*Data Disk Size is a minimum recommendation.

Storage can be expanded by adding additional disk.

Server IOPS Recommendation LiveNX 7.0 – 1000 IOPS Read and 4500 IOPS Write

Virtual NICs on OVA are utilizing E1000

Client Sizing

  • Windows 7, 8, 10 or Mac OSX 64-bit OS
  • 4 Cores
  • 8 GB RAM
  • Web browser: IE11 and higher, Firefox, Chrome and Safari
Components

  • Java JDK `1.8.0_152`
  • NodeJS `v6.12.2`
  • MongoDB `3.4.0`
  • InfluxDB `1.3.9`
  • PM2 `1.1.3`

CISCO DEVICE SUPPORT

ISR Series Routers: 800, 1700, 1800, 1900, 2600, 2600XM, 2800, 2900, 3600, 3700, 3800, 3900, 4300, 4400, 7200, 7600 7200 & 7600 Series Routers Cisco Nexus Switches (Nexus 3000, 7000 & 9000 Series)
ASR 1000 Series Routers, CSR 1000V Cisco AnyConnect Client Cisco Catalyst 3650, 3850 & 4500-X Series switches are supported.

(Limited LiveNX QoS Monitor support on Layer 3-routable interfaces and VLANs depending upon Cisco hardware capabilities.)

ASR 9000 Series Routers (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.) Cisco ASA 5500 Series Firewalls Cisco AnyConnect Network Visibility Module on Windows and Mac OS X Platforms
Cisco Meraki MX Security Appliance Cisco NetFlow Generation Appliance Viptela vEdge Devices

OTHER DEVICE SUPPORT – FLOW

Adtran NetVanta Series Routers

Gigamon GigaSMART

Ntop nProbe

Alcatel-Lucent Routers

Hewlett-Packard Enterprise Procurve Series Switches

Palo Alto Networks Firewalls

Brocade Series Routers

Ixia’s Network Visibility Solution

Riverbed SteelHead WAN Optimization Controllers

Checkpoint Firewall

Juniper MX Series Routers

Silver Peak WAN Optimization Controllers

Extreme Network Switches

Netscaler LoadBalancer

Viptela vEdge Routers

Ziften ZFlow

Adtran NetVanta Series Routers

Cisco Meraki MX Security Appliance

Ixia’s Network Visibility Solution

Alcatel-Lucent Routers

Cisco NetFlow Generation Appliance

Juniper MX Series Routers

Brocade Series Routers

Extreme Network Switches

Ntop nProbe

Cisco Series Routers (ISR Series, CRS-1, ASR 1000 & ASR 9000 Series Routers)

Gigamon GigaSMART

Palo Alto Networks Firewalls

Cisco Catalyst Switches

Hewlett-Packard Enterprise Procurve Series Switches

Riverbed SteelHead WAN Optimization Controllers

Cisco Nexus Switches (Nexus 3000, 7000 & 9000 Series)

Silver Peak WAN Optimization Controllers

Cisco ASA 5500 Series Firewalls

Viptela vEdge Routers

Cisco AnyConnect Network Visibility Module on Windows and Mac OS X Platforms

Ziften ZFlow

LIveSP Specifications

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

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