SOFTWARE ADVISORY NOTICE
April 9, 2013

Dear Cisco Customer,

Cisco engineering has identified the following software issues with the release that you have selected that may affect your use of this software. Please review the Software Advisory notice here to determine if the issues apply to your environment. You may proceed to download this software if you have no concerns with the issue described.

For more comprehensive information about what is included in this software, refer to the Cisco software Release Notes, available from the Product Selector tool. From this page, select the product you are interested in. Release Notes are under "General Information" on the product page.

Affected Software and Replacement Solution for CSCuc84790 and CSCue92054
Software Type	Software Affected	Software Solution
Software Type	Version	Version
Cisco NX-OS Software	NX-OS Release 5.2(6) NX-OS Release 5.2(6a) NX-OS Release 5.2(6b) NX-OS Release 5.2(8) Affected Images: m9500-sf2ek9-mz.5.2.6.bin m9500-sf2ek9-mz.5.2.6a.bin m9500-sf2ek9-mz.5.2.6b.bin m9500-sf2ek9-mz.5.2.8.bin m9500-sf2ek9-mz-npe.5.2.6.bin m9500-sf2ek9-mz-npe.5.2.6b.bin m9500-sf2ek9-mz-npe.5.2.8.bin	None (see Workaround) Replacement Images: None

Affected Software and Replacement Solution for CSCuf31077
Software Type	Software Affected	Software Solution
Software Type	Version	Version
Cisco NX-OS Software	NX-OS Release 5.2(6) NX-OS Release 5.2(6a) NX-OS Release 5.2(6b) NX-OS Release 5.2(8) Affected Images: m9500-sf2ek9-mz.5.2.6.bin m9500-sf2ek9-mz.5.2.6a.bin m9500-sf2ek9-mz.5.2.6b.bin m9500-sf2ek9-mz.5.2.8.bin m9500-sf2ek9-mz-npe.5.2.6.bin m9500-sf2ek9-mz-npe.5.2.6b.bin m9500-sf2ek9-mz-npe.5.2.8.bin m9200-s2ek9-mz.5.2.6.bin m9200-s2ek9-mz.5.2.6a.bin m9200-s2ek9-mz.5.2.6b.bin m9200-s2ek9-mz.5.2.8.bin m9200-s2ek9-mz-npe.5.2.6.bin m9200-s2ek9-mz-npe.5.2.6b.bin m9200-s2ek9-mz-npe.5.2.8.bin	None (see Workaround) Replacement Images: None.

Reason for Advisory:

This software advisory addresses three software issues.

CSCuc84790 and CSCue92054

Headline: IVR checks out SAN_EXT_PKG License Unnecessarily

Affected Platforms:

CSCuc84790 can occur on Cisco MDS 9500 Series Directors with a Supervisor 2 module and a MSM-18/4 module (DS-X9304-18K9) installed or a SSN-16 module (DS-X9316-SSNK9) installed.

Symptom: Following an upgrade to Cisco NX-OS Release 5.2(6), Release 5.2(6a), Release 5.2(6b), or Release 5.2(8), if IVR is configured, multiple IPS licenses may be mistakenly checked out, including the SAN_EXTN_OVER_IP_18_4 and SAN_EXTN_OVER_IP_SSN16 licenses. If FCIP is also configured on the same switch, this configuration can cause FCIP interfaces to be down and display the following message:

fcip1 is down (Tunnel port src interface unbound)

The licenses for all SAN_EXTN_OVER_IP packages in grace period may be

unnecessarily checked out. The process using those licenses is IVR:

'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: The conditions for this issue may be created after a nondisruptive upgrade to Cisco NX-OS Release 5.2(6x) or Release 5.2(8).

If IVR is configured but FCIP is not configured, the extra licenses that are mistakenly checked out do not cause any actual problems except for the loss of the grace period for the licenses. Once the grace periods expire, IVR will check out the correct ENTERPRISE_PKG license automatically and there will be no disruption. If you then attempt to configure FCIP, it will not work because it cannot check out a license.

If both IVR and FCIP are configured, the extra licenses mistakenly checked out do not cause any immediate disruption. IVR and FCIP are both fully functional following the nondisruptive upgrade to Release 5.2(6x) or Release 5.2(8). Again, multiple SAN_EXTN_OVER_IPxxx licenses are mistakenly checked out and grace periods are lost. However, because FCIP is being used, either the SAN_EXTN_OVER_IP_18_4 or SAN_EXTN_OVER_IP_SSN16 license is probably being used. Losing grace periods on the other, older forms of SAN extension licenses does not cause any real loss.

However, if the switch reloads or power cycles following the upgrade, IVR will check out the SAN_EXTN_OVER_IP_18_4 first. Later when FCIP attempts to check out the same license, it will not be able to and FCIP will cease to function.

The FCIP interface will show:

Tunnel port src interface unbound

Workaround: Choose the correct workaround that applies to your configuration.

Upgrade to Release 5.2(6x) or Release 5.2(8) has not occurred: execute the following steps on each affected switch to work around the issue.

1. Open a Service Request with the Cisco TAC and mention this Software Advisory. The TAC will issue a SAN_EXTN_OVER_IP license for each IVR switch. There is no cost for these licenses.

