Guest

Cisco Catalyst 4000 Series Switches

Field Notice: Successive Power Cycling During a Boot Leaves the Switch in ROMMON


Updated October 10, 2002

November 17, 2000


Products Affected

  • WS-C2948G

  • WS-C4003

  • WS-C4912G

Problem Description

If the switch is power cycled three or more times during the boot process, it will come up in ROM monitor (ROMMON) mode. It is also possible for the configuration to be lost during a failed boot caused by a power failure.

Note:?This problem only occurs on the following switches: WS-C2948G, WS-C4912G, and WS-C4003 with ROMMON versions 4.4(1) or 4.5(1).

Background

During an extreme power outage, where the switch boot process gets interrupted by successive power cycling, the switch will not recover from the third or fourth power sequence and stops at the ROMMON prompt. Typing boot at the ROMMON prompt restores proper operation.

Problem Symptoms

This problem only occurs if the system is reset three or more times in rapid succession while the system is trying to come up. The reported scenario in which this happened was during an extreme power outage, where the power was coming up/down for an extended period of time. If this occurs, you can recover by typing boot at the ROMMON prompt.

Workaround/Solution

Workaround:

Issuing a boot bootflash: will get the switch to continue booting.

Solution:

This problem has been fixed in 5.5(5) boot PROM (for use with Catalyst OS 5.1(x) to 5.5(x)) and 6.1(4) boot PROM (required only for upgrade to Catalyst OS 7.1(1)), both of which can be upgraded via software. To check the PROM version, type the version command at the ROMMON prompt, or check the "Fw" field in the output of show module command at the console prompt.

Follow the upgrade procedure below.

Upgrading a Catalyst 4000-family product to ROM version 5.5(5)

This document describes the procedure for upgrading the ROM monitor (ROMMON) on Cat4000-based products.

The procedure to upgrade the ROMMON is slightly complex. It can be done entirely over a Telnet connection if all goes well, but if something fails, having access to the console serial port is necessary. If done improperly, the system can be rendered unbootable and will need to be returned to Cisco for repair. It is recommended that you read all of this procedure before beginning the process.

  1. Get the PROM upgrade binary from Cisco.com, cat4000-promupgrade.5-5-5.bin.

    Place it into a directory on a TFTP server that is accessible from the switch to be upgraded.

  2. From the NMP software prompt, enter enable mode:

      Console>enable
      Enter password: 
      Console> (enable)
    
  3. Verify that the switch is not already running a newer ROMMON than the one which you are going to try to install.

      Console> (enable)show mod
      <...>
      Mod MAC-Address(es)                        Hw     Fw         Sw  --- -------------------------------------- ------ ---------- -----------------  1   xx-xx-xx-xx-xx-xx to xx-xx-xx-xx-xx-xx 1.0    4.4(1)     5.4(1)
    

    The version number under "Fw" indicates the ROMMON, or firmware version number.

  4. Ensure that there is sufficient space in flash to store the new image by using the dir bootflash: command. If there is insufficient space, you will need to delete one or more images and then use the squeeze bootflash: command to reclaim the space.

  5. Download the PROM upgrade image into flash:

      Console> (enable)copy tftp flash  
      IP address or name of remote host []? <ip address>  
      Name of file to copy from []? <path> 
      /cat4000-promupgrade.5-5-5.bin  
      Flash device []? bootflash  
      Name of file to copy to []? cat4000-promupgrade.5-5-5.bin  
      9205592 bytes available on device bootflash, proceed (y/n) [n]? y  
      CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC  
      File has been copied successfully.
    
  6. From the online software, make note of the current autoboot state using the show boot command.

    Example:

      Console> (enable) show boot  
      BOOT variable = bootflash:cat4000.5-5-5.bin,1;  
      CONFIG_FILE variable = bootflash:switch.cfg  
      Configuration register is 0x102  
      ignore-config: disabled  
      auto-config: non-recurring  
      console baud: 9600 
      boot: image specified by the boot system commands
    
  7. Ensure that the last line is as it appears above, reading "boot: image specified by the boot system commands". If not, use the set boot config-register command to fix it.

        Console > (enable)set boot config-register boot system      
        Configuration register is 0x102    
        ignore-config: disabled    
        auto-config: non-recurring    
        console baud: 9600    
        boot: image specified by the boot system commands
        Prepend the promupgrade image to the boot string:
    
  8.   Console> (enable)set boot system flash bootflash:cat4000-promupgrade.5-5-5.bin prepend
      BOOT variable = bootflash:cat4000-promupgrade.5-5-5.bin,1;bootflash:cat4000.5-5-5.bin,1;
    
  9. Reset the switch.

    Note:?It is IMPORTANT that once you have reset the switch for the first time, it not be reset, power cycled, hot swapped, and so on for at least five minutes. Upgrading the ROM monitor firmware can take some time, and if interrupted can leave the switch in a state where it must be returned to Cisco for repair.

    Note:?If you are telnetting in, resetting will disconnect your Telnet session. The switch, when reset, will first boot the promupgrade image. This is a special program that will erase the ROM image out of flash and install the new one. It will then exit, causing the box to reset again. The system will then boot the next image in the boot string, namely the online software.

    Note:?If all goes well, a short time after the reset (somewhere around 2-5 minutes), the switch will reboot back into the online software, functioning correctly.

        Console> (enable)reset
        This command will reset the system.
        Do you want to continue (y/n) [n]? y
        2000 Apr 03 11:51:12 %SYS-5-SYS_RESET:System reset from Console//
     
    
  10. After resetting the switch, if you are monitoring the console serial port, you will see something like the following:

      0:00.530901: ig0: 00:10:7b:aa:d3:fe is 172.20.59.203
      0:00.531660: netmask: 255.255.255.0
      0:00.532030: broadcast: 172.20.59.255
      0:00.532390: gateway: 172.20.59.1
      WS-X4012 bootrom version 4.5(1), built on 2000.04.03 15:20:09
      H/W Revisions: Meteor: 2 Comet: 8 Board: 1
      Supervisor MAC addresses: 00:10:7b:AA:d0:00 through 00:10:7b:AA:d3:ff (1024 
      addresses)
      Installed memory: 32 MB
      Testing LEDs.... done!
      The system will autoboot in 5 seconds.
      Type control-C to prevent autobooting.
      rommon 1 > 
      The system will now begin autobooting.
      Autobooting image: "bootflash:cat4000-promupgrade.5-5-5.bin"
      CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC#############################
      Replacing ROM version 4.4(1) with version 5.5(5)  
      Upgrading your PROM... DO NOT RESET the system
      unless instructed or it may NOT be bootable!!!
      Beginning erase of 524288 bytes at offset 0x0... Done!
      Beginning write of system prom (467456 bytes at offset 0x0)...
      This could take as little as 10 seconds or up to 2 minutes.
      Please DO NOT RESET!
      *******************************************
      Success!
      System will reset in 2 seconds...
      <...>
    

    No intervention is necessary to get the upgrade to complete. Please take care not to cycle power or otherwise reset the system while this upgrade is being performed, or it may be rendered unbootable. The system should then reboot back into the online software:

      0:00.530856: ig0: 00:10:7b:AA:d3:Fe is 172.20.59.203
      0:00.531616: netmask: 255.255.255.0
      0:00.531967: broadcast: 172.20.59.255
      0:00.532342: gateway: 172.20.59.1
      WS-X4012 bootrom version 5.4(1), built on 2000.04.03 15:20:09
      H/W Revisions: Meteor: 2 Comet: 8 Board: 1
      Supervisor MAC addresses: 00:10:7b:AA:d0:00 through 00:10:7b:AA:d3:ff (1024 
      addresses)
      Installed memory: 64 MB
      Testing LEDs.... done!
      The system will autoboot in 5 seconds.
      Type control-C to prevent autobooting.
      rommon 1 > 
      The system will now begin autobooting.
      Autobooting image: "bootflash:cat4000.5-5-5.bin"
      CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
      CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC##################################### 
    
  11. Reconnect to the switch via Telnet if necessary. Go back into enable mode.

  12. Verify that the system is now running the new version of the ROM monitor, as per step 3.

  13. Remove the promupgrade program from the autoboot string:

        Console> (enable) clear boot system flash bootflash:cat4000-promupgrade.5-5-5.bin
        BOOT variable = bootflash:cat4000.5-5-5.bin,1;
     
    
  14. Delete the promupgrade program from flash:

      Console> (enable) del bootflash:cat4000-promupgrade.5-5-5.bin
       
    

    Squeeze the flash to reclaim unused space:

      Console> (enable) squeeze bootflash:
      All deleted files will be removed, proceed (y/n) [n]? y
      Squeeze operation may take some time, proceed (y/n) [n]? y
    

