Monitoring the Runtime Status of the Geographic Edition Framework

Language:

You can display the runtime status of the local Geographic Edition enabled cluster by using the geoadm status command. This command displays output that is organized in the following sections:

Cluster – Provides the name of the local cluster
Partnership – Provides information about all partnerships, including the name of the partner cluster, the synchronization state, the local heartbeats, and the local heartbeat plug-in
Protection group – Provides information about the status of protection groups, including information about the local cluster and the remote cluster
Site – Provides information about all sites, including the names of the sites, the name and role of each site cluster, site heartbeat, and site heartbeat plug-in,
Multigroup – Provides information about all multigroups, including the names of the multigroups, the name of associated sites, and synchronization status
Pending operations – Provides status information about any ongoing transaction processes

You must be assigned the Basic Solaris User rights profile to run the geoadm status command. For more information, see Securing Geographic Edition Software in Oracle Solaris Cluster 4.3 Geographic Edition Installation and Configuration Guide.

The following example shows sample output when an administrator runs the geoadm status command on the cluster-paris cluster.

phys-paris-1# geoadm status

   Cluster:  cluster-paris

   Partnership "paris-newyork-ps": OK
        Partner clusters        : cluster-newyork
        Synchronization         : OK
        ICRM Connection         : OK

        Heartbeat "paris-to-newyork" monitoring "cluster-newyork": OK
             Plug-in "ping_plugin"      : Inactive
             Plug-in "tcp_udp_plugin"   : OK

   Protection group "tcpg"       : OK
        Partnership             : paris-newyork-ps
        Synchronization         : OK

        Cluster cluster-paris   : OK
             Role               : Primary
             Activation state   : Deactivated
             Configuration      : OK
             Data replication   : OK
             Resource groups    : None

        Cluster cluster-newyork : OK
             Role               : Secondary
             Activation state   : Deactivated
             Configuration      : OK
             Data replication   : OK
             Resource groups    : None

   Protection group "testpg"    : OK
        Partnership             : paris-newyork-ps
        Synchronization         : OK

        Cluster cluster-paris   : OK
             Role               : Primary
             Activation state   : Deactivated
             Configuration      : OK
             Data replication   : OK
             Resource groups    : None

        Cluster cluster-newyork : OK
             Role               : Secondary
             Activation state   : Deactivated
             Configuration      : OK
             Data replication   : OK
             Resource groups    : None

   Site : site1

        Controller "cluster-paris"      
             Configuration       : OK

        Controller "cluster-madrid"     
             Configuration       : OK
             Synchronization     : OK

             Heartbeat "paris-to-madrid~site1~cluster-madrid" monitoring "cluster-madrid": OK
                  Plug-in "tcp_udp_plugin"   : OK

        Member "cluster-london"        
             Configuration       : OK
             Synchronization     : OK

             Heartbeat "paris-to-london~site1~cluster-london" monitoring "cluster-london": OK
                  Plug-in "tcp_udp_plugin"   : OK

   Multigroup "mg2"     :
        Site            : site1
        Configuration   : OK
        Synchronization with cluster cluster-madrid      : OK
        Synchronization with cluster cluster-london     : OK

   Multigroup "mg1"     :
        Site            : site1
        Configuration   : OK
        Synchronization with cluster cluster-madrid      : OK
        Synchronization with cluster cluster-london     : OK

Pending operations:

Protection group "tcpg" operation: Start

Pending multigroup operations:

Multigroup "mg1" operation: Start

The information displayed shows that the protection group, tcpg, is started on both the primary cluster, cluster-paris, and the secondary cluster, cluster-newyork. Data is replicating between the partner clusters and both partners are synchronized.

The following table describes the meaning of the status values.

Table 5 Status Value Descriptions

