Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m . Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 4.1(3a) Release Date: March 11, 2009 Part Number: OL-17675-05 E0 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 52.
Introduction Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m . • Introduction, page 2 • Components Supported, page 3 • MDS 9000 Chassis and Module Support in Cisco MDS NX-OS 4.
Components Supported Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m . Components Supported Table 2 lists the NX-OS software part numbers and hardware components supported by the Cisco MDS 9000 Family. Note Table 2 To use the Cisco Storage Services Enabler package, Cisco MDS SAN-OS Release 1.3(5) or later must be installed on the MDS switch.
Components Supported Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m .
Components Supported Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m .
Components Supported Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m .
Components Supported Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m .
Components Supported Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m . Table 2 Cisco MDS 9000 Family Supported Software and Hardware Components (continued) Component Part Number Description Applicable Product Dense WavelengthDivision Multiplexing (DWDM) DWDM-X2-xx.xx MDS 9500 Series DWDM X2 SC optics for 10-Gbps Fibre Channel connectivity to an existing Ethernet DWDM infrastructure, MDS 9200 Series with 15xx.xx nm wavelength, where xx.xx = 60.61, 59.79, 58.
MDS 9000 Chassis and Module Support in Cisco MDS NX-OS 4.x Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m . MDS 9000 Chassis and Module Support in Cisco MDS NX-OS 4.x Table 3 lists the MDS hardware chassis supported by Cisco MDS NX-OS 4.x. Table 3 Cisco MDS NX-OS 4.x Chassis Support Matrix Switch NX-OS 4.
MDS 9000 Chassis and Module Support in Cisco MDS NX-OS 4.x Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m . Table 4 Module Support Matrix for Cisco MDS NX-OS 4.
Migrating from Supervisor-1 Modules to Supervisor-2 Modules Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m . Table 5 Module Support Matrix for Cisco MDS SAN-OS 3.
Software Download Process Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m . Note We strongly recommend that you use the latest available software release supported by your vendor for all Cisco MDS 9000 Family products. Downloading Software The Cisco MDS NX-OS software is designed for mission-critical high availability environments.
Software Download Process Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m . 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 6.
Upgrading Your Cisco MDS NX-OS Software Image Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m .
Upgrading Your Cisco MDS NX-OS Software Image Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m . Note When upgrading Fabric Manager, refer to the supported upgrade path shown in Table 9. For example, when upgrading from SAN-OS Release 3.1(x) to NX-OS Release 4.1(x), you will need to upgrade from Release 3.1(x) to Release 3.2(x) and then upgrade to NX-OS Release 4.1(x) Table 9 Note Supported Fabric Manager Upgrade Paths Current Upgrade Path 3.0.x 3.1.x 3.1.
Upgrading Your Cisco MDS NX-OS Software Image Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m . • Windows 2003 SP2, XP SP2, Windows Vista • Red Hat Enterprise Linux AS Release 4 (Nahant Update 6) • Solaris (SPARC) 8, 9, and 10 • VMWare ESX 3.5: • Virtual Operating System: Windows 2003 SP2 • Java Sun JRE and JDK 1.5(x) and JRE 1.6 are supported • Java Web Start 1.2, 1.0.1, 1.5, 1.6 • Firefox 1.5 and 2.0 • Internet Explorer 6.x, and 7.
Upgrading Your Cisco MDS NX-OS Software Image Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m . Step 4 If you are upgrading a previous installation of Fabric Manager, make sure the previous installation is installed and running. Do not uninstall the previous version. If the previous version is uninstalled, the database will not be migrated and your server settings will not be preserved. Step 5 Select the database.
Upgrading Your Cisco MDS NX-OS Software Image Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m . Note Do not close the command line window. This must remain open for the entire duration of the install. The following is an example of the output of this command: C:\Documents and Settings\user.domain>USER /INSTALL User session is ready to install applications. Step 3 Follow all steps needed to install Fabric Manager, Fabric Manager Server, and Device Manager.
Upgrading Your Cisco MDS NX-OS Software Image Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m . Step 1 Enter the IP address of the switch in the Address field of your browser. Step 2 Click the Cisco Device Manager link in the Device Manager installation window. Step 3 Click Next to begin the installation. Step 4 Follow the onscreen instructions to complete the installation of Device Manager.
Upgrading Your Cisco MDS NX-OS Software Image Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m . traversing an FCIP ISL are impacted, and a fabric reconfiguration occurs. iSCSI initiators connected to the Gigabit Ethernet ports lose connectivity to iSCSI targets while the upgrade is in progress. – Inter-VSAN Routing (IVR): With IVR enabled, you must follow additional steps if you are upgrading from Cisco SAN-OS Release 2.1.(1a), 2.1(1b), or 2.1.(2a).
Upgrading Your Cisco MDS NX-OS Software Image Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m . Table 10 Nondisruptive Upgrade Path to Cisco MDS NX-OS Release 4.1(3a) Current Nondisruptive Upgrade Path NX-OS 4.1(1c) You can nondisruptively upgrade directly to NX-OS Release 4.1(3a) NX-OS 4.1(1b) You can nondisruptively upgrade directly to NX-OS Release 4.1(3a) SAN-OS 3.3(2) You can nondisruptively upgrade directly to NX-OS Release 4.1(3a) SAN-OS 3.
Upgrading Your Cisco MDS NX-OS Software Image Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m . Table 10 Current Nondisruptive Upgrade Path to Cisco MDS NX-OS Release 4.1(3a) (continued) Nondisruptive Upgrade Path SAN-OS 2.1(1b) Upgrade to SAN-OS Release 2.1(2b), then upgrade to Release 3.3(x), and then upgrade to NX-OS Release 4.1(3a) or Upgrade to SAN-OS Release 2.1(2d), then upgrade to Release 3.3(x), and then upgrade to NX-OS Release 4.
Upgrading Your Cisco MDS NX-OS Software Image Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m . Use Table 11 to determine your FICON nondisruptive upgrade path to Cisco MDS NX-OS Release 4.1(3a). Find the image release number you are currently using in the Current Release with FICON Enabled column of the table and use the path recommended. Table 11 FICON Nondisruptive Upgrade Path to NX-OS Release 4.1(3a) Current Release with FICON Enabled Upgrade Path NX-OX 4.
Upgrading Your Cisco MDS NX-OS Software Image Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m . This issue was resolved in Cisco SAN-OS Release 2.1(2b); you must upgrade to Release 2.1(2b) before upgrading to Release 3.3(1c). An upgrade from Cisco SAN-OS Releases 2.1(1a), 2.1(1b), or 2.1(2a) to Release 2.
Upgrading Your Cisco MDS NX-OS Software Image Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m . Reconfiguring SSM Ports Before Upgrading to NX-OS Release 4.1(3a) Starting with Cisco MDS SAN-OS Release 3.0(1), the SSM front panel ports can no longer be configured in auto mode, which is the default for releases prior to Release 3.0(1).
Upgrading Your Cisco MDS NX-OS Software Image Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m . Step 4 Save the running configuration to the startup configuration before the upgrade procedure to ensure that the changes are preserved during and after the upgrade.
Upgrading Your Cisco MDS NX-OS Software Image Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m . To work around an image upgrade failure caused by a lack of space on the bootflash, follow these steps: Step 1 Prior to installing the new image, copy the old (existing) system image file to an external server. You may need to reinstall this file later.
Downgrading Your Cisco MDS SAN-OS Software Image Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m .
Downgrading Your Cisco MDS SAN-OS Software Image Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m . – Gigabit Ethernet Ports: Traffic on Gigabit Ethernet ports is disrupted during a downgrade. This includes IPS modules and the Gigabit Ethernet ports on the MPS-14/2 module, the MSM-18/4 module, and the MDS 9222i switch. Those nodes that are members of VSANs traversing an FCIP ISL are impacted, and a fabric reconfiguration occurs.
Downgrading Your Cisco MDS SAN-OS Software Image Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m . Table 12 Nondisruptive Downgrade Path from NX-OS Release 4.1(3a) (continued) To SAN-OS Release Nondisruptive Downgrade Path SAN-OS 3.1(4) Downgrade to SAN-OS Release 3.3(x) first and then downgrade to Release 3.1(4). SAN-OS 3.1(3a) Downgrade to SAN-OS Release 3.3(x) first and then downgrade to Release 3.1(3a). SAN-OS 3.1(2b) Downgrade to SAN-OS Release 3.
Downgrading Your Cisco MDS SAN-OS Software Image Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m . Table 12 Nondisruptive Downgrade Path from NX-OS Release 4.1(3a) (continued) To SAN-OS Release Nondisruptive Downgrade Path SAN-OS 2.0(1b) Downgrade to SAN-OS Release 3.3(x) first, then to Release 2.1(2x), and then downgrade to Release 2.0(1b). SAN-OS 1.x Downgrade to SAN-OS Release 3.3(x) first, then downgrade to SAN-OS to Release 2.1(2b), then to Release 1.
New Features in Cisco MDS NX-OS Release 4.1(3a) Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m . Downgrading the SSI Image on Your SSM Use the following guidelines when downgrading your SSI image on your SSM: • On a system with at least one SSM installed, the install all command might fail on an SSM when you downgrade from Cisco NX-OS Release 4.1(x) to any SAN-OS 2.x release earlier than SAN-OS Release 2.1(2e). Power down the SSM and perform the downgrade.
New Features in Cisco MDS NX-OS Release 4.1(3a) Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m .
New Features in Cisco MDS NX-OS Release 4.1(3a) Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m . Port Guard Starting from NX-OS 4.1(3a), you can hold a port down after a failure or a series of flaps that are rapid enough to exceed a configured threshold. This capability can help keep the malfunctioning port down to avoid a flood of error reports. Cisco Data Mobility Manager Enhancements Cisco MDS NX-OS Release 4.
New Features in Cisco MDS NX-OS Release 4.1(3a) Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m . High Availability KMC Enhancements in Cisco NX-OS Release 4.1(3a) enable the KMC to be used in high availability environments where unattended operation is a requirement. The KMC can be configured to use an Oracle Enterprise database with Data Guard for redundancy. Both the primary KMC and secondary KMC are configured to point to the redundant database.
Licensed Cisco NX-OS Software Packages Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m . • The Fabric Manager components shared with Cisco DCNM were relocated to a common directory. • The Oracle JDBC component is no longer distributed with Fabric Manager. Note If you require the Oracle JDBC component, you can download it from the Oracle Technology Network. You can download the recommended version (10.2.0.1.0) of the ojdbc14.
Licensed Cisco NX-OS Software Packages Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m . Mainframe Package The Cisco MDS 9000 Mainframe package uses the FICON protocol and allows control unit port management for in-band management from IBM S/390 and z/900 processors. FICON VSAN support is provided to help ensure true hardware-based separation of FICON and open systems. Switch cascading, fabric binding, and intermixing also are included in this package.
Limitations and Restrictions Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m . verification, dual Fibre Channel fabric support, and management using Cisco Fabric Manager provide a complete solution that greatly simplifies and eliminates most downtime associated with data migration. Refer to the Cisco MDS 9000 Data Mobility Manager package fact sheet for more information.
Limitations and Restrictions Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m . parameter outside this specified set. Beginning with NX-OS Release 4.1(1b), these users are still prevented from performing configuration, clear, execute, and debug commands as before, however, they are allowed to perform show commands for all VSANs. This addresses the following: 1.
Limitations and Restrictions Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m . Upgrading to Recover Loss of Performance Manager Data Caution You must upgrade to Fabric Manager Release 3.1(x) and then upgrade to a later release of Fabric Manager to avoid losing Performance Manager data. If data has been lost, follow the steps below to recover the data. Step 1 Disable Performance Manager interpolation using Fabric Manager Web Client.
Limitations and Restrictions Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m . Cisco Storage Media Encryption The following limitations are described for Cisco SME: • Cisco SME Configuration Limits, page 41 • Deleting Cisco SME Interfaces, page 41 • Emulex Driver Version, page 41 Cisco SME Configuration Limits Table 14 lists the Cisco SME configuration limits for this release.
Limitations and Restrictions Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m . VRRP Availability The Virtual Router Redundancy Protocol (VRRP) is not available on the Gigabit Ethernet interfaces on the MSM-18/4 module or module 1 of the MDS 9222i switch, even though it is visible on these modules. The feature is not implemented in the current release. Using a RSA Version 1 Key for SSH Following an Upgrade For security reasons, NX-OS Release 4.
Limitations and Restrictions Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m . > > > > > > > > no destination-profile testProfile transport-method email destination-profile testProfile transport-method http destination-profile testProfile http https://xyz.abc.com destination-profile testProfile alert-group all transport email smtp-server 64.104.140.134 port 25 use-vrf management transport email from abc@cisco.com
Limitations and Restrictions Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m . • If trunk mode is on for any of the interfaces or NP PortChannel is up, the reserved VSANs are 3040 to 4078, and they are not available for user configuration. • The Exchange Virtual Fabric Protocol (EVFP) isolated VSAN is 4079, and it is not available for user configuration. • VSAN 4079 will be impacted by an upgrade to NX-OS Release 4.
Caveats Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m . Caveats This section lists the open and resolved caveats for this release. Use Table 15 to determine the status of a particular caveat. In the table, “O” indicates an open caveat and “R” indicates a resolved caveat. Table 15 Open Caveats and Resolved Caveats Reference NX-OS Software Release (Open or Resolved) NX-OS Software Release (Open or Resolved) 4.1(1c) 4.
Caveats Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m . Table 15 Open Caveats and Resolved Caveats Reference (continued) NX-OS Software Release (Open or Resolved) NX-OS Software Release (Open or Resolved) 4.1(1c) 4.
Caveats Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m . • CSCsu84919 Symptom: When hosts are continuously logging into virtual targets (VTs), the iSAPI process might leak memory which might cause the SSM to fail. Workaround: This issue is resolved. • CSCsu98190 Symptom: During an upgrade from Cisco MDS SAN-OS Release 3.3(1c) to Cisco NX-OS 4.1(1b) and later, applications might experience a very small amount of packet drops in the fabric.
Caveats Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m . %KERN-3-SYSTEM_MSG: eth1: error in ethGetNextRxBuf %KERN-3-SYSTEM_MSG: eth1: stop internals failed %KERN-3-SYSTEM_MSG: eth1: error in rx %KERN-3-SYSTEM_MSG: eth1: error in rx %KERN-3-SYSTEM_MSG: eth1: error in rx %KERN-3-SYSTEM_MSG: eth1: error in rx %KERN-3-SYSTEM_MSG: eth1: error in rx In rare cases, this issue may result in a kernel panic which causes a supervisor switchover.
Caveats Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m . Workaround: This issue is resolved. • CSCsu84511 Symptom: When a Cisco MDS switch is configured to use an AAA server using TACACS+ and with enabling the directed request option, a login using @ provides the network-operator privilege instead of the actual privilege mentioned in the ACS server. This happens once AAA accounting is set to remote.
Caveats Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m . • CSCsw48060 Symptom: FCIP interoperability fails between two MDS switches, one running MDS NX-OS Release 4.1(1c) and the other running MDS NX-OS Release 4.
Caveats Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m . • CSCsy52780 Symptom: Occasionally, when you enter the feature npv command to enable NPV, or enter the no feature npv command to disable NPV, the switch does not reload as expected. Instead, it returns to the Configuration mode prompt. Workaround: If the switch returns to the Configuration mode prompt, enter the reload command.
Related Documentation Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m . Related Documentation The documentation set for the Cisco MDS 9000 Family includes the following documents. To find a document online, use the Cisco MDS SAN-OS Documentation Locator at: http://www.cisco.com/en/US/docs/storage/san_switches/mds9000/roadmaps/doclocater.ht.
Obtaining Documentation and Submitting a Service Request Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m .
Obtaining Documentation and Submitting a Service Request Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c . c o m . Subscribe to the What’s New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.
