It is highly likely that CiscoWorks lost communication to a device while RME had it locked. Now the devices say connection refused when SSH attempted via CLI and RME reports that it can't gain SSH access either.
What is the proper way to correct a situation like this?
Try restarting ConfigMgmtServer (pdterm/pdexec ConfigMgmtServer). However, these days, RME shouldn't be holding any sockets open. You may just be out of VTY lines via some other process. If possible, check the show users output from the device's console.
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 ...