Skip to main content

About the discrete SP sensor status values of the system sensors command output

Contributors
PDFs

Discrete sensors do not have thresholds. Their readings, displayed under the Current column in the SP CLI system sensors command output, do not carry actual meanings and thus are ignored by the SP. The Status column in the system sensors command output displays the status values of discrete sensors in hexadecimal format.

Examples of discrete sensors include sensors for the fan, power supply unit (PSU) fault, and system fault. The specific list of discrete sensors depends on the platform.

You can use the SP CLI system sensors get sensor_name command for help with interpreting the status values for most discrete sensors. The following examples show the results of entering system sensors get sensor_name for the discrete sensors CPU0_Error and IO_Slot1_Present:

SP node1> system sensors get CPU0_Error
Locating sensor record...
Sensor ID              : CPU0_Error (0x67)
 Entity ID             : 7.97
 Sensor Type (Discrete): Temperature
 States Asserted       : Digital State
                         [State Deasserted]
SP node1> system sensors get IO_Slot1_Present
Locating sensor record...
Sensor ID              : IO_Slot1_Present (0x74)
 Entity ID             : 11.97
 Sensor Type (Discrete): Add-in Card
 States Asserted       : Availability State
                        [Device Present]

Although the system sensors get sensor_name command displays the status information for most discrete sensors, it does not provide status information for the System_FW_Status, System_Watchdog, PSU1_Input_Type, and PSU2_Input_Type discrete sensors. You can use the following information to interpret these sensors' status values.

System_FW_Status

The System_FW_Status sensor's condition appears in the form of 0xAABB. You can combine the information of AA and BB to determine the condition of the sensor.

AA can have one of the following values:

Values Condition of the sensor

01

System firmware error

02

System firmware hang

04

System firmware progress

BB can have one of the following values:

Values Condition of the sensor

00

System software has properly shut down

01

Memory initialization in progress

02

NVMEM initialization in progress (when NVMEM is present)

04

Restoring memory controller hub (MCH) values (when NVMEM is present)

05

User has entered Setup

13

Booting the operating system or LOADER

1F

BIOS is starting up

20

LOADER is running

21

LOADER is programming the primary BIOS firmware. You must not power down the system.

22

LOADER is programming the alternate BIOS firmware. You must not power down the system.

2F

ONTAP is running

60

SP has powered off the system

61

SP has powered on the system

62

SP has reset the system

63

SP watchdog power cycle

64

SP watchdog cold reset

For instance, the System_FW_Status sensor status 0x042F means "system firmware progress (04), ONTAP is running (2F)."

System_Watchdog

The System_Watchdog sensor can have one of the following conditions:

  • 0x0080

    The state of this sensor has not changed

Values Condition of the sensor

0x0081

Timer interrupt

0x0180

Timer expired

0x0280

Hard reset

0x0480

Power down

0x0880

Power cycle

For instance, the System_Watchdog sensor status 0x0880 means a watchdog timeout occurs and causes a system power cycle.

PSU1_Input_Type and PSU2_Input_Type

For direct current (DC) power supplies, the PSU1_Input_Type and PSU2_Input_Type sensors do not apply. For alternating current (AC) power supplies, the sensors' status can have one of the following values:

Values Condition of the sensor

0x01 xx

220V PSU type

0x02 xx

110V PSU type

For instance, the PSU1_Input_Type sensor status 0x0280 means that the sensor reports that the PSU type is 110V.