Submit a ticketCall us

WebinarUpcoming Webinar: How Help Desk and Remote Support Pays for Itself

Learn how help desk software can simplify ticketing management, allow you to track hardware and software assets, and accelerate the speed of IT support and service delivery. Gain insights on how remote support tools allow your IT team to maximize their efficiency and ticket resolution by expediting desktop troubleshooting, ultimately helping keep end-users happy and productive.

Register here.

Home > Success Center > Netflow Traffic Analyzer (NTA) > NTA Legacy Installation Guide > Integrated SolarWinds NTA installation > Multi-module system guidelines

Multi-module system guidelines

Updated: May 30, 2018

This Orion Platform topic applies to the highlighted products:

DPAIMEOCETSIPAMLMNCMNPMNTASAMSRMUDTVMANVNQMWPM

If you are installing more than one SolarWinds Orion Platform product, use these recommended guidelines for hardware and software deployment. The information here should be considered guidelines only. You can choose to use more or less hardware, but your performance may vary depending on your deployment scenario.

In Amazon Web Services (AWS), the Elastic Block Storage (EBS) volumes are not your dedicated hardware devices. For SQL and NTA Flow Storage Database, SolarWinds recommends using dedicated instance EBS volumes for medium and large deployments. For large deployments, SolarWinds recommends EBS with provisioned IOPS for high performance for intensive database workloads.

If you have only one SolarWinds Orion module, see the system requirements listed in the installation guide for that module.

Deprecation notices
  • Although you can install Orion Platform 2018.2 products on Windows Server 2012 and 2012 R2, these versions are deprecated and will not be supported on future Orion Platform versions. SolarWinds strongly recommends that you upgrade to Microsoft Windows Server 2016 or later at your earliest convenience.
  • Although you can use SQL Server 2012 with Orion Platform 2018.2 products, this version is deprecated and will not be supported on future versions of the Orion Platform. SolarWinds strongly recommends that you upgrade to Microsoft SQL Server 2016, 2017, or later at your earliest convenience.

How do I calculate hardware requirements for my Orion server?

Your first Orion Platform product must meet the minimum system requirements in the appropriate Administrator Guide. Typically, you need a single quad-core processor and 8 GB of RAM. For each additional module on the same system, add one CPU core and 2 GB of RAM.

Modules CPU RAM
1

Required: 4 cores

Recommended: 8 cores

Required: 8 GB

Recommended: 16 GB

2

Required: 5 cores

Recommended: 10 cores

Required: 10 GB

Recommended: 18 GB

3

Required: 6 cores

Recommended: 12 cores

Required: 12 GB

Recommended: 20 GB

4

Required: 7 cores

Recommended: 14 cores

Required: 14 GB

Recommended: 22 GB

5

Required: 8 cores

Recommended: 16 cores

Required: 16 GB

Recommended: 24 GB

6

Required: 9 cores

Recommended: 18 cores

Required: 18 GB

Recommended: 26 GB

7

Required: 10 cores

Recommended: 20 cores

Required: 20 GB

Recommended: 28 GB

8

Required: 11 cores

Recommended: 22 cores

Required: 22 GB

Recommended: 30 GB

9

Required: 12 cores

Recommended: 24 cores

Required: 24 GB

Recommended: 32 GB

10

Required: 13 cores

Recommended: 26 cores

Required: 26 GB

Recommended: 34 GB

Small deployment guidelines

Modules

Choose up to 3 modules:

  • NPM SL100 - SL500 (including up to 10 remote agents for DPI)
  • SAM AL150 - AL300
  • WPM 5 - WPM 20
  • VNQM IPSLA 5 - IPSLA 25 (up to 5,000 operations)
  • NCM DL50 - DL200
  • IPAM IP1000 - IP4000
  • UDT UT2500 - 5000
  • VMAN VMS8 - VMS64
    If you use VMAN Recommendations, increase the total memory on the server by 4 GB.

