On Wed, 2010-05-26 at 11:40 -0700, Wes Hardaker wrote:
> > On Tue, 25 May 2010 09:51:41 -0400, Chris Fowler
> > 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. How
>>>>> On Tue, 25 May 2010 09:51:41 -0400, Chris Fowler
>>>>> said:
CF> I've simplified the trap and am trying to send it using snmptrap
...
CF> iso.3.6.1.4.1.6889.2.8.1.4.6.1.1: Value out of range (Bad string length)
CF> I thought an octet string c
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
