Specifications

5
Managing Alarms and Events
88
Collecting information for the alarm configuration file
ForeachtypeofFRUandeachsensorforwhichyouwill assignseverities,youmustprovide
identifyinginformation.Table 10explainshowtoobtaintheinformationtoidentifytheFRU
type.
Table 10. Information needed to identify a FRU type
FRU information needed Method for obtaining it Notes
Manufacturer ID From the module’s Linux prompt, enter:
rsys‐ipmitool‐t
<FRU_IPMB_addr> mcinfo
The manufacturer ID and the firmware revision
are shown in decimal, and the product ID is
shown in both decimal and hex. Either the
decimal or hex value can be used in the
configuration file. A prefix of 0x must precede
any hex value.
Product ID
Firmware revision
a
Site type See Resource types of slots and FRUs in
the RPT on page 135.
For non-intelligent FRUs, use the site type of the
proxy FRU that represents it.
a
TheneweventseverityisassignedonlytoFRUswiththelistedfirmwareversionoralater
version.Forexample,ifthefirmwareversionislistedas3.0,theeventseveritywouldbeassigned
toanyFRUwithafirmwareversionof3.0orlater,suchas3.1,3.2,and3.2.4.3.