Back to Articles

Each product's applications connect to and communicate with other applications over various network TCP ports. This section contains listing of all ports in use by each product.

NOTE: The default transmission protocol for all ports is TCP unless otherwise noted.
Table 1. Required ports for ServAssure NXT components
DestinationSourceNotes
Server node (TO)Listening port (ON)Server node (FROM)Application (FOR)Application protocol
All22SSH, Ansible management serverSSH clientsSSHAnsible server and platform admin user access
Search tier

(Solr nodes)

2888Search tier

(Solr nodes)

Solr or ZookeeperHTTPInter-node cluster communication
Search tier

(Solr nodes)

3888Search tier

(Solr nodes)

Solr or ZookeeperHTTPInter-node cluster communication
Search tier

(Solr nodes)

2181Search tier

(Solr nodes)

ZookeeperHTTPInter-node cluster communication
Search tier

(Solr nodes)

8983Cache tier

(NXT Engine nodes)

SolrHTTPSolr search requests
Search tier

(Solr nodes)

8983Load balancer nodesSolrTCPSolr search requests
Search tier

(Solr nodes)

8983HAProxy nodesSolrTCPSolr search requests
Cache tier

(NXT Engine nodes)

8181Load balancer nodesNXT UI

HTTP

Cache tier

(NXT Engine nodes)

8181HAProxy nodesNXT UIHTTP
Cache tier

(NXT Engine nodes)

8181Customer network, user browsersNXT Engine Admin UIHTTPDefault Admin UI access port when SSL is disabled
Cache tier

(NXT Engine nodes)

8181UI tier

(NXT App nodes)

NXT UIHTTPOnly required if NXT UI is disabled for SSL
Cache tier

(NXT Engine nodes)

8182Load balancer nodesIngest ProxyHTTP
Cache tier

(NXT Engine nodes)

8182HAProxy nodesIngest ProxyHTTP
Cache tier

(NXT Engine nodes)

8281Load balancer nodesNXT UI

HTTPS

Cache tier

(NXT Engine nodes)

8281HAProxy nodesNXT UIHTTPS
Cache tier

(NXT Engine nodes)

8281Customer network, user browsersNXT Engine Admin UIHTTPSOnly required if NXT Engine Admin UI is enabled for SSL
Cache tier

(NXT Engine nodes)

8281UI tier

(NXT App nodes)

NXT UIHTTPSOnly required if NXT UI is enabled for SSL
Cache tier

(NXT Engine nodes)

47500

Cache tier

(NXT Engine nodes)

Apache IgniteTCPIgnite cluster discovery
Cache tier

(NXT Engine nodes)

47501

Cache tier

(NXT Engine nodes)

Apache IgniteTCPIgnite cluster discovery
Cache tier

(NXT Engine nodes)

47500-47600ServAssure Dashboard for Alarm Central nodeApache IgniteTCP
UI tier

(NXT App nodes)

8443 or 443Customer networkUser browsersHTTP/HTTPSIf Load Balancer is used with VIP, then destination is TCP/443 on VIP/frontend.
Data tier

(Cassandra nodes)

7000Data tier

(Cassandra nodes)

Cassandra TCPCassandra inter-node cluster communication
Data tier

(Cassandra nodes)

7001Data tier

(Cassandra nodes)

CassandraTCPCassandra inter-node cluster communication
Data tier

(Cassandra nodes)

9042Cache tier

(NXT Engine nodes)

ServAssure NXTTCP
Data tier

(Cassandra nodes)

9142

Cache tier

(NXT Engine nodes)

ServAssure NXTTCP
Trap receiver nodesConfigurable

Default is 162

CMTS/RMD

Not applicable

UDP
NOTE: A different port may be used, depending on the application used for alarm notifications.
Table 2. Required ports for ServAssure Collection Platform components
DestinationSourceNotes
Server node (TO)Listening port (ON)Server node (FROM)Application (FOR)Application protocol
All22SSH, Ansible management serverSSH clientsSSHAnsible server and platform admin user access
Logger5044AllFilebeat for application loggingTCPOptional: filebeat agents send application logs to the central logging server.
Logger5601Administrators, user browser

Kibana/Opensearch-dashboard (Logger) UI

SSLCentral logging server UI - Kibana
ServAssure Poller69CMTS/CM

Not applicable

UDP/TFTP3.1 PNM probe data from CMTS or CM, Poller will need SNMP set commands to devices.
ServAssure L2TP ReceiverN/ARPD/RMDL2TPv3 over IP #115

IP_PROTO(115)

Port is not applicable. L2TP traffic must be routed to the L2TP server.

