Specifications

5
Managing Alarms and Events
89
Table 11liststheinformationneededtoidentifythesensor,theeventstate,andthenew
severitytoassign.
Table 11. Information needed to identify a sensor and event state
Sensor information
needed
Method for obtaining it Notes
Sensor index Retrieve a list of the FRU’s sensors from the RPT using an HPI
application.
For example, from the module’s Linux prompt, use the hpiapp
example application as follows:
1. Start the application by entering:
hpiapp
2. Identify the FRU’s resource ID by entering:
3
0
3. Request a sensor list by entering:
q
s
b
4. When prompted, enter the resource ID.
The sensor index is based on the order of the sensors in
the resource presence table. To identify the sensor
index, assign numbers to the list of sensors, starting
with 0 (zero) at the top of the list.
Alternatively, retrieve the sensor list using the CLI:
1. Access the platform-management CLI as described in
Accessing the platform-management CLI on page 56.
2. Specify the applicable FRU type. For example, for a front
module, enter:
front<number>
3. Request a sensor list. Enter:
showsensorsall
The CLI lists the sensors in the reverse order from their
order in the resource presence table. To identify the
sensor index, assign numbers to the sensors, starting
with 0 (zero) at the bottom of the list and moving to the
top.
Event state See the reference manual for the FRU to locate the numeric
event state values for the sensor. For shelf-specific FRUs such
as PEMs and fans, see the reference manual for the platform.
For non-intelligent FRUs associated with the shelf, look
for their sensors in the manual that covers the proxy (for
example, refer to the appropriate Shelf Peripheral
Module Hardware Reference for the ATCA-6000, which
uses one or two SPMs as proxy FRUs).
Severity to assign Select one of the severities defined by HPI:
0 = Critical
1 = Major
2 = Minor
3 = Information
4 = OK
Critical, major, and minor events are considered alarms
and are added to the DAT.