Configuring Firewalls
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 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 1–2 and Table 1–3 might be required by storage replication services such as the Availability Suite feature of Oracle Solaris software. See product documentation for details.
Table 1-2 Ports and Protocols Used by Geographic Edition Partnerships - 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
|
Intercluster 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
|
|
Table 1-3 Ports and Protocols Used by Geographic Edition Partnerships - Optional Services
|
|
|
|
161
|
TCP and UDP
|
Simple Network Management Protocol (SNMP) communications
|
|
162
|
TCP and UDP
|
SNMP traps
|
|