vRealize Operations Manager has certain port requirements for its components. All ports specified are default ports.

Port Requirements for vRealize Operations Manager

Port Information for Connectivity from Data Node

Connectivity from the data node within the same cluster.

Source

Destination

Port

Protocol

Service Description

Data Node

Remote Collector

443

TCP

HTTPS

Data Node

Remote Collector

80

TCP

HTTP

Data Node

Data Node

443

TCP

HTTPS

Data Node

Data Node

80

TCP

HTTP

Data Node

Master Node

6061

TCP

Communication with Geode Locator on Master

Data Node

Replica Node

6061

TCP

Communication with Geode Locator on Replica

Data Node

Data Node

10000

TCP

Communication with Geode server embedded in Analytics process

Data Node

Data Node

10002-10010

TCP

Geode TCP inter-node failure detection & peer-to-peer TCP communication

Data Node

Data Node

10002-10010

UDP

Geode unicast UDP messaging

Data Node

Master Node

20002-20010

TCP

Geode TCP inter-node failure detection & peer-to-peer TCP communication for Master Locator

Data Node

Master Node

20002-20010

UDP

Geode unicast UDP messaging for Master Locator

Data Node

Master Node

20002-20010

TCP

Geode TCP inter-node failure detection & peer-to-peer TCP communication for Replica Locator

Data Node

Master Node

20002-20010

UDP

Geode unicast UDP messaging for Replica Locator

Data Node

Master Node

5433

TCP

Communication with Postgres Central DB on Master Node

Data Node

Replica Node

5433

TCP

Communication with Postgres Central DB on Replica Node

Data Node

localhost

5432

TCP

Communication with Postgres HIS & Alarm DB

Data Node

Data Node

7001

TCP

Cassandra inter-node communication

Data Node

Data Node

9042

TCP

Cassandra client

Data Node

Master Node

123

UDP

NTP

Data Node

Replica Node

123

UDP

NTP

Port Information for Connectivity from Remote Collector

Connectivity from the remote collector within the same cluster.

Source

Destination

Port

Protocol

Service Description

Remote Collector

Master Node

6061

TCP

Communication with Geode Locator on Master

Remote Collector

Replica Node

6061

TCP

Communication with Geode Locator on Replica

Remote Collector

Data Node

10000

TCP

Communication with Geode server embedded in Analytics process

Remote Collector

Data Node

443

TCP

HTTPS

Remote Collector

Data Node

80

TCP

HTTP

Remote Collector

Master Node

123

UDP

NTP

Remote Collector

Replica Node

123

UDP

NTP

Internal Communications

The following components require internal communication.

Table 1. Communication Between Master Node and Replica Node

Component

Protocol

Port

Postgres Replica Database

TCP

5433

Table 2. Communication Between Analytics Nodes

Component

Protocol

Port

HTTPS

TCP

443

Gemfire Locator

TCP

6061

Gemfire

TCP

10000

Gemfire

TCP

20000:20010

Cassandra (inter-node)

TCP

7001

Cassandra client

TCP

9042

Table 3. Communication From Remote Collector to Analytics Node

Component

Protocol

Port

HTTPS

TCP

443

Gemfire Locator

TCP

6061,

Gemfire

TCP

10000

Table 4. Communication Between Remote Collector and Analytics Node

Component

Protocol

Port

HTTPS (Casa)

TCP

443

Table 5. Communication Between Remote Collector and Master and Data Nodes

Component

Protocol

Port

HTTP

TCP

80

HTTPS

TCP

443

Gemfire Locator

TCP

6061

Gemfire

TCP and UDP

10000:10010

Gemfire

TCP and UDP

20000:20010

NTP

UDP

123

Table 6. Communication From End Point Operations Management Agent to Analytics Node

Component

Protocol

Port

HTTPS

TCP

443

Table 7. Communication From End Point Operations Management Agent to Remote Collector

Component

Protocol

Port

HTTPS

TCP

443

External Communications

The following components require external communications.

Table 8. Communication from Analytics Nodes and Remote Collectors to External Resources

Component

Protocol

Port

Platform Services Controller

TCP

443

DNS

TCP, UDP

53

LDAP

TCP

389

LDAPS

TCP

636

GC TCP

TCP

3268, 3269

NTP

UDP

123

SMTP

TCP

25

SNMP

UDP

161

Adapters

TCP

**

SSH

TCP

22

CIM (Common Information Model) Service

TCP

5898

From vCenter to vRealize Operations Manager

Component

Protocol

Port

Unicorn Service

REST

443

** Ports required for adapters to communicate with external devices vary based upon the requirements of the device. Consult adapter documentation for required ports.

Note:

vROPS requires a TCP connection over HTTP via Port 10433 to connect to vSphere 5.x when retrieving inventory tag information.

Note:

The user interface and administrative interface to vROPS Operations Manager are through Port 443 with a TCP connection. See the topic, Port Requirements for vRealize Operations Manager.