Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > Internet traffic encryption for additional polling engine on the NPM server

Internet traffic encryption for additional polling engine on the NPM server

Created by Interspire Import, last modified by Magdalena.Markova on Mar 22, 2018

Views: 1,274 Votes: 1 Revisions: 15

Overview

This article provides brief information on Internet traffic encryption for additional polling engine on the NPM server.

Environment

All NPM versions

Detail

When an additional polling engine is deployed, all data transferred between the main and additional polling engines use SolarWinds Information Service (SWIS). All SWIS traffic is encrypted.
Communication between the main and the additional polling engines use the Windows Communication Foundation (WCF) framework. 
The data packets are sent as asynchronous messages from one service endpoint to another.
Communication transfer authentication is based on a certificate which uses TLS channel on port 17777 and this communication is encrypted.

See Centralized Deployment with Additional polling engines in 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 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.

Last modified

Tags

Classifications

Public