Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.3(4) (OL-14116-12, July 2009)

Table Of Contents
Send documentation comments to mdsfeedback-doc@cisco.com
34
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.3(4)
OL-14116-12
Caveats
Symptom: When NPV is enabled, IP access list commands are not accessible.
Workaround: This issue is resolved.
CSCsz40628
Symptom: An Inter-Switch Link (ISL) does not come up after one switch reloads.
Workaround: This issue is resolved.
CSCsz70307
Symptom: While Fabric Manager discovers the fabric, SNMP fails and the switch reloads. The
HBAs of the end devices in the fabric have Fabric-Device Management Interface (FDMI) enabled.
Workaround: This issue is resolved.
CSCsz74907
Symptom: In very rare circumstances, the zone server might fail due to a heartbeat failure.
Workaround: This issue is resolved.
CSCsz75692
Symptom: When a Cisco Fabric Switch for HP c-Class BladeSystem or Cisco Fabric Switch for
IBM BladeCenter reloads following the system startup-config init command, the switch does not
auto boot, but remains at the loader prompt. The command erroneously erases the startup
configuration from the boot flash.
Workaround: This issue is resolved.
CSCsz84022
Symptom: The TPC application cannot discover the MDS 9509 switch when it is connected to an
MDS 9020 switch.
Workaround: This issue is resolved.
CSCsz95999
Symptom: A kernel failure in the Mgmt0 driver caused the MDS 9222i switch to reboot
Workaround: This issue is resolved.
CSCta08796
Symptom: A memory leak caused the port manager to fail and put the ports in a hardware failure
state.
Workaround: This issue is resolved.
CSCta15575
Symptom: The SystemName property on the CIM Server is returning the wrong values for N port
and F port.
Workaround: This issue is resolved.
CSCta28642
Symptom: SNMP should gracefully handle timeouts caused by port initialization.
Workaround: This issue is resolved.
CSCta34629
Symptom: The system manager core server does not clean up the core files on the MDS 9513
switch.
Workaround: This issue is resolved.