clRGinfo command
Purpose
Creates a report that displays the location and state of one or more specified resource groups.Syntax
clRGinfo [-h][-v][-s|-c][-t][-p][-a][-m][i][resgroup1] [resgroup2]...Description
If the cluster services are not running on the local node, this clRGinfo command identifies a node where the cluster services are active and obtains the resource group information from the active cluster manager. If this command is used without any resource groups that are specified, the information about all the configured resource groups is displayed.
The output of the command displays both the global state of the resource group and the special state of the resource group on the local node.
The primary instance of a resource group can be in one of the following states:
- Online
- All resources for this resource group are active.
- Error
- An error occurred while PowerHA® SystemMirror® was processing the resource group.
- Unmanaged
- Cluster services were stopped with the unmanage option.
- Offline
- The resource group is not active.
A resource group can be in the following transitional state while cluster events
are in progress:
- Acquiring
- Resources for the resource group are being activated.
- Releasing
- Resources for the resource group are being released.
- Temp error
- A recoverable error occurred.
When a cluster uses sites and replicated resources, the resource group that
contains the replicated resources has a primary and secondary instance that manages the replication
end points. The clRGinfo command displays the following states for the secondary
instance of a resource group:
- Online secondary
- All secondary resources for this resource group are active.
- Error secondary
- An error occurred while PowerHA SystemMirror was processing the secondary resources for a resource group.
- Unmanaged secondary
- Cluster services were stopped with the unmanage option.
- Offline secondary
- The secondary instance of a resource group is not active.
- Acquiring secondary
- The secondary resources for the resource group are being activated.
- Releasing secondary
- The secondary resources for the resource group are being released.
- Temp error secondary
- A recoverable error occurred while PowerHA SystemMirror was processing the secondary resources for a resource group.
Resource groups can be configured with dependencies that enable automatic
placement and management of resource groups in relationship to other resource groups. The
clRGinfo command displays the following states for resource groups with parent
and child relationships and for resource groups that have location dependencies:
- Offline due to parent offline
- The child resource group is not active because the parent resource group is not active.
- Offline due to fallover
- A fallover occurred and the resource group is not active.
- Offline due to lack of node
- The resource group is not identified to a node in the cluster.
- Offline due to target offline
- The resource group that is involved in the relationship with a resource group is not active, and the configured dependencies dictate that this resource group must not be active.
Flags
- -a
- Displays the current location of a resource group and its destination after a cluster event. Use this flag in pre-event and post-event scripts, especially in PowerHA SystemMirror clusters that have dependent resource groups. When PowerHA SystemMirror processes dependent resource groups, multiple resource groups can be moved at once with the rg_move event.
- -c
- Displays the output in a colon-separated format.
- -h
- Displays the usage message.
- -i
- Displays any administrator directed online or offline operations.
- -m
- Displays the status of the application.
- -p
- Displays the priority override location information for a resource group.
- -s
- Displays the output in a colon-separated format.
- -t
- Displays the delayed timer information, all delayed fallback timers, and settling timers that
are currently active on the local node.Note: You can only use this flag if the cluster manager is active on the local node.
- -v
- Displays the verbose output.
Examples
- The following example displays the report for running the clRGinfo command
without specifying any flag
parameters:
# clRGinfo ----------------------------------------------------------------------------- Group Name State Node ----------------------------------------------------------------------------- VS_DATA_RG ONLINE powerha53 ONLINE powerha54 ONLINE powerha63 ONLINE powerha64 VS_REDO_RG ONLINE powerha53 ONLINE powerha54 ONLINE powerha63 ONLINE powerha64 RG1 ONLINE powerha53 OFFLINE powerha54 ACQUIRING powerha63 OFFLINE powerha64 - The following example displays the report for running the clRGinfo command in
a cluster with sites.
# clRGinfo ----------------------------------------------------------------------------- Group Name State Node ----------------------------------------------------------------------------- OASTRG ONLINE als018022@site1 ONLINE SECONDARY alm194200@site2 VOTERG ONLINE als018022@site1 ONLINE SECONDARY alm194200@site2 - The following example displays the report for running the clRGinfo -m
command:
$ /usr/es/sbin/cluster/utilities/clRGinfo -m Group Name State Application state Node --------------------------------------------------------------- Group1 ONLINE ONLINE MONITORED merry Application state could be any one of the below possible values: OFFLINE ONLINE FAILED ONLINE FAILOVER ONLINE MONITORED ONLINE NOT MONITORED ONLINE MONITOR FAILED ONLINE MONITOR SUSPENDED - The following example displays the report for running the clRGinfo
-i command:
$ /usr/es/sbin/cluster/utilities/clRGinfo -i -------------------------------------------------------------------------------- Group Name State Application state Node -------------------------------------------------------------------------------- Rg1 ONLINE ONLINE STOPPED BY ADMINISTRATOR node1 INSTANCE_SAP OFFLINE node2 Application state could be any one of the below possible values: OFFLINE ONLINE FAILED ONLINE FAILOVER ONLINE MONITORED ONLINE NOT MONITORED ONLINE MONITOR FAILED ONLINE MONITOR SUSPENDED ONLINE STOPPED BY ADMINISTRATOR OFFLINE STARTED BY ADMINISTRATOR