IBM Support

IJ32813: "MMCHNODE --DAEMON-INTERFACE" COMMAND ON A WINDOWS NODE CAN RESULT IN CLUSTER CONFIGURATION ISSUES.

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

  • Issuing a "mmchnode --daemon-interface" attempts
    to change the cluster configuration
    repository (CCR). When this mmchnode is issued from
    a Windows node,  CCR gets
    committed with invalid IPv4 information,
    rendering the cluster in a non-working state.
    

Local fix

  • None.
    A manual CCR restore (mmsdrrestore --ccr-repair)
    may be necessary to restore
    the cluster to a working state.
    

Problem summary

  • Issuing a "mmchnode --daemon-interface" attempts
    to change the cluster configuration
    repository (CCR). When this mmchnode is issued from
    a Windows node,  CCR gets
    committed with invalid IPv4 information,
    rendering the cluster in a non-working state.
    

Problem conclusion

  • Benefits of the solution:
    Prevent Cluster Configuration Repository (CCR) from
    getting corrupted with invalid IPv4 addresses.
    
    Work Around:
    None.
    A manual CCR restore (mmsdrrestore --ccr-repair)
    may be necessary to restore
    the cluster to a working state.
    
    Problem trigger:
    Issuing "mmchnode --daemon-interface"
    command on a Windows node specifying
    an alternate IPv4 address.
    
    Symptom:
    Error output/message:
    The mmchnode command fails with
    a message trail resembling:
    
    'mmchnode: Unable to commit new changes.'
    'mmchnode: [E] The command was unable to reach the
    CCR service on any quorum node.  Ensure the CCR service
    (mmfsd or mmsdrserv daemon) is running on all quorum
    nodes and the communication port is not blocked by the
    firewall.'
    'mmchnode: 6027-1271 Unexpected error from function
    setRunningCommand.  Return code: 149'
    
    Platforms affected:
    Windows/x86_64 only.
    
    Functional Area affected:
    CCR.
    
    Customer Impact:
    High Importance.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ32813

  • Reported component name

    SPEC SCALE STD

  • Reported component ID

    5737F33AP

  • Reported release

    505

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-05-26

  • Closed date

    2021-05-26

  • Last modified date

    2021-05-26

  • APAR is sysrouted FROM one or more of the following:

    IJ32554

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    SPEC SCALE STD

  • Fixed component ID

    5737F33AP

Applicable component levels

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"STXKQY","label":"IBM Spectrum Scale"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"505","Line of Business":{"code":"LOB26","label":"Storage"}}]

Document Information

Modified date:
27 May 2021