Emerson is a trademark registered in the U.S. Patent and Trademark Office. All other product or service names are the property of
their respective owners.
®
Intel
is a trademark or registered trademark of Intel Corporation or its subsidiaries in the United States and other countries.
™
and all other Java-based marks are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other
, Windows® and Windows Me® are registered trademarks of Microsoft Corporation; and Windows XP™ is a trademark of
®
, CompactPCI®, AdvancedTCA™ and the PICMG, CompactPCI and AdvancedTCA logos are registered trademarks of the
®
is a registered trademark of The Open Group in the United States and other countries.
Notice
While reasonable efforts have been made to assure the accuracy of this document, Emerson assumes no liability resulting from any
omissions in this document, or from the use of the information obtained therein. Emerson reserves the right to revise this document
and to make changes from time to time in the content hereof without obligation of Emerson to notify any person of such revision or
changes.
Electronic versions of this material may be read online, downloaded for personal use, or referenced in another document as a URL to
an Emerson website. The text itself may not be published commercially in print or electronic form, edited, translated, or otherwise
altered without the permission of Emerson,
It is possible that this publication may contain reference to or information about Emerson products (machines and programs),
programming, or services that are not available in your country. Such references or information must not be construed to mean that
Emerson intends to announce such Emerson products, programming, or services in your country.
Limited and Restricted Rights Legend
If the documentation contained herein is supplied, directly or indirectly, to the U.S. Government, the following notice shall apply unless
otherwise agreed to in writing by Emerson.
Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (b)(3) of the Rights in Technical
Data clause at DFARS 252.227-7013 (Nov. 1995) and of the Rights in Noncommercial Computer Software and Documentation clause
at DFARS 252.227-7014 (Jun. 1995).
ATCA-7350 Control via IPMI Programmer’s Reference (6806800H29E)
About this Manual
Overview of Contents
This manual is intended for users qualified in electronics or electrical engineering. Users must
have a working understanding of Intelligent Platform Management Interface (IPMI).
It provides information on how to control and monitor the functionality of the ATCA-7350 via
IPMI and contains the following chapters and appendices:
zChapter 1, Introduction, on page 11 describes the main features of the IPMC firmware.
zChapter 2, Supported Commands, on page 15 lists all the IPMI1.5 and IPMI2.0 standard
commands supported by the ATCA-7350.
zChapter 3, FRU Information and Sensor Data Records, on page 27 provides the FRU
information and all the sensor data records.
zChapter 4, SOL Module Configuration, on page 53 describes how to configure the Serial
over LAN.
zAppendix A, Related Documentation, on page 59 provides links to further ATCA-7350-
related documentation.
Abbreviations
This document uses the following abbreviations:
AbbreviationDefinition
ACPIAdvanced Configuration and Power Interface
ATCAAdvanced Telecom Computing Architecture
BIOSBasic Input/Output System
CMDIPMI Command Specified in Hexadecimal
CPUCentral Processing Unit
FBDFully Buffered DIMM
FPGAField-Programmable Gate Array
FRUField Replaceable Unit
FWFirmware
GAGeneral Availability
GUIDGlobal Unique Identifier
HDHard Disk
IANAInternet Assigned Numbers Authority
IPMBIntelligent Platform Management Bus
ATCA-7350 Control via IPMI Programmer’s Reference (6806800H29E)
7
About this Manual
AbbreviationDefinition
IPMCIntelligent Platform Management Controller
IPMIIntelligent Platform Management Interface
LANLocal Area Network
LEDLight Emitting Diode
LSBLeast Significant Bit
LUNLogical Units
MACMedia Access Control
MSBMost Significant Bit
NetFnIPMI Network Function in Hexadecimal
OEMOriginal Equipment Manufacturer
PICMGPCI Industrial Computer Manufacturers Group
PwrOkPower OK
RTMRear-Transition Modules
SDRSensor Data Records
SELSystem Event Log
SOLSerial Over LAN
VCCVirtual Channel Connection
VERVersion
Conventions
The following table describes the conventions used throughout this manual.
NotationDescription
0x00000000Typical notation for hexadecimal numbers (digits are 0
0b0000Same for binary numbers (digits are 0 and 1)
boldUsed to emphasize a word
ScreenUsed for on-screen output and code related elements or
Courier + BoldUsed to characterize user input and to separate it from
ReferenceUsed for references and for table and figure descriptions
File > ExitNotation for selecting a submenu
through F), for example used for addresses and offsets
commands in body text
system output
<text>Notation for variables and keys
[text]Notation for software buttons to click on the screen and
parameter description
...Repeated item for example node 1, node 2, ..., node 12
8
ATCA-7350 Control via IPMI Programmer’s Reference (6806800H29E)
About this Manual
NotationDescription
.
.
.
..Ranges, for example: 0..4 means one of the integers
|Logical OR
Omission of information from example/command that is
not necessary at the time being
0,1,2,3, and 4 (used in registers)
Indicates a hazardous situation which, if not avoided,
could result in death or serious injury
Indicates a hazardous situation which, if not avoided,
may result in minor or moderate injury
Indicates a property damage message
Summary of Changes
This manual has been revised and replaces all prior editions.
Part NumberPublication DateDescription
6806800H29ADecember 2008First edition
6806800H29BJanuary 2009Second edition
6806800H29CJanuary 2009Third edition
6806800H29DFebruary 2009Fourth edition
6806800H29EAugust 2011Added Table 3-30 on page 47 and Ta b le
Comments and Suggestions
No danger encountered. Pay attention to important
information
3-31 on page 48.
We welcome and appreciate your comments on our documentation. We want to know what you
think about our manuals and how we can make them better.
Mail comments to us by filling out the following online form:
http://www.emersonnetworkpowerembeddedcomputing.com/ > Contact Us > Online Form
ATCA-7350 Control via IPMI Programmer’s Reference (6806800H29E)
9
About this Manual
In "Area of Interest" select "Technical Documentation". Be sure to include the title, part number,
and revision of the manual and tell us how you used it.
10
ATCA-7350 Control via IPMI Programmer’s Reference (6806800H29E)
Introduction
1.1Overview
The ATCA-7350 provides an intelligent hardware management system as defined in the
AdvancedTCA Base Specification (PICMG 3.0; AMC.0). This system implements an Intelligent
Peripheral Management Controller (IPMC) based on the proprietary H8S reference design from
American Megatrends Inc.
The ATCA-7350 IPMC supports all standard Intelligent Peripheral Management Interface (IPMI)
commands and provides hardware interfaces for other system managements features such as
hot-swap control, LED control, power control and temperature and voltage monitoring. The
IPMC also supports a Keyboard Controller Style (KCS) based host interface for payload-to-IPMI
communication.
1
In addition, the following features are included:
Table 1-1 Features
FeatureFurther Details...
Supported for fault tolerant field upgrade
Support for field updates of firmware via the payload
processor interface
Serial over LAN (SOL)Serial over LANon page 13
Sensor management including, among others, power
good and boot bank supervision sensor
FRU inventory with MAC address recordMAC Address Recordon page 13
Local system event log (SEL)Local System Event Logon page 14
External watchdogExternal Watchdogon page 14
BIOS boot configuration via IPMIBoot Configuration Parameterson page 14
IPMC Firmware Upgrade on page 12
Sensors on page 13
Chassis Device Commands on page 18
1.2Feature Description
Besides its basic functions, the ATCA-7350 provides the features described in this section.
1.2.1HPM.1 Specific Firmware Upgrades
ATCA-7350 Control via IPMI Programmer’s Reference (6806800H29E)
11
IntroductionHPM.1 Specific Firmware Upgrades
1.2.1.1IPMC Firmware Upgrade
The IPMC firmware basically consists of five major parts:
zBoot loader
zActive and Backup IPMI firmware
zActive and Backup SDR data
The boot loader maintains redundant copies of the firmware in the flash memory of the ATCA-
7350. Each time the IPMC firmware is upgraded, the most recent firmware version is kept in
flash memory and the older firmware version is overwritten by the new one. Once the new IPMI
firmware is programmed, the IPMC resets itself to boot from the new image. The boot loader
validates the new IPMC firmware. Provided the IPMC can power up successfully the current
image is made active and the previously active image is made backup. In case of power-up
failures, the boot loader automatically recovers from crisis and boots from the previous image.
The IPMC can be upgraded via KCS and IPMB interface. To ensure that the payload is not
interrupted during IPMC firmware upgrade, the IPMC is storing all operational information (Ekeying, SOL parameters, hot-swap state, last events to be queued, graceful shutdown timeout,
latest pin settings…) in non-volatile storage.
The IPMC firmware is fully HPM.1 compliant. Thus in general also open source tools like
ipmitool can be used for IPMC firmware upgrade. However, we recommend to use the firmware
upgrade tools provided by Emerson (fcu, fuf, or ipmi_upd.sh). To obtain these tools contact your
local sales representative.
The SDR data is hold as a separate component which can be upgraded separately. The IPMC
holds an active and a backup component.
1.2.1.2BIOS Upgrade
BIOS can either be upgraded via flash based tools provided from Emerson, or via IPMI with the
use of HPM.1 specific protocols. The BIOS firmware is fully implemented as HPM.1 specific
components with an active and an backup image. BIOS upgrade via IPMI is intended to be used
for crisis recovery only. This is because it is much more time consuming than using flash based
routines. Be aware that even when no BIOS boot bank is programmed at all (no boot loader)
crisis recovery via IPMI is always possible.
1.2.1.3FPGA Upgrade
The FPGA can be upgraded via IPMI also. The IPMC controls an active component and a
backup component for crisis recovery.
12
ATCA-7350 Control via IPMI Programmer’s Reference (6806800H29E)
Serial over LANIntroduction
1.2.2Serial over LAN
Serial over LAN (SOL) is an IPMI v.2.0 defined capability that allows to establish a virtual serial
console connection with the payload over LAN. The serial data of the payload is transferred to
the IPMC. The IPMC generates RMCP+ packets, which are routed to the ethernet controller of
the base interfaces. Be aware that SOL/LAN configuration is only possible if the Ethernet
controller and its payload is fully powered, otherwise the completion code 0xD5 is returned. For
more information on how to use and configure SOL see Chapter 4, SOL Module Configuration,
on page 53.
1.2.3Sensors
Apart from several voltage and temperature specific sensors (for details refer to Sensor Data
Records on page 29), the IPMC provides the following additional sensors:
Table 1-2 Sensors
Sensor Description
Firmware Progress, and Boot
Error Sensor
The IPMC firmware provides Firmware Progress (Table 3-24 on page
43), and Boot Error (Table 3-16 on page 37) sensors to enable
payload firmware and payload OS to report boot progress and OS
Boot via IPMI event messages.
1.2.4MAC Address Record
The ATCA-7350 implements an MAC address FRU OEM record. You can retrieve all MAC
addresses of the blade from the FRU information. For more details refer to MAC Address
Record on page 27.
1.2.5Asynchronous Event Notification
To enable payload applications to be informed about graceful shutdown/reboot requests, the
FRU Activate (Deactivate) and FRU Control (Graceful Reboot) command message is routed as
a LUN2 message to the payload interface.
If the payload application has registered to these commands via the OpenIPMI library, it gets
informed and can take all necessary actions before the payload is gracefully rebooted or shutdown.
1.2.6Graceful Shutdown Timeout
The IPMI command Set System Boot Options together with the parameter #98 can be used to
persistently specify the timeout for Graceful Shutdown. For more information refer to Chassis
Device Commands on page 18.
ATCA-7350 Control via IPMI Programmer’s Reference (6806800H29E)
13
IntroductionLocal System Event Log
1.2.7Local System Event Log
The IPMC provides a local system event log (SEL). Thus, event information is stored on-board
the ATCA-7350 as well.
1.2.8External Watchdog
For crisis recovery purposes the IPMI building block provides an external hardware watchdog.
The IPMI firmware is reset if it does not trigger the watchdog anymore.
1.2.9Boot Configuration Parameters
The IPMC supports BIOS boot order selection via IPMI partially. Be aware, that in case of the
BIOS boot order is selected via IPMI the boot order displayed in the BIOS menu doesn't reflect
the boot order selected via IPMI. For more information how to set the boot order via IPMI refer
to System Boot Option Commands, parameter #5.
14
ATCA-7350 Control via IPMI Programmer’s Reference (6806800H29E)
Supported Commands
2.1Standard IPMI Commands
The IPMC is fully compliant to the Intelligent Platform Management Interface v.1.5. This section
provides information about the supported IPMI commands.
2.1.1Global IPMI Commands
The IPMC supports the following global IPMI commands.
Table 2-1 Supported Global IPMI Commands
CommandNetFn (Request/Response) CMDComments
Get Device ID0x06/0x070x01-
2
Cold Reset0x06/0x070x02-
Warm Reset0x06/0x070x03-
Get Self Test Results0x06/0x070x04-
Get Device GUID0x06/0x070x08-
2.1.2System Interface Commands
The system interface commands are supported by blades providing a system interface.
Table 2-2 Supported System Interface Commands
CommandNetFn (Request/Response)CMD
Set BMC Global Enables0x06/0x070x2E
Get BMC Global Enables0x06/0x070x2F
Clear Message Flags0x06/0x070x30
Get Message Flags0x06/0x070x31
Get Message0x06/0x070x33
Send Message0x06/0x070x34
Set Channel Access0x06/0x070x40
Get Channel Access0x06/0x070x41
Get Channel Info 0x06/0x070x42
Set User Access 0x06/0x070x43
Get User Access 0x06/0x070x44
Set User Name0x06/0x070x45
ATCA-7350 Control via IPMI Programmer’s Reference (6806800H29E)
15
Supported CommandsWatchdog Commands
Table 2-2 Supported System Interface Commands (continued)
CommandNetFn (Request/Response)CMD
Get User Name 0x06/0x070x46
Set User Password 0x06/0x070x47
Set User Payload Access0x06/0x070x4C
Get User Payload Access0x06/0x070x4D
Set Channel Security Keys0x06/0x070x5C
2.1.3Watchdog Commands
The watchdog commands are supported by blades providing a system interface and a
watchdog type 2 sensor.
The pre-timeout option is not supported.
Table 2-3 Supported Watchdog Commands
CommandNetFn (Request/Response) CMD
Reset Watchdog Timer0x06/0x070x22
Set Watchdog Timer0x06/0x070x24
Get Watchdog Timer0x06/0x070x25
2.1.4SEL Device Commands
Table 2-4 Supported SEL Device Commands
CommandNetFn (Request/Response)CMD
Get SEL Info0x0A/0x0B0x40
Reserve SEL0x0A/0x0B0x42
Get SEL Entry0x0A/0x0B0x43
Add SEL Entry0x0A/0x0B0x44
Clear SEL0x0A/0x0B0x47
Get SEL Time0x0A/0x0B0x48
Set SEL Time0x0A/0x0B0x49
16
ATCA-7350 Control via IPMI Programmer’s Reference (6806800H29E)
FRU Inventory CommandsSupported Commands
2.1.5FRU Inventory Commands
Table 2-5 Supported FRU Inventory Commands
CommandNetFn (Request/Response) CMD
Get FRU Inventory Area Info0x0A/0x0B0x10
Read FRU Data0x0A/0x0B0x11
Write FRU Data0x0A/0x0B0x12
2.1.6Sensor Device Commands
Table 2-6 Supported Sensor Device Commands
NetFn
Command
(Request/Response) CMDComments
Get Device SDR Info0x04/0x050x20-
Get Device SDR0x04/0x050x21-
Reserve Device SDR Repository0x04/0x050x22-
Get Sensor Reading Factors0x04/0x050x23-
Set Sensor Hysteresis0x04/0x050x24-
Get Sensor Hysteresis0x04/0x050x25-
Set Sensor Threshold0x04/0x050x26-
Get Sensor Threshold0x04/0x050x27-
Set Sensor Event Enable0x04/0x050x28-
Get Sensor Event Enable0x04/0x050x29-
Get Sensor Event Status0x04/0x050x2B-
Get Sensor Reading0x04/0x050x2D-
Get Sensor Type0x04/0x050x2F-
Set Event Receiver0x04/0x050x00-
Get Event Receiver0x04/0x050x01-
Platform Event0x04/0x050x02-
ATCA-7350 Control via IPMI Programmer’s Reference (6806800H29E)
17
Supported CommandsChassis Device Commands
2.1.7Chassis Device Commands
Table 2-7 Supported Chassis Device Commands
CommandNetFn (Request/Response) CMD
Set System Boot Options0x00/0x010x08
Get System Boot Options0x00/0x010x09
2.1.7.1System Boot Options Commands
The IPMI system boot options commands allow you to control the boot process of a blade by
sending boot parameters to the blade’s boot firmware (for example BIOS, U-Boot or VxWorks).
The boot firmware interprets the sent boot parameters and executes the boot process
accordingly. Each boot parameter addresses a particular functionality and consists of a
sequence of one or more bytes. The IPMI specification assigns numbers to boot parameters.
Boot parameters 0 to 7 are standard parameters whose structure and functionality is defined
by the IPMI specification. The boot parameters 96 to 127 are OEM-specific which can be used
for different purposes.
The following table lists which boot properties can be configured and the corresponding boot
parameter number.
Table 2-8 Configurable System Boot Option Parameters
Configurable Boot PropertyCorresponding Boot Parameter Number
Boot flags5
Selection between default and backup boot flash as
device to boot from
Selection between default and backup EEPROM as
device where the on-board FPGA loads its configuration
stream from
Timeout for graceful shutdown98
Write Protection for BIOS boot banks and FRU
information
96
99
18
ATCA-7350 Control via IPMI Programmer’s Reference (6806800H29E)
Chassis Device CommandsSupported Commands
2.1.7.1.1System Boot Options Parameter #5
This boot parameter is implemented as specified within the IPMI specification, but not all flags
are supported.
Table 2-9 System Boot Options Parameter #5
Data ByteDescription
1[7] - 1b = boot flags valid. The bit should be set to indicate that valid flag data is
present. This bit may be automatically cleared based on the boot flag valid bit
clearing parameter, above.
[6] - Not supported.
[5] - Not supported
[4:0] - reserved
2[7] - 1b = CMOS clear
[6] - Not supported
[5:2] - Boot device selector
0000b = No override
0001b = Force PXE
0010b = Force boot from default Hard-drive
0011b = Not supported
0100b = Not supported
0101b = Force boot from default CD/DVD
0110b = Not supported
0111b-1110b = Reserved
1111b = Force boot from Floppy/primary removable media
[1] - 1b = Not supported
[0] - 1b = Not supported
3Not supported
4Not supported
5Reserved
ATCA-7350 Control via IPMI Programmer’s Reference (6806800H29E)
19
Supported CommandsChassis Device Commands
2.1.7.1.2System Boot Options Parameter #96
This boot parameter is an Emerson-specific OEM boot parameter. Its definition is given in the
following table.
Table 2-10 System Boot Options Parameter #96
Boot Option
Parameter DataDescription
1This parameter specifies the processor ID for which the boot option is to be set.
This parameter has to be 0 always for this blade.
2This parameter is used to select the BIOS boot bank of which the payload shall
There is no Set Selector or Block Selector with this command.
The System Boot Options parameter #96 is non-volatile. Its parameter data remains
preserved after IPMC power cycles and firmware upgrades.
2.1.7.1.3System Boot Options Parameter #98
This boot parameter is an Emerson-specific OEM parameter.
This timer specifies how long the IPMC waits for the payload to shut down gracefully. If the
payload software does not configure its OpenIPMI library to be notified for graceful shutdown
requests, the IPMC shuts down the payload when the timer expires.
Table 2-11 System Boot Options Parameter #98
Boot Option Parameter
DataDescription
1This parameter specifies the Graceful Shutdown Timeout LSB (given in
100 msec)
2This parameter specifies the Graceful Shutdown Timeout MSB (given in
100 msec)
20
ATCA-7350 Control via IPMI Programmer’s Reference (6806800H29E)
LAN Device CommandsSupported Commands
There is no Set Selector or Block Selector with this command.
The System Boot Options parameter #98 is non-volatile. Its parameter data remains
preserved after IPMC power cycles and firmware upgrades.
2.1.7.1.4System Boot Options #99
This parameter is an Emerson-specific OEM parameter. It is used to enable or disable BIOS
and FRU write protection
Table 2-12 System Boot Options Parameter #99
Boot Option Parameter
DataDescription
1This parameter enables/disables BIOS and FRU write protection:
[7:4] Bios ID (0= Boot Bank A, 1= Boot Bank B, 2= FRU information,
others reserved)
There is no Set Selector or Block Selector with this command. The Boot Option parameter data
returned with the IPMI command Get System Boot Options provides the write protect status of
the two BIOS flashes and of the FRU information (one byte for each instance).
2.1.8LAN Device Commands
Table 2-13 Supported LAN Device Commands
CommandNetFn (Request/Response)CMD
Set LAN Configuration Parameters0x0C/0x0D0x01
Get LAN Configuration Parameters0x0C/0x0D0x02
Set SOL Configuration Parameters0x0C/0x0D0x21
Get SOL Configuration Parameters0x0C/0x0D0x22
ATCA-7350 Control via IPMI Programmer’s Reference (6806800H29E)
21
Supported CommandsPICMG 3.0 Commands
2.2PICMG 3.0 Commands
The Emerson IPMC is a fully compliant AdvancedTCA intelligent Platform Management
Controller i.e. it supports all required and mandatory AdvancedTCA commands as defined in
the PICMG 3.0 specifications.
Table 2-14 Supported PICMG 3.0 Commands
NetFn
Command
Get PICMG Properties0x2C/0x2D0x00-
Get Address Info0x2C/0x2D0x01-
FRU Control0x2C/0x2D0x04-
Get FRU LED Properties0x2C/0x2D0x05-
Get FRU LED Color Capabilities0x2C/0x2D0x06-
Set FRU LED State0x2C/0x2D0x07-
Get FRU LED State0x2C/0x2D0x08-
Set IPMB State0x2C/0x2D0x09-
Set FRU Activation Policy0x2C/0x2D0x0A-
(Request/Response)CMDComments
Get FRU Activation Policy0x2C/0x2D0x0B-
Set FRU Activation0x2C/0x2D0x0C-
Get Device Locator Record ID0x2C/0x2D0x0D-
Set Port State0x2C/0x2D0x0E-
Get Port State0x2C/0x2D0x0F-
Compute Power Properties0x2C/0x2D0x10-
Set Power Level0x2C/0x2D0x11-
Get Power Level0x2C/0x2D0x12-
Get IPMB Link Info0x2C/0x2D0x18-
Set AMC Port State0x2C/0x2D0x19-
Get AMC Port State0x2C/0x2D0x1A-
Get FRU Control Capabilities0x2C/0x2D0x1E-
Get target upgrade capabilities0x2C/0x2D0x2E-
Get component properties0x2C/0x2D0x2F-
Abort firmware upgrade0x2C/0x2D0x30-
Initiate upgrade action0x2C/0x2D0x31-
Upload firmware block0x2C/0x2D0x32-
Finish firmware upload0x2C/0x2D0x33-
Get upgrade status0x2C/0x2D0x34-
22
ATCA-7350 Control via IPMI Programmer’s Reference (6806800H29E)
The firmware upgrade commands supported by the ATCA-7350 are implemented
according to the PICMG HPM.1 Revision 1.0 specification.
(Request/Response)CMDComments
2.3Emerson Specific Commands
The Emerson IPMC supports several commands which are not defined in the IPMI or PICMG
3.0 specification but are introduced by Emerson: serial output commands.
zBefore sending any of these commands, the shelf management software must
check whether the receiving IPMI controller supports Emerson specific IPMI
commands, by using the IPMI command 'Get Device ID'. Sending Emerson specific
commands to IPMI controllers which do not support these IPMI commands will lead
to no or undefined results.
zImplementing any of the Emerson specific IPMI commands means that the software
is not portable to other IPMI controllers that do not use the IPMC firmware.
Hysteresis Support0x00No Hysteresis or unspecified
ATCA-7350 Control via IPMI Programmer’s Reference (6806800H29E)
Sensor Data RecordsFRU Information and Sensor Data Records
Table 3-28 Log Disabled Sensor (continued)
FeatureRaw ValueDescription
Threshold Access Support0x00No Thresholds
Event Message Control0x00Per Threshold / Discrete State
Reading Definition--
Table 3-29 PwrOk Sig. Drop Sensor
FeatureRaw ValueDescription
Sensor NamePwrOk Sig. Drop-
Sensor LUN0x00-
Sensor Number0x12-
Entity ID0xA0PICMG Front Board
Sensor Type0x08Power Supply
Event/Reading Type0x6FDiscrete (sensor-specific)
Assertion Event Mask(Byte 15)0x03-
Assertion Event Mask(Byte 16)0x00-
Assertion Events--
-Event Offset: 0Presence detected
-Event Offset: 1Power supply failure detected
Deassertion Event Mask(Byte 17)0x00-
Deassertion Event Mask(Byte 18)0x00-
Threshold Mask(Byte 19)0x03-
Threshold Mask(Byte 20)0x00-
Base Unit0x00(unspecified)
Rearm mode0x01Auto
Hysteresis Support0x00No Hysteresis or unspecified
Threshold Access Support0x00No Thresholds
Event Message Control0x00Per Threshold / Discrete State
Reading Definition--
Table 3-30 RTM Handle Sensor
FeatureRaw Value Description
Sensor NameRTM Handle-
Sensor LUN0x00 -
Sensor Number0x30 -
Entity ID0xC0PICMG Rear Transition Module
Sensor Type 0xEBOEM reserved
ATCA-7350 Control via IPMI Programmer’s Reference (6806800H29E)
47
FRU Information and Sensor Data RecordsSensor Data Records
Table 3-30 RTM Handle Sensor (continued)
FeatureRaw Value Description
Event/Reading Type0x6FDiscrete (sensor-specific)
Assertion Event Mask (Byte 15)0x0F-
Assertion Event Mask (Byte 16) 0x00-
Assertion Events --
-Sensor Offset: 0Handle state ok (both in
open/close state)
-Sensor Offset: 1Upper handle closed
-Sensor Offset: 2Lower handle closed
Deassertion Event Mask (Byte 17)0x00-
Deassertion Event Mask (Byte 18)0x00-
Threshold Mask (Byte 19)0x0F-
Threshold Mask (Byte 20)0x00-
Base Unit0x00(unspecified)
Rearm mode0x01Auto
Hysteresis Support 0x00No Hysteresis or unspecified
Threshold Access Support0x00No Thresholds
Event Message Control 0x00Per Threshold / Discrete State
Reading Definition--
Table 3-31 RTM HS Sensor
Feature Raw ValueDescription
Sensor NameRTM HS-
Sensor LUN0x00-
Sensor Number0x31 -
Entity ID0xC0PICMG Rear Transition Module
Sensor Type0xF0PICMG 3.0: FRU HotSwap
Event/Reading Type0x6FDiscrete (sensor-specific)
Assertion Event Mask (Byte 15) 0xFF-
Assertion Event Mask (Byte 16)0x00-
48
Deassertion Event Mask (Byte
17)
Deassertion Event Mask (Byte
18)
Threshold Mask (Byte 19) 0xFF-
Threshold Mask (Byte 20)0x00 -
Base Unit 0x00 (unspecified)
ATCA-7350 Control via IPMI Programmer’s Reference (6806800H29E)
0x00-
0x00-
Sensor Data RecordsFRU Information and Sensor Data Records
Table 3-31 RTM HS Sensor (continued)
Feature Raw ValueDescription
Rearm mode0x01Auto
Hysteresis Support0x00No Hysteresis or unspecified
Threshold Access Support 0x00No Thresholds
Event Message Control0x00Per Threshold / Discrete State
Reading Definition-See PICMG 3.0 Specification,
chapter "Reading the FRU HotSwap Sensor"
Table 3-32 SYSTEM RESTART Sensor
FeatureRaw ValueDescription
Sensor NameSYSTEM RESTART-
Sensor LUN0x00-
Sensor Number0x1B-
Entity ID0xA0PICMG Front Board
Sensor Type0x1DSystem Boot Initiated
Event/Reading Type0x6FDiscrete (sensor-specific)
Assertion Event Mask(Byte 15)0x80-
Assertion Event Mask(Byte 16)0x00-
Assertion Events--
-Event Offset: 7System restart
Deassertion Event Mask(Byte 17)0x00-
Deassertion Event Mask(Byte 18)0x00-
Threshold Mask(Byte 19)0x80-
Threshold Mask(Byte 20)0x00-
Base Unit0x00(unspecified)
Rearm mode0x01Auto
Hysteresis Support0x00No Hysteresis or unspecified
Threshold Access Support0x00No Thresholds
Event Message Control0x00Per Threshold / Discrete State
Reading Definition--
Table 3-33 Ver Change Sensor
FeatureRaw ValueDescription
Sensor NameVer Change-
Sensor LUN0x00-
Sensor Number0x1C-
ATCA-7350 Control via IPMI Programmer’s Reference (6806800H29E)
49
FRU Information and Sensor Data RecordsSensor Data Records
Table 3-33 Ver Change Sensor (continued)
FeatureRaw ValueDescription
Entity ID0xA0PICMG Front Board
Sensor Type0x2BVersion Change
Event/Reading Type0x6FDiscrete (sensor-specific)
Assertion Event Mask(Byte 15)0x81-
Assertion Event Mask(Byte 16)0x00-
Assertion Events--
-Event Offset: 7Software or firmware change
detected with associated entity was
successful.
Deassertion Event Mask(Byte 17)0x00-
Deassertion Event Mask(Byte 18)0x00-
Threshold Mask(Byte 19)0x81-
Threshold Mask(Byte 20)0x00-
Base Unit0x00(unspecified)
Rearm mode0x01Auto
Hysteresis Support0x00No Hysteresis or unspecified
Threshold Access Support0x00No Thresholds
Event Message Control0x00Per Threshold / Discrete State
Reading Definition--
Table 3-34 Watchdog Sensor
FeatureRaw ValueDescription
Sensor NameWatchdog-
Sensor LUN0x00-
Sensor Number0x17-
Entity ID0xA0PICMG Front Board
Sensor Type0x23Watchdog 2
Event/Reading Type0x6FDiscrete (sensor-specific)
Assertion Event Mask(Byte 15)0x0F-
Assertion Event Mask(Byte 16)0x00-
Assertion Events--
-Event Offset: 0Timer expired, status only (no
action, no interrupt)
-Event Offset: 1Hard reset
50
-Event Offset: 2Power down
-Event Offset: 3Power cycle
Deassertion Event Mask(Byte 17)0x00-
ATCA-7350 Control via IPMI Programmer’s Reference (6806800H29E)
Sensor Data RecordsFRU Information and Sensor Data Records
Table 3-34 Watchdog Sensor (continued)
FeatureRaw ValueDescription
Deassertion Event Mask(Byte 18)0x00-
Threshold Mask(Byte 19)0x0F-
Threshold Mask(Byte 20)0x00-
Base Unit0x00(unspecified)
Rearm mode0x01Auto
Hysteresis Support0x00No Hysteresis or unspecified
Threshold Access Support0x00No Thresholds
Event Message Control0x00Per Threshold / Discrete State
Reading Definition-See IPMI 1.5 Specification
ATCA-7350 Control via IPMI Programmer’s Reference (6806800H29E)
51
FRU Information and Sensor Data RecordsSensor Data Records
52
ATCA-7350 Control via IPMI Programmer’s Reference (6806800H29E)
SOL Module Configuration
4.1Introduction
This chapter includes the following sections:
zConfigure the SOL
zEnable SOL load
zSetup a SOL session
zQuery the configuration of SOL
zConfigure the SOL mode in OS
4
4.2Configure the SOL
Before the configuration, the IPMC has no user or IP address, so you cannot connect to the
IPMC through IPMITOOL. In this case, you need to use IPMI commands through the IPMB
channel of the shelf managers to configure the SOL and set the IPMC.
The IPMB address is the hardware address marked on the shelf multiplied by 2.
Configuring SOL
Perform the following six steps to configure the SOL:
1. Set the IP addresses of the two channels.
Use the command Set LAN Configuration Parameters of IPMI2.0 with Parameter
selector of 3.
See table 23-2 in section 23.1 of the IPMI 2.0 specification.
The value of Parameter selector is 3.
For example, on Emerson shelf manager, set the IP address of channel 1 to
172.17.10.78 and that of channel 2 to 172.18.10.78.
ipmicmd -k "0 90 0 0c 01 01 03 ac 11 0a 4e" smi 0
ipmicmd -k "0 90 0 0c 01 02 03 ac 12 0a 4e" smi 0
ATCA-7350 Control via IPMI Programmer’s Reference (6806800H29E)
53
SOL Module ConfigurationEnable SOL Load
"90" is the IPMB address of the blade.
The IP addresses of the two channels cannot be set to be in the same network
segment. Otherwise, the settings fail.
2. Set the subnet mask of the two channels.
Use the command Set LAN Configuration Parameters of IPMI2.0 with Parameter
selector of 6.
The value of Parameter selector is 6.
See table 23-4 in section 23.2 of the IPMI 2.0 specification.
For example, on Emerson shelf manager, set the subnet masks of both channel 1
and channel 2 to 255.255.0.0.
ipmicmd -k "0 90 0 0c 01 01 06 ff ff 00 00" smi 0
ipmicmd -k "0 90 0 0c 01 02 06 ff ff 00 00" smi 0
"90" is the IPMB address of the blade.
3. Set the user name.
Use the command Set User Name of IPMI2.0.
See table 23-32 in section 23.28 of the IPMI 2.0 specification.
For example, on Emerson shelf manager, set the user name to solusername.
ipmicmd -k "0 90 0 06 45 02 73 6f 6c 75 73 65 72 6e 61 6d 65" smi 0
4. Set the password.
Use the command Set User Password of IPMI2.0.
See table 23-34 in section 23.30 of the IPMI 2.0 specification.
For example, on Emerson shelf manager, set the password to soluserpassword.
ipmicmd -k "0 90 0 06 47 82 02 73 6f 6c 75 73 65 72 70 61 73 73 77 6f 72 64" smi 0
5. Set the user right.
Use the command Set User Access Command of IPMI2.0.
For example, on Emerson shelf manager, set the right of user 2 to Administrator (4).
ipmicmd -k "0 90 0 06 43 f1 02 04 00" smi 0
6. Enable the user.
Use the command Set User Password Command of IPMI2.0.
For example, on Emerson shelf manager, enable user 2.
ipmicmd -k "0 90 0 06 47 82 01" smi 0
4.3Enable SOL Load
Use the command Set SOL Configuration Parameters of IPMI2.0. The value of Parameter
selector is 1.
See table 26-3 in section 26.2 of the IPMI 2.0 specification.
54
ATCA-7350 Control via IPMI Programmer’s Reference (6806800H29E)
Setup SOL SessionSOL Module Configuration
The value of Parameter selector is 1.
See table 26-5 in section 26.3 of the IPMI 2.0 specification.
On Emerson shelf manager, enable the SOL of channel 1.
ipmicmd -k "0 90 0 0c 21 01 01 01" smi 0
4.4Setup SOL Session
After the previous seven steps, you can set up a session or an SOL connection to the IPMC
through IPMITOOL. You can use the commands provided by IPMITOOL to directly configure
the SOL for the IPMC.
If a shelf manager supports automatic configuration through the script, you can use the script
to configure the SOL directly. For example, in the command line of Emerson shelf manager, run
the commands sv_stop and sv_start to restart the script and configure the SOL automatically.
After that, you can use the SOL without configuring and modifying it.
4.5Query the Configuration of SOL
Querying the configuration of SOL
To query the configurations, do the following:
1. Query the IP address.
Use the command Get LAN Configuration Parameters.
See table 23-3 in section 23.2 of the IPMI 2.0 specification.
The value of Parameter selector is 3.
For example, on Emerson shelf manager, query the IP address of channel 1.
ipmicmd -k "0 90 0 0c 02 01 03 00 00" smi 0
"90" is the IPMB address of the blade.
2. Query the subnet mask.
Use the command Get LAN Configuration Parameters.
The value of Parameter selector is 6.
For example, on Emerson shelf manager, query the subnet mask of channel 1.
ipmicmd -k "0 90 0 0c 02 01 06 00 00" smi 0
3. Query the user name.
Use the command Get User Name.
See table 22-33 in section 22.29 of the IPMI 2.0 specification.
For example, on Emerson shelf manager, query the name of the user 2.
ipmicmd -k "0 90 0 06 46 02 " smi 0
4. Query the channel information.
Use the command Get Channel Access.
ATCA-7350 Control via IPMI Programmer’s Reference (6806800H29E)
55
SOL Module ConfigurationQuery the Configuration of SOL
See table 22-27 in section 22.23 of the IPMI 2.0 specification.
For example, on Emerson shelf manager, query the information about channel 1.
ipmicmd -k "0 90 0 06 41 01 40" smi 0
5. Query the user right.
Use the command Get User Access.
See table 22-31 in section 22.27 of the IPMI 2.0 specification.
For example, on Emerson shelf manager, query the right of user 2 in channel 1.
ipmicmd -k "0 90 0 06 44 01 02" smi 0
If a session can be set up between the IPMITOOL and IPMC, you can query the information
through IPMITOOL. For example, query network configuration information.
IP Header : TTL=0x40 Flags=0x40 Precedence=0x00 TOS=0x10
IPMC ARP Control : ARP Responses Enabled, Gratuitous ARP Enabled
Gratituous ARP Intrvl : 2.0 seconds
Default Gateway IP : 172.17.166.55
RMCP+ Cipher Suites :
Cipher Suite Priv Max : uuuaXXXXXXXXXXX
: X=Cipher Suite Unused
: c=CALLBACK
: u=USER
: o=OPERATOR
56
: a=ADMIN
: O=OEM
For details on how to query and set by IPMITOOL, refer to the documents related to IPMITOOL.
ATCA-7350 Control via IPMI Programmer’s Reference (6806800H29E)
Configure the SOL Module in OSSOL Module Configuration
4.6Configure the SOL Module in OS
All the configurations and the queries example above are carried out on the shelf manager of
Emerson. If you want to do it in OS with standard IPMI tools by sending the IPMI command to
the IPMC through KCS, some parameters of the command should be modified.
For example, we set the IP address of channel 1:
Emerson shelf manager:
ipmicmd -k "0 90 0 0c 01 01 03 ac 11 0a 4e" smi 0
Linux OS:
ipmicmd -k "f 0 0c 01 01 03 ac 11 0a 4e" smi 0
The identification section is different while the other parameters are the same, where "f" is the
sending address of local KCS, "0" is the logic unit number.
ATCA-7350 Control via IPMI Programmer’s Reference (6806800H29E)
57
SOL Module ConfigurationConfigure the SOL Module in OS
58
ATCA-7350 Control via IPMI Programmer’s Reference (6806800H29E)
ARelated Documentation
A
A.1Emerson Network Power - Embedded Computing
Documents
The Emerson Network Power - Embedded Computing publications listed below are referenced
in this manual. You can obtain electronic copies of Emerson Network Power - Embedded
Computing publications by contacting your local Emerson sales office. For documentation of
final released (GA) products, you can also visit the following website:
http://www.emersonnetworkpowerembeddedcomputing.com > Resource Center > Technical
Documentation Search. This site provides the most up-to-date copies of Emerson Network
Power - Embedded Computing product documentation.
Table A-1 Related Documentation
Document TitlePublication Number
ATCA-7150 Installation and Use6806800E88
ATCA-7350 Installation and Use6806800H59
RTM-ATCA-7350 Installation and Use6806800H30
ATCA-7150: Control via IPMI Programmer’s Reference6806800E85
For additional information, refer to the following table for related specifications. As an additional
help, a source for the listed document is provided. Please note that, while these sources have
been verified, the information is subject to change without notice.