Field	Value Descriptions
`Partnership`	`OK` – The partners are connected. `Error` – The connection between the partner clusters is lost. `Degraded` – The partnership has been successfully created but a connection with the partner cluster has not yet been established. This status value occurs when the partnership has been created and the partner cluster has not been configured.
`Synchronization`	`OK` – The configuration information is synchronized between partner clusters. `Error` – The configuration information differs between the partner clusters. You need to resynchronize the partnership for a partnership synchronization error, or resynchronize the protection group for a protection group synchronization error. For information about resynchronizing a partnership, see Resynchronizing a Partnership. For information about resynchronizing a protection group, see Resynchronizing a Protection Group. `Mismatch` – Configuration information has been created separately on the clusters. The configuration information must be replaced by a copy of the configuration information from the partner cluster. You can synchronize the protection group configuration by using the `geopg get` command. `Unknown` – Information is not accessible because the partners are disconnected or because some components of the protection group cannot be reached.
`ICRM Connection`	`OK` – The Intercluster Resource Management (ICRM) module is running properly. `Error` – The ICRM module on the local cluster is unable to communicate with the ICRM module on the remote cluster.
`Heartbeat`	`OK` – Heartbeat checks are running and the partner cluster responds within the specified timeout and retry periods. `Offline` – Heartbeat checks are not running. `Error` – Heartbeat checks are running but the partner is not responding and retries have timed out. `Degraded` – Heartbeat checks are running but one of the primary heartbeat plug-ins is degraded or is not running.
`Heartbeat plug-in`	`OK` – Responses are being received from the partner. `Inactive` – Plug-in is not in use but is a standby for retrying to contact the partner if the other plug-ins obtain no response. `No-Response` – Partner cluster is not responding.
`Protection group` (overall protection group state)	`OK` – No component of the protection group on either partner is in the Degraded, Error, or Unknown status, and the protection group configuration is the same on both partner clusters. `Degraded` – Data replication is either not running or is in a partial error state. `Error` – At least one component of the partnership is in an error state on at least one partner, or the protection group configuration is different between the partner clusters. `Unknown` – The status for at least one component of the protection group is unknown, or the status of the protection group is not accessible.
`Protection group` > `Synchronization` (state of protection group configuration information between partner clusters)	`OK` – The configuration is synchronized between partner clusters. `Error` – The configuration on the partner clusters is different. You must synchronize the protection group again. `Mismatch` – The protection group has been configured on each partner cluster individually. You must remove the configuration from one cluster and copy the configuration of the partner cluster. `Unknown` – Information is not accessible because the partners are disconnected.
`Protection group` > `Cluster` (state of protection group on each cluster)	`None` – The data replication or resource group component is not configured in the protection group. `OK` – The state of all the protection group components, such as configuration data, data replication, or resource groups, is `OK`, `NONE`, or `N/A` on the cluster. `Degraded` – The state of one or more of the protection group components is in the `Degraded` state on the cluster. `Error` – The state of some components of the protection group, such as configuration data, data replication, or resource groups, is in `Error`. `Unknown` – The state of some components of the protection group, such as configuration data, data replication, or resource groups, is unavailable.
`Protection group` > `Cluster` > `Role`	`Primary` – The cluster is the primary cluster for this protection group. `Secondary` – The cluster is the secondary cluster for this protection group. `Unknown` – Information is not accessible because the partners are disconnected or because some components of the protection group cannot be reached.
`Protection group` > `Cluster` > `Activation state`	`Activated` – The protection group is activated. `Deactivated` – The protection group is deactivated. `Unknown` – Information is not accessible because the partners are disconnected or because some components of the protection group cannot be reached.
`Protection group` > `Cluster` > `Configuration`	`OK` – Protection group configuration has been validated without errors on the cluster. `Error` – Protection group configuration validation resulted in errors on the cluster. You need to revalidate the protection group. For information about validating a protection group, see Validating a Protection Group in Oracle Solaris Cluster 4.3 Geographic Edition Installation and Configuration Guide. `Unknown` – Information is not accessible because the partners are disconnected or because some components of the protection group cannot be reached.
`Protection group` > `Cluster` > `Data replication`	`None` – Data replication is not configured. `OK` – Data replication is running and data is synchronized with the partner cluster when the protection group is activated. Replication is suspended when the protection group is deactivated. This state represents data replication on this cluster and does not reflect the overall state of data replication. This state is mapped from the corresponding state in the data replication subsystem. `Degraded` – Data is not replicated and not synchronized with the partner cluster when the protection group is activated. New writes will succeed but not be replicated. This state represents data replication on this cluster and does not reflect the overall state of data replication. This state is mapped from the corresponding state in the data replication subsystem. `Error` – Data replication from the primary cluster to the secondary cluster is in error if the data replication subsystem reports an error or if data replication is not suspended when the protection group is deactivated. This state represents data replication on this cluster and does not reflect the overall state of data replication. This state is mapped from the corresponding state in the data replication subsystem. `Unknown` – Information is not accessible because the partners are disconnected or because some components of the protection group cannot be reached. `N/A` – The data replication state of the protection group could not be mapped. Data replication is in a valid state on its own but in an `Error` state for the protection group. This state is available only if you are using Availability Suite data replication.
`Protection group` > `Cluster` > `Resource groups`	`None` – No resource group is protected by this protection group. `OK` – If the cluster has the `Primary` role, all resource groups are online when the protection group is activated or unmanaged when the protection group is deactivated. If the cluster has the `Secondary` role, all resource groups are unmanaged. `Error` – If the cluster has the `Primary` role, not all resource groups are online when the protection group is activated or unmanaged when the protection group is deactivated. If the cluster has the `Secondary` role, not all resource groups are unmanaged. `Unknown` – Information is not accessible because the partners are disconnected or because some components of the protection group cannot be reached.
`Site` > `Controller` or `Member` > `Configuration`	`OK` – The site configuration is correct. `Error` – The site configuration has an error. `Unknown` – The site configuration is not checked.
`Site` > `Controller` or `Member` > `Synchronization`	`DIFFERENT` – Site configuration information on two compared clusters is different but compatible. This is a transitory status. Eventually, the older of the two configurations is automatically synchronized with the newer configuration, at which time the synchronization status becomes OK. If for some reason the status remains at DIFFERENT, use the `geosite validate` subcommand to synchronize the site configurations. `ERROR` – The site configuration on two compared clusters is different and cannot be automatically resolved. Configuration changes from an issuing controller cluster are not accepted by a cluster while it is in the ERROR synchronization status with the issuing controller. If configuration information between two clusters do not resolve automatically and the clusters are in the ERROR status, use the `geosite update` subcommand to resolve site configuration conflicts between the two clusters. `OK` – Site configuration information matches on the compared clusters. `UNKNOWN` – Site configuration information cannot be compared because the Geographic Edition framework cannot reach a cluster. Configuration changes from an issuing controller cluster are not propagated to a cluster while it is in the UNKNOWN synchronization status. If the cluster is not automatically synchronized, use the `geosite validate` subcommand to update the cluster with the latest site configuration information.
`Site` > `Controller` or `Member` > `Heartbeat`	`OK` – Heartbeat monitoring is enabled, and the partner cluster is responding within timeout and retry periods. `Degraded` – Heartbeat checks are running but one of the primary heartbeat plug-ins is degraded or is not running. `Error` – Heartbeat monitoring is running but the partner cluster is not responding and retries have timed out. `Offline` – Heartbeat monitoring is offline.
`Site` > `Controller` or `Member` > `Heartbeat` > `Plug-in`	`OK` – The partner cluster is responding. `Inactive` – 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. `No-response` – The partner cluster is not responding.
`Multigroup` > `Configuration`	`OK` – The configuration of the multigroup is correct and validated without errors. `Error` – The configuration of the multigroup has errors. Run the `geomg validate` command on the multigroup to identify the error. `Unknown` – The configuration is not accessible.
`Multigroup` > `Synchronization`	`DIFFERENT` – Multigroup configuration information on two compared clusters is different but compatible. This is a transitory status. Eventually, the older of the two configurations is automatically synchronized with the newer configuration, at which time the synchronization status becomes OK. If for some reason the status remains at DIFFERENT, use the `geomg validate` command to synchronize the multigroup configurations. `ERROR` – The multigroup configuration on two compared clusters is different and cannot be automatically resolved. Configuration changes from an issuing controller cluster are not accepted by a cluster while it is in the ERROR synchronization status with the issuing controller. If configuration information between two clusters do not resolve automatically and the clusters are in the ERROR status, use the `geomg update` command to resolve multigroup configuration conflicts between the two clusters. `OK` – Multigroup configuration information matches on the compared clusters. `UNKNOWN` – Multigroup configuration information cannot be compared because the Geographic Edition framework cannot reach a cluster. Configuration changes from an issuing controller cluster are not propagated to a cluster while it is in the UNKNOWN synchronization status. If the cluster is not automatically synchronized after the Geographic Edition framework is started on that cluster, use the `geomg validate` command to update the cluster with the latest multigroup configuration information.