Submit a ticketCall us

Announcing NCM 7.7
With NCM 7.7, you can examine the rules that make up an access control list for a Cisco ASA device. Then you can apply filters to display only rules that meet the specified criteria, order the rules by line number or by the hit count, and much more.
See new features and improvements.

Home > Success Center > Network Performance Monitor (NPM) > NPM 12.2 Administrator Guide > SolarWinds NPM requirements > NPM software requirements

NPM software requirements

Created by Lori Krell_ret, last modified by Magdalena.Markova on Apr 12, 2017

Views: 1,222 Votes: 3 Revisions: 17
  • 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.

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
  • Windows 8.1, 64-bit (not Standard Edition)
  • Windows 10

Installing SolarWindsNPM on Windows Server 2012 R2 Essentials or Windows Server Core is not supported.

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 Internet Information Services (IIS), version 8.0 or later

Use default settings for Anonymous Authentication of the SolarWinds NetPerfMon website (Enabled).

IIS is installed by the SolarWinds installer. You can install this software manually to reduce your installation time or network bandwidth.

.NET Framework

.NET 4.6.2

Run the same version of. NET on your primary server and any Additional Polling Engines or Additional 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

Web console browser

  • Microsoft Internet Explorer version 11 or later with Active scripting
  • Microsoft Edge
  • Firefox 52.0 or later
  • Chrome 58.0 or later

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

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.

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, make sure port 4369 is open.
  • RPC ports > 1024 (TCP, bidirectional) is used by the Job Engine v2 process 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.

 

Port Protocol Service/
Process
Direction Description Encryption
12 UDP SNMP Informs Bidirectional Receive trap messages n/a
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 Bidirectional Resolving 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 web console. For example, if you specify an IP address of 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 might also be used for Cisco UCS monitoring.

n/a

161

UDP

SolarWinds Job Engine v2

SolarWinds Cortex

Bidirectional

Send and receive SNMP information

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

162

UDP

SolarWinds Trap Service Inbound

Receive trap messages

n/a

443

TCP

IIS Inbound

Default port for https binding.

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

Communication between the SolarWinds server and 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

Communication with the SQL Server Browser Service to determine how to communicate with certain non-standard SQL Server installations. <conditionaltext data-mc-conditions="Core.MindTouch">For more information, see this Microsoft Technet article.</conditionaltext>

n/a

1801

TCP

MSMQ Bidirectional

MSMQ WCF binding <conditionaltext data-mc-conditions="Core.MindTouch">(for more information see this KB: http://support.microsoft.com/kb/183293)</conditionaltext>

WCF

5671

TCP

RabbitMQ

AMQP

Bidirectional

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

Sending messages to RabbitMQ.

TLS 1.2

17777

TCP

SolarWinds Orion Module Engine

SolarWinds Information Service

SolarWinds Information Service V3

SolarWinds Cortex

Bidirectional

Communication between services and SolarWinds Orion module traffic.

Communication between the Orion Web Console and the polling engine.

Communication between the main server and pool members.

RSA handshake, AES 256 communication using WCF

TLS 1.2 with Cortex

17778

HTTPS

SolarWinds Agent Inbound to the Orion server

Required for access to the SWIS API and agent communication

SSL
Last modified
00:25, 12 Apr 2017

Tags

Classifications

Public