WPM 2.2.3 system requirements

Released: December 4, 2018

Updated February 28, 2019

Supports: WPM 2.2.3

These recommended system requirements are for SolarWinds Web Performance Monitor (WPM) 2.2.3 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 WPM 2.2.3 Release Notes.

You can install standalone versions of the WPM Recorder and Player on separate 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. 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
  • 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 SolarWinds NetPerfMon website. 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 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
  • Microsoft Internet Explorer 11 or later with Active scripting
  • Microsoft Edge
  • Mozilla Firefox 62.0 or later
  • Google Chrome 69.0 or later

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

Other
  • RabbitMQ (primary messaging service between the primary and additional polling engines)
  • MSMQ (fall back and legacy messaging)
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 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.

WPM port requirements

Review and open ports for WPM to support communication for the Orion server, the main polling engine, Additional Polling Engines (APEs), and Additional Web Servers (AWS). These ports include feature specific requirements including Orion agents and SolarWinds High Availability (HA).

Ports 4369, 25672, and 5672 are opened by default on the main server for RabbitMQ messaging. These ports can be blocked by the firewall. If using High Availability, make sure port 4369 is open.

The Job Engine v2 process uses RPC ports > 1024 (TCP, bidirectional) to communicate with network devices.

If your devices do not use the default syslog port to send messages, you must also modify the Orion server to listen to that port.

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:

  • SolarWinds Alerting Service V2
  • SolarWinds Administration Service
  • SolarWinds Information Service
  • SolarWinds Information Service V3
  • SolarWinds Orion Module Engine
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:

  • SolarWinds Alerting Service V2
  • SolarWinds Administration Service
  • SolarWinds Information Service
  • SolarWinds Information Service V3
  • SolarWinds Orion Module Engine
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:

  • SolarWinds Orion Module Engine
  • SolarWinds Information Service
  • SolarWinds Information Service V3
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

WPM Recorder port requirements

The WPM Recorder is a Windows application you can install on a computer to capture web browser steps as you perform them to simulate the typical steps taken by end users, including mouse clicks, text input, and file downloads.

In addition to WPM Recorder system requirements, note these TCP/IP port requirements:

  • 80, open for http traffic
  • 443, open for https traffic
  • 17777, open for SolarWinds traffic

WPM Player port requirements

The WPM Player is a Windows service you can install on remote computers to simulate end user experiences with web applications by playing back recorded transactions.

In addition to WPM Player system requirements, note these TCP/IP port requirements:

  • 80, open for http traffic
  • 443, open for https traffic
  • 17777, open for SolarWinds traffic
  • 17777, open for SolarWinds traffic
  • 17781, open for server-initiated (passive) communication mode
  • 17782, open for server-initiated (active) communication mode
  • 17783, open for WPM Player automatic updates

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 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:

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

Deprecation notice: Starting with Orion Platform 2018.4, SQL Server 2012, 2012 SP1, 2012 SP2, 2012 SP3, and 2012 SP4 are not supported anymore.

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)

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

When you set up your database server, do the following:

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

Small

Medium

Large

XL

  • English with collation setting SQL_Latin1_General_CP1_CI_AS
  • English with collation setting SQL_Latin1_General_CP1_CS_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

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:

  • 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

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 Platform 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

Memory: 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

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

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: