MPCBL0050N02Q Intel, MPCBL0050N02Q Datasheet - Page 222

• Manufacturer Part Number: MPCBL0050N02Q
• Manufacturer: Intel

Specifications of MPCBL0050N02Q

• Lead Free Status / RoHS Status: Supplier Unconfirmed

Table 78.
Intel NetStructure
Technical Product Specification
222
®
Warning and error messages (Sheet 1 of 11)
E102
E103
E104
E105
E106
E107
E108
E109
E110
E150
E151
E152
E153
Number
MPCBL0050 Single Board Computer
Unsupported interface “%1”. Must be
one of {kcs | lan}.
Unsupported authorization type “%1”.
Must be one of {none | md2 | md5 |
password}.
Unsupported privilege level “%1”. Must
be one of {callback | user | operator |
admin}.
Illegal IPMB address: 0x%1.
Parse error: %1.
AMC site number %1 is out-of-range
(must be between %2 and %3).
IPMC site number %1 is out-of-range
(must be between %2 and %3).
Syntax error in target argument: “%1”
When communicating locally, it is not
possible to specify a target blade other
than 0x20.
IPMI communication problem while
reading FRU address info.
The specified system does not support
FRUs of type "%1".
The specified target is ambiguous. There
is more than one possible FRU of type
"%1".
There is no response from any %1 at
the specified location.
Message
The user has supplied the interface option with an
argument other than “kcs” or “lan”. %1 is replaced with
the offending interface name.
The user has supplied the authtype option with an
argument other than “none”, “md2”, “md5”, or
“password”. %1 is replaced with the offending
authorization type.
The user has supplied the privilege option with an
argument other than “callback”, “user”, “operator” or
“admin”. %1 is replaced with the offending privilege
level.
The user has supplied an out-of-range IPMB address.
The range enforced by sbcupdate is [0x02, 0xFE], but
the chassis in use is likely to require a subset of this
range.
This message is displayed as a result of a number of
different errors in invocation syntax such as, unknown
option, missing option argument, string supplied for a
numerical option argument, etc. %1 is replaced with
further detail on the parse problem.
From the AMC specification, the AMC site numbers
must be between 1 and 8, inclusive.
The user has supplied an out-of-range IPMC site
number. The range enforced by sbcupdate is [0x01,
0xFF], but the chassis in use is likely to require a
subset of this range.
The argument to the target option is malformed.
For “direct to the blade” operation (that is, KCS or
RMCP+ direct), if the target argument includes an IPMB
address, it must be 0x20 (for example: --target
0x20:rtm or --target rtm). SBCs and CMMs from Intel
do not support bridging from one SBC to another to
from the SBC to the ShMC.
During a FRU operation, this message is displayed if
there is a problem sending messages to the carrier
SBC, for example, a timeout or error completion code.
The three commands send to the carrier are Get Device
ID, Get PICMG Properties and Get Address Info.
The user specified an FRU operation to a target that is
not supported by the SBC. For example, this message
is displayed if the target argument is “amc” and the
SBC in use does not have an AdvancedMC* module.
If the target’s carrier board supports more than one
sub-FRU of the given type, then the sub-FRU’s site
number must be supplied on the command line. For
example, on an MPCBL0050 SBC, it is fine to use
“--target amc” because only a single amc is supported.
Using the same target argument for a multi-AMC SBC
is ambiguous. In that case, it is required to use
something like “--target amc6”.
A sub-FRU was specified but is not currently present in
the system.
MPCBL0050—Firmware Update Utilities
Description
Order Number: 318146-001
September 2007