Make sure the server you install Nagios Network Analyzer on meets the requirements below.
Server OS (Only 64-bit supported):
See Nagios Software / Operating System (OS) compatibility matrix.
Minimum system specs:
Recommended system specs:
Additional details can be found in the Hardware Recommendations guide:
Network Analyzer – Hardware Recommendations
*Out of the box, Nagios Network Analyzer ships with the capability to collect and analyze network flow data, which requires a minimum of 1 processing core and 2 GB RAM. Users can additionally further integrate network mapping (add one core and 2GB RAM), packet analysis (add one core and 2GB RAM), and intrusion detection (add one core and 2 GB RAM). Larger environments and/or extensive use of the integrations will require at least double these numbers.
**Dependent on the amount of traffic, speed of collected flow data, Raw Data Lifetime chosen for Sources, and on which integrations (notably Suricata and Wireshark) are loaded and the degree to which they are used.
This document is intended to outline the steps required to manually install Nagios Network Analyzer, along with its prerequisites from source.
This document is intended for use by Administrators who wish to install Nagios Network Analyzer on physical servers, operating systems and distributions other than those provided as our official pre-built Virtual Machines.
Network Analyzer Manual Installation Instructions - NNA 2026
Network Analyzer Manual Installation Instructions - NNA 2024
This document is intended to outline the steps required to install Nagios Network Analyzer within Hyper-V.
This document is intended to outline the steps required to install Nagios Network Analyzer within VMware Workstation Player.
Installing Nagios Network Analyzer with VMware Workstation Pro
This document is intended to explain how to convert the VMware OVA virtual machine image of Nagios Network Analyzer to VirtualBox.
This document is intended for use by Nagios Network Analyzer customers who wish to run Nagios Network Analyzer within VirtualBox rather than VMware.