Strange traps from SC-TS01
We are currently running fireware release 3.06
The traps for temp sensor is sent with the OID 1.3.6.1.2.1.1.2 which is a bit odd as that OID is sysObjectID and should be used for SNMP get. And the trap does not match the MIB-file.
Bellow I have included a tcpdump of one of the traps. To not taint it with our monitor system.
13:33:07.002163 IP (tos 0x20, ttl 94, id 62826, offset 0, flags [none], proto: UDP (17), length: 173) xx.xx.xx.xx.65534 > xxxxxx.snmptrap: [udp sum ok] { SNMPv2c C=xxxxxxx { V2Trap(125) R=1 system.sysUpTime.0=328468917 S:1.1.4.1.0=system.sysObjectID E:17095.4.1.0="Int. Temp,21.44,WARNING,08 February 2012,00:24:49" } }
I checked the release notes for new firmware and I could not find that this issue was mentioned.
Is there a fix for this issue?
The traps for temp sensor is sent with the OID 1.3.6.1.2.1.1.2 which is a bit odd as that OID is sysObjectID and should be used for SNMP get. And the trap does not match the MIB-file.
Bellow I have included a tcpdump of one of the traps. To not taint it with our monitor system.
13:33:07.002163 IP (tos 0x20, ttl 94, id 62826, offset 0, flags [none], proto: UDP (17), length: 173) xx.xx.xx.xx.65534 > xxxxxx.snmptrap: [udp sum ok] { SNMPv2c C=xxxxxxx { V2Trap(125) R=1 system.sysUpTime.0=328468917 S:1.1.4.1.0=system.sysObjectID E:17095.4.1.0="Int. Temp,21.44,WARNING,08 February 2012,00:24:49" } }
I checked the release notes for new firmware and I could not find that this issue was mentioned.
Is there a fix for this issue?
This discussion has been closed.
Comments