Submit a ticketCall us

Systems Monitoring for Dummies
Our new eBook will teach you the fundamentals and help you create monitors and alerts that are effective, meaningful, and actionable. Monitoring is more than a checkbox on your to-do list. This free eBook will give you practical advice to help you succeed in all aspects of monitoring – discovery, alerting, remediation, and troubleshooting. Don’t miss out on this indispensable resource for newbies, experienced IT pros, and everyone in between. Register Now.

Home > Success Center > Netflow Traffic Analyzer (NTA) > NTA 4.2.3 Recommended System Requirements

NTA 4.2.3 Recommended System Requirements

 

​Updated: September 13, 2017 ​

Supports: NTA 4.2.3

SolarWinds NTA requires:

  • Appropriate SolarWinds NPM version hosted on the same server
  • NTA Flow Storage Database
  • Microsoft SQL Database
  • For production environments, SolarWinds recommends that SolarWinds NPM, Microsoft SQL Database, and NTA Flow Storage Database are hosted on separate servers.
  • SolarWinds NTA requires a 64-bit operating system.

Polling engine requirements

The following requirements ensure the scalability benefits of SolarWinds NTA:

Type Requirements
Operating system

64-bit operating system: Microsoft Windows Server 2012 and later

If you have more than one poller, make sure they are all installed on 64-bit operating systems.

SolarWinds NPM

Version 12.2

Databases

Microsoft SQL Server 2012 and later.

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.

NTA Flow Storage Database requirements

The following table lists the minimum hardware requirements for the NTA Flow Storage Database which is used for storing flow data in SolarWinds NTA.

Recommendations

  • Install the NTA Flow Storage Database on a different server than the SolarWinds Orion database. This way, the high amount of incoming flows will not affect the performance.
  • In case you want to use SAN storage, please make sure your environment meets the IOPS requirements for the NTA Flow Storage Database server.
  • Solid-state drives (SSD) are recommended for all components.
  • Do not install the NTA Flow Storage Database on a polling engine (main or additional) because it might affect performance.
  • Use a dedicated disk or LUN for storing your flows data.

    We do not recommend installing the NTA Flow Storage Database on the C:\ drive.

  • Do not run anti-virus software or any other file scanning application over data in the NTA Flow Storage Database. File scanning applications affect the database performance and may even prevent the database from running properly.

    You can also review antivirus exclusions for all Orion products. For more information, see Files and directories to exclude from antivirus scanning.

Type Requirements
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 2012 and later

.NET Framework

4.6.2

If it is not already installed, .Net Framework auto-installs with the SolarWinds NTA Flow Storage Database.

Port requirements

The following table lists ports that SolarWinds NetFlow Traffic Analyzer uses to communicate with other devices and servers.

Port Protocol Service/Process Direction Description
80 TCP World Wide Web Publishing Service Bidirectional Port used for web console and any other web servers.
137 UDP NetBIOS Outbound

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

UDP

TCP

SolarWinds Job Engine v2 Outbound Port used for sending and receiving SNMP information, including 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.

Port used for communication between remote Flow Storage Database and NTA Main Poller.

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.

Virtual machine requirements

SolarWinds NTA may be installed on VMware Virtual Machines and Microsoft Virtual Servers if the following conditions are met in your virtual environment:

  • Each virtual machine needs to meet the SolarWinds NPM requirements for virtual machines. For more information, see the SolarWinds Network Performance Monitor Administrator Guide.
  • Each installation of NPM should have its own dedicated network interface controller.

SolarWinds NPM uses SNMP to monitor your network. SNMP traffic is generally assigned low priority, and thus you can experience gaps in monitoring data.

Orion SQL database requirements

NPM and your SolarWinds Orion database should use separate servers.

Multiple SolarWinds Orion server installations using the same database are not supported.

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

SQL Server

SolarWinds supports Express, Standard, or Enterprise versions of the following:

  • SQL Server 2012, 2012 SP1, 2012 SP2, or 2012 SP3
  • SQL Server 2014 or 2014 SP1
  • SQL Server 2016
  • SQL Server 2017
  • SolarWinds strongly recommends using the 64-bit version of SQL Server.
  • The FullWithSQL installer package automatically installs SQL Server 2014 Express. This is recommended for evaluations.
  • SQL Server Compact Edition 3.5 SP2 is only supported for evaluations.
  • Due to latency effects, SolarWinds does not recommend installing your SQL Server and your Orion server or additional polling engine in different locations across a WAN. For more information, see Install SolarWinds software and SolarWinds database (SQL Server) across a WAN.
  • You can set the database recovery model to Full Recovery if you use Always On Availability. SolarWinds recommends Simple database recovery mode to ensure best performance.

SQL Server collation

  • English with collation setting SQL_Latin1_General_CP1_CI_AS
  • German with collation setting German_PhoneBook_CI_AS
  • Japanese with collation setting Japanese_CI_AS
  • Simplified Chinese with collation setting Chinese_PRC_CI_AS

We support CI database on an CS SQL Server.

We do not support case-sensitive databases.

CPU speed

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:

  • A hardware RAID Controller with a battery backed-up write back cache
  • Disk Subsystem 1 Array 1: 2x 146 GB 15K disks RAID 1 (mirroring) for the OS
  • Disc Subsystem 2 Array 2: 2x 146 GB 15K disks RAID 1 (Pagefile + Extra Storage)
  • Disk Subsystem 3 Array 3: with 6x 15k 146 GB or 300 GB disks configured in a RAID 1+0 array for your SQL MDF and FILEGROUPS.
  • Disk Subsystem 4 Array 4: with 4x 15k 146 GB or 300 GB disks configured in a RAID 1+0 array for your SQL LDF Transaction LOG file
  • Disk Subsystem 5 Array 5: with 4x 15k 146 GB or 300 GB disks configured in a RAID 1+0 array for your tempdb data file
  • Disk Subsystem 6 Array 6: with 4x 15k 146 GB or 300 GB disks configured in a RAID 0 array for your tempdb log file
  • Due to intense I/O requirements, a RAID 1+0 drive is strongly recommended for the SolarWinds database, data, and log files with a dedicated drive for the server operating system and tempdb files.
  • Other RAID configurations can negatively affect your SQL Server's performance.
  • Mirrored drives for the OS and RAID 1+0 for database data files are recommended.
  • Solid state drives (SSD) are recommended for all components.

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.

Memory

SL100

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

Authentication

Both Windows Integrated Authentication and SQL authentication mechanisms are supported.

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:

  • SQL Server System Common Language Runtime (CLR) Types. Orion products use secure SQL CLR stored procedures for selected, non-business data operations to improve overall performance.
  • Microsoft SQL Server Native Client
  • Microsoft SQL Server Management Objects
Last modified

Tags

Classifications

Public