APAR status
Closed as program error.
Error description
Customer needed a way to change the severity of certain events such that they get notification.
Local fix
Problem summary
Several RAS events had inconsistent values as their SEVERITY and STATE. For instance, the event "network_bond_degraded", with STATE=DEGRADED, has SEVERITY=INFO. As a result, related failures were not propagated properly.
Problem conclusion
Benefits of the solution: Consistent view of unHEALTHY RAS events. No more showing HEALTHY RAS events as if they were errors. Work Around: No known work around; need to look up the RAS event definition each time to understand if it is a problem Problem trigger: Conditions for raising one of the following RAS events are met: - bond_degraded - ces_bond_degraded - ces_ips_all_unassigned - gnr_pdisk_unknown - heartbeat_missing - scale_mgmt_server_failed - tct_cs_disabled Symptom Unexpected Results/Behavior Platforms affected: ALL Linux OS environments Functional Area affected: - System Health - GUI Customer Impact: Suggested
Temporary fix
Comments
APAR Information
APAR number
IJ29542
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-12-01
Closed date
2020-12-16
Last modified date
2020-12-16
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:
12 January 2021