Updated: March 14, 2016
Supports: NTA 4.2.2
SolarWinds NTA requires:
The following requirements ensure the scalability benefits of SolarWinds NTA:
|Operating system|| |
64-bit operating system: Microsoft Windows Server 2008 and later
If you have more than one poller, make sure they are all installed on 64-bit operating systems.
|SolarWinds NPM|| |
Microsoft SQL Server 2008 and later
SQL Server 2008 Express and earlier restricts the size of any database to 4 GB. For this reason, SolarWinds does not support using SQL Server 2008 Express and earlier with SolarWinds NTA in production environments.
In SQL Server 2008 R2 Express and later, Microsoft increased the restriction of maximum database size to 10 GB. You can use these versions in production environments if your flow storage requirements do not exceed 10 GB.
The NTA Flow Storage Database is where SolarWinds NTA stores your flow data. If you decide to store flows on a remote server, which SolarWinds recommends for production environments, you must install the NTA Flow Storage Database there first.
A connection to Orion SQL database is required, because CBQoS data and some additional low level details are still stored in Orion SQL database.
The following table lists the minimum hardware requirements for the NTA Flow Storage Database which is used for storing flow data in SolarWinds NTA.
|CPU||3 GHz or faster |
Evaluation requires 2 CPUs
Production environments require 4 CPUs or more (4 - 16 CPUs)
|RAM||Evaluation requires 8 GB or more |
Production environments require 16 GB or more (16 - 128 GB)
To ensure optimal performance, you should increase RAM together with the database size.
|Hard drive space|| |
20 GB on 7200 RPM disk or more
With the default 30-day retention period and default top talker optimization, you should plan at least 8 GB of additional storage capacity per sustained 1000 flows per second. The required hard drive space strongly depends on your flow traffic, and SolarWinds NTA recommends you provide more space accordingly.
NTFS file system required
The only RAID configurations that should be used with SolarWinds NTA are 0 or 1+0. Other RAID or SAN configurations are not recommended, as they can result in data loss and significantly decreased performance.
|Operating system|| |
64-bit Microsoft Windows Server 2008 SP2 and later
|.NET Framework|| |
If it is not already installed, .Net Framework auto-installs with the SolarWinds NTA Flow Storage Database.
The following table lists ports that SolarWinds NetFlow Traffic Analyzer uses to communicate with other devices and servers.
|80||TCP||World Wide Web Publishing Service||Bidirectional||Port used for web console and any other web servers.|
Port for outbound traffic if NetBIOS name resolution is turned on.
When NTA is trying to resolve the NetBIOS names of servers in their conversations, you may find a large amount of outbound UDP 137 traffic from the NTA collector to a number of external addresses. You can confirm the traffic by using the Flow Navigator to match the outbound connections to existing conversations.
This is normal behavior when NetBIOS is enabled. An easy way to demonstrate the behavior is to disable NetBIOS in NTA and watch all outbound connections terminate.
|161||TCP||SolarWinds Job Engine||Bidirectional||Port used for polling CBQoS-enabled devices.|
|1433||TCP||SolarWinds Collector Service||Outbound||Port used for communication between the NTA Flow Storage Database and the existing SQL server.|
|2055||UDP||SolarWinds Collector Service||Inbound||Port for receiving flows on any SolarWinds NTA collector.|
|5671||TCP||RabbitMQ||Bidirectional||Rabbit MQ messaging|
|17777||TCP||SolarWinds Information Service||Bidirectional||Port for sending and receiving traffic between SolarWinds NPM and other Orion Modules.|
|17778||HTTPS and TCP||SolarWinds Information Service||Bidirectional||Open to access the SolarWinds Information Service API and agent communication|
|17791||TCP||SolarWinds Agent||Bidirectional||Open for agent communication on any SolarWinds Orion server running Windows Server 2008 R2 SP1|
|Device-specific||Any port required by a specific device.|
For a complete list of the port requirements for the SolarWinds Orion server, see the Port Requirements document.
SolarWinds NTA may be installed on VMware Virtual Machines and Microsoft Virtual Servers if the following conditions are met in your virtual environment:
SolarWinds NPM uses SNMP to monitor your network. SNMP traffic is generally assigned low priority, and thus you can experience gaps in monitoring data.
NPM and your SolarWinds Orion database should use separate servers.
Multiple SolarWinds Orion server installations using the same database are not supported.
Important End of Support
Microsoft SQL Server: Support for SQL 2008 and 2008 R2 is deprecated as of this release. Future releases will no longer support using SQL 2008 or 2008 R2 as your database server. SolarWinds recommends that you upgrade directly to SQL 2016 at your earliest convenience.
If you install on a virtual machine, you must maintain your SQL Server database on a separate, physical drive.
The following table lists software and hardware requirements for your SolarWinds Orion database server using SolarWinds NPM license levels.
|Requirements||SL100, SL250, SL500||SL2000||SLX|
SolarWinds supports Express, Standard, or Enterprise versions of the following:
SQL Server collation
We support CI database on an CS SQL Server.
We do not support case-sensitive databases.
Quad core processor or better
Dual quad core processor or better
Dual quad core processor or better
Hard drive space
20 GB minimum
40 GB recommended
50 GB minimum
100 GB recommended
100 GB minimum
400 GB recommended
SolarWinds recommends the following configuration:
Per Windows standards, some common files may need to be installed on the same drive as your server operating system. You may want to move or expand the Windows or SQL temporary directories.
4 GB minimum
8 GB recommended
16 GB minimum
64 GB recommended
64 GB minimum
128 GB recommended
SL250 & SL500
8 GB minimum
16 GB recommended
Either mixed-mode or SQL authentication
|Other software|| |
If you are managing your SolarWinds Orion database, SolarWinds recommends you install the SQL Server Management Studio component.
The Installation Wizard installs the following required x86 components if they are not found on your Orion database server: