This information is intended for anyone who wants to install, configure, or maintain NetFlow Optimizer (NFO). The information is written for experienced Linux or Windows system administrators who are familiar with virtual machine technology and data center operations.
you can install NetFlow Optimizer on premises (Linux or Windows server) or in your cloud environments (AWS, Azure, or GCP). Please be sure to have the following before you begin the installation of the NetFlow Optimizer software:
You have Amazon Web Services (AWS) environment for AWS installations. See steps in Setting Up with Amazon EC2
You have to login as root for Linux and administrator for Windows installations and updates
License – A license is required before you can begin using NetFlow Optimizer software. Please register at https://www.netflowlogic.com/register-form/ to get your FREE evaluation license or contact email@example.com
Network Device - Please refer to the “Configuring NetFlow Data Export” section in your Cisco (or other) device documentation
NFO is distributed as a virtual appliance in OVA file format, as Amazon Machine Image (AMI), as RPM or TAR.GZ for Linux, or as EXE for Windows.
You can install the NetFlow Optimizer virtual appliance or software on a platform with the following specifications.
AWS EC2 Image
VMware ESXi 5.x and above
Linux kernel 2.6+ on
OSes which support UNIX System V:
OSes which support systemd:
OSes which support OpenRC:
Windows Server 2008 R2, 2012, 2012 R2, 2016, 2019 (64-bit)
CPU, Memory, Disk Space
- CPU: Min 4 CPU cores (8 or 16 CPU cores for higher performance) - Memory: Min 4 GB (16 GB recommended) - Disk Space: 20 GB
During deployment of the NFO virtual appliance you can select different sizes according to the ingestion requirements for the environment. The small configuration requires the following virtual resources.
4 vCPUs, 2GHz each
Approximately 20GB storage space
You can use one of the following browsers to connect to the NFO Web user interface.
Mozilla Firefox 38.0 and up
Safari 6.0 , 7.0
Google Chrome 34.0 and 43.0 and up
IE10, IE11, and MS Edge
The following network ports must be accessible.
NetFlow Optimizer GUI
NetFlow/IPFIX Ingestion (plus all ports for ingestion as necessary)
161/UDP and 162/UDP
SNMP polling and SNMP traps
20047/TCP and 20048/TCP
NetFlow Optimizer internal services
To change ports 20047/20048 perform the following:
Add or change the following lines in
Change controller port and PCE port in
# Controller listener port number
coss.controller.port = 20047
# Controller connection timeout in milliseconds
coss.controller.connectionTimeout = 60000
# Default PCE configuration notification changes listener port number
coss.pce.port = 20048
# Default PCE configuration notification changes host
coss.pce.host = 127.0.0.1
NOTE: Restart NFO and Tomcat after applying these changes as follows:
Stop NFO using GUI
Restart Tomcat using one of the following commands:
/etc/init.d/tomcat_nfo restart or
service tomcat_nfo restart
Start NFO using GUI
By default, the NFO virtual appliance has 4 vCPUs, 8GB of virtual memory, and 20GB of disk space provisioned.
You can change the settings according to the environment for which you intend to collect NetFlow. During the virtual appliance deployment, you can select the size of the appliance as follows.
Number of VMs
NetFlow Ingest Rate