Multi-module system guidelines for the Orion Platform

This topic applies to all Orion Platform products.

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 databases used by Orion Platform products, 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 for that module in the Success Center.

End-of-support notices

Products running on Orion Platform 2018.4 and later are no longer compatible with the following operating system and database versions:

  • Windows Server 2012 and 2012 R2
  • SQL Server 2012, 2012 SP1, 2012 SP2, 2012 SP3, and 2012 SP4

To use the new features introduced in Orion Platform 2018.4 and later, upgrade your environment 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 for that product. 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:

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

You can install Log Analyzer, NTA, or SCM as part of a small deployment, but it is not included in this configuration. Use the Medium Deployment guidelines for these Orion Platform products.

Orion
server

Physical server or virtual machine

  • CPU: 4 cores + 1 core for each additional module
  • RAM: 8 GB + 2 GB for each additional module

    How do I calculate hardware requirements?

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

The SolarWinds Orion Installer installs IIS and .NET 4.8 if they are not already on your server.

SolarWinds Orion SQL database
server

  • Quad core processor or better
  • 16 GB RAM
  • 100 GB (or more) storage in RAID 1+0 configuration (RAID 5 not supported)

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

  • SQL Server 2017, 2016, or 2014, Standard or Enterprise Edition

    SolarWinds recommends SQL Server 2016 SP1 or later.

Amazon Web Service VMs

Orion
server

m4.large

Recommended: m4.xlarge

Primary database
server (SolarWinds Orion database)

r4.xlarge

When using the Amazon RDS as your database server for small environments, use the db.r4.xlarge template.

Amazon RDS db.r4.xlarge

Microsoft Azure

Orion
server

DS12_v2

4 CPU

16 GB RAM

150 GB disk

Primary database
server (SolarWinds Orion database)

DS4_v2 Standard

8 CPU

28 GB RAM

System SSD 126 GB (included in Azure VM instance) + 1 TB for SQL database (included in Azure SQL Server Compute)

Azure SQL

Only products on Orion Platform 2019.2.

The Orion Server must be set to use the same time zone as Azure SQL (UTC by default).

Required tiers depend on whether you are using the memory-optimized tables (In-Memory OLTP) feature of MS SQL Server 2016 and 2019. This feature improves the performance of transaction processing, data ingestion, data load, and transient data scenarios.

With memory-optimized tables:

  • DTU Premium Tier P1
  • vCore Business Critical Gen4 Tier 1
  • vCore Business Critical Gen5 Tier 2

Without memory-optimized tables:

  • DTU Standard Tier S3
  • DTU Premium Tier P1
  • vCore General Purpose Tier 2
  • vCore Business Critical Tier 2

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:

  • IPAM IP16,000
  • Log Analyzer LA10 - LA250
  • NCM DL500 - DL1000
  • SAM SAM50 - SAM75
  • SCM SCM50 - SCM1000
  • UDT UT10,000 - 25,000
  • VMAN VMS112 - VMS320
    If you use VMAN Recommendations, increase the total memory on the server by 8 GB.
  • VNQM IPSLA 25 - IPSLA 50 (up to 10,000 operations)
  • WPM 50 - WPM 200

Orion
server

Physical server or virtual machine

  • CPU: 4 cores + 1 core for each additional module
  • RAM: 8 GB + 2 GB for each additional module

    How do I calculate hardware requirements?

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

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

SolarWinds Orion SQL database
server

  • 8 processor cores or more
  • 64 GB RAM
  • 250 GB (or more) storage in RAID 1+0 configuration (RAID 5 not supported)

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

  • Hardware RAID Controller (software RAID not supported)
  • SQL Server 2017, 2016, or 2014, Standard or Enterprise Edition

    SolarWinds recommends SQL Server 2016 SP1 or later.

NTA Flow Storage database
server specifications

Physical server or virtual machine

  • Quad core processor or better
  • 16 GB RAM
    Note: Increase the NTA Flow Storage database RAM as the database size increases.
  • 100 GB - 1 TB of storage capacity on local NTFS disk
    Note: More 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 per second retained for 30 days. For example, if you want 50,000 flows per second stored for 30 days, you need a base of 100 GB plus an additional 400 GB of storage.
  • 1 x 1 Gb dedicated NIC

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 and later requires an instance of MS SQL Server 2016 SP1 or later for storing flow data. See NTA current version requirements for more details.
Log Analyzer database

Physical server or virtual machine

  • Quad core processor or better
  • 16 GB RAM
  • 100 GB - 1 TB of storage capacity on local NTFS disk
    Note: More or less space may be required, depending on the number of stored events. Log Analyzer supports 1,000 Events per Second across all polling engines.
  • 1 x 1 Gb dedicated NIC
  • MS SQL 2016 SP1 and later, Standard or Datacenter Edition
  • Supported collations:
    • English with collation setting SQL_Latin1_General_CP1_CI_AS
    • English with collation setting SQL_Latin1_General_CP1_CS_AS

Amazon Web Service VMs

