Hello Frank, The agent is going to be supporting only one security level at one time. And hence removing and adding the groups/access back again. I was able to get this to work without a restart. When the security level was changed, I updated the USM users [removing old and adding new users]
Thanks, George. On Thursday, November 6, 2014 12:35 AM, Frank Fock <[email protected]> wrote: Hello George, A restart is not necessary, of course. Most likely you did not properly re-add the necessary entries? Why are you changing so many things just to change the security level? Best regards, Frank > On 06 Nov 2014, at 04:59, George Bachus <[email protected]> wrote: > > Hello, > > I am in the process of implementing an agent that will support both v2 and > v3. I have the basic agent running for both these versions. The problem I > seem to be having is in v3, when I change the security level. > Once I change the security level, all requests to the agent from a manager > [with new security level settings], get an "unknown user names " error. > Basically the authorization fails. > Now if I restart the agent, then all is fine. The requests get processed and > the response is sent correctly. > > What i would like to know is that, is it necessary to restart the agent when > the security level is changed or is it that I am missing a step or two? > When the security level changes, I am > * removing the groups from the VACM MIB > * removing the access using the old security level > * adding the groups back again with the new users > * adding the views back again with the new security level. > > Any insights to this is helpful. > > Thanks, > George > _______________________________________________ > SNMP4J mailing list > [email protected] > https://oosnmp.net/mailman/listinfo/snmp4j _______________________________________________ SNMP4J mailing list [email protected] https://oosnmp.net/mailman/listinfo/snmp4j
