Contents

• Putty Xmodem File Transfer Driver
• Putty And Xmodem
• Putty Xmodem File Transfer Free
• Putty Xmodem Download
• Putty Xmodem File Transfer

Putty xmodem file transfer. You should be able to use HYPERTRM. EXE in C: program Fileswindows NT and HYPERTRM. DLL in C:windows System32.It can send a file containing xmodem without any problems but receiving a file fails every time. In this case contact the IT service to help configure PSCP PuTTy and Windows ambient Path variables. Downloading a File with Xmodem. To download a file from a remote machine, complete the following steps: 1. On the remote machine, issue the appropriate Xmodem command to instruct the Xmodem software to send the file that you want to download. The remote machine software should then prompt you to initiate the transfer. From Lua script. Launch rx binary. Luasenddata ('rx -X u-boot.bin',true); - Upload file luaxmodemsnd ('D:00Shareu-boot.bin'); - or with xmodem 1K luaxmodem1Ksnd ('D:00Shareu-boot.bin'). 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. PuTTY zmodem transfering file integration. Zmodem integration. Sz.exe and rz.exe binaries are available here.

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.

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.

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

   • Catalyst 2940 and 2950 series switches

   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.

   • Catalyst 2970, 3550, 3560 and 3750 series switches

   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.

   • Catalyst 2955 series switches

   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.

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:

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

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

5. 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:

1. Set the baud rate to 115200 on the switch: prompt.

2. Restart HyperTerminal.

3. Under COM PORT properties, select the bits per second as 115200. The switch: prompt is displayed.

4. Start the Xmodem recovery.

5. 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:

1. Issue the show version command in order to verify the current version of software that you run.

   Here is an example:

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

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

Contents

Introduction

This document explains how to use the xmodem command at the console to download Cisco IOS® software using the ROM monitor (ROMmon).

Prerequisites

Requirements

There are no specific requirements for this document.

Components Used

The information in this document is based on these software and hardware versions:

• Cisco 827, 1600, 1700, 2600, 3600, and 3700 Series Routers

• Cisco AS5200, AS5300, AS5350, and AS5400 Universal Access Servers

Note: Xmodem can also be used on certain Catalyst switches.

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.

Overview

Xmodem can be used on a group of routers (see Components Used) and is used in disaster recovery situations where the router has no valid Cisco IOS software or bootflash image to boot from and hence, only boots up in ROMmon. This procedure can also be used where there are no Trivial File Transfer Protocol (TFTP) servers or network connections, and a direct PC connection (or through a modem connection) to the router's console is the only viable option. Because this procedure relies on the console speed of the router and the serial port of the PC, it can take a long time to download an image. For example, downloading Cisco IOS Software Release 12.1(16) IP Plus image to a Cisco 1600 Series Router using a speed of 38400 bps takes approximately 25 minutes.

Usage

Here is the command syntax for xmodem as per the Command Reference Manual for Cisco IOS version 12.2.

Putty Xmodem File Transfer Driver

This table describes the command syntax for the xmodem command.

Putty And Xmodem

Note: xmodem options e, f, and s are only supported on the Cisco 1600 Series Routers. In order to find out the syntax and available options to use with the xmodem command, enter xmodem -? at the ROMmon prompt.

Here is an example of the xmodem command issued on a Cisco 1603 Router:

Here is an example of the xmodem command issued on a Cisco 2620 Router:

Examples

Notes:

Putty Xmodem File Transfer Free

• The xmodem transfer only works on the console port. You can only download files to the router. You cannot use xmodem to get files from the router.

• It is also important to note that the -sdata-rate option is only available on the Cisco 1600 Series Routers and was implemented to overcome the console baud rate limitation of 9600 bps. If you specify -sdata-rate of 115200 bps for example, you can increase the download rate and hence, reduce download time. Other Cisco routers support console speeds up to 115200 bps. Therefore, the -sdata-rate option is not required.

• Ensure that the PC serial port is using a 16550 universal asynchronous transmitter/receiver (UART) if you are downloading a Cisco IOS software image through the router's console speed at 115200. If the PC serial port is not using a 16550 UART, it is recommended that you use a speed of 38,400 or lower.

Xmodem Procedure for Downloading a Cisco IOS Software Image onto a Cisco 1603 Router

Use this xmodem procedure in order to download a Cisco IOS software image onto a Cisco 1603 Router.

