Cisco MDS 9020 Fabric Switch Release Notes for Cisco MDS 9020 FabricWare Release 2.1(3) (OL-6990-02-C0, November 2006)

Send documentation comments to [e-mail].
6
Cisco MDS 9020 Fabric Switch Release Notes for Cisco MDS 9000 FabricWare Release 2.1(3)
OL-6990-02
Caveats
Symptom: The firmware upgrade check is incorrect, which disallows upgrading to future releases.
Workaround: None.
• CSCsd81739
Symptom: The firmware does not support Large-block NAND flash.
Workaround: None.
• CSCsd83253
Symptom: With the Emulex LP9002 HBAs, it may take up to 2 minutes for the HBA to log in when
performing a cable pull or reinsertion.
Workaround: None.
• CSCsd83259
Symptom: When using the AB378A 4-Gbps HBA, the link is not reset following the loop
initialization and before the FLOGI.
Workaround: None.
• CSCeh81887
Symptom: Some ports report the last change time inaccurately.
Workaround: None.
• CSCse23168
Symptom: Excessive CRC errors occur on a 4-Gbps link transferring a specific data pattern.
Workaround: None.
• CSCse35739
Symptom: Using a zone name or zone set name that is the same as the switch name that appears as
the CLI prompt causes an error when you edit the zone or zone set through Cisco Fabric Manager.
Workaround: Change either the zone set name, the zone name, or the CLI prompt
Open FabricWare Caveats
• CSCei52587
Symptom: If a Cisco MDS 9020 switch is used as the seed switch for Fabric Manager discovery in
a mixed fabric of Cisco MDS 9000 Series switches, some ISL links might be missing.
Workaround: Use a Cisco MDS 9100, Cisco MDS 9200, or Cisco MDS 9500 Series switch as the
seed switch or rediscover the network if it is not possible to have them as seed switches.
• CSCsc77866
Symptom: When a fabric including a Cisco MDS 9020 Fabric Switch and third-party devices is
discovered using Fabric Manager, where the Cisco MDS 9020 Fabric Switch is used as a seed for
the discovery, the map might not display some of the end devices (hosts and disks) connected to the
third-party switches. When the zone with these devices is highlighted on the Fabric Manager map,
the devices on the third-party switches are shown as “not in fabric.” The CLI displays for FCNS and
zone information are correct.
Workaround: None.