The problem with doing this automatically is that there is no good place to put it. The logical place to put such a feature is in DCR. However, DCR doesn't actually communicate with the device (not yet anyway), so it wouldn't know if the device is unreachable or not. If you put the feature in RME, then what if RME isn't available?
That said, there are some features to aid with trimming devices. Campus Manager has a script called DeleteDevices (under NMSROOT/campus/bin) which allows you to delete unreachable devices from Campus Manager only. In Common Services 3.1 (part of LMS 3.0) when you choose to delete devices, you get a pop-up asking if you want to delete all the devices, or just those that are not managed by any application. While this still wouldn't give you what you want, it may help prune other unwanted 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 ...