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

SL Command for Integrity Cell-Based Servers

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 87 highlights

Table 8-4 iLO 2 Event Log Filter Options Filtering Option N: User Login P: Port Name I: IP Address M: Date Filter Criteria Filter by user Login ID Filter by port name (Serial, Telnet, SSH, WEB) Filter by user IP Address (dotted decimal format) Filter by date stamp of the records entries (MM/DD/YYYY) If you select more than one filtering option, it acts as an additional filter. For example, if you select the filtering option N followed by P, the logs displayed are the logs that satisfy the filtering criteria for options N and P. NOTE: The iLO2 Event Logs cannot be cleared. A finite number of records are stored. The older records are replaced as the log fills up. Table 8-5 lists alert (severity) levels. Table 8-5 Alert Levels Severity 0 1 2 3 5 7 Minor forward progress Major forward progress Informational Warning Critical Fatal Definition See also: DC (default configuration) and VFP (virtual front panel). SL Command for Integrity Cell-Based Servers SL: Show Logs - View the events in the log history. SL displays the contents of the events that have been stored in nonvolatile memory. Events are data items that communicate system information from the source of the event to other parts of the system, and ultimately to the system administrator. Events are produced by intelligent hardware modules, the operating system, and system firmware. Events funnel into iLO 2 from different sources throughout the server. Events can be a result of a failure or an error (such as fan failure, machine-check, and so on). They can indicate a major change in system state (firmware boot start, system power on/off) or they might be forward progress markers, (such as CPU self test complete). Event data indicates what the event was, where it happened, and the severity of the event. The most important events are error logs (alert level 3 or higher), and major change of state logs, because they give information that can provide clues about the cause of anomalous behavior. The log viewer contains an event decoder to help you interpret events. Table 8-6 lists events, actions, and functions of the logs. Text User Interface 87

  • 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
Table 8-4 iLO 2 Event Log Filter Options
Filter Criteria
Filtering Option
Filter by user Login ID
N: User Login
Filter by port name (Serial, Telnet, SSH, WEB)
P: Port Name
Filter by user IP Address (dotted decimal format)
I: IP Address
Filter by date stamp of the records entries (MM/DD/YYYY)
M: Date
If you select more than one filtering option, it acts as an additional filter. For example, if you
select the filtering option
N
followed by
P
, the logs displayed are the logs that satisfy the filtering
criteria for options
N
and
P
.
NOTE:
The iLO2 Event Logs cannot be cleared.
A finite number of records are stored. The older records are replaced as the log fills up.
Table 8-5
lists alert (severity) levels.
Table 8-5 Alert Levels
Definition
Severity
Minor forward progress
0
Major forward progress
1
Informational
2
Warning
3
Critical
5
Fatal
7
See also: DC (default configuration) and VFP (virtual front panel).
SL Command for Integrity Cell-Based Servers
SL
: Show Logs - View the events in the log history.
SL
displays the contents of the events that have been stored in nonvolatile memory.
Events are data items that communicate system information from the source of the event to other
parts of the system, and ultimately to the system administrator. Events are produced by intelligent
hardware modules, the operating system, and system firmware. Events funnel into iLO 2 from
different sources throughout the server.
Events can be a result of a failure or an error (such as fan failure, machine-check, and so on).
They can indicate a major change in system state (firmware boot start, system power on/off) or
they might be forward progress markers, (such as CPU self test complete). Event data indicates
what the event was, where it happened, and the severity of the event. The most important events
are error logs (alert level 3 or higher), and major change of state logs, because they give information
that can provide clues about the cause of anomalous behavior. The log viewer contains an event
decoder to help you interpret events.
Table 8-6
lists events, actions, and functions of the logs.
Text User Interface
87