User's Manual

This example configures general platform event trap settings and trap destination number 1 and commits the
transaction:
Server# scope fault
Server /fault # scope pef-destination 1
Server /fault /pef-destinations *# set enabled yes
Server /fault /pef-destinations *# set addr 1.2.3.4
Server /fault /pef-destinations *# commit
Server /fault /pef-destinations # show
Trap Destination 1:
IP Address: 1.2.3.4
Enabled: yes
Server /fault /pef-destinations #
Interpreting Platform Event Traps
A CIMC platform event alert contains an enterprise object identifier (OID) in the form
1.3.6.1.4.1.3183.1.1.0.event. The first ten fields of the OID represent the following information:
iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).wired_for_management(3183).PET(1).version(1).version(0),
indicating an IPMI platform event trap (PET) version 1.0 message. The last field is an event number, indicating
the specific condition or alert being notified.
Platform Event Trap Descriptions
The following table provides a description of the event being notified in a platform event trap message, based
on the event number in the trap OID.
Platform Event DescriptionEvent Number [Note 1]
Test Trap0h0
Temperature Warning010107h65799
Temperature Critical010109h65801
Under Voltage, Critical020102h131330
Voltage Critical020109h131337
Current Warning030107h196871
Fan Critical040102h262402
Processor related (IOH-Thermalert/Caterr sensor) – predictive failure
deasserted
070400h459776
Processor related (IOH-Thermalert/Caterr sensor) – predictive failure
asserted
070401h459777
Processor Power Warning – limit not exceeded
070500h460032
Processor Power Warning – limit exceeded
070501h460033
Power Supply Critical0800F5h524533
Power Supply Warning080107h524551
Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.5
OL-28893-01 153
Configuring Platform Event Filters
Interpreting Platform Event Traps