Hello I using send_v2trap() function to send out inform notification from agent to trap receiver of NMS. The notification configured in below standard MIB via SNMP set command: - SNMP-NOTIFICATION-MIB::snmpNotifyTable - SNMP-TARGET-MIB::snmpTargetAddrTable - SNMP-TARGET-MIB::snmpTargetParamsTable
The inform can be received in trap receiver correctly. But if I restart the trap receiver, it can't receive inform any more. I check the wireshark trace file of inform message, and find: 1) Net-snmp agent will discover remote engineID, engineBoots and engineTime before sending out first infom.The discovered engineID, engineBoots and engineTime will be cached and used to build up informRequest. 2) There is no discovery procedure for second inform. The cached engineID, engineBoots and engineTime are always used for further informRequest. If the trap receiver is restarted, the engineBoots and engineTime are changed, but net-snmp agent still use the old cached values for informRequest. So this informRequest will be rejected by trap receiver becuse it is not fit in the time window (> 150 sec). The only way to solve this problem is to restart net-snmp agent. My question: is there any way to force engineID discovery procedure before sending every informRequest? The used net-snmp version: 5.5 Thanks in advance! With best regards, Shu Zhong Hua ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
