IBM Support

IT37427: crtdrprimary for a HA queue manager fails with AMQ3930E due to DR replication interfaces mismatch on the HA appliances

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

  • When adding a HA queue manager to a DR configuration(i.e.
    running
    crtdrprimary command) with different interfaces configured as DR
    replication interfaces on the HA appliances, the crtdrprimary
    command
    fails with error AMQ3930E.
    
    Example(using eth):
    
    Failure  : eth30 as DR interface on HA appliance 1 and eth31 as
    DR interface on HA appliance 2
    Success : eth30 or eth31  as DR interfaces on both HA appliance
    
    Example(using Ling Aggregation Interfaces):
    
    Failure  : LAG1 as DR interface on HA appliance 1 and LAG2 as DR
    interface on HA appliance 2
    Success : LAG1 or LAG2  as DR interfaces on both HA appliance
    
    MQ appliance has requirement that same interface should be used
    as DR interface for a HA
    queue manager on both HA appliances. This requirement is
    applicable only when the
    DR configuration is using floating IP. However the crtdrprimary
    for HA queue manager fails
    even when no floating IP is used for DR replication.
    

Local fix

  • Use the same 'Configuration name' for the custom link-agg DR
    replication interface.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    IBM MQ Appliance users configuring DR for a HA queue manager
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    An incorrect check in the crtdrprimary logic caused the command
    to incorrectly enforce a requirement which mandates same
    interface for DR replication on both HA appliances even when no
    floating IP was used.
    

Problem conclusion

  • The incorrect check in crtdrprimary command has been removed to
    resolve the problem.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.2 LTS   9.2.0.4
    v9.x CD    9.2.5
    
    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

    IT37427

  • 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

    2021-06-25

  • Closed date

    2021-10-19

  • Last modified date

    2021-10-19

  • 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

[{"Line of Business":{"code":"LOB36","label":"IBM Automation"},"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SS5K6E","label":"IBM MQ Appliance"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"920"}]

Document Information

Modified date:
20 October 2021