Submit a ticketCall us
Home > Success Center > Web Performance Monitor (WPM) > WPM Documentation > WPM 2.2.2 system requirements

WPM 2.2.2 system requirements

Created by carolyn.mazenko, last modified by carolyn.mazenko on Dec 20, 2018

Views: 1,087 Votes: 0 Revisions: 43

​Updated October 22, 2018

Important: These recommended system requirements are for SolarWinds Web Performance Monitor (WPM) 2.2.2 as a single product installed on Orion Platform 2018.2.

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 also install standalone versions of the WPM Recorder and Player on a separate computer, as described in the WPM Administrator Guide. For example, you can install a copy of the WPM Player on a workstation 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.

Software requirements

  • SolarWinds only supports installing the Orion agent on domain controllers. Do not install any other SolarWinds products on domain controllers.
  • SolarWinds does not support the installation of any Orion product on the same server as a Microsoft SharePoint, Microsoft Exchange, or Research in Motion (RIM) Blackberry server, nor do we support sharing a database server with those applications.

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 and 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 these versions is ending and they will not be supported on future Orion Platform 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
  • English (UK or US)
  • German
  • Japanese
  • Simplified Chinese

IP address version

IPv4

IPv6 implemented as a dual stack

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

Orion Web Console browser

  • Microsoft Internet Explorer 11 or later with Active scripting
  • Microsoft Edge
  • Mozilla Firefox 56.0 or later
  • Google Chrome 62.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 by 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 Service/
Process
Direction Description Encryption12

user-defined, default: 22

SSH

SolarWinds Job Engine v2

IIS

Bidirectional Port for accessing ASA devices through CLI Device-based

25

TCP

SolarWinds Alerting Service V2 Outbound

SMTP port for non-encrypted messages

n/a
53 UDP SolarWinds Job Engine v2 Outbound Resolving DNS queries n/a

80

TCP

IIS Inbound

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.

The port may also be used for Cisco UCS monitoring.

n/a
135 TCP     Microsoft EPMAP (DCE/RPC Locator service)  

161

UDP

SolarWinds Job Engine v2 Outbound

Sending and receiving SNMP information.

SNMP v1 and v2 are unencrypted. SNMP v3 uses AES & 3DES encryption.

162

UDP

SolarWinds Trap Service Inbound

Receiving trap messages

n/a

443

TCP

IIS Inbound

Default port for https binding.

Also used for bi-directional ESX/ESXi server polling, or for Cisco UCS monitoring.

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

Receiving 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 between the Orion Server and the SQL Server. Open the port from the Orion Web Console to the SQL Server.

n/a

1434

UDP

SolarWinds Alerting Service V2

SolarWinds Administration Service

SolarWinds Information Service

SolarWinds Information Service V3

SolarWinds Orion Module Engine

Outbound

Used for communication with the SQL Server Browser Service to determine how to communicate with certain non-standard SQL Server installations.

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 Orion servers.

TLS 1.2

17777

TCP

SolarWinds Orion Module Engine

SolarWinds Information Service

SolarWinds Information Service V3

Bidirectional

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.

RSA handshake, AES 256 communication using WCF

17778

HTTPS

SolarWinds Agent Inbound to the Orion server

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 Player Inbound Used for player-initiated communications mode n/a

 

Orion agent port requirements 

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 inbound  

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 ports to connect to the Windows OS.

445

TCP

inbound  

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.

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.

Important: 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. See Change the Agent Port.

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.

In Passive mode, port 17790 must be opened on the host where the agent is installed and allowed by the firewall.

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 monitored remote computers run Windows 2008 R2.

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.

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).

Hardware

Small
SL100, SL250, SL500

Medium
SL2000

Large
SLX

XL (up to 400,000 monitored elements)

CPU

Quad core processor or better

Quad core processor or better

Quad core processor or better

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

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.

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

6 GB minimum

8 GB recommended

8 GB minimum

16 GB recommended

16 GB minimum

32 GB recommended

32 GB minimum

Database server (SQL 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.

Requirements Small
SL100, SL250, SL500
Medium
SL2000
Large
SLX
XL
(up to 400,000 monitored elements)

SQL Server

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

  • SQL Server 2012
  • SQL Server 2012 SP1
  • SQL Server 2012 SP2
  • SQL Server 2012 SP3
  • SQL Server 2012 SP4
  • SQL Server 2014
  • SQL Server 2014 SP1
  • SQL Server 2014 SP2
  • SQL Server 2016
  • SQL Server 2016 SP1
  • SQL Server 2017 (including installations on Linux)

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.

Recommendations

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

  • 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 (CI) database on a case-sensitive CS SQL Server.

The Orion Platform does not support case-sensitive databases.

CPU

Quad core processor or better

Dual quad core processor or better

Dual quad core processor or better

4 CPUs/60 cores

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

Memory, listed by NPM license levels

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

Authentication

Either mixed-mode or Windows authentication. If you require SQL authentication, you must enable mixed mode on your SQL server.
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

Amazon Web Services (AWS deployments)

To deploy your Orion Platform using Amazon Web Services, consider the following requirements, 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
  • 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

  • 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 Additional Polling Engines (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 and Player system requirements

The WPM Recorder is a Windows application that you can install on any computer that meets the following recommended system requirements:

Resource Requirement
CPU 1 GHz or better

Memory

2 GB

Operating system

Microsoft Windows Vista, 7, 8, Server 2003, Server 2008, Server 2012 or Server 2016 
TCP/IP ports 80 (TCP) open for http traffic
443 (TCP) open for https traffic
17777 (TCP) open for SolarWinds traffic
Browser

Internet Explorer (IE) 11

If your organization requires an earlier IE version, use IE 11's document modes to emulate earlier versions.

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

Microsoft Windows Vista, 7, 8, Server 2003, Server 2008, Server 2012 or Server 2016 
TCP/IP ports

80 (TCP) open for http traffic
443 (TCP) open for https traffic
17777 (TCP) open for SolarWinds  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

Browser

Internet Explorer (IE) 11

Note: If your organization requires an earlier IE version, use IE 11's document modes to emulate earlier versions.

Last modified

Tags

Classifications

Public