Sun Cluster Geographic Edition partner clusters communicate using transport services and ICMP echo requests and replies (pings). Their packets must therefore pass data center firewalls, including any firewalls configured on cluster nodes in partner clusters. The table below contains a list of required and optional services and protocols used by Sun Cluster Geographic Edition partnerships, and the associated ports that you must open in your firewalls for these services to function. The ports listed are defaults, so if you customize the port numbers serving the specified transfer protocols, the customized ports must be opened instead.
Ports other than those listed in Table 4–2 might be required by storage replication services such as the Sun StorageTek Availability Suite product. See product documentation for details.
Table 4–2 Ports and Protocols Used by Sun Cluster Geographic Edition Partnerships
Port Number |
Protocols |
Use in Sun Cluster Geographic Edition partnership |
---|---|---|
Required Services |
||
22 |
UDP and TCP |
Secure shell (ssh). Used during the initial certificate transfer that establishes trust between partner clusters. |
2084 |
UDP (default), TCP |
Inter-cluster heartbeat |
11162 |
TCP |
The Java Management Extensions (JMX) port (jmxmp-connector-port). A messaging protocol used for the exchange of configuration and status information between the two sites in a partnership. |
- |
ICMP Echo Request/Reply |
Backup heartbeat between partner clusters |
Optional Services |
||
161 |
TCP and UDP |
Simple Network Management Protocol (SNMP) communications |
162 |
TCP and UDP |
SNMP traps |
6789 |
TCP and UDP |
The Sun Cluster Manager GUI |