Event log entries – HP Integrated Lights-Out 4 User Manual
Page 299
12. When you are finished debugging the host server, use PuTTY to connect to the CLI and turn
off the debug socket to the Virtual Serial Port. Then, enter the following command:
windbg_disable
NOTE:
You can disconnect and reconnect the Windows debugger as long as you keep the
iLO debug socket enabled.
Event log entries
lists typical iLO event log entries.
Table 17 Event log entries
Description
Event log entry
The server power was removed.
Server power removed
The IP address for the browser that logged in.
Browser login:
The server power was restored.
Server power restored
The IP address for the browser that logged out.
Browser logout:
The server was reset.
Server reset
A browser login failed.
Failed Browser login ? IP
Address:
iLO failed an internal test. The probable cause is failure of a critical component.
Further use of iLO on this server is not recommended.
iLO Self Test Error: #
iLO was reset.
iLO reset
The on-board clock was set.
On-board clock set; was
<#:#:#:#:#:#>
The server logged one or more critical errors.
Server logged critical
error(s)
A user cleared the event log.
Event log cleared by:
LO was reset to the default settings.
iLO reset to factory
defaults
The iLO ROM was upgraded.
iLO ROM upgrade to <#>
iLO was reset for a ROM upgrade.
iLO reset for ROM upgrade
iLO was reset by user diagnostics.
iLO reset by user
diagnostics
The power was restored to iLO.
Power restored to iLO
An error occurred in iLO, and iLO reset itself. If this issue persists, call customer
support.
iLO reset by watchdog
The server reset iLO.
iLO reset by host
A noncritical error occurred in iLO, and iLO reset itself. If this issue persists,
call customer support.
Recoverable iLO error, code
<#>
The SNMP trap did not connect to the specified IP address.
SNMP trap delivery failure:
The SNMP trap did not connect to the specified IP address.
Test SNMP trap alert failed
for:
The SNMP trap did not connect to the specified IP address.
Power outage SNMP trap alert
failed for:
Event log entries 299