Multi-module system guidelines

If you have more than one 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.

We recommend checking the admin guide for a full list of all supported versions.

In AWS, the Elastic Block Storage (EBS) volumes are not your dedicated hardware devices. For SQL and NTA Flow Storage Database, we recommend considering the purchase of dedicated instance EBS volumes for medium and large deployments. For large deployments, we also recommend EBS with provisioned IOPS for high performance for intensive database workloads.

If you have only one Orion module, refer to the system requirements listed in the administrator’s guide for that module.

Small deployment guidelines

Modules

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.

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

Orion Application
Server Specifications

Physical server or virtual machine

  • Quad core processor or better
  • 8-16 GB RAM
  • 150 GB, 15,000 RPM
  • 1 x 1 Gb dedicated NIC
  • Windows Server 2012 R2, 2012, or 2008 R2 SP1

The Orion installer installs IIS (32-bit mode) and .NET 4.5 if they are not already on your server.

SQL Database
Server Specifications

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 2012 R2, 2012, or 2008 R2 SP1
  • Microsoft SQL Server 2014, 2012, or 2008 R2 Standard Edition

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

AWS VMs

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

Medium deployment guidelines

Modules

NPM SL500 - SL2000

NTA for NPM SL2000

  • 50,000 FPS received sustained on the main poller

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

Orion Application
Server Specifications

Physical server or virtual machine

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

The Orion installer installs IIS (32-bit mode) and .NET 4.5 if they are not already on your server.

SQL Database
Server Specifications

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 2012 R2, 2012, or 2008 R2 SP1
  • Microsoft SQL Server 2014, 2012, or 2008 R2 Standard 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 2012 R2, 2012, or 2008 R2 SP1

NTA-specific information

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

3RAM for the NTA Flow Storage Database should be increased as the database size increases.

4More or less space may be needed depending on your data retention policies and the number of flows stored. You need approximately 8 GB of additional storage for every 1000 flows that are 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.

AWS VMs

Orion Application Server
  • m4.xlarge
  • 2 CPUs, 16GB RAM
  • 150GB (default is 50GB for m4.large)
Primary Database Server
  • r3.xlarge
  • 4 CPUs, 30.5GB RAM
  • SSD 80GB (included in r3.xlarge) + EBS Volume 500GB
NTA Flow Storage
  • r3.xlarge
  • 4 CPUs, 30.5GB RAM
  • SSD 80GB (included in r3.xlarge) + EBS Volume 500GB
  • 8 GB for every received sustained 1000 Flows/s with 30-days retention period

Large deployment guidelines

Modules

NPM SLX (with multiple pollers)

NTA for NPM SLX

  • 50,000 FPS received sustained on the main poller
  • Up to 6 pollers (5 in addition to the main poller) 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

Orion Application
Server Specifications

Physical server or virtual machine

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

The Orion installer installs IIS (32-bit mode) and .NET 4.5 if they are not already on your server.

SQL Database
Server Specifications

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 2012 R2, 2012, or 2008 R2 SP1
  • Microsoft SQL Server 2014, 2012, or 2008 R2 Standard 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 2012 R2, 2012, or 2008 R2

Additional Polling Engine
Server Specifications

Virtual machine recommended

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

The Orion installer installs IIS (32-bit mode) and .NET 4.5 if they are not already on your server.

NTA-specific information

AWS VMs

Orion Application Server
  • m4.2xlarge
  • 2 CPUs, 16GB RAM
  • 150GB (default is 50GB for m4.large)
Primary Database Server
  • r3.2xlarge
  • 4 CPUs, 30.5GB RAM
  • SSD 80GB (included in r3.xlarge) + EBS Volume 500GB
NTA Flow Storage
  • r3.4xlarge
  • 16 CPU, 122GB RAM
  • SSD 320GB (included in r3.xlarge) + EBS Volume 2.5TB
  • 2.5TB is Flowstorage, 300k FPS with 30-days retention, EBS with Provisioned IOPS recommended.

Additional references