Installation guide

Table Of Contents
41
Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.2(8c)
OL-27554-07
Caveats
11 0x021400 0x283f75 31 0x3734c7 0xcf3f89 0 0
ADD_PROGRESS
Condition: This issue occurs during a normal operation.
Workaround: This issue is resolved.
CSCue76534
Symptom: Zone conversion from the legacy zoning to smart zoning by using the zone convert
smart-zoning command might fail without a notice. The zone conversion failure leaves the devices
in zones with an FC-4 type of unknown.
This condition can be confirmed with the following command:
switch# show zone smart-zoning auto-conv status vsan 1-4093
Vsan: 1
zone name device-zone-1 vsan 1
pwwn 11:11:11:11:11:11:11:01 unknown
pwwn 22:22:22:22:22:22:22:01 unknown
Condition: This issue only occurs when the smart zoning conversion command is used on switches
with a single supervisor after an In-Service Software Upgrade (ISSU) from the smart zoning
unaware version to smart zoning aware version. The conversion might fail for all devices that you
attempt to convert.
Workaround: This issue is resolved.
CSCtz92415
Symptom: The zone server crashes with the following error:
%SYSMGR-2-SERVICE_CRASHED: Service "zone" (PID 2573) hasn't caught signal 6 (core will
be saved).
Condition: This occurs during a normal operation.
Workaround: This issue is resolved.
CSCui47352
Symptom: Although the password for TACACS server is entered in the encrypted format, the Cisco
NX-OS software still re-encrypts it.
Condition: This issue occurs when using the TACACS server and the key 7 parameter.
Workaround: This issue is resolved.
CSCts79593
Symptom: The operational status of a virtual storage area network (VSAN) is displayed as Down.
Condition: This issue occurs when one of these conditions is met:
After using the suspend and no suspend command for a VSAN, which is carried on an E port.
In the VSAN 1, without any trigger, the F ports associated to the VSAN 1 go Down.
Workaround: This issue is resolved.
CSCtt97930
Symptom: Registered state change notifications (RSCNs) are sent repeatedly to a device using
inter-VSAN routing (IVR).
Condition: This issue occurs when IVR is enabled on on the device.
Workaround: This issue is resolved.
CSCuj33175