Putty Xmodem File Transfer

Putty Xmodem File Transfer
Cisco Xmodem Ios Transfer

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.

Using a Serial Cable and Ghostlink to Transfer Files from PC to ST - Tera term download - https://en.osdn.jp/projects/ttssh2/rel. XMODEM is a file transfer protocol which enables users to transmit files between different computers. XMODEM was developed by Ward Christensen in 1977 and since then the method of sharing files has changed. It became extremely popular in the early bulletin board system (BBS) market because of its simple implementation. Xmodem is a slow transfer protocol, and the transfer of a file as large as a Cisco IOS software image could take an unacceptably long time. An increase to the console speed on the 3600 router helps decrease the time it takes to do the xmodem file transfer. Execute the terminal emulator commands to begin the Xmodem transfer. For example, using HyperTerminal: Click on Transfer, then Send File. Type the file path and name in the Filename field.

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.

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:

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 either the boot flash:filename command or the boot flash:directory/filename command.
- Catalyst 2950
- Catalyst 3550
If you issue the boot command and the result is in a successful bootup, either the default switch> prompt or the hostname> prompt displays.
Be sure to verify that you have configured the correct boot statement on the switch. See the Verify section of this document.
If you issue the boot command and the command does not result in a successful bootup, either the switch: prompt displays or you are stuck in a continuous reboot again. 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.
Download the Cisco IOS image (.bin file) to which you want to upgrade from the Software Center (Downloads) - LAN Switching Software (registered customers only) .
Note: Do not use a CMS image (.tar file). This image is a larger image and takes longer to transfer.
Issue the dir flash: command in order to compare the size of the image in bytes to the free space that remains in Flash. Here is an example:
If necessary, issue the delete command in order to delete any corrupt images that remain. Here is an example:
The next example shows an Xmodem procedure on a 2955 with the use of HyperTerminal. The procedure is the same for any of the Catalyst fixed configuration switches that this document covers.
1. Issue the copy xmodem: flash:filename command on the switch.
  Here is an example:
2. From the top of the HyperTerminal window, choose Transfer > Send File.
3. Choose the Xmodem protocol in the Send File dialog box and click Browse in order to select the Cisco IOS image (.bin file) that you downloaded previously.
4. Click Send in order to begin the Xmodem transfer.
  The Xmodem file transfer begins. This transfer can take up to 2 hours, which depends on the size of the image.
Boot the new image that you just copied over with the Xmodem procedure.
Issue the boot flash:filename command, as this example shows:
Be sure to verify that your boot statements are set correctly.

How to Speed Up Xmodem Recovery

When a user tries to recover the switch from a corrupted or missing IOS, the copy xmodem: flash:[IOS filename] command might not be displayed under the switch: prompt. The copy command might be displayed under the switch: prompt, but not the copy xmodem: command.

Complete these steps in order to speed up the Xmodem recovery:

Set the baud rate to 115200 on the switch: prompt.
Restart HyperTerminal.
Under COM PORT properties, select the bits per second as 115200. The switch: prompt is displayed.
Start the Xmodem recovery.
After the Xmodem recovery, set the BAUD rate back to 9600. If the set BAUD 9600 command does not bring the baud rate to 9600, issue the unset BAUD command in order to bring the baud rate to a default value of 9600 bps.

Verify

Complete these steps:

Issue the show version command in order to verify the current version of software that you run.
Here is an example:
Issue the dir flash:filename command in order to display the Cisco IOS image (.bin file) on a Catalyst 2940, 2950 or 2955.
If you run a CMS image on a Catalyst 2970, 3550, 3560, or 3750, you can store the Cisco IOS image in an image directory. Here is an example:
You may need to issue the dir flash:directory command on a Catalyst 3550 in order to display the Cisco IOS image (.bin file). Here is an example:
Issue the show boot command in order to verify that the boot statement is set correctly.
Here is an example:
Note: Boot statements do not display in the configuration or when you issue the show run command on any of the fixed configuration switches that this document covers. You must issue the show boot command in order to display boot statements.
If no boot statement is set or if the boot statement points to an old or missing version of software, configure the correct boot statement. Issue the boot system flash:filename command.
If you use a CMS image on a Catalyst 2970, 3550, 3560, or 3750, you can store the Cisco IOS image (.bin file) in its own image directory. Issue the boot system flash:directory/filename command. Here is an example:

Related Information

The DAM1021 originally came with FPGA firmware 0.8. Since then Soren has released a new version of the firmware, Rev 0.9.

In order to upload it to the DAC one must connect the DAC to a computer using either a “classic” serial port, like the one found at the back of older computers, or a USB to Serial adapter. Then a cable must be made connecting three pins of the DB9 connector to the connector J10 on the DAC board.

These pictures illustrate the connections that are needed:

You use your new cable to connect the DAM to your computer’s serial port (or USB-to-serial adapter). You do not power on the DAM DAC just yet.

Once you are done with making the physical connection, you need to get your hands on some software that supports the XModem 1K data transfer protocol. This is a pretty old protocol, so your choices in software are pretty limited. One such choice is the “classic” HyperTerminal, but since it is no longer available with Windows I chose the more modern ExtraPUTTY. It is a fork of the classic PuTTY telnet/ssl client software that also supports “vintage” transfer protocols such as XModem.

Once you have it installed it is pretty easy to establish a serial connection at 115200, 8, n, 1, as specified by Soekris. You click on the “serial” tickbox and enter your computer’s serial port (in my case it’s COM5) along with the specified speed (115200bps):

You click on “open” and you get a black terminal screen. You now need to power on the DAC. Once you do that, you should get something like this:

This means that everything is fine. You might see an “I0” instead of an “I3”. That is OK.

Now you need to get to the uManager prompt. You type “+++” and wait for a second. You will not see the “+” characters as you type them. That is OK. You will get this:

Now type “download”, followed by Enter. You will see something like this:

This means that you have 30 seconds to begin sending your file. To do that you click on File Transfer -> Xmodem 1K -> Send. Select your firmware file and off you go!

When the transfer completes you will see something like this:

One thing – do not forget to give the “update” command once you have uploaded the code followed by a “y” and return.

Next you type “exit” (and Enter) to exit the uManager prompt and you are ready to power cycle the DAC. Once you have done that, you repeat the above steps to get to the uManager prompt and you verify that you have successfully updated the firmware. You should now be at FPGA firmware 0.9!