IBM 8872 Service Guide - Page 35

Viewing, error, Configuration/Setup, Utility, program

Get IBM 8872 - eServer xSeries 460 PDF manuals and user guides
UPC - 000435813060
View all IBM 8872 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 35 highlights

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 The BMC log is limited in size. When the log is full, new entries will not overwrite existing entries; therefore, you must periodically clear the BMC log through the Configuration/Setup Utility program (the menu choices are described in the User's Guide). When you are troubleshooting an error, be sure to clear the BMC log so that you can find current errors more easily. Entries that are written to the BMC log during the early phase of POST show an incorrect date and time as the default time stamp; however, the date and time are corrected as POST continues. Each BMC log entry appears on its own page. To display all the data for an entry, use the Up Arrow (↑) and Down Arrow (↓) keys or the Page Up and Page Down keys. To move from one entry to the next, select Get Next Entry or Get Previous Entry. The log indicates an assertion event when an event has occurred. It indicates a deassertion event when the event is no longer occurring. Some of the error codes and messages in the BMC log are abbreviated. If you view the BMC log through the Web interface of the optional Remote Supervisor Adapter II SlimLine, the messages can be translated. 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. When you are 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. 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
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
The
BMC
log
is
limited
in
size.
When
the
log
is
full,
new
entries
will
not
overwrite
existing
entries;
therefore,
you
must
periodically
clear
the
BMC
log
through
the
Configuration/Setup
Utility
program
(the
menu
choices
are
described
in
the
User’s
Guide
).
When
you
are
troubleshooting
an
error,
be
sure
to
clear
the
BMC
log
so
that
you
can
find
current
errors
more
easily.
Entries
that
are
written
to
the
BMC
log
during
the
early
phase
of
POST
show
an
incorrect
date
and
time
as
the
default
time
stamp;
however,
the
date
and
time
are
corrected
as
POST
continues.
Each
BMC
log
entry
appears
on
its
own
page.
To
display
all
the
data
for
an
entry,
use
the
Up
Arrow
(
↑
)
and
Down
Arrow
(
↓
)
keys
or
the
Page
Up
and
Page
Down
keys.
To
move
from
one
entry
to
the
next,
select
Get
Next
Entry
or
Get
Previous
Entry
.
The
log
indicates
an
assertion
event
when
an
event
has
occurred.
It
indicates
a
deassertion
event
when
the
event
is
no
longer
occurring.
Some
of
the
error
codes
and
messages
in
the
BMC
log
are
abbreviated.
If
you
view
the
BMC
log
through
the
Web
interface
of
the
optional
Remote
Supervisor
Adapter
II
SlimLine,
the
messages
can
be
translated.
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.
When
you
are
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
.
Chapter
2.
Diagnostics
19