Standard Break Key Sequence Combinations During Password Recovery

Contents

Introduction
Standard Break Key Combinations
Troubleshooting Tips
How to Simulate a Break Key Sequence

Introduction

This document provides standard break key sequence combinations for the most common operating systems, and some troubleshooting tips.

Standard Break Key Combinations

Troubleshooting Tips

• Problems encountered during password recovery often occur because users do not know what the break key sequence is for the (non-Cisco) software they are using. For software not listed above and for additional information, users should refer to the documentation of their individual software packages.

   

• The auxiliary (AUX) port is not active during the boot sequence of a router. Therefore, sending a break through the AUX port does not work. You need to be connected to the console port, and have the following settings:

  9600 baud rate
  No parity
  8 data bits
  1 stop bit
  No flow control

• Some versions of Windows NT have hyperterminal softwares that have a problem with sending the correct break key signal. You might consider visiting http://www.hilgraeve.com/htpe/index.html for an upgrade of the hyperterminal software.

How to Simulate a Break Key Sequence

This is useful if your terminal emulator doesn't support the break key, or if a bug prevents it from sending the correct signal (the hyperterminal under Windows NT used to suffer from this behavior):

1. 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.

2. 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.

    

3. Disconnect your terminal and reconnect with a 9600 baud rate. You should now be in ROM Monitor mode.