Documentation forOrion Platform

SolarWinds Port Requirements

Updated: August 18, 2021

The following reference provides a comprehensive list of port requirements for SolarWinds products. The ports vary from product to product and on a per use basis. In some cases, ports are configurable. Refer to your product Administrator Guide for more information.

If you have installed one or more Orion Platform products, make sure you review ports for the Orion Platform and the features you use in addition to the ports required by your product.

Orion Platform products

Ports for Orion Platform features

Additional Polling Engines

Additional Polling Engines have the same port requirements as the Main Polling Engine. The following ports are the minimum required for an Additional Polling Engine to ensure the most basic functions.

Port Proto-
col
Service/
Process
Direction Description
161 UDP SolarWinds Job Engine Outbound The port used for sending and receiving SNMP information.
162 UDP SolarWinds Trap Service Inbound The port used for receiving trap messages.

1433

TCP

SolarWinds Collector
Service
Outbound The port used for communication between the APE and the Orion database.
1434 UDP SQL Browse Service Outbound The port used for communication with the SQL Server Browser Service to determine how to communicate with certain non-standard SQL Server installations. Required only if your SQL Server is configured to use dynamic ports.

5671

TCP

RabbitMQ Outbound

The port used for SSL-encrypted RabbitMQ messaging from the Main Polling Engine to the Additional Polling Engine.

17777

TCP

SolarWinds Information
Service
Bidirectional

The port used for communication between the Additional Polling Engine and the Main Polling Engine.

Additional Web Servers

Port Protocol Service/Process Direction Description

80

TCP

World Wide Web Publishing Service Inbound

Default additional web server port. Open the port to enable communication from your computers to the Orion Web Console.

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.

443 TCP IIS Inbound The default port for https binding.

1433

TCP

SolarWinds Information Service Outbound

The port used for communication between the SolarWinds server and the SQL Server. Open the port from your Orion Web Console to the SQL Server.

5671 TCP RabbitMQ Outbound

The port used for SSL-encrypted RabbitMQ messaging from the Additional Web Server to the Main Polling Engine.

17777

TCP

SolarWinds Information Service Outbound

Orion module traffic. Open the port to enable communication from all polling engines (both Main or Additional) to the Additional Web Server, and from the Additional Web Server to polling engines.

High Availability

Port Protocol Service/Process Direction Description
53 UDP SolarWinds High Availability Service outbound Used when failing over with a virtual hostname to update the virtual hostname's DNS entry and for periodic monitoring.
135 TCP SolarWinds High Availability Service bidirectional Used to remotely manage services including DHCP server or DNS server.
4369 TCP RabbitMQ bidirectional TCP ports 4369 and 25672 must be open between the main and secondary servers to allow RabbitMQ clustering between the two servers. These ports exchange EPMD and Erlang distribution protocol messages for RabbbitMQ. They do not need to be open in additional polling engine pools.
5671 TCP

SolarWinds High Availability

bidirectional Port 5671 must be open into the HA pool with the main Orion server from all Orion servers.
17777 TCP SolarWinds installer bidirectional Used when installing the standby server software. You can close this port after installation.
25672 TCP RabbitMQ bidirectional TCP ports 4369 and 25672 must be open between the main and secondary servers to allow RabbitMQ clustering between the two servers. These ports exchange EPMD and Erlang distribution protocol messages for RabbbitMQ. They do not need to be open in additional polling engine pools.

Network Atlas

Port

Protocol

Service/Process Direction

Description

17777 TCP SolarWinds Information Service Bidirectional Remote instances of Network Atlas require TCP on port 17777 to either the SolarWinds NPM or the SolarWinds EOC server.

Orion Agent

Orion Agents: target computer

Port Protocol Service/
Process
Direction Description Communication
method
OS
22 TCP

sshd

Agent installer

Inbound

Used to install the agent on Linux/Unix computers through SSH and SFTP or SCP.

Either Linux/Unix
135
TCP

Agent installer

Inbound

(DCE/RPC Locator service) Microsoft EPMAP. This port must be open on the target computer for remote deployment.

WMI is only needed for deploying the agent to a Windows server with the Add Node or Add Agent wizard. If you do not want to open WMI ports required for software deployment, you can use another deployment method for the Agent.

WMI also uses any random TCP port greater than 1024. See WMI portocalypse on THWACK.

Either Windows
445
TCP Agent installer

Inbound

Microsoft-DS SMB file sharing. This port must be open on the target computer (inbound) for remote deployment.

Either Windows
17778
TCP

SolarWinds Agent

Outbound

Used continuously by the agent to communicate back to the Orion server. Also used to deploy the agent. Agent-initiated

All

17790

TCP

SolarWinds Agent

Inbound

Used to communicate with the Orion server. Server-initiated All

Orion Agent: Orion Server

Port Protocol Service/
Process
Direction Description Communication
method
OS
22 TCP n/a

Outbound

Used to install the agent on Linux/Unix computers through SSH and SFTP or SCP.

