IBM 8863 Service Guide - Page 35

Viewing, error, Configuration/Setup, Utility, program

Page 35 highlights

v The BMC log is limited in size and is designed so that when the log is full, new entries will not overwrite existing entries; therefore, you must periodically clear the BMC log from the Configuration/Setup Utility program (the menu choices are described in the User's Guide). v When troubleshooting an error, make sure to clear the BMC log so that you can find current errors more easily. v Entries written to the BMC log early in the POST procedure will show an incorrect date as the default timestamp; however, the date and time will correct itself as POST continues. v Each BMC log entry appears on its own page; to display all the data for an entry, use the up arrow (↑) and down arrow (↓) or the Page Up and Page Down keys. To move from one entry to the next, move the cursor to the Get Next Entry or Get Previous Entry line; then, press Enter. v The log indicates an Assertion Event when an event has occurred. It indicates a Deassertion Event when the event is no longer occurring. v Some of the error codes and messages in the BMC log are abbreviated. v Viewing the BMC log through the web interface of the optional Remote Supervisor Adapter II SlimLine allows all messages to be translated. The following illustration shows an example of a BMC log entry. BMC System Event Log Get Next Entry Get Previous Entry Clear BMC SEL Entry Number= Record ID= Record Type= Timestamp= Entry Details: 00005 / 00011 0005 02 2005/01/25 16:15:17 Generator ID= 0020 Sensor Type= 04 Assertion Event Fan Threshold Lower Non-critical - going high Sensor Number= 40 Event Direction/Type= 01 Event Data= 52 00 1A You can view the contents of the POST error log, the BMC log, and the system-error log from the Configuration/Setup Utility program. You can view the contents of the BMC log also from the diagnostic programs. Note: When troubleshooting PCI-X slots, note that the error logs report the PCI-X buses numerically. The numerical assignments vary depending on the configuration. You can check the assignments by running the Configuration/Setup Utility program (see the User's Guide for more information). Viewing error logs from the Configuration/Setup Utility program For complete information about using the Configuration/Setup Utility program, see the User's Guide. To view the error logs, complete the following steps: Chapter 2. Diagnostics 19

  • 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

v
The
BMC
log
is
limited
in
size
and
is
designed
so
that
when
the
log
is
full,
new
entries
will
not
overwrite
existing
entries;
therefore,
you
must
periodically
clear
the
BMC
log
from
the
Configuration/Setup
Utility
program
(the
menu
choices
are
described
in
the
User’s
Guide
).
v
When
troubleshooting
an
error,
make
sure
to
clear
the
BMC
log
so
that
you
can
find
current
errors
more
easily.
v
Entries
written
to
the
BMC
log
early
in
the
POST
procedure
will
show
an
incorrect
date
as
the
default
timestamp;
however,
the
date
and
time
will
correct
itself
as
POST
continues.
v
Each
BMC
log
entry
appears
on
its
own
page;
to
display
all
the
data
for
an
entry,
use
the
up
arrow
(
)
and
down
arrow
(
)
or
the
Page
Up
and
Page
Down
keys.
To
move
from
one
entry
to
the
next,
move
the
cursor
to
the
Get
Next
Entry
or
Get
Previous
Entry
line;
then,
press
Enter.
v
The
log
indicates
an
Assertion
Event
when
an
event
has
occurred.
It
indicates
a
Deassertion
Event
when
the
event
is
no
longer
occurring.
v
Some
of
the
error
codes
and
messages
in
the
BMC
log
are
abbreviated.
v
Viewing
the
BMC
log
through
the
web
interface
of
the
optional
Remote
Supervisor
Adapter
II
SlimLine
allows
all
messages
to
be
translated.
The
following
illustration
shows
an
example
of
a
BMC
log
entry.
BMC
System
Event
Log
----------------------------------------------------------
Get
Next
Entry
Get
Previous
Entry
Clear
BMC
SEL
Entry
Number=
00005
/
00011
Record
ID=
0005
Record
Type=
02
Timestamp=
2005/01/25
16:15:17
Entry
Details:
Generator
ID=
0020
Sensor
Type=
04
Assertion
Event
Fan
Threshold
Lower
Non-critical
-
going
high
Sensor
Number=
40
Event
Direction/Type=
01
Event
Data=
52
00
1A
You
can
view
the
contents
of
the
POST
error
log,
the
BMC
log,
and
the
system-error
log
from
the
Configuration/Setup
Utility
program.
You
can
view
the
contents
of
the
BMC
log
also
from
the
diagnostic
programs.
Note:
When
troubleshooting
PCI-X
slots,
note
that
the
error
logs
report
the
PCI-X
buses
numerically.
The
numerical
assignments
vary
depending
on
the
configuration.
You
can
check
the
assignments
by
running
the
Configuration/Setup
Utility
program
(see
the
User’s
Guide
for
more
information).
Viewing
error
logs
from
the
Configuration/Setup
Utility
program
For
complete
information
about
using
the
Configuration/Setup
Utility
program,
see
the
User’s
Guide
.
To
view
the
error
logs,
complete
the
following
steps:
Chapter
2.
Diagnostics
19