1. Launch a terminal emulator program.

   In this example, configure Windows HyperTerminal for 8-N-1 at 9600 bps and connect your PC's serial port to the console port of the router. Once connected, you need to get into the ROMmon prompt (rommon 1>). Typically, if the router's Cisco IOS software image and bootflash image are both corrupt, the router only comes up in ROMmon mode. If the former is not true and you need to get into the ROMmon prompt, you need to change the configuration register (typically 0x2102 as given by show version) to 0x0:

2. From the ROMmon prompt, issue the xmodem command. However, before you issue the xmodem command, ensure that you have the new Cisco IOS software image on your PC.

   In this example, all Flash memory is erased before downloading using the f option (only on the Cisco 1600 Series ). Perform a CRC-16 checksum using the c option and using a download speed of 115200 bps (only on the Cisco 1600 Series ) by specifying -s115200:

   Note: If the console port is attached to a modem, both the console port and the modem must be operating at the same baud rate.

   Warning:

3. Configure the terminal emulator program for a data rate of 115200 bps to match the xmodem speed specified above. This is done by closing the previous terminal session of 9600 bps and opening a new one at 115200 with 8-N-1. The trick here is that the Cisco 1603 only supports a maximum baud rate of 9600 bps. Therefore, when connecting at 115200 bps, you cannot see the router prompt. This is an important point to remember. Once connected to the router at 115200 bps, select Transfer and Send File from the HyperTerminal menu bar.

4. Specify the image file name and location and enter xmodem as the protocol.

5. Click on Send to start the transfer.

   This message is received when the transfer is complete:

6. Per the message above, you need to exit your 115200 bps HyperTerminal session and restart a new one at 9600 bps. Once connected, the router's ROMmon prompt appears. Verify that the download was successful by issuing a dir flash:.

7. Change the config register back to 0x2102 and reset or power cycle the router so that the new Cisco IOS software image gets loaded.

Xmodem Procedure for Downloading a Cisco IOS Software Image onto a Cisco 2620 Router

Use this xmodem procedure in order to download a Cisco IOS software image onto a Cisco 2620 Router.

1. Launch a terminal emulator program.

   This example Windows HyperTerminal is configured for 8-N-1 at 9600 bps. Connect your PC's serial port to the console port of the router. Once connected, get into the ROMmon prompt (rommon 1>). Typically, if the router's Cisco IOS software image and bootflash image are both corrupt, the router only comes up in ROMmon mode. If the former is not true and you need to get into the ROMmon prompt, then you will need to change the configuration register (typically 0x2102 as given by show version) to 0x0 as follows:

2. Once in ROMmon, change the console baud rate from 9600 bps to 115200 bps to speed up the download time. Use the confreg command and complete the instructions presented on the screen.

3. Once the router boots up in ROMmon, the HyperTerminal sessions start to display illegible characters. You need to exit the current terminal session and start a new one at a data rate of 115200 bps to match the console rate as in step 2.

4. You are now ready to issue the xmodem command. However, before issuing the xmodem command, ensure that you have the new Cisco IOS software image on your PC.

   Warning:

5. From the HyperTerminal menu bar, select Transfer > Send and specify the image name/location and xmodem protocol as in steps 3 and 4 and start the transfer.

6. Once the transfer is complete, these messages appear:

   Notice how the Flash gets erased towards the end automatically compared to Cisco C1600. Therefore, the reason why the f option is not required here. Finally, ensure that you reset the console speed back to 9600 and change the boot sequence back to default by changing the configuration register back to 0x2102:

Xmodem Procedure for Downloading a Cisco IOS Software Image onto a Cisco 3600 Router

Use this xmodem procedure in order to download a Cisco IOS software image onto a Cisco 3600 Series Router.

Putty Xmodem Download

The standard procedure uses the default console speed of 9600 bits per second. 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.

When in ROMMON mode, complete this procedure using the ROMMON confreg utility.

1. Open a new hyperterminal with these settings:

2. After setting the hyperterminal, you receive a rommon prompt. Enter the xmodem command. Before you enter an xmodem command, there should be a software image residing in your terminal or your local hard drive.

3. After this message appears, you have to download the file using xmodem and this procedure:

   1. Go to Hyperterminal and click the Transfer menu.

   2. Select Send File.

   3. In the dialog box which appears, click on browse and look for the file name on your local hard drive.

   4. Under the filename field is the Protocol drop-down box. Choose Xmodem.

   5. Click Send to initiate the file transfer.

4. After the transfer completes, the router will reload itself. When the reload completes, press the return key to be taken to a prompt and to reset the configuration register and the console line speed.

5. Upon changing the console speed, you will lose connectivity. Go to your terminal program, change the baud rate to 9600, and reconnect to the router console.

Putty Xmodem File Transfer

Related Information