RME locked device

helexis · ‎10-12-2009

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?

Joe Clarke · ‎10-12-2009

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.

helexis · ‎10-13-2009

Update:

I am not certain how this happened but my theory is that CiscoWorks copied the running config to startup while the temporary vty lockout line was present.

Ran a NetConfig job with TFTP protocol to remove the [access-class sl_def_acl in] line from the vty section. Devices now accessible.