Upgrading a Catalyst 4000-family product to ROM version 6.1(4):

Follow the steps below:

  1. Get the appropriate promupgrade program from CCO, cat4000-promupgrade.6-1-4.bin. Place it into a directory on a TFTP server that is accessible from the switch to be upgraded.

  2. From the CatOS software prompt, enter enable mode:

      Console>enable
      Enter password: 
      Console> (enable)
    
  3. Verify that the switch is not already running a newer ROMMON than the one to which you are upgrading. The ROMMON version number is printed as the "System Bootstrap Version" in the output of the show version command.

  4. Ensure that there is sufficient space in flash to store the promupgrade image by using the dir bootflash: command. If there is insufficient space, delete one or more images and then use the squeeze bootflash: command to reclaim the space.

  5. Download the promupgrade image into flash:

    Console> (enable) copy tftp flash
         IP address or name of remote host []? <tftpserver>
         Name of file to copy from []? /cat4000-promupgrade.6-1-4.bin
         Flash device []? bootflash
         Name of file to copy to []? cat4000-promupgrade.6-1-4.bin
         9205592 bytes available on device bootflash, proceed (y/n) [n]? y
         CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
         File has been copied successfully
    
  6. From the online software, note the current autoboot configuration using the show boot command.

  7. Ensure that the last line in the output of show boot command reads: boot: image specified by the boot system commands. If not, use the set boot config-register command to fix it.

  8. Prepend the promupgrade image to the boot string:

        Console> (enable) set boot system flash bootflash:cat4000-promupgrade.6-1-4.bin 
        prepend
        BOOT variable = bootflash:cat4000-promupgrade.6-1-4.bin,1;bootflash:cat4000.5-5-8.bin,1;
    
  9. Reset the switch to allow it to boot the promupgrade program.

    Note:?DO NOT interrupt this booting process, by performing a reset, power cycle, OIR of the supervisor, etc. for at least five minutes! If the process is not allowed to complete properly, the switch must be returned to Cisco for repair.

Note:?A Telnet session is disconnected when the switch is reset, and you will lose connectivity to the switch for some time.

If all goes well, the switch reboots back into the online software somewhere around 2-5 minutes after reset.

DDTS

To follow the bug ID link below and see detailed bug information, you must be a registered user and you must be logged in.

CSCdm80016 (registered customers only)

CSCdr13141 (registered customers only)

For More Information

If you require further assistance, or if you have any further questions regarding this field notice, please contact the Cisco Systems Technical Assistance Center (TAC) by one of the following methods:

Receive Email Notification For New Field Notices

Product Alert Tool - Set up a profile to receive email updates about reliability, safety, network security, and end-of-sale issues for the Cisco products you specify.