IBM Support

IT22158: MQ appliance HA fails to initialise on reboot. Primary QM shows HA status partitioned,other QM shows unknown status

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • MQ appliance HA initialisation fails on appliance restart.
    Primary appliance shows HA status as partitioned and secondary
    as UNKNOWN
    
    on MQ appliance 1:
    
    mqa(mqcli)# status QM1
    QM(QM1)                                  Status(Running
    elsewhere)
    HA role:                                 UNKNOWN
    HA status:                               UNKNOWN
    HA control:                              Enabled
    HA preferred location:                   This appliance
    mqa(mqcli)# status QM2
    QM(QM2)                                  Status(Running
    elsewhere)
    HA role:                                 UNKNOWN
    HA status:                               UNKNOWN
    HA control:                              Enabled
    HA preferred location:                   Other appliance
    
    on MQ appliance 2:
    
    mqa(mqcli)# status QM1
    QM(QM1)                                  Status(Running)
    HA role:                                 Primary
    HA status:                               Partitioned
    HA control:                              Enabled
    HA preferred location:                   Other appliance
    QM(QM2)                                  Status(Running)
    HA role:                                 Primary
    HA status:                               Partitioned
    HA control:                              Enabled
    HA preferred location:                   This appliance
    
    Also  getting following message:
    
    mqa(mqcli)# makehaprimary QM1
    AMQ6682: The appliance could not be made the primary for the
    queuemanager.
    

Local fix

  • If any link aggregations are configured which are not required
    then deleting them can circumvent the problem.
    
    This is because link aggregations can take several seconds to
    initialise when an appliance is booted.  On appliances that have
    been configured with multiple link aggregations this can delay
    the allocation of the hostname and lead to the MQ HA subsystem
    being started before the hostname has been allocated.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users of IBM MQ Appliances who have appliances configured in a
    MQ HA group
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The problem occurred when the appliance was rebooted because of
    a coding defect which allowed the appliance to start the MQ HA
    subsystem before the appliance had resolved its hostname.
    

Problem conclusion

  • The MQ appliance startup code has been modified to wait for a
    hostname to be allocated before starting the MQ HA subsystem.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.0.8
    
    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

    IT22158

  • Reported component name

    IBM MQ APPL M20

  • Reported component ID

    5725Z0900

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-08-25

  • Closed date

    2017-09-05

  • Last modified date

    2017-09-05

  • 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

    IBM MQ APPL M20

  • Fixed component ID

    5725Z0900

Applicable component levels

  • R800 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS5K6E","label":"IBM MQ Appliance"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
05 September 2017