HP Integrity BL870c HP Integrity iLO 2 Operations Guide, Eleventh Edition - Page 116

Events, Remote Serial Console, View Console

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

Page 116 highlights

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 in to iLO 2 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 can be forward progress markers (such as CPU selftest complete). Events are produced by intelligent hardware modules, the OS, and system firmware. Events funnel into the BMC from different sources throughout the server. iLO 2 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: 0: Minor forward progress 1: Major forward progress 2: Informational 3: Warning 5: Critical 7: Fatal Remote Serial Console The Remote Serial Console page (Figure 8-8) enables you to securely view and manage a remote server. You must have console access right to use this feature. You can also connect to the system console by launching View Console from the Remote Serial Console page. 116 Using iLO 2

  • 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
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
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 in to iLO 2 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 can be forward progress markers (such as CPU selftest complete).
Events are produced by intelligent hardware modules, the OS, and system firmware. Events
funnel into the BMC from different sources throughout the server. iLO 2 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:
0: Minor forward progress
1: Major forward progress
2: Informational
3: Warning
5: Critical
7: Fatal
Remote Serial Console
The Remote Serial Console page (
Figure 8-8
) enables you to securely view and manage a remote
server. You must have console access right to use this feature.
You can also connect to the system console by launching
View Console
from the Remote Serial
Console page.
116
Using iLO 2