Documentation forWeb Performance Monitor

WPM 3.0 system requirements

Release Date: June 6, 2019

Updated August 30, 2019

These recommended system requirements are for SolarWinds Web Performance Monitor (WPM) 3.0 as a single product installed on Orion Platform 2019.2.

Note the following details about these system requirements:

  • WPM requirements may vary, depending on the websites being monitored and the number of transactions assigned to WPM Players. Some Single-Page Applications (SPAs) may consume many system resources.
  • WPM Recorders and a WPM Player are added to the Orion server during installation, but you can deploy standalone versions of those tools to remote systems situated near a large group of end users to get more accurate samplings of website performance. See WPM Recorder requirements and WPM Player requirements.
  • 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 3.0 Release Notes and the Orion Platform 2019.2 Release Notes.

Software requirements for the Orion server

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

Software Requirements
Operating system
  • Windows Server 2016
  • Windows Server 2019

Desktop operating systems, such as Windows 10, 64-bit Pro or Enterprise 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.

Support differences between Orion Agents and Orion Platform products

  • You cannot install Orion Platform products 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 Microsoft SharePoint, Microsoft Exchange or Research in Motion (RIM) Blackberry server.

End-of-support notice: Orion Platform 2019.2 products are no longer compatible with Windows Server 2012 and 2012 R2. To use the new features introduced in Orion Platform 2018.4 or later, upgrade your environment at your earliest convenience.

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.8 or later

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 WPM. See this article for details.

Services

If using the Syslog or SNMP Traps feature of the Orion Platform, make sure the following services are running after installation is complete:

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

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

  • Firefox
  • Chrome

The following browsers are also supported:

  • Microsoft Edge
  • Microsoft Internet Explorer 11 or later with Active scripting

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

Allow access to required files

To allow the Orion Platform to access required files for a WPM Player, exclude these files from anti-virus protection:

  • C:\ProgramData\SolarWinds\SEUM
  • Volume:\Program Files (x86)\SolarWinds\
  • C:\Windows\Temp\SWSEUMPlayerUpdate

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.

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

Return to top

  • Ports 4369, 25672, and 5672 are open by default on the main server for RabbitMQ messaging. These ports can be blocked by the firewall. When running High Availability, ensure ports 4369 and 25672 are open.
  • RPC ports > 1024 (TCP, bidirectional) are used by the Job Engine v2 process to communicate with Windows nodes.

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

Access Cisco Adaptive Security Appliance (ASA) devices through the Command-Line Interface (CLI).

Device-based
25 TCP SolarWinds Alerting Service V2 Outbound

SMTP port for non-encrypted messages

N/A
53 UDP SolarWinds Job Engine V2 Bidirectional

Resolve DNS queries

N/A
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 Orion Web Console. For example, if you specify 192.168.0.3 and port 8080, the URL used 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.

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

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

N/A
161 UDP SolarWinds Job Engine v2, SolarWinds Cortex (communication) Bidirectional

Send and receive SNMP information.

SNMP v1 and v2 are unencrypted.

SNMP v3 uses AES and 3DES encryption.

162 UDP

SolarWinds Trap Service

SNMP Informs

Bidirectional

Receive trap messages

N/A
443 TCP IIS Inbound

Default port for https binding. Also used for bi-directional ESX/ESXi server polling.

SSL
465 TCP SolarWinds Alerting Service V2 Outbound

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

SSL
514 UDP SolarWinds Syslog Service Inbound

Receive syslog messages

N/A
587 TCP SolarWinds Alerting Service V2 Outbound

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

TLS
1433 TCP

SolarWinds Alerting Service V2

SolarWinds Administration Service

SolarWinds Information Service

SolarWinds Information Service V3

SolarWinds Orion Module Engine

Outbound

Used for communication from the Orion Server to the Orion database server.

N/A
1434 UDP

SolarWinds Alerting Service V2

SolarWinds Administration Service

SolarWinds Information Service

SolarWinds Information Service V3

SolarWinds Orion Module Engine

SQL Server Browse Service

Outbound

Communication with the SQL Server Browser Service to determine how to handle certain non-standard SQL Server installations. Required only if your Orion database server is configured to use dynamic ports.

N/A
1801 TCP MSMQ Bidirectional

MSMQ WCF binding

WCF
5671 TCP RabbitMQ Bidirectional

For encrypted RabbitMQ messaging (AMQP/TLS) into the main polling engine from all scalability engines.

TLS 1.2
17777 TCP

SolarWinds Orion Module Engine

SolarWinds Information Service

SolarWinds Information Service V3

SolarWinds Cortex (communication)

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.

Direction: Bidirectional

Service/Process:

  • SolarWinds Orion Module Engine
  • SolarWinds Information Service
  • SolarWinds Information Service V3
  • SolarWinds Cortex (communication)

RSA handshake, AES 256 communication using WCF

TLS 1.2 with Cortex

17778 HTTPS SolarWinds Agent Bidirectional

