IBM Support

IJ26654: CSM_RESYNC_NEEDED SHOWN IN MMHEALTH

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

  • The message should only show up if the
    communication between a node
    and the cluster manager.
    This triggers the events "csm_resync_needed"
    and "heartbeat_missing" to be shown erroneously.
    

Local fix

  • None, other than using the same
    software version throughout the cluster
    

Problem summary

  • The message should only show up if the
    communication between a node
    and the cluster manager.
    This triggers the events "csm_resync_needed"
    and "heartbeat_missing" to be shown erroneously.
    

Problem conclusion

  • Benefits of the solution:
    Less network traffic between the nodes,
    more accurate status for the mmhealth node
    and the mmhealth cluster
    
    Work Around:
    None, other than using the same
    software version throughout the cluster
    
    Problem trigger:
    If a node is on a newer software release
    than the cluster manager some events sent
    out to build the cluster health can not
    be handled when they report components which
    are not know to the cluster manager node.
    This will trigger retries which will fail
    triggering the events "csm_resync_needed"
    and "heartbeat_missing".
    A "mmhealth node show --resync" will not help
    but would just put load on the network.
    
    Symptom:
    Unexpected Results/Behavior
    
    Platforms affected:
    ALL Operating System environments
    
    Functional Area affected:
    System Health
    
    Customer Impact:
    If a customer follows the suggested action
    network traffic is created which gets
    noticeable depending on the size of the cluster.
    For clusters < 100 Nodes:
    Suggested: has little or no impact on customer operation
    For clusters > 100 Nodes:
    High Importance: an issue which will cause a
    degradation of the system in some manner,
    or loss of a less central capability
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ26654

  • 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

    2020-08-03

  • Closed date

    2020-08-03

  • Last modified date

    2020-08-03

  • 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

    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:
05 August 2020