Caveats
S e n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a c k - d o c @ c i s c o . c o m
CSCsl65951
•
Symptom: Using Fabric Manager Release 3.2(2), an error is displayed in the creation wizard. This
occurs when an enclosure spans multiple fabrics and not all fabrics are managed and when the Data
Migration Wizard is used to create a job with that enclosure as the existing storage (selecting all ports
listed in that enclosure).
Workaround: This issue is resolved.
CSCsm08837
•
Symptom: When an IVR-enabled MDS switch with an empty device alias database, attempts to join
a fabric which has approximately 7000 device aliases, the device alias merge fails. In this situation,
the following occurs:
Workaround: This issue is resolved.
CSCsm54071
•
Symptom: Data Virtual Targets (DVTs) are lost after a downgrade from Release 3.3(1x) to earlier
releases.
Workaround: This issue is resolved.
CSCsm94323
•
Symptom: When a PortChannel is created between 2 switches using the PortChannel wizard in Fabric
Manager, the map might not immediately update and may not show the ISLs as part of the PortChannel.
After a few discovery cycles, if the map is not updated, then the ISLs may be displayed along with the
PortChannel in the map.
Workaround: This issue is resolved.
•
CSCso05448
Symptom: FCIP links might fail to come up after a module reload following a hardware failure on
the module.
Workaround: This issue is resolved.
•
CSCso55622
Symptom: In Microsoft Windows 2000, 2003, 2003 R2, and 2008, when installing Fabric Manager,
Fabric Manager Server, and Device Manager, a service may not restart and/or may not properly execute
the PostgreSQL installer. This may lead to an incorrect conversion of the PostgreSQL database and/or
the service may not start. This occurs when running Microsoft Windows 2000, 2003, 2003 R2, or 2008
with Terminal Server running in Application mode.
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.3(3)
36
During the merge process between local and remote switches, the remote device alias database
–
is received on the local switch. The local switch validates those device aliases with SAP 110
(which is IVR).
Since all 7000 aliases could not be sent in a single MTS message, the aliases are fragmented
–
into 5 messages.
While IVR requires approximately 20 seconds to process each fragment, effectively it takes
–
around 100 seconds to process all 5 messages.
–
Because DDAS has a timeout of around 60 seconds, the merge is rejected.
The merge process is retried after few minutes and the process repeats. Then finally failed.
–
OL-14116-11
Print Page