HP Cisco Nexus 5000 Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS R - Page 34

Caveats Send documentation comments to [email protected] • CSCse31881 Symptom: If there are IP over Fibre Channel (IPFC) interfaces configured on an SSM, you might experience issues if you downgrade from SAN-OS Release 3.x to Release 2.x. Workaround: This issue is resolved. • CSCsg19148 Symptom: Time zone changes that are executed on an MDS switch do not take effect on the 12-port, 24-port, and 48 port 1-Gbps/2-Gbps/4-Gbps Fibre Channel modules, and on the 4-port 10-Gbps module. This issue occurs in SAN-OS Releases 3.0(1), 3.0(2), 3.0(2a), and 3.0(3). Time zone changes that are executed on an MDS switch do not take effect on the 16-port or 32-port 1-Gbps/2-Gbps module, on the 4-port or 8-port Gigabit Ethernet IP services module, the MPS-14/2 module, and on the SSM. This issue occurs in SAN-OS Release 3.0(3). This issue has no effect on functionality. However, debug messages and syslogs from the MDS switching modules have incorrect timestamps if the time zone is configured on an MDS switch. Workaround: This issue is resolved. • CSCsg19303 Symptom: Graceful shutdowns of ISLs are not supported for IVR traffic. Workaround: This issue is resolved. • CSCsk35951 Symptom: In a configuration with a PortChannel with FCIP members and write acceleration in use, if IVR NAT is enabled on one end of the PortChannel and not enabled on the other end, then traffic over the FCIP tunnel might fail. Workaround: This issue is resolved. • CSCsk63929 Symptom: If DMM is provisioned on the SSM and you downgrade to a Cisco MDS SAN-OS release that does not support DMM, the configuration persists and the GUI and CLI show DMM as a provisioned application. Workaround: This issue is resolved. • CSCsk87502 Symptom: If an NASB configuration in a VSAN is destroyed while a target discovery is pending, the NASB process fails. Issue the show nasb vsan x command on the SSM to view the target discovery in the Pending state. Workaround: This issue is resolved. • CSCsk93834 Symptom: In rare situations during a storage-based online data migration job, the user might not be able to destroy the job if the following sequence of events occurs: 1. A storage-based data migration job is executing. 2. A port flap occurs on the server and the server HBA port goes down. 3. The storage-based data migration job continues executing until it completes. 4. The user issues the dmm module module-id job job-id destroy command to delete the storage-based data migration job, but the delete fails. Workaround: This issue is resolved. Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.3(3) 34 OL-14116-11