Re: Bad string length
Chris Fowler <[email protected]>
| Newsgroups | gmane.network.net-snmp.user |
|---|---|
| Message-ID | <1274900115.3374.45.camel@cfowler-desktop> |
On Wed, 2010-05-26 at 11:40 -0700, Wes Hardaker wrote: > >>>>> On Tue, 25 May 2010 09:51:41 -0400, Chris Fowler <[email protected]> said: > The other possibility (though based on your output I don't think this > applies) is that the MIB itself has a size limit for the variable and > you're exceeding it. However, the above makes it look like you're not > loading that part of the MIB tree so this shouldn't be possible given > you current script and output > This is what is was. Apparently they've updated the mib to increase the size of the object. I did an unset MIB in the shell and it worked fine. > CF> It seems the Avaya PBX "forwards" a trap from a device as a string > CF> argument to its trap. Ugly... > > Uhh... yeah... I won't comment on that! I'm not sure their motivation. I'm going to have to write a perl script to take the trap received from snmptrapd and get the other trap out of it. 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