SAM 6.4 System Requirements

Released: March 7, 2017

Updated: January 25, 2018

These system requirements define the minimum requirements for SAM 6.4 as a single installed product. You may need to increase your requirements in small, medium, or large environments with multi-modules installed.

For additional information on requirements and configurations, see the SAM 6.4 Release Notes.

Hardware requirements

Important: These system requirements define the minimum requirements for SAM 6.4 as a single installed product. You may need to increase your requirements in small, medium, or large environments with multi-modules installed.

The following table lists minimum hardware requirements and recommendations for your SolarWinds Orion server. Installing multiple SolarWinds Orion products on the same computer may change the requirements.

Hardware requirements are listed by SolarWinds SAM license level.

Feature AL150 - AL300 AL700 — AL1100 AL1500 — ALX
CPU Quad core, 2.5 GHz or better Quad core, 2.5 GHz or better Quad core, 3.0 GHz or better

To poll vCenter 6.5 virtual servers, SAM 6.4 requires 3.0 GHz or better CPU and Virtual Infrastructure Monitor (VIM) 7.1 or higher (included with SAM). See VMAN documentation for details. VIM is included in SAM 6.6 and Virtualization Manager (VMAN) 8.0 or later.

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

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

4 GB minimum

8 GB recommended

8 GB minimum

16 GB recommended

16 GB minimum

32 GB recommended

Software requirements

  • SolarWinds does not support installing SolarWinds Orion on domain controllers.
  • SolarWinds neither recommends nor supports the installation of any Orion product on the same server or using the same database server as a Research in Motion (RIM) Blackberry server.

Important End of Support

Microsoft Windows Server: Support for Windows Server 2008 R2 is deprecated as of this release. Future releases will no longer support installing on Windows Server 2008 R2, though you can continue to monitor computers running Windows Server 2008 R2. SolarWinds recommends that you upgrade to Windows Server 2012, 2012 R2, or 2016 at your earliest convenience.

Software Requirements
Operating System Production
  • Windows Server 2008 R2 SP1 with IIS in 32-bit mode.
  • Windows Server 2012, 2012 R2. IIS must be installed.
  • Windows Server 2016

SolarWinds recommends that SolarWinds administrators have local administrator privileges to ensure full functionality of local SolarWinds tools. Accounts limited to use of the SolarWinds Web Console do not require administrator privileges.

Installing SAM on Windows Server 2012 R2 Essentials e is not supported.

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

IPv4

IPv6 implemented as a dual stack. For more information, see RFC 4213 - Basic Transition Mechanisms for IPv6 Hosts and Routers.

CIDR notation is not supported for IPv6 addresses.

Web server

Microsoft Internet Information Services (IIS), version 7.5 or later, in 32‑bit mode

  • DNS specifications require that host names be composed of alphanumeric characters (A-Z, 0-9), the minus sign (-), and periods (.). Underscore characters (_) are not allowed. For more information, see RFC 952 - DOD Internet Host Table Specification.
  • IIS is installed by the SolarWinds installer. You can install this software manually to reduce your installation time or network bandwidth.
  • SolarWinds products are not compatible with IIS version 6.0 installations that use web gardens.
Microsoft .NET Framework

.NET 4.5

Compatible with 4.6.1

SolarWinds recommends using .NET 4.5.2.

Be sure that you are running the same version of .NET on your primary server and any additional polling engines or web servers in the environment.

Services

The following services must be running after installation is complete to collect syslog messages and traps:

  • SolarWinds Syslog Service
  • SolarWinds Trap Service
Orion Web Console browser
  • Microsoft Internet Explorer version 11 or later with Active scripting
  • Microsoft Edge Firefox 46.0 or later (Toolset Integration is not supported on Firefox)
  • Chrome 51.0 or later
  • Safari for iPhone
Other MSMQ
User privileges SolarWinds recommends that administrators have local administrator privileges to ensure full functionality of local SolarWinds tools. Accounts limited to the web console do not require administrator privileges.

Orion SQL database requirements

Your SolarWinds Orion Plaform product and your SolarWinds Orion database should use separate servers.

Multiple SolarWinds Orion server installations using the same database are not supported.

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

Important End of Support

Microsoft SQL Server: Support for SQL 2008 and 2008 R2 is deprecated as of this release. Future releases will no longer support using SQL 2008 or 2008 R2 as your database server. SolarWinds recommends that you upgrade directly to SQL 2016 at your earliest convenience.

Requirements AL150 - AL300 AL700 — AL1100 AL1500 — ALX
SQL Server

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

  • SQL Server 2008, 2008 SP1, 2008 SP2, 2008 SP3, or 2008 SP4
  • SQL Server 2008 R2, 2008 R2 SP1, 2008 R2 SP2, or 2008 R2 SP3
  • SQL Server 2012, 2012 SP1, 2012 SP2, or 2012 SP3
  • SQL Server 2014 or 2014 SP1
  • SQL Server 2016
  • Due to latency effects, SolarWinds does not recommend installing your SQL Server and your SolarWinds server or additional polling engine in different locations across a WAN. For more information, see SQL Server Configuration Best Practices.

  • Either mixed-mode or SQL authentication must be supported.

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

  • You can set the database recovery model to Full recovery mode only if you use Always On Availability. We strongly recommend Simple recovery mode due to ensure best performance.
