HP Integrity rx2800 rx2800 i2 User Service Guide - Page 81

Using event logs, iLO 3 MP event logs, Ctrl-B

Page 81 highlights

• The hex code for each event log is 128 bits long with an architected format: ◦ Some enumerated fields can be mapped to defined text strings. ◦ All can be displayed in hex, keyword, or text mode. • Events are created by firmware or OS code, and are sent over the PDH bus to the BMC for storage in either or both of the SEL and FP logs (HP-UX shows an I/O path for the BMC). • The iLO 3 MP can display event logs: SEL events are sent over the IPMB, between the BMC and the iLO 3 MP. • Event logs can also be read back over the PDH bus by software (for example, the IPMI driver or agent) for storage on disk. Using event logs To consult the event logs: 1. Connect to the system console. 2. Use Ctrl-B to access the iLO 3 MP menu. 3. Use the sl command to view event logs: System Event (E) and Forward Progress (F) logs are very useful in determining the context of an error (See the following figure for an example): NOTE: Remember that: • E shows only event logs for Warning, Critical, or Fatal faults by default; F shows all event log outputs. • System Event Logs (SELs) are never overwritten, unless they are first manually cleared: since they employ ring buffering, oldest logs get overwritten first. Forward Progress Logs (FPL) are circular and contain additional, non-critical information. • The alert threshold can be changed. iLO 3 MP event logs The iLO 3 MP provides diagnostic and configuration capabilities. See the HP Integrity iLO 3 Operations Guide for details on the iLO 3 MP commands. To access the iLO 3 MP, do the following: NOTE: The iLO 3 MP must be accessed from a terminal console which has access to the iLO 3 MP. 1. Login with proper username and password. NOTE: Default operator login and password: login = oper, password = oper. 2. Press cl to display the console history log. This log displays console history from oldest to newest. 3. Press sl to display the status logs. The status logs consist of: • System Event • Forward Progress • iLO Event • Cllear SEL and FPL • Live Events 4. For a more information on configuring the iLO 3 MP and using the iLO 3 MP commands, see the HP Integrity iLO 3 MP Operations Guides. Errors and reading error logs 81

  • 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

The hex code for each event log is 128 bits long with an architected format:
Some enumerated fields can be mapped to defined text strings.
All can be displayed in hex, keyword, or text mode.
Events are created by firmware or OS code, and are sent over the PDH bus to the BMC for
storage in either or both of the SEL and FP logs (HP-UX shows an I/O path for the BMC).
The iLO 3 MP can display event logs: SEL events are sent over the IPMB, between the BMC
and the iLO 3 MP.
Event logs can also be read back over the PDH bus by software (for example, the IPMI driver
or agent) for storage on disk.
Using event logs
To consult the event logs:
1.
Connect to the system console.
2.
Use
Ctrl-B
to access the iLO 3 MP menu.
3.
Use the
sl
command to view event logs: System Event (E) and Forward Progress (F) logs are
very useful in determining the context of an error (See the following figure for an example):
NOTE:
Remember that:
E
shows only event logs for Warning, Critical, or Fatal faults by default;
F
shows all event log
outputs.
System Event Logs (SELs) are never overwritten, unless they are first manually cleared: since
they employ ring buffering, oldest logs get overwritten first. Forward Progress Logs (FPL) are
circular and contain additional, non-critical information.
The alert threshold can be changed.
iLO 3 MP event logs
The iLO 3 MP provides diagnostic and configuration capabilities. See the
HP Integrity iLO 3
Operations Guide
for details on the iLO 3 MP commands. To access the iLO 3 MP, do the following:
NOTE:
The iLO 3 MP must be accessed from a terminal console which has access to the iLO 3
MP.
1.
Login with proper username and password.
NOTE:
Default operator login and password: login =
oper
, password =
oper
.
2.
Press
cl
to display the console history log. This log displays console history from oldest to
newest.
3.
Press
sl
to display the status logs. The status logs consist of:
System Event
Forward Progress
iLO Event
Cllear SEL and FPL
Live Events
4.
For a more information on configuring the iLO 3 MP and using the iLO 3 MP commands, see
the
HP Integrity iLO 3 MP Operations Guides
.
Errors and reading error logs
81