You can install NTA as part of a small deployment, but it is not included in this configuration. Use the Medium Deployment guidelines for NTA.

Orion
server

Physical server or virtual machine

  • Storage: 150 GB, 15,000 RPM
  • 1 x 1 Gb dedicated NIC
  • Windows Server 2016 or 2016, 2012 R2, or 2012, Standard or Datacenter Edition

The SolarWinds Orion installer installs IIS and .NET 4.6.2 or later if they are not already on your server.

SolarWinds Orion SQL database
server

Physical server recommended

  • Quad core processor or better
  • 16 GB RAM
  • 100 GB1 (or more) storage in RAID 1+0 configuration (RAID 5 not supported)
  • Windows Server 2016, 2012 R2, or 2012, Standard or Datacenter Edition
  • SQL Server 2017, 2016, 2014, or 2012, Standard or Enterprise Edition

1More or less space may be needed depending on your data retention policies, number of elements measured, and polling frequency.

Amazon Web Service VMs

Orion
server
  • m4.large
  • 2 CPUs, 8 GB RAM
  • 150 GB (default is 50 GB for m4.large)
Primary database
server (SolarWinds Orion database)
  • r3.xlarge
  • 4 CPUs, 16 GB RAM
  • SSD 80 GB (included in r3.xlarge) + EBS Volume 500 GB

When using the Amazon RDS as your database server for small environments, the following template is required:

  • db.r4.xlarge

Medium deployment guidelines

Modules

NPM SL500 - SL2000

NTA for NPM SL2000

  • 50,000 FPS received sustained on the main polling engine

2 - 4 additional modules:

  • SAM AL700 - AL1100
  • WPM 50 - WPM 200
  • VNQM IPSLA 25 - IPSLA 50 (up to 10,000 operations)
  • NCM DL500 - DL1000
  • IPAM IP16,000
  • UDT UT10,000 - 25,000
  • VMAN VMS112 - VMS320
    If you use VMAN Recommendations, increase the total memory on the server by 8 GB.

Orion
server

Physical server or virtual machine

  • 150 GB, 15,000 RPM
  • 1 x 1 Gb dedicated NIC
  • Windows Server 2016, 2012 R2, or 2012 Standard or Datacenter Edition

The SolarWinds Orion installer installs IIS and .NET 4.6.2 or later if they are not already on your server.

SolarWinds Orion SQL database
server

Physical server recommended

  • Dual quad core processor or better
  • 64 GB RAM
  • 250 GB2 (or more) storage in RAID 1+0 configuration (RAID 5 not supported)
  • Hardware RAID Controller (software RAID not supported)
  • Windows Server 2016, 2012 R2, or 2012, Standard or Datacenter Edition
  • SQL Server 2017, 2016, 2014, or 2012 Standard or Enterprise Edition

NTA Flow Storage database
server specifications

Physical server or virtual machine

  • Quad core processor or better
  • 16 GB3 RAM
  • 100 GB - 1 TB4 of storage capacity on local NTFS disk
  • 1 x 1 Gb dedicated NIC
  • Windows Server 2016, 2012 R2, or 2012, Standard or Datacenter Edition

Storing flow data in NTA

  • NTA 4.0: if the NTA server is running a 32-bit operating system, NTA stores the flow data in the SQL database (NTA Flow Storage FastBit database is not installed). See NTA 4.x Installation: FAQs
  • NTA 4.1 and later requires a 64-bit operating system. SolarWinds recommends a separate NTA Flow Storage database.
  • NTA 4.4 requires an instance of MS SQL Server 2016 or later for storing flow data. See NTA 4.4 requirements for more details.

2More or less space may be needed depending on your data retention policies, number of measured elements, and polling frequency.

3Increase the NTA Flow Storage database RAM as the database size increases.

