MPCBL0050N02Q Intel, MPCBL0050N02Q Datasheet - Page 223

• Manufacturer Part Number: MPCBL0050N02Q
• Manufacturer: Intel

Specifications of MPCBL0050N02Q

• Lead Free Status / RoHS Status: Supplier Unconfirmed

Firmware Update Utilities—MPCBL0050
Table 78.
September 2007
Order Number: 318146-001
Warning and error messages (Sheet 2 of 11)
E154
E155
E156
E157
E158
E204
E206
E207
E213
E214
E218
E222
E226
Number
IPMI communication error while
checking for the target presence.
IPMI communication problem while
determining the IPMB-0 address of IPMC
site %1.
The specified system does not support
IPMCs at site %1.
Cannot bridge to the target from a %1.
Did you mean to use the --target/-t
option?
Cannot contact the %1 while its carrier
board is in firmware transfer mode.
RMCP connection to "%1" failed
Invalid Username
Invalid Password
The authentication type: %1 is
unavailable for the selected privilege
level
No valid authentication type available
Unable to find suitable KCS Driver
No slot available to establish session
A LAN failure occurred
Message
While attempting to check for the presence of a sub-
FRU, there was an IPMI communication error, such as a
timeout. No completion code was returned, successful
or otherwise, in response to the query.
While attempting to find the IPMB address of the target
(such as the Get Address Info command) there was an
IPMI communication error, such as a timeout. No
completion code was returned, successful or otherwise,
in response to the query.
The target site specified is supported by the chassis,
but not for an AdvancedTCA board. For example, slots
15 and 16 of an MPCHC0001 contain PEM and fan
trays, but not SBCs.
Cannot communicate to a second SBC while running
locally on a different SBC (for example, the KCS
interface).
It is not possible to communicate with a sub-FRU (for
example, an RTM or AMC) while the carrier board (for
example, SBC) is in firmware transfer mode. Try again
later when the carrier is no longer in transfer mode, or
bring the carrier out of transfer mode with the Intel
OEM Exit FW Transfer mode command.
An RMCP/RMCP+ session could not be activated with
the target because of an earlier problem such as a bad
username or password.
An RMCP/RMCP+ session can not be established
because the supplied username was not accepted by
the target.
An RMCP/RMCP+ session can not be established
because the supplied password was not accepted by
the target.
An RMCP/RMCP+ session can not be established
because the desired authentication algorithm (for
example, MD2, MD5, etc.) was refused by the target
for the supplied privilege level. If no privilege is
specified, the default privilege is administrator. If no
privilege is specified, it is the same as typing –L
administrator.
For the given user and channel, the target does not
support MD5, MD2, straight password or none. This
could mean the target is misconfigured, or that the
target only supports an OEM authentication algorithm.
No IPMI request can be made using any known IPMI
device driver. For operating systems that have a
compiled-in IPMI driver, this indicates that the KCS
interface is in a bad state and may require a power
cycle of the SBC and/or any attached sub-FRUs. For
OSs that have loadable IPMI driver modules, the KCS
interface could be broken as above, or else the IPMI
driver service needs to be started with the /etc/init.d/
ipmi start command.
For direct LAN communication to an SBC (for example,
RMCP+ direct), the SBC already has its maximum
number of RMCP+ sessions active and cannot accept a
new session. For an RMCP bridge, it is the ShMC that
cannot accept an additional RMCP/RMCP+ session.
A LAN (that is RMCP/RMCP+) error occurred that is not
described by an other situation in this table.
Intel NetStructure
®
MPCBL0050 Single Board Computer
Description
Technical Product Specification
223