MPCBL0050N02Q Intel, MPCBL0050N02Q Datasheet - Page 200

• Manufacturer Part Number: MPCBL0050N02Q
• Manufacturer: Intel

Specifications of MPCBL0050N02Q

• Lead Free Status / RoHS Status: Supplier Unconfirmed

10.6.6
10.6.6.1
10.6.6.2
Intel NetStructure
Technical Product Specification
200
®
Automatic Firmware Update
While performing a firmware update via the KCS interface or an RMCP bridge, invoking
auto mode will automatically negotiate between a direct or staged firmware update. A
staged firmware update will be attempted first, while the direct firmware update is used
as a fall back. If the target supports staged updates and it is in a state that allows
staged updates, a staged update will be performed. If staged updates are not possible,
a direct firmware update will be attempted. Note that auto mode is the default mode,
by omitting the mode option (-M), auto is assumed.
Automatic Firmware Update using KCS Interface
To perform an auto firmware update over the KCS interface, you must be logged into
the target SBC as root.
The syntax of the command is:
The following is an example of an auto firmware update via the KCS interface:
The above command line can be abbreviated since the KCS interface and the auto
mode are both default options. The command can be abbreviated as follows:
Automatic Firmware Update via RMCP Bridging
In order for RMCP bridging to work correctly, the Shelf Manager must be connected to
the network in order to transmit TCP/IP traffic to and from your client. You must also
specify the interface option to be lan for RMCP bridging. Auto mode is default so by
omitting the -M option, auto is assumed.
When using the sbcupdate utility over RMCP bridge with Intel NetStructure
MPCMM0001/0002 Chassis Management Module:
When using the sbcupdate utility over an RMCP bridge with a 3rd party Shelf Manager,
it is essential that communication between the target IPMC and a remote network node
via a shelf manager can be established. Refer to
privileges for RMCP bridging” on page 190
commands that must be forwarded to IPMB by the Shelf Manager.
The syntax of the command is:
An example of auto firmware update via RMCP bridging is:
• Check that the CMM firmware version is 6.1.1.x or higher.
• Transfer the /usr/share/doc/sbcutils/cmdPrivilege.ini file to both the active and
MPCBL0050 Single Board Computer
standby CMMs. Place cmdPrivelege.ini in the /etc/ directory on the CMMs. Then,
restart the RMCP servers. More details on this can be found in
“Configuring the Intel NetStructure
# sbcupdate -I kcs -M auto <path to firmware image/filename>
# sbcupdate -I kcs -M auto MPCBL0050_FW_NNNNNN.hex
# sbcupdate MPCBL0050_FW_NNNNNN.hex
# sbcupdate -I lan -M auto -H <shelf_manager_ip_address>
# sbcupdate -I lan -M auto -H 10.90.90.91 -U root
-U <RMCP_username> -P <RMCP_password> -t <target>
<path to firmware image/filename>
-P cmmrootpass -t 0x8e MPCBL0050_FW_NNNNNN.hex
®
MPCMM0001/0002 CMM” on page
for more information on the required RMCP
Table 74, “Required IPMI command
MPCBL0050—Firmware Update Utilities
Order Number: 318146-001
Section 10.5.2,
September 2007
191.