APAR status
Closed as program error.
Error description
In an environment with four MQ Appliances, where there are 2 different HA groups at different data centers and the queue managers on the first data center replicates to the appliances in the other site (DR site), the following steps were performed after disabling eth20 in both appliances at the DR site. mqa(mqcli)# makedrprimary -m QM1 The makedrprimary command succeeded. mqa(mqcli)# dltdrprimary -m QM1 The dltdrprimary command succeeded. mqa(mqcli)# sethagrp -i QM1 Removing high availability configuration on appliance 'MQAPPDR2'. AMQ6589W: Failed to remove high availability configuration on appliance 'MQAPPDR2'. The user should issue command 'dltmqm' on remote appliance 'MQAPPDR2' when it becomes available. AMQ6546E: An internal IBM MQ Appliance error has occurred. Review of the logs for 'sethagrp -i QM1' shows that it failed while checking the DRDB health. 2020-09-12 08:58:58.374157089-04:00:1234488: { Entering drbd_check_healthy 2020-09-12 08:58:58.377805562-04:00:1234488: drbdadm dump >/dev/null 2020-09-12 08:58:58.381669543-04:00:1234488: /etc/drbd.d/QM1_DR.res: in resource drbd_QM1_DR, on MQAPPDR1: IP 10.43.137.13 not found on this host. /etc/drbd.d/QM1_DR.res: in resource drbd_QM1_DR, on MQAPPDR1: IP 10.XX.YYY.ZZ not found on this host. 2020-09-12 08:58:58.383800099-04:00:1234488: rc(10) 2020-09-12 08:58:58.385892706-04:00:1234488: DRBD is not healthy! 2020-09-12 08:58:58.389488658-04:00:1234488: } Leaving drbd_check_healthy 113 2020-09-12 08:58:58.394011872-04:00:1234488: } Leaving createHAQM_pre 113 Although QM1 is a legitimate queue manager, it is not currently valid because it refer to a local IP address (10.XX.YYY.ZZ) that doesn't exist. The IP 10.XX.YYY.ZZ is the IP for eth20 on MQAPPDR1 which was disabled at the time of executing sethagrp.
Local fix
Enable eth20 before issuing sethagrp.
Problem summary
**************************************************************** USERS AFFECTED: Users using MQ Appliance for High Availability (HA) and Disaster Recovery (DR) Platforms affected: MultiPlatform **************************************************************** PROBLEM DESCRIPTION: The command used to validate DRDB health wasn't working when the interface used wasn't available.
Problem conclusion
The code has been modified to use a different command to validate DRDB health when the interface is absent. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v9.2 LTS 9.2.0.3 v9.x CD 9.2.2 The latest available maintenance can be obtained from 'WebSphere MQ Recommended Fixes' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037 If the maintenance level is not yet available information on its planned availability can be found in 'WebSphere MQ Planned Maintenance Release Dates' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309 ---------------------------------------------------------------
Temporary fix
Comments
APAR Information
APAR number
IT34493
Reported component name
MQ APPL M2002 V
Reported component ID
5737H4701
Reported release
920
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2020-10-09
Closed date
2021-06-30
Last modified date
2021-07-08
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
MQ APPL M2002 V
Fixed component ID
5737H4701
Applicable component levels
[{"Type":"MASTER","Line of Business":{"code":"LOB36","label":"IBM Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS5K6E","label":"IBM MQ Appliance"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]
Document Information
Modified date:
09 July 2021