SNMP V3 - Informs and Change

--===============0289676905==
Content-Type: multipart/alternative;
boundary="----=_Part_13407_8674927.1205417691731"

------=_Part_13407_8674927.1205417691731
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi,

Can you please help me on the SNMPV3 informs processing and the
usmKeyChange functionalities together.

Our agent in order to send a SNMPv3 inform will persist the auth and priv
passwords(as encrypted) in the agent configuration files. Whenever the agent
is restarted, the keys will be constructed new with the passwords available
in the conf files.

Now when the manager performs the keyChange operation, a new key will be
created with the given password and the keys will be updated in the
configuration files. But the password will not be updated.

If the agent is restarted, as mentioned earlier, the keys will be recreated
with the old passwords.

The questions are,

1. When the agent is restarted, is it right to get the password from the key
provided we know the engineID.
2. Or in the keyChange manager application, is it right to send the password
and get updated in the configuration files.

The idea is we require the latest password.

Pls. clarify me.

Thanks,
Dev.

------=_Part_13407_8674927.1205417691731
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi,<br>
<br>
Can you please help me on the SNMPV3&nbsp; informs processing and the usmKeyChange functionalities together.<br>
<br>
Our agent in order to send a SNMPv3 inform will persist the auth and
priv passwords(as encrypted) in the agent configuration files. Whenever
the agent is restarted, the keys will be constructed new with the
passwords available in the conf files.<br>
<br>
Now when the manager performs the keyChange operation, a new key will
be created with the given password and the keys will be updated in the
configuration files. But the password will not be updated.<br>
<br>
If the agent is restarted, as mentioned earlier, the keys will be recreated with the old passwords.<br>
<br>
The questions are,<br>
<br>
1. When the agent is restarted, is it right to get the password from the key provided we know the engineID.<br>
2. Or in the keyChange manager application, is it right to send the password and get updated in the configuration files.<br><br>The idea is we require the latest password.<br>
<br>
Pls. clarify me.<br>
<br>
Thanks,<br>
Dev.

------=_Part_13407_8674927.1205417691731--


--===============0289676905==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
--===============0289676905==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/...net-snmp-users

--===============0289676905==--