Please disregard this as I determined the cause. I found a ‘no exec’ statement in the running config. I should have detected this first. I suspect it occurred as a typo when I was entering a ‘no exec-timeout’ command for the line console 0. Anyhow, for what it’s worth here’s what happens when this mistake is made.
I configured 3 routers in a CCNA OSPF lab. When finished
with the lab I decided to save the configurations. I did the copy running-config startup-config command on a 2501 while telnetted in from another router. I performed this on a second 2501 also.
Now one of the 2501s boots, no problems.
The other 2501 boots and all startup information is visible via the console port until the beginning of the —System Configuration Dialog—, where it locks up. Actually text “system configuration dialog doesn’t appear, the process stops just before that.
However, the router is working because it is possible to telnet in via the same serial port connection that was used during the lab. But no matter how I end the telnet session or shut down the 2501, it still locks up at the same place, disabling the console port.
Any suggestions on how to remedy this will be greatly appreciated.
