IJ51222: MMHEALTH ENCRYPTION MONITORING DOES NOT SHOW NEEDED DETAILED INFORMATION IN THE DEFAULT VIEW.

APAR status

• Closed as program error.

Error description

• If a problem with an encryption server happens just the Rkmid is
  visible in the default "mmhealth node show" view. Furthermore
  there are two monitoring mechanisms, one which will use an index
  to convey whether main or backup server is affected and one
  which will directly use the hostname or ip for that. Moreover
  the usual way to resolve an event with "mmhealth event resolve"
  has been broken for that component.
  

Local fix

• mmhealth node show encryption -v (or -Y) to see the server
  information. mmhealth node eventlog -Y would work as well.
  Resolving the event needs a "mmsysmoncontrol restart"
  

Problem summary

• If a problem with an encryption server happens just the Rkmid is
  visible in the default "mmhealth node show" view. Furthermore
  there are two monitoring mechanisms, one which will use an index
  to convey whether main or backup server is affected and one
  which will directly use the hostname or ip for that. Moreover
  the usual way to resolve an event with "mmhealth event resolve"
  has been broken for that component.
  

Problem conclusion

• This problem is fixed in 5.2.0.1
  To see all Spectrum Scale APARs and their respective
  Fix solutions refer to page:
  https://public.dhe.ibm.com/storage/spectrumscale/spectrum_scale_
  apars.html
  
  Benefits of the solution:
  With the change the RkmId will be shown as entity, but the
  server information will be visible with the event details. Both
  monitoing approaches will use server IP/name for the detailed
  information.  "mmhealth event resolve" will work as it should
  plus it will be needed less often as an automatic will use the
  newer monitoring method to resolve events automatically.
  (configurable, default is active)
  
  Work Around:
  mmhealth node show encryption -v (or -Y) to see the server
  information. mmhealth node eventlog -Y would work as well.
  Resolving the event needs a "mmsysmoncontrol restart"
  
  Problem trigger:
  Code change to have RkmId as the common ground for old and new
  monitoring methods.
  
  Symptom:
  Unexpected Results/Behavior
  
  Platforms affected:
  ALL Linux OS environments
  
  Functional Area affected:
  System Health
  
  Customer Impact:
  Suggested
  

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:

Fix information

• Fixed component name

  SPEC SCALE STD

• Fixed component ID

  5737F33AP

Applicable component levels