Network Management
Internet traffic encryption for additional polling engine on the NPM server
This article provides information on internet traffic encryption for additional polling engine on the NPM server.
First published date
Last published date
Overview
This article provides information on internet traffic encryption for additional polling engines on the NPM server. It also lists port requirements.
Product section
Resolution
Starting with Orion Platform 2020.2.6, communication between the main and the additional polling engines uses RabbitMQ messaging (AMQP over TLS/SSL).
The data packets are sent as asynchronous messages from one service endpoint to another.
Communication transfer authentication is based on a certificate that uses the TLS channel on port 17777, and this communication is encrypted.
See Centralized Deployment with Additional Polling Engines in the Scalability Engine Guidelines for SolarWinds Orion Products.
Port requirements for 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 |
PROTOCOL |
SERVICE/PROCESS |
DIRECTION |
DESCRIPTION |
|---|---|---|---|---|
|
1433 |
TCP |
SolarWinds Collector Service |
Outbound |
The port used for communication between the APE and the Orion database. |
| 1801 | TCP | Message Queuing WCF | Inbound | Relevant only for Orion Platform 2020.2.5 and earlier. In 2020.2.6, MSMQ was completely removed. The port used for MSMQ messaging from the Orion Web Console to the Additional Polling Engine. |
|
5671 |
TCP |
RabbitMQ |
Bidirectional |
The port used for SSL-encrypted RabbitMQ messaging from the Orion Web Console to the Additional Polling Engine. |
|
17777 |
TCP |
SolarWinds Information Service |
Bidirectional |
The port used for communication between the Additional Polling Engine and the Orion Web Console. |