2. Install the SAN_EXTN_OVER_IP license on each switch, as in the following example:

switch# copy tftp://172.18.108.26/MDS20130306134428321.lic bootflash:

Trying to connect to tftp server......

TFTP get operation was successful

switch# install license bootflash:MDS20130306134428321.lic

Installing license ......done

switch# show license usage

Feature Ins Lic Status Expiry Date Comments

Count

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

FM_SERVER_PKG No - Unused -

MAINFRAME_PKG No - Unused -

ENTERPRISE_PKG No - Unused -

DMM_FOR_SSM_PKG Yes 1 Unused never 1 license(s) missing

SAN_EXTN_OVER_IP Yes 1 Unused never -

PORT_ACTIVATION_PKG No 0 Unused -

...snip

3. After the licenses are installed, an upgrade to Release 5.2(6x) or Release 5.2(8) will not cause any licenses to be mistakenly checked out or any FCIP disruption. The problem will not occur.

Upgrade to Release 5.2(6x) or Release 5.2(8) has occurred, and IVR is configured, but FCIP is not configured: the extra licenses that are checked out do not cause any problems except for the loss of the grace period for each license.

Once the grace period expires, IVR will check out the correct ENTERPRISE_PKG license automatically and there will be no disruption.

Upgrade to Release 5.2(6x) or Release 5.2(8) has occurred, and both IVR and FCIP are configured: if FCIP is configured, or the loss of licenses' grace period is a problem, complete the following steps on each affected switch to work around the issue.

1. Open a Service Request with the Cisco TAC and mention this Software Advisory. The TAC will issue a SAN_EXTN_OVER_IP license for each IVR switch. There is no cost for these licenses.

2. Issue the show license command to determine which license file contains the SAN_EXTN_OVER_IP_18_4 license. If there are multiple licenses in the same file, repeat steps 3, 4, and 5 for all those licenses and the features those licenses have enabled.

3. Enter the show license usage license-name command to identify the applications that use each license contained in the license file, as in the following example:

switch# show license usage SAN_EXTN_OVER_IP_18_4

Application

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

IVR_FCIP

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

4. Back up the configuration of FCIP and other applications from the running configuration on the switch.

5. Disable the features in use by the license. This action is disruptive to any non-FCIP interVSAN routing (IVR) traffic.

switch# no feature fcip

switch# no feature ivr

6. Copy license files from the switch.

switch# copy licenses bootflash:lic-backup.tar

switch# copy bootflash:lic-backup.tar tftp://xxx.xxx.xxx.xxx

7. Enter the clear license command to clear the license using the filename identified in step 2.

8. Reinstall the license files.

9. Install the new SAN_EXTN_OVER_IP license as described previously.

10. Configure FCIP by entering the feature fcip command and reconfigure FCIP.

11. Configure IVR by entering the feature ivr command and reconfigure IVR.

12. Configure the other features that were disabled in steps 3, 4, and 5.

Further Problem Description: Once you execute the appropriate workaround, no further actions are required.

CSCuf31077

Headline: Gen 3 port drops all outbound packets with OFFLINE and TIMEOUT

Affected Platforms: CSCuf31077 can occur on Cisco MDS 9500 Series Directors and Cisco MDS 9222i switches when any of the following modules are installed:

· 24-port 8-Gbps Fibre Channel switching module (DS-X9224-96K9)

· 48-port 8-Gbps Fibre Channel switching module (DS-X9248-96K9)

· 4/44-port Host Optimized 8-Gbps Fibre Channel switching module (DS-X9248-48K9)

Symptom: Ports on the 24-port, 48-port, or 4/44-port 8-Gbps Fibre Channel switching modules go into a suspended state and packets cannot egress or ingress on the port.

Conditions: This issue occurs after a nondisruptive upgrade to Cisco NX-OS Release 5.2(6x) or Release 5.2(8), and a link flap occurs on the ports.

Workaround: To work around this issue, do one of the following:

1. To temporarily recover a port in this state, enter the shut command followed by the no shut command on the port. A port that is recovered in this way can fail again.

2. To permanently work around this issue, reload the affected 24-port, 48-port, or 4/44-port 8-Gbps Fibre Channel switching module. If the switch contains primarily these modules, then reload the entire switch. Following the reload, the issue will not reoccur.

3. Downgrade or upgrade the Cisco NX-OS software to a release that is not affected by this bug. If a port is in this suspended state at the time of the upgrade or downgrade, the upgrade or downgrade does not automatically recover the port. Enter the shut command followed by the no shut command on the port after the upgrade or downgrade is complete to recover the port.

Further Problem Description: The main indications of a port exhibiting this issue are the following:

· The interface is up, there is an F port, there are zero frames per second in and out, there are output discards, and all B2B credits are remaining.

· Logging onboard shows small numbers of OFFLINE and TIMEOUT drops that are incrementing.

Disclaimer:

To increase availability, Cisco recommends that you upgrade affected images with the suggested replacement software images as soon as they become available.

The terms and conditions that governed your rights and obligations and those of Cisco, with respect to the original software will apply to the replacement software.