SM> How many devices are monitored?
Thousands.
SM> Generally this kind of behavior observed in our network monitoring tool,
SM> because of devices are having same engine ID.
We know with 100% certainty that there are no *current* devices with
the same engine ID. I am not asking for how to troub
: [email protected] [mailto:[email protected]]
Sent: Thursday, June 23, 2011 1:01 PM
To: [email protected]
Subject: Agent Reporting usmStatsNotInTimeWindows
Hi,
We are using net-snmp5.2.6 library to communicate with switches SNMP agent.
Our manager was working
On Thu, 28 Jul 2011 15:30:03 -0400 Doug wrote:
DM> WH> The SNMPv3 specifications say that a running manager should allow its
DM> WH> notion of an agents clock values to go forward, but not backward. Thus,
DM> WH> we're doing what we're supposed to do: we won't accept *older* values
DM> WH> than wh
WH> The SNMPv3 specifications say that a running manager should allow its
WH> notion of an agents clock values to go forward, but not backward. Thus,
WH> we're doing what we're supposed to do: we won't accept *older* values
WH> than what we have cached (but would accept newer values). So, we're
W
> On Thu, 23 Jun 2011 05:26:04 -0400, said:
> We are using net-snmp5.2.6 library to communicate with switches SNMP agent.
5.2.6 is rather old at this point, you might consider upgrading to a
newer release.
> Our manager was working fine for some time without any issues. after
> some days t
Hi,
We are using net-snmp5.2.6 library to communicate with switches SNMP agent.
Our manager was working fine for some time without any issues. after some days
the agent starts giving report " usmStatsNotInTimeWindows" to all GETNEXT
queries. we noticed that the enginetime supplied by manager
Hi,
We are using net-snmp5.2.6 library to communicate with switches SNMP agent.
Our manager was working fine for some time without any issues. after some days
the agent starts giving report " usmStatsNotInTimeWindows" to all GETNEXT
queries. we noticed that the enginetime supplied by manager
