![]() | Sun System Handbook - ISO 4.1 October 2012 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||
Solution Type Technical Instruction Sure Solution 1446587.1 : What is the difference between the ILOM System Event Log and the IPMI System Event Log?
In this Document
Applies to:Sun Fire X4270 M3 Server - Version: Not Applicable to Not Applicable - Release: N/A to N/AInformation in this document applies to any platform. Applies To: Document applies to any platform which supports ILOM version 3.x and above (X86 and SPARC T-series) GoalPurpose:This article explains differences between the ILOM event logs and the IPMI event logs. SolutionDescriptionLog files from the server platform can be generated in any of the following three ways: 1. From SP CLI by executing: show /SP/logs/event/list/ 2. From ILOM GUI by going to: System Monitoring > Event Logs> Select All Events in the Filter 3. Remotely by executing: ipmitool -H <ILOM IP address> -U <user name> -P <password> sel list IPMI System Event LogThe IPMI tool has been designed to keep the System Event Log (SEL) entries to a bare minimum. For instance, we have a number of IPMI "sensors" in the Sensor Data Repository. The tool provides us with the capability of assigning "thresholds" to some of these sensors. Every time a sensor threshold is crossed, an entry is made in the SEL. In newer platforms these thresholds are limited to those triggers that must drive system policy of some sort, usually error detection and state-changing events.IPMI SEL can hold approximately 909 entries. This can be found by running 'ipmitool sel' command: % ipmitool sel ILOM System Event LogThe ILOM SEL is a superset of IPMI SEL which can hold approximately 2000 entries and includes audit logs. If we are monitoring the server status through the SP/ILOM interfaces such as CLI, IPMI, Web - the login/logout audit entries typically cause the ILOM SEL to start rolling faster than the IPMI SEL.To counteract this, in ILOM ver 3.1, audit log entries were moved to their own log file. This should keep hardware events available longer in the ILOM event log. To summarize, the engineering effort is to reduce the IPMI SEL entries to a bare minimum - maintaining only those events that are informational and actionable (that is control state or contribute to fault diagnosis). The ILOM system event logs accessible through the CLI or the Web interface should be the first aid to review what has been happening on the system. Attachments This solution has no attachment |
||||||||||||
|