4More or less space may be required, depending on your data retention policies and the number of stored flows. You need approximately 8 GB of additional storage for every 1,000 flows retained for 30 days. For example, if you want 50,000 flows stored for 30 days, you need a base of 100 GB plus an additional 400 GB of storage.

Amazon Web Service VMs

Orion
server

  • m4.xlarge
  • 2 CPUs, 16 GB RAM
  • 150 GB (default is 50 GB for m4.large)

Primary database
server (SolarWinds Orion database)

  • r3.xlarge
  • 4 CPUs, 30.5 GB RAM
  • SSD 80 GB (included in r3.xlarge) + EBS Volume 500 GB

When using the Amazon RDS as your database server for medium environments, the following template is required:

  • db.r4.2xlarge
NTA Flow Storage
  • r3.xlarge
  • 4 CPUs, 30.5 GB RAM
  • SSD 80 GB (included in r3.xlarge) + EBS Volume 500 GB
  • 8 GB for every received sustained 1000 Flows/s with 30-days retention period

Large deployment guidelines

Modules

NPM SLX (with multiple polling engines)

NTA for NPM SLX

  • 50,000 FPS received sustained on the main polling engine
  • Up to 6 polling engines (5 in addition to the main polling engine) for 300,000 FPS received sustained

Any combination of these modules:

  • SAM ALX
    • 1 APE for every 10,000 component monitors
    • Maximum of 50,000 component monitors per primary Orion SAM server + 4 APEs
  • VNQM IPX
    • ~5,000 IP SLA operations per polling engine
  • NCM DLX
    • 1 APE for every 10,000 devices, for NCM 7.1 and later
    • Maximum of 30,000 devices per NCM instance (that is, NCM server + 2 NCM APEs)
  • IPAM IPX
    • 750,000 IP
  • UDT UTX
    • 150,000 ports per polling engine
  • VMAN VMS480 and higher
    If you use VMAN Recommendations, increase the total memory on the server by 16 GB.
    For every 3000 VMs, SolarWinds recommends that you add an additional free polling engine. Additional polling engines for VMAN are free of charge.

Orion
server

Physical server or virtual machine (VM)

  • Storage: 150 GB, 15,000 RPM
  • 1 x 1 Gb dedicated NIC
  • Windows Server 2016, 2012 R2, or 2012, Standard or Datacenter Edition

The SolarWinds Orion installer installs IIS and .NET 4.6.2 or later if they are not already on your server.

SolarWinds Orion SQL database
server

Physical server recommended

  • Dual/quad core processor or better
  • 128 GB RAM
  • Hardware RAID Controller (software RAID not supported)
  • Disk Subsystem 1 Array 1: 2 x 146 GB 15,000 disks RAID 1 (mirroring) operating system
  • Disk Subsystem 2 Array 2: 2 x 146 GB 15,000 disks RAID 1 (Pagefile + extra storage)
  • Disk Subsystem 3 Array 3: with 6x 15,000 146 GB or 300 GB disks configured in a RAID 1+0 arrays to allow for maximum write performance. This is for your SQL MDF AND FILEGROUPS
  • Disk Subsystem 4 Array 4: with 4x 15,000 146 GB or 300 GB disks configured in a RAID 1+0 arrays to allow for maximum write performance. This is 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
  • 1 Gb LAN port
  • Windows Server 2016, 2012 R2, or 2012, Standard or Datacenter Edition
  • SQL Server 2017, 2016, 2014, or 2012, Standard or Enterprise Edition

NTA Flow Storage
server

Physical server or virtual machine

  • Quad core processor or better
  • 16 GB3 RAM
  • 100 GB - 1 TB4 of storage capacity on local NTFS disk
  • 1 x 1 Gb dedicated NIC
  • Windows Server 2016, 2012 R2, or 2012, Standard or Datacenter Edition