Orion
server

m4.2xlarge

Primary database
server (SolarWinds Orion database)

r4.xlarge

When using the Amazon RDS as your database server for medium environments, use the db.r4.xlarge template.

NTA Flow Storage

r3.xlarge

Log Analyzer database

r3.xlarge

Amazon RDS db.r4.2xlarge

Microsoft Azure

Orion
server

DS12_v2

4 CPU

16 GB RAM

150 GB disk

Primary database
server (SolarWinds Orion database)

DS4_v2 Standard

8 CPU

28 GB RAM

System SSD 126 GB (included in Azure VM instance) + 1 TB for SQL database (included in Azure SQL Server Compute)

NTA Flow Storage

DS12_v2

4 CPU

30.5 GB RAM (8 GB for every received sustained 1000 Flows/s with 30-days retention period)

System SSD 80 GB (included in D12_v2) + Data Azure Storage Disk Volume 500 GB

Log Analyzer Database

DS12_v2

4 CPU

30.5 GB RAM

System SSD 80 GB (included in D12_v2) + Data Azure Storage Disk Volume 500 GB

Azure SQL DB

Only products on Orion Platform 2019.2.

The Orion Server must be set to use the same time zone as Azure SQL (UTC by default).

Required tiers depend on whether you are using the memory-optimized tables (In-Memory OLTP) feature of MS SQL Server 2016 and 2019. This feature improves the performance of transaction processing, data ingestion, data load, and transient data scenarios.

With memory-optimized tables:

  • DTU Premium Tier P2
  • vCore Business Critical Gen4 Tier 2
  • vCore Business Critical Gen5 Tier 2

Without memory-optimized tables:

  • DTU Standard Tier S3
  • DTU Premium Tier P1
  • vCore General Purpose Tier 2
  • vCore Business Critical Tier 2

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:

  • IPAM IPX
    • 750,000 IP
  • Log Analyzer LA250 - LA1000
  • NCM DLX
    • 1 Additional Polling Engine (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)
  • SAM SAM300
    • 1 APE for every 10,000 component monitors
  • SCM SCM5000
  • UDT UTX
    • 150,000 ports per polling engine
  • VMAN VMS480 and higher
    • Per VMAN Recommendations, increase the total memory on the server by 16 GB.
    • 1 APE for every 3000 VMs. VMAN APEs do not require extra licenses.
  • VNQM IPX
    • ~5,000 IP SLA operations per polling engine

Orion
server

Physical server or virtual machine (VM)

  • CPU: 4 cores + 1 core for each additional module
  • RAM: 8 GB + 2 GB for each additional module

    How do I calculate hardware requirements?

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

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

SolarWinds Orion SQL database
server

  • Eight processor cores or more
  • 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
  • SQL Server 2017, 2016, or 2014, Standard or Enterprise Edition

    SolarWinds recommends SQL Server 2016 SP1 or later.

NTA Flow Storage
server

Physical server or virtual machine

  • Quad core processor or better
  • 16 GB RAM
    Note: Increase the NTA Flow Storage database RAM as the database size increases.
  • 100 GB - 1 TB of storage capacity on local NTFS disk
    More 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 per second retained for 30 days. For example, if you want 50,000 flows per second stored for 30 days, you need a base of 100 GB plus an additional 400 GB of storage.
  • 1 x 1 Gb dedicated NIC

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 and later requires an instance of MS SQL Server 2016 SP1 or later for storing flow data. See NTA current version 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 2019 or 2016

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

Log Analyzer database

Physical server or virtual machine

  • Quad core processor or better
  • 16 GB RAM
  • 100 GB - 1 TB of storage capacity on local NTFS disk
    Note: More or less space may be required, depending on the number of stored events. Log Analyzer supports 1,000 Events per Second across all polling engines.
  • 1 x 1 Gb dedicated NIC
  • MS SQL Server 2016 with SP1 and later, Standard or Datacenter Edition
  • Supported collations:
    • English with collation setting SQL_Latin1_General_CP1_CI_AS
    • English with collation setting SQL_Latin1_General_CP1_CS_AS

Amazon Web Service VMs

Orion server

m5d.2xlarge

Primary database
server (SolarWinds Orion database)

r5d.2xlarge

When using the Amazon RDS as your database server for large environments, use db.r4.4xlarge template.

NTA Flow Storage

r5d.4xlarge

Log Analyzer database

r5d.4xlarge

Amazon RDS db.r4.4xlarge

Microsoft Azure

Orion
server

DS4_v2

8 CPU

32 GB RAM

150 GB disk

Primary database
server (SolarWinds Orion database)

DS4_v2

Azure Storage Disk with Provisioned IOPS recommended

8 CPU

61 GB RAM

System SSD 160 GB (included in DS4_v2) + 1x Data EBS Volume 150 GB + 2x Data Azure Storage Disk Volume 500 GB*

NTA Flow Storage

D15_v2

16 CPU

