Geo-redundancy ports in a cloud deployment

Edit online

Learn which ports to open between clusters in geographically distinct areas in a full cloud deployment.

The table lists the ports to open for a full cloud geo-redundant deployment:
Table 1. Geo-redundancy ports for a cloud deployment
Cluster location Exposed port Service name Target port Description Type
Primary 16311 <release_name>-webgui-primary-0 16311 Incoming connection into primary webgui pod Incoming
Backup 16311 <release_name>-webgui-backup-0 16311 Incoming connection into backup webgui pod Incoming
Primary 4100 <release_name>-objserv-agg-primary 4100 Incoming primary ObjectServer port Incoming
Primary 4101 <release_name>-objserv-agg-primary 4101 Primary ObjectServer Insert Delete Update Control (IDUC) port Incoming
Backup 4100 <release_name>-objserv-agg-backup 4100 Incoming backup ObjectServer port Incoming
Backup 4101 <release_name>-objserv-agg-backup 4101 Backup ObjectServer IDUC port Incoming
Primary N/A   4100   Outgoing
Primary 8888 <release_name>-ibm-ea-dr-coordinator-service-eacoordinator 8080 External port for the DR coordinator Incoming
Backup 8888 <release_name>-ibm-ea-dr-coordinator-service-eacoordinator 8080 External port for the DR coordinator Incoming
Primary and Backup 9081 <release_name>-nciserver-0 9081 SOAP and nameserver port Incoming
Primary and Backup 4851 <release_name>-nciserver-0 4851 Derby replication port Incoming
Primary and Backup 1527 <release_name>-nciserver-0 1527 Derby connection port Incoming
Primary and Backup 3000 <release_name>-nciserver-0 3000 RMI server port Incoming
Primary and Backup 3001-3100 <release_name>-nciserver-0 3001-3100 RMI client port Incoming