SAM 6.8 System Requirements

Released: March 12, 2019

Updated: July 10, 2019

Important: These recommended system requirements are for SolarWinds Service & Application Monitor (SAM) 6.8 as a single product installed on Orion Platform 2018.4.

For additional information on requirements and configurations, see the Multi-module system guidelines. You should also review your product administration guides and release notes for the exact product requirements beyond these minimums. We also recommend reviewing the SAM 6.8 release notes.

Software requirements

  • SolarWinds only supports installing the Orion agent on domain controllers. Do not install any other SolarWinds products on domain controllers.
  • SolarWinds only supports installing the Orion agent on the same server as a Microsoft SharePoint, Microsoft Exchange, or Research in Motion (RIM) Blackberry server. Sharing a database server with those applications is not supported.

The following table lists software requirements and recommendations for a SolarWinds installation on both physical and virtual computers.

Software Requirements
Operating System

Deprecation notice: Starting with Orion Platform 2018.4, Windows Server 2012 and 2012 R2 are not supported anymore.

  • Windows Server 2016
  • Windows Server 2019

Desktop operating systems, such as Windows 10, 64-bit (not Standard Edition), are supported for evaluation environments only. To make a smooth transition from your evaluation to production deployment, SolarWinds recommends that you avoid installing evaluations on desktop operating systems.

Operating system languages
  • English (UK or US)
  • German
  • Japanese
  • Simplified Chinese
IP address version

IPv4

IPv6 implemented as a dual stack

Dual stack

CIDR notation is not supported for IPv6 addresses.

Web server

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

IIS is installed by the SolarWinds Orion Installer. You can install this software manually to reduce your installation time or network bandwidth.

Microsoft .NET Framework

.NET 4.6.2

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

Services

If you are using the Syslog or SNMP Traps feature of the Orion Platform, make sure the following services are running after installation is complete to collect syslog messages and traps:

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

Orion Platform products support the two most recent versions of the following web browsers available at the release date:

  • Firefox
  • Chrome

Orion Platform products also support the following browsers:

  • Microsoft Internet Explorer 11 with Active scripting
  • Do not enable Enterprise Mode on Internet Explorer. This setting forces Internet Explorer to emulate version 7, which is not supported.
  • Microsoft Edge

Account privileges

SolarWinds recommends that SolarWinds Orion administrators have local administrator privileges on the Orion server to ensure full functionality of local SolarWinds tools.

Orion user accounts limited to the Orion Web Console do not require local administrator privileges.

Hardware requirements

Return to top

The following table lists minimum hardware requirements and recommendations for your SolarWinds Orion server on both physical and virtual computers. Use the minimum hardware configuration if you are 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.

Installing multiple Orion Platform products on the same computer may change the requirements.

