Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.2(6) Release Date: August 09, 2012 Part Number: OL-27554-01 J0 This document describes the caveats and limitations for switches in the Cisco MDS 9000 Family. Use this document in conjunction with documents listed in the “Related Documentation” section on page 62. Release notes are sometimes updated with new information on restrictions and caveats.
Contents Table 1 Online History Change Revision Date Description K0 May 31, 2013 Added resolved caveat CSCtr01652. L0 June 13 Added open caveat CSCub47799. M0 Sept 15, 2014 Added open caveat CSCtz53329.
Components Supported Note Table 2 For the latest information about supported transceivers, see the Cisco MDS 9000 Family Pluggable Transceivers data sheet. Cisco MDS 9000 Family Supported Software and Hardware Components Component Part Number Description Applicable Product Software M95S2K9-5.2.6 MDS 9500 Supervisor/Fabric-2, NX-OS software MDS 9500 Series only M92S2K9-5.2.6 MDS 9200 Supervisor/Fabric-2, NX-OS software MDS 9222i Switch only M91S3K9-5.2.
Components Supported Table 2 Cisco MDS 9000 Family Supported Software and Hardware Components (continued) Component Part Number Description Applicable Product Licenses M9500SSE184K9 Storage Services Enabler License for one MSM-18/4 module MDS 9500 Series only M9222ISSE1K9 Storage Services Enabler License MDS 9222i Switch only M9200SSE184K9 Storage Services Enabler License for one MSM-18/4 module MDS 9200 Series only M95DMM184K9 Data Mobility Manager License for one MSM-18/4 module MDS 9500
Components Supported Table 2 Cisco MDS 9000 Family Supported Software and Hardware Components (continued) Component Part Number Description Chassis DS-C9513 Cisco MDS 9513 Multilayer Director (13-slot multilayer MDS 9513 Switch director with 2 slots for Supervisor-2 modules, with 11 slots available for switching modules — SFPs sold separately) DS-C9509 Cisco MDS 9509 Multilayer Director (9-slot multilayer MDS 9509 Switch director with 2 slots for Supervisor modules, with 7 slots available for switc
Components Supported Table 2 Cisco MDS 9000 Family Supported Software and Hardware Components (continued) Component Part Number Description Applicable Product Switching Modules Cisco MDS 9000 12-port 4-Gbps Fibre Channel Switching Module with SFP LC connectors MDS 9500 Series Cisco 24-port 4-Gbps Fibre Channel Switching Module with SFP LC connectors MDS 9500 Series Cisco MDS 9000 48-port 4-Gbps Fibre Channel Switching Module with SFP LC MDS 9500 Series Cisco MDS 9000 Family 4-Port 10-Gbps Fibre
Components Supported Table 2 Cisco MDS 9000 Family Supported Software and Hardware Components (continued) Component Part Number Description Applicable Product Optics SFP-10G-SR 10GBASE-SR SFP+ Module MDS 9500 Series, 8-port 10-Gbps FCoE Module (DS-X9708-K9) SFP-10G-LR 10GBASE-LR SFP+ Module MDS 9500 Series, 8-port 10-Gbps FCoE Module (DS-X9708-K9) SFP-H10GB-CU1M 10GBASE-CU SFP+ cable 1 meter MDS 9500 Series, 8-port 10-Gbps FCoE Module (DS-X9708-K9) SFP-H10GB-CU3M 10GBASE-CU SFP+ cable 3 met
Components Supported Table 2 Cisco MDS 9000 Family Supported Software and Hardware Components (continued) Component Part Number Description Applicable Product LC-type fiber-optic SFP DS-FC10G-SW SFP+ optics (LC type) for 10-Gbps Fibre Channel for shortwave mode 32-port 8-Gbps Advanced Fibre Channel Module (DS-X9232-256K9), 48-port 8-Gbps Advanced Fibre Channel Module (DS-X9248-256-K9) DS-FC10G-LW SFP+ optics (LC type) for 10-Gbps Fibre Channel for longwave mode 32-port 8-Gbps Advanced Fibre Chan
MDS 9000 Chassis and Module Support Table 2 Cisco MDS 9000 Family Supported Software and Hardware Components (continued) Component Part Number Description DWDM-X2-xx.xx Dense Wavelength - Division Multiplexi ng (DWDM) MDS 9500 Series DWDM X2 SC optics for 10-Gbps Fibre Channel connectivity to an existing Ethernet DWDM MDS 9200 Series infrastructure, with 15xx.xx nm wavelength, where xx.xx = 60.61, 59.79, 58.98, 58.17, 56.55, 55.75, 54.94, 54.13, 52.52, 51.72, 50.92, 50.12, 48.51, 47.72, 46.92, 46.
MDS 9000 Chassis and Module Support Table 3 Cisco MDS NX-OS 5.x Chassis Support Matrix Switch NX-OS 5.x Support MDS 9513 Yes MDS 9509 Yes MDS 9506 Yes MDS 9222i Yes MDS 9148 Yes Cisco MDS 8-Gb Fabric Switch for HP c-Class Blade System Yes MDS 9134 Yes1 MDS 9124 Yes1 Cisco MDS 4-Gbps Fabric Switch for HP c-Class BladeSystem Yes1 Cisco MDS 4-Gbps Fabric Switch for IBM BladeCenter Yes1 1. This switch supports Cisco MDS NX-OS Release 5.
MDS 9000 Chassis and Module Support Table 4 Module Support Matrix for Cisco MDS NX-OS 5.x (continued) Module Description MDS 9500 Series MDS 9222i NX-OS 5.2(x) NX-OS 5.0(x) NX-OS 5.2(x) NX-OS 5.
MDS 9000 Chassis and Module Support Table 5 Module Support Matrix for Cisco MDS NX-OS 4.x (continued) Module Description MDS 9500 Series MDS 9222i MDS 9216i DS-X9032 32-port 1-, 2-Gbps Fibre Channel Switching Module Yes No Yes DS-X9032-SSM 32-port Storage Services Module (SSM) Yes Yes Yes DS-X9308-SMIP 8-port 1-, 2-Gbps IP Switching Module No No No DS-X9304-SMIP 4-port 1-, 2-Gbps IP Switching Module No No No 1. In software releases earlier than Cisco NX-OS Release 4.
Software Download Process Table 6 Module Support Matrix for Cisco MDS SAN-OS 3.x (continued) MDS 9222i MDS 9216i MDS 9216A MDS 9216 32-port 1-, 2-Gbps Fibre Channel Switching Yes Module No Yes Yes Yes DS-X9032-SSM 32-port Storage Services Module (SSM) Yes Yes Yes Yes Yes DS-X9308-SMIP 8-port 1-, 2-Gbps IP Switching Module Yes No Yes Yes Yes DS-X9304-SMIP 4-port 1-, 2-Gbps IP Switching Module Yes Yes Yes Yes Yes Module Description DS-X9032 MDS 9500 Series 1.
Software Download Process Table 7 Software Release Compatibility Cisco NX-OS Software Minimum NX-OS or SAN-OS Release Tested NX-OS and SAN-OS Releases NX-OS Release 5.2(6) NX-OS Release 5.0(1a) or later NX-OS Release 5.0(1a) and later NX-OS Release 4.2(3) or later NX-OS Release 4.2(3) and later SAN-OS Release 3.3(5) or later SAN-OS Release 3.3(5) and later Downloading Software The Cisco MDS NX-OS software is designed for mission-critical high availability environments.
Software Download Process Selecting the Correct Software Image for an MDS 9100 Series Switch The system and kickstart image that you use for an MDS 9100 series switch depends on which switch you use, as shown in Table 8.
Upgrading Your Cisco MDS NX-OS Software Image NPE Software Images No payload encryption (NPE) images are available with some releases of Cisco MDS NX-OS Release 5.2(x) software. The NPE images are intended for countries who have import restrictions on products that encrypt payload data. To differentiate an NPE image from the standard software image, the letters npe are included in the image name as follows: • m9500-sf2ek9-kickstart-mz-npe.5.2.2.bin • m9500-sf2ek9-mz-npe.5.2.2.
Upgrading Your Cisco MDS NX-OS Software Image subsequently perform a nondisruptive software downgrade from NX-OS Release 5.2(1). For additional information, see the “Downgrading Guidelines Specific to NX-OS Release 5.2(6)” section on page 21. • Ensure that you have a Supervisor-2A module (DS-X9530-SF2A-K9) installed in a MDS 9500 Series switch if you plan to use the Cisco MDS 9000 8-port 10-Gbps Fibre Channel over Ethernet (FCoE) (DS-X9708-K9).
Upgrading Your Cisco MDS NX-OS Software Image The network can now run in IVR-NAT mode. General Upgrading Guidelines Follow these general guidelines before performing a software upgrade: • Review the nondisruptive upgrade path to release 5.2(6) in Table 11. • Install and configure dual supervisor modules before the upgrade. • Issue the show install all impact upgrade-image CLI command to determine if your upgrade will be nondisruptive.
Upgrading Your Cisco MDS NX-OS Software Image Table 11 Nondisruptive Upgrade Path to Cisco MDS NX-OS Release 5.2(6) Current Release Nondisruptive Upgrade Path and Ordered Upgrade Steps NX-OS: Release 5.2(1) and 5.2(2), 5.2(2a), and 5.2(2d) Upgrade directly to NX-OS Release 5.2(6). All 5.0(x) releases Upgrade directly to NX-OS Release 5.2(6). All 4.2(x) releases and 4.1(x) releases 1. Upgrade to NX-OS Release 5.0(x). 2. Upgrade to NX-OS Release 5.2(6). 1. Upgrade to NX-OS Release 4.2(9). 2.
Downgrading Your Cisco MDS SAN-OS Software Image Cisco MDS NX-OS Release 5.2(6) is not a FICON-certified release. Table 12 lists the SAN-OS and NX-OS releases that are certified for FICON. Refer to the specific release notes for FICON upgrade path information. Table 12 FICON Supported Releases FICON Supported Releases NX-OS Release 5.2(2) Release 4.2(7b) Release 4.2(1b) Release 4.1(1c) SAN-OS Release 3.3(1c) Release 3.2(2c) Release 3.0(3b) Release 3.0(3) Release 3.0(2) Release 2.
Downgrading Your Cisco MDS SAN-OS Software Image Downgrading Guidelines Specific to NX-OS Release 5.2(6) The following guidelines applies to a downgrade from Cisco MDS NX-OS Release 5.2(6): • Cisco NX-OS Release 5.2(6) supports IDLE as a fill word for the switchport fill-pattern command. Releases earlier than Release 5.2(6) supported only the ARBFF fill word. As a result, when you downgrade from Cisco NX-OS Release 5.
Downgrading Your Cisco MDS SAN-OS Software Image – no switchport mode st to negate the SPAN target port mode for the SPAN target port General Downgrading Guidelines Follow these general guidelines before you perform a a software downgrade: • Issue the system no acl-adjacency-sharing execute command to disable ACL adjacency usage on Generation 2 and Generation 1 modules.
Downgrading Your Cisco MDS SAN-OS Software Image NX-OS Release 5.2(x) and Release 5.0(x) Software Downgrade and Upgrade Matrix for Cisco MDS 9509 and 9506 Switches See the compatibility information in Table 14 to determine if a downgrade to, or upgrade from Release 5.0(x) software is disruptive or nondisruptive on a Cisco MDS 9509 or 9506 switch. Table 14 NX-OS Release 5.2(x) and Release 5.
Downgrading Your Cisco MDS SAN-OS Software Image Table 15 Nondisruptive Downgrade Path from NX-OS Release 5.2(6) To NX-OS or SAN-OS Release Nondisruptive Downgrade Path and Ordered Downgrade Steps NX-OS: Release 5.2(1), 5.2(2), Downgrade directly from NX-OS Release 5.2(6). 5.2(2a), and 5.2(2d) All 5.0(x) releases All 4.2(x) and 4.1(x) releases Downgrade directly from NX-OS Release 5.2(6)1, 2, 3 1. Downgrade to NX-OS Release 5.0(x). 2. Downgrade to NX-OS Release 4.2(x) or 4.1(x). 1.
New Features in Cisco MDS NX-OS Release 5.2 FICON Downgrade Paths Table 16 lists the downgrade paths for FICON releases. Find the image release number that you want to downgrade to in the To Release with FICON Enabled column of the table and follow the recommended downgrade path. Table 16 FICON Downgrade Path To Release with FICON Enabled Downgrade Path NX-OS Release 4.2(7b) You can nondisruptively downgrade directly from NX-OS Release 5.2(2) NX-OS Release 4.
New Features in Cisco MDS NX-OS Release 5.2 Smart Zoning Cisco smart zoning simplifies zoning to reduce the burden on administrators and enable automation of SAN provisioning without affecting SAN hardware resource consumption. When the smart zoning feature is enabled, Cisco MDS 9000 Family fabrics provision the hardware access control entries specified by the zone set more efficiently.
New Features in Cisco MDS NX-OS Release 5.2 New Features in Cisco MDS NX-OS Release 5.2(2a) Cisco MDS NX-OS Release 5.2(2a) is a maintenance release that includes bug fixes and the following feature enhancement: • Port Monitor Port monitoring has been enhanced with several ASIC counters that monitor and report internal packet drops. Additional information about this feature enhancement is available in the Cisco MDS 9000 Series Interfaces Configuration Guide. New Features in Cisco MDS NX-OS Release 5.
New Features in Cisco MDS NX-OS Release 5.2 Cisco MDS NX-OS Release 5.2(2) supports configuring IOA with NPV. New Features in Cisco MDS NX-OS Release 5.2(1) Cisco MDS NX-OS Release 5.2(1) supports the following software features: • Software support for the MDS 9000 8-port 10-Gbps Fibre Channel over Ethernet (FCoE) module The MDS 9000 8-port 10-Gbps Fibre Channel over Ethernet (FCoE) module is a multihop-capable FCoE module for the core data center.
Licensed Cisco NX-OS Software Packages – Performance forecasting charts – External SMI-S 1.4 agent – FCoE provisioning and management Detailed information about Cisco DCNM features is available in the Cisco DCNM Release Notes, Release 5.2, and in the feature configuration guides for Cisco DCNM for SAN. For additional information about Cisco MDS NX-OS Release 5.2(1), see the Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.2(1). New Hardware in Cisco MDS NX-OS Release 5.
Licensed Cisco NX-OS Software Packages SAN Extension over IP Package The Cisco MDS 9000 SAN Extension over IP package allows the customer to use FCIP to extend SANs over wide distances on IP networks using the Cisco MDS 9000 family IP storage services. Refer to the Cisco MDS 9000 SAN Extension over IP package fact sheet for more information.
Deprecated Features On-Demand Port Activation License On-demand ports allow customers to benefit from Cisco NX-OS Software features while initially purchasing only a small number of activated ports on 8-Gbps or 4-Gbps Cisco MDS 9100 Series Multilayer Fabric switches. As needed, customers can expand switch connectivity by licensing additional ports.
Limitations and Restrictions SNIA Common Information Model SNIA Common Information Model (CIM or cimserver) commands are no longer supported. CIM is supported in Cisco DCNM-SAN Release 5.2. The SMI-S agent that is installed on the Cisco DCNM-SAN server allows external application to access fabric and switch profiles as specified in SNIA CIM. For additional information, see the Cisco DCNM Release Notes, Release 5.2. IVR Non-NAT Mode IVR non-NAT mode is not supported in Cisco NX-OS Release 5.2(x).
Limitations and Restrictions • Configuring a Persistent FCID in an IVR Configuration with Brocade Switches, page 39 SME Quorum You cannot change the quorum or the SME master node during a master key rekey. If a change occurs during the smart card portion of the operation, the master key rekey operation will fail and must be repeated from the beginning. OUI Mismatch for SME Tape Targets If Cisco DCNM does not discover all expected tape targets, check the sme.log to identify an OUI mismatch.
Limitations and Restrictions prevented from performing configuration, clear, execute, and debug commands as before, however, they are allowed to perform show commands for all VSANs. The ability to execute the show command addresses the following: • In a network environment, users often need to view information in other VSANs even though they do not have permission to modify configurations in those VSANs.
Limitations and Restrictions Using a RSA Version 1 Key for SSH Following an Upgrade For security reasons, NX-OS Release 4.2(1b) does not support RSA version 1 keys. As a result, if you upgrade to NX-OS Release 4.2(1b) from an earlier version that did support RSA version 1 keys, and you had configured an RSA version 1 key for SSH, then you will not be able to log in through SSH following the upgrade. If you have an RSA version 1 key configured for SSH, before upgrading to NX-OS Release 4.
Limitations and Restrictions > > enable commit When you attempt to apply these commands in the ASCII configuration, the following commands fail: > > > no destination-profile testProfile transport-method email destination-profile testProfile transport-method http destination-profile testProfile http https://xyz.abc.com To work around this issue, issue these commands after the commit command.
Limitations and Restrictions VF_ID Value Value Description FF0h ... FFEh Vendor specific. FFFh Do not use as a Virtual Fabric Identifier. FEFh = 4079 Applying Zone Configurations to VSAN 1 In the setup script, you can configure system default values for the default-zone to be permit or deny, and you can configure default values for the zone distribution method and for the zone mode. These default settings are applied when a new VSAN is created.
Limitations and Restrictions Support for FCIP Compression Modes In Cisco NX-OS Release 4.2(1b) and later, FCIP compression mode 1 and compression mode 3 are not supported on the Cisco MSM-18/4 module and on the SSN-16 module. Saving Copies of the Running Kickstart and System Images After you upgrade to MDS NX-OS Release 4.
Caveats PPRC Not Supported with FCIP Write Acceleration IBM Peer to Peer Remote Copy (PPRC) is not supported with FCIP Write Acceleration. Configuring a Persistent FCID in an IVR Configuration with Brocade Switches The following information is relevant if you have a fabric that consists of Cisco MDS 9000 switches and Brocade switches, and the Cisco MDS switches are running either NX-OS Release 4.x or Release 5.x and Brocade is running FOS higher than 6.x.
Caveats Table 17 Open Caveats and Resolved Caveats Reference (continued) NX-OS Software Release (Open or Resolved) NX-OS Software Release (Open or Resolved) 5.2(2d) 5.
Caveats Table 17 Open Caveats and Resolved Caveats Reference (continued) NX-OS Software Release (Open or Resolved) NX-OS Software Release (Open or Resolved) 5.2(2d) 5.
Caveats Table 17 Open Caveats and Resolved Caveats Reference (continued) NX-OS Software Release (Open or Resolved) NX-OS Software Release (Open or Resolved) 5.2(2d) 5.
Caveats Workaround: This issue is resolved. • CSCty01206 Symptom: After upgrading Fabric Manager Server and the Cisco Key Management Centers (KMC) from Cisco NX-OS Release 4.2(3) to Release 5.0(4d) to Release 5.2(1), the old tape key replication relationships are lost. However, you are able to create new tape key replication relationships for the newly created tape-backup groups. This symptom occurs following an upgrade of the KMC to Cisco NX-OS Release 5.2(1). Workaround: This issue is resolved.
Caveats -----5 5 6 6 -------1 1 1 1 --------------ethport ethport ethport ethport -------3445 11344 30298 3491 ------------------------2012-05-02 12:02:36 2012-05-02 12:02:38 2012-05-02 12:06:47 2012-05-02 12:06:49 This symptom might occur when a PortChannel is created over Gigabit Ethernet ports.
Caveats Symptom: On an Cisco MDS 9513 switch, SCSI traffic sent from a LUN to a device configured for IVR or FC Redirect gets dropped. This symptom occurs when the LUN numbers end with 0x2x, 0x22, or 0x81. Workaround: This issue is resolved. • CSCua04249 Symptom: A FICON tape acceleration (FTA) control message that was received out of sequence caused the MSM-18/4 module to fail. This symptom occurred when FTA was enabled for read acceleration. Workaround: This issue is resolved.
Caveats • CSCua84273 Symptom: A replaced smart card configuration is not persistent following a switch reload. Workaround: This issue is resolved. • CSCub11370 Symptom: A Cisco MDS 9124 switch incorrectly indicates that the TCAM is full when it is not. The symptom occurs when a Cisco MDS 9124 switch is in NPV mode and an NPIV switch is connected to it with PortChannels. If the NPIV mode switch reloads, the TCAM member table counter is not decreased. Workaround: This issue is resolved.
Caveats ... ------Address ------... 0040 ----Bytes ----- -----Frames ------ 00000000000016ac 0000000000000029 Workaround: This issue is resolved. • CSCts71286 Symptom: An AAA authentication error occurs. switch(config)# aaa group server ldap ldap-group switch(config)# aaa authentication login default group ldap-group too big pss key or value size could not update aaa configuration switch(config)# This symptom might be seen on a switch that is running Cisco NX-OS Release 5.
Caveats This symptom occurs only on the following Generation 3 modules: – Cisco MDS 9000 24-Port 8-Gbps Fibre Channel Switching Module (DS-X9224-96K9) – Cisco MDS 9000 48-Port 8-Gbps Fibre Channel Switching Module (DS-X9248-96K9) – Cisco MDS 9000 4/44-Port Host-Optimized 8-Gbps Fibre Channel Switching Module (DS-X9248-48K9) Workaround: This issue is resolved.
Caveats Symptom: Device Manager does not show the power supply information correctly. Even if you make a change in redundant or combined mode, Device Manager shows the lowest value under capacity when you have two different power supplies. Workaround: This issue is resolved.
Caveats This issue is extremely rare. The conditions for this issue may be created after a nondisruptive upgrade to Cisco NX-OS Release 5.2(x). However, service disruption might not appear immediately on the affected PortChannel. The next time one or more members of the PortChannel flap, traffic loss could occur.
Caveats This symptom occurred on a Cisco MDS 9513 switch with Cisco NX-OS Release 4.2(7a) that was upgrading to Cisco NX-OS Release 5.0(4d). Workaround: This issue is resolved. • CSCtz23936 Symptom: Following an upgrade from Cisco NX-OS Release 3.3(x) to Release 4.2(x), IVR over FCIP caused an ENTERPRISE_PKG license to be checked out. Before the upgrade, IVR was using the SAN_EXTN_OVER_IP_IPS2 license.
Caveats %SYSMGR-STANDBY-5-CFGWRITE_STARTED: Configuration copy started (PID 2589). %RADIUS-3-RADIUS_ERROR_MESSAGE: could not register with cfs: 0x80b3003e %SYSMGR-2-SERVICE_CRASHED: Service "cfs" (PID 2883) hasn't caught signal 11 (core will be saved). Workaround: This issue is resolved. • CSCtz85952 Symptom: An F port interface goes down and will not come back up.
Caveats There are duplicate pPWWNs. switch# show zone internal ddas-table Device Alias Database State: 1 Device Alias Mode: enhanced -----------------------------------------------------------------------------Device Alias Name PWWN -----------------------------------------------------------------------------mystorage_8DA 50:00:11:22:33:44:55:66 mystorage_8D0 50:00:11:22:33:44:55:66 Workaround: This issue is resolved.
Caveats 2012 Jul 12 10:31:56 MDS03 %SANTAP-SLOT3-4-ST_NEAR_MAX_LUNS_PER_HOST: Warning: Approaching MAX_LUNS_PER_HOST(256) limit for Host 1:2:3:4:5:6:7:8, DVT 1:2:3:4:5:6:7:8. Existing num luns 230 2012 Jul 12 10:31:56 MDS03 %SANTAP-SLOT3-4-ST_NEAR_MAX_LUNS_PER_HOST: Warning: Approaching MAX_LUNS_PER_HOST(256) limit for Host 1:2:3:4:5:6:7:8, DVT 1:2:3:4:5:6:7:8.
Caveats Workaround: Enter the following supervisor commands on the problematic FCR peer, which will trigger this FCR peer to resync with the rest of the fabric, and force it to come out of the error state: switch# test fc-redirect config sync-with-fabric switch# test fc-redirect config sync-with-fabric all-peers If more than one peer is affected by this issue, then additional steps are needed.
Caveats Condition: This issue applies to the following NX-OS versions or platform combinations only: – The Cisco MDS switches running MDS NX-OS Release 5.2(6), 5.2(6a), 5.2(6b), 5.2(8), 5.2(8a), or 6.2(1). – The Cisco Nexus 7000 switches running NX-OS version 6.1(3) or 6.1(4). In addition, the following conditions must be true: – Device-alias is set to enhanced mode by using the device-alias mode enhanced command.
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.
Caveats IVR_FCIP ---------------------------------------------------------------------------- 2. Back up the FCIP configuration and other applications from the running configuration on the switch. 3. Disable the features in use by the license. This action is disruptive to any non-FCIP IVR traffic. switch# no feature fcip switch# no feature IVR 4. Copy the license files off the switch as follows: switch# copy licenses bootflash:lic-backup.tar switch# copy bootflash:lic-backup.tar tftp://xxx.xxx.xxx.
Caveats Symptom: In an SME or IOA deployment, if the number of H->T flows that are added exceeds 512, then subsequent disruptive platform events can leave an FCR unable to process interprocess (MTS) messages at a rate fast enough to support the scaled configuration. This situation can cause an MTS-buffers full condition in the FCR, which can result in unpredictable behavior. Some of the resulting errors may be unrecoverable, and may require a disruptive restart of the flows.
Caveats switch(config)# ivr aam pre-deregister-check switch(config)# show ivr aam pre-deregister-check AAM pre-deregister check status -------------------------FAILURE There are merged entries or AAM has not been enabled with the following switches: switch swwn 20:00:00:0d:ec:3e:f4:c0 Workaround : Disable IVR and AAM support on FCR and flap the ports: switch (config)# no fc-redirect ivr-support enable switch (config)# no ivr aam register AAM is currently disabled. No change will be made.
Caveats Workaround: Restore connectivity to the primary KMC. • CSCtz40700 Symptom: When a trunk link fails, the 1.3.6.1.4.1.9.9.289.1.3 trap has an incorrect link failure reason of “gracefully down.” This symptom might be seen only when a link failure occurs on a E, TE, or TF port. Workaround: Ignore the link down reason because the link down trap is valid. • CSCtz40745 Symptom: A “VSAN down” trap is sent for VSAN 4094 when a trunk port goes down because the VSAN is not configured on the trunk.
Related Documentation Related Documentation The documentation set for NX-OS for the Cisco MDS 9000 Family includes the following documents. To find a document online, access the following web site: http://www.cisco.com/en/US/products/ps5989/tsd_products_support_series_home.html The documentation set for Cisco Fabric Manager appears in the Cisco Fabric Manager Release Notes for Release 4.2(1), which is available from the following website: http://www.cisco.com/en/US/products/ps10495/prod_release_notes_list.
Related Documentation Software Installation and Upgrade • Cisco MDS 9000 NX-OS Software Upgrade and Downgrade Guide • Cisco MDS 9000 Family Storage Services Interface Image Install and Upgrade Guide • Cisco MDS 9000 Family Storage Services Module Software Installation and Upgrade Guide • Cisco MDS 9000 Family NX-OS Licensing Guide • Cisco MDS 9000 Family NX-OS Fundamentals Configuration Guide • Cisco MDS 9000 Family NX-OS System Management Configuration Guide • Cisco MDS 9000 Family NX-OS Inte
Obtaining Documentation and Submitting a Service Request Obtaining Documentation and Submitting a Service Request For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.
