Re: SNMP Trap Truncated?

On 7 May 2012 19:00, Mathew Samuel <[email protected]> wrote:
> If I walk the mteTriggerTable then here is an example entry that I see:
> DISMAN-EVENT-MIB::mteTriggerEnabled."snmpd.conf".'44448217: No response from lo' = INTEGER: true(1)

That fits.

> So yes the index values are being cut off.
> Can I change the SnmpAdminString to be something larger?

No - this is an Internet Standard MIB, with a standard definition.
The index value is limited to 32 characters.
   This was decided by the Internet community - you can't
just unilaterally decide to change it.


> Perhaps this had been larger with net-snmp-5.1.2-13.el4_7.2
> when I saw this work without being truncated before.

It's quite possible that the earlier version had a broken implementation.
We completely re-wrote the DisMan Event MIB code at some point.
I can't offhand remember when this changed, but the current version
is certainly a much fuller and accurate implementation.
   You may well have seen the effects of the earlier (looser) code.

The index value is simply used to identify a particular row of
the table - it's not intended to contain arbitrary log messages.
  Why not simply configure things using a shorter identifying tag?

Dave

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
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