Storing flow data in NTA

  • NTA 4.0: if the NTA server is running a 32-bit operating system, NTA stores the flow data in the SQL database (NTA Flow Storage FastBit database is not installed). See NTA 4.x Installation: FAQs
  • NTA 4.1 and later requires a 64-bit operating system. SolarWinds recommends a separate NTA Flow Storage database.
  • NTA 4.4 requires an instance of MS SQL Server 2016 or later for storing flow data. See NTA 4.4 requirements for more details.

Additional polling engine server

Virtual machine recommended

  • Quad core processor or better
  • 32 GB RAM
  • 150 GB, 15,000 RPM
  • 1 x 1 Gb dedicated NIC
  • Windows Server 2016, 2012 R2, or 2012

The SolarWinds Orion installer installs IIS and .NET 4.6.2 or later if they are not already on your server.

3Increase the NTA Flow Storage database RAM as the database size increases.

Amazon Web Service VMs

Orion server

  • m4.2xlarge
  • 2 CPUs, 16 GB RAM
  • 150 GB (default is 50 GB for m4.large)

Primary database
server (SolarWinds Orion database)

  • r3.2xlarge
  • 4 CPUs, 30.5 GB RAM
  • SSD 80 GB (included in r3.xlarge) + EBS Volume 500 GB

When using the Amazon RDS as your database server for medium environments, the following template is required:

  • db.r4.4xlarge
NTA Flow Storage
  • r3.4xlarge
  • 16 CPU, 122 GB RAM
  • SSD 320 GB (included in r3.xlarge) + EBS Volume 2.5 TB
  • 2.5 TB is Flowstorage, 300k FPS with 30-days retention, EBS with Provisioned IOPS recommended.

 

Extra large deployment guidelines

To monitor up to 400,000 elements, ensure your deployment meets the following minimum requirements. Extra large environment require deploying Additional Polling Engines to scale your deployment.

Disk Performance is measured using IOPS.

CPU recommendations use the PassMark score (© 2018 PassMark® Software, obtained at https://www.cpubenchmark.net/high_end_cpus.html on April 9, 2018).

How do I find out the PassMark score of my server?

  1. Download the Pass Mark Performance Test (© 2018 PassMark® Software, obtained at https://www.passmark.com/products/pt.htm on April 9, 2018).
  2. Run it on your server to find out a PassMark score of your server.

Orion
server

Additional polling
engine server

  • Quad core processor or better
  • 32 GB RAM
  • Storage: 150 GB, 15,000 RPM
  • 1 x 1 Gb dedicated NIC
  • Windows Server 2016, 2012 R2, or 2012, Standard or Datacenter Edition

SolarWinds Orion SQL database
server

Minimum:

  • CPUs with a total combined PassMark score of 32,000 or higher
  • 256 GB RAM
  • Disk: Read/Write I/O Performance of 30,000 IOPs
  • Enterprise edition of the following MS SQL Server versions:
    • MS SQL Server 2012, 2012 SP1, 2012 SP2, 2012 SP3, 2012 SP4
    • SQL Server 2014, 2014 SP1, 2014 SP2
    • MS SQL Server 2016, 2016 SP1
    • MS SQL Server 2017 (including Linux installs)

Recommended:

  • 4 CPU/ 60 cores
  • 512 GB
  • 190,000 IOPS or better
  • 1 Gbit dedicated NIC

Amazon Web Service

Orion
server

  • m5.4xlarge

  • 16 CPU
  • 32 GB RAM
  • 50 GiB General Purpose SSD (GP2)
  • 100/3,000 IOPS

Additional polling
engine server

  • m5.xlarge
  • 4 CPU
  • 16 GB RAM
  • 50 GiB General Purpose SSD (GP2)
  • 100/3000 IOPS

Primary database
server (SolarWinds Orion database)

  • db.r4.8xlarge
  • 32 CPU
  • 244 GB RAM
  • 1,500 GiB Provisioned IOPS (SSD)
  • 20,000 IOPS

 

 
Last modified

Tags

Classifications

Public