Some changes were putback yesterday to have repair events logged. A repair event is either automatically initiated by FMD when it detects a component has been replaced in the system, or via the 'fmadm repair ' CLI. The CRs that were putback:
- 6502956 repair events should be logged
- 6430447 Notifications (message, SNMP trap) should be generated in response to a list.repaired event
In short, the changes institute the following:
- Add an FMA message code to the FMD dictionary for repair events
- Have syslog-msg and snmp-trapgen agents subscribe to repair events. This equates to logging repair events to the Solaris console/messages file and notifying external consumers of repairs via SNMP.
- Log repair events to the FMA fault log. fmdump is also updated to understand/display repair events
This is a great improvement - it closes the loop on the life of a fault in the system. We've not got logging of all aspects of a problem in a system - from error detection, through diagnosis, and now finally repair.
:wq
