Installation guide

ManualsBrandsCisco ManualsComputer equipmentDS-X9530-SF1-K9 - Supervisor-1 Module - Control Processor

Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.2(6)

OL-27554-01

Caveats

This issue might be seen on an Cisco MDS 9000 Series switch with the MDS 9000 18/4-port

Multiservice (MSM-18/4) module.

Workaround: None.

• 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:

There are two methods for working around this issue:

–

Leave the VSAN in interop mode 1 and do all zoning from the McData side. This method is

completely nondisruptive.

–

Convert VSAN to interop 4. This method is disruptive to the entire VSAN becuase it needs to

be suspended and the fcdomain domains need to be adjusted to be in the range of 1 to 31.

• CSCuc84790

Symptom: Following an upgrade to NX-OS Release 5.2(6) or Release 5.2(6a), FCIP interfaces are

down and the following message appears:

fcip1 is down (Tunnel port src interface unbound)

The licenses for all SAN_EXTN_OVER_IP packages in the grace period might be unnecessarily

checked out.The inter-VSAN routing (IVR) process is using those licenses.

switch# show ivr

License status

-----------------

IVR is running based on the following license(s)

SAN_EXTN_OVER_IP

SAN_EXTN_OVER_IP_IPS2

SAN_EXTN_OVER_IP_IPS4

SAN_EXTN_OVER_IP_9216i

SAN_EXTN_OVER_IP_18_4

SAN_EXTN_OVER_IP_SSN16

Conditions: This symptom might be seen when IVR is running over FCIP.

Workaround: To work aorund this issue, follow these steps:

1. Enter the show license usage license package name command to identify the applications that

are using the license. For example:

switch# show license usage SAN_EXTN_OVER_IP_18_4

Application

----------------------------------------------------------------------------