Logging

Enclosure Firmware Management events are written to three logs. The following sections describe the type of events that are included in each log. All logs can be used to verify progress and completion tasks and for troubleshooting purposes.

Firmware Log

HP BladeSystem 141392 Logging

This log displays detailed information for the last Enclosure Firmware Management operation executed on the server. This log is specific for the server, and is cleared any time a new Enclosure Firmware Management operation is started on the server. This log is also cleared when the server is removed from the enclosure.

The firmware log is the most useful resource to determine the progress of an Enclosure Firmware Management operation on a particular server.

Session Log

HP BladeSystem 141391 Logging

This log displays detailed information for the last Enclosure Firmware Management operation executed on the server and logs the entire session to the iLO VSP. This log is specific for the server, and is cleared anytime a new Enclosure Firmware Management operation is started on the server. This log is also cleared when the server is removed from the enclosure.

Firmware Management Log

HP BladeSystem 141389 Logging

The Enclosure Firmware Management log provides a consolidated view of major Enclosure Firmware Management events, such as firmware image selections, policy and schedule changes, and firmware operations initiating and completing. This log does not contain the step-by-step details included in the firmware log for each server.

The Enclosure Firmware Management Log is retained on the standby Onboard Administrator, if present.

Event failures

When an Enclosure Firmware Management task completes, the final event listed in the server firmware log is Firmware Management successfully completed or Firmware Management is incomplete.

If the last operation that appears in the Enclosure Firmware Management log does not indicate successful completion, the other firmware log entries might indicate the problem encountered by the Onboard Administrator. For example, the server must be powered off before a manual discovery, manual update, or scheduled update is performed. The log might indicate that the server was powered on, so the Enclosure Firmware Management operation was stopped.

If a failure occurs while performing an Enclosure Firmware Management task, the failed entry is logged as Firmware Management failed on blade X. The Onboard Administrator attempts the task again up to three times. If the task completes, the previous failed log entries can be disregarded. For detailed event information and current activity, see the firmware log for the server.

Logging