RE: SNMP Trap Truncated?

Hi,

Just had a follow-up question. I changed the identifying tag to just contain the error code 44448217 so that fits fine however I did notice that the line that follows is not on a new line as you can see:

  DISMAN-EVENT-MIB::sysUpTimeInstance  0:0:23:32.36
            SNMPv2-MIB::snmpTrapOID.0  DISMAN-EVENT-MIB::mteTriggerFired
    DISMAN-EVENT-MIB::mteHotTrigger.0  44448217  DISMAN-EVENT-MIB::mteHotTargetName.0
DISMAN-EVENT-MIB::mteHotContextName.0  
        DISMAN-EVENT-MIB::mteHotOID.0  SNMPv2-SMI::enterprises.7143.6.9.1.0
      DISMAN-EVENT-MIB::mteHotValue.0  1201  SNMPv2-SMI::enterprises.7143.6.9.2.0  7


Should I be including some sort of new line character at the end of the error code so that a new line is forced?

Cheers,
Matt


-----Original Message-----
From: Mathew Samuel [mailto:[email protected]] 
Sent: Tuesday, May 08, 2012 12:31 AM
To: 'Dave Shield'
Cc: '[email protected]'
Subject: RE: SNMP Trap Truncated?

Thank you Dave for your help. I shortened identifying tag to just the code so it'll fit just fine now.

Cheers,
Matt

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Dave Shield
Sent: Monday, May 07, 2012 2:43 PM
To: Mathew Samuel
Cc: [email protected]
Subject: 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

------------------------------------------------------------------------------
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