NAME | SYNOPSIS | DESCRIPTION | SUBCOMMANDS | OPTIONS | EXTENDED DESCRIPTION | EXIT STATUS | ATTRIBUTES | SEE ALSO
Creating a partnership between the local cluster and remote clusters.
geops create --cluster remote-partner-cluster-name partnership-name [--heartbeat-name heartbeat-name] [--property property-setting [,...]]Joining a partnership.
geops join-partnership remote-cluster-name partnership-name [--heartbeat-name heartbeat-name]Leaving a partnership.
geops leave-partnership partnership-namePrinting partnership configuration information.
geops list partnership-nameModifying partnership properties.
geops set-prop partnership-name --property property-setting [,...]Resynchronizing a partnership.
geops update partnership-namePrinting version information.
geops --versionDisplaying help information.
geops --helpThe geops command enables you to create, configure, and manage the partnerships that are defined between clusters. A partnership is a pair of clusters that define a cluster infrastructure on which an application might be protected against disaster.
A partnership requires a running heartbeat between clusters. Partner clusters monitor each other with heartbeats.
The Sun Cluster Geographic Edition software notifies all remote partners of changes in the partnership configuration.
Use the geops command on a cluster that has been enabled for partnership.
To use the geops command to create, configure, and manage the partnerships, you must be assigned the proper role-based access control (RBAC) rights profile.
If you have root access, you have permissions to perform any operation. If you do not have root access, the following RBAC rights apply:
Basic Solaris User. You can read information about Sun Cluster Geographic Edition entities by using commands such as geoadm list, geohb list, and geops list.
Geo Management. You can perform all the read operations that someone with Basic Solaris User access can perform. You can also perform administrative and configuration tasks such as geohb add, geopg switchover, geoadm start, and geoadm stop.
For more information, see the rbac(5) man page and “Sun Cluster Geographic Edition Software and RBAC” in Sun Cluster Geographic Edition System Administration Guide.
Subcommands specify the actions that are performed by the command. Only one subcommand is allowed on the command line.
The following subcommands are supported:
Creates a partnership between the local cluster and a remote cluster.
Enables the local cluster to join an existing partnership.
Using the geops join-partnership command on a cluster that is already a member of a partnership causes the partnership configuration from the remote cluster to overwrite the partnership configuration of the local cluster.
If the remote partner cluster is down, modifications to the local cluster might not be propagated to the remote partner cluster.
Removes the local cluster from a partnership. This subcommand deletes the partnership when the last participating cluster in the partnership leaves.
Displays partnership configuration information.
Modifies the properties of a partnership. This subcommand updates the local cluster configuration and notifies remote partner clusters of the configuration change.
Updates partnership properties on a partner cluster while the cluster is disconnected from the partner cluster.
The following options are supported:
Specifies the logical hostname of the cluster with which to form a partnership. The logical hostname is used by the Sun Cluster Geographic Edition software and maps to the name of the remote partner cluster. For example, a remote partner cluster name might resemble the following:
cluster-paris
Specifies an identifier for the heartbeat on a partner cluster that the local cluster can use to monitor partner availability. You must create the heartbeat by using the geohb command before you specify the heartbeat in the geops command.
If this option is omitted, the Sun Cluster Geographic Edition software uses the default heartbeat mechanism between member clusters.
Specifies the value of partnership properties. You can specify multiple properties at one time by using multiple statements.
Using the geops join-partnership command on a cluster that is already a member of a partnership causes the partnership configuration from the partner cluster to overwrite the partnership configuration of the local cluster.
See the EXTENDED DESCRIPTION section for a description of the properties.
Specifies the name of the partnership.
Displays version information. This option stops interpretation of subsequent arguments.
Displays help information and stops interpretation of subsequent arguments.
The question mark might be interpreted as a special character by some shells. Use quotes (-"?") or an escape character to avoid pattern-matching.
The following section lists the partnership properties. These properties are set at creation and tunable at runtime.
Describes the partnership.
Optional property.
Type: String.
Default value: empty string.
Specifies the path to the script or command that is triggered when a heartbeat loss notification is issued.
Optional property.
Type: String.
Default value: Empty string.
Specifies the email address to send messages to when a heartbeat loss notification is issued. You can specify multiple email addresses by separating each email address with a comma.
Optional property.
Type: String array.
Default value: Empty string.
The Notification_EmailAddrss and the Notification_ActionCmd properties enable notification on heartbeat loss events. Heartbeat-loss events are detected locally on each cluster of the partnership, and the notification is triggered locally on the cluster where the event is detected. The email addresses and the notification action path should be valid on each cluster in the partnership.
The Sun Cluster Geographic Edition software enables you to specify a command to execute when a heartbeat-loss notification is issued. You can specify the path to the command by using the Notification_ActionCmd property. The command is executed with root permissions, so the file must have root ownership and execution permissions. If both properties have been configured, an email is sent after the command that is specified in the Notification_ActionCmd property is run.
The following exit values are returned:
The command executed successfully.
An error has occurred.
See attributes(5) for descriptions of the following attributes:
ATTRIBUTE TYPE |
ATTRIBUTE VALUE |
---|---|
Architecture |
SPARC |
Availability |
SUNWscgctl |
Interface Stability |
Evolving |
NAME | SYNOPSIS | DESCRIPTION | SUBCOMMANDS | OPTIONS | EXTENDED DESCRIPTION | EXIT STATUS | ATTRIBUTES | SEE ALSO