IJ29444: MMHEALTH SHOW DEGRADED STATUS DUE TO RECONNECT_START

APAR status

• Closed as program error.

Error description

• GPFS keeps in DEGRADED if reconnect_start is
  initialized by one IP but reconnection is established
  using another IP.
  
  The issue may happen when there are multiple connections
  between 2 nodes with different IPs. If one IP connection
  failed reconnect_start event is triggered and GPFS
  enters DEGRADED state. Later the state should change to
  HEALTHY after a reconnect_done/reconnection_aborted
  event is triggered. While if the reconnection is
  established using another IP then no
  reconnect_done/reconnection_aborted event is triggered
  so GPFS keeps in DEGRADED status.
  
  Reported In:
  Spectrum Scale 5.0.4.3
  

Local fix

• On the node reporting the issue run:
  mmsysmoncontrol restart
  

Problem summary

• After Node-B successfully reestablishes
  a broken connection to Node-A,
  Node-A still shows the reconnect_start
  state (DEGRADED).
  

Problem conclusion

• Benefits of the solution:
  No more incorrect node connect status.
  
  Work around:
  Restart the systemhealth monitor (mmsysmoncontrol restart).
  
  Problem trigger:
  Reconnecting broken connections
  
  Symptom:
  Error output/messages
  
  Platforms affected:
  ALL Operating System environments
  
  Functional Area affected:
  System Health
  
  Customer Impact:
  Low
  

Temporary fix

Comments

APAR Information

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

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

  IJ30684

Fix information

• Fixed component name

  SPEC SCALE ADV

• Fixed component ID

  5737F35AP

Applicable component levels