Cisco Cisco MDS 9000 NX-OS Software Release 5.2
44
Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.2(8d)
Caveats
Symptom: After using the zone convert smart-zoning zone name vsan command, the user does
not know how long the Smart Zoning conversion process is going to take.
not know how long the Smart Zoning conversion process is going to take.
Condition: During the Smart Zoning conversion process.
Workaround: This issue is resolved.
•
CSCul22781
Symptom: After a supervisor switchover, a subsequent ISL flap results in one or more VSAN
becoming isolated on the ISL.
becoming isolated on the ISL.
Condition: These issues only occur in situations after the supervisors fail over or a user-initiated
switch over ocuurs (but not an in service switchover situation, ie ISSU/ISSD). The preconditions are
created before the switchover by activating zone changes (such as adding or removing zones from a
zoneset) and is more likely to occur on systems with very large zone configurations.
switch over ocuurs (but not an in service switchover situation, ie ISSU/ISSD). The preconditions are
created before the switchover by activating zone changes (such as adding or removing zones from a
zoneset) and is more likely to occur on systems with very large zone configurations.
The symptoms described here can occur if zones are modified while a switch is running any NX-OS
release 5.2(2) to 5.2(8c) (inclusive), and 6.2(1) to 6.2(5) (inclusive).
release 5.2(2) to 5.2(8c) (inclusive), and 6.2(1) to 6.2(5) (inclusive).
Workaround: Contact Cisco TAC for assistance clearing the condition nondisruptively.
Further Problem Description: This issue can be prevented if the standby supervisor is rebooted
before the switchover occurs.
before the switchover occurs.
Open Caveats
•
CSCtr10877
Symptom: Some Fibre-Channel Redirect (FCR) peers might get out of synchronization with the
master switch FCR peer after an Inter-Switch Link (ISL) flap. This might cause the intelligent
application flows not to come online or to get deleted.
master switch FCR peer after an Inter-Switch Link (ISL) flap. This might cause the intelligent
application flows not to come online or to get deleted.
Workaround: This issue might occur when using any of the following FCR intelligent applications:
–
Storage Media Encryption (SME)
–
I/O Acceleration (IOA)
–
Data Mobility Manager (DMM)
Workaround: Check the intelligent applications to verify whether any flows are deleted on the
problematic switch. If they did, you must recreate flows again through the application CLI, or Cisco
Fabric Manager, or Cisco Data Center Network Manager (DCNM)-SAN interface.
problematic switch. If they did, you must recreate flows again through the application CLI, or Cisco
Fabric Manager, or Cisco Data Center Network Manager (DCNM)-SAN interface.
Enter the following supervisor CLI commands on the problematic FCR switch which causes it to
resynchronize its configuration with the rest of the fabric.
resynchronize its configuration with the rest of the fabric.
For a single switch, use the following command:
test fc-redirect config sync-with-fabric
If more than one peer is affected by this issue, use the following command:
test fc-redirect config sync-with-fabric all-peers
•
CSCtr50223
Symptom: On the MDS 9513 switch, when an MSM-18/4 module boots up, it sends a request to the
supervisor module to mount the modflash on the MSM-18/4 module. If there is a timeout or error in
response, the following syslog message displays:
supervisor module to mount the modflash on the MSM-18/4 module. If there is a timeout or error in
response, the following syslog message displays:
%LC_MNT_MGR-SLOT3-2-LC_MNT_MGR_ERROR: SUP mount failed. MTS receive timedout
%PROC_MGR-SLOT3-2-ERR_MSG: ERROR: PID 1144 (lc_mnt_mgr) exited abnormally, exit status
(0xa)