Re: SNMP Trap Truncated?
Dave Shield <[email protected]>
| Newsgroups | gmane.network.net-snmp.user |
|---|---|
| Message-ID | <CAKoMtGbSmqA=TvHSCLrU66LS6b1+RxwX57j7f85y9wPpBk0bjg@mail.gmail.com> |
On 7 May 2012 15:36, Mathew Samuel <[email protected]> wrote: > DISMAN-EVENT-MIB::sysUpTimeInstance 0:0:21:08.75 > SNMPv2-MIB::snmpTrapOID.0 DISMAN-EVENT-MIB::mteTriggerFired > DISMAN-EVENT-MIB::mteHotTrigger.0 44448217: No response from lo <snip> > Essentially the line with the error code (i.e. 44448217) some how gets > truncated. This is the value of the varbind "mteHotTrigger.0', which is reporting the index value of the mteTriggerTable that caused the trap to be sent - i.e. the relevant value of mtTriggerName. The syntax of mteTriggerName is SnmpAdminString (SIZE (1..32)) so this value is limited to 32 characters. That appears to be roughly the length of the value that's being logged here. How are you configuring the monitor entry? What is the snmpd.conf directive that you are using? What happens if you walk the mteTriggerTable? What sort of index values do you see? 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