Putty Xmodem File Transfer
Cisco Xmodem Ios Transfer
Putty Xmodem Cisco

The only option to recover the switch is an Xmodem file transfer. Step 4 covers this file transfer. If the boot command has failed or there is no valid image from which to boot in Flash, perform an Xmodem file transfer. A typical Xmodem file transfer can take up to 2 hours, which depends on the image size. Go under File - Transfer - Xmodem - Send and choose the file that you wish the transfer. The transfer will start and you will see a transfer window pop up like this:Once completed, you should get a prompt back to your ROMMON:Begin the Xmodem or Xmodem-1K transfer nowC. While PuTTY does support a serial connection, it doesn't have an XMODEM file transfer option. In the ATLAS, once you make the selection for it to either 'Load and Use Config' or 'Save Config Remotely,' you must then have your VT100 program either transmit the file or receive the file using XMODEM. Download ExtraPuTTY for free. ExtraPuTTY - fork of putty 0.67. (Add win32 API,shortcuts for pre-defined command,can use files instead of the registry,auto-reconnect, scripting a session with lua,integrates FTP,TFTP,Ymodem,Xmodem transfert protocols, integrates cygwin, zmodem, session manager,hyper link projects and others.).

Contents

Introduction

This document explains how to recover Cisco Catalyst fixed configuration switches from a corrupt or missing system image or an incorrectly set boot variable. The Catalyst fixed configuration switches that this document describes include the 2940, 2950/2955, 2970, 3550, 3560, 3750 and the 3750 Metro series switches.

Prerequisites

Requirements

If you have not already done so, connect a PC to the console port of the switch. For information on how to connect a terminal to a Catalyst fixed configuration switch, refer to Connecting a Terminal to the Console Port on Catalyst Switches. Use a terminal emulation program such as Microsoft Windows HyperTerminal in order to establish the console session. These are the settings:

Bits per second: 9600
Data bits: 8
Parity: None
Stop bits: 1
Flow control: None

Components Used

This document is not restricted to specific software and hardware versions.

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Conventions

Refer to Cisco Technical Tips Conventions for more information on document conventions. Eml to pst converter full version with crack.

Problem

When Catalyst fixed configuration switches experience boot errors, these conditions can apply:

The switch is in a continuous reboot.
The switch displays the switch: prompt.
The error loading flash: message appears.

Switch Displays the Switch: Prompt or 'Error Loading Flash:'

The switch: prompt indicates that the switch has not booted completely and requires the user to complete the boot process.
The error loading flash:<image> message indicates that the switch failed to load an image because of a corrupt or missing image.
The corrupt or missing image can be the result of a failed download. In this case, the image has a bad checksum or a failed software upgrade, and the upgrade procedure was not followed properly. There is the possibility that the user deleted the image but did not replace the image. A boot variable can have been set incorrectly.

With a console session open, you see an error message that is similar to this:

Putty Xmodem File Transfer

Normally, the switch attempts to automatically boot the next valid image in the Flash file system. Here is an example:

If there is no valid backup image from which to boot, the boot process fails completely. Here is an example:

Step-by-Step Recovery Procedure

Use this solution to solve the problem.

Note: A PC must be attached to the console port of the switch, as the Prerequisites section of this document states.

If the switch is in a continuous reboot, complete one of the procedures in this step, which depends on your switch model.
Note: If the switch is not in a continuous reboot, but is already at the switch: prompt, proceed directly to Step 2.
1. Unplug the power cord.
2. Hold down the MODE button while you reconnect the power cable to the switch.
  The MODE button is on the left side of the front panel.
3. Release the MODE button after the STAT LED goes out.
  Note: The LED position can vary slightly, which depends on the model.
  You are now at the switch: prompt.
4. Proceed to Step 2.
1. Unplug the power cord.
2. Hold down the MODE button while you reconnect the power cable to the switch.
  The MODE button is on the left side of the front panel.
3. Release the MODE button after the LED that is above Port 1x goes out.
  Note: The LED position can vary slightly, which depends on the model.
  You are now at the switch: prompt.
4. Proceed to Step 2.
1. Issue a break sequence from the keyboard in order to break into switch: mode.
  The terminal application and operating system that you use determine the break sequence to use. HyperTerminal that runs on Windows 2000 uses Ctrl-Break. For more information, refer to Standard Break Key Sequence Combinations During Password Recovery.
  This example uses HyperTerminal to break into switch: mode on a 2955:
2. Proceed to Step 2.
Issue the flash_init command and the load_helper command.
If the Flash has already initialized, you see this:
If the Flash has not initialized, you see this:
Issue the load_helper command in order to load any boot helper images. Here is an example:
Issue the dir flash: command in order to view the contents of the Flash file system.
Determine if there are any Cisco IOS® image files or image directories in flash:. The Cisco IOS image files are .bin files, and the image directories are named with the image filename, excluding the .bin extension. If no Cisco IOS image files or image directories exist, you see this:
If your Flash directory looks like this, proceed directly to Step 4. Step 4 recovers the switch with an Xmodem file transfer.
If there is still an image in Flash, issue the boot command in order to try to recover the switch. Before you issue the boot command, verify where the Cisco IOS image is stored in the Flash directory. The location in which the image is stored can differ, which depends on your switch model.
- Catalyst 2940, 2950, and 2955 Flash file system
  The Cisco IOS image file (.bin file) always resides in the flash: directory on Catalyst 2940, 2950 and 2955 series switches. Here is an example:
- Catalyst 2970, 3550, 3560, and 3750 Flash file system
  The organization of the Flash file system on a Catalyst 2970, 3550, 3560, and 3750 is a little different. You can store the Cisco IOS image file in the flash: directory. However, if you use the Cluster Management Suite (CMS) image in order to manage switches with a web interface, you can store the Cisco IOS image file in its own directory. Issue the dir flash:directory command in order to display the image file in this case.
Attempt to Boot the Image
After you have verified where the Cisco IOS image file resides, try to boot the image. Issue eit