NEC ExpressA1160 - Manual (Page 191)

Examine the Management Firmware Event Log
10-29
column. For example, click Sensor Name to sort the rows alphabetically by sensor
name, which lists all events reported by each sensor as a group.
Note: The arrow indicates the direction of the sort and reverses if you click it again.
3. Compare the information about each event to information in the alerts received to
analyze and resolve problems.
4. If desired, click Clear Log to empty the partition event log. A confirmation dialog
box appears.
5. Click OK to confirm the request to clear the log.
Note: The operating system or other software might have the ability to clear the log
also.
10.7.3. Asserted and De-Asserted Statuses
Sensor readings and event logs use the asserted/de-asserted terminology found in the
IPMI — Intelligent Platform Management Interface Specification Second Generation
v2.0, which includes the following definitions:
y Asserted
If a sensor is asserted, this means that the condition represented by the sensor is
true. For example if the Partition_Viable sensor is asserted, this means the partition
is viable.
y De-asserted
If a sensor is de-asserted, this means that the condition represented by the sensor
is false. For example if the Partition_Viable sensor is de-asserted, this means the
partition is not viable.
The following examples show how to interpret asserted and de-asserted statuses for
sensors.
Sensor Name
Asserted or
De-Asserted Meaning
Partition_Viable Asserted The partition is viable.
Partition_Viable De-asserted The Partition_Viable sensor is inactive (de-asserted); that
is, the partition is not viable.
Partition_Dgrade Asserted The partition is degraded.
Partition_Dgrade De-asserted The Partition_Dgrade sensor is inactive (de-asserted); that
is, the partition is not degraded.
The following examples show how to interpret asserted and de-asserted statuses for