Submit a ticketCall us

WebinarWebinar: A checklist for planning your Network Performance Monitor (NPM) upgrade

Are you ready for your next upgrade? To help you plan smoothly, join this webcast to learn more about, SolarWinds® Orion® Installer, SolarWinds Upgrade Advisor, Upgrades Guides, Training Videos, and other resources available. We’ll share key upgrade planning considerations, lessons learned from customers with practical advice from SolarWinds Product Experts. We’ll also give practical tips to identify the estimated time needed and resources, how to prepare the business and IT staff for changes, ways to plan for required system changes, and more.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > NPM Documentation > Network Performance Monitor Getting Started Guide > Production installation > Orion multi-module system guidelines for a SolarWinds NPM installation

Orion multi-module system guidelines for a SolarWinds NPM installation

Created by Chris.Moyer_ret, last modified by Chris.Moyer_ret on Oct 03, 2016

Views: 19,588 Votes: 3 Revisions: 28

This topic applies to all Orion Platform products.

Updated: December 4, 2018

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 or Log Manager 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.

End-of-support notices

Orion Platform 2018.4 products 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, 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 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:

  • IPAM IP1000 - IP4000
  • NCM DL50 - DL200
  • NPM SL100 - SL500 (including up to 10 remote agents for DPI)
  • SAM AL150 - AL300
  • 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 Manager for Orion, 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

  • Storage: 150 GB, 15,000 RPM
  • 1 x 1 Gb dedicated NIC
  • Windows Server 2016, 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
  • Windows Server 2016, Standard or Datacenter Edition
  • SQL Server 2017, 2016, or 2014, Standard or Enterprise Edition

    SolarWinds recommends SQL Server 2016 SP1 or later.

1More or less space may be needed depending on your data retention policies, number of elements measured, and polling frequency. (or more) storage in RAID 1+0 configuration (RAID 5 not supported)

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.

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 Manager for Orion LM10 - LM250
  • NCM DL500 - DL1000
  • SAM AL700 - AL1100
  • 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

  • 150 GB, 15,000 RPM
  • 1 x 1 Gb dedicated NIC
  • Windows Server 2016, 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
  • Hardware RAID Controller (software RAID not supported)
  • Windows Server 2016, Standard or Datacenter Edition
  • 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 GBRAM
  • 100 GB - 1 TB4 of storage capacity on local NTFS disk
  • 1 x 1 Gb dedicated NIC
  • Windows Server 2016, 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 SP1 or later for storing flow data. See NTA 4.4 requirements for more details.
Log Manager for Orion database

Physical server or virtual machine

  • Quad core processor or better
  • 16 GB RAM
  • 100 GB - 1 TB5 of storage capacity on local NTFS disk
  • 1 x 1 Gb dedicated NIC
  • Windows Server 2016, 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

2 More or less space may be needed depending on your data retention policies, number of measured elements, and polling frequency. (or more) storage in RAID 1+0 configuration (RAID 5 not supported)

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

4 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 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.

5 More or less space may be required, depending on the number of stored events. Log Manager for Orion supports 1,000 Events per Second across all polling engines.

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 Manager for Orion database

r3.xlarge

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 Manger for Orion LM250 - LM1000
  • 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)
  • SAM ALX
    • 1 APE for every 10,000 component monitors
    • Maximum of 50,000 component monitors per primary Orion SAM server + 4 APEs
  • SCM SCM5000
  • 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.
  • VNQM IPX
    • ~5,000 IP SLA operations per polling engine

Orion
server

Physical server or virtual machine (VM)

  • Storage: 150 GB, 15,000 RPM
  • 1 x 1 Gb dedicated NIC
  • Windows Server 2016, 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, Standard or Datacenter Edition
  • 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 GB6 RAM
  • 100 GB - 1 TB7 of storage capacity on local NTFS disk
  • 1 x 1 Gb dedicated NIC
  • Windows Server or 2016, 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 SP1 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

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

Log Manager for Orion database

Physical server or virtual machine

  • Quad core processor or better
  • 16 GB RAM
  • 100 GB - 1 TB8 of storage capacity on local NTFS disk
  • 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

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

7 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 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.

8 More or less space may be required, depending on the number of stored events. Log Manager for Orion supports 1,000 Events per Second across all polling engines.

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 Manager for Orion database

r5d.4xlarge

 

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, 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 GB9 RAM
  • 100 GB - 1 TB10 of storage capacity on local NTFS disk
  • 1 x 1 Gb dedicated NIC
  • Windows Server 2016 or later, 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 SP1 or later for storing flow data. See NTA 4.4 requirements for more details.
Log Manager for Orion database

Physical server or virtual machine

  • Quad core processor or better
  • 16 GB RAM
  • 100 GB - 1 TB11 of storage capacity on local NTFS disk
  • 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

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

10More 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.

11More or less space may be required, depending on the number of stored events. Log Manager for Orion supports 1,000 Events per Second across all polling engines.

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 Manager for Orion database

r5d.4xlarge

Disclaimer: Please note, any content posted herein regarding third-party software is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.

Last modified

Tags

Classifications

Public