Documentation forServer & Application Monitor

SAM 2020.2 System Requirements

Release date: June 4, 2020

Updated: August 25, 2020

Important: These recommended system requirements are for SolarWinds Server & Application Monitor (SAM) 2020.2 as a single product installed on Orion Platform 2020.2. They also apply to the SAM 2020.2.1 service release.

This document includes the following sections:

System requirements may vary, depending on:

  • If you deploy SAM in the cloud or on-premises.
  • The size of the environment to be monitored.
  • If your environment includes other Orion Platform modules.

To determine requirements beyond those included here, review the following documents:

If you deploy additional Orion Platform modules, review related guides, release notes, and system requirements in the SolarWinds Success Center, plus the Multi-module system guidelines for the Orion Platform.

Orion server software requirements

Do not install SAM on the same server as SolarWinds Access Rights Manager (ARM).

To deploy SAM locally, on a server, review the following recommendations for the main Orion server. Alternatively, see Cloud deployment options.

Software Requirements
Operating system
  • Microsoft Windows Server 2012 R2*
  • Microsoft Windows Server 2016
  • Microsoft Windows Server 2019

*Support for Microsoft Windows Server 2012 R2 is included in SAM 2020.2 so SAM 6.7 customers can upgrade to the latest version of SAM. For the best experience, SolarWinds recommends using Windows Server 2016 or 2019 for the Orion server.

Desktop operating systems, such as Windows 10, 64-bit Pro or Enterprise are supported for evaluation environments only. For a smooth transition from an evaluation to production deployment, SolarWinds recommends that you avoid installing evaluations on desktop operating systems.

Support differences between Orion Agents and Orion Platform products

  • You cannot install Orion Platform products on domain controllers.
    Exception: You can install Orion agents on domain controllers.
  • You cannot install Orion Platform products or any scalability engines on Microsoft SharePoint, Microsoft Exchange, or BlackBerry servers. Exception: You can install Orion Agents on the same server as a SharePoint, Exchange or Blackberry server.
Operating system languages
  • English (UK or US)
  • German
  • Japanese
  • Simplified Chinese
IP address version
  • IPv4
  • IPv6
  • Dual stack

CIDR notation is not supported for IPv6 addresses.

Web server

If you're not using Windows Authentication, make sure Anonymous Authentication is enabled for the SolarWinds NetPerfMon website. Anonymous Authentication is used with the default forms-based authentication.

The SolarWinds Orion Installer adds IIS by default, but you can install it manually to reduce installation time.

Microsoft .NET Framework

.NET 4.8

Run the same version of. NET on your primary server and any Additional Polling Engines (APEs) or Additional Web Servers (AWS) in the environment.

SolarWinds recommends installing .NET on your primary Orion server and all scalability engines before installing SAM. See this article for details.

Services

Starting in Orion Platform 2020.2, the Orion Log Viewer (OLV) replaces the legacy Syslog and Trap Viewers. If you continue using Syslogs and Traps, make sure the following services are running after installation is complete:

  • SolarWinds Syslog Service
  • SolarWinds Trap Service
Orion Web Console browser

The Orion Platform supports the two latest versions of the following web browsers available on the release date:

  • Firefox
  • Chrome

The following browsers are also supported:

  • Microsoft Edge
  • Microsoft Internet Explorer 11 with Active scripting

    Starting with Orion Platform 2020.2, some pages are not compatible with IE 11. Classic Dashboards continue to support Internet Explorer 11.

    Do not enable Enterprise Mode on Internet Explorer. This setting forces Internet Explorer to emulate version 7, which is not supported.

Browser requirements:

  • JavaScript enabled
  • Cookies enabled
Account privileges SolarWinds recommends that Orion administrators have local administrator privileges on the Orion server to ensure full functionality of local Orion Platform tools. Orion user accounts limited to the Orion Web Console do not require local administrator privileges.
Other PowerShell 5 is required on Windows Server 2012 R2 to use the offline installer to install Orion Platform 2020.2.

Orion server hardware requirements

Return to top

The following table lists minimum and recommended hardware requirements for your Orion server that hosts the Orion Platform and its modules. Installing multiple modules may change the requirements. Use the minimum requirements if you're evaluating the product or do not anticipate heavy usage.

SolarWinds strongly suggests using the recommended hardware configuration to avoid potential performance issues caused by a heavy load or custom configurations, such as increased data retention or more frequent polling intervals.

Hardware requirements are listed by deployment size, based on SAM node-based license levels. Click here to compare component-based vs. node-based license levels. CPU recommendations for SAM1000 and larger deployments use the PassMark Score. For details, see CPU Benchmarks (© 2019 PassMark® Software, obtained at www.cpubenchmark.net on April 15, 2020).

