Viewing RDQM and HA group status
We can view the status of the HA group and of individual replicated data queue managers (RDQMs).
We use the rdqmstatus command to view the status of individual RDQMs and of the HA group as a whole.
You must be a user in the mqm and haclient groups to run the rdqmstatus command. We can run the command on any of the three nodes.
Procedure
-
To view the status of a node and the RDQMs that are part of the HA configuration:
rdqmstatus
The identify of the node that you ran the command on and the status of the RDQMs in the HA configuration is displayed, for example:Node: mqhavm07.exampleco.com Queue manager name: RDQM8 Queue manager status: Running elsewhere HA current location: mqhavm08.exampleco.com Queue manager name: RDQM9 Queue manager status: Running elsewhere HA current location: mqhavm09.exampleco.com Queue manager name: RDQM7 Queue manager status: Running HA current location: This node
-
To view the status of the three nodes in the HA group, enter the following command:
rdqmstatus -n
The online or offline status of each node is reported. For example:Node mqha04(mqhavm04.example.com) is online Node mqha05(mqhavm05.example.com) is offline Node mqha06(mqhavm06.example.com) is online
-
To view the status of a particular queue manager on all the nodes in the HA group, enter the
following command:
rdqmstatus -m qmname
where qmname is the name of the RDQM you want to view the status for. The status of the RDQM on the current node is displayed, followed by a summary of the status of the other two nodes from the perspective of the current node.The following table summarizes the information about the current node that can be returned by the rdqmstatus command for an RDQM.
The following table summarizes the information that is returned by the rdqmstatus command for the other nodes in the HA group.Table 1. Current node status Status attribute Possible values When displayed Node name nodename Always displayed Queue manager status Running
Running elsewhere
Ended
UnavailableAlways displayed CPU n.nn% Only shown when current node has primary role (that is, the RDQM is running on this node) Memory nnnMB used, y.yGB allocated Only shown when current node has primary role (that is, the RDQM is running on this node) Queue manager file system nnnMB used, y.yGB allocated [z%] Only shown when current node has primary role (that is, the RDQM is running on this node) HA role Primary Secondary Unknown Always displayed HA status All nodes in standby
This node in standby
Remote nodes in standby
Mixed
status of remote nodes
All nodes in standby
Current node in standby
Both remote nodes in standby
Different status for each remote node (see next table for individual status)
Same status for both remote nodes (see next table for all values)HA control Enabled
Disabled
Unknown
Always displayed. Shows whether RDQM is under Pacemaker control HA preferred location None
This node
Unknown
nodenameAlways displayed HA floating IP interface Interface_name Always displayed HA floating IP address IPV4_address Always displayed Table 2. Other node status Status attribute Possible values When displayed Node name nodename
Always displayed HA status Normal
Synchronization in progress
Remote unavailable
Inconsistent
Paused
Remote node in standby
Unknown
Nodes are in sync with each other
Synchronizing with remote node
Unable to communicate with remote node
Out of sync with remote node, and not synchronizing
Replication paused
Remote node in standbyHA synchronization in progress n.n% Displayed when synchronization in progress, and command run as root HA estimated synchronization time yyyy-mm-dd hh:mm:ss.nnn Displayed when synchronization in progress HA out of sync data nKB Displayed when remote node unavailable or inconsistent
Example
Example of normal status on primary node:Node: mqhavm07.exampleco.com Queue manager status: Running CPU: 0.00 Memory: 123MB Queue manager file system: 606MB used, 1.0GB allocated [60%] HA role: Primary HA status: Normal HA control: Enabled HA current location: This node HA preferred location: This node HA floating IP interface: Eth4 HA floating IP address: 192.0.2.4 Node: mqhavm08.exampleco.com HA status: Normal Node: mqhavm09.exampleco.com HA status: NormalExample of normal status on a secondary node:
Node: mqhavm08.exampleco.com Queue manager status: Running elsewhere HA role: Secondary HA status: Normal HA control: Enabled HA current location: mqhavm07.exampleco.com HA preferred location: mqhavm07.exampleco.com HA floating IP interface: Eth4 HA floating IP address: 192.0.2.4 Node: mqhavm07.exampleco.com HA status: Normal Node: mqhavm09.exampleco.com HA status: Normal
Example of status on primary node when synchronization is in progress:
Node: mqhavm07.exampleco.com Queue manager status: Running CPU: 0.53 Memory: 124MB Queue manager file system: 51MB used, 1.0GB allocated [5%] HA role: Primary HA status: Synchronization in progress HA control: Enabled HA current location: This node HA preferred location: This node HA floating IP interface: Eth4 HA floating IP address: 192.0.2.4 Node: mqhavm08.exampleco.com HA status: Synchronization in progress HA synchronization progress: 11.0% HA estimated time to completion: 2017-09-06 14:55:05 Node: mqhavm09.exampleco.com HA status: Synchronization in progress HA synchronization progress: 11.0% HA estimated time to completion: 2017-09-06 14:55:06Example of a primary node showing multiple states:
Node: mqhavm07.exampleco.com Queue manager status: Running CPU: 0.02 Memory: 124MB Queue manager file system: 51MB used, 1.0GB allocated [5%] HA role: Primary HA status: Mixed HA control: Enabled HA current location: This node HA preferred location: This node HA floating IP interface: Eth4 HA floating IP address: 192.0.2.4 Node: mqhavm08.exampleco.com HA status: Normal Node: mqhavm09.exampleco.com HA status: Inconsistent