SNMP Trap Truncated?

Mathew Samuel <[email protected]>
Newsgroups gmane.network.net-snmp.user
Message-ID <42A906474A92AF469A58D043EC721B00058AC1@SOTTEXCH10.corp.ad.entrust.com>
Hi,

So we receive an SNMP trap and the text is as follows:

The following SNMP trap notification was generated by ms931.mytest.com (xx.x.xxx.xx):
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  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  1224  SNMPv2-SMI::enterprises.7143.6.9.2.0  7

Essentially the line with the error code (i.e. 44448217) some how gets truncated. Or the line that follows eats it up or something. The snmpd service, that we use, is being run on Linux RH 5.6 and the RPM package version is net-snmp-5.3.2.2-9.el5_5.1. We have the 44448217 error message that we provide but why is it being truncated? This didn't happen with net-snmp-5.1.2-13.el4_7.2. Just wondering if any one else has experienced this issue and if it is something that can be resolved? Also tried with net-snmp-5.3.2.2-17 and the truncation still occurred.

Cheers,
Matt

------------------------------------------------------------------------------
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.