Feature SAM100 SAM300 SAM400 SAM1000 and larger
CPU Quad core processor or better Quad core processor or better Quad core processor or better CPUs with a total combined PassMark score of 7,000 or higher
Do not enable Physical Address Extension (PAE).
Hard drive space

10 GB minimum

20 GB recommended

15 GB minimum

40 GB recommended

30 GB minimum

40 GB recommended

40 GB minimum

60 GB recommended

Read/Write I/O: 1,000 IOPS

SolarWinds recommends two 146 GB 15K (RAID 1/Mirrored Settings) hard drives with a dedicated drive for the server OS and Orion Platform installation.

Some common files may need to be installed on the same drive as the server OS. You may want to move or expand the Windows temporary directories.

Memory

6 GB minimum

8 GB recommended

8 GB minimum

16 GB recommended

16 GB minimum

32 GB recommended

32 GB recommended

Orion database server (SQL Server) requirements

The following table lists requirements for your Orion database server, using SAM node-based license levels.

  • If using component-based licensing, click here to compare component- and node-based license levels.
  • The Orion server and the Orion database must use separate servers.
  • If you install on a virtual machine, you must maintain your Orion database on a separate, physical drive.
  • As of Orion Platform 2019.4, you can use an Azure SQL Database Managed Instance as your database server. See the Orion Platform Products Installation and Upgrade Guide for supported deployment scenarios.
Feature

SAM100

SAM300 SAM400 SAM1000 and larger
Microsoft SQL Server

Express, Standard, or Enterprise versions of:

  • SQL Server 2012*
  • SQL Server 2014
  • SQL Server 2014 SP1
  • SQL Server 2014 SP2
  • SQL Server 2016
  • SQL Server 2016 SP1
  • SQL Server 2016 SP2
  • SQL Server 2017
  • SQL Server 2019

*Support for SQL Server 2012 is included in SAM 2020.2 so SAM 6.7 customers can upgrade to the latest version of SAM. For the best experience, SolarWinds recommends using later versions of SQL Server.

Recommendations:

  • Use the 64-bit version of SQL Server.
  • Use SQL Server Express only for evaluations and small environments, such as SAM10. Note that Hardware health and AppInsight for Active Directory are database-intensive features that can impact database capacity and performance.
  • Use the Simple database recovery model for best performance.
  • Use the Full database recovery model if your Orion database is hosted on a SQL cluster or you use Always On Availability. However, you must back up your database regularly and ensure that the volume where you store transactions log has free space equal to or greater than the size of the Orion database. Transaction logs will continue to grow indefinitely until a database backup occurs and transactions are committed to the database. SolarWinds recommends daily database backups if using Full database recovery model.
  • To reduce disk utilization when using SQL Server Express, shorten the Detailed Statistic Retention period on the Polling Settings page. The default value is 7 days. See Optimize the database used by Orion Platform products.

Enterprise versions of:

  • SQL Server 2012*
  • SQL Server 2014
  • SQL Server 2014 SP1
  • SQL Server 2014 SP2
  • SQL Server 2016
  • SQL Server 2016 SP1
  • SQL Server 2016 SP2
  • SQL Server 2017
  • SQL Server 2019
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

SolarWinds products support a case-insensitive (CI) database on a CS SQL Server.

SolarWinds products do not support case-sensitive databases.

CPU Quad core processor or better Dual quad core processor or better Dual quad core processor or better CPUs with a total combined PassMark score of 32,000 or higher
Hard drive space

20 GB minimum

40 GB recommended

50 GB minimum

100 GB recommended

100 GB minimum

400 GB recommended*

2 TB recommended

Read/Write I/O:

30,000 IOPs minimum

190,000 IOPS or better recommended

1 Gbit dedicated NIC

  • Due to intense I/O requirements, a RAID 1+0 drive is strongly recommended for the Orion database, data, and log files with a dedicated drive for the server OS and tempdb files. Other RAID configurations can negatively affect SQL Server performance.
  • Mirrored drives for the OS and RAID 1+0 for database data files are recommended.
  • Solid-state drives (SSD) are strongly recommended.

Some common files may need to be installed on the same drive as your server OS. You may want to move or expand the Windows or SQL temporary directories. See Working with Temporary Directories.

Memory

16 GB minimum

32 GB recommended

16 GB minimum

64 GB recommended

64 GB minimum

128 GB recommended

256 GB minimum

512 GB recommended

