Temperature failure for probe (CPU_A)

[jhi_ironport]

Hello,

we have a couple of C150s, running quite ok. Ever since enabling snmp traps both the boxes are bombing our management station with traps saying

Temperature has exceeded a recoverable failure threshold for probe (CPU_A)

Documetation says this trap is sent when CPU temp is above 90C. Also it suggests heatsink issue.

Before we set out on replacing the (new) boxes, we'd like to confirm it's real HW issue, but I'm unable to get any independent reading of the temperature probes. SNMP returns only "planar" temperature, which is cool:

SNMPv2-SMI::enterprises.15497.1.1.1.9.1.2.1 = INTEGER: 15
SNMPv2-SMI::enterprises.15497.1.1.1.9.1.3.1 = STRING: "Planar"

Upgrade from AsyncOS 5.5 to 6.1 made no difference.

In case of HW failure orange light should be flashing, too, and this is something the on-site personel couldn't confirm. OTOH, the LEDs seem to be hidden a bit on C150 ...

What would you suggest to do next?

Thanks,
--
jozef :-)

[Rayman_Jr]

I just put the IronPort C-600 OIDs in a WEB site...it seems that those are little bit different than C-150

C600 OIDs
http://riihimaki.dyndns.org/ironport_oids.html

. .15497.1.1.1.9.1.3.1 on C-600 is "Ambient" and .15497.1.1.1.9.1.2.1 is its temperature in Celsius. Your value 15 make sense for ambient but not for Planar

You can for example get the full list of OIDs with unix snmpwalk command.

To get MIB descriptions of IronPort specific traps:

snmpwalk -Os -c public -v 2c -m ALL ironporthost.acme.com ironport

To get OID numbers of IronPort specific traps:

snmpwalk -Os -c public -v 2c -On -m ALL ironporthost.acme.com ironport

[jhi_ironport]

Hello jariih,

reading through the MIB, .15497.1.1.1.9.1.* should be temperature table, with lines numbered by the last number, and columns of value-name pairs numbered in the previous one ("2" and "3").

On bigger boxes there are more - your listing shows 5 lines, among them also CPU_A value. Too bad such value doesn't exist here on C150, there's just one line with "Planar" value:

SNMPv2-SMI::enterprises.15497.1.1.1.9.1.3.1 = STRING: "Planar"
SNMPv2-SMI::enterprises.15497.1.1.1.9.1.3.2 = No Such Instance currently exists at this OID
SNMPv2-SMI::enterprises.15497.1.1.1.9.1.3.3 = No Such Instance currently exists at this OID
SNMPv2-SMI::enterprises.15497.1.1.1.9.1.3.4 = No Such Instance currently exists at this OID
SNMPv2-SMI::enterprises.15497.1.1.1.9.1.3.5 = No Such Instance currently exists at this OID

Anyway, support asked for remote access and will check the boxes.

[jhi_ironport]

FYI: IronPort support identified this as known issue, fixed since 6.1.5-103. We upgraded from 6.1.0-301 to 6.3.5-003, and indeed the trap flood disappeared. Thanks!