| Skip Navigation Links | |
| Exit Print View | |
|
Oracle Solaris Cluster Geographic Edition System Administration Guide |
| Skip Navigation Links | |
| Exit Print View | |
|
|
Oracle Solaris Cluster Geographic Edition System Administration Guide |
1. Introduction to Administering the Geographic Edition Software
3. Administering the Geographic Edition Infrastructure
4. Administering Access and Security
Geographic Edition Software and RBAC
Modifying a User's RBAC Properties
Configuring Secure Cluster Communication Using Security Certificates
Configuring Secure Cluster Communication Using IPsec
How to Configure IPsec for Secure Cluster Communication
5. Administering Cluster Partnerships
7. Administering Protection Groups
8. Monitoring and Validating the Geographic Edition Software
9. Customizing Switchover and Takeover Actions
A. Standard Geographic Edition Properties
B. Legal Names and Values of Geographic Edition Entities
C. Disaster Recovery Administration Example
E. Troubleshooting Geographic Edition Software
F. Deployment Example: Replicating Data With MySQL
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 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 Oracle Solaris Cluster Geographic Edition Partnerships
| ||||||||||||||||||||||||||||||
|