> On Tue, 20 Jan 2009 11:03:20 -0800 (PST), PoWah Wong
> said:
PW> Which version of netsnmp start to support SHA & AES?
I'm not sure. They've been supported for a very long time. Even
the 5.0 line of code supported them.
--
Wes Hardaker
Sparta, Inc.
-
> On Thu, 22 Jan 2009 14:49:15 -0500, Arvind Gupta
> said:
AG> Want to know that do we have some standard MIB or MIB element which shall be
AG> used to trigger the trap resync from the NMS.
There is no way to "resync" a bunch of traps. They're sent from the
agent and never "queued". I
> On Thu, 22 Jan 2009 11:28:17 -0800, "Mike Ayers"
> said:
MA> In non-proxy situations they context engine ID and authoritative
MA> engine ID should be the same. I won't make an absolute statement
MA> here, as I haven't investigated this deeply enough to be sure.
It's possible to use t
I used Net-Snmp 5.1 on Windows XP to provide some information with SNMPv2c
about custom applications in 2004. It is still being used, running on a 24x7
basis without failures.
De: Rodolfo Leffa [mailto:rodolfole...@gmail.com]
Enviado el: jueves, 22 de enero de
The next thing to try is checking whether the agent is actually
receiving anything.
Try stopping the agent, and then starting it manually using the command
snmpd -f -Le -d
(plus any other options that you normally use)
That will show raw packet dumps of traffic in &
