Documentation forSolarWinds platformand Orion Platform

SolarWinds Hybrid Cloud Observability port requirements

SolarWinds platform RC documentation - The following content is a draft for a SolarWinds platform Release Candidate. All content subject to change. Some links might not function yet.

See the following sections for port requirements:

SolarWinds Installer port requirements for SolarWinds Hybrid Cloud Observability

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 engine (depending on the SolarWinds 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.

SolarWinds platform server port requirements for SolarWinds Hybrid Cloud Observability

  • 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 or Process Direction Description
21 TCP SolarWinds Collector Service Bidirectional The port used for FTP (CDR/CMR download).
user-defined, default: 22 SSH

SolarWinds Job Engine v2

IIS

Outbound from the Observability server to the device

Port for accessing ASA devices through CLI.

Used by Nutanix hardware health monitoring.

23 TCP SolarWinds Collector Service Bidirectional The port used for TELNET for CLI (operation polling).
25 TCP SolarWinds Alerting Service V2 Outbound SMTP port for non-encrypted messages.
53 UDP SolarWinds Job Engine v2 Bidirectional Resolving DNS queries.
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 Observability Web Console.

The port might also be used for Cisco UCS monitoring.

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

Required for devices polled via WMI. Used to initiate communication with the remotely managed host.

Collect Asset Inventory data.

161 UDP

SolarWinds Job Engine v2

SolarWinds Cortex

Bidirectional

Send and receive SNMP information.

Collect Asset Inventory data.

162 UDP

SolarWinds Trap Service

SNMP Informs

Inbound Receive trap messages.
443 TCP

IIS

World Wide Web Publishing Service

Bidirectional

Default port for HTTPS binding.

The port used for conducting secure SSL communications.

Also used for bidirectional ESX/ESXi server polling and Cisco UCS monitoring.

445 TCP File and Printer Sharing (SMB-In) Bidirectional Used by Asset Inventory to poll machines with VBScript if Windows updates cannot be processed remotely.
465 TCP SolarWinds Alerting Service V2 Outbound SMTP port used to send TLS-enabled email alert actions.
514 UDP SolarWinds Syslog Service Inbound Receive syslog messages.
587 TCP SolarWinds Alerting Service V2 Outbound SMTP port used to send TLS-enabled email alert actions.
1024 - 1034 TCP Job Engine v2 Bidirectional Dynamically assigned ports for WMI (Windows) used to communicate with Windows nodes.
1433 TCP

SolarWinds Alerting Service V2

SolarWinds Administration Service

SolarWinds Information Service

SolarWinds Information Service V3

SolarWinds Module Engine

Outbound Communication between the Observability server and the SQL Server.
1434 UDP

SolarWinds Alerting Service V2

SolarWinds Administration Service

SolarWinds Information Service

SolarWinds Information Service V3

SolarWinds Module Engine

SQL Server Browse Service

Outbound

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.

1468 TCP SolarWinds Syslog Service Inbound Receive syslog messages.
5005 UDP SolarWinds Collector Service Bidirectional The port used for RTCP data (call metrics) listening from Avaya Call Manager.
5022 TCP SolarWinds Collector Service Bidirectional The port used for communication with Avaya Call Manager via CLI through SSH.
5671 TCP RabbitMQ Bidirectional

For encrypted RabbitMQ messaging (AMQP/TLS) into the Main Polling Engine from all Observability servers (Additional Polling Engines, HA servers, or Additional Web Servers).

Sending messages to RabbitMQ.

6514 TCP SolarWinds Syslog Service Inbound Receive syslog messages.
8443 HTTPS SolarWinds Orion Module Engine/Business Layer Plugin Outbound The port used for Cisco Call Manager AXL credentials troubleshooting.
17777 TCP

SolarWinds Module Engine

SolarWinds Information Service SolarWinds Information Service V3 SolarWinds Cortex

Bidirectional

Communication between services and SolarWinds module traffic.

Communication between the Observability Web Console and the polling engines.

Communication between the main server and pool members.

17778 HTTPS SolarWinds Agent Inbound to the Observability server Communication between the Observability server, the SolarWinds Information Service (SWIS) API, and agents.
38008 TCP/IP SolarWinds Credentials service (SolarWinds.Credentials) Inbound Supports the Manage Credentials page, and features that use those credentials, such as API pollers.
38010 TCP/IP SolarWinds API Poller service (Orion.ApiPoller) Inbound Supports the API Poller feature.
50000 TCP SolarWinds Collector Service Bidirectional The port used for CDR data (call records) listening from Avaya Call Manager.

Ports required for container monitoring in SolarWinds Hybrid Cloud Observability

Port Protocol Service/Process Direction Description
38012 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 SolarWinds platform 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)

