IBM QS21 Service Guide - Page 87

necessary.

Page 87 highlights

Table 7. BMC test results (continued) Test Extended Number Status results Actions 166-813- Abort xxx BMC BMC I2C test canceled: cannot return the number of requested data bytes. 166-814- Abort xxx BMC BMC I2C test canceled: requested sensor, data, or record is not present. 166-814- Abort xxx BMC BMC I2C test 1. Turn off the system and disconnect it from power. The canceled: invalid system must be removed from AC power in order to reset data field in the the BMC. request. 2. After 45 seconds, reconnect the system to power and turn on the system. 3. Run the test again. 4. Make sure that the DSA Diagnostic code is at the latest level. The latest level DSA Diagnostic code can be found on the IBM Support Web site at http://www.ibm.com/ support/docview.wss?uid=psg1SERV-DSA/. 5. Check BMC firmware level and upgrade if necessary. The installed firmware level can be found in the DSA Diagnostic Event Log within the Firmware/VPD section for this component. The latest level firmware for this component can be found on the IBM Support Web site at http://www.ibm.com/support/us/en/. 6. Run the test again. 7. If the test continues to fail, refer to the other sections of this chapter for diagnosis and corrective action. 166-816- Abort xxx BMC BMC I2C test canceled: the command is illegal for the specified sensor or record type 166-817- Abort xxx BMC BMC I2C test canceled: a command response could not be provided 166-818- Abort xxx BMC BMC I2C test canceled: cannot execute a duplicated request. Chapter 5. Diagnostics and troubleshooting 69

  • 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

Table
7.
BMC
test
results
(continued)
Test
Number
Status
Extended
results
Actions
166-813-
xxx
BMC
Abort
BMC
I2C
test
canceled:
cannot
return
the
number
of
requested
data
bytes.
166-814-
xxx
BMC
Abort
BMC
I2C
test
canceled:
requested
sensor,
data,
or
record
is
not
present.
166-814-
xxx
BMC
Abort
BMC
I2C
test
canceled:
invalid
data
field
in
the
request.
1.
Turn
off
the
system
and
disconnect
it
from
power.
The
system
must
be
removed
from
AC
power
in
order
to
reset
the
BMC.
2.
After
45
seconds,
reconnect
the
system
to
power
and
turn
on
the
system.
3.
Run
the
test
again.
4.
Make
sure
that
the
DSA
Diagnostic
code
is
at
the
latest
level.
The
latest
level
DSA
Diagnostic
code
can
be
found
on
the
IBM
Support
Web
site
at
support/docview.wss?uid=psg1SERV-DSA/.
5.
Check
BMC
firmware
level
and
upgrade
if
necessary.
The
installed
firmware
level
can
be
found
in
the
DSA
Diagnostic
Event
Log
within
the
Firmware/VPD
section
for
this
component.
The
latest
level
firmware
for
this
component
can
be
found
on
the
IBM
Support
Web
site
at
6.
Run
the
test
again.
7.
If
the
test
continues
to
fail,
refer
to
the
other
sections
of
this
chapter
for
diagnosis
and
corrective
action.
166-816-
xxx
BMC
Abort
BMC
I2C
test
canceled:
the
command
is
illegal
for
the
specified
sensor
or
record
type
166-817-
xxx
BMC
Abort
BMC
I2C
test
canceled:
a
command
response
could
not
be
provided
166-818-
xxx
BMC
Abort
BMC
I2C
test
canceled:
cannot
execute
a
duplicated
request.
Chapter
5.
Diagnostics
and
troubleshooting
69