Specifications

Processor Presence and Population Check QSSC-S4R Technical Product Specification
282
24.25.6 Power Unit Redundancy
The BMC supports redundant power sub-systems and implements a Power Unit Redundancy sensor per platform. A
Power Unit Redundancy sensor is of sensor type Power Unit (09h) and reading type Availability Status (0Bh). This
sensor generates events when a power sub-system transitions between redundant and non-redundant states, as
determined by the number and health of the power subsystem’s component power supplies. The definition of
redundancy is power subsystem dependent and sometimes even configuration dependent.The BMC allows
redundancy to be configured on a per power-unit-redundancy sensor basis via the OEM SDR records.
24.26 3.28 Event Message Generation and Reception
The BMC cannot be configured to act as an event generator on the IPMB, so the BMC does not accept the Set Event
Receiver
command. The BMC does respond to the Get Event Receiver command.
24.27 3.29 Event Logging Disabled Sensor
The BMC implements an Event Logging Disabled type (10h) sensor that is event only. It supports offset 02h – Log
Area (SEL) Reset / Clear. Only assertion events are logged for this sensor.
24.28 3.30 SMI Timeout Sensor
The BMC supports an SMI timeout sensor (sensor type OEM (F3h), event type Discrete (03h)) that asserts if the SMI
signal has been asserted for more than 90 seconds. A continuously asserted SMI signal is an indication that the BIOS
cannot service the condition that caused the SMI. This is usually because that condition prevents the BIOS from
running.
When an SMI timeout occurs, the BMC asserts the SMI timeout sensor and logs a SEL event for that sensor. The BMC
will also reset the system.
24.29 BMC Self Test
The BMC performs tests as part of its initialization. If a failure is determined, such as a corrupt BMC SDR, then the
BMC stores the error internally. BMC or BMC subsystem failures detected during regular BMC operation may also be
stored internally. The IPMI 2.0 Get Self Test Results command can be used to return the first error detected.
Table 187 shows self-test errors that may be posted. Self test result monitoring occurs when the applicable subsystem
is accessed. This happens both at runtime and at BMC initialization.
Table 187. BMC Self Test Results
First
Byte
Second
Byte
Description Performed
During BMC
Init
55h 00h No error detected N/A
57h 01h BMC operational code corrupted Yes
57h 02h BMC boot / firmware update code
corrupted
Yes
57h 08h SDR repository empty Yes
57h 10h IPMB Signal Error No
57h 20h BMC FRU device inaccessible Yes
57h 40h BMCSDR repository inaccessible Yes
57h 80h BMC SEL device inaccessible Yes
24.30 BMC Test Commands
For hardware and manufacturing test purposes, there are two Intel General Application net function commands: Get
SM Signal (14h) and Set SM Signal (15h). These commands can be used to force the front panel LED and fan speed
state, and to sense the state of the front panel buttons without causing the BMC firmware to act on changes to them
(button pushes).
Each command request takes a signal type, a signal instance (to allow for supporting multiple signals of a particular
type), and an action to perform. The signal types are guaranteed to be consistent across platforms, although some
platforms may introduce new signal types for platform-specific signals that can be accessed by these commands and
may not provide support for others that are not appropriate for the platform.