Add Severity level to payload of list.suspects event
State
10-Fix Delivered (Fix available in build)
Category:Subcategory
fma:other
Keywords
swfma
Responsible Engineer
Robert Johnston
Reported Against
Duplicate Of
Introduced In
Commit to Fix
snv_121
Fixed In
snv_121
Release Fixed
solaris_nevada(snv_121)
Related Bugs
Submit Date
18-March-2007
Last Update Date
13-August-2009
Description
The the Severity level assigned to a given diagnosis (message ID) is currently only captured in the message content. It should be added to the payload of the list.suspects event which in turn represent the primary connected services interface for the generation of fault alarm telemetry. The severity level is in turn used in auto service request generation to determine the severity of the service request.
The Severity of the event is currently only captured in the in the message content. It needs to be added as a standard payload member of the list.suspects event which is the primary connected service interface for generating fault alarm telemetry. The severity member would in turn be used to determine the severity level of the service request.
An associated object would also have to be added to the SUN-FM-MIB.
Work Around
N/A
Comments
Yes, this should be added to list.suspect. With the recently-improved
libfmd_msg this should be easy.
This request has been repeated from systems management ISVs who want to
consume list.suspect and flag it appropriately in the network mngmt
software. With the severity not included in list.suspect their only
alternative is to use cmdline getmsg (tricky to get working!) or
correlate with the SNMP data.