Ports required for Nutanix inSolarWinds Hybrid Cloud Observability

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

Additional polling engine port requirements for SolarWinds Hybrid Cloud Observability

Additional polling engines (APEs) 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 by the Additional polling engine (APE) to query for SNMP information on the device and to send it to the APE.
162 UDP SolarWinds Trap Service Inbound The port used by the APE for receiving trap messages from devices.

1433

TCP

SolarWinds Collector
Service
Outbound The port used for communication between the APE and the SolarWinds platform database.
1434 UDP SQL Browse Service Outbound The port used for communication with the SQL Server Browser Service (SolarWinds platform database) and the APE 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 server port requirements for SolarWinds Hybrid Cloud Observability

Port Protocol Service/Process Direction Description

80

TCP

World Wide Web Publishing Service Inbound

Default Additional polling engine port. Open the port to enable communication from your computers to the SolarWinds platform Web Console.

If you specify any port other than 80, you must include that port in the URL used to access the SolarWinds platform 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 platform server and the SQL Server. Open the port from your SolarWinds platform Web Console to the SQL Server.

5671 TCP RabbitMQ Outbound

The port used for SSL-encrypted RabbitMQ messaging from the Additional polling engine 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 polling engine, and from the Additional polling engine to polling engines.

High Availability port requirements for SolarWinds Hybrid Cloud Observability

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 SolarWinds platform server from all SolarWinds platform 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 requirements for SolarWinds Hybrid Cloud Observability

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.

SolarWinds platform agent port requirements for SolarWinds Hybrid Cloud Observability

SolarWinds platform agent: Target computer

Port Protocol Service or 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 Observability server. Also used to deploy the agent. Agent-initiated All
17790 TCP SolarWinds Agent Inbound Used to communicate with the Observability server. Server-initiated All

SolarWinds platform agentSolarWinds platform server

Port Protocol Service or 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

Observability Module Engine

SolarWinds Agent

Inbound Used continuously by the agent to communicate back to the Observability server. Also used to deploy the agent. Agent-initiated All
17790 TCP

Observability Module Engine

SolarWinds Agent

Outbound Used to communicate with the Observability server. Server-initiated All

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

DPA integration port requirements for SolarWinds Hybrid Cloud Observability

In addition to the port requirements necessary for DPA and Observability, integration requires the following ports.

DPA server

Port Protocol Service or Process Direction Description

443 (cloud) or

8124 (on-premises)

TCP (HTTPS)

Windows: Ignite PI Service

Linux: java/tomcat

Inbound

Outbound

This is the default port number of your DPA website and jSWIS proxy. This port must be open to receive data from the Observability server.

SolarWinds platform server

Port Protocol Service or Process Direction Description
17776 TCP SolarWinds Information Service

Inbound

Outbound

This port must be open to access the SolarWinds Information Service API (notifications).

17777 TCP

SolarWinds Information Service

SolarWinds Orion Module Engine

Inbound

Outbound

This port must be open for all Observability traffic.
17778 TCP SolarWinds Information Service

Inbound

Outbound

This port must be open to access the SolarWinds Information Service API.