Suresh kumar <[email protected]> writes:

> 1. Engine ID discovered correctly during discovery; but Agent still
> incrementing usmStatsUnknownEngineIDs.0 (See EngineIDErrorPkt.pcap)
> 2. Also sending report
> SNMP-USER-BASED-SM-MIB::usmStatsNotInTimeWindows.0 (See
> EngineIDErrorPkt.pcap). updated System time on Agent; still error
> received.

These are actually normal.  In the process of engineID discovery (and
time discovery) the agent will receive a message with the wrong
engineID, so the agent increments the count and sends back the real one.
That's actually how engineID discovery works.

-- 
Wes Hardaker
Please mail all replies to [email protected]

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

Reply via email to