HP rp3440 HP Integrity and HP 9000 iLO MP Operations Guide, Fifth Edition - Page 73

Events, funnel into BMC from different sources throughout the server. The iLO MP polls the BMC - cpu

Get HP rp3440 PDF manuals and user guides View all HP rp3440 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 73 highlights

Figure 6-5 System Status > System Event Log Page Table 6-8 lists the fields, buttons, and descriptions. Table 6-8 System Event Log Page Description Fields and Buttons System Event Log Forward Progress Log Boot Log Previous Boot Log Delete Log Description High attention events and errors. Reading the system event log turns off the attention LED (blinking yellow). All events. In a web GUI session you cannot view forward progress logs, only system event logs. All events between "start of boot" and "boot complete". The boot log from the previous boot. Deletes the log. NOTE: You can view only the most pertinent fields for each event on the web. For a more complete decoding of the events, use the TUI available by logging into the iLO MP through telnet or SSH. Events Events can be a result of a failure or an error (such as fan failure, Machine-Check Abort, and so on). They can indicate a major change in system state (such as firmware boot start or system power on/off), or they might be forward progress markers (such as CPU selftest complete). Events are produced by intelligent hardware modules, the OS, and system firmware. Events funnel into BMC from different sources throughout the server. The iLO MP polls the BMC for new events and stores them in nonvolatile memory. Events communicate system information from the source of the event to other parts of the system, and ultimately to the system administrator. The log viewer contains an event decoder to help you interpret events. The following event severity (or alert) levels are defined: Web GUI 73

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
Figure 6-5 System Status > System Event Log Page
Table 6-8
lists the fields, buttons, and descriptions.
Table 6-8 System Event Log Page Description
Description
Fields and Buttons
High attention events and errors. Reading the system event log turns off the attention
LED (blinking yellow).
System Event Log
All events. In a web GUI session you cannot view forward progress logs, only system
event logs.
Forward Progress Log
All events between “start of boot” and “boot complete”.
Boot Log
The boot log from the previous boot.
Previous Boot Log
Deletes the log.
Delete Log
NOTE:
You can view only the most pertinent fields for each event on the web. For a more
complete decoding of the events, use the TUI available by logging into the iLO MP through telnet
or SSH.
Events
Events can be a result of a failure or an error (such as fan failure, Machine-Check Abort, and so
on). They can indicate a major change in system state (such as firmware boot start or system
power on/off), or they might be forward progress markers (such as CPU selftest complete).
Events are produced by intelligent hardware modules, the OS, and system firmware. Events
funnel into BMC from different sources throughout the server. The iLO MP polls the BMC for
new events and stores them in nonvolatile memory. Events communicate system information
from the source of the event to other parts of the system, and ultimately to the system
administrator.
The log viewer contains an event decoder to help you interpret events.
The following event severity (or alert) levels are defined:
Web GUI
73