[fm-discuss] ereports and payload questions

[Cynthia A. McGuire]

The ereports generated by the fault manager (fmd) are private and pre-date the existence of the event registry (http://opensolaris.org/os/project/events-registry).  A listing of the fmd errors are found in usr/src/cmd/fm/fmd/common/fmd_error.h where the ereport leaf class is derived by eliding 'EFMD' and converting the remainder to lower case (see usr/src/cmd/fm/fmd/common/mkerror.sh).  Not all of the error codes in fmd_error.h are converted to ereports and it takes a bit of sleuthing to find out which ones are.

According to the protocol, the only required payload members for an ereport are 'class', 'version', 'detector' and 'ena'.  This is documented in payload specification the for ereport class definition in the event registry.  I suppose the fmd self-diagnosis engine uses an implied detector of itself, so there is no real reason to include the detector. 

The 'resource' member is optional and often used to offer additional details about the error and its impact to the system.  In the  ereport.cpu.ultraSPARC-IVplus.ce example, the cpu is listed as the detector but the resource payload member expresses details about the component (dimm) impacted by the error.  Having this information in the ereport helps the diagnosis engine determine where the problem is.

Cindi
--
This message posted from opensolaris.org