RME 4.2 (LMS 3.1) Alias devices not detected or are forgotten
Recently upgraded to LMS 3.1 - Now device aliases get detected, I resolve the alias which deletes the unwanted device entry, however LMS seems to forget this and will suddenly discover these devices again. Also, it is struggling to detect aliases so we have 2 interfaces on the same device which are not reported as aliases. Any idea where I should look?
Re: RME 4.2 (LMS 3.1) Alias devices not detected or are forgotte
The first thing to check is how these duplicate devices are re-entering DCR. Alias resolution is not persistent. Once the aliases are resolved, the duplicate device is deleted. If that same device is brought back, then the alias will come back.
The way the RME alias algorithm work is as follows:
* Make sure the two devices have different DCR IDs (else they are really the same device).
* Find all entries in the RME database with the management IP address of the new device.
* For all matching interfaces, check the MAC address.
* If the MAC matches, check the port count on both devices.
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 ...