CPQHSV110V3-MIB :: sCellEventTrapD5b

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › CPQHSV110V3-MIB › sCellEventTrapD5b

sCellEventTrapD5b

Module: CPQHSV110V3-MIB

OID (symbolic): CPQHSV110V3-MIB::sCellEventTrapD5b

OID (numeric): 1.3.6.1.4.1.232.0.13603419

Node type: NOTIFICATION-TYPE

Description: Severity: Warning -- not failed but attention recommended or required. A drive enclosure temperature sensor out of range condition has been reported by one of the drive enclosure elements. The handle field contains the WWN of the drive enclosure containing the Drive Enclosure Environmental Monitoring Unit. This problem was detected by the Drive Enclosure Environmental Monitoring Unit located in the drive enclosure determined by the content of the denclNum field as follows:

  • If denclNum is less than 99, the location is as indicated by the content of the rackNum and denclNum fields.
  • If denclNum is equal to 99, the location is unknown. Note that the content of the rackNum field is undefined in this case.
  • If denclNum is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rackNum and denclNum fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate.
Note that the content of the rackNum field will not be valid until a future release. The location of the temperature sensor (1 through 11) is identified in the alarmErrorCode.field.en field as follows:
  • 1 = Power Supply 1 Exhaust
  • 2 = Power Supply 2 Exhaust
  • 3 = Drive Enclosure Environmental Monitoring Unit
  • 4 = Drive Bay 1
  • 5 = Drive Bay 2
  • 6 = Drive Bay 3
  • 7 = Drive Bay 4
  • 8 = Drive Bay 5
  • 9 = Drive Bay 6
  • A = Drive Bay 7
  • B = Drive Bay 8
  • C = Drive Bay 9
  • D = Drive Bay 10
  • E = Drive Bay 11
  • F = Drive Bay 12
  • 10 = Drive Bay 13
  • 11 = Drive Bay 14

The temperature sensor out of range condition is described by the content of the alarmErrorCode.field.ec field as follows:

  • 1 = The element temperature is approaching, but has not reached, the high temperature CRITICAL threshold. Continued operation under these conditions may result in a CRITICAL condition and may reduce an element's MTBF.
  • 2 = The element temperature is above the high temperature CRITICAL threshold. Continued operation under these conditions may result in element failure.
  • 3 = The element temperature is approaching, but has not reached, the low temperature CRITICAL threshold. Continued operation under these conditions may result in a CRITICAL condition and may reduce an element's MTBF.
  • 4 = The element temperature has reached the low temperature CRITICAL threshold. Continued operation under these conditions may result in element failure.

The actual temperature threshold values can be found in the HSV element manager GUI. The enclosures array shows the drive enclosures available on the Fibre Channel loop pair (0 = Loop A, 1 = Loop B) identified in the loop field. The location of an available drive enclosure is determined by the content of the enclosures.denclNum field as follows:

  • If enclosures.denclNum is less than 99, the location is as indicated by the content of the enclosures.rackNum and enclosures.denclNum fields.
  • If enclosures.denclNum is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rackNum field is undefined in this case.
  • If enclosures.denclNum is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rackNum and enclosures.denclNum fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate.
Note that the content of the enclosures.rackNum field will not be valid until a future release.

Examples

Send this trap to an SNMP manager — replace <manager> with the IP or hostname of your monitoring server (SNMPv2c):

snmptrap -v2c -c public <manager> '' CPQHSV110V3-MIB::sCellEventTrapD5b
snmptrap -v2c -c public <manager> '' 1.3.6.1.4.1.232.0.13603419

Listen for incoming traps on the manager host (-f keeps it in the foreground, -Lo prints to stdout — useful for testing):

snmptrapd -f -Lo -c /dev/null authCommunity log public

Example snmptrapd log entry:

zoo11-linux.zoo [UDP: [192.168.30.111]:58441->[192.168.30.10]:162]:
  DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (153652809) 17 days, 18:48:48.09
  SNMPv2-MIB::snmpTrapOID.0 = OID: CPQHSV110V3-MIB::sCellEventTrapD5b

Start monitoring HP StorageWorks HSV110 (EVA) array controller with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CPQHSV110V3-MIB::sCellEventTrapD5b OID value, configure state conditions and alerts, and monitor any HP StorageWorks HSV110 (EVA) array controller from a single console.

OID Breakdown

Upper-level ancestors (7 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.232compaqCOMPAQ-ID-REC-MIB
Numeric OIDNameModule
1.3.6.1.4.1.232.0.13603419sCellEventTrapD5bCPQHSV110V3-MIB