Viewing DR RDQM status

You can view the status of all disaster recovery replicated data queue managers (DR RDQMs) on a node, or detailed information for a specified DR RDQM.

About this task

You use the rdqmstatus command to view the status of all DR RDQMs, or of individual RDQMs.

[MQ 9.3.0 Jun 2022] The summary status for a node also displays information about the DRBD kernel module that RDQM relies upon. When you upgrade RDQM, it is important to ensure that the correct version of the DRBD kernel module is installed for the version of RHEL kernel running on the system. The status displays the version of the OS kernel, the kernel version that the DRBD module was built for, the DRBD version, and the DRBD kernel module loaded status.

You must be a user in the mqm group to run the rdqmstatus command. You can run the command on either node of the DR RDQM pair.

Procedure

To view the summary status of all the DR RDQMs on a node, run the following command on that node:
```
rdqmstatus
```
The status of the DR RDQMs on the node is displayed, for example:
```
Node:                                   mqhavm07.exampleco.com
OS kernel version:                      3.10.0-1160.15.2
DRBD OS kernel version:                 3.10.0-1160
DRBD version:                           9.1.1
DRBD kernel module status:              Loaded

Queue manager name:                     DRQM8
Queue manager status:                   Ended immediately
DR role:                                Secondary

Queue manager name:                     DRQM7
Queue manager status:                   Running
DR role:                                Primary
```
The DRBD kernel module status is one of the following values:

Loaded

Indicates that the DRBD module has been loaded.

Partially loaded

Can occur when the DRBD module has been loaded, but does not function correctly due to a mismatch.

Not loaded

The DRBD module is not loaded. This can be displayed on a newly installed configuration, when no RDQM queue managers have yet been created.

Not installed

Indicates that either the DRBD module is not installed. or that IBM® MQ was unable to determine the OS kernel version of the DRBD module.

Previously installed version still loaded

This status can arise if a new DRBD module is installed while the existing DRBD module is running (that is, an RDQM queue manager is running). The newly installed module is reported in the status, but is not the module that is actually running.

To view the status of a particular RDQM, enter the following command:

rdqmstatus -m  qmname

The following table summarizes the information that is returned.

Table 1. Status attributes
Status Attribute	Possible Values	When Displayed
Queue manager status	state (as displayed by `dspmq`)	Always displayed
CPU	`n`.`nn`%	Only shown when RDQM on current node has primary role
Memory	`nnn`MB	Only shown when RDQM on current node has primary role
Queue manager file system	`nnn`MB used`,n`.`n`GB allocated [`n`%]	Only shown when RDQM on current node has primary role
DR role	Primary Secondary Unknown	Always displayed
DR Status	Normal	Normal operation
	Synchronization in progress	Synchronization is in progress
	Partitioned	The queue manager has been started on both nodes while the DR replication network is unavailable
	Remote system unavailable	The connection to the other node has been lost
	Inconsistent	A synchronization was in progress, but was interrupted
	Reverting to snapshot	The user has chosen to revert to the snapshot that was taken when the queue manager entered the Inconsistent state.
	Remote system not configured	The primary instance of the RDQM has been configured, but no secondary instance has been configured
	Failed negotiation	One of the nodes has been set to synchronous replication and the other to asynchronous replication
DR type	Synchronous or asynchronous	Always displayed
DR port	`port_number` (the TCP/IP port used to replicate the data for this queue manager)	Always displayed
DR local IP address	The local IP address this queue manager is replicating from for DR	Always displayed
DR remote IP address	The remote IP address this queue manager is replicating to for DR	Always displayed
DR out of sync data	`n`KB	Displayed when remote node unavailable or inconsistent
DR synchronization progress	`n`%	Displayed when synchronization is in progress
DR estimated time to completion	`YYYY`-`MM`-`DD` `HH`:`MM`:`SS`	Displayed when synchronization is in progress
Snapshot reversion progress	`n`%	Displayed when DR status is `Reverting to snapshot`. The status counts down, so 0% shows completion
DR last in sync	`YYYY`-`MM`-`DD` `HH`:`MM`:`SS`	Displayed when DR data is out of sync (after initial synchronization). Gives the time and date when the data was last in sync.

