Guest

Cisco Catalyst 6000 Series Switches

Field Notice: GBIC EEPROM Errors Incorrect in Cisco IOS® Software Release 12.1(13)E for the Catalyst 6000


October 15, 2002


Products Affected

Product

Comments

c6sup11-js-mz.121-13.E

Catalyst 6000 Supervisor IOS (with MSFC1) Enterprise image

c6sup11-ps-mz.121-13.E

Catalyst 6000 Supervisor IOS (with MSFC1) Desktop image

c6sup12-js-mz.121-13.E

Catalyst 6000 Supervisor IOS (with MSFC2) Enterprise image

c6sup12-ps-mz.121-13.E

Catalyst 6000 Supervisor IOS (with MSFC2) Service Provider image

c6sup22-js-mz.121-13.E

Catalyst 6000 Supervisor IOS (with SUP2/MSFC2) Enterprise image

c6sup22-ps-mz.121-13.E

Catalyst 6000 Supervisor IOS (with SUP2/MSFC2) Service Provider image

Problem Description

Legacy GBICs with bad or unrecognized EEPROMs are put in link down state.

Background

The show interface command was cleaned up to support new information about GBICs and GBIC security, like bad EEPROM and security violations. This mistakenly resulted in the GBICs that have bad EEPROM information being kept down.

Problem Symptoms

GBICs that worked in releases prior to Cisco IOS Software Release 12.1(13)E fail after upgrading.

In native Cisco IOS Software Release 12.1(13), ports with GBICs that have a bad GBIC EEPROM checksum will not be allowed to come up. This is the expected behavior for 1000BASE-TX (copper) and CWDM GBICs but is incorrect for other GBICs. With previous releases, ports with the other GBICs that had checksum errors were allowed to come up.

The following error message is printed when this error occurs in the 12.1(13)E release:

 %PM_SCP-SP-3-GBIC_BAD: GBIC integrity check on port 1/2 failed: bad key

The show interface command will print the following output:

    Router#show interface status

    Port    Name               Status       Vlan       Duplex  Speed Type
    Gi2/1                      faulty       routed       full   1000 bad EEPROM

Workaround/Solution

The workaround is to downgrade to the previous release of Cisco IOS Software Release 12.1E or use a GBIC with a good checksum. Once the fixed release is available, the solution for this issue will be to upgrade to that release. Further details can be found in the DDTS referenced below.

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

CSCdy68962

GBIC security behavior incorrect in 12.1(13)E - needs to match CatOS

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.