NAME | SYNOPSIS | DESCRIPTION | SUBCOMMANDS | OPTIONS | EXTENDED DESCRIPTION | EXIT STATUS | ATTRIBUTES | SEE ALSO
Checking whether the Sun Cluster Geographic Edition infrastructure is enabled on the local cluster.
geoadm showEnabling the Sun Cluster Geographic Edition infrastructure on the local cluster.
geoadm startDisplaying the runtime status of the Sun Cluster Geographic Edition entities on the local cluster.
geoadm statusDisabling the Sun Cluster Geographic Edition infrastructure on the local cluster.
geoadm stop [--cleanup] [--force]Displaying version information.
geoadm --versionDisplaying help information.
geoadm --helpThe geoadm command enables or disables the Sun Cluster Geographic Edition infrastructure on the local cluster. This command can also be used to check whether the Sun Cluster Geographic Edition software is enabled on the cluster.
After installation, the Sun Cluster Geographic Edition product must be enabled by using the command geoadm start. This command enables the cluster to participate in partnerships and to host protection groups. The geoadm start command configures the highly available infrastructure that unlocks the Sun Cluster Geographic Edition module on the cluster.
The geoadm stop command stops the highly available infrastructure that leaves the Sun Cluster Geographic Edition module locked on the cluster. Use the geoadm stop command before removing product packages.
The geoadm stop command can successfully disable the Sun Cluster Geographic Edition module on a cluster only under one condition All local states of the protection groups in which the cluster is involved must be Offline or Unknown.
Running the geoadm start or the geoadm stop command on one node of the cluster affects the entire cluster.
To use the geoadm command to enable or disable the Sun Cluster Geographic Edition infrastructure, 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 the command that performs. Only one subcommand is allowed on the command line.
The following subcommands are supported:
Displays whether the Sun Cluster Geographic Edition software is enabled on the cluster.
Configures and enables the Sun Cluster Geographic Edition infrastructure on the cluster.
Displays the runtime status of the Sun Cluster Geographic Edition entities on the local cluster.
The Sun Cluster Geographic Edition software must be installed on the local cluster before you can use the status subcommand. You can use the status subcommand whether or not the cluster has been enabled for partnership.
The status subcommand displays the following information:
Whether the local cluster is enabled for partnership.
Whether the local cluster is involved in a partnership. If the cluster is involved in a partnership, the status subcommand lists all partnership members.
Heartbeat status.
Protection group status.
Status of ongoing transactions.
See the EXTENDED DESCRIPTION section for details about the possible values for each status.
Disables the Sun Cluster Geographic Edition infrastructure and configuration on the cluster.
All protection groups on the cluster must be in the Offline state to successfully use the stop subcommand.
The stop subcommand removes the cluster state and Sun Cluster Geographic Edition infrastructure resource groups on the cluster, but the stop subcommand does not remove data replication resource groups.
The Sun Cluster Geographic Edition infrastructure is enabled and configured again the first time you use the start subcommand after using the stop subcommand.
The following options are supported:
Specifies that the cluster should clean up the overall Sun Cluster Geographic Edition configuration. Cleaning up the configuration enables a cluster to restart with an empty configuration.
The --cleanup option removes the configuration for the Sun Cluster Geographic Edition entities such as partnerships, protection groups, and heartbeats from the cluster. If you enable the cluster again by using the geoadm start command, you must define new user-entity configuration information.
If you do not use the --cleanup option, the configuration tables of the entities that you have defined remain on the cluster.
Indicates that you want to bypass the command confirmation questions while the Sun Cluster Geographic Edition infrastructure is being disabled.
Displays version information. This option stops interpretation of subsequent arguments.
Displays help information. This option 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 sections list the status descriptions.
Partnership status displays status for the local cluster only. The partnership status can be one of the following:
The partner clusters are connected.
The partner clusters are disconnected.
Synchronization status displays status for all the clusters in a partnership. The partnership synchronization status can be one of the following:
The configuration is synchronized between partner clusters.
The configuration on the partner clusters is different. You must synchronize the partnership again.
The partner clusters have been configured individually. Therefore, you must delete the configuration on one cluster and copy the configuration of the partner cluster.
Information is not accessible because the partners are disconnected.
Heartbeat status displays status for a single cluster only. The heartbeat status can be one of the following:
Heartbeat monitoring is running, and the partner cluster is responding within timeout and retry periods.
Heartbeat monitoring is running, but the partner cluster is not responding and retries have timed out.
Heartbeat monitoring is not running.
Heartbeat plug-in status displays status for a single cluster only. The heartbeat plug-in status can be one of the following:
The partner cluster is responding.
The plug-in is not in use. It is a standby plug-in that is used for retrying if other plug-ins do not respond.
The partner cluster is not responding.
Protection group status displays the overall status for all the clusters in the protection group. The overall protection group status can be one of the following:
The protection group is online, application resource groups are online, and data replication is running.
The protection group is inactive.
The protection group and the application resource groups are online, but data replication is either not running or is in partial error state.
The protection group is online, but at least one component of the partnership, such as configuration, data replication, or resource groups, is in an error state.
The protection group is online, but the status for at least one component of the partnership, such as configuration, data replication, or resource groups, is unknown.
Protection group configuration status displays the status for a single cluster only. The protection group configuration status can be one of the following;
The protection group configuration has been validated without errors on the cluster.
The validation of the protection group configuration resulted in error. You must validate the protection group again.
Information is not accessible because the partner clusters are disconnected.
Data replication status displays the status of data replication that has been configured for the protection group on a single cluster. The protection group data replication status can be one of the following;
Data replication is configured, online, and running without errors.
Data replication is either off or in a partial error state.
Data replication is not operating because of an error.
Data replication has not been configured.
Information is not accessible because the partners are disconnected.
Resource group status displays the status of resource groups that have been configured for the protection group on a single cluster. The protection group resource group status can be one of the following;
All resource groups are online on the primary cluster, and all resource groups are offline or unmanaged on the secondary cluster.
Not all resource groups are online on the primary cluster, or not all resource groups are offline or unmanaged on the secondary cluster.
Information is not accessible because the partners are disconnected.
The following exit values are returned:
The command completed 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