Communication port requirements


Peer communications are established through HTTP and Transmission Control Protocol (TCP) ports. 

Some content is unavailable due to permissions.

communications require unique port assignments for each component, and each component has specific port requirements. The Web server requires one port for standard communications and another port to receive shutdown commands. Different components can use the same port, provided they are installed on different computers. Note that two peers cannot be installed using the same ports on the same server.

A port number must be available exclusively on the computer. 

Port requirements for TrueSight Orchestration in a classic mode

The following table describes the port requirements for TrueSight Orchestration in a classic mode. 

Some content is unavailable due to permissions.

Component server ports

Port description

Protocol

Default port

Repository

Standard communication port

HTTP/HTTPS

28080

Primary CDP, AP, LAP, HA-CDP, OCP

Standard communication port

HTTP/HTTPS

38080

BMC authentication service

Standard communication port

HTTP/HTTPS

8080/8443

Health and Value Dashboard

Standard communication port

HTTP/HTTPS

18080

Repository

Shutdown port

HTTP/HTTPS

28050

Primary CDP, AP, LAP, HA-CDP, OCP

Shutdown port

HTTP/HTTPS

38050

BMC authentication service

Shutdown port

HTTP/HTTPS

8005

Health and Value Dashboard

Shutdown port

HTTP/HTTPS

18050

Primary CDP

Peer communications port

JMS with SSL

61719

Secondary CDP (HA-CDP), AP, LAP

The installation program sets the start of the default port range by adding 2 to the primary CDP port number.  For example, if the primary CDP port number is 61719, the port number for the HA-CDP, AP, and LAP will be 61721. The port number for all of these peers will be the same.

Peer communications port

JMS with SSL

61721

Embedded Remedy Single Sign-On

The installation program sets the start of the default port range by adding 10 to the web service port number.  For example, if the repository web service port number is 28080, the embedded RSSO on the repository uses the first available port number (in increments of 10) in the range 28090 - 65535.

Similarly, if the CDP web service port is 38080, the corresponding embedded RSSO uses the first available port number (in increments of 10) in the range 38090 - 65535.

RSSO communications port

JMS with SSL

28090 on repository

38090 on CDP

Some content is unavailable due to permissions.

Dashboard uses this port to communicate with the grid.

You cannot specify a different port. Ensure that this port is not used by any other entity. You cannot change this port during installation.

JMX RMI service port

 

1089

Cassandra database

Standard communication port


9024

Port requirements for TrueSight Orchestration in containers

The following table describes the port requirements for TrueSight Orchestration in containers. 

Some content is unavailable due to permissions.

in containers ports

Port description

Default port

Docker Cluster Management

TCP

2377

Nodes communication

TCP and UDP

7946

Overlay network traffic

TCP and UDP

4789

Docker registry

TCP

5000

Apache Derby Database

TCP

1527

Load Balancer

TCP

9090

Repository

TCP

28080

CDP

TCP

38080 and 61719

SSH, SFTP,SCP

TCP

22

Telnet

TCP

23

FTP

TCP

21

POP adapter

TCP

110

IMAP Adapter

TCP

143

POP over SSL

TCP

995

IMAP over SSL

TCP

993

SMTP adapter

TCP

25

SMTP over SSL

TCP

465

SNMP Monitor

UDP

162

SNMP Actor

TCP

161

Port requirements for Development Studio

Some content is unavailable due to permissions.

Development Studio, which is a client, needs access to the following ports:

  • CDP server's standard communication port 38080
  • Peer communications port 61719
  • Repository server's standard communication port 28080

The following image depicts the communication paths (shown in the Communication-paths topic) and the communication ports used for communication over these paths.


CommPathsWithPortReqs.png


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*