Authentication Use either mixed-mode or Windows authentication. If you require SQL authentication, enable mixed mode on your SQL server.
Other software

SolarWinds recommends installing SQL Server Management Studio on your Orion database server. The Orion Installer adds the following x86 components if they're not found on the Orion database server:

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

For remote execution of PowerShell scripts, PowerShell 2.0 or later is required on the Orion server, Additional Polling Engines, and target servers.

You cannot host the Orion database on SharePoint, Exchange, or BlackBerry servers.

*SolarWinds recommends the following hard drive configuration for large deployments in physical environements:

  • 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,

Cloud deployment

Orion Platform products support the following cloud solutions:

Amazon Web Services

Return to top

To deploy a single Orion Platform product using Amazon Web Service, consider using the following templates, listed according to SAM node-based license levels. Click here to compare component- and node-based license levels.

Requirements

SAM100

SAM300

SAM400

SAM1000 and larger

Orion server m4.large

m4.xlarge

Recommended: m5d.xlarge with SDD drive

m5d.2xlarge

Recommended: m5d.2xlarge with SSD

m5.2xlarge

Recommended: m5d.2xlarge with SSD

Orion database using Amazon RDS for SQL Server db.r4.xlarge db.r4.xlarge

db.r4.2xlarge

db.r5.16xlarge

Orion database deployed on an Amazon VM m4.large r4.xlarge

r4.2xlarge

Recommended: r5d.4xlarge

r5d.24xlarge

IOPS: 30,000

Additional Polling Engines Only relevant for large environments that monitor over 12,000 components m5.xlarge

Microsoft Azure

Return to top

The Orion Platform supports several Microsoft Azure deployment options, as listed here according to SAM node-based license levels. If using component-based licensing, click here to compare component- and node-based license levels.

To deploy a single Orion Platform product on Microsoft Azure, consider using the following instance types, based on your deployment size. (Recommendations use SAM node-based license levels. Click here to compare component- and node-based license levels.)

Feature

SAM100

SAM300

SAM400

SAM1000 and larger

Orion server

A4_v2

DS12_v2

DS4_v2

DS4_v2

Orion database using Azure SQL Database

All installed products must run on Orion Platform 2019.2 or later.

The time zone setting of the Orion Server must match the Azure SQL DB time zone (UTC).

To deploy Azure SQL and create a new user in the Configuration wizard, SA account credentials are required in the Configuration wizard.

Starting with Orion Platform 2019.4, the Orion Platform does not support memory-optimized tables. If you are using memory optimized tables, they are automatically disabled.

DTU Standard Tier S3 or better

vCore General Purpose Tier 2 or better

DTU Standard Tier S3 or better

vCore General Purpose Tier 2 or better

DTU Standard Tier S4 or better

vCore General Purpose Tier 2 or better

DTU Standard Tier S12 (up to 100k components), P15 (up to 400k components), or better

vCore General Purpose Tier 16 (up to 100k components), 30 (up to 400k components) or better

Orion database using Azure SQL Database managed instance

Gen5
4 vCores

Gen5
8 vCores

Gen5
16 vCores

Gen5
40 vCores

Orion database in an Azure VM

A4_v2

DS4_v2 Standard

E8s_v3

E64as_v4

IOPS 30,000+

* Azure Storage Disk volumes are not your dedicated hardware. Consider using Azure Reserved Instances of storage disk volumes for SQL servers.


Port requirements

Review and open ports on the Orion server to support communication between the Main Polling Engine, Additional Polling Engines (APEs), and Additional Web Servers (AWS).

Port # Protocol Service/Process Direction Description Encryption
User-defined, default: 22 SSH

SolarWinds Job Engine v2

IIS

Outbound from the Orion server to the device

Cisco ASA device access through the CLI.

Nutanix hardware health monitoring

Device-based
25 TCP SolarWinds Alerting Service V2 Outbound SMTP port for non-encrypted messages.  
53 UDP SolarWinds Job Engine v2 Bidirectional Resolve DNS queries.  
80 TCP IIS Inbound

Default Additional Web Server port. If you specify any port other than 80, include it in the URL used to access the Orion Web Console. For example, if you specify 192.168.0.3 and port 8080, the URL to access the Orion Web Console is http://192.168.0.3:8080.

Open the port to enable communication from your computers to the Orion Web Console.

The port may also be used for Cisco UCS monitoring.

 
135 TCP Microsoft EPMAP (DCE/RPC Locator service) Bidirectional

WMI uses port 135 to initiate communication with a remotely managed host, then switches to any random port between TCP ports 1024 — 65535. Click here for details.