L2TPv3 is configured to use IP (IP_PROTO(115)) as its transport protocol.

L2TP over IP stream of data for static pseudowire

CMTS/CM161ServAssure Poller

Collecting CM/CMTS information

UDP

SNMP

Data Collection
CMTS21ServAssure Poller

Upstream Spectrum Analyzer

FTPPoller needs FTP username and password for PNM tests (CMTS RxMer and CMTS Upstream Spectrum Analysis) for E6000 only.
CMTS22ServAssure Poller / PNM Server or Single TFTP Server

Upstream Spectrum Analyzer

SFTPPoller needs SFTP username and password for PNM tests (CMTS RxMer and CMTS Upstream Spectrum Analysis).

SFTP uses the SSH port.

CMTS22ServAssure Poller

Upstream Spectrum Analyzer

TCPDefault SSH port to the CMTS to run CLI commands for Upstream Spectrum Captures (E6000 compatibility mode only)
CMTS23ServAssure Poller

Upstream Spectrum Analyzer

TCPDefault Telnet port to the CMTS to run CLI commands for Upstream Spectrum Captures (E6000 compatibility mode only).
RMD (CommScope)22ServAssure Poller

Not applicable

SCPPNM CMTS RxMer tests.
RMD (CommScope)161ServAssure Poller

Not applicable

UDP

SNMP

PNM CMTS RxMer tests.
ServAssure Collection Manager8085ServAssure PollerData publishingHTTPData Ingest
ServAssure Collection Manager47500ServAssure Collection ManagerApache IgniteTCPInter-node discovery
ServAssure Collection Manager47501ServAssure Collection ManagerApache IgniteTCPInter-node communication
CTM API ConfigurableServAssure Collection Manager

CTM API

HTTP(S)CTM API access if enabling SNMPv3 data collection.

SNMPv3 support is a licensed feature that requires deployment and configuration of an external token manager as well as significant additional hardware and system resources. Please contact CommScope Professional Services for additional information.

Table 3. Required ports for customer access, authentication, and notification servers components
DestinationSourceNotes
Server node (TO)Listening port (ON)Server node (FROM)Application (FOR)Application protocol
Customer Notification EndpointConfigurableCache tier

(NXT Engine nodes)

NotificationsHTTPS
Customer Premise LDAP389UI tier

(NXT App nodes)

LDAP Client AuthorizationTCP
Customer Premise LDAPS636UI tier

(NXT App nodes)

LDAPS Client AuthorizationTCP
Table 4. Required ports for Message bus components
DestinationSourceNotes
Server node (TO)Listening port (ON)Server node (FROM)Application (FOR)Application protocol
RabbitMQ5672Cache tier

(NXT Engine nodes)

MessagingAMQPWhen integrated with ServAssure Collection Platform
RabbitMQ5672RabbitMQMessagingAMQP
RabbitMQ5672ServAssure Poller

Messaging

AMQP
RabbitMQ5672ServAssure Collection Manager

Messaging

AMQP
RabbitMQ 5672Profile OptimizerMessagingAMQP
RabbitMQ25672RabbitMQRabbitMQ applicationAMQPRabbitMQ Clustering Port
RabbitMQ4369RabbitMQRabbitMQ applicationAMQP

Peer discovery service used by RabbitMQ nodes

RabbitMQ15672Administrators, user browsersRabbitMQ Admin UIHTTP
Table 5. Required ports for Load balancer components
DestinationSourceNotes
Server node (TO)Listening port (ON)Server node (FROM)Application (FOR)Application protocol
HAProxy25002

Customer network

HAProxy administrators, user browsersHTTP
HAProxy8181UI tier

(NXT App nodes)

ServAssure NXT UI backend to Cache tier (NXT Engine nodes)HTTP
HAProxy8182Trap receiver nodesIngestHTTPSending filtered traps to Ingest
HAProxy8281UI tier

(NXT App nodes)

ServAssure NXT UI backend to Cache tier (NXT Engine nodes)HTTPSRequired when SSL is enabled.
HAProxy8983Cache tier

(NXT Engine nodes)

Solr searchTCP
Load balancer8181UI tier

(NXT App nodes)

ServAssure NXT UI backend to Cache tier (NXT Engine nodes)HTTP
Load balancer8182Trap receiver nodesIngestHTTPSending filtered traps to Ingest
Load balancer8281UI tier

(NXT App nodes)

ServAssure NXT UI backend to Cache tier (NXT Engine nodes)HTTPSRequired when SSL is enabled.
Load balancer8983Cache tier

(NXT Engine nodes)

Solr searchTCP