WPM 2.2.2 system requirements
Released: May 24, 2018
Updated: October 22, 2018
Supports: WPM 2.2.2
These recommended system requirements are for SolarWinds Web Performance Monitor (WPM) 2.2.3 as a single product installed on Orion Platform 2018.4.
Requirements may increase for medium or large environments, or environments with multi-modules installed; see Orion Scalability Guidelines for WPM and Multi-module system guidelines. You should also review the WPM 2.2.2 Release Notes for the exact product requirements beyond these minimums.
You can install standalone versions of the WPM Recorder and WPM Player on remote machines, as described in the WPM Administrator Guide. For example, install a WPM Player in a satellite office in the same geographical location as a large group of end users to get more accurate samplings of website performance. Requirements for those machines vary from the primary WPM requirements. See WPM Recorder and Player system requirements.
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.
The following table lists software requirements and recommendations for a SolarWinds installation on both physical and virtual computers.
| Software | Requirements | |
|---|---|---|
| Operating system | Production | Evaluation environments only |
|
Windows Server 2012 Windows Server 2012 R2 Windows Server 2016 Deprecation notice: Although you can install Orion Platform 2018.2 products on Windows Server 2012 and 2012 R2, mainstream support for thes versions is ending and they will not be supported on future Orion Platfor versions. SolarWinds strongly recommends that you upgrade to Microsoft Windows Server 2016 or later at your earliest convenience. |
Windows 8.1, 64-bit (not Standard Edition) Windows 10 All production operating systems |
|
| Installing WPM on Windows Server 2012 R2 Essentials or Windows Server Core is not supported. Desktop operating systems, such as Windows 8.1, 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 |
|
|
| IP address version |
CIDR notation is not supported for IPv6 addresses. |
|
| Web server |
Microsoft IIS 8.0 or later Use default settings for Anonymous Authentication of the SolarWinds NetPerfMon website (Enabled). IIS is installed by the SolarWinds Orion Installer. You can install this software manually to reduce 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. |
|
| Orion Web Console browser |
Do not enable Enterprise Mode on Internet Explorer. This setting forces Internet Explorer to emulate version 7, which is not supported. |
|
| Other |
|
|
| Services |
The following services must be running after installation is complete to collect syslog messages and traps:
|
|
| Orion Web Console screen resolution | 1024 x 768 | |
Account privileges
SolarWinds recommends that SolarWinds Orion administrators have local administrator privileges on the Orion server to ensure full functionality of local SolarWinds tools. SolarWinds Orion user accounts limited to the Orion Web Console do not require local administrator privileges.
To use domain accounts with WPM, each account should have local admin privileges and be able to log into the Orion Web Console locally.
Server port requirements
Ports 4369, 25672, and 5672 are opened by default on the main 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.
| Port | Protocol | Description | Encrytpion 12 |
|---|---|---|---|
|
22 |
SSH |
Port for accessing ASA devices through CLI Direction: Bidirectional Service/Process: SolarWinds Job Engine v2 and IIS |
Device-based |
| 25 | TCP |
SMTP port for non-encrypted messages Direction: Outbound Service/Process: SolarWinds Alerting Service V2 |
N/A |
| 53 | UDP |
Resolving DNS queries Direction: Outbound Service/Process: SolarWinds Alerting Service V2 |
N/A |
| 80 | TCP |
Default Additional Web Server (AWS) port. If you specify any port other than 80, you must include that port in the URL used to access the Orion Web Console. For example, if you specify 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. Direction: Inbound Service/Process: IIS
|
N/A |
| 135 | TCP | Microsoft EPMAP (DCE/RPC Locator service) | N/A |
| 161 | UDP |
Sending and receiving SNMP information. Direction: Outbound Service/Process: SolarWinds Job Engine v2 |
SNMP v1 and v2 are unencrypted SNMP v3 uses AES & 3DES encryption. |
| 162 | UDP |
Receiving trap messages Direction: Inbound Service/Process: SolarWinds Trap Service |
N/A |
| 443 | TCP |
Default port for https binding. Also used for bi-directional ESX/ESXi server polling, or for Cisco UCS monitoring. Direction: Inbound Service/Process: IIS |
SSL |
| 465 | TCP |
SMTP port used to send TLS-enabled email alert actions. Direction: Outbound Service/Process: SolarWinds Alerting Service V2 |
SSL |
| 514 | UDP |
Receiving syslog messages Direction: Inbound Service/Process: SolarWinds Syslog Service |
N/A |
| 587 | TCP |
SMTP port used to send TLS-enabled email alert actions. Direction: Outbound Service/Process: SolarWinds Alerting Service V2 |
TLS |
| 1433 | TCP |
Used for communication between the Orion Server and the SQL Server. Open the port from the Orion Web Console to the SQL Server. Direction: Outbound Service/Process:
|
N/A |
| 1434 | UDP |
Used for communication with the SQL Server Browser Service to determine how to communicate with certain non-standard SQL Server installations. Direction: Outbound Service/Process:
|
N/A |
| 1801 | TCP |
MSMQ WCF binding Direction: Bidirectional Service/Process: MSMQ |
WCF |
| 5671 | TCP |
For encrypted RabbitMQ messaging (AMQP/TLS) into the main polling engine from all Orion servers. Direction: Bidirectional Service/Process: RabbitMQ |
TLS 1.2 |
| 17777 | TCP |
Used for Orion module traffic, communication between services, and communication between the main server and pool members. Open the port to enable bi-directional communication between the Orion Web Console and the main polling engine. Direction: Bidirectional Service/Process:
|
RSA handshake, AES 25 communication using WCF |
| 17778 | HTTPS |
Required for access to the SWIS API and agent communication Direction: Inbound to the Orion server Service/Process: SolarWinds Agent |
SSL |
| 17781 | TCP |
The default port the WPM Player listens on. This port must be open between the Orion Server and the WPM player for proper communications. Direction: Bidirectional Service/Process: WPM Player |
N/A |
| 17782 | TCP |
Used for player-initiated communications mode Direction: Inbound Service/Process: WPM Player |
N/A |
Orion agent port requirements
The following ports are used by the SolarWinds Orion agent.
| Port | Protocol | Description | Encrytpion |
|---|---|---|---|
|
22 |
SSH |
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. Direction: Bidirectional |
N/A |
| 135 | TCP |
To support Microsoft EPMAP (DCE/RPC Locator service), open this port on the client computer for remote deployment. The Orion Poller Agent installer uses Active Directory, RPC, and SMB protocol port to connect to the Windows OS. Direction: Inbound |
N/A |
| 445 | TCP |
To support Microsoft-DS SMB file sharing, open this port on the client computer (inbound) for remote deployment. The Orion Poller Agent installer uses Active Directory, RPC, and SMB protocol ports to connect to the Windows OS. Direction: Inbound |
N/A |
| 17778 | TCP |
Send and receive information from Windows and Linux devices polled by agents using agent-initiated communication. Used to deploy agents. This requirement is for Active agents only. If Passive agents are used, no ports need to be opened on the firewall for the Orion server. Direction: Bidirectional |
SSL TLS 1.0 or later |
| 17790 | TCP |
Used by the agent to communicate with the Orion server when the agent is in server-initiated communication mode. In Passive mode, port 17790 must be opened on the host where the agent is installed and allowed by the firewall. Direction: Bidirectional |
SHA1 certificate TLS 1.0 or later |
| 17791 | TCP |
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 monitored remote computers run Windows Server 2008 R2. Direction: Bidirectional |
N/A |
Hardware requirements
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. These requirements apply to small (SL100, SL250, and SL500), Medium (SL2000), and XL (up to 400,000 monitored events) deployments.
SolarWinds strongly suggests using the recommended hardware configuration to avoid potential performance issues caused by heavy loads or custom configurations such as increased data retention or frequent polling intervals.
Installing multiple SolarWinds Orion Platform products on the same computer may change the requirements.
Hardware requirements are listed by deployment size, based on SolarWinds Network Performance Monitor (NPM) license level. CPU recommendations for XL deployments use the PassMark Score. For details, see Pass Mark Performance Test (Copyright © 2018 PassMark® Software, obtained at https://www.cpubenchmark.net/high_end_cpus.html on April 9, 2018).
CPU
Do not enable Physical Address Extension (PAE).
|
Small |
Medium |
Large |
XL |
|---|---|---|---|
| Quad core processor or better | Quad core processor or better | Quad core processor or better | 8-core processor or better |
Hard drive space
|
Small |
Medium |
Large |
XL |
|---|---|---|---|
|
10 GB minimum 20 GB recommended |
15 GB minimum 40 GB recommended |
30 GB minimum 40 GB recommended |
32 GB minimum |
| Two 146 GB 15K (RAID 1/Mirrored Settings) hard drives are recommended with a dedicated drive for the server operating system and SolarWinds installation. | |||
| During upgrades, the installer needs 2 GB of free space. | |||
| 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 temporary directories. | |||
Memory
|
Small |
Medium |
Large |
XL |
|---|---|---|---|
|
6 GB minimum 8 GB recommended |
8 GB minimum 16 GB recommended |
16 GB minimum 32 GB recommended |
32 GB minimum |
Database server requirements
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.
The following table lists software and hardware requirements for your Orion database server using NPM license levels. These requirements apply to small (SL100, SL250, and SL500), Medium (SL2000), and XL (up to 400,000 monitored events) deployments.
CPU
|
Small |
Medium |
Large |
XL |
|---|---|---|---|
|
Quad core processor or better |
Dual quad core processor or better |
Dual quad core processor or better |
4 CPUs/60 cores |
Hard drive space
|
Small |
Medium |
Large |
XL |
|---|---|---|---|
|
20 GB minimum 40 GB recommended |
50 GB minimum 100 GB recommended |
100 GB minimum 400 GB recommended SolarWinds recommends the following configuration:
|
190,000 IOPs or better 1 Gbit dedicated NIC |
|
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 operating system 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 (listed by NPM license levels)
|
Small |
Medium |
Large |
XL |
|---|---|---|---|
|
SL100 4 GB minimum 8 GB recommended |
16 GB minimum 64 GB recommended |
64 GB minimum 128 GB recommended |
256 GB minimum |
|
SL250 & SL500 8 GB minimum 16 GB recommended |
Microsoft SQL Server
|
Small |
Medium |
Large |
XL |
|---|---|---|---|
|
Express, Standard, or Enterprise versions of the following:
Deprecation notice: Although you can use SQL Server 2012 with Orion Platform 2018.2 products, this version is deprecated and will not be supported on future versions of the Orion Platform. SolarWinds strongly recommends that you upgrade to Microsoft SQL Server 2016, 2017, or later at your earliest convenience. When you set up your database server, do the following:
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. Back up your database regularly to ensure that the volume where you store your transaction log has free space that is at least equal to or greater than the size of your Orion database. Transaction logs will continue to grow indefinitely until a database backup is performed and transactions are committed to the database. We recommend daily database backups when you use the Full Recovery model. |
|||
SQL Server collation
|
Small |
Medium |
Large |
XL |
|---|---|---|---|
The Orion Platform supports a case-insensitive database on a case-sensitive SQL Server. The Orion Platform does not support case-sensitive databases. |
|||
Other software
|
Small |
Medium |
Large |
XL |
|---|---|---|---|
|
If you are managing your 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 the Orion database server:
|
|||
Amazon Web Services (AWS) deployments
To deploy your Orion Platform using Amazon Web Services, consider the following requirements, listed according to NPM license levels. These requirements apply to small (SL100, SL250, and SL500), Medium (SL2000), and XL (up to 400,000 monitored events) deployments.
Orion server
|
Small |
Medium |
Large |
XL |
|---|---|---|---|
|
m4.large 2 CPUs 8 GB RAM 150 GB (default is 50 GB for m4.large) |
m4.xlarge 2 CPUs 16 GB RAM 150 GB (default is 50 GB for m4.large) |
m4.2xlarge 2 CPUs 16 GB RAM 150 GB (default is 50 GB for m4.large) |
CPU: 16 CPU 32 GB RAM 50 GiB General Purpose SSD (GP2) 100/3,000 IOPS |
Orion database server
|
Small |
Medium |
Large |
XL |
|---|---|---|---|
|
r3.xlarge 4 CPUs 16GB RAM SSD 80GB (included in r3.xlarge) + EBS Volume 500GB |
r3.xlarge 4 CPUs 30.5GB RAM SSD 80GB (included in r3.xlarge) + EBS Volume 500GB |
r3.2xlarge 4 CPUs 30.5GB RAM SSD 80GB (included in r3.xlarge) + EBS Volume 500GB |
32 CPU 244 GB RAM 1,500 GiB Provisioned IOPS (SSD) 20,000 IOPS |
Additional Polling Engines (APEs)
|
Small |
Medium |
Large |
XL |
|---|---|---|---|
|
APEs are required to monitor over 12,000 elements. |
4 CPU 16 GB RAM 50 GiB General Purpose SSD (GP2) 100/3000 IOPS |
||
WPM Recorder system requirements
The WPM Recorder is a Windows application that you can install on any computer that meets the following recommended system requirements. These requirements apply to small (SL100, SL250, and SL500), Medium (SL2000), and XL (up to 400,000 monitored events) deployments.
| Resource | Requirement |
|---|---|
| CPU | 1 GHz or better |
| Memory | 2 GB |
| Operating system |
Windows Vista Windows 7 Windows 8 Windows Server 2003 Windows Server 2008 Windows Server 2012 Windows Server 2016 |
| TCP/IP ports |
80 (TCP) open for http traffic 443 (TCP) open for https traffic 17777 (TCP) open for SolarWinds traffic |
| Web browser |
Internet Explorer (IE) 11 If your organization requires an earlier IE version, use IE 11's document modes to emulate earlier versions. |
WM Player system requirements
The WPM Player is a Windows service that you can install on any computer that meets the following system requirements. To learn about managing loads on servers that host WPM Players, see Scalability Engine Guidelines for SolarWinds Orion Products for WPM or Player Load Percentage widget.
| Resource | Requirement |
|---|---|
| CPU | Quad core processor or better |
| Memory | 3 GB |
| Operating system |
Windows Vista Windows 7 Windows 8 Windows Server 2003 Windows Server 2008 Windows Server 2012 Windows Server 2016 |
| TCP/IP ports |
80 (TCP) open for http traffic 443 (TCP) open for https traffic 17777 (TCP) open for SolarWinds traffic 17781 (TCP) open for server-initiated (passive) communication mode 17782 (TCP) open for server-initiated (active) communication mode 17783 (TCP) open for WPM Player automatic updates |
| Web browser |
Internet Explorer (IE) 11 If your organization requires an earlier IE version, use IE 11's document modes to emulate earlier versions. |
Other requirements
For additional information about Orion Platform requirements and configurations, see: