15Module Management LED Functions ........................................................... 47
ID 1052-3624, Rev. 1.0Page 7
PrefaceAM4022
This page has been intentionally left blank.
Page 8ID 1052-3624, Rev. 1.0
AM4022IPMI Firmware
1.Introduction
1.1Terminology and Acronym Definitions
The following table provides descriptions for terms and acronyms used in this guide. The descriptions are derived primarily from the IPMI specifications.
Table 1:Terminology and Acronym Definitions
TERM/ ACRONYMDESCRIPTION
AMCAdvanced Mezzanine Card
BSPBoard Support Package
DMIDesktop Management Interface
FRUField Replaceable Unit
FWHFirmware Hub
2
I
C
IPMBIntelligent Platform Management Bus
IPMB-0AdvancedTCA shelf-level IPMB
IPMB-LLocal, on-carrier IPMB that links the carrier IPMC with the MMCs of installed modules
IPMCIntelligent Platform Management Controller located on the AMC carrier
IPMIIntelligent Platform Management Interface
IOLIPMI over LAN. An MMC is accessed via LAN, not IPMB.
KCSKeyboard Controller Style
MMCModule Management Controller – an IPMI controller located on the AMC module
MPManagement Power
PICMGPCI Industrial Computer Manufacturer Group
PWRPayload Power
SDRSensor Data Record
Inter-Integrated Circuit
SDRRSensor Data Record Repository
SELSystem Event Log
SMBIOSSystem Management BIOS
SMSSystem Management Software (designed to run under the OS)
SOLSerial over LAN. A serial interface is redirected by LAN using the RMCP+ protocol.
ID 1052-3624, Rev. 1.0Page 9
IPMI FirmwareAM4022
1.2Related Publications
The following publications contain information relating to this product.
Table 2:Related Publications
PRODUCTPUBLICATION
IPMIIPMI Specification V2.0
IPMIIPMI - Platform Management FRU Information Storage Definition v1.0,
As a hot-swappable field-replaceable unit (FRU), the AM4022 follows the stringent carrier
grade RASM feature set, namely - Reliability, Availability, Serviceability, Maintainability.
Built in accordance with the AMC.0 specification, the AM4022 is also compliant with the AMC.1,
AMC.2, and AMC.3 specifications and is easily managed via its IPMI v2.0-compliant management features.
As with every Advanced Mezzanine Card (AMC), the AM4022 is equipped with a Module Management Controller (MMC).
1.3IPMI in AdvancedMC / AdvancedTCA Environment
The Module Management Controller is a crucial component of any AMC module. Besides acting as a regular IPMI management controller (sensor monitoring, event logging, etc.), it also
provides an interface to all necessary data related to module power requirements and implemented interfaces (E-Keying). Further, it plays an active role in the module hot swap state management. The carrier IPMI Controller (IPMC) communicates with the MMC using the local IPMB
(IPMB-L) bus. In an ATCA/AMC environment, it is the IPMC that actually turns on/off module
(payload) power. However, before the IPMC enables the module payload power, various criteria must be satisfied by both the carrier and the module, including power requirements and capabilities, matching interfaces, current module hot swap state, and any other special conditions
as specified by the Shelf Manager policy.
Page 10ID 1052-3624, Rev. 1.0
AM4022IPMI Firmware
1.4Module Management Controller Hardware
On the AM4022 processor AMC module, the MMC is implemented using an NXP® ARM7 microcontroller with 512 kB of internal flash and 56 kB of RAM.
An external 64 kB serial EEPROM chip is used for firmware private data and for FRU inventory
storage. An additional external 4 MB serial SPI flash is used for redundant firmware image storage.
The MMC implements one local Keyboard Controller Style (KCS) interface with interrupt support for communication with the system side management software and the uEFI BIOS. The
IPMB-L bus is used for interconnection with the IPMC.
IPMI over LAN (IOL) and Serial Over LAN (SOL) are supported on all four Ethernet channels
of the module. SOL is only available on one Ethernet channel at a time.
The MMC provides access to various sensors which permit the monitoring of:
•System power voltages: +12V (PWR), +5V, +3.3V, +3.3V (MP)
•Temperatures: CPU and PCH die as well as airflow near AMC edge-connector
•Power Good, LAN links, IPMB link, board reset, POST code, boot error, CPU States (processor hot, THERMTRIP, …), IPMB-L state, Health error, IPMI watchdog, etc.
2.MMC Firmware
2.1Key Features
The following are key features of the AM4022 MMC firmware:
•Compliant with the related IPMI and PICMG® specifications
•Firmware designed and specially made for AdvancedMC environments (ATCA, µTCA)
•Supports one KCS interface with interrupt support
•Supports the local IPMB (IPMB-L) interface
•Out-of-Band management and monitoring using IPMB-L interface permits access to
sensors regardless of the module’s CPU state
•Sensor thresholds fully configurable
•Sensor names prefixed with AMC module Bay ID (A1…4, B1…4)
•Usable in µTCA slots 1…12. Sensor names for slots 9…12 are prefixed with C1…C4
•Complete IPMI watchdog functionality
•Complete FRU functionality
•Firmware can be updated in the field
•Firmware image management may done by the open tool “ipmitool” (functions “hpm” or
“fwum”)
•Downloading new firmware image does not break currently running firmware activities
•Manual firmware image roll-back in case of upgrade failure
•Interoperable with other AMC, ATCA, or IPMI solutions
ID 1052-3624, Rev. 1.0Page 11
IPMI FirmwareAM4022
•Fail-over control to a recovery BIOS in the event a non-working uEFI BIOS is detected
•OEM commands for uEFI BIOS firmware bank selection and uEFI BIOS boot order
override
•IPMI over LAN (IOL) support
•Serial over LAN (SOL) support
•Graceful shutdown support
•The “Health” LED indicates whether the module is healthy (normal operation) and all
sensors are within the specified range (green) or at least one sensor is out of range
(amber).
2.2Supported IPMI and ATCA Commands
2.2.1Standard IPMI Commands
The following table shows an excerpt from the command list specified in the IPMI specification
2.0. The shaded table cells indicate commands supported by the AM4022 MMC.
M = mandatory, O = optional
Table 3:Standard IPMI Commands
IPMI 2.0
COMMAND
SPEC.
NETFNCMD
SECTION
IPM DEVICE “GLOBAL” COMMANDSM
Get Device ID20.1App01h
Cold Reset20.2App02h
Warm Reset20.3App03hO / No
Get Self Test Results20.4App04h
Manufacturing Test On20.5App05hO / No
Set ACPI Power State20.6App06hO / No
Get ACPI Power State20.7App07hO / No
Get Device GUID20.8App08hO / No
KONTRON
SUPPORT
ON MMC
M / Yes
O / Yes
O / Yes
Broadcast “Get Device ID”20.9App01h
BMC WATCHDOG TIMER COMMANDS
Reset Watchdog Timer27.5App22h
Set Watchdog Timer27.6App24h
Get Watchdog Timer27.7App25h
Page 12ID 1052-3624, Rev. 1.0
M / Yes
O
O / Yes
O / Yes
O / Yes
AM4022IPMI Firmware
Table 3:Standard IPMI Commands (Continued)
IPMI 2.0
COMMAND
SPEC.
NETFNCMD
SECTION
BMC DEVICE AND MESSAGING COMMANDSO
Set BMC Global Enables22.1App2Eh
Get BMC Global Enables22.2App2Fh
Clear Message Flags22.3App30h
Get Message Flags22.4App31h
Enable Message Channel Receive22.5App32h
Get Message22.6App33h
Send Message22.7App34h
Read Event Message Buffer22.8App35h
Get BT Interface Capabilities22.9App36hO / No
Get System GUID22.14App37hO / No
KONTRON
SUPPORT
ON MMC
O / Yes
O / Yes
O / Yes
O / Yes
O / Yes
O / Yes
O / Yes
O / Yes
Get Channel Authentication Capabilities22.13App38h
Get Session Challenge22.15App39h
Activate Session22.17App3Ah
Set Session Privilege Level22.18App3Bh
Close Session22.19App3Ch
Get Session Info22.20App3Dh
Get AuthCode22.21App3FhO / No
Set Channel Access22.22App40h
Get Channel Access22.23App41h
Get Channel Info22.24App42h
Set User Access22.26App43h
Get User Access22.27App44h
Set User Name22.28App45h
Get User Name22.29App46h
O / Yes
O / Yes
O / Yes
O / Yes
O / Yes
O / Yes
O / Yes
O / Yes
O / Yes
O / Yes
O / Yes
O / Yes
O / Yes
Set User Password22.30App47h
ID 1052-3624, Rev. 1.0Page 13
O / Yes
IPMI FirmwareAM4022
Table 3:Standard IPMI Commands (Continued)
IPMI 2.0
COMMAND
SPEC.
NETFNCMD
SECTION
Activate Payload24.1App48h
Deactivate Payload24.2App49h
Get Payload Activation Status24.4App4Ah
Get Payload Instance Info24.5App4Bh
Set User Payload Access24.6App4Ch
Get User Payload Access24.7App4Dh
Get Channel Payload Support24.8App4Eh
Get Channel Payload Version24.9App4Fh
Get Channel OEM Payload Info24.10App50hO / No
Master Write-Read22.11App52h O / No
Get Channel Cipher Suits22.15App54hO / No
KONTRON
SUPPORT
ON MMC
O / Yes
O / Yes
O / Yes
O / Yes
O / Yes
O / Yes
O / Yes
O / Yes
Suspend/Resume Payload Encryption24.3App55h
Set Channel Security Keys22.25App56hO / No
Get System Interface Capabilities22.9App57hO / No
CHASSIS DEVICE COMMANDSO
Get Chassis Capabilities28.1Chassis00h
Get Chassis Status28.2Chassis01h
Chassis Control28.3Chassis02h
Chassis Reset28.4Chassis03hO / No
Chassis Identify28.5Chassis04hO / No
Set Chassis Capabilities28.7Chassis05hO / No
Set Power Restore Policy28.8Chassis06hO / No
Get System Restart Cause28.11Chassis07hO / No
Set System Boot Options28.12Chassis08hO / No
O / Yes
O / Yes
O / Yes
O / Yes
Get System Boot Options28.13Chassis09hO / No
Get POH Counter28.14Chassis0Fh
Page 14ID 1052-3624, Rev. 1.0
O / Yes
AM4022IPMI Firmware
Table 3:Standard IPMI Commands (Continued)
IPMI 2.0
COMMAND
SPEC.
NETFNCMD
SECTION
EVENT COMMANDSM
Set Event Receiver29.1S/E00h
Get Event Receiver29.2S/E01h
Platform Event (a.k.a. “Event Message”)29.3S/E02h
PEF AND ALERTING COMMANDSO
Get PEF Capabilities30.1S/E10hO / No
Arm PEF Postpone Timer30.2S/E11hO / No
Set PEF Configuration Parameters30.3S/E12hO / No
Get PEF Configuration Parameters30.4S/E13hO / No
Set Last Processed Event ID30.5S/E14hO / No
Get Last Processed Event ID30.6S/E15hO / No
KONTRON
SUPPORT
ON MMC
M / Yes
M / Yes
M / Yes
Alert Immediate30.7S/E16hO / No
PET Acknowledge30.8S/E17hO / No
SENSOR DEVICE COMMANDSM
Get Device SDR Info35.2S/E20h
Get Device SDR35.3S/E21h
Reserve Device SDR Repository35.4S/E22h
Get Sensor Reading Factors35.5S/E23hO / No
Set Sensor Hysteresis35.6S/E24h
Get Sensor Hysteresis35.7S/E25h
Set Sensor Threshold35.8S/E26h
Get Sensor Threshold35.9S/E27h
Set Sensor Event Enable35.10S/E28h
Get Sensor Event Enable35.11S/E29h
M / Yes
M / Yes
M / Yes
O / Yes
O / Yes
O / Yes
O / Yes
O / Yes
O / Yes
Re-arm Sensor Events35.12S/E2AhO / No
ID 1052-3624, Rev. 1.0Page 15
Loading...
+ 33 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.