Recovering From Corrupted Software; Recovering From Lost Or Forgotten Passwords On Non-Lre Catalyst 2950 Switches - Cisco 2950 - Catalyst Switch Configuration Manual

Using Recovery Procedures

Recovering from Corrupted Software

Switch software can be corrupted during an upgrade, by downloading the wrong file to the switch, and
by deleting the image file. In all of these cases, the switch does not pass the power-on self-test (POST),
and there is no connectivity.
This procedure uses the Xmodem protocol to recover from a corrupt or wrong image file. There are many
software packages that support the Xmodem protocol, and this procedure is largely dependent on the
emulation software you are using.
Follow these steps to recover from corrupted software:
Step 1 Connect a PC with terminal-emulation software supporting the Xmodem protocol to the switch console
port.
Step 2 Set the line speed on the emulation software to 9600 baud.
Disconnect the switch power cord.
Step 3
Reconnect the power cord to the switch.
Step 4
The software image does not load. The switch starts in boot loader mode, which is indicated by the
switch#
Use the boot loader to enter commands, and start the transfer.
Step 5
switch# copy xmodem: flash:image_filename.bin
When the Xmodem request appears, use the appropriate command on the terminal-emulation software
Step 6
to start the transfer and to copy the software image to flash memory.
Recovering from Lost or Forgotten Passwords on Non-LRE Catalyst 2950
Switches
Follow these steps if you have forgotten or lost the switch password on a non-LRE Catalyst 2950 switch:
Connect a terminal or PC with terminal emulation software to the console port. For more information,
Step 1
refer to the switch hardware installation guide.
Note
Step 2 Set the line speed on the emulation software to 9600 baud.
Step 3 Unplug the switch power cord.
Catalyst 2950 and Catalyst 2955 Switch Software Configuration Guide
32-2
prompt.
You can configure your switch for Telnet by following the procedure in the
section on page 2-9.
Chapter 32 Troubleshooting
"Accessing the CLI"
78-11380-10