IBM Support

IT17481: ERROR "REMOTE APPLIANCE(S) UNAVAILABLE" ENCOUNTERED IN HA-DR NETWORK BY APPLIANCE THAT GETS SUSPENDED FROM HA GROUP.

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

  • Disaster Recovery (DR) primary and secondary queue managers are
    not getting asynchronously replicated on an appliance which is
    part of an HA group after that appliance gets suspended from
    the HA group.  Once that appliance resumes the HA state, the
    asynchronous replication works.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of the MQ Appliance who have configured
    queue managers to be part of a DR and HA group and who have
    suspended the appliance from the HA group.
    
    This issue is more likely to be encountered if all of the
    appliance's HA and DR interfaces are defined on the same subnet,
    or if the appliance hosts multiple DR/HA queue managers.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    A logic error within the crtdrsecondary command could
    incorrectly cause the wrong IP address to be recorded in the DR
    configuration. In this scenario, the IP address recorded was a
    temporary address owned by the current DR/HA primary, rather
    than the permanent address of the adapter.
    
    This then caused failures to establish the DR link when the
    appliance was suspended from the HA group, as the temporary
    address ceased to be valid.
    

Problem conclusion

  • The crtdrsecondary command has been updated to correct this
    issue.
    
    If the issue has been encountered, then it is necessary to
    re-run the crtdrprimary and crtdrsecondary commands after
    applying this fix, in order to correct the saved DR
    configuration on the appliances.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.0.6
    
    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

    IT17481

  • Reported component name

    IBM MQ APPL M20

  • Reported component ID

    5725S1400

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-10-13

  • Closed date

    2016-12-19

  • Last modified date

    2017-03-10

  • 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

    5725S1400

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:
10 March 2017