Guest

Cisco Catalyst 6500 Series Switches

Field Notice: Rommon Upgrade for the WS-SVC-CMM


March 16, 2004


Products Affected

WS-C6509=
SC6K-2.1-CSM
WS-C6513=

Problem Description

Ethernet Out of Band Channel (EOBC) disaster recovery is not supported for the Communications Media Module (CMM) when in the same chassis as a Supervisor 720. The CMM looks for the Supervisor in slot 1 or 2 of the Catalyst 6000. The Supervisor 720 is in slot 5 or 6 on the Catalyst 6509 and slot 7 or 8 on the Catalyst 6513. In order to support EOBC disaster recovery on the Supervisor 720, a new rommon image is required.

Background

Prior to this procedure, there was no provision to upgrade the ROMMON on the CMM gateway using the IOS command line interface (CLI). This procedure provides the steps to perform a ROMMON upgrade in the field from the IOS CLI.

Problem Symptoms

Disaster recovery for Sup720 supervisor does not work without the ROMMON upgrade.

Workaround/Solution

The ROMMON upgrade procedure takes about 15 minutes. The rommon upgrade procedure involves copying the .srec file to bootflash, erasing the current ROMMON and writing in a new ROMMON image. Care should be taken to follow the steps as mentioned. An unsuccessful upgrade may mean that the CMM card needs to be returned for an RMA. It is advisable to read the procedure first, understand the procedure, and note any warnings before performing the actual upgrade.

Note: Do NOT attempt to perform the upgrade on multiple cards simultaneously.

Note: The ROMMON upgrade is a very CPU intensive operation. Perform the ROMMON upgrade during a maintenance window when there is NO traffic on the CMM module.

Note: If using MGCP trombone download for the configurations, the command no ccm-manager config may need to be entered so that the whole trombone configuration is not downloaded again after the power cycle.

  1. Download the CMM_RM.srec.122-1r.zip ROMMON File from the Catalyst 6000/Cisco 7600 ROMMON (registered customers only) page. Place the file in the bootflash using TFTP. Take special care not to erase the existing files on the bootflash during the TFTP procedure.

    Perform a dir bootflash: command and ensure the amount of space available is sufficient. The bootflash must have at least 1000000 bytes free to store the CMM_RM.srec.122-1r.T2 file.

    CMM-prompt#copy tftp bootflash:
    

    There will be a request for the TFTP address. Enter the appropriate TFTP address at the location. In the following step, 171.69.1.129 is shown as an example:

    CMM-prompt#Address or name of remote host [ ]? 171.69.1.129
    

    The CMM will ask for the source filename. Enter the .srec filename. Here CMM_RM.srec.122-1r.T2 is shown as an example:

    CMM-prompt# Source filename [ ]? CMM_RM.srec.122-1r.T2
    

    The CMM will ask for the destination filename and suggest CMM_RM.srec.122-1r.T2 as the default. Press Enter once to retain the default destination filename or rename it to whatever .srec filename desired.

    CMM-prompt# Destination filename [CMM_RM.srec.122-1r.T2]?
    

    Warning: The CMM will ask if the bootflash is to be erased before copying. Please respond with an N to retain the contents of the bootflash, such as host images.

    CMM-prompt# Erase bootflash: before copying [confirm]? N
    

    The file is then copied to bootflash:. The output will look as follows:

    Loading CMM_RM.srec.122-1r.T2 from 171.69.1.129 (via GigabitEthernet1/0): !
         !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
         !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
         [OK - 622901 bytes]
    
         Verifying checksum... OK (0x2DDC)
         622901 bytes copied in 5.512 secs (113008 bytes/sec)
    
  2. Check to ensure that the CMM_RM.srec.122-1r.T2 file is present in the bootflash. The output will be similar to the example below, depending on the files present in the bootflash. Note the presence of the file named CMM_RM.srec.122-1r.T2 .

    CMM-prompt#dir bootflash:
         Directory of bootflash:/
    
         1 -rw- 7901384 wscmm-i6s-mzoct3.test1
         2 -rw- 7899484 wscmm-i6s-mz-Missouri
         3 -rw- 7901328 wscmm-i6s-mzoct8.test1
         4 -rw- 622901 CMM_RM.srec.122-1r.T2
    
         33030144 bytes total (8704788 bytes free)
    

    Note: If the appropriate host image is not present in the bootflash, the rommon upgrade procedure will not be performed and an error message will be displayed. This is because the appropriate host image is required in the bootflash in order to reboot the system after the power cycle is completed. Ensure that a host software image is present in bootflash.

  3. Performing the actual rommon upgrade will take several minutes once the following command is entered. It will suspend for some time in between. Once it is completed it will return to the prompt. So please be patient.

    CMM-prompt#test mscmm romupd CMM_RM.srec.122-1r.T2 
    
    
         eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee
         eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee
         eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee
         eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee
         eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee
         eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee
         eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee
         eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee
         eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee
         eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee
         .............................................................
         ..............................................................
         ..............................................................
         ..............................................................
         ..............................................................
    
    
         rommon upgrade completed.
    

    Ensure that the host image is present in bootflash and power cycle the CMM. At this point, if the CMM has automatically reloaded the system, the rommon upgrade is complete. If the CMM does not automatically reload, follow the steps below to recycle the CMM:

  4. Power down the CMM module from the supervisor and then power it up. This is very critical. No other commands should be executed until this point. The other option is to pull the CMM module out and re-insert it. The CMM module should go to the rommon prompt. From the rommon prompt, bootup with the required host image.

    Supervisor-prompt#set module power down 
         Supervisor-prompt#set module power up
    

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.

DDTS

Description

CSCec22540 (registered customers only)

Jagger EOBC disaster recovery not supported on Sup 720

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.