JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris Cluster Geographic Edition System Administration Guide     Oracle Solaris Cluster 4.1
search filter icon
search icon

Document Information


1.  Introduction to Administering the Geographic Edition Software

2.  Before You Begin

3.  Administering the Geographic Edition Infrastructure

4.  Administering Access and Security

Geographic Edition Software and RBAC

Setting Up and Using RBAC

RBAC Rights Profiles

Modifying a User's RBAC Properties

Configuring Secure Cluster Communication Using Security Certificates

Configuring Firewalls

Configuring Secure Cluster Communication Using IPsec

How to Configure IPsec for Secure Cluster Communication

5.  Administering Cluster Partnerships

6.  Administering Heartbeats

7.  Administering Protection Groups

8.  Monitoring and Validating the Geographic Edition Software

9.  Customizing Switchover and Takeover Actions

10.  Script-Based Plug-Ins

A.  Standard Geographic Edition Properties

B.  Legal Names and Values of Geographic Edition Entities

C.  Disaster Recovery Administration Example

D.  Takeover Postconditions

E.  Troubleshooting Geographic Edition Software

F.  Deployment Example: Replicating Data With MySQL

G.  Error Return Codes for Script-Based Plug-Ins


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 4-2 and Table 4-3 might be required by storage replication services such as the Availability Suite feature of Oracle Solaris software. See product documentation for details.

Table 4-2 Ports and Protocols Used by Geographic Edition Partnerships - Required Services

Port Number
Use in Geographic Edition partnership
Secure shell (ssh). Used during the initial certificate transfer that establishes trust between partner clusters.
UDP (default), TCP
Intercluster heartbeat
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 4-3 Ports and Protocols Used by Geographic Edition Partnerships - Optional Services

Port Number
Use in Geographic Edition partnership
Simple Network Management Protocol (SNMP) communications
SNMP traps