This section provides procedures to create a Geographic Edition partnership between two clusters.
Before You Begin
Ensure that the following conditions are met:
The cluster on which you want to create the partnership is up and running.
If a partner cluster is a zone cluster, either application-based replication such as, Oracle Data Guard, or EMC Symmetrix Remote Data Facility storage-based replication is configured or no data replication is used.
The geoadm start command must have already been run on the this cluster and the partner cluster. For more information about using the geoadm start command, see Enabling the Geographic Edition Framework.
The cluster name of the partner cluster is known.
The host information of the partner cluster must defined in the local host file. The local cluster needs to be able to reach the partner cluster by name.
Security has been configured on the two clusters by installing the appropriate certificates. See Configuring Trust Between Partner Clusters for more information.
You must be assigned the Geo Management RBAC rights profile to complete this procedure. For more information about RBAC, see Securing Geographic Edition Software.
local-partner-cluster# geops create -c remote-partner-cluster[.domain-name] [-h heartbeat] \ [-p property-setting [-p…]] partnership
Specifies the name of the remote cluster that will participate in the partnership. If clusters in the partnership are in different domains, you must also specify the domain name of the remote cluster.
This name matches the logical hostname used by the Geographic Edition framework on the remote cluster.
Specifies a custom heartbeat to use in the partnership to monitor the availability of the partner cluster.
If you omit this option, the default Geographic Edition heartbeat is used.
Custom heartbeats are provided for special circumstances and require careful configuration. Consult your Oracle specialist for assistance if your system requires the use of custom heartbeats. For more information about configuring custom heartbeats and custom heartbeat plug-ins, see Chapter 5, Administering Heartbeats and Heartbeat Plug-Ins in Oracle Solaris Cluster 4.3 Geographic Edition System Administration Guide.
If you create a custom heartbeat, you must add at least one plug-in to prevent the partnership from remaining in degraded mode.
You must configure the custom heartbeat that you provide in this option before you run the geops command.
Specifies the value of partnership properties with a string of property=value pair statements.
Specify a description of the partnership with the Description property.
You can configure heartbeat-loss notification with the Notification_emailaddrs and Notification_actioncmd properties. For more information about configuring heartbeat-loss notification, see Configuring Heartbeat-Loss Notification in Oracle Solaris Cluster 4.3 Geographic Edition System Administration Guide.
For more information about the properties you can set, see Appendix A, Standard Geographic Edition Properties, in Oracle Solaris Cluster 4.3 Geographic Edition System Administration Guide.
Specifies the name of the partnership.
For information about the names and values that are supported by the Geographic Edition framework, see Legal Names and Values of Geographic Edition Entities in Oracle Solaris Cluster 4.3 Geographic Edition System Administration Guide.
For more information about the geops command, refer to the geops (1M) man page.
The partnership states will be Degraded and the heartbeat state will be Offline. These states will change after the partnership is joined from the partner cluster.
local-partner-cluster# geoadm status
This example creates the paris-newyork-ps partnership on the cluster-paris.usa cluster.
cluster-paris.usa1# geops create -c cluster-newyork.usa \ -p Description=Transatlantic \ -p Notification_emailaddrsemail@example.com \ paris-newyork-psExample 3 Creating a Partnership That Uses a Custom Heartbeat and a Custom Heartbeat Plug-In
This example creates the heartbeat paris-to-newyork, creates the custom heartbeat plug-in command1 and adds it to the custom heartbeat, creates a the partnership paris-newyork-ps to use the custom heartbeat, and verifies the partnership status.
# geohb create -r cluster-newyork paris-to-newyork # geohb add-plugin command1 paris-to-newyork -p Query_cmd=/usr/bin/hb/ # geops create -c cluster-newyork -h paris-to-newyork paris-newyork-ps # geoadm status
To finalize the new partnership, the remote partner cluster must join the partnership. Go to Joining an Existing Partnership.
To remove a partnership between two clusters, see How to Remove Trust Between Two Clusters in Oracle Solaris Cluster 4.3 Geographic Edition System Administration Guide.