A P P E N D I X  E

ShMM Sensor Map and Fault Isolation

This appendix defines the sensors within the CT900 ShMM card and, where applicable, defines what system function(s) is/are affected when a sensor is triggered.


ShMM Sensors


TABLE E-1 ShMM Sensor Map

Sensor Number

Sensor
Name

Sensor
Type

Sensor
Description

Fault Condition
(impacted function)

0

FRU 0 HOT_SWAP

Discrete (0x6f), "Hot Swap" (0xf0)

Hot swap for Active ShMM

 

1

IPMB LINK

Discrete (0x6f), "IPMB Link" (0xf1)

IPMB link for ShMM carrier

Communication will fail

2

Local Temp

Threshold (0x01), "Temperature" (0x01)

Local temperature sensor

If the local temperature goes above the UNR threshold the ShMM carrier may overheat.

3

3V3_local

Threshold (0x01), "Voltage" (0x02)

Standby 3.3V signal on the ShMM carrier

Event will be logged

4

I2C_PWR_A

Threshold (0x01), Voltage" (0x02)

12V signal on the ShM carrier (I2C A power)

Event will be logged

5

I2C_PWR_B

Threshold (0x01), "Voltage" (0x02)

5V signal on the ShMM carrier (I2C B power)

Event will be logged

6

VBAT

Threshold (0x01), "Voltage" (0x02)

VBAT signal on the ShMMcarrier

Event will be logged

7

Fan Tach. 0

Threshold (0x01), "Fan" (0x04)

FT0 tach sensor for fan 1

Fan Fault will occur and FT red/SAP LED will be lit if threshold crossed.

8

Fan Tach. 1

Threshold (0x01), "Fan" (0x04)

FT0 tach sensor for fan 2

Fan Fault will occur and FT red/SAP LED will be lit if threshold crossed.

10

Fan Tach. 2

Threshold (0x01), "Fan" (0x04)

FT1 tach sensor for fan 1

Fan Fault will occur and FT red/SAP LED will be lit if threshold crossed.

11

Fan Tach. 3

Threshold (0x01), "Fan" (0x04)

FT1 tach sensor for fan 2

Fan Fault will occur and FT red/SAP LED will be lit if threshold crossed.

13

Fan Tach. 4

Threshold (0x01), "Fan" (0x04)

FT2 tach sensor for fan 1

Fan Fault will occur and FT red/SAP LED will be lit if threshold crossed.

14

Fan Tach. 5

Threshold (0x01), "Fan" (0x04)

FT2 tach sensor for fan 2

Fan Fault will occur and FT red/SAP LED will be lit if threshold crossed.

15

-48A Bus voltage

Discrete (0x6f), "Entity Presence" (0x25)

GPIO 12 presence on the carrier

Used to find if input is present or not.

16

-48B Bus voltage

Discrete (0x6f), "Entity Presence" (0x25)

GPIO 13 presence on the carrier

Used to find if input is present or not.

17

-48A ACB voltage

Discrete (0x6f), "Entity Presence" (0x25)

GPIO 14 presence on the carrier

Used to find if input is present or not.

18

-48B ACB voltage

Discrete (0x6f), "Entity Presence" (0x25)

GPIO 15 presence on the carrier

Used to find if input is present or not.

19

-48A ACB Fuse

Discrete (0x6f), "Entity Presence" (0x25)

GPIO12 || GPIO 14 This not mapped to a specific signal but describes the health on 48V A line

Used to find if input is present or not.

20

-48B ACB Fuse

Discrete (0x6f), "Entity Presence" (0x25)

GPIO13 || GPIO 15 This not mapped to a specific signal but describes the health on 48V

Used to find if input is present or not.

128

CPLD State

Discrete (0x6f), "OEM reserved" (0xde)

CPLD state sensor:

  • 0002h - Local Healthy
  • 0004h - Switchover Request Local
  • 0010h - Switchover Status LED 1
  • 0200h - Remote Healthy (Status of other ShMM; 1 = healthy, 0 = not healthy)
  • 1000h - Local Presence (Status of ShMM; 1 = connected, 0 = not connected)
  • 2000h - Active

Events generated when ShMM CPLD state changes (including redundancy state changes).

129

Reboot Reason

OEM Reserved (0xdd)

The state mask for the sensor indicates the cause of the last reboot. (The sensor reading is always 0 and does not have any meaning.)

  • [1] The reboot was caused by a switchover operation.
  • [2] The reboot was caused by a forced switchover operation.
  • [3] The reboot was caused by the CLI command terminate.
  • [4] The reboot was caused by loss of the HEALTHY bit.
  • [5] The reboot was caused by loss of the ACTIVE bit.
  • [6] The reboot of the Backup ShMM happened because the redundancy connection was broken but the Active ShMM was still alive.
  • [7] The reboot happened due to an error during the Shelf Manager startup.
  • [8] The reboot was caused by the ShMM hardware watchdog.
  • [9] The reboot was initiated by software (a reboot() system call).
  • [10] The ShMM has been power cycled.