Справочник Пользователя для Intel SE7520JR2
Intel® Server Board SE7520JR2
Platform Management
Revision 1.0
C78844-002
133
5.3.12
Field Replaceable Unit (FRU) Inventory Devices
An enterprise-class system typically has FRU information for each major system board,
(processor board, memory board, I/O board, etc.). The FRU data includes information such as
serial number, part number, model, and asset tag. This information can be accessed in two
ways: through IPMI FRU commands or by using Master Write-Read commands.
(processor board, memory board, I/O board, etc.). The FRU data includes information such as
serial number, part number, model, and asset tag. This information can be accessed in two
ways: through IPMI FRU commands or by using Master Write-Read commands.
The mBMC provides FRU device command access to its own FRU device. The mBMC
implements the interface for logical FRU inventory devices as specified in the Intelligent
Platform Management Interface Specification, Version 1.5. This functionality provides
commands used for accessing and managing the FRU inventory information associated with the
mBMC (FRU ID 0). These commands can be delivered over the Host and LAN channel
interfaces.
implements the interface for logical FRU inventory devices as specified in the Intelligent
Platform Management Interface Specification, Version 1.5. This functionality provides
commands used for accessing and managing the FRU inventory information associated with the
mBMC (FRU ID 0). These commands can be delivered over the Host and LAN channel
interfaces.
5.3.12.1
mBMC FRU Inventory Area Format
The mBMC FRU inventory area format follows the Platform Management FRU Information
Storage Definition. See the Platform Management FRU Information Storage Definition, Version
1.0 for details.
Storage Definition. See the Platform Management FRU Information Storage Definition, Version
1.0 for details.
The mBMC provides only low-level access to the FRU inventory area storage. It does not
validate or interpret the data that is written. This includes the common header area. Applications
cannot relocate or resize any FRU inventory areas.
validate or interpret the data that is written. This includes the common header area. Applications
cannot relocate or resize any FRU inventory areas.
5.3.13 NMI
Generation
The mBMC-generated NMI pulse duration is 200 ms. The following may cause the mBMC to
generate an NMI pulse:
generate an NMI pulse:
•
Receiving a Chassis Control command issued from one of the command interfaces. Use of
this command will not cause an event to be logged in the SEL.
this command will not cause an event to be logged in the SEL.
•
Detecting that the control panel Diagnostic Interrupt button has been pressed. Use of this
command will cause a button event to be logged into the SEL Type code - 13h (Critical
Interrupt), Sensor Specific offset – 6Fh
command will cause a button event to be logged into the SEL Type code - 13h (Critical
Interrupt), Sensor Specific offset – 6Fh
•
A PEF table entry matching an event where the filter entry has the NMI action indicated.
•
Watchdog timer pre-timeout expiration with NMI pre-timeout action enabled.
Once an NMI has been generated by the mBMC, the mBMC will not generate another until the
system has been reset or powered down.
system has been reset or powered down.
5.3.14 SMI
Generation
The mBMC can be configured to generate an SMI due to Watchdog timer pre-timeout expiration
with SMI pre-timeout interrupt specified.
with SMI pre-timeout interrupt specified.
5.3.15
Event Message Reception
The mBMC supports externally (e.g., BIOS) generated events via the Platform Event Message
command. Events received via this command will be logged to the SEL and processed by PEF.
command. Events received via this command will be logged to the SEL and processed by PEF.