122 GB RAM (2.5 TB is Flow Storage, 300k FPS with 30-days retention, Azure Storage Disk with Provisioned IOPS recommended)

System SSD 320 GB (included in D12_v2) + Data Azure Storage Disk Volume 2.5 TB

Log Analyzer Database

D15_v2

16 CPU

122 GB RAM (2.5 TB is events storage, 300k EPS with 30-days retention, Azure Storage Disk with Provisioned IOPS recommended)

System SSD 320 GB (included in D12_v2) + Data Azure Storage Disk Volume 2.5 TB

Azure SQL DB

Only products on Orion Platform 2019.2.

The Orion Server must be set to use the same time zone as Azure SQL (UTC by default).

Required tiers depend on whether you are using the memory-optimized tables (In-Memory OLTP) feature of MS SQL Server 2016 and 2019. This feature improves the performance of transaction processing, data ingestion, data load, and transient data scenarios.

With memory-optimized tables:

  • DTU Premium Tier P4
  • vCore Business Critical Gen4 Tier 4
  • vCore Business Critical Gen5 Tier 4

Without memory-optimized tables:

  • DTU Standard Tier S4
  • DTU Premium Tier P2
  • vCore General Purpose Tier 2
  • vCore Business Critical Tier 2

Extra large deployment guidelines

To monitor up to 400,000 elements, ensure your deployment meets the following minimum requirements. Extra large environments 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 2019 or 2016, 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 2014, 2014 SP1 or 2014 SP2
    • MS SQL Server 2016 SP1, 2016 SP2
    • MS SQL Server 2017 (including Linux installs)

      SolarWinds recommends SQL Server 2016 SP1 or later.

Recommended:

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

Physical server or virtual machine

  • Quad core processor or better
  • 16 GB RAM
    Note: Increase the NTA Flow Storage database RAM as the database size increases.
  • 100 GB - 1 TB of storage capacity on local NTFS disk
    Note: More 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 per second retained for 30 days. For example, if you want 50,000 flows per second stored for 30 days, you need a base of 100 GB plus an additional 400 GB of storage.
  • 1 x 1 Gb dedicated NIC

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 and later requires an instance of MS SQL Server 2016 SP1 or later for storing flow data. See NTA current version requirements for more details.
Log Analyzer database

Physical server or virtual machine

  • Quad core processor or better
  • 16 GB RAM
  • 100 GB - 1 TB of storage capacity on local NTFS disk
    Note: More or less space may be required, depending on the number of stored events. Log Analyzer supports 1,000 Events per Second across all polling engines.
  • 1 x 1 Gb dedicated NIC
  • MS SQL Server 2016 with SP1 and later, Standard or Datacenter Edition
  • Supported collations:

    • English with collation setting SQL_Latin1_General_CP1_CI_AS
    • English with collation setting SQL_Latin1_General_CP1_CS_AS

Amazon Web Service

Orion
server

m5.4xlarge

Additional polling
engine server

m5.xlarge

Primary database
server (SolarWinds Orion database)

r5d.4xlarge (database server)

db.r4.8xlarge (Amazon RDS)

NTA Flow Storage database

r5d.4xlarge

Log Analyzer database

r5d.4xlarge

Amazon RDS db.r4.8xlarge

Microsoft Azure

Orion
server

DS4_v2

8 CPU

32 GB RAM

150 GB disk

Primary database
server (SolarWinds Orion database)

DS4_v2

Azure Storage Disk with Provisioned IOPS recommended

8 CPU

61 GB RAMg

System SSD 160 GB (included in DS4_v2) + 1x Data EBS Volume 150 GB + 2x Data Azure Storage Disk Volume 500 GB*

NTA Flow Storage

D15_v2

16 CPU

122 GB RAM (2.5 TB is Flow Storage, 300k FPS with 30-days retention, Azure Storage Disk with Provisioned IOPS recommended)

System SSD 320 GB (included in D12_v2) + Data Azure Storage Disk Volume 2.5 TB

Log Analyzer Database

D15_v2

16 CPU

122 GB RAM (2.5 TB is event storage, 300k EPS with 30-days retention, Azure Storage Disk with Provisioned IOPS recommended)

System SSD 320 GB (included in D12_v2) + Data Azure Storage Disk Volume 2.5 TB

Azure SQL DB

Only products on Orion Platform 2019.2.

The Orion Server must be set to use the same time zone as Azure SQL (UTC by default).

Required tiers depend on whether you are using the memory-optimized tables (In-Memory OLTP) feature of MS SQL Server 2016 and 2019. This feature improves the performance of transaction processing, data ingestion, data load, and transient data scenarios.

With memory-optimized tables:

  • DTU Premium Tier P11
  • vCore Business Critical Gen4 Tier 16
  • vCore Business Critical Gen5 Tier 14

Without memory-optimized tables up to 100k elements (up to 400k):

  • DTU Standard Tier S9 (S12)
  • DTU Premium Tier P6 (P11)
  • vCore General Purpose Tier 16 (30)
  • vCore Business Critical Tier 8 (14)