Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.2(8), (OL-27554-04, December 10, 2012)

37
Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.2(8)
OL-27554-04
Caveats
Symptom: While trying to download Device Manager using a switch IP address, the URL displays
an “http error 403” message for switches with a single supervisor, including the Cisco MDS 9222i
switch, the Cisco MDS 9148 switch, and the Cisco MDS 9134 switch.
This symptom might be seen on a Cisco MDS 9000 switch that is either running Cisco NX-OS
Release 5.2(6) or that was upgraded from a release where this issue was not present.
Workaround: This issue is resolved.
• CSCub65651
Symptom: If a Director class switch that is part of a fabric is upgraded to Cisco NX-OS Release
5.2(2d), the FCNS database in some of the switches in the fabric might get out of sync.
This symptom might be seen when IVR devices are present in the fabric and these devices are not
local to the switch being upgraded.
Workaround: This issue is resolved.
• CSCuc17564
Symptom: A host cannot discover a target through IVR.
This symptom might be seen in IVR non-NAT mode. There is a domain overlap conflict between
two VSANs that are participating in IVR. The fcdomain was reconfigured and a disruptive fcdomain
restart occurred.
Workaround: This issue is resolved.
• CSCuc35483
Symptom: Activation of a zone set in a VSAN in interop mode 1, fails with the following error
messages:
%ZONE-2-ZS_CHANGE_ACTIVATION_FAILED_RESN_DOM: %$VSAN <vsan>%$ Activation failed
: reason Invalid zonset format domain <dom>
%ZONE-2-ZS_CHANGE_SFC_FAILED: %$VSAN <vsan>%$ SFC failed : domain <dom> returns
INVALID_ZSET_FORMAT
The failure occurs only if the following conditions exist:
– Zone set activation occurs from a Cisco MDS 9000 switch.
– The switch is running Cisco NX-OS Release 5.2(6) or Release 5.2(6a).
– The VSAN in question is running in interop mode 1.
– McData switches are present in the VSAN that is in interop mode 1.
Workaround: This issue is resolved.
• CSCuc62769
Symptom: In some cases, the system does not take the corrective action of shutting down a faulty
fabric module. The system health loopback tests might fail, and the show hardware internal
statistics device fabric errors command might show serdes errors with the SER substring.
This issue affects fabric 3 modules, and occurs when there is bad hardware. The bad hardware causes
errors after a supervisor switchover and the fabric side receives serial link errors, but the channel
status is still in sync on both sides.
Workaround: This issue is resolved.
• CSCuc63272
Symptom: Detecting a faulty supervisor to the fabric takes over an hour. During this time, modules
are treated as failed and are reset, which causes a service interruption.