Example

Example of normal status on primary node:

Queue manager status:                   Running
CPU:                                    0.00
Memory:                                 123MB
Queue manager file system:              51MB used, 1.0GB allocated [5%]
DR role:                                Primary
DR status:                              Normal
DR type:                                Synchronous
DR port:                                3000
DR local IP address:                    192.168.20.1
DR remote IP address:                   192.168.20.2

Example of normal status on a secondary node:

Queue manager status:                   Ended immediately
DR role:                                Secondary
DR status:                              Normal
DR port:                                3000
DR local IP address:                    192.168.20.2
DR remote IP address:                   192.168.20.1

Example of status on primary node when synchronization is in progress:

Queue manager status:                   Running
CPU:                                    0.53
Memory:                                 124MB
Queue manager file system:              51MB used, 1.0GB allocated [5%]
DR role:                                Primary
DR status:                              Synchronization in progress
DR type:                                Synchronous
DR port:                                3000
DR local IP address:                    192.168.20.1
DR remote IP address:                   192.168.20.2
DR synchronization progress:            11.0%
DR estimated time to completion:        2017-09-06 14:55:05

Example of a primary node, showing it is partitioned:

Queue manager status:                   Running
CPU:                                    0.02
Memory:                                 124MB
Queue manager file system:              51MB used, 1.0GB allocated [5%]
DR role:                                Primary
DR status:                              Partitioned
DR type:                                Synchronous
DR port:                                3000
DR local IP address:                    192.168.20.1
DR remote IP address:                   192.168.20.2

Example of a primary node, showing it is out of sync with the secondary node:

Queue manager status:                   Running
CPU:                                    0.00
Memory:                                 123MB
Queue manager file system:              51MB used, 1.0GB allocated [5%]
DR role:                                Primary
DR status:                              Remote unavailable
DR type:                                Asynchronous
DR port:                                3000
DR local IP address:                    192.168.20.1
DR remote IP address:                   192.168.20.2
DR out of sync data:                    15932KB
DR last in sync:                        2020-07-27 16:01:47

Example of a summary status showing a mismatch between the OS kernel version (RHEL 7.9) and the DRBD kernel module (targeted for RHEL 7.8). Even though the status reports that DRBD kernel module is loaded and the expected queue manager is running, you should update DRBD kernel module with the version targeted for the running OS kernel in this situation.

Node:                                   mqhavm07.exampleco.com
OS kernel version:                      3.10.0-1160.15.2
DRBD OS kernel version:                 3.10.0-1127
DRBD version:                           9.1.1
DRBD kernel module status:              Loaded
 
Queue manager name:                     DRQM8
Queue manager status:                   Ended immediately
DR role:                                Secondary

Queue manager name:                     DRQM7
Queue manager status:                   Running
DR role:                                Primary

Example of a summary status showing a mismatch between the OS kernel version (RHEL 7.9) and the DRBD kernel module (targeted for RHEL 7.6). In this example the version mismatch is more severe and DRBD kernel module fails to load successfully. QM3 is a DR queue manager and is meant to be the Primary instance, but since the DRBD kernel module did not fully load, it reports as Secondary with a DR status of Unknown. To resolve this failure the DRBD kernel module must be updated with the version target for the running OS kernel.

Node:                                   mqhavm57.exampleco.com
OS kernel version:                      3.10.0-1160.15.2
DRBD OS kernel version:                 3.10.0-957
DRBD version:                           9.1.2+ptf.3
DRBD kernel module status:              Partially loaded

Queue manager name:                     QM3
Queue manager status:                   Status not available
DR role:                                Secondary
DR status:                              Unknown