Required for access to the SWIS API and agent communication

SSL
17781 TCP WPM Player Bidirectional

The default port the WPM Player listens on. This port must be open between the Orion Server and the WPM Player for proper communications.

N/A
17782 TCP WPM Playback Player Inbound

Used for WPM Player-initiated communications mode

Direction: Inbound

Service/Process: WPM Playback Player

N/A
17783 TCP WPM Playback Player Bidirectional

Used for automatic WPM Player updates

N/A

See also:

Hardware requirements for the Orion server

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.

  • Do not install Orion Platform products on the same server as SolarWinds Access Rights Manager (ARM).
  • 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 SolarWinds NPM license levels. CPU recommendations for XL deployments use the PassMark Score. For details, see PassMark Performance Test (Copyright © 2019 PassMark® Software, obtained at https://www.cpubenchmark.net/high_end_cpus.html on April 24, 2019).

Feature

Small

SL100, SL250, SL500

Medium

SL2000

Large

SLX

XL

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

50 GB recommended

Read/Write I/O performance of 800 IOPS

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

16 GB minimum

32 GB recommended

Orion database server requirements

Return to top

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

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

  • 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.
  • As of Orion Platform 2019.2, you can use Azure SQL or Amazon RDS as your database server. See the Orion Platform 2019.2 release notes for details.
Feature

Small

SL100, SL250, SL500

Medium

SL2000

Large

SLX

XL

SQL Server

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, very small environments, and EOC.

Enterprise versions of supported SQL Servers:

  • 2014
  • 2014 SP1
  • 2014 SP2
  • 2016
  • 2016 SP1
  • 2016 SP2
  • 2017 (including installations on Linux)

End-of-support notice: Products running Orion Platform 2018.4 and later are not compatible with Windows Server 2012 and 2012 R2. To use new features introduced in Orion Platform 2018.4 or later, upgrade your environment at your earliest convenience.

Recommendations

  • Use 64-bit version of SQL Server.
  • Use the Simple database recovery model to ensure best performance.
  • You can use the Full database recovery model 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 the volume where you store transactions log has free space at least equal to or greater than the size of the Orion database. Transaction logs will continue to grow indefinitely until a database backup is performed and transactions are committed to the database. SolarWinds recommends daily database backups if using the Full database recovery model.
SQL Server collation
  • 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

SolarWinds products support a CI database on an 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*

500 GB minimum

1TB recommended

Read/Write I/O performance of 30,000 IOPs

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 SolarWinds database, data, and log files with a dedicated drive for the server operating system and tempdb files.
  • Other RAID configurations can negatively affect your SQL Server's 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. For details, see Working with Temporary Directories.

Memory

8 GB minimum

16 GB recommended

16 GB minimum

64 GB recommended

64 GB minimum

128 GB recommended

256 GB minimum

512 GB recommended

Authentication

Either mixed-mode or Windows authentication. If you require SQL authentication, you must enable mixed mode on your SQL server.

Other software

SolarWinds recommends installing Microsoft SQL Server Management Studio on your Orion database server. The Orion Installer adds the following x86 components if they are not found on your 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 overall performance.
  • Microsoft SQL Server Native Client
  • Microsoft SQL Server Management Objects

You cannot share the SolarWinds Orion database with Microsoft SharePoint, Microsoft Exchange, or Research in Motion (RIM) BlackBerry servers.

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

  • 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

Amazon Web Services (AWS) deployments

To deploy your Orion Platform product using AWS, consider using the following templates, listed according to NPM license levels.

Require-
ments

Small

SL100, SL250, SL500

Medium

SL2000

Large

SLX

XL (up to 400,000 elements)

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

SolarWinds 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 (APES) Only relevant for environments that monitor over 12,000 elements.

m5.xlarge

Microsoft Azure deployments

Return to top

To deploy your Orion Platform product on Microsoft Azure, consider using the following instance types, listed according to NPM license levels.

Feature

Small

SL100, SL250, SL500

Medium

SL2000

Large

SLX

XL (up to 400,000 elements)

Orion server

DS12_v2

4 CPU

16 GB RAM

150 GB disk

DS12_v2

4 CPU

16 GB RAM

150 GB disk

DS4_v2

8 CPU

32 GB RAM

150 GB disk

DS4_v2

8 CPU

32 GB RAM

150 GB disk

SolarWinds Orion database server in an Azure VM

D12_v2

4 CPU

30.5 GB RAM

System SSD 80 GB (included in D12_v2) + Data Azure Storage Disk Volume 500 GB*

DS4_v2 Standard

8 CPU

28 GB RAM

System SSD 126 GB (included in Azure VM instance) + 1 TB for SQL database (included in Azure SQL Server Computer)

D4_v2

Azure Storage Disk with Provisioned IOPS recommended

8 CPU

61 GB RAM

System SSD 160 GB (included in D4_v2) + 2x Data Azure Storage Disk Volume 500 GB*

E32-8s_v3

Azure Storage Disk with Provisioned IOPS recommended

8 CPU

256 GB RAM

System SSD 512 GB (included in E32-8s_v3) + 2x Data Azure Storage Disk Volume 500 GB*

SolarWinds Orion database using Azure SQL DB

All installed products must run on Orion Platform 2019.2, such as:

  • DPAIM 11.2
  • EOC 2.2
  • ETS 11.0.8
  • IPAM 4.9
  • LA 2.1
  • NCM 8.0
  • NPM 12.5
  • NTA 4.6
  • PM 2.1.7
  • SAM 6.9
  • SCM 1.2
  • SRM 6.9
  • UDT 3.4
  • VMAN 8.5
  • VNQM 4.6
  • WPM 3.0

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

When deploying Azure SQL and creating a new user in the Configuration wizard, SA account credentials are required.

When using Azure SQL for your database server, the required tiers depend on whether you are using memory-optimized tables. Memory-optimized tables (In-Memory OLTP), supported in MS SQL Server 2016 and 2019, improve the performance of transaction processing, data ingestion, data load, and transient data scenarios.

Azure SQL DB tiers if using In-Memory OLTP

DTU Tier P1

vCore Business Critical Gen4 Tier 1

vCore Business Critical Gen5 Tier 2

DTU Tier P2

vCore Business Critical Gen4 Tier 2

vCore Business Critical Gen5 Tier 2

DTU Tier P4

vCore Business Critical Gen4 Tier 4

vCore Business Critical Gen5 Tier 4

DTU Tier P11

vCore Business Critical Gen4 Tier 16

vCore Business Critical Gen5 Tier 14

Azure SQL DB tiers without In-Memory OLTP

DTU Standard Tier S3

DTU Premium Tier P1

vCore General Purpose Tier 2

vCore Business Critical Tier 2

DTU Standard Tier S3

DTU Premium Tier P1

vCore General Purpose Tier 2

vCore Business Critical Tier 2

DTU Standard Tier S4

DTU Premium Tier P2

vCore General Purpose Tier 2

vCore Business Critical Tier 2

DTU Standard Tier S9 (up to 100k elements), S12 (up to 400k elements)

DTU Premium Tier P6 (up to 100k elements), P11 (up to 400k elements)

vCore General Purpose Tier 16 (up to 100k elements), 30 (up to 400k elements)

vCore Business Critical Tier 8 (up to 100k elements), 14 (up to 400k elements).

* If you're not using Azure Disk Storage for SQL servers, consider using Azure Reserved VM Instances.

WPM Recorder requirements

Return to top

In addition to the WPM Recorders added to the Orion server when you install WPM, you can deploy WPM Recorders to other computers on machines other than the Orion server, such as a computer in a branch office.

WPM 3.0 supports two types of recorders — the new WPM Recorder introduced in WPM 3.0 and the Deprecated WPM Recorder from WPM 2.2.3. >> Learn more

Before upgrading the OS to Windows 10 v.1607 or later on a remote machine that hosts a WPM Recorder, back up *.config files for WPM Recorders and WPM Players. Otherwise, Windows may overwrite those files when you upgrade.

The following requirements apply to standalone versions of the new WPM Recorder:

Resource Requirement
CPU Single processor with 1 GHz or more
Memory 2 GB
Operating system

Windows 7, 8, 10

Windows Server 2008, 2012, 2016, and 2019

x64 machines only

TCP/IP ports

80 (TCP) open for HTTP traffic

443 (TCP) open for HTTPS traffic

17777 (TCP) open for SolarWinds traffic

Web browser

Same as the Orion Web Console

The following requirements apply to standalone versions of the Deprecated WPM Recorder:

Resource Requirement
CPU Single processor with 1 GHz or more
Memory 2 GB
Operating system

Windows 7, 8, 10*

Windows Server 2008, 2012, 2016*, and 2019*

*Recordings that include certificate validation may interrupt the WPM Player. >> Learn more

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 Document mode to emulate earlier versions.

WPM Player requirements

Return to top

As described in How WPM works, 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.

You can install a standalone version on any computer that meets the following system requirements. To learn about managing loads on hosts, see Scalability Engine Guidelines for SolarWinds Orion Products. You can also check the Player Load Percentage widget.

If a computer hosts a hypervisor or virtual machine monitor (VMM) running various servers (for example, print or file servers), consider adding another server and installing the WPM Player on that server instead.

Minimum WPM Player requirements

Resource Requirement
CPU Quad core processor or better
Memory 3 GB
Operating system

Windows 7, 8, 10*

Windows Server 2008, 2012, 2016*, and 2019*

*Recordings that include certificate validation may interrupt the WPM Player. >> Learn more

Account and security

Accounts can access the remote administrator share

Updated root certificates

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 (bidirectional)

Web browser

Internet Explorer (IE) 11

If your organization requires an earlier IE version, use IE 11 Document mode to emulate earlier versions.