Hardware requirements are listed by deployment size, based on SAM license levels. CPU recommendations for XL deployments use the PassMark Score. To learn more, see Pass Mark Performance Test (Copyright © 2018 PassMark® Software, obtained at https://www.cpubenchmark.net/high_end_cpus.html on April 9, 2018).

Feature AL150 - AL300 AL700 — AL1100 AL1500 — ALX
CPU Quad core processor or better Quad core processor or better Quad core processor or better
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

100 GB recommended

SolarWinds recommends two 146 GB 15K (RAID 1/Mirrored Settings) hard drives with a dedicated drive for the server operating system and SolarWinds 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

10 GB minimum

20 GB recommended

15 GB minimum

40 GB recommended

30 GB minimum

40 GB recommended

Database server (SQL Server) requirements

Return to top

The following table lists software and hardware requirements for your SolarWinds Orion database server using SolarWinds SAM license levels.

  • The Orion server and the SolarWinds Orion database must use separate servers.
  • If you install on a virtual machine, you must maintain your SQL Server database on a separate, physical drive.
Requirements AL150 - AL300 AL700 — AL1100 AL1500 — ALX
SQL Server

SolarWinds supports Express, Standard, or Enterprise versions of the following:

  • 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 (including installations on Linux)

End-of-support notice: Products running on Orion Platform 2018.4 and later are no longer compatible with 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.

SolarWinds recommends that you use Express versions only for evaluations and very small environments.

Recommendations

  • Use the 64-bit version of SQL Server.
  • Use the Simple database recovery mode to ensure best performance.
  • You can set the database recovery model to Full Recovery if your Orion Database is hosted on a SQL Cluster or if you use Always On Availability. However, you must back up your database regularly and ensure that volume you store your transaction log has free space that is at least equal to or greater than the size of your Orion database. Your transaction logs will continue to grow indefinitely until a database backup is performed and the transactions committed to the database. We recommend daily database backups when you use the Full Recovery model.
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 supports a case insensitive (CI) database on an CS SQL Server.

SolarWinds does not support case-sensitive databases.

CPU Quad core processor or better Dual quad core processor or better Dual quad core processor or better
Hard drive space

20 GB minimum

40 GB recommended

50 GB minimum

100 GB recommended

100 GB minimum

400 GB recommended

SolarWinds recommends the following configuration:

  • 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 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 a 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 a tempdb data file
  • Disk Subsystem 6 Array 6: with 4x 15K 146 GB or 300 GB disks configured in a RAID 0 array for a tempdb log file
  • Due to intense I/O requirements, a RAID 1+0 drive is strongly recommended for the SolarWinds 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 recommended for all components.

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

Memory

AL150

4 GB minimum

8 GB recommended

16 GB minimum

64 GB recommended

64 GB minimum

128 GB recommended

AL300

16 GB minimum

32 GB recommended

Other software

If you are managing the SolarWinds Orion database, SolarWinds recommends installing the SQL Server Management Studio component.

The Orion Installer adds the following required x86 components if they are not found on the Orion database server:

  • SQL Server System Common Language Runtime (CLR) Types. Orion products use secure SQL CLR stored procedures for selected, non-business data operations to improve overall 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.

Amazon Web Services deployments

Return to top

To deploy your Orion Platform product using AWS, consider using the templates cited in the following table, listed according to SAM licensing levels:

Requirements

AL150, AL300, AL700

AL1100, AL1500

AL2500

ALX

Orion server m4.large

m4.xlarge

Recommended: m5d.xlarge with SDD drive

m4.2xlarge

Recommended: m5d.2xlarge with SSD

m5.4xlarge

Recommended: m5d.2xlarge with SSD

Orion database server r4.xlarge r4.xlarge

r3.2xlarge

Recommended: r5d.xlarge with SSD

db.r4.8xlarge

Recommended: R5d.12xlarge

Amazon RDS db.r4.xlarge db.r4.2xlarge db.r4.4xlarge db.r4.8xlarge
Additional Polling Engines N/A m5.xlarge

Orion Platform server port requirements

Return to top

  • Ports 4369, 25672, and 5672 are opened by default on the main Orion server for RabbitMQ messaging. These ports can be blocked by the firewall. When running SolarWinds High Availability, ensure ports 4369 and 25672 are open.

  • RPC ports > 1024 (TCP, bidirectional) is used by the Job Engine v2 process to communicate with Windows nodes.

    See also Orion Platform system requirements.

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

SolarWinds Job Engine v2

IIS

Bidirectional Port for accessing ASA devices through the CLI
25 TCP SolarWinds Alerting Service V2 Outbound SMTP port for non-encrypted messages
53 UDP SolarWinds Job Engine v2 Bidirectional Resolving DNS queries
80 TCP IIS Inbound

Default additional web server port. If you specify any port other than 80, you must include that port in the URL used to access the web console. For example, if you specify an IP address of 192.168.0.3 and port 8080, the URL used to access the 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 might also be used for Cisco UCS monitoring.

161 UDP

SolarWinds Job Engine v2

SolarWinds Cortex

Bidirectional Send and receive SNMP information
162 UDP SolarWinds Trap Service Inbound Receive trap messages
443 TCP IIS Inbound Default port for https binding.
465 TCP SolarWinds Alerting Service V2 Outbound SMTP port used to send TLS-enabled email alert actions
514 UDP SolarWinds Syslog Service Inbound Receive syslog messages
587 TCP SolarWinds Alerting Service V2 Outbound SMTP port used to send TLS-enabled email alert actions
1433 TCP

SolarWinds Alerting Service V2

SolarWinds Administration Service

SolarWinds Information Service

SolarWinds Information Service V3

SolarWinds Orion Module Engine

Outbound Communication between the SolarWinds server and the SQL Server.
1434 UDP

SolarWinds Alerting Service V2

SolarWinds Administration Service

SolarWinds Information Service

SolarWinds Information Service V3

SolarWinds Orion Module Engine

Outbound Communication with the SQL Server Browser Service to determine how to communicate with certain non-standard SQL Server installations. For more information, see this Microsoft Technet article.
1801 TCP MSMQ Bidirectional MSMQ WCF binding (for more information see this KB: http://support.microsoft.com/kb/183293)
5671 TCP

RabbitMQ

AMQP

Bidirectional For encrypted RabbitMQ messaging (AMQP/TLS) into the main polling engine from all Orion servers. Sending messages to RabbitMQ.
17777 TCP

SolarWinds Orion Module Engine

SolarWinds Information Service

SolarWinds Information Service V3

SolarWinds Cortex

Bidirectional

Communication between services and SolarWinds Orion module traffic.

Communication between the Orion Web Console and the polling engine.

Communication between the main server and pool members.

17778 HTTPS SolarWinds Agent Inbound to the Orion server Required for access to the SWIS API and agent communication

SAM port requirements

Return to top

Review and open ports for SAM to support communication for the main polling engine, Orion SQL server, additional polling engines, web server, and additional web servers. For a comprehensive list of requirements relevant for individual features, see Port requirements for all SolarWinds products.

SAM component monitor ports

Return to top

Component/Monitor Port Type Description
DHCP User Experience Monitor 67 UDP The UDP port used for the DHCP request.
DHCP User Experience Monitor 68 UDP The UDP port used for the DHCP response.
Directory Size Monitor See SAM WMI requirements below.
DNS Monitor DNS User Experience Monitor 53 TCP/UDP The TCP and UDP port used for DNS queries.
Download Speed Monitor 19 The port used for the character generator service.
ESX Hardware Monitoring 5989 Ensure port 5989 is open on the firewall.
File Age Monitor File Change Monitor File Existence Monitor Files Size Monitor 445 TCP/UDP These components monitor uses TCP/445 and UDP/445 ports.
File Count Monitor See SAM WMI requirements below.
FTP Monitor FTP User Experience Monitor 21 This field is the port number used for FTP sessions
HTTP Form Login Monitor HTTP Monitor TCP Port Monitor 80 This field is the port number used for HTTP forms-based login sessions.
HTTPS Monitor 443 The port used by the web site.
IMAP4 Monitor 143 and 993 IMAP4 This component monitor uses these ports when used with a Microsoft Exchange mail server.
IMAP4 Port sessions 143 IMAP4 This field is the port number used for IMAP 4 sessions.
IMAP4 Port sessions 585 IMAP4 For Secure IMAP (IMAP4-SSL), use port 585.
IMAP4 Port sessions 993 IMAP4 For IMAP4 over SSL (IMAPS), use port 993.
IMAP4 User Experience Monitor 25 SMTP This component monitor uses these ports when used with a Microsoft Exchange mail server.
LDAP User Experience Monitor 389 The port used for LDAP connections.
LDAP User Experience Monitor 636 For LDAP over SSL, use port 636.
Linux/Unix Script Monitor Ports 22 This field allows you to specify the port number used for the SSH connection.
NNTP Monitor 119 UDP This field is the port number used for NNTP connections.
ODBC User Experience Monitor 1630 TCP This component monitor uses port TCP/1630.
Oracle User Experience Monitor 1521 TCP The Oracle SQL*Net Listener allows Oracle client connections to the database over Oracle's SQL*Net protocol. You can configure it during installation. To reconfigure this port, use Net Configuration Assistant.
Oracle User Experience Monitor 1526 TCP The Oracle SQL*Net Listener allows Oracle client connections to the database over Oracle's SQL*Net protocol. You can configure it during installation. To reconfigure this port, use Net Configuration Assistant.
Performance Counter Monitor See description TCP

This monitor uses RPC, requiring the following ports:

TCP/135

RPC/named pipes (NP) TCP 139

RPC/NP TCP 445

RPC/NP UDP 137

RPC/NP UDP 138

POP3 Monitor See Description

This component monitor uses the following ports when used with a Microsoft Exchange mail server.

  • 102 X.400 MTA
  • 110 POP3
  • 119 NNTP
  • 143 IMAP4
  • 389 LDAP
  • 563 POP3 over SSL
  • 636 LDAP over SSL
  • 993 IMAP4 over SSL
  • 995 Secure POP3 over SSL

POP3 Monitor

POP3 User Experience Monitor

110 (default) This field is the port number used for POP3 connections.

POP3 Monitor

POP3 User Experience Monitor

995 For Secure POP3 (SSL-POP) use port 995.
POP3 User Experience Monitor 110 (default) This field is the port number used for POP3 sessions. The default value is 110. For Secure POP3 (SSL-POP) use port 995. It also uses an SMTP Port, port 25 for SMTP sessions.
Process Monitor SNMP This component monitor uses SNMP communication.
Process Monitor WMI Uses WMI communication to test if the specified Windows process is running and uses RPC communication to test if the specified Windows process is running.
RADIUS User Experience Monitor

1812

1645

This field is the RADIUS protocol authentication port. The default value is 1812. Cisco devices may require port 1645. This field is the RADIUS protocol accounting port. The default value is 1813. Cisco devices may require port 1646.
RWHOIS Port Monitor 4321 This template tests the ability of an RWHOIS server to accept incoming sessions on port 4321.
SMTP Monitor 465 SSMTP For Secure SMTP (SSMTP), use port 465.
SQL Server User Experience Monitor 1433 This component monitor only works if Microsoft SQL Server is using the default port 1433. If you have a Microsoft SQL Server database that uses a non-standard port, you cannot monitor it using the SQL Server User Experience monitor. You need to use the ODBC User Experience monitor instead to manually define a connection string that will allow you to talk to Microsoft SQL Server on its custom port.
TACACS+User Experience Monitor 49 This field is the TACACS+ protocol connection port. The default value is 49.
Tomcat Server Monitor 8080 This field allows you to specify the port number used by the web site. The default value for this field is 8080.
VMware Performance Counter Monitor 443 Port number to use for VMware API. The default is 443.
ESX Hardware Monitoring 5989 Ensure port 5989 is open on the firewall.
Windows Event Log Monitor

This component monitor uses the following ports:

  • TCP/135
  • RPC/named pipes (NP) TCP 139
  • RPC/NP TCP 445
  • RPC/NP UDP 137
  • RPC/NP UDP 138
  • POP3 User Experience Monitor port 110

SAM template port requirements

Template port requirements will vary depending on how you utilize them. The following provides a list of monitor templates that use ports.

Template Port Description
Blackberry Delivery Confirmation template 25 Blackberry Delivery Confirmation template uses port 25 on the SMTP server for sending the test email. If the SMTP server uses a different port, change this value.
Java Application Server (SNMP) template 1161 This template is configured to send SNMP requests on port 1161.
SNPP Port Monitor 444 This template tests the ability of an SNMP server to accept incoming sessions on port 444.
Windows FTP Server (via WMI) 21 This template monitors the Windows FTP Publishing Service and tests the ability of the FTP server to accept incoming sessions on port 21.

SAM container service monitoring port requirements

To support container service monitoring, allow all outbound communication from orchestrator machines on the following ports:

  • 17799 (to the Orion Cortex API)
  • 17778 (to the SWIS API)

All other ports are used for internal communication by specific orchestrators, and should not be blocked by internal orchestrator firewall rules. You can change ports in configuration files manually, but SolarWinds does not recommend doing so.

Following are port-related details for supported container services:

  • Kubernetes
    • 17799 - Cortex (Orion Platform communication)
    • 17778 - SWIS
    • 30043 - Node Port (internal docker communication)
    • 4043 - Target Port / Container Port (internal docker communication)
  • Docker
    • 17799 - Cortex (Orion Platform communication)
    • 17778 - SWIS
    • 6784 - report/wave status (internal docker communication)
    • 4043 - container port (internal docker communication)
  • Docker Swarm 17.12+
    • 17799 - Cortex (Orion Platform communication)
    • 17778 - SWIS
    • 6784 - report/wave status (internal docker communication)
    • 4043 - container port (internal docker communication)
  • Apache Mesos
    • 17799 - Cortex (Orion Platform communication)
    • 17778 - SWIS
    • 4043 - Mesos master server port (internal Mesos communication)
    • 8080 - Deployment service (internal Mesos communication)

For a comprehensive list of port requirements for all products, see SolarWinds Port Requirements.


SAM WMI requirements

Return to top

Microsoft Windows by default uses a random port between 1024 and 65535 for WMI communications.

You must create firewall exceptions to allow bidirectional TCP/UDP traffic on ports 1024 - 65535 or the component monitors and templates that use WMI will not work.

The following component monitors use WMI:

  • Performance Counter Monitor
  • Process Monitor – WMI (if script uses WMI access)
  • Windows Event Log Monitor
  • Windows PowerShell Monitor (if script uses WMI access)
  • Windows Script Monitor
  • Windows Service Monitor (if script uses WMI access)

The following templates use WMI:

  • Active Directory
  • Active Directory 2016 Domain Controller Security
  • Active Directory 2016 Services and Counters
  • Blackberry Enterprise Server
  • Citrix XenApp 5.0 Core WMI Counters
  • Citrix XenApp 5.0 ICA Session WMI Counters
  • Citrix XenApp 5.0 Presentation Server WMI Counters
  • Citrix XenApp 5.0 Services
  • Errors in Application Event Log
  • Exchange 2007
  • Exchange 2007—2010 Client Access Role Services
  • Exchange 2007—2010 Client Access Role WMI Counters
  • Exchange 2007—2010 Common WMI Counters
  • Exchange 2007—2010 Edge Transport Role Services
  • Exchange 2007—2010 Hub Transport Role Services
  • Exchange 2007—2010 Hub Transport Role WMI Counters
  • Exchange 2007—2010 Mailbox Role Services
  • Exchange 2007—2010 Mailbox Role WMI Counters
  • Exchange 2007—2010 Unified Messaging Role Services
  • Exchange 2007—2010 WMI Counters
  • Exchange 2013 Client Access Role Services
  • Exchange 2013 Client Access Role WMI Counters
  • Exchange 2016 Client Access Role Services
  • Exchange 2016 Hub Transport Role Counters
  • Exchange 2016 Hub Transport Role Servers and Counters
  • Exchange 2010 Common Performance Counters
  • Exchange Server 2000 and 2003
  • Internet Information Services
  • Orion Server
  • SharePoint Server (MOSS) 2007
  • SharePoint Services (WSS) 3.0
  • SQL Server 2005 Database
  • SQL Server 2008 Database
  • Windows Print Services
  • Windows Server 2003-2008

Additional SAM technology requirements

Return to top

Refer to these Success Center articles for additional SAM requirements:

Additional resources

Return to top

For additional information about Orion Platform requirements and configurations, refer to:


Legal notices

Return to top

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