Asset Inventory data collection.

 
161 UDP

SolarWinds Job Engine v2

SolarWinds Cortex service

Bidirectional

Send and receive SNMP information.

Asset Inventory data collection.

SNMP v1 and v2 are unencrypted.

SNMP v3 uses AES and 3DES encryption.

162 UDP

SolarWinds Trap service

SNMP Informs

Bidirectional Receive trap messages.  
443 TCP IIS Bidirectional

Default port for HTTPS binding. Also used for bidirectional ESX/ESXi server polling and Cisco UCS device monitoring.

SSL
445 TCP File and Printer Sharing (SMB-In) Bidirectional Used to copy script that checks for Windows updates during Asset Inventory polling via WMI.  
465 TCP SolarWinds Alerting Service V2 Outbound

SMTP port used to send TLS-enabled email alert actions.

SSL
514 UDP SolarWinds Syslog Service Bidirectional Receive syslog messages.  
587 TCP SolarWinds Alerting Service V2 Outbound SMTP port used to send TLS-enabled email alert actions.  
1433 TCP

SolarWinds Administration Service

SolarWinds Alerting Service V2

SolarWinds Information Service

SolarWinds Information Service V3

SolarWinds Orion Module Engine

Outbound

Communication between the Orion Server and the Orion database server.

 
1434 UDP

SolarWinds Administration Service

SolarWinds Alerting Service V2

SolarWinds Information Service

SolarWinds Information Service V3

SolarWinds Orion Module Engine

SQL Server Browse Service

Bidirectional

Communication with SQL Server Browser Service to determine how to handle non-standard SQL Server installations.

Required only if your Orion database server is configured to use dynamic ports.

 
1801 TCP MSMQ Bidirectional

MSMQ WCF binding with WCF encryption.

 
5671 TCP

RabbitMQ

Bidirectional

For RabbitMQ messaging (AMQP/TLS) between the Main Polling Engine and Additional Polling Engines, High Availability servers, or Additional Web Servers.

TLS 1.2
17777 TCP

SolarWinds Cortex (communication)

SolarWinds Information Service

SolarWinds Information Service V3

SolarWinds Orion Module Engine

Bidirectional

Communication between services and SolarWinds Orion module traffic.

Communication between the Orion Web Console, the Main Polling Engine, and all scalability engines.

Communication between the main server and pool members.

RSA handshake, AES 256 communication using WCF

TLS 1.2 with SolarWinds Cortex

17778 HTTPS and TCP

SolarWinds Agent

Bidirectional

Communication between the Orion server, the SolarWinds Information Service (SWIS) API, and agents.

SSL

Additional SAM technology requirements

*See also Third-party software required to monitor Asset Inventory and hardware health.

SAM licensing levels

Return to top

If using component-based licensing, this table provides equivalent node-based license tiers for SAM system requirements.

Node-based license tier Component-based license tier
SAM10 AL150
SAM25 AL300
SAM50 AL700
SAM75 AL1100
SAM100 AL1500
SAM200 AL2500
SAM300* ALX

*Additional tiers are available. Contact SolarWinds Sales for details.

More learning resources

To learn more about Orion Platform requirements and configurations, see:


Legal notices

Return to top

© 2020 SolarWinds Worldwide, LLC. All rights reserved.

This document may not be reproduced by any means nor modified, decompiled, disassembled, published or distributed, in whole or in part, or translated to any electronic medium or other means without the prior written consent of SolarWinds. All right, title, and interest in and to the software, services, and documentation are and shall remain the exclusive property of SolarWinds, its affiliates, and/or its respective licensors.

SOLARWINDS DISCLAIMS ALL WARRANTIES, CONDITIONS, OR OTHER TERMS, EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, ON THE DOCUMENTATION, INCLUDING WITHOUT LIMITATION NONINFRINGEMENT, ACCURACY, COMPLETENESS, OR USEFULNESS OF ANY INFORMATION CONTAINED HEREIN. IN NO EVENT SHALL SOLARWINDS, ITS SUPPLIERS, NOR ITS LICENSORS BE LIABLE FOR ANY DAMAGES, WHETHER ARISING IN TORT, CONTRACT OR ANY OTHER LEGAL THEORY, EVEN IF SOLARWINDS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

The SolarWinds, SolarWinds & Design, Orion, and THWACK trademarks are the exclusive property of SolarWinds Worldwide, LLC or its affiliates, are registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other SolarWinds trademarks, service marks, and logos may be common law marks or are registered or pending registration. All other trademarks mentioned herein are used for identification purposes only and are trademarks of (and may be registered trademarks) of their respective companies.