CPU Quad core processor, 2.5 GHz or better Quad core processor, 2.5 GHz or better Dual quad core processor, 3.0 GHz 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

4 GB minimum

8 GB recommended

8 GB minimum

16 GB recommended

16 GB minimum

32 GB recommended

Additional memory improves both performance and reliability.
Memory and Additional Pollers Each additional poller requires 16 GB of additional RAM. For example, SAM plus 2 additional pollers would require 32GB of RAM. 3 additional pollers would require 48GB of RAM, and so on.
Authentication Either mixed-mode or SQL authentication
Other software

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

The Installation Wizard installs the following required x86 components if they are not found on your 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

SAM's PowerShell Script Monitor works with PowerShell 1.0 and higher for local execution.

PowerShell 2.0 or higher is required for remote execution.

Port requirements

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 server. These ports include feature specific requirements including Orion agents, High Availability, and component monitors and templates.

Ports 4369, 25672, and 5672 are opened by default. These ports can be blocked by the firewall.

Port Protocol Direction Encryption Description
25 TCP SMTP port for non-encrypted messages
161 UDP

Bidirectional

Statistics collection
162 UDP Inbound Trap Server listening for incoming messages
443 TCP Bidirectional Default port for https binding and bi-directional ESX/ESXi server polling and for Cisco UCS monitoring.
465 TCP Outbound SSL SSL-enabled email alert actions
587 TCP Outbound TLS TLS-enabled email alert actions
1801 TCP WCF MSMQ WCF binding
4369 Bidirectional Required for RabbitMQ messaging (epmd)
5671 TCP Bidirectional TLS SSL encrypted RabbitMQ messaging from the additional polling engines to the main polling engine
5672 Non-encrypted RabbitMQ messaging between the primary and additional polling engines. This is a backup communication port that is not used by default.
25672 Bidirectional Required for RabbitMQ messaging (Erlang distribution)
17777 TCP Bidirectional RSA handshake, AES 256 communication using WCF

Orion module traffic. Open the port to enable communication from your poller to the Orion Web Console, and from the Orion Web Console to your poller.

High Availability Service. Used for communication between the main server and pool members.

Job Engine V2, Collector Service, Business Layer, and Information Service v2,23. Used for communication between the services.

The port used for communication between the Orion Web Console and the poller.

17778 HTTPS SSL

Required to access the SolarWinds Information Service API and agent communication

SolarWinds Information Service API

17779 HTTP and HTTPS SolarWinds Toolset Integration over HTTP

Agents

The following ports are used by the SolarWinds Orion agent.

Port Type Direction Encryption Description
22 TCP Bidirectional Used to install the agent on Linux computers through SSH and SFTP or SCP. Open this port for outbound connections on the Orion server or additional polling engings and inbound connections on the monitored computer.
135 TCP

(DCE/RPC Locator service) Microsoft EPMAP. This port must be open on the client computer for remote deployment.

Active directory, RPC and SMB protocol ports are used by Orion Poller Agent installer to connect to Windows OS and to deploy Windows Agent.

445 TCP

Microsoft-DS SMB file sharing. This port must be open on the client computer (inbound) for remote deployment.

Active directory, RPC and SMB protocol ports are used by Orion Poller Agent installer to connect to Windows OS and to deploy Windows Agent.

17778 TCP Bidirectional SSL, TLS 1.0 or later Send and receive information from Windows and Linux devices polled by agents using agent-initiated communication. Used to deploy agents.
17790 TCP Bidirectional SHA1 certificate, TLS 1.0 or later Used by the agent to communicate with the Orion server when the agent is in server-initiated communication mode.
17791 TCP Bidirectional Used by the agent to communicate with the Orion server when the agent is in agent-initiated communication mode. This port must be opened if the reomte computers you monitor run Windows 2008 R2.

High Availability

The following ports are used in addition to ports used by your primary products when you enable High Availability.

Port Type Description
4369 TCP Open on the main Orion server and its standby server for RabbitMQ clustering. This port exchanges EPMD and Erlang distribution protocol messages for RabbbitMQ. This port is not required when protecting additional polling engines.
5671 TCP For encrypted RabbitMQ messaging (AMQP/TLS) into the main polling engine on the Orion server.
25672 TCP Open on the main Orion server and its standby server for RabbitMQ clustering. This port exchanges EPMD and Erlang distribution protocol messages for RabbbitMQ. This port is not required when protecting additional polling engines.

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.
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
IMAP4 Monitor 143 and 993 IMAP4 This component monitor uses these ports when used with a Microsoft Exchange mail server.
IMAP4 User Experience Monitor 25 SMTP 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.
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

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 SMTP Monitor 25 SMTP This component uses port 25 for SMTP sessions.
SMTP Monitor 465 SSMTP For Secure SMTP (SSMTP), use port 465.
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 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.
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.
Finger Port Monitor 79 This template tests the ability of the Finger service to accept incoming sessions on port 79.
Gopher Port Monitor 70 This template tests the ability of a Gopher server to accept incoming sessions on port 70.
IRC Port Monitor 6667 This template tests the ability of an IRC server to accept incoming sessions on port 6667.
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 SNPP 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 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

Refer to these Success Center articles for additional SAM requirements:

Additional resources

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.