MPCBL0050N02Q Intel, MPCBL0050N02Q Datasheet - Page 166

• Manufacturer Part Number: MPCBL0050N02Q
• Manufacturer: Intel

Specifications of MPCBL0050N02Q

• Lead Free Status / RoHS Status: Supplier Unconfirmed

Note:
9.4
9.5
Intel NetStructure
Technical Product Specification
166
®
The IP address, once configured by the reference script provided, is stored in a non-
volatile memory and is persistent across IPMC update and payload resets. The IP
addresses are assigned to the IPMC independently of the host (OS) IP addresses and
they need not match. The IP addresses used by the OS are not visible to the IPMC.
To start SOL communication, the user invokes the SOL client utility with the IP address
of the blade and a series of authentication parameters (username, password, privilege
level, cipher suite, etc.). The IPMI v2.0 specification allows for AES encryption
algorithms for encryption of payload data sent over the network, including AES-128,
which uses 128-bit cipher keys.
The SOL client utility initializes an RMCP+ session with the blade and activates SOL.
When authentication is successfully completed, the IPMC firmware collects serial port
data from the blade’s serial port, formats it into network packets and forwards it to the
SOL client utility over the SOL session. The SMBus sideband interface port between the
IPMC and base interface Ethernet controller is used for this purpose. The SOL client
utility receives the packets, extracts the serial port data, and displays it on the screen.
The IPMC extracts the serial port data received from the SOL client utility and writes it
to the serial port of the blade. This allows network redirection of blade’s serial port data
stream that is independent of the host OS or EFI BIOS. The Ethernet controller plays a
critical role in redirecting the packets meant for the IPMC, based on receive filters.
The default SOL baud rate is 9.6 kbps.
The EFI BIOS default baud rate is 115.200 kbps. If SOL is configured for a different
baud rate, the EFI BIOS output is not seen using the SOL client until the EFI BIOS baud
rate is set to match the SOL client baud rate.
Serial Over LAN Client
The SOL client establishes an IPMI-over-LAN connection with the IPMC on the blade. It
then activates SOL, which effectively switches the board hardware to redirect serial
traffic to the IPMC instead of the serial port. Any outbound characters from the UART
are now packetized by the IPMC and sent over the network to the SOL client via the
sideband interface port. Conversely, any input on the SOL client is packetized by the
client and sent over the network to the IPMC, which is responsible for conveying it to
the UART.
SOL data is carried over the network in UDP datagrams. IPMI 2.0 defines the
specification of packet formats and protocols for SOL. As per the IPMI 2.0 specification,
RMCP+ is the packet format with the Payload Type set to “SOL”. Authentication,
integrity, and encryption for SOL are part of the RMCP+ specification.
The ipmitool client (version 1.8.7 or higher) is required. The ipmitool software is open
source. For more information, see
This client needs to be downloaded and compiled on the Linux* operating system of
your choice.
Reference Configuration Script
Intel provides an SOL reference script (reference_cfg) that sets up the various
parameters required for SOL operation.
The SOL configuration reference script (reference_cfg) sends a sequence of IPMI
commands to configure an SBC to enable the SOL feature. This script can be executed
on a payload CPU for local configuration, or on a node that has network connectivity to
the target SBC. Without this IPMC configuration, the SOL client utility is not able to
MPCBL0050 Single Board Computer
Section
9.8.2.2.
MPCBL0050—Serial Over LAN
Order Number: 318146-001
September 2007