When I try to add a device with SNMPv3 auth and/or priv passwords that are less than 8 characters long, I get an error message.
Here is an example of the error message seen when the privacy password length is less than 8 characters (the auth password length is longer than 8 characters in this case):
Password and verify values for Privacy Password must be minimum of 8 characters length.
The error message appears as well if the authentication password length is less than 8 characters or if both auth and priv passwords length is less than 8 characters. Only the error message text is a bit different for authentication password.
The message appears either when trying to fill in the SNMPv3 credentials manually when adding a device or when creating a default credential set.
I found a known bug (CSCtr21972) which should have been already fixed in LMS 4.2 according to LMS 4.2 release notes.
I was running LMS 4.2 before the upgrade to 4.2.2 and 4.2.4 but I never tried adding a device with SNMPv3 credentials while running LMS 4.2, so I don't know if it had that limitation as well in 4.2.
I only tried this today after the upgrade to 4.2.2 and then again after the upgrade to 4.2.4.
In both versions I saw the error message.
Do you familiar with this limitation?
Do you know if there is any place where I can change it? I didn't find any SNMPv3 password policy like we have with the local users on LMS.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...