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 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
You must configure the Geographic Edition software for secure communication between partner clusters. The configuration must be reciprocal, so cluster cluster-paris must be configured to trust its partner cluster cluster-newyorkand cluster cluster-newyork must be configured to trust its partner cluster cluster-paris.
If you are using the GUI to administer the Geographic Edition software, the root password must be the same on all nodes of both partner clusters.
For information about setting up security certificates for partner clusters, see Configuring Trust Between Partner Clusters.
For information about the example cluster configuration, see Example Geographic Edition Cluster Configuration.