Either Linux/Unix
17778
TCP

Orion Module Engine

SolarWinds Agent

Inbound

Used continuously by the agent to communicate back to the Orion server. Also used to deploy the agent. Agent-initiated

All

17790

TCP

Orion Module Engine

SolarWinds Agent

Outbound

Used to communicate with the Orion server. Server-initiated All

Orion Agent: Local ports

The following ports are required for local communication inside the server or agent. Do not open them in the firewall; they are used only by local services.

Port Protocol Direction Description
17775 TCP Inbound (on agents) RestAPI forwarder for Cortex
17798 TCP Inbound (on servers) Cortex Diagnostics API
Dynamic TCP Inbound (on agents) Port used for communication between the JobEngine and its workers.

Orion Installer

Port Protocol Service/Process Direction Description

80

HTTP

Installer (SolarWinds Administration Service) Outbound Used when installation data are transferred from the main polling engine to additional polling engines (depending on the Orion Platform configuration).
443 HTTPS Installer (SolarWinds Administration Service)

Inbound (online installer)

Outbound (when data are downloaded from the main polling engine to additional polling engines)

Used by the online installer when data are downloaded from the Internet. It can also be used when installation data are transferred from the main polling engine to additional polling engines.
17777 WCF

SolarWinds Administration Service

Bidirectional

Used for the communication between polling engines, also used as a fallback option when HTTP/HTTPS fails to download data to additional polling engine.

Database Performance Analyzer Integration Module (DPAIM)

 

Engineer's Toolset (ETS)

Engineer's Toolset on the Desktop

 

Engineer's Toolset on the Web

 

Enterprise Operations Console (EOC)

 

IP Address Manager (IPAM)

 

Log Analyzer

 

NetFlow Traffic Analyzer (NTA)

 

Network Configuration Manager (NCM)

 

Network Performance Monitor (NPM)

NPM ports

 

NetPath™

 

Patch Manager

 

Server & Application Monitor (SAM)

SAM ports

 

Container monitoring

Port Protocol Service/Process Direction Description
38102 HTTPS Container Monitoring Bidirectional Communication between the Orion Business Layer and container environments

Additional port requirements for container services include:

  • For Docker and Docker Swarm:
    • 80: Used to download the configuration file from the Orion server
    • 4043: Container port (internal Docker communication)
    • 6784: Report status (internal Docker communication)
  • For Kubernetes (K8s) and Microsoft Azure Kubernetes (AKS):
    • 4043: Target port/Container port (internal Docker communication)
    • 10250: Listening port for Kubelet agent
    • 30043: Node port (internal Docker communication)
  • For Apache Mesos:
    • 4043: Mesos master server port (internal Mesos communication)
    • 8080: Deployment service (internal Mesos communication)

Nutanix

Port Protocol Service/Process Direction Description Encryption
22 SSH SolarWinds Job Engine v2 Outbound The port used for Nutanix hardware health monitoring.  
9440 HTTPS and TCP SolarWinds Cortex Bidirectional Communication between polling engines and the Nutanix AOS API. TLS 1.2

Server Configuration Monitor (SCM)

 

Storage Resource Monitor (SRM)

 

User Device Tracker (UDT)

 

Virtualization Manager (VMAN)

VMAN ports

 

Container monitoring

Port Protocol Service/Process Direction Description
38102 HTTPS Container Monitoring Bidirectional Communication between the Orion Business Layer and container environments

Additional port requirements for container services include:

  • For Docker and Docker Swarm:
    • 80: Used to download the configuration file from the Orion server
    • 4043: Container port (internal Docker communication)
    • 6784: Report status (internal Docker communication)
  • For Kubernetes (K8s) and Microsoft Azure Kubernetes (AKS):
    • 4043: Target port/Container port (internal Docker communication)
    • 10250: Listening port for Kubelet agent
    • 30043: Node port (internal Docker communication)
  • For Apache Mesos:
    • 4043: Mesos master server port (internal Mesos communication)
    • 8080: Deployment service (internal Mesos communication)

Nutanix

Port Protocol Service/Process Direction Description Encryption
22 SSH SolarWinds Job Engine v2 Outbound The port used for Nutanix hardware health monitoring.  
9440 HTTPS and TCP SolarWinds Cortex Bidirectional Communication between polling engines and the Nutanix AOS API. TLS 1.2

VoIP & Network Quality Manager (VNQM)

 

Web Performance Monitor (WPM, formerly SEUM)

 

Other SolarWinds products

Access Rights Manager (ARM)

 

Dameware (DRS, MRC, DRE)

Dameware centralized

 

Dameware stand-alone

 

Dameware Remote Everywhere

 

Database Performance Analyzer (DPA)

 

ipMonitor

 

Kiwi CatTools

 

Kiwi Syslog Server

 

Network Topology Mapper (NTM)

 

Security Event Manager (SEM)

 

Serv-U File Server

 

Web Help Desk (WHD)