5 replies
by gjohnson
Were using telnet or were you directly attached to the router on the console port and using hyperterm?
If you are, sometimes you have to adjust your terminal emulation settings. I just got a new cisco router and I couldn't talk to it unless I set my term settings to 8,none,1 -- 8,none,2 -- etc. I also had to adjust the speed at which my machine talked to the router. I finally hit a config that the router would accept keyboard input.
Good luck
by adeelmemon
by mike mullins
Connect to the router with the following terminal settings:
1200 baud rate
No parity
8 data bits
1 stop bit
No flow control
You no longer see any output on your screen. This is normal.
Power cycle (switch off and then on) the router and press the spacebar for 10-15 seconds. This generates a signal similar to the break sequence.
Disconnect your terminal and reconnect with a 9600 baud rate. You should now be in ROM Monitor mode.
Continue with the procedures outlined @
http://www.cisco.com/warp/public/779/smbiz/service/knowledge/general/recovery2.htm
to gain access to your router.
Good Luck
by adeelmemon
by adeelmemon
This discussion is closed to new replies.
Trending Security posts
Sort by Trending