Dana Burns wrote:
> So by using the system clock, does the engineID change at each boot?
Of course not. The system clock is used as one source during the
*initial* generation of the engineID. Once it has been generated, it's
persistent.
> I can still authenticate if I use the -e option on the com
> >> "JM" == Jeff Miller writes:
>
> JM> - Changing the snmpd engineID will make the previous
> JM> localized engineID for a given security name incorrect
> JM> and render those users in the USM table unusable.
>
> Dave is right, the engineID itself is not "localized". "localization"
> refers to h
> "JM" == Jeff Miller writes:
JM> - Changing the snmpd engineID will make the previous
JM> localized engineID for a given security name incorrect
JM> and render those users in the USM table unusable.
Dave is right, the engineID itself is not "localized". "localization"
refers to how master
On 08/05/07, Miller, Jeff (eng) <[EMAIL PROTECTED]> wrote:
> My understanding is that:
> - Changing the snmpd engineID will make the previous
> localized engineID for a given security name incorrect
> and render those users in the USM table unusable.
Ummm... Not sure.
I'd need to check through
M engineID and the snmpd engineID?
On 08/05/07, Miller, Jeff (eng) <[EMAIL PROTECTED]> wrote:
> is it necessary to regenerate the usmUsers if I change the
> engineID so that the engineID is again localized?
Yes. I believe that
On 08/05/07, Miller, Jeff (eng) <[EMAIL PROTECTED]> wrote:
> is it necessary to regenerate the usmUsers if
> I change the engineID so that the engineID is again localized?
Yes. I believe that this is correct.
Dave
-
Th
