{"id":158,"date":"2012-03-29T13:20:44","date_gmt":"2012-03-29T11:20:44","guid":{"rendered":"https:\/\/blog.4-it.net\/?p=158"},"modified":"2012-03-29T13:20:44","modified_gmt":"2012-03-29T11:20:44","slug":"recovering-catalyst-fixed-configuration-switches-from-a-corrupted-or-missing-image","status":"publish","type":"post","link":"https:\/\/blog.4-it.net\/?p=158","title":{"rendered":"Recovering Catalyst Fixed Configuration Switches from a Corrupted or Missing Image&#8216;"},"content":{"rendered":"<h2><a name=\"intro\"><\/a>Introduction<\/h2>\n<p>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.<\/p>\n<h2><a name=\"prereq\"><\/a>Prerequisites<\/h2>\n<h3><a name=\"req\"><\/a>Requirements<\/h3>\n<p>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 <a href=\"http:\/\/www.cisco.com\/en\/US\/products\/hw\/switches\/ps700\/products_tech_note09186a008010ff7a.shtml\">Connecting a Terminal to the Console Port on Catalyst Switches<\/a>. Use a terminal emulation program such as Microsoft Windows HyperTerminal in order to establish the console session. These are the settings:<\/p>\n<ul>\n<li>Bits per second: <strong>9600<\/strong><\/li>\n<li>Data bits: <strong>8<\/strong><\/li>\n<li>Parity: <strong>None<\/strong><\/li>\n<li>Stop bits: <strong>1<\/strong><\/li>\n<li>Flow control: <strong>None<\/strong><\/li>\n<\/ul>\n<p><img decoding=\"async\" src=\"http:\/\/www.cisco.com\/image\/gif\/paws\/41845\/192-a.gif\" alt=\"192-a.gif\" usemap=\"\" border=\"0\" \/><\/p>\n<h3><a name=\"hw\"><\/a>Components Used<\/h3>\n<p>This document is not restricted to specific software and hardware versions.<\/p>\n<p>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.<\/p>\n<h3><a name=\"conventions\"><\/a>Conventions<\/h3>\n<p>Refer to <a href=\"http:\/\/www.cisco.com\/en\/US\/tech\/tk801\/tk36\/technologies_tech_note09186a0080121ac5.shtml\">Cisco Technical Tips Conventions<\/a> for more information on document conventions.<\/p>\n<h2><a name=\"topic1\"><\/a>Problem<\/h2>\n<p>When Catalyst fixed configuration switches experience boot errors, these conditions can apply:<\/p>\n<ul>\n<li>The switch is in a continuous reboot.<\/li>\n<li>The switch displays the <tt>switch:<\/tt> prompt.<\/li>\n<li>The <tt>error loading flash:<\/tt> message appears.<\/li>\n<\/ul>\n<h3><a name=\"subtopic1a\"><\/a>Switch Displays the Switch: Prompt or &#8222;Error Loading Flash:&#8220;<\/h3>\n<ul>\n<li>The <tt>switch:<\/tt> prompt indicates that the switch has not booted completely and requires the user to complete the boot process.<\/li>\n<li>The <tt>error loading flash:&lt;image&gt;<\/tt> message indicates that the switch failed to load an image because of a corrupt or missing image.\n<p>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.<\/li>\n<\/ul>\n<p>With a console session open, you see an error message that is similar to this:<\/p>\n<blockquote>\n<pre>Error loading \"flash:c2950-i6q4l2-mz.121-12c.EA1.bin\"<\/pre>\n<\/blockquote>\n<p>Normally, the switch attempts to automatically boot the next valid image in the Flash file system. Here is an example:<\/p>\n<blockquote>\n<pre>Error loading \"flash:c2950-i6q4l2-mz.121-12c.EA1.bin\"\r\nInterrupt within 5 seconds to abort boot process.\r\nLoading \"flash:\/c2950-i6q4l2-mz.121-13.EA1.bin\"...######\r\n########################################################\r\n<em> <span style=\"color: #0000ff;\">!--- Output suppressed.<\/span> <\/em><\/pre>\n<\/blockquote>\n<p>If there is no valid backup image from which to boot, the boot process fails completely. Here is an example:<\/p>\n<blockquote>\n<pre>Error loading \"flash:c2950-i6q4l2-mz.121-12c.EA1.bin\"\r\nInterrupt within 5 seconds to abort boot process.\r\n<strong>Boot process failed...<\/strong><\/pre>\n<\/blockquote>\n<h2><a name=\"topic2\"><\/a>Step-by-Step Recovery Procedure<\/h2>\n<p>Use this solution to solve the problem.<\/p>\n<p><strong>Note:\u00a0<\/strong>A PC must be attached to the console port of the switch, as the <a href=\"http:\/\/www.cisco.com\/en\/US\/products\/hw\/switches\/ps628\/products_tech_note09186a0080169696.shtml#prereq\">Prerequisites<\/a> section of this document states.<\/p>\n<ol type=\"1\">\n<li>If the switch is in a continuous reboot, complete one of the procedures in this step, which depends on your switch model.\n<p><strong>Note:\u00a0<\/strong>If the switch is not in a continuous reboot, but is already at the <tt>switch:<\/tt> prompt, proceed directly to Step 2.<\/p>\n<ol type=\"a\">\n<li>\n<ul>\n<li><strong>Catalyst 2940 and 2950 series switches<\/strong>\n<p><img decoding=\"async\" src=\"http:\/\/www.cisco.com\/image\/gif\/paws\/41845\/192-b.gif\" alt=\"192-b.gif\" usemap=\"\" border=\"0\" \/><\/li>\n<\/ul>\n<\/li>\n<li>Unplug the power cord.<\/li>\n<li>Hold down the <strong>MODE<\/strong> button while you reconnect the power cable to the switch.\n<p>The MODE button is on the left side of the front panel.<\/li>\n<li>Release the <strong>MODE<\/strong> button after the STAT LED goes out.\n<p><strong>Note:\u00a0<\/strong>The LED position can vary slightly, which depends on the model.<\/p>\n<p>You are now at the <tt>switch:<\/tt> prompt.<\/li>\n<li>Proceed to Step 2.<\/li>\n<\/ol>\n<ol type=\"a\">\n<li>\n<ul>\n<li><strong>Catalyst 2970, 3550, 3560 and 3750 series switches<\/strong>\n<p><img decoding=\"async\" src=\"http:\/\/www.cisco.com\/image\/gif\/paws\/41845\/192-c.gif\" alt=\"192-c.gif\" usemap=\"\" border=\"0\" \/><\/li>\n<\/ul>\n<\/li>\n<li>Unplug the power cord.<\/li>\n<li>Hold down the <strong>MODE<\/strong> button while you reconnect the power cable to the switch.\n<p>The MODE button is on the left side of the front panel.<\/li>\n<li>Release the <strong>MODE<\/strong> button after the LED that is above Port 1x goes out.\n<p><strong>Note:\u00a0<\/strong>The LED position can vary slightly, which depends on the model.<\/p>\n<p>You are now at the <tt>switch:<\/tt> prompt.<\/li>\n<li>Proceed to Step 2.<\/li>\n<\/ol>\n<ol type=\"a\">\n<li>\n<ul>\n<li><strong>Catalyst 2955 series switches<\/strong><\/li>\n<\/ul>\n<\/li>\n<li>Issue a break sequence from the keyboard in order to break into switch: mode.\n<p>The terminal application and operating system that you use determine the break sequence to use. HyperTerminal that runs on Windows 2000 uses <strong>Ctrl-Break<\/strong>. For more information, refer to <a href=\"http:\/\/www.cisco.com\/en\/US\/products\/hw\/routers\/ps133\/products_tech_note09186a0080174a34.shtml\">Standard Break Key Sequence Combinations During Password Recovery<\/a>.<\/p>\n<p>This example uses HyperTerminal to break into switch: mode on a 2955:<\/p>\n<blockquote>\n<pre>C2955 Boot Loader (C2955-HBOOT-M) Version 12.1(0.508)EA1, BETA TEST SOFTWARE\r\nCompiled Wed 30-Oct-02 15:24 by antonino\r\nWS-C2955T-12 starting...\r\nBase ethernet MAC Address: 00:03:fd:62:7c:00\r\nXmodem file system is available.\r\nInitializing Flash...\r\nflashfs[0]: 19 files, 2 directories\r\nflashfs[0]: 0 orphaned files, 0 orphaned directories\r\nflashfs[0]: Total bytes: 7741440\r\nflashfs[0]: Bytes used: 4628480\r\nflashfs[0]: Bytes available: 3112960\r\nflashfs[0]: flashfs fsck took 7 seconds.\r\n...done initializing flash.\r\nBoot Sector Filesystem (bs:) installed, fsid: 3\r\nParameter Block Filesystem (pb:) installed, fsid: 4\r\n<strong>*** The system will autoboot in 15 seconds *** Send break character to prevent autobooting.<\/strong>\r\n<em> <span style=\"color: #0000ff;\">!--- Wait until you see this message before !--- you issue the break sequence. !--- Enter <strong>Ctrl-Break<\/strong> with the use of HyperTerminal.<\/span> <\/em>\r\nThe system has been interrupted prior to initializing the\r\nflash filesystem.  The following commands will initialize\r\nthe flash filesystem, and finish loading the operating\r\nsystem software:\r\nflash_init\r\nload_helper\r\nboot\r\nswitch:<\/pre>\n<\/blockquote>\n<\/li>\n<li>Proceed to Step 2.<\/li>\n<\/ol>\n<\/li>\n<li>Issue the <strong>flash_init<\/strong> command and the <strong>load_helper<\/strong> command.\n<p>If the Flash has already initialized, you see this:<\/p>\n<blockquote>\n<pre>switch: <strong>flash_init<\/strong>\r\n  Initializing Flash...\r\n  ...The flash is already initialized.\r\n  switch:<\/pre>\n<\/blockquote>\n<p>If the Flash has not initialized, you see this:<\/p>\n<blockquote>\n<pre>switch: <strong>flash_init<\/strong>\r\nInitializing Flash...\r\nflashfs[0]: 21 files, 2 directories\r\nflashfs[0]: 0 orphaned files, 0 orphaned directories\r\nflashfs[0]: Total bytes: 7741440\r\nflashfs[0]: Bytes used: 4499456\r\nflashfs[0]: Bytes available: 3241984\r\nflashfs[0]: flashfs fsck took 7 seconds.\r\n...done initializing flash.\r\nBoot Sector Filesystem (bs:) installed, fsid: 3\r\nParameter Block Filesystem (pb:) installed, fsid: 4<\/pre>\n<\/blockquote>\n<p>Issue the <strong>load_helper<\/strong> command in order to load any boot helper images. Here is an example:<\/p>\n<blockquote>\n<pre>switch: <strong>load_helper<\/strong>\r\nswitch:<\/pre>\n<\/blockquote>\n<\/li>\n<li>Issue the <strong>dir flash:<\/strong> command in order to view the contents of the Flash file system.\n<p>Determine if there are any Cisco IOS\u00ae 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:<\/p>\n<blockquote>\n<pre>switch: <strong>dir flash:<\/strong>\r\nDirectory of flash:\/\r\n2    -rwx  5        &lt;date&gt;               private-config.text\r\n3    -rwx  110       &lt;date&gt;               info\r\n4    -rwx  976       &lt;date&gt;               vlan.dat\r\n6    -rwx  286       &lt;date&gt;               env_vars\r\n26   -rwx  1592      &lt;date&gt;               config.text\r\n8    drwx  1088      &lt;date&gt;               html\r\n19   -rwx  110       &lt;date&gt;               info.ver\r\n4393472 bytes available (3347968 bytes used)\r\nswitch:<em> <span style=\"color: #0000ff;\">!--- No Cisco IOS images or image directories exist in Flash.<\/span> <\/em><\/pre>\n<\/blockquote>\n<p>If your Flash directory looks like this, proceed directly to Step 4. Step 4 recovers the switch with an Xmodem file transfer.<\/p>\n<p>If there is still an image in Flash, issue the <strong>boot<\/strong> command in order to try to recover the switch. Before you issue the <strong>boot<\/strong> 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.<\/p>\n<ul>\n<li><strong>Catalyst 2940, 2950, and 2955 Flash file system<\/strong>\n<p>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:<\/p>\n<blockquote>\n<pre>switch: <strong>dir flash:<\/strong>\r\nDirectory of flash:\/\r\n3    -rwx  2888547   &lt;date&gt;               c2950-i6q4l2-mz.121-13.EA1.bin        \r\n<em> <span style=\"color: #0000ff;\">!--- The Cisco IOS image file (.bin file) is stored in !--- the flash: directory on Catalyst 2940, 2950, and 2955 series switches.<\/span> <\/em>\r\n4    -rwx  976       &lt;date&gt;               vlan.dat\r\n6    drwx  832       &lt;date&gt;               html\r\n22   -rwx  110       &lt;date&gt;               info\r\n23   -rwx  110       &lt;date&gt;               info.ver\r\n25   -rwx  38        &lt;date&gt;               env_vars\r\n\r\n3132928 bytes available (4608512 bytes used)\r\n<em> <span style=\"color: #0000ff;\">!--- This output is from a Catalyst 2950 switch. Output from a !--- Catalyst 2940 or 2955 varies slightly.<\/span> <\/em><\/pre>\n<\/blockquote>\n<\/li>\n<li><strong>Catalyst 2970, 3550, 3560, and 3750 Flash file system<\/strong>\n<p>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 <strong>dir flash:directory<\/strong> command in order to display the image file in this case.<\/p>\n<blockquote>\n<pre>switch: <strong>dir flash:<\/strong>\r\nDirectory of flash:\/\r\n2    -rwx  976       &lt;date&gt;               vlan.dat\r\n3    -rwx  386       &lt;date&gt;               system_env_vars\r\n4    -rwx  5         &lt;date&gt;               private-config.text\r\n6    -rwx  1554      &lt;date&gt;               config.text\r\n24   drwx  192       &lt;date&gt;               c3550-i5q3l2-mz.121-13.EA1\r\n<em> <span style=\"color: #0000ff;\">!--- You can store the Cisco IOS image file in its own directory. !--- Name the directory with the image name, but exclude the .bin extension.<\/span> <\/em>\r\n42   -rwx  33        &lt;date&gt;               env_vars\r\n<em> <span style=\"color: #0000ff;\">!--- Output suppressed.<\/span> <\/em>\r\nswitch: <strong>dir flash:c3550-i5q3l2-mz.121-13.EA1<\/strong>\r\n<em> <span style=\"color: #0000ff;\">!--- Issue the <strong>dir flash:&lt;directory&gt;<\/strong> !--- command in order to view the Cisco IOS image file.<\/span> <\/em>\r\nDirectory of flash:c3550-i5q3l2-mz.121-13.EA1\/\r\n\r\n25   drwx  832       &lt;date&gt;               html\r\n40   -rwx  3993612   &lt;date&gt;               c3550-i5q3l2-mz.121-13.EA1.bin\r\n<em> <span style=\"color: #0000ff;\">!--- This is where the Cisco IOS image file is stored for a CMS image.<\/span> <\/em>\r\n41   -rwx  252       &lt;date&gt;               info\r\n\r\n9992192 bytes available (6006784 bytes used)\r\n<em> <span style=\"color: #0000ff;\">!--- This output is from a Catalyst 3550 switch. Output from a !--- Catalyst 2970, 3560, or 3750 varies slightly.<\/span> <\/em>\r\nswitch:<\/pre>\n<\/blockquote>\n<\/li>\n<\/ul>\n<p><strong>Attempt to Boot the Image<\/strong><\/p>\n<p>After you have verified where the Cisco IOS image file resides, try to boot the image. Issue either the <strong>boot flash:filename<\/strong> command or the <strong>boot flash:directory\/filename<\/strong> command.<\/p>\n<ul>\n<li><strong>Catalyst 2950<\/strong><br \/>\n<blockquote>\n<pre>switch: <strong>boot flash:c2950-i6q4l2-mz.121-13.EA1.bin<\/strong>      \r\n<em> <span style=\"color: #0000ff;\">!--- This example uses the <strong>boot flash:&lt;filename&gt;<\/strong> !--- command on a 2950.<\/span> <\/em>\r\n Loading \"flash:c2950-i6q4l2-mz.121-13.EA1.bin\"...###########\r\n ###########################################################\r\n<em> <span style=\"color: #0000ff;\">!--- Output suppressed. !--- This command syntax is the same for Catalyst 2940 and 2955 series !--- switches.<\/span> <\/em><\/pre>\n<\/blockquote>\n<\/li>\n<li><strong>Catalyst 3550<\/strong><br \/>\n<blockquote>\n<pre>switch: <strong>boot flash:c3550-i5q3l2-mz.121-13.EA1\/c3550-i5q3l2-mz.121-13.EA1.bin <\/strong>    \r\n<em> <span style=\"color: #0000ff;\">!--- This example uses the <strong>boot flash:&lt;filename&gt;\/&lt;directory&gt;<\/strong> !--- command on a 3550.<\/span> <\/em>\r\nLoading \"flash:c3550-i5q3l2-mz.121-13.EA1\/c3550-i5q3l2-mz.121-13.EA1.bin\"...####\r\n################################################################################           \r\n<em> <span style=\"color: #0000ff;\">!--- Output suppressed. !--- This command syntax is the same for Catalyst 2970, 3560, and 3750 !--- series switches.<\/span> <\/em><\/pre>\n<\/blockquote>\n<\/li>\n<\/ul>\n<p>If you issue the <strong>boot<\/strong> command and the result is in a successful bootup, either the default <tt>switch&gt;<\/tt> prompt or the <tt>hostname&gt;<\/tt> prompt displays.<\/p>\n<blockquote>\n<pre>Press RETURN to get started!\r\nSwitch&gt;\r\n<em> <span style=\"color: #0000ff;\">!--- The bootup was successful.<\/span> <\/em><\/pre>\n<\/blockquote>\n<p>Be sure to verify that you have configured the correct boot statement on the switch. See the <a href=\"http:\/\/www.cisco.com\/en\/US\/products\/hw\/switches\/ps628\/products_tech_note09186a0080169696.shtml#topic3\">Verify<\/a> section of this document.<\/p>\n<p>If you issue the <strong>boot<\/strong> command and the command does not result in a successful bootup, either the <tt>switch:<\/tt> 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.<\/li>\n<li>If the <strong>boot<\/strong> command has failed or there is no valid image from which to boot in Flash, perform an Xmodem file transfer.\n<p>A typical Xmodem file transfer can take up to 2 hours, which depends on the image size.<\/p>\n<p>Download the Cisco IOS image (.bin file) to which you want to upgrade from the <a href=\"http:\/\/www.cisco.com\/tacpage\/sw-center\/sw-lan.shtml\" target=\"_blank\">Software Center (Downloads) &#8211; LAN Switching Software<\/a> <img loading=\"lazy\" decoding=\"async\" src=\"http:\/\/www.cisco.com\/apps-ui\/generic\/interim\/images\/popup_icon.gif\" alt=\"\" width=\"15\" height=\"9\" border=\"0\" \/> (<a href=\"http:\/\/tools.cisco.com\/RPF\/register\/register.do\">registered<\/a> customers only) .<\/p>\n<p><strong>Note:\u00a0<\/strong>Do not use a CMS image (.tar file). This image is a larger image and takes longer to transfer.<\/p>\n<p>Issue the <strong>dir flash:<\/strong> command in order to compare the size of the image in bytes to the free space that remains in Flash. Here is an example:<\/p>\n<blockquote>\n<pre>switch: <strong>dir flash:<\/strong>\r\nDirectory of flash:\/ \r\n<em> <span style=\"color: #0000ff;\">!--- Output suppressed.<\/span> <\/em>\r\n3132928 bytes available (4608512 bytes used)\r\n<em> <span style=\"color: #0000ff;\">!--- There are approximately 3 MB of Flash space available for a new image.<\/span> <\/em><\/pre>\n<\/blockquote>\n<p>If necessary, issue the <strong>delete<\/strong> command in order to delete any corrupt images that remain. Here is an example:<\/p>\n<blockquote>\n<pre>switch: <strong>delete flash:c2950-i6q4l2-mz.121-12c.EA1.bin<\/strong>         \r\n<em> <span style=\"color: #0000ff;\">!--- Issue the <strong>delete flash:&lt;filename&gt;<\/strong> !--- command in order to delete a Cisco IOS image.<\/span> <\/em>\r\nAre you sure you want to delete \"flash:c2950-i6q4l2-mz.121-12c.EA1.bin\" (y\/n)? <strong>y<\/strong>\r\n<em> <span style=\"color: #0000ff;\">!--- Enter <strong>y<\/strong> for yes if you want to delete the image.<\/span> <\/em>\r\nFile \"flash:c2950-i6q4l2-mz.121-12c.EA1.bin\" deleted\r\nswitch:<\/pre>\n<\/blockquote>\n<p>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.<\/p>\n<ol type=\"a\">\n<li>Issue the <strong>copy xmodem: flash:filename<\/strong> command on the switch.\n<p>Here is an example:<\/p>\n<blockquote>\n<pre>switch: <strong>copy xmodem: flash:c2955-i6q4l2-mz.121-13.EA1.bin<\/strong>\r\nBegin the Xmodem or Xmodem-1K transfer now...\r\nCCC<\/pre>\n<\/blockquote>\n<\/li>\n<li>From the top of the HyperTerminal window, choose <strong>Transfer &gt; Send File<\/strong>.\n<p><img decoding=\"async\" src=\"http:\/\/www.cisco.com\/image\/gif\/paws\/41845\/192-d.gif\" alt=\"192-d.gif\" usemap=\"\" border=\"0\" \/><\/li>\n<li>Choose the <strong>Xmodem<\/strong> protocol in the Send File dialog box and click <strong>Browse<\/strong> in order to select the Cisco IOS image (.bin file) that you downloaded previously.\n<p><img decoding=\"async\" src=\"http:\/\/www.cisco.com\/image\/gif\/paws\/41845\/192-e.gif\" alt=\"192-e.gif\" usemap=\"\" border=\"0\" \/><\/li>\n<li>Click <strong>Send<\/strong> in order to begin the Xmodem transfer.\n<p><img decoding=\"async\" src=\"http:\/\/www.cisco.com\/image\/gif\/paws\/41845\/192-f.gif\" alt=\"192-f.gif\" usemap=\"\" border=\"0\" \/><\/p>\n<p>The Xmodem file transfer begins. This transfer can take up to 2 hours, which depends on the size of the image.<\/p>\n<blockquote>\n<pre>CCCCCCC.........................................................................\r\n................................................................................\r\n................................................................................\r\n................................................................................\r\n................................................................................\r\n................................................................................\r\n................................................................................\r\n................................................................................\r\n.............................................................................\r\nFile \"xmodem:\" successfully copied to \"flash:c2955-i6q4l2-mz.121-13.EA1.bin\"\r\n<em> <span style=\"color: #0000ff;\">!--- If the Xmodem file transfer fails for some reason, restart the process. !--- If the Xmodem file transfer is successful, you return to the !--- switch: prompt.<\/span> <\/em>\r\nswitch:<\/pre>\n<\/blockquote>\n<\/li>\n<\/ol>\n<\/li>\n<li>Boot the new image that you just copied over with the Xmodem procedure.\n<p>Issue the <strong>boot flash:filename<\/strong> command, as this example shows:<\/p>\n<blockquote>\n<pre>switch: boot flash:c2955-i6q4l2-mz.121-13.EA1.bin\r\nLoading \"flash:c2955-i6q4l2-mz.121-13.EA1.bin\"...###############################\r\n################################################################################\r\n<em> <span style=\"color: #0000ff;\">!--- Output suppressed.<\/span> <\/em>\r\nPress RETURN to get started!\r\nSwitch&gt;\r\n<em> <span style=\"color: #0000ff;\">!--- The bootup was successful.<\/span> <\/em><\/pre>\n<\/blockquote>\n<p>Be sure to verify that your boot statements are set correctly.<\/li>\n<\/ol>\n<h3><a name=\"speedrecovery\"><\/a>How to Speed Up Xmodem Recovery<\/h3>\n<p>When a user tries to recover the switch from a corrupted or missing IOS, the <strong>copy xmodem: flash:[IOS filename]<\/strong> command might not be displayed under the <tt>switch:<\/tt> prompt. The <strong>copy<\/strong> command might be displayed under the <tt>switch:<\/tt> prompt, but not the <strong>copy xmodem:<\/strong> command.<\/p>\n<p>Complete these steps in order to speed up the Xmodem recovery:<\/p>\n<ol type=\"1\">\n<li>Set the baud rate to <strong>115200<\/strong> on the <tt>switch:<\/tt> prompt.<br \/>\n<blockquote>\n<pre>switch: <strong>set BAUD 115200<\/strong>\r\n<em> <span style=\"color: #0000ff;\">!--- The screen goes blank after you enter this command.<\/span> <\/em><\/pre>\n<\/blockquote>\n<\/li>\n<li>Restart HyperTerminal.<\/li>\n<li>Under COM PORT properties, select the bits per second as <strong>115200<\/strong>. The <tt>switch:<\/tt> prompt is displayed.<\/li>\n<li>Start the Xmodem recovery.<\/li>\n<li>After the Xmodem recovery, set the BAUD rate back to <strong>9600<\/strong>. If the <strong>set BAUD 9600<\/strong> command does not bring the baud rate to 9600, issue the <strong><a href=\"http:\/\/www.cisco.com\/en\/US\/docs\/switches\/lan\/catalyst3750\/software\/release\/12.2_40_se\/command\/reference\/bootldr.html#wp1012631\">unset<\/a> BAUD<\/strong> command in order to bring the baud rate to a default value of 9600 bps.<\/li>\n<\/ol>\n<h2><a name=\"topic3\"><\/a>Verify<\/h2>\n<p>Complete these steps:<\/p>\n<ol type=\"1\">\n<li>Issue the <strong>show version<\/strong> command in order to verify the current version of software that you run.\n<p>Here is an example:<\/p>\n<blockquote>\n<pre>2955#<strong>show version<\/strong>\r\n Cisco Internetwork Operating System Software\r\n IOS (tm) C2955 Software (C2955-I6Q4L2-M), Version <strong>12.1(13)EA1<\/strong>, RELEASE SOFTWARE\r\n <em> <span style=\"color: #0000ff;\">!--- This is the current version of software.<\/span> <\/em><\/pre>\n<\/blockquote>\n<\/li>\n<li>Issue the <strong>dir flash:filename<\/strong> command in order to display the Cisco IOS image (.bin file) on a Catalyst 2940, 2950 or 2955.<br \/>\n<blockquote>\n<pre>2950#<strong>dir flash:<\/strong>\r\nDirectory of flash:\/\r\n3  -rwx           5   Mar 01 1993 00:12:55  private-config.text\r\n4  -rwx     2905856   Jan 01 1970 03:06:25  <strong>c2955-i6q4l2-mz.121-13.EA1.bin<\/strong>\r\n<em> <span style=\"color: #0000ff;\">!--- The Cisco IOS image (.bin file) is stored in flash: !--- on a Catalyst 2940, 2950 or 2955. !--- Output suppressed.<\/span> <\/em><\/pre>\n<\/blockquote>\n<p>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:<\/p>\n<blockquote>\n<pre>3550#<strong>dir flash:<\/strong>\r\nDirectory of flash:\/\r\n2  -rwx         976   Mar 01 1993 21:47:00  vlan.dat\r\n4  -rwx           5   Mar 06 1993 23:32:04  private-config.text\r\n6  -rwx        1554   Mar 06 1993 23:32:04  config.text\r\n7  <strong>d<\/strong>rwx         192   Mar 01 1993 00:14:02  <strong>c3550-i5q3l2-mz.121-13.EA1<\/strong>\r\n<em> <span style=\"color: #0000ff;\">!--- Notice the \"d\" for directory in the permission statement. !--- This is an image directory that is installed when you upgrade the !--- switch with a CMS image. !--- The Cisco IOS image (.bin file) is inside this directory.<\/span> <\/em>\r\n5  -rwx     3823261   Mar 01 1993 00:46:01  <strong>c3550-i5q3l2-mz.121-12c.EA1.bin<\/strong>          \r\n<em> <span style=\"color: #0000ff;\">!--- This is another Cisco IOS image (.bin file).<\/span> <\/em>\r\n8  -rwx          33   Mar 01 1993 00:14:06  env_vars\r\n9  -rwx         384   Mar 01 1993 00:14:06  system_env_vars\r\n15998976 bytes total (6168576 bytes free)\r\n<em> <span style=\"color: #0000ff;\">!--- This output is from a Catalyst 3550 switch. Output from a !--- Catalyst 2970, 3560, or 3750 varies slightly.<\/span> <\/em>\r\n3550#<\/pre>\n<\/blockquote>\n<p>You may need to issue the <strong>dir flash:directory<\/strong> command on a Catalyst 3550 in order to display the Cisco IOS image (.bin file). Here is an example:<\/p>\n<blockquote>\n<pre>3550#<strong>dir flash:c3550-i5q3l2-mz.121-13.EA1<\/strong>\r\nDirectory of flash:\/c3550-i5q3l2-mz.121-13.EA1\/\r\n23  drwx         832   Mar 01 1993 00:12:00  html\r\n40  -rwx     3993612   Mar 01 1993 00:14:02  c3550-i5q3l2-mz.121-13.EA1.bin\r\n41  -rwx         252   Mar 01 1993 00:14:02  info\r\n15998976 bytes total (6168576 bytes free)\r\n<em> <span style=\"color: #0000ff;\">!--- This output is from a Catalyst 3550 switch. Output from a !--- Catalyst 2970, 3560, or 3750 varies slightly.<\/span> <\/em>\r\n3550#<\/pre>\n<\/blockquote>\n<\/li>\n<li>Issue the <strong>show boot<\/strong> command in order to verify that the boot statement is set correctly.\n<p>Here is an example:<\/p>\n<blockquote>\n<pre>Switch#<strong>show boot<\/strong>\r\nBOOT path-list:\r\n<em> <span style=\"color: #0000ff;\">!--- No boot system statement is set in this case. !--- Output suppressed.<\/span> <\/em><\/pre>\n<\/blockquote>\n<p><strong>Note:\u00a0<\/strong>Boot statements do not display in the configuration or when you issue the <strong>show run<\/strong> command on any of the fixed configuration switches that this document covers. You must issue the <strong>show boot<\/strong> command in order to display boot statements.<\/p>\n<p>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 <strong>boot system flash:filename<\/strong> command.<\/p>\n<blockquote>\n<pre>2955#<strong>configure terminal<\/strong>\r\n2955(config)#<strong>boot system flash:c2955-i6q4l2-mz.121-13.EA1.bin<\/strong>\r\n<em> <span style=\"color: #0000ff;\">!--- This is how to set a boot system statement on a Catalyst 2940, 2950, or 2955.<\/span> <\/em>\r\n2955(config)#<strong>end<\/strong>\r\n2955#\r\n2955#<strong>show boot<\/strong>\r\nBOOT path-list:       flash:c2955-i6q4l2-mz.121-13.EA1.bin      \r\n<em> <span style=\"color: #0000ff;\">!--- Output suppressed.<\/span> <\/em><\/pre>\n<\/blockquote>\n<p>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 <strong>boot system flash:directory\/filename<\/strong> command. Here is an example:<\/p>\n<blockquote>\n<pre>3550#<strong>configure terminal<\/strong>\r\n3550(config)#<strong>boot system flash:c3550-i5q3l2-mz.121-13. EA1\/c3550-i5q3l2-mz.121-13.EA1.bin<\/strong>\r\n<em> <span style=\"color: #0000ff;\">!--- This command should be on one line. !--- This is how to set a boot system statement on a Catalyst !--- 3550 if the Cisco IOS image (.bin file) is in its own image directory.<\/span> <\/em>\r\n3550#<strong>end<\/strong>\r\n3550#\r\n3550#<strong>show boot<\/strong>\r\nBOOT path-list: <strong>flash:c3550-i5q3l2-mz.121-13.EA1\/c3550-i5q3l2-mz.121-13.EA1.bin<\/strong>\r\n<em> <span style=\"color: #0000ff;\">!--- Output suppressed.<\/span> <\/em><\/pre>\n<\/blockquote>\n<\/li>\n<\/ol>\n<blockquote>\n<pre><em>[QUELLE: <a href=\"http:\/\/www.cisco.com\/en\/US\/products\/hw\/switches\/ps628\/products_tech_note09186a0080169696.shtml\">http:\/\/www.cisco.com\/en\/US\/products\/hw\/switches\/ps628\/products_tech_note09186a0080169696.shtml<\/a>]<\/em><\/pre>\n<\/blockquote>\n","protected":false},"excerpt":{"rendered":"<p>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 [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[22],"tags":[],"class_list":["post-158","post","type-post","status-publish","format-standard","hentry","category-cisco"],"_links":{"self":[{"href":"https:\/\/blog.4-it.net\/index.php?rest_route=\/wp\/v2\/posts\/158","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.4-it.net\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.4-it.net\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.4-it.net\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.4-it.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=158"}],"version-history":[{"count":2,"href":"https:\/\/blog.4-it.net\/index.php?rest_route=\/wp\/v2\/posts\/158\/revisions"}],"predecessor-version":[{"id":160,"href":"https:\/\/blog.4-it.net\/index.php?rest_route=\/wp\/v2\/posts\/158\/revisions\/160"}],"wp:attachment":[{"href":"https:\/\/blog.4-it.net\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=158"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.4-it.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=158"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.4-it.net\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=158"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}