Cisco Catalyst 6000 Series Switches

Revised April 28, 2004

April 16, 2002

Products Affected

• WS-X6K-SUP1A-MSFC

• WS-X6K-SUP1A-MSFC2

• WS-X6K-S2-MSFC2

• WS-F6K-DFC

• WS-X6816-GBIC

Problem Description

Systems that shipped from Cisco with Cisco IOS® Software (Catalyst Cisco IOS Software, not Catalyst OS [CatOS]) configured on the Supervisor Engine may have an incompatible flash format on the Supervisor Engine bootflash, Multilayer Switch Feature Card 2 (MSFC2) bootflash or Distributed Forwarding Card (DFC) bootflash. This issue is also documented in the DDTS referenced below.

Background

During manufacturing, testing diagnostics are used to validate the functional operation of these devices. The default format used was for CatOS software. When the requested OS was for Cisco IOS Software, reformatting of the flash devices was not performed. This was a manufacturing issue that has been corrected by having all flash device formats compatible with the final OS that ships on the cards.

Problem Symptoms

Supervisor Engine Bootflash

If the Supervisor Engine bootflash has the wrong format, a file cannot be written to it or deleted. This prevents the OS from being upgraded and prevents crashinfo files from being saved in the event of a crash.

To check if the Supervisor Engine has been formatted correctly for Cisco IOS Software, use the show sup-bootflash: all command.

The output of the command is:

    -#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name
     1  .. unknown  3F67A64B 13B88BC  24  20154428 Jan 12 2002 06:49:41 c6sup22-jsv-mz.121-8a.E3


    11827012 bytes available (20154556 bytes used)


    -------- F I L E S Y S T E M S T A T U S --------

    Device Number = 0
    DEVICE INFO BLOCK: 
    Magic Number = 6887635 File System Vers = 10000 (1.0)
    Length = 2000000 Sector Size = 80000 
   Programming Algorithm = 7 Erased State = FFFFFFFF
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    File System Offset = 80000 Length = 1E80000
    MONLIB Offset = 100 Length = 10028 
    Bad Sector Map Offset = 7FFF8 Length = 8 
    Squeeze Log Offset = 1F00000 Length = 80000 
    Squeeze Buffer Offset = 1F80000 Length = 80000 
    Num Spare Sectors = 0
    Spares:

Check the Programming Algorithm. If the Programming Algorithm is 7, your sup-bootflash is incorrectly formatted for Cisco IOS Software.

MSFC2 Bootflash

The format of the bootflash does not allow any images to be deleted or saved on the bootflash without first doing a complete reformat and download of the original Cisco IOS Software. The following error message is received if the bootflash has the wrong structure:

Device driver error writing device

Another way to check if the bootflash format on the MSFC2 is correct is to issue the show bootflash: all command.

The output of the command is:

    -#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name
     1  .. unknown  3F67A64B 13B88BC  24  20154428 Jan 12 2002 06:49:41 c6sup22-jsv-mz.121-8a.E3


    11827012 bytes available (20154556 bytes used)


    -------- F I L E S Y S T E M S T A T U S --------

    Device Number = 0
    DEVICE INFO BLOCK: 
    Magic Number = 6887635 File System Vers = 10000 (1.0)
    Length = 2000000 Sector Size = 80000 
   Programming Algorithm = 7 Erased State = FFFFFFFF
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    File System Offset = 80000 Length = 1E80000
    MONLIB Offset = 100 Length = 10028 
    Bad Sector Map Offset = 7FFF8 Length = 8 
    Squeeze Log Offset = 1F00000 Length = 80000 
    Squeeze Buffer Offset = 1F80000 Length = 80000 
    Num Spare Sectors = 0
    Spares:

Check the Programming Algorithm. If the Programming Algorithm is 7, your bootflash is incorrectly formatted for Cisco IOS Software.

DFC Bootflash

If the DFC bootflash has the wrong format, a file cannot be written to it or deleted. This prevents crashinfo files from being saved in the event of a crash.

To check if the bootflash has been formatted correctly, issue the show dfc#7-bootflash all command.

Note:?This example shows DFC#7 in slot 7. DFCs may be in various slots.

 No files on device
    
    15204352 bytes available (0 bytes used)
    
    -------- F I L E S Y S T E M S T A T U S --------
    Device Number = 2
    DEVICE INFO BLOCK:
    Magic Number = 6887635 File System Vers = 10000 (1.0)
    Length = 1000000 Sector Size = 80000
   Programming Algorithm = 7 Erased State = FFFFFFFF
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
    File System Offset = 80000 Length = E80000
    MONLIB Offset = 100 Length = C648
    Bad Sector Map Offset = 7FFFC Length = 4
    Squeeze Log Offset = F00000 Length = 80000
    Squeeze Buffer Offset = F80000 Length = 80000
    Num Spare Sectors = 0
    Spares:

Check the Programming Algorithm. If the Programming Algorithm is 7, your DFC bootflash is incorrectly formatted for Cisco IOS Software.

Workaround/Solution

Supervisor Engines

The following procedure is not traffic-impacting, but should be completed during a controlled maintenance window.

Reformat the sup-bootflash and slavesup-bootflash:

1. Confirm the existence of a Cisco IOS image on the sup-bootflash, slavesup-bootflash and PC card (if one is installed).

2. Format the sup-bootflash.

3. Copy the image file from slavesup-bootflash to sup-bootflash.

4. Format the slavesup-bootflash.

5. Copy the image file from sup-bootflash to slavesup-bootflash.

MSFC2

After you have determined that the bootflash is incorrectly formatted, you can reformat the bootflash with the format bootflash: command.

Note:?Never attempt to format the bootflash if you previously tried to write or delete to the MSFC2 bootflash. If you have tried to write or delete items from the bootflash and you received the Device driver error writing device message, you will fail a format attempt and leave the system inoperable after that point. You must reload the system Cisco IOS image and re-setup your connection to CCO before formatting the bootflash.

DFC

format dfc#n-bootflash:

To verify proper formatting, try copying a file to the bootflash. This example is one way to facilitate this:

router#copy running-config dfc#n-bootflash:test-config
Destination filename [test-config]?
7352 bytes copied in 6.720 secs (1225 bytes/sec)


router#show dfc#n-bootflash:
-#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name
 1  ..  config  1B5AB261  81D38   11    7352   Mar 15 2002 15:21:38 test-config

15196872 bytes available (7480 bytes used)
router#

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.

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:

• Open a service request on Cisco.com
• By email
• By telephone

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.