I'm testing snmptrapd because it appears to be crashing when receiving a
trap from an Avaya PBX. Here is what was in the system log:
Apr 29 07:49:48 ens4 snmptrapd[98]: s8720-b.vr.vanran.com [172.30.3.3]:
Trap iso.3.6.1.2.1.1.3.0 = Timeticks: (23758427) 2 days, 17:59:44.27,
iso.3.6.1.6.3.1.1.4.1.0 = OID: iso.3.6.1.4.1.6889.1.8.1.0.12,
iso.3.6.1.4.1.6889.2.8.2.1.1.1.4 = STRING: "VR-S8720-A",
iso.3.6.1.4.1.6889.2.8.1.4.6.1.18 = STRING: "1000165620",
iso.3.6.1.4.1.6889.2.8.1.4.6.1.17 = STRING:
"FPA:00000:0000000000:0429074936::N", iso.3.6.1.4.1.6889.2.8.1.4.6.1.1 =
STRING: "A:\"2010-04-29 07:49:36 172.30.3.56(via 172.30.3.56) TRAP, SNMP
v1, community public cmgTrapTypes Enterprise Specific Trap (109)
Uptime: 7 days, 21:59:22.03 cmgTrapSubsystem.0 = STRING: \"Net\"
cmgTrapOnBoard.0 = STRING: \"no\" cmgTrapLocation.0 = STRING: \"001V\"
cmgMgpFaultMask.0 = Hex-STRING: 00 00 \"",
iso.3.6.1.4.1.6889.2.8.1.4.6.1.3 = STRING: "CMG",
iso.3.6.1.4.1.6889.2.8.1.4.6.1.4 = STRING: "26",
iso.3.6.1.4.1.6889.2.8.1.4.6.1.6 = "", iso.3.6.1.4.1.6889.2.8.1.4.6.1.26
= STRING: "172.30.3.4", iso.3.6.1.4.1.6889.2.8.1.4.6.1.27 = "",
iso.3.6.1.4.1.6889.2.8.1.4.6.1.
I've simplified the trap and am trying to send it using snmptrap
#!/bin/sh
snmptrap -v 2c -c public 10.0.5.22 '' iso.3.6.1.4.1.6889.1.8.1.0.3 \
iso.3.6.1.4.1.6889.2.8.2.1.1.1.5 s 'VR-S8720-A' \
iso.3.6.1.4.1.6889.2.8.1.4.6.1.18 s '1000165620' \
iso.3.6.1.4.1.6889.2.8.1.4.6.1.17 s
'FPA:00000:0428073807:0000000000::N' \
iso.3.6.1.4.1.6889.2.8.1.4.6.1.1 s "A:\"2010-04-28 07:38:07
172.30.3.56(via 172.30.3.56) TRAP, SNMP v1, community public
cmgTrapTypes Enterprise Specific Trap (30) Uptime: 6 days, 21:47:55.05
cmgTrapSubsystem.2 = STRING: \"HW\" cmgTrapOnBoard.2 = STRING: \"no\"
cmgTrapLocation.2 = STRING: \"001V2\" cmgHardwareFaultMask.2 =
Hex-STRING: 00 00 80 cmgPrimaryClockSource.2 = STRING: \"v2\"
cmgSecondaryClockSource.2 = \"\" cmgActiveClockSource.2 = INTEGER:
primary(1) \"" \
iso.3.6.1.4.1.6889.2.8.1.4.6.1.3 s 'CMG'
When I try to send that trap I get:
iso.3.6.1.4.1.6889.2.8.1.4.6.1.1: Value out of range (Bad string length)
I thought an octet string could be from 0-65536 octets in length? Do I
need to specify a an option on the CLI? It seems the Avaya PBX
"forwards" a trap from a device as a string argument to its trap.
Ugly...
Thanks,
Chris
------------------------------------------------------------------------------
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
