Table 32: fan presence sensors, Event trigger offset – next steps – Kontron S4600 SEL Troubleshooting User Manual
Page 57

System Event Log Troubleshooting Guide for EPSD
Platforms Based on Intel
®
Xeon
®
Processor E5 4600/2600/2400/1600/1400 Product Families
Cooling Subsystem
Revision 1.1
Intel order number G90620-002
47
Byte
Field
Description
14
Event Data 1
[7:6]
– 00b = Unspecified Event Data 2
[5:4]
– 00b = Unspecified Event Data 3
[3:0]
– Event Trigger Offset as described in Table 32
15
Event Data 2
Not used
16
Event Data 3
Not used
The following table describes the severity of each of the event triggers for both assertion and deassertion.
Table 32: Fan Presence Sensors – Event Trigger Offset – Next Steps
Event Trigger Offset
Assertion
Severity
Deassert
Severity
Description
Next Steps
Hex
Description
01h
Device
Present
OK
Degraded
Assertion
–A fan was inserted. This
event may also get logged when the
BMC initializes when AC is applied.
Informational only
Deassert
– A fan was removed, or
was not present at the expected
location when the BMC initialized.
These events only get generated in the systems with hot-swappable fans,
and normally only when a fan is physically inserted or removed. If fans
were not physically removed:
1. Use the Quick Start Guide to check whether the right fan
headers were used.
2. Swap the fans round to see whether the problem stays with the
location or follows the fan.
3. Replace the fan or fan wiring/housing depending on the outcome
of step 2.
4. Ensure the latest FRUSDR update has been run and the correct
chassis is detected or selected.
Table 33: Fan Redundancy Sensors Typical Characteristics
Byte
Field
Description
11
Sensor Type
04h = Fan
12
Sensor Number
0Ch