Embed Size (px)
Citation preview
1
The EMC Connectrix MDS 9000 NX-OS Family of multilayer directorsand fabric switches offers intelligent fabric-switching services thatrealize maximum performance while ensuring high reliability levelsThese release notes provide the most up-to-date information on andchanges Topics include
Revision history 2 Product description 2 New features and changes 3 Fixed problems 4 Environment and system requirements 5 Known problems and limitations 22 Technical notes 33 Documentation 36 Software media organization and files 37 Installation 37 Troubleshooting and getting help 38
MDS 9000 NX-OS50(4b)
Release NotesPN 300-010-831
Rev A05
Februry 4 2011
2 EMC Connectrix MDS 9000 NX-OS Release Notes
Revision history
Revision history
The following table presents the revision history of this document
Product descriptionThank you for purchasing an MDS 9000 multilayer fabric director orswitch The information contained in this document is a supplementto the MDS 9000 documentation that can be found on wwwciscocomReaders familiar with standard EMCreg release notes may notice thatthe organization of this document is somewhat different than they areused to Take the time to familiarize yourself with the informationprovided
Readers will find information from the original Cisco release notesfor NX-OS and annotations in the technical section including CallHome capability zoning and configuration parameters
As always in an EMC environment refer to the EMC Support Matrixavailable through E-Labtrade Interoperability Navigator athttpelabnavigatorEMCcom for the latest information onsupported configurations
The answers to many MDS 9000 related questions can be found in theEMC Knowledgebase located at
httpPowerlinkEMCcom
The Connectrixreg MDS 9000 Family of multilayer directors and fabricswitches offers intelligent fabric-switching services that realizemaximum performance while ensuring high reliability levels Theycombine robust and flexible hardware architecture with multiplelayers of network and storage management intelligence This
Revision Date Description
50(4b) February 4 2011 Bug fixes
50(4) November 8 2010 Bug fixes
50(1a) September 28 2010 VMAX FCIP write acceleration
50(1a) May 28 2010 VMAX limitation changes
50(1a) April 12 2010 New features enhancements and bug fixes
3
New features and changes
EMC Connectrix MDS 9000 NX-OS Release Notes
powerful combination enables highly available scalable storagenetworks that provide advanced security and unified managementfeatures These release notes provide the most up-to-date informationon new features and changes
New features and changesCisco NX-OS Release 50(4b) is a maintenance release containing bugfixes There are no new features
Generation 1 Hardware support discontinuedNX-OS Release 50(4b) does not support the following Generation 1modules
DS-X9302-14K9 - 142-port Multiprotocol Services(MPS-142)Module
DS-X9016 16-port 1- 2-Gbps Fibre Channel Switching Module
DS-X9032 32-port 1- 2-Gbps Fibre Channel Switching Module
DS-X9032-SSM 32-port Storage Services Module (SSM)
Generation 1 modules should be removed from a switch chassisbefore the installation of NX-OS 50(4b) begins
In addition NX-OS Release 50(4b) does not support the MDS 9216iswitch
Unsupported featuresThe following features are not currently supported in EMCenvironments The list is inclusive of past releases
Trunking F ports and trunking F port channels are not supportedon the following MDS 9000 components
bull DS-C9134-K9 Cisco MDS 9134 Multilayer Fabric Switch ifNPIV is enabled and the switch is used as the NPV coreswitch
bull DS-C9124-K9 Cisco MDS 9124 Multilayer Fabric Switch if NPIV is enabled and the switch is used as the NPV core switch
1 gigabit attach on 8 gigabit Cisco fibre channel line-cards Advanced Encryption Standard (iSCSI only)
4 EMC Connectrix MDS 9000 NX-OS Release Notes
Fixed problems
Boot over SAN is not supported with IVR NAT Caching Services Module Cisco Call Home Cisco MDS Data Mobility Manager (DMM) for the Cisco MDS
9000 Common Information Model Fabric Binding on any McData switch is not supported for Interop
mode four Fabric-Device Management Interface Installation of the 9513 into the EC-1500 cabinet Installation of the 9124 into the EC-1700-C abinet No heterogeneous fabrics supported with SME No disk encryption supported with SME IPSEC iSCSI 16 and 32 port cards are not supported in a 9222i IPsec with Ipv6 Tunneling (IPv4 and v6) is not supported on the same interface iSNS Cloud Discovery LUN Zoning in Fabric NPV on any stand-alone switches Offline data restore tool Proxy Initiator (limited to 1800) Read-Only Zones Storage Management Initiative Specification (SMI-S) 110
support Transceiver and Calibration Information Trespass support VRRP TACACS is not supported for switch-to-switch authentication NDMP backup with IOA is not supported at this time Secure Erase
Note To obtain the most up-to-date information on EMC supportedconfigurations reference the most current release notes available athttpPowerlinkEMCcom and the EMC Support Matrix available throughE-Lab Interoperability Navigator at httpelabnavigatorEMCcom
Fixed problemsCisco-specific caveats for resolved problems can be found in theCisco release-noted documentation with the equivalent firmwarelevel at the following Cisco website
5
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
httpwwwciscocomenUSpartnerproductsps10495prod_release_notes_listhtml
Note Cisco makes all release notes past and present available on thiswebsite
Environment and system requirementsThis section describes the system requirements for MDS NX-OSRelease 50(4b) and includes the following topics
Hardware Supported and Minimum Software Required Determining the Software Version Upgrade Prerequisites Software Upgrade Mechanisms Image Upgrade Matrix Best Practices Maximum ports per Chassis
Telco 2 post racksNote that the 9509 and 9513 should not be used in a 2 post Telco rackdue to weight considerations Refer to the Cisco MDS 9000 HardwareInstallation Guides on httpwwwciscocom for more information
EC-1700 configuration informationConfiguration information appears in the Connectrix EC-1700 CabinetInstallation and Setup Manual on the EMC Powerlinkreg website
Note Currently only the MDS 9509 and 9513 are supported in the EC-1700-Ccabinet The MDS 9124 is not supported in the EC-1700-C
8Gb Power RequirementsEven though Cisco director class models may operate at 100 to 240VAC in configurations consisting of 8 Gb modules 200-240 VAC ishighly recommended Operating at lower voltages will decrease thenumber of modules that may be installed in your chassis
6 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
For more information on power requirements please refer toAppendix C of the Cisco MDS 9500 Series Hardware Installation Guide
Hardware and software componentsEMC supported hardware and software modules are listed in CiscoNX-OS 50(4b) release notes located on the Cisco web site
Note Table 1 lists the MDS 9000 Family software and hardware componentsthat are not supported by EMC as well as the comparable NX-OS partnumbers
For older NX-OS part numbers see prior existing versions of SAN OSrelease notes
Table 1 MDS 9000 Family software and hardware modules not supported(page 1 of 2)
Component EMC part number Description Applicable products
Service modules DS-X9304-18FK9 18-port Fibre Channel4-port GigabitEthernet Multiservice FIPS (MSFM-184)module
MDS 9500 Series and9200 Series
Optics DS-X2-FC10G-ER X2SC optics 10-Gbps Fibre Channel forExtended Reach (40 km)
MDS 9500 Series and9200 Series exceptfor the MDS 9216
DS-X2-E10G-SR X2SC optics 10-Gbps Ethernet for ShortReach
DS-X2-FC10G_CX4 X2CX-4 optics 10-Gbps Fibre Channelcopper
LC-type fiber-optic SFP DS-SFP-GE-T 1-Gbps Ethernet SFP MDS 9000 Family
CWDM DS-CWDM-xxxx Gigabit Ethernet and 4-Gbps FibreChannel SFP LC interface xxxx nmwhere xxxx = 1470 1490 1510 15301550 1570 1590 or 1610 nm
DS-CWDM-MUX-4 Adddrop multiplexer for four CWDMwavelengths
DS-CWDM-MUX-8 Adddrop multiplexer for eight CWDMwavelengths
DS-CWDMCHASSIS Two slot chassis for CWDM adddropmultiplexers
7
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Note EMC personnel can obtain a complete list of Cisco part numbers fromthe Product Support Bulletins available under the ProductTechnicalInformation section of the EMC Global Services website athttpwwwcsisusEMCcomMyGSiVisitURLaspurl=10137
Support for the Generation 3 ModulesThe MDS 9513 Director requires Cisco MDS NX-OS 41(1b) or laterand the MDS 9513 Fabric 2 modules to support the MDS 9000 48-port8-Gbps Fibre Channel module and the MDS 9000 24-port 8-GbpsFibre Channel module
The MDS 9513 Director requires Cisco MDS NX-OS 41(1b) or laterbut does not require the MDS 9513 Fabric 2 modules to support theMDS 9000 444-port 8-Gbps Host-optimized Fibre Channel module
The MDS 9509 Director and the MDS 9506 Director also support theGeneration 3 8-Gbps modules The switches require Supervisor-2modules and Cisco MDS NX-OS 41(1b) or above to support theGeneration 3 8-Gbps modules
For information on the tasks associated with readying the MDS 9500Series to support Generation 3 8-Gbps Fibre Channel switchingmodules refer to the Migrating to Generation 3 Modules appendix inthe Cisco MDS 9500 Series Hardware Installation Guide It presents anoverview of the Generation 3 8-Gbps modules provides usageguidelines for the modules and describes three procedures formigrating hardware and upgrading software to enable use of thesemodules in an MDS 9513 Director
For information on replacing the MDS 9513 Fabric 1 modules withFabric 2 modules refer to the Migrating to Generation 3 Modulesappendix in the Cisco MDS 9500 Series Hardware Installation Guide Itprovides information on installing new Fabric 2 modules while
Port analyzer adapter DS-PAA-2 DS-PAA A standalone Fibre Channel-to-Ethernetadapter that allows for simple transparentanalysis of Fibre Channel traffic in aswitched fabric
MDS 9000 Family
Table 1 MDS 9000 Family software and hardware modules not supported(page 2 of 2)
Component EMC part number Description Applicable products
8 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
running NX-OS Release 4x and SAN-OS Release 3x It also providesinformation on installing the MDS 9513 Fabric 2 modules andactivating higher bandwidth
Configuring Generation 3 and Generation 2 Switching ModulesThe Cisco MDS 9500 Multilayer Directors are designed to operatewith any combination of Cisco MDS 9000 Generation 2 andGeneration 3 modules However there are limitations to considerwhen combining the various modules and supervisors in the CiscoMDS 9500 Series platform chassis The references listed in this sectionprovide specific information about configurations that combinedifferent modules and supervisors
For information on configuring Generation 2 and Generation 3switching modules refer to the Configuring Generation 2 andGeneration 3 Switching Modules chapter in the Cisco MDS 9000Family CLI Configuration Guide
For information on port index availability refer to the ldquoPort IndexAvailabilityrdquo section in the Product Overview chapter of the CiscoMDS 9500 Series Hardware Installation Guide
For information on Cisco MDS 9000 hardware and softwarecompatibility refer to the EMC Support Matrix available through E-LabInteroperability Navigator (ELN) at httpelabnavigatorEMCcom
MDS 9000 Chassis and Module Support in Cisco MDS NX-OS 5xTable 2 lists the MDS hardware chassis supported by Cisco MDSNX-OS 5x
Table 2 Cisco MDS NX-OS 5x Chassis Support Matrix
Switch NX-OS 5x Support
MDS 9513 Yes
MDS 9509 Yes
MDS 9506 Yes
MDS 9222i Yes
MDS 9216i No
9
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Table 3 lists the MDS hardware modules supported by Cisco MDSNX-OS 5x
MDS 9216A No
MDS 9216 No
MDS 9148 Yes
MDS 9134 Yes
MDS 9124 Yes
MDS 9140 No
MDS 9120 No
Table 2 Cisco MDS NX-OS 5x Chassis Support Matrix
Switch NX-OS 5x Support
Table 3 Module Support Matrix for Cisco MDS NX-OS 5x (page 1 of 2)
Module DescriptionMDS 9500Series MDS 9222i
DS-X9530-SF2A-K9 MDS 9500 Supervisor-2A Module Yes NA
DS-X9530-SF2-K9 MDS 9500 Supervisor-2 Module Yes NA
DS-X9530-SF1-K9 MDS 9500 Supervisor-1 Module No NA
DS-X9224-96K9 24-port 8-Gbps Fibre Channel Switching Module Yesa No
DS-X9248-96K9 48-port 8-Gbps Fibre Channel Switching Module Yesa No
DS-X9248-48K9 444-port Host Optimized 8-Gbps Fibre ChannelSwitching Module
Yes Yes
DS-X9316-SSNK9 16-Port Storage Services Node (SSN-16) Yes Yes
DS-X9304-18K9 184-Port Multiprotocol Services Module(MSM-184)
Yes Yes
DS-X9112 12-port 4-Gbps Fibre Channel Switching Module Yes Yes
DS-X9124 24-port 4-Gbps Fibre Channel Switching Module Yes Yes
DS-X9148 48-port 4-Gbps Fibre Channel Switching Module Yes Yes
DS-X9704 4-port 10-Gbps Fibre Channel Switching Module Yes Yes
10 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Migrating from Supervisor-1 Modules to Supervisor-2 ModulesAs of Cisco MDS SAN-OS Release 30(1) the Cisco MDS 9509 and9506 Directors support both Supervisor-1 and Supervisor-2 modulesSupervisor-1 and Supervisor-2 modules cannot be installed in thesame switch except during migration Both the active and standbysupervisor modules must be of the same type either Supervisor-1 orSupervisor-2 modules For Cisco MDS 9513 Directors bothsupervisor modules must be Supervisor-2 modules
CAUTION
Migrating your supervisor modules is a disruptive operation
Note Migrating from Supervisor-2 modules to Supervisor-1 modules is not supported
To migrate from a Supervisor-1 module to a Supervisor-2 module refer to the step-by-step instructions in the Cisco MDS 9000 NX-OS Release 41(x) and SAN-OS 3(x) Software Upgrade and Downgrade Guide
DS-X9302-14K9 142-port Multiprotocol Services (MPS-142)Module
No No
DS-X9016 16-port 1- 2-Gbps Fibre Channel SwitchingModule
No No
DS-X9032 32-port 1- 2-Gbps Fibre Channel SwitchingModule
No No
DS-X9032-SSM 32-port Storage Services Module (SSM) No No
DS-X9308-SMIP 8-port 1- 2-Gbps IP Switching Module No No
DS-X9304-SMIP 4-port 1- 2-Gbps IP Switching Module No No
a Requires DS-13SLT-FAB2 in the MDS 9513
Table 3 Module Support Matrix for Cisco MDS NX-OS 5x (page 2 of 2)
Module DescriptionMDS 9500Series MDS 9222i
11
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Software Download ProcessUse the software download procedure to upgrade to a later versionor downgrade to an earlier version of an operating system Thissection describes the software download process for the Cisco MDSNX-OS software and includes the following topics
ldquoDetermining the Software Versionrdquo on page 11
ldquoDownloading Softwarerdquo on page 11
ldquoSelecting the Correct Software Image for an MDS 9100 SeriesSwitchrdquo on page 12
ldquoSelecting the Correct Software Image for an MDS 9200 SeriesSwitchrdquo on page 13
ldquoSelecting the Correct Software Image for an MDS 9500 SeriesSwitchrdquo on page 13
Determining the Software VersionTo determine the version of Cisco MDS NX-OS or SAN-OS softwarecurrently running on a Cisco MDS 9000 Family switch using the CLIlog in to the switch and enter the show version EXEC command
To determine the version of Cisco MDS NX-OS or SAN-OS softwarecurrently running on a Cisco MDS 9000 Family switch using theFabric Manager view the Switches tab in the Information pane locatethe switch using the IP address logical name or WWN and check itsversion in the Release column
Note EMC strongly recommends that you use the latest qualified softwarerelease for all MDS 9000 Family products Refer to the EMC Support Matrixavailable through E-Lab Interoperability Navigator (ELN) athttpelabnavigatorEMCcom for the latest information on qualifiedfirmware revisions
Downloading SoftwareThe Cisco MDS NX-OS software is designed for mission-critical highavailability environments To realize the benefits of nondisruptiveupgrades on the Cisco MDS 9500 Directors we highly recommendthat you install dual supervisor modules
12 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Before performing upgrades submit all requested changes to theEMC Global Services CCA change control process so that anypotential operating environment impacts can be analyzedbeforehand
EMC personnel should also refer to the Connectrix MDS 9000 FamilySoftware Image Upgrade Instructions for a complete list of prerequisitesThis document is available on the Global Services websitehttpwwwcsisusEMCcom under Application Download AreaESN Product Information Connectrix MDS 9000 Family EMCpersonnel can download the Software Images from the GlobalServices website httpwwwcsisusEMCcom under ApplicationDownload Area ESN Product Information Connectrix MDS 9000Family
See the following sections in this release note for details on how youcan nondisruptively upgrade your Cisco MDS 9000 switch Issuingthe install all command from the CLI or using Fabric Manager toperform the downgrade enables the compatibility check The checkindicates if the upgrade can happen nondisruptively or disruptivelydepending on the current configuration of your switch and thereason
Compatibility check is doneModule bootable Impact Install-type Reason------ -------- -------------- ------------ ------
1 yes non-disruptive rolling2 yes disruptive rolling Hitless upgrade is not supported3 yes disruptive rolling Hitless upgrade is not supported4 yes non-disruptive rolling5 yes non-disruptive reset6 yes non-disruptive reset
Selecting the Correct Software Image for an MDS 9100 Series SwitchThe system and kickstart image that you use for an MDS 9100 seriesswitch depends on which switch you use as shown in Table 4
Table 4 Software Images for MDS 9100 Series Switches
Cisco MDS 9100 Series Switch Type Naming Convention
9124 and 9134 Filename begins with m9100-s2ek9
9148 Filename begins with m9100-s3ek9
13
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Selecting the Correct Software Image for an MDS 9200 Series SwitchThe system and kickstart image that you use for an MDS 9200 seriesswitch depends on which switch you use as shown in Table 5
Selecting the Correct Software Image for an MDS 9500 Series SwitchThe system and kickstart image that you use for an MDS 9500 Seriesswitch depends on whether the switch is based on a Supervisor-1module or a Supervisor-2 module as shown in Table 6
Use the show module command to display the type of supervisormodule in the switch The following is sample output from the showmodule command on a Supervisor 2 module
Table 5 Software Images for MDS 9200 Series Switches
Cisco MDS 9200 Series Switch Type Naming Convention
9222i Filename begins with m9200-s2ek9
Table 6 Software Images for Supervisor Type
Cisco MDS 9500 Series Switch Type Supervisor Module Type Naming Convention
9513 9509 and 9506 Supervisor-2 module Filename begins with m9500-sf2ek9
14 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
switch show moduleMod Ports Module-Type Model Status--- ----- -------------------------------- ------------------ ------------7 0 SupervisorFabric-2 DS-X9530-SF2-K9 active 8 0 SupervisorFabric-2 DS-X9530-SF2-K9 ha-standby
Upgrading Your Cisco MDS NX-OS Software ImageThis section lists the guidelines recommended for upgrading yourCisco MDS NX-OS software image and includes the following topics
ldquoGeneral Upgrading Guidelinesrdquo on page 14
ldquoDowngrading Your Cisco MDS SAN-OS Software Imagerdquo onpage 18
Note Before you begin the upgrade process review the list of chassis andmodules that NX-OS Release 50(4b) supports See the ldquoMDS 9000 Chassisand Module Support in Cisco MDS NX-OS 5xrdquo on page 8
Note For detailed instructions for performing a software upgrade usingCisco Fabric Manager see the Cisco Fabric Manager Release Notes forRelease 50(4b) which is available from the following websitehttpPowerlinkEMCcom
General Upgrading Guidelines
Note To upgrade to NX-OS Release 50(4b) you must be running NX-OSRelease 4x If you are running SAN-OS Release 32(3a) or earlier firstupgrade to SAN-OS Release 33(x) then NX-OS Release 4x and thenupgrade to NX-OS Release 50(4b)
Use the following guidelines when upgrading to Cisco MDS NX-OSRelease 5x
Install and configure dual supervisor modules
Issue the show install all impact upgrade-image CLI command todetermine if your upgrade will be nondisruptive
15
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Be aware of the impact of an upgrade on VSAN 4079 if you areupgrading from SAN-OS Release 3x to NX-OS 50(4b) See theldquoUpgrading Effect on VSAN 4079rdquo on page 17
Follow the recommended guidelines for upgrading a Cisco MDS9124 or MDS 9134 Switch as described in ldquoUpgrading a CiscoMDS 9124 or MDS 9134 switchrdquo on page 18
Take note of the affect of upgrades on MDS 9500 series switchesthat have active IOA flows as described in ldquoMDS 9500 seriesupgrades with active IOA flowsrdquo on page 18
Be aware that some features impact whether an upgrade isdisruptive or nondisruptive
bull Fibre Channel Ports Traffic on Fibre Channel ports can benondisruptively upgraded See Table 7 on page 16 for thenondisruptive upgrade path for all NX-OS and SAN-OSreleases
bull Storage Services Intelligent storage services traffic such asSANTap NASB and FC write acceleration is disruptedduring an upgrade Fibre Channel traffic is not
bull Gigabit Ethernet Ports Traffic on Gigabit Ethernet ports isdisrupted during an upgrade or downgrade This includes theGigabit Ethernet ports on the MSM-184 module and the MDS9222i switch Those nodes that are members of VSANs traversingan FCIP ISL are impacted and a fabric reconfiguration occursiSCSI initiators connected to the Gigabit Ethernet ports loseconnectivity to iSCSI targets while the upgrade is in progress
bull FICON If you have FICON enabled the upgrade path isdifferent See Table 6 on page 13
Use Table 7 to determine your nondisruptive upgrade path to Cisco MDSNX-OS Release 50(4b) find the image release number you are currentlyusing in the Current column of the table and use the path recommended
16 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Note The software upgrade information in Table 7 applies only to FibreChannel switching traffic Upgrading system software disrupts IP traffic andSSM intelligent services traffic
MDS NX-OS Release 50(4b) is not a FICON-qualified release
Table 7 Nondisruptive Upgrade Path to Cisco MDS NX-OS Release 50(4b)
Current Nondisruptive Upgrade Path
NX-OS 50(4) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 50(1a) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(7b) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(5) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(3) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(1b) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(1a) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 41(3a) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 41(1b) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
SAN-OS 33(4a) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
NX-OS 33(4) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 33(3) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 33(2) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 33(1c) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 32(3a) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 32(2c) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 32(1a) Upgrade to SAN-OS Release then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 31(3a) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 31(2) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
17
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Use Table 8 to determine your FICON nondisruptive upgrade path toCisco MDS NX-OS Release 42(7b) Find the image release numberyou are currently using in the Current Release with FICON Enabledcolumn of the table and use the path recommended
Note For more information on the FICON qualified NX-OS releases refer tothe EMC Support Matrix available through E-Lab Interoperability Navigator(ELN) at httpelabnavigatorEMCcom
Upgrading Effect on VSAN 4079If you are upgrading to NX-OS Release 50(4b) and you have notcreated VSAN 4079 the NX-OS software will automatically createVSAN 4079 and reserve it for EVFP use If VSAN 4079 is reserved forEVFP use the switchport trunk allowed vsan command will filterout VSAN 4079 from the allowed list as shown in the followingexample
switch(config-if) switchport trunk allowed vsan1-40801-40784080switch(config-if)
If you have created VSAN 4079 the upgrade to NX-OS Release50(4b) will have no affect on VSAN 4079
If you downgrade to a release of NX-OS lower than 41(x) afterNX-OS Release 50(4b) creates VSAN 4079 and reserves it for EVFPuse the VSAN will no longer be reserved
Table 8 FICON Nondisruptive Upgrade Path to NX-OS Release 42(7b)
Current Release withFICON Enabled Upgrade Path
NX-OS 42(1b) You can nondisruptively upgrade directly to NX-OS Release 42(7b)
NX-OS 41(1c) You can nondisruptively upgrade directly to NX-OS Release 42(7b)
SAN-OS 33(1c) You can nondisruptively upgrade directly to NX-OS Release 42(7b)
18 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Upgrading a Cisco MDS 9124 or MDS 9134 switchIf you are upgrading from Cisco MDS SAN-OS Release 31(1) to CiscoNX-OS Release 4x before upgrading to NX-OS Release 50(4b) on aCisco MDS 9124 or MDS 9134 switch follow these guidelines
During the upgrade configuration is not allowed and the fabric isexpected to be stable
The Fabric Shortest Path First (FSPF) timers must be configured tothe default value of 20 seconds otherwise the nondisruptiveupgrade is blocked to ensure that the maximum down toim forthe control plane can be 80 seconds
If there are any CFS commits in the fabric the nondisruptiveupgrade will fail
If there is a zone server merge in progress in the fabric thenondisruptive upgrde will fail
If a service terminates the nondisruptive upgrade the showinstall all failure-reason command can display the reason thatthe nondisruptive upgrade cannot proceed
If there is not enough memory in the system to load the newimages the upgrade will be made disruptive due to insufficientresources and the user will be notified in the compativility table
MDS 9500 series upgrades with active IOA flowsWhen upgading an MDS 9500 series switch that has active IOA flowsthose flows may be interrupted during the supervisor moduleswitchover To workaround this issue you have to enablespanning-tree portfast on the interface on the catalyst connected tothe management interface of the activestandby supervisor for theinterface to come up fast without causing the cluster to lose quorum
Downgrading Your Cisco MDS SAN-OS Software ImageThis section lists the guidelines recommended for downgrading yourCisco MDS SAN-OS software image and includes the followingtopics
ldquoGeneral downgrading guidelinesrdquo on page 19
19
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
General downgrading guidelinesUse the following guidelines to nondisruptively downgrade yourCisco MDS NX-OS Release 50(4b)
Install and configure dual supervisor modules
Issue the system no acl-adjacency-sharing execute command todisable acl adjacency usage on Generation 2 and Generation 1modules If this command fails reduce the number of zones IVRzones TE ports or a combination of these in the system and issuethe command again
Disable all features not supported by the downgrade release Usethe show incompatibility system downgrade-image command todetermine what you need to disable
bull If you are running in interoperability mode two such featuresare the Reliable Commit Service and Full Zone DatabaseDistribution They can be disabled by running thesecommand in config term mode
no zone rcs enableno zoneset capability distribute full
Use the show install all impact downgrade-image command todetermine if your downgrade will be nondisruptive
Be aware that some features impact whether a downgrade isdisruptive or nondisruptive
bull Fibre Channel Ports Traffic on Fibre Channel ports can benondisruptively downgraded See Table 9 on page 20 for thenondisruptive downgrade path for all SAN-OS releases
bull Storage Services Intelligent storage services traffic such asSANTap NASB and FC write acceleration is disruptedduring a downgrade Fibre Channel traffic is not
bull Gigabit Ethernet Ports Traffic on Gigabit Ethernet ports isdisrupted during a downgrade This includes the GigabitEthernet ports on the MSM-184 module and the MDS 9222iswitch Those nodes that are members of VSANs traversing anFCIP ISL are impacted and a fabric reconfiguration occursiSCSI initiators connected to the Gigabit Ethernet ports loseconnectivity to iSCSI targets while the downgrade is inprogress
20 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
bull FICON If you have FICON enabled the downgrade path isdifferent See Table 10 on page 21
Note A downgrade from NX-OS Release 4x to SAN-OS Release 33(1c) is notsupported on MDS switches when FC-Redirect based applications such asData Mobility Manager or Storage Media Encryption are configured in thefabric if either of the following conditions are satisfied
1 A target for which FC-Redirect is configured is connected locally and thereare Generation 1 modules with ISLs configured in the switch
2 A host for which FC-redirect is configured is connected locally ona Generation 1 module
If these conditions exist remove the application configuration forthese targets and hosts before proceeding with the downgrade
Use Table 9 on page 20 to determine the nondisruptive downgradepath from Cisco NX-OS Release 50(4b) Find the NX-OS or SAN-OSimage you want to downgrade to in the To SAN-OSNX-OS Releasecolumn of the table and use the path recommended
Note The software downgrade information in Table 10 on page 21 appliesonly to Fibre Channel switching traffic Downgrading system softwaredisrupts IP and SSM intelligent services traffic
Table 9 Nondisruptive Downgrade Path from NX-OS Release 50(4b) (page 1 of2)
To SAN-OS NX-OSRelease Nondisruptive Downgrade Path
NX-OS 50(4) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 50(1a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(7b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(5) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(3) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(1b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(1a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 41(3a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
21
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Use Table 10 to determine your nondisruptive downgrade path if youhave FICON enabled from Cisco NX-OS Release 42(7b) Find the imagerelease number you are currently using in the Current Release withFICON Enabled column of the table and use the path recommended
NX-OS 41(1b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
SAN-OS 33(5a) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33())
SAN-OS 33(5) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(4a) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
NX-OS 33(4) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(3) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
NX-OS 33(2) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(1c) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 32(3a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 32(x)
SAN-OS 32(2c) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 32(x)
SAN-OS 32(1a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
SAN-OS 31(3a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
SAN-OS 31(2) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
Table 9 Nondisruptive Downgrade Path from NX-OS Release 50(4b) (page 2 of2)
To SAN-OS NX-OSRelease Nondisruptive Downgrade Path
Table 10 FICON Downgrade Path from NX-OS Release 42(7b)
To SAN-OSNX-OS Release withFICON Enabled Downgrade Path
NX-OS 42(1b) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
NX-OS 41(1c) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
SAN-OS 33(1c) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
22 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Best practicesLog messages are not saved across system reboots or power outagesTherefore EMC recommends that customers configure a SyslogServer in order to redirect and capture all log messages on a remoteserver For more information please refer to the Cisco MDS 9000Family Configuration Guide available at
httpwwwciscocomenUSproductsps5989products_support_series_homehtml
Maximum ports per chassisTable 11 shows the maximum ports per chassis
a V2 indicates a 9506 or 9509 with Generation-2 Supervisors The presence of anygeneration one module in a switch will limit the maximum port count to 252This includes the 16-port 32-port 14+2 IPS4 and IPS8 cards
Known problems and limitationsFor a list of problems with this release please refer to the CiscoRelease notes located at
httpwwwciscocomenUSproductsps5989prod_release_notes_listhtml
Limitations and restrictionsThe following limitations and restrictions apply to all switches in theCisco MDS 9000 Family unless a limitation for a specific switch isstated
ldquoStorage Media Encryption (SME) limitationsrdquo on page 24
Table 11 Maximum ports per chassis
Chassis Maximum number of ports
MDS 9506-V2 192a
MDS 9509-V2 336
MDS 9513 528
23
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
ldquoSME configuration limitsrdquo on page 24
ldquoDeleting Cisco SME interfacesrdquo on page 25
ldquoCisco MDS 9124 and 9134 Multilayer fabric switchesrdquo on page 25
ldquoN-Port virtualization configuration limitsrdquo on page 25
ldquoMaximum number of zones supported in Interop Mode 4rdquo onpage 25
ldquoIPv6rdquo on page 26
ldquoIP-ACL supportrdquo on page 26
ldquoUser Rolesrdquo on page 26
ldquoUsing a RSA Version 1 Key for SSH Following an Upgraderdquo onpage 27
ldquoApplying Zone Configurations to VSAN 1rdquo on page 27
ldquoInterVSAN Routingrdquo on page 28
ldquoRSPAN Traffic Not Supported on CTS Ports on 8-GbpsSwitching Modulesrdquo on page 28
ldquoIO Accelerator Feature Limitationsrdquo on page 28
ldquoSupport for FCIP Compression Modesrdquo on page 28
ldquoSaving Copies of the Running Kickstart and System Imagesrdquo onpage 29
ldquoConfiguring Buffer Credits on a Generation 2 or Generation 3Modulerdquo on page 29
ldquoStorage services module power budgetrdquo on page 29
ldquoiSCSI proxy initiator in Celerra HighRoad environmentsrdquo onpage 30
ldquoHPUX N_port IDrdquo on page 30
ldquoInteroperability limitationsrdquo on page 31
ldquoNASBrdquo on page 31
ldquoReserved VSAN Range and Isolated VSAN Range Guidelinesrdquoon page 31
ldquoSymmetrix VMax limitationsrdquo on page 32
ldquoStorage Applications on the MSM-184rdquo on page 32
ldquoDowngrading with fport-channel-trunk enabledrdquo on page 32
ldquoLDAP Authenticationrdquo on page 33
24 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
ldquoMDS-9148 limitationsrdquo on page 33
Storage Media Encryption (SME) limitationsAn SME node can only belong to one cluster Adding the node tomore than one cluster will cause problems
Currently there is no prevention or warning in place when an attemptis made to add a node to multiple clusters
SME configuration limitsTable 12 lists the SME configuration limits for this release
Table 12 SME configuration limits
Configuration Limits
Number of switches in the fabric 10
Number of clusters per switch 1
Switches in a cluster 4
Fabrics in a cluster 2
Modules in a switch 11
Cisco MSM-184 modules in a cluster 32
Initiator-Target-LUNs (ITLs) 1024
LUNs behind a target 32
Host and target ports in a cluster 128
Number of hosts per target 128
Tape backup groups per cluster 2
Volume groups in a tape backup group 4
Cisco Key Management Center ( of keys) 32K
Targets per switch that can be FC-redirected 32
25
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Deleting Cisco SME interfacesA Cisco SME interface can be deleted from the cluster only after theinterface is administratively shut-down and all related tasksassociated with the interface shut-down are complete
Cisco MDS 9124 and 9134 Multilayer fabric switchesThe Cisco MDS 9124 and 9134 Multilayer fabric switches do notsupport the following Cisco MDS SAN-OS features
IVR Remote Span Translative loop support FCCmdash no generation quench reaction only
In addition the following features have these limits
VSANs mdash 16 maximum SPAN mdash 1 session maximum
N-Port virtualization configuration limitsThe NPV features have maximum configuration limits Table 13shows the verified and maximum limits for the NPV switchesrunning NX-OS Release 5x
Maximum number of zones supported in Interop Mode 4In interop mode 4 the maximum number of zones that is supportedin an active zone set is 2047 due to limitations in the connectedvendor switch When IVR is used in interop mode 4 the maximumnumber of zones supported including IVR zones in the active zoneset is 2047 The limit for the maximum number of IVR zones perVSAN is 250 zones (two members per zone)
Table 13 NPV features limitations
Feature Verified limits Maximum limits
FLOGIs or F Disc per NPV port group 114 114
NPV switches per NPV core switch 105 105
FLOGIs per line card on NPV core switch 400 400
26 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
IPv6The management port on Cisco MDS switches supports oneuser-configured IPv6 address but does not supportauto-configuration of an IPv6 address
IP-ACL supportDo not apply IP-ACLs to only one member of a PortChannel groupApply IP-ACLs to the entire channel group
If IP-ACLs are already configured in a Gigabit Ethernet interface youcannot add this interface to a Ethernet PortChannel group
Refer to the Cisco MDS 9000 Family Configuration Guide
User RolesIn SAN-OS Release 33(x) and earlier when a user belongs to a rolewhich has a VSAN policy set to Deny and the role allows access to aspecific set of VSANs (for example 1 through 10) the user isrestricted from performing the configuration clear execute anddebug commands which had a VSAN parameter outside thisspecified set Beginning with NX-OS Release 41(1b) these users arestill prevented from performing configuration clear execute anddebug commands as before however they are allowed to performshow commands for all VSANs The ability to execute the showcommand addresses the following
In a network environment users often need to view informationin other VSANs even though they do not have permission tomodify configurations in those VSANs
This behavior makes Cisco MDS 9000 Series switches consistentwith other Cisco products such as Cisco Nexus 7000 Seriesswitches that exhibit the same behavior for those roles (whenthey apply to the VLAN policy)
27
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Using a RSA Version 1 Key for SSH Following an UpgradeFor security reasons NX-OS Release 42(x) and higher does notsupport RSA version 1 keys As a result if you upgrade from anearlier version that did support RSA version 1 keys and you hadconfigured a RSA version 1 key for SSH then you will not be able tolog in through SSH following the upgrade
If you have a RSA version 1 key configured for SSH beforeupgrading to NX-OS Release 42(x) or higher follow these steps
1 Disable SSH
2 Create RSA version 2 DSA keys
3 Enable SSH
4 Delete any RSA version 1 keys on any remote SSH clients andreplace the version 1 keys with the new version 2 keys from theswitch
Proceed with the upgrade to NX-OS Release 42(x) or higher
If you upgrade before disabling SSH and creating RSA version 2 keysfollow these steps
1 Open a Telnet session and log in through the console
2 Issue the no feature ssh command to disable SSH
3 Issue the ssh key rsa 1024 command to create RSA version 2 keys
4 Issue the feature ssh command to enable SSH
Applying Zone Configurations to VSAN 1In the setup script you can configure system default values for thedefault-zone to be permit or deny and you can configure defaultvalues for the zone distribution method and for the zone mode
These default settings are applied when a new VSAN is createdHowever the settings will not take effect on VSAN 1 because it existsprior to running the setup script Therefore when you need thosesettings for VSAN 1 you must explicitly issue the followingcommands
zone default-zone permit vsan 1 zoneset distribute full vsan 1 zone mode enhanced vsan 1
28 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
InterVSAN RoutingWhen using InterVSAN Routing (IVR) it is recommended to enableCisco Fabric Services (CFS) on all IVR-enabled switches Failure to doso may cause mismatched active zone sets if an error occurs duringzone set activation
RSPAN Traffic Not Supported on CTS Ports on 8-Gbps Switching ModulesAn inter-switch link (ISL) that is enabled for Cisco TrustSec (CTS)encryption must be brought up in non-CTS mode to support remoteSPAN (RSPAN) traffic on the following modules
DS-X9248-96K9 Cisco MDS 9000 48-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9224-96K9 Cisco MDS 9000 24-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9248-48K9 Cisco MDS 9000 444-Port Host-Optimized8-Gbps Fibre Channel Switching Module
If the ISL link is brought up with CTS enabled random packets dropsof both RSPAN traffic and normal traffic will occur on the receiverport switch
IO Accelerator Feature LimitationsIOA does not support the following NX-OS features
IVR flows
Devices with NPV and NPIV enabled
F port trunking
bull F port channeling
Support for FCIP Compression ModesIn Cisco NX-OS Release 42(1b) and higher FCIP compression mode 1and compression mode 3 are not supported on the Cisco MSM-184module and on the SSN-16 module
29
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Saving Copies of the Running Kickstart and System ImagesAfter you upgrade to MDS NX-OS Release 42(1b) or higher you arenot allowed to delete rename move or overwrite the kickstart andsystem images that are in the current system bootvar settings on anactive or standby MDS Supervisor-2 module on any Cisco MDS 9500Series switch This restriction does not apply to the integratedsupervisor module on the MDS 9200 and MDS 9100 series switches
Configuring Buffer Credits on a Generation 2 or Generation 3 ModuleWhen you configure port mode to auto or E on a Generation 2module one of the ports will not come up for the followingconfiguration
Port Mode auto or E for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E on a Generation 3module one or two of the ports will not come up for the followingconfiguration
Port Mode auto or E for the first half of the ports the second halfof the ports or for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E for all ports in the globalbuffer pool you need to reconfigure buffer credits on one or more ofthe ports The total number of buffer credits configured for all theports in the global buffer pool should be reduced by 64
Storage services module power budgetThe MDS 9509 does not have the power budget to run seven SSMcards EMC recommends a maximum of four SSMs in one 9509Customers wishing to use more than four SSMs in one chassis shouldrefer to the Cisco MDS 9000 documentation on the Ciscocom websiteto validate that there is enough power available for their desiredconfiguration
30 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Note Upgrading to the 3000 watt power supplies will alleviate thiscondition
iSCSI proxy initiator in Celerra HighRoad environmentsEMC supports the iSCSI proxy initiator feature in Celerrareg
HighRoadreg environments In proxy initiator mode one Fibre Channelinitiator is used for all iSCSI clients who access the switch via thesame iSCSI interface (iscsi33 for example)
The initiators will use the PWWN assigned to the iSCSI interface TheiSCSI interface to which an iSCSI client will logon to is configured inthe client and must be permitted by the virtual target configured forthat initiator
The current session environment supported on the MDS is
300 sessions per port 1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no InitialR2T=yes
Refer to the specific initiator support documentation on how to setthe parameters The implementation will not perform properly ifthese bits are not set
Refer to the MDS documentation for more information regarding theconfiguration of the iSCSI proxy initiator at the following Ciscowebsite
httpwwwciscocomenUSproducts
HPUX N_port IDThe N_port ID port value of 255 (0xFF) has special meaning forHP-UX A N_port ID (FC_ID) can not be returned from a switch thatcontains this value for the N_port ID (FC_ID) port value for a HP-UXinitiator or HP-UX target port Port ID value of 255 (0xFF) cannot be
31
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
configured for HP-UX initiator port and HP-UX target ports whenconfiguring MDS FC_IDs The port_ID value is the third byte of theFC_ID
Interoperability limitationsRefer to the EMC Support Matrix (ESM) and the EMC Networked Storage Topology Guide for modes of operation and caveats
NASBThe NASB feature requires that the backup application load the tapedrive with a compatible tape cartridge prior to configuring NASB inthe backup VSAN
Reserved VSAN Range and Isolated VSAN Range GuidelinesOn an NPV switch with a trunking configuration on any interface or ona regular switch where the feature fport_channel_trunk command hasbeen issued to enable the F PortChannel feature follow theseconfiguration guidelines for reserved VSANs and the isolated VSAN
bull If trunk mode is on for any of the interfaces or NP PortChannelis up the reserved VSANs are 3040 to 4078 and they are notavailable for user configuration
bull The Exchange Virtual Fabric Protocol (EVFP) isolated VSAN is4079 and it is not available for user configuration
bull VSAN 4079 will be impacted by an upgrade to NX-OS Release42(3) depending on whether or not VSAN 4079 was createdprior to the upgrade See theldquoUpgrading Effect on VSAN 4079rdquoon page 17
The following VSAN IDs are assigned in the Fibre Channel Framingand Signaling (FC-FS) interface standard
VF_ID Value Value Description
00h Do not use as a Virtual FabricIdentifier
001h EFFh Available as a Virtual FabricIdentifier
F00h FEEh Reserved
32 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Symmetrix VMax limitationsAt the time of this writing the following features are not supportedfor use with the Symmetrix VMax
FCIP Write Acceleration
The NX-OS IOA functionality is only supported with the Q2 SREnginuity release 5874229182 or higher
For the most up to date status please refer to the current revision ofthese Release Notes on httpPowerlinkemccom and the EMCSupport Matrix available through E-Lab Interoperability Navigator (ELN) athttpelabnavigatorEMCcom
Storage Applications on the MSM-184The MDS 9000 184-Port Multiservice Module (MSM-184) does notsupport multiple concurrent storage applications Only oneapplication can run on the MSM-184 at a time
Downgrading with fport-channel-trunk enabledIf you are running MDS NX-OS Release 42(x) or higher with thefport-channel-trunk feature enabled and you downgrade to anyNX-OS 41(1x) release the installer performs a nondisruptivedowngrade even though the fport-channel-trunk feature is notsupported in NX-OS 41(1x) releases
As a result the switch is in an inconsistent state and the ports maynot function properly
FEFh Control VF-ID (see FibreChannel Link Services (FC-LS)and Fibre Channel SwitchFabric Generation 4 (FC-SW-4)standards)
FF0h FFEh Vendor specific
FFFh Do not use as a Virtual FabricIdentifier
FEFh = 4079
33
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
If you are in this state a workaround is to reboot the switch followingthe upgrade
LDAP AuthenticationThere is currently a limitation in the LDAP server configuration CLIthat prevents the use of an OU with spaces in the name Normallythese OU names could be surrounded by quotation marks howeverquotation marks are not supported by the ldap-server command
MDS-9148 limitationsThe Cisco MDS 9148 Multilayer Fabric Switch does not support thefollowing NX-OS features
Medium and Long range 4GB Agilent
IVR
Remote Span
Translative loop support
FCC - no generation quench reaction only
FC-Redirect
In addition the following features have these limits
VSANS - 31 maximum
SPAN - 1 session maximum
Technical notesThe following sections provide further information on technicalnotes
EMC Email Home for Cisco MDS switchesInstallation and Trouble shooting instructions can be found in thedocumentation located at the EMC Customer Service Internalwebsite
httpwwwcsisusemccomcsweb2esnesnhomehtmConnectrix20MDS20900020Family
34 EMC Connectrix MDS 9000 NX-OS Release Notes
Technical notes
Customers requiring installation of this solution should contact theirEMC Customer Engineer to assist with the installation and providethe documentation
Supported iSCSI sessionsThe current iSCSI session environment supported on the MDS is
300 sessions per port
1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no
InitialR2T=yes
Upgrading Cisco SAN-OSThere are several methods available for upgrading SAN-OS SoftwareEMC personnel are strongly recommended that all upgrades be doneby the Automated One-Step Upgrade using the install all
command EMC personnel should refer to the Connectrix MDS 9000Family Software Image Upgrade Instructions for a complete list ofprerequisites and instructions for performing the upgrade Thisdocument along with tftp software is available on the GlobalServices website at httpwwwcsisusEMCcom under ApplicationDownload Area ESN Product Information Connectrix MDS 9000Family
The Software Upgrade Wizard is an option for upgrades While theinstall all is the preferred method the Software Install Wizard canalso be used
Supported configuration parametersFor the most up-to-date information refer to the EMC Support Matrixavailable through E-Lab Interoperability Navigator athttpelabnavigatoremccom for the latest information onsupported configurations
35
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
Supported zoning parametersRefer to the EMC Networked Storage Topology Guide for the mostup-to-date information on supported zoning parameters
At the time these notes were published the following parameterswere supported
20 VSANs 5 Hops 2000 Unique members per physical infrastructure 1000 Zonesets per physical infrastructure 2000 Zones per physical infrastructure 1 FCIP tunnel
Supported IVR parameters IVR zone members 1000 IVR zones 1000 IVR zone sets 32 VSANS 20 IVR enabled switches 64
An RPQ can be submitted for any configurations that exceed thislimit
Managing zone changes in multiswitch fabricsZoning changes may be made through Fabric Manager or CLI Whenaccessing Fabric Manager or CLI the user does so from the point ofview of one switch That is Fabric Manager and CLI are accessed byentering the IP address of one switch in the fabric
When zoning changes are made the applicable VSAN and zone setdata is propagated to the rest of the switches in the fabric via the ISLs
When zoning changes are made to a VSAN the zone set data ispropagated to the rest of the switches in the fabric via the ISLs Bydefault only the active zone set information is relayed to all switchesin the VSAN If the user accesses the Fabric Manager and CLI fromanother switch in the fabric the new VSAN and zone set informationwill not be viewable To view the active and inactive zone set on theother switches in the fabric the user must log in to the CLI and issuea command from the EXEC prompt
36 EMC Connectrix MDS 9000 NX-OS Release Notes
Documentation
Example The following is an example of copying VSAN 1 through 20 zoningdata
CiscoMDS_name zone copy active full vsan 1-20
CiscoMDS_name conf t
Enter configuration commands one per line End with CNTL Z
CiscoMDS_name(config) zoneset distribute full vsan 1-20
CiscoMDS_name(config)
Note This command needs to be issued on all switches in the fabric one timeonly
This is a nondisruptive command After issuing the commands theuser will now see the active and inactive zone sets for the specifiedVSANs on any switch that is chosen from which to manage the fabric
After a zoning change is made save the running configuration to thestartup configuration
DocumentationSend documentation comments to mdsfeedback-doccom
Product DocumentationAs of NX-OS Release 42(1a) software configuration information isavailable in new feature-specific configuration guides for thefollowing information
System management
Interfaces
Fabric
Quality of service
Security
IP services
High availability and redundancy
37
Software media organization and files
EMC Connectrix MDS 9000 NX-OS Release Notes
The information in these new guides previously existed in the CiscoMDS 9000 Family CLI Configuration Guide That configuration guideremains available on Ciscocom and should be used for all softwarereleases prior to NX-OS Release 42(1a) Configuration guidesaddress the features introduced in or available in a particular releaseSelect and view the configuration guide that pertains to the softwareinstalled in your switch
In addition Fabric Manager information has been removed from theMDS NX-OS Release Notes (this document) and placed intostandalone Fabric Manager Release Notes that support both CiscoMDS 9000 Family switches and Cisco Nexus 5000 Series switchesThe Cisco Fabric Manager Release Notes are available onhttpPowerlinkemccom and from the following website
httpwwwciscocomenUSpartnerproductsps10495prod_release_notes_listhtml
Technical supportThese release notes complement a Cisco documentation set EachCisco document refers to where to get help However for any itemssupplied by EMC see ldquoTroubleshooting and getting helprdquo onpage 38
Software media organization and filesFor information on related software environment and systemrequirements refer to the EMC Support Matrix on EMC Powerlink at
httpPowerlinkEMCcom
InstallationFor hardware installation information refer to the Cisco MDS HWInstallation Guides available at Ciscocom
For EMC-specific installation information refer to ldquoEnvironment andsystem requirementsrdquo on page 5 in this document
38 EMC Connectrix MDS 9000 NX-OS Release Notes
Troubleshooting and getting help
Troubleshooting and getting helpEMC support product and licensing information can be obtained asfollows
Product information mdash For documentation release notes softwareupdates or for information about EMC products licensing andservice go to the EMC Powerlink website (registration required) at
httpPowerlinkEMCcom
Technical support mdash For technical support go to EMC CustomerService on Powerlink To open a service request through Powerlinkyou must have a valid support agreement Please contact your EMCsales representative for details about obtaining a valid supportagreement or to answer any questions about your account
Copyright copy 2011 EMC Corporation All rights reserved
EMC believes the information in this publication is accurate as of its publication date The information issubject to change without notice
THE INFORMATION IN THIS PUBLICATION IS PROVIDED ldquoAS ISrdquo EMC CORPORATION MAKES NOREPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION INTHIS PUBLICATION AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OFMERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Use copying and distribution of any EMC software described in this publication requires an applicablesoftware license
For the most up-to-date regulatory document for your product line go to the Technical Documentation andAdvisories section on EMC Powerlink
For the most up-to-date listing of EMC product names see EMC Corporation Trademarks on EMCcom
All other trademarks used herein are the property of their respective owners
2 EMC Connectrix MDS 9000 NX-OS Release Notes
Revision history
Revision history
The following table presents the revision history of this document
Product descriptionThank you for purchasing an MDS 9000 multilayer fabric director orswitch The information contained in this document is a supplementto the MDS 9000 documentation that can be found on wwwciscocomReaders familiar with standard EMCreg release notes may notice thatthe organization of this document is somewhat different than they areused to Take the time to familiarize yourself with the informationprovided
Readers will find information from the original Cisco release notesfor NX-OS and annotations in the technical section including CallHome capability zoning and configuration parameters
As always in an EMC environment refer to the EMC Support Matrixavailable through E-Labtrade Interoperability Navigator athttpelabnavigatorEMCcom for the latest information onsupported configurations
The answers to many MDS 9000 related questions can be found in theEMC Knowledgebase located at
httpPowerlinkEMCcom
The Connectrixreg MDS 9000 Family of multilayer directors and fabricswitches offers intelligent fabric-switching services that realizemaximum performance while ensuring high reliability levels Theycombine robust and flexible hardware architecture with multiplelayers of network and storage management intelligence This
Revision Date Description
50(4b) February 4 2011 Bug fixes
50(4) November 8 2010 Bug fixes
50(1a) September 28 2010 VMAX FCIP write acceleration
50(1a) May 28 2010 VMAX limitation changes
50(1a) April 12 2010 New features enhancements and bug fixes
3
New features and changes
EMC Connectrix MDS 9000 NX-OS Release Notes
powerful combination enables highly available scalable storagenetworks that provide advanced security and unified managementfeatures These release notes provide the most up-to-date informationon new features and changes
New features and changesCisco NX-OS Release 50(4b) is a maintenance release containing bugfixes There are no new features
Generation 1 Hardware support discontinuedNX-OS Release 50(4b) does not support the following Generation 1modules
DS-X9302-14K9 - 142-port Multiprotocol Services(MPS-142)Module
DS-X9016 16-port 1- 2-Gbps Fibre Channel Switching Module
DS-X9032 32-port 1- 2-Gbps Fibre Channel Switching Module
DS-X9032-SSM 32-port Storage Services Module (SSM)
Generation 1 modules should be removed from a switch chassisbefore the installation of NX-OS 50(4b) begins
In addition NX-OS Release 50(4b) does not support the MDS 9216iswitch
Unsupported featuresThe following features are not currently supported in EMCenvironments The list is inclusive of past releases
Trunking F ports and trunking F port channels are not supportedon the following MDS 9000 components
bull DS-C9134-K9 Cisco MDS 9134 Multilayer Fabric Switch ifNPIV is enabled and the switch is used as the NPV coreswitch
bull DS-C9124-K9 Cisco MDS 9124 Multilayer Fabric Switch if NPIV is enabled and the switch is used as the NPV core switch
1 gigabit attach on 8 gigabit Cisco fibre channel line-cards Advanced Encryption Standard (iSCSI only)
4 EMC Connectrix MDS 9000 NX-OS Release Notes
Fixed problems
Boot over SAN is not supported with IVR NAT Caching Services Module Cisco Call Home Cisco MDS Data Mobility Manager (DMM) for the Cisco MDS
9000 Common Information Model Fabric Binding on any McData switch is not supported for Interop
mode four Fabric-Device Management Interface Installation of the 9513 into the EC-1500 cabinet Installation of the 9124 into the EC-1700-C abinet No heterogeneous fabrics supported with SME No disk encryption supported with SME IPSEC iSCSI 16 and 32 port cards are not supported in a 9222i IPsec with Ipv6 Tunneling (IPv4 and v6) is not supported on the same interface iSNS Cloud Discovery LUN Zoning in Fabric NPV on any stand-alone switches Offline data restore tool Proxy Initiator (limited to 1800) Read-Only Zones Storage Management Initiative Specification (SMI-S) 110
support Transceiver and Calibration Information Trespass support VRRP TACACS is not supported for switch-to-switch authentication NDMP backup with IOA is not supported at this time Secure Erase
Note To obtain the most up-to-date information on EMC supportedconfigurations reference the most current release notes available athttpPowerlinkEMCcom and the EMC Support Matrix available throughE-Lab Interoperability Navigator at httpelabnavigatorEMCcom
Fixed problemsCisco-specific caveats for resolved problems can be found in theCisco release-noted documentation with the equivalent firmwarelevel at the following Cisco website
5
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
httpwwwciscocomenUSpartnerproductsps10495prod_release_notes_listhtml
Note Cisco makes all release notes past and present available on thiswebsite
Environment and system requirementsThis section describes the system requirements for MDS NX-OSRelease 50(4b) and includes the following topics
Hardware Supported and Minimum Software Required Determining the Software Version Upgrade Prerequisites Software Upgrade Mechanisms Image Upgrade Matrix Best Practices Maximum ports per Chassis
Telco 2 post racksNote that the 9509 and 9513 should not be used in a 2 post Telco rackdue to weight considerations Refer to the Cisco MDS 9000 HardwareInstallation Guides on httpwwwciscocom for more information
EC-1700 configuration informationConfiguration information appears in the Connectrix EC-1700 CabinetInstallation and Setup Manual on the EMC Powerlinkreg website
Note Currently only the MDS 9509 and 9513 are supported in the EC-1700-Ccabinet The MDS 9124 is not supported in the EC-1700-C
8Gb Power RequirementsEven though Cisco director class models may operate at 100 to 240VAC in configurations consisting of 8 Gb modules 200-240 VAC ishighly recommended Operating at lower voltages will decrease thenumber of modules that may be installed in your chassis
6 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
For more information on power requirements please refer toAppendix C of the Cisco MDS 9500 Series Hardware Installation Guide
Hardware and software componentsEMC supported hardware and software modules are listed in CiscoNX-OS 50(4b) release notes located on the Cisco web site
Note Table 1 lists the MDS 9000 Family software and hardware componentsthat are not supported by EMC as well as the comparable NX-OS partnumbers
For older NX-OS part numbers see prior existing versions of SAN OSrelease notes
Table 1 MDS 9000 Family software and hardware modules not supported(page 1 of 2)
Component EMC part number Description Applicable products
Service modules DS-X9304-18FK9 18-port Fibre Channel4-port GigabitEthernet Multiservice FIPS (MSFM-184)module
MDS 9500 Series and9200 Series
Optics DS-X2-FC10G-ER X2SC optics 10-Gbps Fibre Channel forExtended Reach (40 km)
MDS 9500 Series and9200 Series exceptfor the MDS 9216
DS-X2-E10G-SR X2SC optics 10-Gbps Ethernet for ShortReach
DS-X2-FC10G_CX4 X2CX-4 optics 10-Gbps Fibre Channelcopper
LC-type fiber-optic SFP DS-SFP-GE-T 1-Gbps Ethernet SFP MDS 9000 Family
CWDM DS-CWDM-xxxx Gigabit Ethernet and 4-Gbps FibreChannel SFP LC interface xxxx nmwhere xxxx = 1470 1490 1510 15301550 1570 1590 or 1610 nm
DS-CWDM-MUX-4 Adddrop multiplexer for four CWDMwavelengths
DS-CWDM-MUX-8 Adddrop multiplexer for eight CWDMwavelengths
DS-CWDMCHASSIS Two slot chassis for CWDM adddropmultiplexers
7
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Note EMC personnel can obtain a complete list of Cisco part numbers fromthe Product Support Bulletins available under the ProductTechnicalInformation section of the EMC Global Services website athttpwwwcsisusEMCcomMyGSiVisitURLaspurl=10137
Support for the Generation 3 ModulesThe MDS 9513 Director requires Cisco MDS NX-OS 41(1b) or laterand the MDS 9513 Fabric 2 modules to support the MDS 9000 48-port8-Gbps Fibre Channel module and the MDS 9000 24-port 8-GbpsFibre Channel module
The MDS 9513 Director requires Cisco MDS NX-OS 41(1b) or laterbut does not require the MDS 9513 Fabric 2 modules to support theMDS 9000 444-port 8-Gbps Host-optimized Fibre Channel module
The MDS 9509 Director and the MDS 9506 Director also support theGeneration 3 8-Gbps modules The switches require Supervisor-2modules and Cisco MDS NX-OS 41(1b) or above to support theGeneration 3 8-Gbps modules
For information on the tasks associated with readying the MDS 9500Series to support Generation 3 8-Gbps Fibre Channel switchingmodules refer to the Migrating to Generation 3 Modules appendix inthe Cisco MDS 9500 Series Hardware Installation Guide It presents anoverview of the Generation 3 8-Gbps modules provides usageguidelines for the modules and describes three procedures formigrating hardware and upgrading software to enable use of thesemodules in an MDS 9513 Director
For information on replacing the MDS 9513 Fabric 1 modules withFabric 2 modules refer to the Migrating to Generation 3 Modulesappendix in the Cisco MDS 9500 Series Hardware Installation Guide Itprovides information on installing new Fabric 2 modules while
Port analyzer adapter DS-PAA-2 DS-PAA A standalone Fibre Channel-to-Ethernetadapter that allows for simple transparentanalysis of Fibre Channel traffic in aswitched fabric
MDS 9000 Family
Table 1 MDS 9000 Family software and hardware modules not supported(page 2 of 2)
Component EMC part number Description Applicable products
8 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
running NX-OS Release 4x and SAN-OS Release 3x It also providesinformation on installing the MDS 9513 Fabric 2 modules andactivating higher bandwidth
Configuring Generation 3 and Generation 2 Switching ModulesThe Cisco MDS 9500 Multilayer Directors are designed to operatewith any combination of Cisco MDS 9000 Generation 2 andGeneration 3 modules However there are limitations to considerwhen combining the various modules and supervisors in the CiscoMDS 9500 Series platform chassis The references listed in this sectionprovide specific information about configurations that combinedifferent modules and supervisors
For information on configuring Generation 2 and Generation 3switching modules refer to the Configuring Generation 2 andGeneration 3 Switching Modules chapter in the Cisco MDS 9000Family CLI Configuration Guide
For information on port index availability refer to the ldquoPort IndexAvailabilityrdquo section in the Product Overview chapter of the CiscoMDS 9500 Series Hardware Installation Guide
For information on Cisco MDS 9000 hardware and softwarecompatibility refer to the EMC Support Matrix available through E-LabInteroperability Navigator (ELN) at httpelabnavigatorEMCcom
MDS 9000 Chassis and Module Support in Cisco MDS NX-OS 5xTable 2 lists the MDS hardware chassis supported by Cisco MDSNX-OS 5x
Table 2 Cisco MDS NX-OS 5x Chassis Support Matrix
Switch NX-OS 5x Support
MDS 9513 Yes
MDS 9509 Yes
MDS 9506 Yes
MDS 9222i Yes
MDS 9216i No
9
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Table 3 lists the MDS hardware modules supported by Cisco MDSNX-OS 5x
MDS 9216A No
MDS 9216 No
MDS 9148 Yes
MDS 9134 Yes
MDS 9124 Yes
MDS 9140 No
MDS 9120 No
Table 2 Cisco MDS NX-OS 5x Chassis Support Matrix
Switch NX-OS 5x Support
Table 3 Module Support Matrix for Cisco MDS NX-OS 5x (page 1 of 2)
Module DescriptionMDS 9500Series MDS 9222i
DS-X9530-SF2A-K9 MDS 9500 Supervisor-2A Module Yes NA
DS-X9530-SF2-K9 MDS 9500 Supervisor-2 Module Yes NA
DS-X9530-SF1-K9 MDS 9500 Supervisor-1 Module No NA
DS-X9224-96K9 24-port 8-Gbps Fibre Channel Switching Module Yesa No
DS-X9248-96K9 48-port 8-Gbps Fibre Channel Switching Module Yesa No
DS-X9248-48K9 444-port Host Optimized 8-Gbps Fibre ChannelSwitching Module
Yes Yes
DS-X9316-SSNK9 16-Port Storage Services Node (SSN-16) Yes Yes
DS-X9304-18K9 184-Port Multiprotocol Services Module(MSM-184)
Yes Yes
DS-X9112 12-port 4-Gbps Fibre Channel Switching Module Yes Yes
DS-X9124 24-port 4-Gbps Fibre Channel Switching Module Yes Yes
DS-X9148 48-port 4-Gbps Fibre Channel Switching Module Yes Yes
DS-X9704 4-port 10-Gbps Fibre Channel Switching Module Yes Yes
10 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Migrating from Supervisor-1 Modules to Supervisor-2 ModulesAs of Cisco MDS SAN-OS Release 30(1) the Cisco MDS 9509 and9506 Directors support both Supervisor-1 and Supervisor-2 modulesSupervisor-1 and Supervisor-2 modules cannot be installed in thesame switch except during migration Both the active and standbysupervisor modules must be of the same type either Supervisor-1 orSupervisor-2 modules For Cisco MDS 9513 Directors bothsupervisor modules must be Supervisor-2 modules
CAUTION
Migrating your supervisor modules is a disruptive operation
Note Migrating from Supervisor-2 modules to Supervisor-1 modules is not supported
To migrate from a Supervisor-1 module to a Supervisor-2 module refer to the step-by-step instructions in the Cisco MDS 9000 NX-OS Release 41(x) and SAN-OS 3(x) Software Upgrade and Downgrade Guide
DS-X9302-14K9 142-port Multiprotocol Services (MPS-142)Module
No No
DS-X9016 16-port 1- 2-Gbps Fibre Channel SwitchingModule
No No
DS-X9032 32-port 1- 2-Gbps Fibre Channel SwitchingModule
No No
DS-X9032-SSM 32-port Storage Services Module (SSM) No No
DS-X9308-SMIP 8-port 1- 2-Gbps IP Switching Module No No
DS-X9304-SMIP 4-port 1- 2-Gbps IP Switching Module No No
a Requires DS-13SLT-FAB2 in the MDS 9513
Table 3 Module Support Matrix for Cisco MDS NX-OS 5x (page 2 of 2)
Module DescriptionMDS 9500Series MDS 9222i
11
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Software Download ProcessUse the software download procedure to upgrade to a later versionor downgrade to an earlier version of an operating system Thissection describes the software download process for the Cisco MDSNX-OS software and includes the following topics
ldquoDetermining the Software Versionrdquo on page 11
ldquoDownloading Softwarerdquo on page 11
ldquoSelecting the Correct Software Image for an MDS 9100 SeriesSwitchrdquo on page 12
ldquoSelecting the Correct Software Image for an MDS 9200 SeriesSwitchrdquo on page 13
ldquoSelecting the Correct Software Image for an MDS 9500 SeriesSwitchrdquo on page 13
Determining the Software VersionTo determine the version of Cisco MDS NX-OS or SAN-OS softwarecurrently running on a Cisco MDS 9000 Family switch using the CLIlog in to the switch and enter the show version EXEC command
To determine the version of Cisco MDS NX-OS or SAN-OS softwarecurrently running on a Cisco MDS 9000 Family switch using theFabric Manager view the Switches tab in the Information pane locatethe switch using the IP address logical name or WWN and check itsversion in the Release column
Note EMC strongly recommends that you use the latest qualified softwarerelease for all MDS 9000 Family products Refer to the EMC Support Matrixavailable through E-Lab Interoperability Navigator (ELN) athttpelabnavigatorEMCcom for the latest information on qualifiedfirmware revisions
Downloading SoftwareThe Cisco MDS NX-OS software is designed for mission-critical highavailability environments To realize the benefits of nondisruptiveupgrades on the Cisco MDS 9500 Directors we highly recommendthat you install dual supervisor modules
12 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Before performing upgrades submit all requested changes to theEMC Global Services CCA change control process so that anypotential operating environment impacts can be analyzedbeforehand
EMC personnel should also refer to the Connectrix MDS 9000 FamilySoftware Image Upgrade Instructions for a complete list of prerequisitesThis document is available on the Global Services websitehttpwwwcsisusEMCcom under Application Download AreaESN Product Information Connectrix MDS 9000 Family EMCpersonnel can download the Software Images from the GlobalServices website httpwwwcsisusEMCcom under ApplicationDownload Area ESN Product Information Connectrix MDS 9000Family
See the following sections in this release note for details on how youcan nondisruptively upgrade your Cisco MDS 9000 switch Issuingthe install all command from the CLI or using Fabric Manager toperform the downgrade enables the compatibility check The checkindicates if the upgrade can happen nondisruptively or disruptivelydepending on the current configuration of your switch and thereason
Compatibility check is doneModule bootable Impact Install-type Reason------ -------- -------------- ------------ ------
1 yes non-disruptive rolling2 yes disruptive rolling Hitless upgrade is not supported3 yes disruptive rolling Hitless upgrade is not supported4 yes non-disruptive rolling5 yes non-disruptive reset6 yes non-disruptive reset
Selecting the Correct Software Image for an MDS 9100 Series SwitchThe system and kickstart image that you use for an MDS 9100 seriesswitch depends on which switch you use as shown in Table 4
Table 4 Software Images for MDS 9100 Series Switches
Cisco MDS 9100 Series Switch Type Naming Convention
9124 and 9134 Filename begins with m9100-s2ek9
9148 Filename begins with m9100-s3ek9
13
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Selecting the Correct Software Image for an MDS 9200 Series SwitchThe system and kickstart image that you use for an MDS 9200 seriesswitch depends on which switch you use as shown in Table 5
Selecting the Correct Software Image for an MDS 9500 Series SwitchThe system and kickstart image that you use for an MDS 9500 Seriesswitch depends on whether the switch is based on a Supervisor-1module or a Supervisor-2 module as shown in Table 6
Use the show module command to display the type of supervisormodule in the switch The following is sample output from the showmodule command on a Supervisor 2 module
Table 5 Software Images for MDS 9200 Series Switches
Cisco MDS 9200 Series Switch Type Naming Convention
9222i Filename begins with m9200-s2ek9
Table 6 Software Images for Supervisor Type
Cisco MDS 9500 Series Switch Type Supervisor Module Type Naming Convention
9513 9509 and 9506 Supervisor-2 module Filename begins with m9500-sf2ek9
14 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
switch show moduleMod Ports Module-Type Model Status--- ----- -------------------------------- ------------------ ------------7 0 SupervisorFabric-2 DS-X9530-SF2-K9 active 8 0 SupervisorFabric-2 DS-X9530-SF2-K9 ha-standby
Upgrading Your Cisco MDS NX-OS Software ImageThis section lists the guidelines recommended for upgrading yourCisco MDS NX-OS software image and includes the following topics
ldquoGeneral Upgrading Guidelinesrdquo on page 14
ldquoDowngrading Your Cisco MDS SAN-OS Software Imagerdquo onpage 18
Note Before you begin the upgrade process review the list of chassis andmodules that NX-OS Release 50(4b) supports See the ldquoMDS 9000 Chassisand Module Support in Cisco MDS NX-OS 5xrdquo on page 8
Note For detailed instructions for performing a software upgrade usingCisco Fabric Manager see the Cisco Fabric Manager Release Notes forRelease 50(4b) which is available from the following websitehttpPowerlinkEMCcom
General Upgrading Guidelines
Note To upgrade to NX-OS Release 50(4b) you must be running NX-OSRelease 4x If you are running SAN-OS Release 32(3a) or earlier firstupgrade to SAN-OS Release 33(x) then NX-OS Release 4x and thenupgrade to NX-OS Release 50(4b)
Use the following guidelines when upgrading to Cisco MDS NX-OSRelease 5x
Install and configure dual supervisor modules
Issue the show install all impact upgrade-image CLI command todetermine if your upgrade will be nondisruptive
15
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Be aware of the impact of an upgrade on VSAN 4079 if you areupgrading from SAN-OS Release 3x to NX-OS 50(4b) See theldquoUpgrading Effect on VSAN 4079rdquo on page 17
Follow the recommended guidelines for upgrading a Cisco MDS9124 or MDS 9134 Switch as described in ldquoUpgrading a CiscoMDS 9124 or MDS 9134 switchrdquo on page 18
Take note of the affect of upgrades on MDS 9500 series switchesthat have active IOA flows as described in ldquoMDS 9500 seriesupgrades with active IOA flowsrdquo on page 18
Be aware that some features impact whether an upgrade isdisruptive or nondisruptive
bull Fibre Channel Ports Traffic on Fibre Channel ports can benondisruptively upgraded See Table 7 on page 16 for thenondisruptive upgrade path for all NX-OS and SAN-OSreleases
bull Storage Services Intelligent storage services traffic such asSANTap NASB and FC write acceleration is disruptedduring an upgrade Fibre Channel traffic is not
bull Gigabit Ethernet Ports Traffic on Gigabit Ethernet ports isdisrupted during an upgrade or downgrade This includes theGigabit Ethernet ports on the MSM-184 module and the MDS9222i switch Those nodes that are members of VSANs traversingan FCIP ISL are impacted and a fabric reconfiguration occursiSCSI initiators connected to the Gigabit Ethernet ports loseconnectivity to iSCSI targets while the upgrade is in progress
bull FICON If you have FICON enabled the upgrade path isdifferent See Table 6 on page 13
Use Table 7 to determine your nondisruptive upgrade path to Cisco MDSNX-OS Release 50(4b) find the image release number you are currentlyusing in the Current column of the table and use the path recommended
16 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Note The software upgrade information in Table 7 applies only to FibreChannel switching traffic Upgrading system software disrupts IP traffic andSSM intelligent services traffic
MDS NX-OS Release 50(4b) is not a FICON-qualified release
Table 7 Nondisruptive Upgrade Path to Cisco MDS NX-OS Release 50(4b)
Current Nondisruptive Upgrade Path
NX-OS 50(4) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 50(1a) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(7b) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(5) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(3) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(1b) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(1a) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 41(3a) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 41(1b) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
SAN-OS 33(4a) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
NX-OS 33(4) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 33(3) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 33(2) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 33(1c) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 32(3a) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 32(2c) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 32(1a) Upgrade to SAN-OS Release then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 31(3a) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 31(2) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
17
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Use Table 8 to determine your FICON nondisruptive upgrade path toCisco MDS NX-OS Release 42(7b) Find the image release numberyou are currently using in the Current Release with FICON Enabledcolumn of the table and use the path recommended
Note For more information on the FICON qualified NX-OS releases refer tothe EMC Support Matrix available through E-Lab Interoperability Navigator(ELN) at httpelabnavigatorEMCcom
Upgrading Effect on VSAN 4079If you are upgrading to NX-OS Release 50(4b) and you have notcreated VSAN 4079 the NX-OS software will automatically createVSAN 4079 and reserve it for EVFP use If VSAN 4079 is reserved forEVFP use the switchport trunk allowed vsan command will filterout VSAN 4079 from the allowed list as shown in the followingexample
switch(config-if) switchport trunk allowed vsan1-40801-40784080switch(config-if)
If you have created VSAN 4079 the upgrade to NX-OS Release50(4b) will have no affect on VSAN 4079
If you downgrade to a release of NX-OS lower than 41(x) afterNX-OS Release 50(4b) creates VSAN 4079 and reserves it for EVFPuse the VSAN will no longer be reserved
Table 8 FICON Nondisruptive Upgrade Path to NX-OS Release 42(7b)
Current Release withFICON Enabled Upgrade Path
NX-OS 42(1b) You can nondisruptively upgrade directly to NX-OS Release 42(7b)
NX-OS 41(1c) You can nondisruptively upgrade directly to NX-OS Release 42(7b)
SAN-OS 33(1c) You can nondisruptively upgrade directly to NX-OS Release 42(7b)
18 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Upgrading a Cisco MDS 9124 or MDS 9134 switchIf you are upgrading from Cisco MDS SAN-OS Release 31(1) to CiscoNX-OS Release 4x before upgrading to NX-OS Release 50(4b) on aCisco MDS 9124 or MDS 9134 switch follow these guidelines
During the upgrade configuration is not allowed and the fabric isexpected to be stable
The Fabric Shortest Path First (FSPF) timers must be configured tothe default value of 20 seconds otherwise the nondisruptiveupgrade is blocked to ensure that the maximum down toim forthe control plane can be 80 seconds
If there are any CFS commits in the fabric the nondisruptiveupgrade will fail
If there is a zone server merge in progress in the fabric thenondisruptive upgrde will fail
If a service terminates the nondisruptive upgrade the showinstall all failure-reason command can display the reason thatthe nondisruptive upgrade cannot proceed
If there is not enough memory in the system to load the newimages the upgrade will be made disruptive due to insufficientresources and the user will be notified in the compativility table
MDS 9500 series upgrades with active IOA flowsWhen upgading an MDS 9500 series switch that has active IOA flowsthose flows may be interrupted during the supervisor moduleswitchover To workaround this issue you have to enablespanning-tree portfast on the interface on the catalyst connected tothe management interface of the activestandby supervisor for theinterface to come up fast without causing the cluster to lose quorum
Downgrading Your Cisco MDS SAN-OS Software ImageThis section lists the guidelines recommended for downgrading yourCisco MDS SAN-OS software image and includes the followingtopics
ldquoGeneral downgrading guidelinesrdquo on page 19
19
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
General downgrading guidelinesUse the following guidelines to nondisruptively downgrade yourCisco MDS NX-OS Release 50(4b)
Install and configure dual supervisor modules
Issue the system no acl-adjacency-sharing execute command todisable acl adjacency usage on Generation 2 and Generation 1modules If this command fails reduce the number of zones IVRzones TE ports or a combination of these in the system and issuethe command again
Disable all features not supported by the downgrade release Usethe show incompatibility system downgrade-image command todetermine what you need to disable
bull If you are running in interoperability mode two such featuresare the Reliable Commit Service and Full Zone DatabaseDistribution They can be disabled by running thesecommand in config term mode
no zone rcs enableno zoneset capability distribute full
Use the show install all impact downgrade-image command todetermine if your downgrade will be nondisruptive
Be aware that some features impact whether a downgrade isdisruptive or nondisruptive
bull Fibre Channel Ports Traffic on Fibre Channel ports can benondisruptively downgraded See Table 9 on page 20 for thenondisruptive downgrade path for all SAN-OS releases
bull Storage Services Intelligent storage services traffic such asSANTap NASB and FC write acceleration is disruptedduring a downgrade Fibre Channel traffic is not
bull Gigabit Ethernet Ports Traffic on Gigabit Ethernet ports isdisrupted during a downgrade This includes the GigabitEthernet ports on the MSM-184 module and the MDS 9222iswitch Those nodes that are members of VSANs traversing anFCIP ISL are impacted and a fabric reconfiguration occursiSCSI initiators connected to the Gigabit Ethernet ports loseconnectivity to iSCSI targets while the downgrade is inprogress
20 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
bull FICON If you have FICON enabled the downgrade path isdifferent See Table 10 on page 21
Note A downgrade from NX-OS Release 4x to SAN-OS Release 33(1c) is notsupported on MDS switches when FC-Redirect based applications such asData Mobility Manager or Storage Media Encryption are configured in thefabric if either of the following conditions are satisfied
1 A target for which FC-Redirect is configured is connected locally and thereare Generation 1 modules with ISLs configured in the switch
2 A host for which FC-redirect is configured is connected locally ona Generation 1 module
If these conditions exist remove the application configuration forthese targets and hosts before proceeding with the downgrade
Use Table 9 on page 20 to determine the nondisruptive downgradepath from Cisco NX-OS Release 50(4b) Find the NX-OS or SAN-OSimage you want to downgrade to in the To SAN-OSNX-OS Releasecolumn of the table and use the path recommended
Note The software downgrade information in Table 10 on page 21 appliesonly to Fibre Channel switching traffic Downgrading system softwaredisrupts IP and SSM intelligent services traffic
Table 9 Nondisruptive Downgrade Path from NX-OS Release 50(4b) (page 1 of2)
To SAN-OS NX-OSRelease Nondisruptive Downgrade Path
NX-OS 50(4) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 50(1a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(7b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(5) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(3) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(1b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(1a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 41(3a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
21
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Use Table 10 to determine your nondisruptive downgrade path if youhave FICON enabled from Cisco NX-OS Release 42(7b) Find the imagerelease number you are currently using in the Current Release withFICON Enabled column of the table and use the path recommended
NX-OS 41(1b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
SAN-OS 33(5a) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33())
SAN-OS 33(5) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(4a) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
NX-OS 33(4) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(3) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
NX-OS 33(2) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(1c) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 32(3a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 32(x)
SAN-OS 32(2c) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 32(x)
SAN-OS 32(1a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
SAN-OS 31(3a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
SAN-OS 31(2) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
Table 9 Nondisruptive Downgrade Path from NX-OS Release 50(4b) (page 2 of2)
To SAN-OS NX-OSRelease Nondisruptive Downgrade Path
Table 10 FICON Downgrade Path from NX-OS Release 42(7b)
To SAN-OSNX-OS Release withFICON Enabled Downgrade Path
NX-OS 42(1b) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
NX-OS 41(1c) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
SAN-OS 33(1c) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
22 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Best practicesLog messages are not saved across system reboots or power outagesTherefore EMC recommends that customers configure a SyslogServer in order to redirect and capture all log messages on a remoteserver For more information please refer to the Cisco MDS 9000Family Configuration Guide available at
httpwwwciscocomenUSproductsps5989products_support_series_homehtml
Maximum ports per chassisTable 11 shows the maximum ports per chassis
a V2 indicates a 9506 or 9509 with Generation-2 Supervisors The presence of anygeneration one module in a switch will limit the maximum port count to 252This includes the 16-port 32-port 14+2 IPS4 and IPS8 cards
Known problems and limitationsFor a list of problems with this release please refer to the CiscoRelease notes located at
httpwwwciscocomenUSproductsps5989prod_release_notes_listhtml
Limitations and restrictionsThe following limitations and restrictions apply to all switches in theCisco MDS 9000 Family unless a limitation for a specific switch isstated
ldquoStorage Media Encryption (SME) limitationsrdquo on page 24
Table 11 Maximum ports per chassis
Chassis Maximum number of ports
MDS 9506-V2 192a
MDS 9509-V2 336
MDS 9513 528
23
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
ldquoSME configuration limitsrdquo on page 24
ldquoDeleting Cisco SME interfacesrdquo on page 25
ldquoCisco MDS 9124 and 9134 Multilayer fabric switchesrdquo on page 25
ldquoN-Port virtualization configuration limitsrdquo on page 25
ldquoMaximum number of zones supported in Interop Mode 4rdquo onpage 25
ldquoIPv6rdquo on page 26
ldquoIP-ACL supportrdquo on page 26
ldquoUser Rolesrdquo on page 26
ldquoUsing a RSA Version 1 Key for SSH Following an Upgraderdquo onpage 27
ldquoApplying Zone Configurations to VSAN 1rdquo on page 27
ldquoInterVSAN Routingrdquo on page 28
ldquoRSPAN Traffic Not Supported on CTS Ports on 8-GbpsSwitching Modulesrdquo on page 28
ldquoIO Accelerator Feature Limitationsrdquo on page 28
ldquoSupport for FCIP Compression Modesrdquo on page 28
ldquoSaving Copies of the Running Kickstart and System Imagesrdquo onpage 29
ldquoConfiguring Buffer Credits on a Generation 2 or Generation 3Modulerdquo on page 29
ldquoStorage services module power budgetrdquo on page 29
ldquoiSCSI proxy initiator in Celerra HighRoad environmentsrdquo onpage 30
ldquoHPUX N_port IDrdquo on page 30
ldquoInteroperability limitationsrdquo on page 31
ldquoNASBrdquo on page 31
ldquoReserved VSAN Range and Isolated VSAN Range Guidelinesrdquoon page 31
ldquoSymmetrix VMax limitationsrdquo on page 32
ldquoStorage Applications on the MSM-184rdquo on page 32
ldquoDowngrading with fport-channel-trunk enabledrdquo on page 32
ldquoLDAP Authenticationrdquo on page 33
24 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
ldquoMDS-9148 limitationsrdquo on page 33
Storage Media Encryption (SME) limitationsAn SME node can only belong to one cluster Adding the node tomore than one cluster will cause problems
Currently there is no prevention or warning in place when an attemptis made to add a node to multiple clusters
SME configuration limitsTable 12 lists the SME configuration limits for this release
Table 12 SME configuration limits
Configuration Limits
Number of switches in the fabric 10
Number of clusters per switch 1
Switches in a cluster 4
Fabrics in a cluster 2
Modules in a switch 11
Cisco MSM-184 modules in a cluster 32
Initiator-Target-LUNs (ITLs) 1024
LUNs behind a target 32
Host and target ports in a cluster 128
Number of hosts per target 128
Tape backup groups per cluster 2
Volume groups in a tape backup group 4
Cisco Key Management Center ( of keys) 32K
Targets per switch that can be FC-redirected 32
25
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Deleting Cisco SME interfacesA Cisco SME interface can be deleted from the cluster only after theinterface is administratively shut-down and all related tasksassociated with the interface shut-down are complete
Cisco MDS 9124 and 9134 Multilayer fabric switchesThe Cisco MDS 9124 and 9134 Multilayer fabric switches do notsupport the following Cisco MDS SAN-OS features
IVR Remote Span Translative loop support FCCmdash no generation quench reaction only
In addition the following features have these limits
VSANs mdash 16 maximum SPAN mdash 1 session maximum
N-Port virtualization configuration limitsThe NPV features have maximum configuration limits Table 13shows the verified and maximum limits for the NPV switchesrunning NX-OS Release 5x
Maximum number of zones supported in Interop Mode 4In interop mode 4 the maximum number of zones that is supportedin an active zone set is 2047 due to limitations in the connectedvendor switch When IVR is used in interop mode 4 the maximumnumber of zones supported including IVR zones in the active zoneset is 2047 The limit for the maximum number of IVR zones perVSAN is 250 zones (two members per zone)
Table 13 NPV features limitations
Feature Verified limits Maximum limits
FLOGIs or F Disc per NPV port group 114 114
NPV switches per NPV core switch 105 105
FLOGIs per line card on NPV core switch 400 400
26 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
IPv6The management port on Cisco MDS switches supports oneuser-configured IPv6 address but does not supportauto-configuration of an IPv6 address
IP-ACL supportDo not apply IP-ACLs to only one member of a PortChannel groupApply IP-ACLs to the entire channel group
If IP-ACLs are already configured in a Gigabit Ethernet interface youcannot add this interface to a Ethernet PortChannel group
Refer to the Cisco MDS 9000 Family Configuration Guide
User RolesIn SAN-OS Release 33(x) and earlier when a user belongs to a rolewhich has a VSAN policy set to Deny and the role allows access to aspecific set of VSANs (for example 1 through 10) the user isrestricted from performing the configuration clear execute anddebug commands which had a VSAN parameter outside thisspecified set Beginning with NX-OS Release 41(1b) these users arestill prevented from performing configuration clear execute anddebug commands as before however they are allowed to performshow commands for all VSANs The ability to execute the showcommand addresses the following
In a network environment users often need to view informationin other VSANs even though they do not have permission tomodify configurations in those VSANs
This behavior makes Cisco MDS 9000 Series switches consistentwith other Cisco products such as Cisco Nexus 7000 Seriesswitches that exhibit the same behavior for those roles (whenthey apply to the VLAN policy)
27
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Using a RSA Version 1 Key for SSH Following an UpgradeFor security reasons NX-OS Release 42(x) and higher does notsupport RSA version 1 keys As a result if you upgrade from anearlier version that did support RSA version 1 keys and you hadconfigured a RSA version 1 key for SSH then you will not be able tolog in through SSH following the upgrade
If you have a RSA version 1 key configured for SSH beforeupgrading to NX-OS Release 42(x) or higher follow these steps
1 Disable SSH
2 Create RSA version 2 DSA keys
3 Enable SSH
4 Delete any RSA version 1 keys on any remote SSH clients andreplace the version 1 keys with the new version 2 keys from theswitch
Proceed with the upgrade to NX-OS Release 42(x) or higher
If you upgrade before disabling SSH and creating RSA version 2 keysfollow these steps
1 Open a Telnet session and log in through the console
2 Issue the no feature ssh command to disable SSH
3 Issue the ssh key rsa 1024 command to create RSA version 2 keys
4 Issue the feature ssh command to enable SSH
Applying Zone Configurations to VSAN 1In the setup script you can configure system default values for thedefault-zone to be permit or deny and you can configure defaultvalues for the zone distribution method and for the zone mode
These default settings are applied when a new VSAN is createdHowever the settings will not take effect on VSAN 1 because it existsprior to running the setup script Therefore when you need thosesettings for VSAN 1 you must explicitly issue the followingcommands
zone default-zone permit vsan 1 zoneset distribute full vsan 1 zone mode enhanced vsan 1
28 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
InterVSAN RoutingWhen using InterVSAN Routing (IVR) it is recommended to enableCisco Fabric Services (CFS) on all IVR-enabled switches Failure to doso may cause mismatched active zone sets if an error occurs duringzone set activation
RSPAN Traffic Not Supported on CTS Ports on 8-Gbps Switching ModulesAn inter-switch link (ISL) that is enabled for Cisco TrustSec (CTS)encryption must be brought up in non-CTS mode to support remoteSPAN (RSPAN) traffic on the following modules
DS-X9248-96K9 Cisco MDS 9000 48-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9224-96K9 Cisco MDS 9000 24-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9248-48K9 Cisco MDS 9000 444-Port Host-Optimized8-Gbps Fibre Channel Switching Module
If the ISL link is brought up with CTS enabled random packets dropsof both RSPAN traffic and normal traffic will occur on the receiverport switch
IO Accelerator Feature LimitationsIOA does not support the following NX-OS features
IVR flows
Devices with NPV and NPIV enabled
F port trunking
bull F port channeling
Support for FCIP Compression ModesIn Cisco NX-OS Release 42(1b) and higher FCIP compression mode 1and compression mode 3 are not supported on the Cisco MSM-184module and on the SSN-16 module
29
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Saving Copies of the Running Kickstart and System ImagesAfter you upgrade to MDS NX-OS Release 42(1b) or higher you arenot allowed to delete rename move or overwrite the kickstart andsystem images that are in the current system bootvar settings on anactive or standby MDS Supervisor-2 module on any Cisco MDS 9500Series switch This restriction does not apply to the integratedsupervisor module on the MDS 9200 and MDS 9100 series switches
Configuring Buffer Credits on a Generation 2 or Generation 3 ModuleWhen you configure port mode to auto or E on a Generation 2module one of the ports will not come up for the followingconfiguration
Port Mode auto or E for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E on a Generation 3module one or two of the ports will not come up for the followingconfiguration
Port Mode auto or E for the first half of the ports the second halfof the ports or for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E for all ports in the globalbuffer pool you need to reconfigure buffer credits on one or more ofthe ports The total number of buffer credits configured for all theports in the global buffer pool should be reduced by 64
Storage services module power budgetThe MDS 9509 does not have the power budget to run seven SSMcards EMC recommends a maximum of four SSMs in one 9509Customers wishing to use more than four SSMs in one chassis shouldrefer to the Cisco MDS 9000 documentation on the Ciscocom websiteto validate that there is enough power available for their desiredconfiguration
30 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Note Upgrading to the 3000 watt power supplies will alleviate thiscondition
iSCSI proxy initiator in Celerra HighRoad environmentsEMC supports the iSCSI proxy initiator feature in Celerrareg
HighRoadreg environments In proxy initiator mode one Fibre Channelinitiator is used for all iSCSI clients who access the switch via thesame iSCSI interface (iscsi33 for example)
The initiators will use the PWWN assigned to the iSCSI interface TheiSCSI interface to which an iSCSI client will logon to is configured inthe client and must be permitted by the virtual target configured forthat initiator
The current session environment supported on the MDS is
300 sessions per port 1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no InitialR2T=yes
Refer to the specific initiator support documentation on how to setthe parameters The implementation will not perform properly ifthese bits are not set
Refer to the MDS documentation for more information regarding theconfiguration of the iSCSI proxy initiator at the following Ciscowebsite
httpwwwciscocomenUSproducts
HPUX N_port IDThe N_port ID port value of 255 (0xFF) has special meaning forHP-UX A N_port ID (FC_ID) can not be returned from a switch thatcontains this value for the N_port ID (FC_ID) port value for a HP-UXinitiator or HP-UX target port Port ID value of 255 (0xFF) cannot be
31
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
configured for HP-UX initiator port and HP-UX target ports whenconfiguring MDS FC_IDs The port_ID value is the third byte of theFC_ID
Interoperability limitationsRefer to the EMC Support Matrix (ESM) and the EMC Networked Storage Topology Guide for modes of operation and caveats
NASBThe NASB feature requires that the backup application load the tapedrive with a compatible tape cartridge prior to configuring NASB inthe backup VSAN
Reserved VSAN Range and Isolated VSAN Range GuidelinesOn an NPV switch with a trunking configuration on any interface or ona regular switch where the feature fport_channel_trunk command hasbeen issued to enable the F PortChannel feature follow theseconfiguration guidelines for reserved VSANs and the isolated VSAN
bull If trunk mode is on for any of the interfaces or NP PortChannelis up the reserved VSANs are 3040 to 4078 and they are notavailable for user configuration
bull The Exchange Virtual Fabric Protocol (EVFP) isolated VSAN is4079 and it is not available for user configuration
bull VSAN 4079 will be impacted by an upgrade to NX-OS Release42(3) depending on whether or not VSAN 4079 was createdprior to the upgrade See theldquoUpgrading Effect on VSAN 4079rdquoon page 17
The following VSAN IDs are assigned in the Fibre Channel Framingand Signaling (FC-FS) interface standard
VF_ID Value Value Description
00h Do not use as a Virtual FabricIdentifier
001h EFFh Available as a Virtual FabricIdentifier
F00h FEEh Reserved
32 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Symmetrix VMax limitationsAt the time of this writing the following features are not supportedfor use with the Symmetrix VMax
FCIP Write Acceleration
The NX-OS IOA functionality is only supported with the Q2 SREnginuity release 5874229182 or higher
For the most up to date status please refer to the current revision ofthese Release Notes on httpPowerlinkemccom and the EMCSupport Matrix available through E-Lab Interoperability Navigator (ELN) athttpelabnavigatorEMCcom
Storage Applications on the MSM-184The MDS 9000 184-Port Multiservice Module (MSM-184) does notsupport multiple concurrent storage applications Only oneapplication can run on the MSM-184 at a time
Downgrading with fport-channel-trunk enabledIf you are running MDS NX-OS Release 42(x) or higher with thefport-channel-trunk feature enabled and you downgrade to anyNX-OS 41(1x) release the installer performs a nondisruptivedowngrade even though the fport-channel-trunk feature is notsupported in NX-OS 41(1x) releases
As a result the switch is in an inconsistent state and the ports maynot function properly
FEFh Control VF-ID (see FibreChannel Link Services (FC-LS)and Fibre Channel SwitchFabric Generation 4 (FC-SW-4)standards)
FF0h FFEh Vendor specific
FFFh Do not use as a Virtual FabricIdentifier
FEFh = 4079
33
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
If you are in this state a workaround is to reboot the switch followingthe upgrade
LDAP AuthenticationThere is currently a limitation in the LDAP server configuration CLIthat prevents the use of an OU with spaces in the name Normallythese OU names could be surrounded by quotation marks howeverquotation marks are not supported by the ldap-server command
MDS-9148 limitationsThe Cisco MDS 9148 Multilayer Fabric Switch does not support thefollowing NX-OS features
Medium and Long range 4GB Agilent
IVR
Remote Span
Translative loop support
FCC - no generation quench reaction only
FC-Redirect
In addition the following features have these limits
VSANS - 31 maximum
SPAN - 1 session maximum
Technical notesThe following sections provide further information on technicalnotes
EMC Email Home for Cisco MDS switchesInstallation and Trouble shooting instructions can be found in thedocumentation located at the EMC Customer Service Internalwebsite
httpwwwcsisusemccomcsweb2esnesnhomehtmConnectrix20MDS20900020Family
34 EMC Connectrix MDS 9000 NX-OS Release Notes
Technical notes
Customers requiring installation of this solution should contact theirEMC Customer Engineer to assist with the installation and providethe documentation
Supported iSCSI sessionsThe current iSCSI session environment supported on the MDS is
300 sessions per port
1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no
InitialR2T=yes
Upgrading Cisco SAN-OSThere are several methods available for upgrading SAN-OS SoftwareEMC personnel are strongly recommended that all upgrades be doneby the Automated One-Step Upgrade using the install all
command EMC personnel should refer to the Connectrix MDS 9000Family Software Image Upgrade Instructions for a complete list ofprerequisites and instructions for performing the upgrade Thisdocument along with tftp software is available on the GlobalServices website at httpwwwcsisusEMCcom under ApplicationDownload Area ESN Product Information Connectrix MDS 9000Family
The Software Upgrade Wizard is an option for upgrades While theinstall all is the preferred method the Software Install Wizard canalso be used
Supported configuration parametersFor the most up-to-date information refer to the EMC Support Matrixavailable through E-Lab Interoperability Navigator athttpelabnavigatoremccom for the latest information onsupported configurations
35
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
Supported zoning parametersRefer to the EMC Networked Storage Topology Guide for the mostup-to-date information on supported zoning parameters
At the time these notes were published the following parameterswere supported
20 VSANs 5 Hops 2000 Unique members per physical infrastructure 1000 Zonesets per physical infrastructure 2000 Zones per physical infrastructure 1 FCIP tunnel
Supported IVR parameters IVR zone members 1000 IVR zones 1000 IVR zone sets 32 VSANS 20 IVR enabled switches 64
An RPQ can be submitted for any configurations that exceed thislimit
Managing zone changes in multiswitch fabricsZoning changes may be made through Fabric Manager or CLI Whenaccessing Fabric Manager or CLI the user does so from the point ofview of one switch That is Fabric Manager and CLI are accessed byentering the IP address of one switch in the fabric
When zoning changes are made the applicable VSAN and zone setdata is propagated to the rest of the switches in the fabric via the ISLs
When zoning changes are made to a VSAN the zone set data ispropagated to the rest of the switches in the fabric via the ISLs Bydefault only the active zone set information is relayed to all switchesin the VSAN If the user accesses the Fabric Manager and CLI fromanother switch in the fabric the new VSAN and zone set informationwill not be viewable To view the active and inactive zone set on theother switches in the fabric the user must log in to the CLI and issuea command from the EXEC prompt
36 EMC Connectrix MDS 9000 NX-OS Release Notes
Documentation
Example The following is an example of copying VSAN 1 through 20 zoningdata
CiscoMDS_name zone copy active full vsan 1-20
CiscoMDS_name conf t
Enter configuration commands one per line End with CNTL Z
CiscoMDS_name(config) zoneset distribute full vsan 1-20
CiscoMDS_name(config)
Note This command needs to be issued on all switches in the fabric one timeonly
This is a nondisruptive command After issuing the commands theuser will now see the active and inactive zone sets for the specifiedVSANs on any switch that is chosen from which to manage the fabric
After a zoning change is made save the running configuration to thestartup configuration
DocumentationSend documentation comments to mdsfeedback-doccom
Product DocumentationAs of NX-OS Release 42(1a) software configuration information isavailable in new feature-specific configuration guides for thefollowing information
System management
Interfaces
Fabric
Quality of service
Security
IP services
High availability and redundancy
37
Software media organization and files
EMC Connectrix MDS 9000 NX-OS Release Notes
The information in these new guides previously existed in the CiscoMDS 9000 Family CLI Configuration Guide That configuration guideremains available on Ciscocom and should be used for all softwarereleases prior to NX-OS Release 42(1a) Configuration guidesaddress the features introduced in or available in a particular releaseSelect and view the configuration guide that pertains to the softwareinstalled in your switch
In addition Fabric Manager information has been removed from theMDS NX-OS Release Notes (this document) and placed intostandalone Fabric Manager Release Notes that support both CiscoMDS 9000 Family switches and Cisco Nexus 5000 Series switchesThe Cisco Fabric Manager Release Notes are available onhttpPowerlinkemccom and from the following website
httpwwwciscocomenUSpartnerproductsps10495prod_release_notes_listhtml
Technical supportThese release notes complement a Cisco documentation set EachCisco document refers to where to get help However for any itemssupplied by EMC see ldquoTroubleshooting and getting helprdquo onpage 38
Software media organization and filesFor information on related software environment and systemrequirements refer to the EMC Support Matrix on EMC Powerlink at
httpPowerlinkEMCcom
InstallationFor hardware installation information refer to the Cisco MDS HWInstallation Guides available at Ciscocom
For EMC-specific installation information refer to ldquoEnvironment andsystem requirementsrdquo on page 5 in this document
38 EMC Connectrix MDS 9000 NX-OS Release Notes
Troubleshooting and getting help
Troubleshooting and getting helpEMC support product and licensing information can be obtained asfollows
Product information mdash For documentation release notes softwareupdates or for information about EMC products licensing andservice go to the EMC Powerlink website (registration required) at
httpPowerlinkEMCcom
Technical support mdash For technical support go to EMC CustomerService on Powerlink To open a service request through Powerlinkyou must have a valid support agreement Please contact your EMCsales representative for details about obtaining a valid supportagreement or to answer any questions about your account
Copyright copy 2011 EMC Corporation All rights reserved
EMC believes the information in this publication is accurate as of its publication date The information issubject to change without notice
THE INFORMATION IN THIS PUBLICATION IS PROVIDED ldquoAS ISrdquo EMC CORPORATION MAKES NOREPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION INTHIS PUBLICATION AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OFMERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Use copying and distribution of any EMC software described in this publication requires an applicablesoftware license
For the most up-to-date regulatory document for your product line go to the Technical Documentation andAdvisories section on EMC Powerlink
For the most up-to-date listing of EMC product names see EMC Corporation Trademarks on EMCcom
All other trademarks used herein are the property of their respective owners
3
New features and changes
EMC Connectrix MDS 9000 NX-OS Release Notes
powerful combination enables highly available scalable storagenetworks that provide advanced security and unified managementfeatures These release notes provide the most up-to-date informationon new features and changes
New features and changesCisco NX-OS Release 50(4b) is a maintenance release containing bugfixes There are no new features
Generation 1 Hardware support discontinuedNX-OS Release 50(4b) does not support the following Generation 1modules
DS-X9302-14K9 - 142-port Multiprotocol Services(MPS-142)Module
DS-X9016 16-port 1- 2-Gbps Fibre Channel Switching Module
DS-X9032 32-port 1- 2-Gbps Fibre Channel Switching Module
DS-X9032-SSM 32-port Storage Services Module (SSM)
Generation 1 modules should be removed from a switch chassisbefore the installation of NX-OS 50(4b) begins
In addition NX-OS Release 50(4b) does not support the MDS 9216iswitch
Unsupported featuresThe following features are not currently supported in EMCenvironments The list is inclusive of past releases
Trunking F ports and trunking F port channels are not supportedon the following MDS 9000 components
bull DS-C9134-K9 Cisco MDS 9134 Multilayer Fabric Switch ifNPIV is enabled and the switch is used as the NPV coreswitch
bull DS-C9124-K9 Cisco MDS 9124 Multilayer Fabric Switch if NPIV is enabled and the switch is used as the NPV core switch
1 gigabit attach on 8 gigabit Cisco fibre channel line-cards Advanced Encryption Standard (iSCSI only)
4 EMC Connectrix MDS 9000 NX-OS Release Notes
Fixed problems
Boot over SAN is not supported with IVR NAT Caching Services Module Cisco Call Home Cisco MDS Data Mobility Manager (DMM) for the Cisco MDS
9000 Common Information Model Fabric Binding on any McData switch is not supported for Interop
mode four Fabric-Device Management Interface Installation of the 9513 into the EC-1500 cabinet Installation of the 9124 into the EC-1700-C abinet No heterogeneous fabrics supported with SME No disk encryption supported with SME IPSEC iSCSI 16 and 32 port cards are not supported in a 9222i IPsec with Ipv6 Tunneling (IPv4 and v6) is not supported on the same interface iSNS Cloud Discovery LUN Zoning in Fabric NPV on any stand-alone switches Offline data restore tool Proxy Initiator (limited to 1800) Read-Only Zones Storage Management Initiative Specification (SMI-S) 110
support Transceiver and Calibration Information Trespass support VRRP TACACS is not supported for switch-to-switch authentication NDMP backup with IOA is not supported at this time Secure Erase
Note To obtain the most up-to-date information on EMC supportedconfigurations reference the most current release notes available athttpPowerlinkEMCcom and the EMC Support Matrix available throughE-Lab Interoperability Navigator at httpelabnavigatorEMCcom
Fixed problemsCisco-specific caveats for resolved problems can be found in theCisco release-noted documentation with the equivalent firmwarelevel at the following Cisco website
5
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
httpwwwciscocomenUSpartnerproductsps10495prod_release_notes_listhtml
Note Cisco makes all release notes past and present available on thiswebsite
Environment and system requirementsThis section describes the system requirements for MDS NX-OSRelease 50(4b) and includes the following topics
Hardware Supported and Minimum Software Required Determining the Software Version Upgrade Prerequisites Software Upgrade Mechanisms Image Upgrade Matrix Best Practices Maximum ports per Chassis
Telco 2 post racksNote that the 9509 and 9513 should not be used in a 2 post Telco rackdue to weight considerations Refer to the Cisco MDS 9000 HardwareInstallation Guides on httpwwwciscocom for more information
EC-1700 configuration informationConfiguration information appears in the Connectrix EC-1700 CabinetInstallation and Setup Manual on the EMC Powerlinkreg website
Note Currently only the MDS 9509 and 9513 are supported in the EC-1700-Ccabinet The MDS 9124 is not supported in the EC-1700-C
8Gb Power RequirementsEven though Cisco director class models may operate at 100 to 240VAC in configurations consisting of 8 Gb modules 200-240 VAC ishighly recommended Operating at lower voltages will decrease thenumber of modules that may be installed in your chassis
6 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
For more information on power requirements please refer toAppendix C of the Cisco MDS 9500 Series Hardware Installation Guide
Hardware and software componentsEMC supported hardware and software modules are listed in CiscoNX-OS 50(4b) release notes located on the Cisco web site
Note Table 1 lists the MDS 9000 Family software and hardware componentsthat are not supported by EMC as well as the comparable NX-OS partnumbers
For older NX-OS part numbers see prior existing versions of SAN OSrelease notes
Table 1 MDS 9000 Family software and hardware modules not supported(page 1 of 2)
Component EMC part number Description Applicable products
Service modules DS-X9304-18FK9 18-port Fibre Channel4-port GigabitEthernet Multiservice FIPS (MSFM-184)module
MDS 9500 Series and9200 Series
Optics DS-X2-FC10G-ER X2SC optics 10-Gbps Fibre Channel forExtended Reach (40 km)
MDS 9500 Series and9200 Series exceptfor the MDS 9216
DS-X2-E10G-SR X2SC optics 10-Gbps Ethernet for ShortReach
DS-X2-FC10G_CX4 X2CX-4 optics 10-Gbps Fibre Channelcopper
LC-type fiber-optic SFP DS-SFP-GE-T 1-Gbps Ethernet SFP MDS 9000 Family
CWDM DS-CWDM-xxxx Gigabit Ethernet and 4-Gbps FibreChannel SFP LC interface xxxx nmwhere xxxx = 1470 1490 1510 15301550 1570 1590 or 1610 nm
DS-CWDM-MUX-4 Adddrop multiplexer for four CWDMwavelengths
DS-CWDM-MUX-8 Adddrop multiplexer for eight CWDMwavelengths
DS-CWDMCHASSIS Two slot chassis for CWDM adddropmultiplexers
7
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Note EMC personnel can obtain a complete list of Cisco part numbers fromthe Product Support Bulletins available under the ProductTechnicalInformation section of the EMC Global Services website athttpwwwcsisusEMCcomMyGSiVisitURLaspurl=10137
Support for the Generation 3 ModulesThe MDS 9513 Director requires Cisco MDS NX-OS 41(1b) or laterand the MDS 9513 Fabric 2 modules to support the MDS 9000 48-port8-Gbps Fibre Channel module and the MDS 9000 24-port 8-GbpsFibre Channel module
The MDS 9513 Director requires Cisco MDS NX-OS 41(1b) or laterbut does not require the MDS 9513 Fabric 2 modules to support theMDS 9000 444-port 8-Gbps Host-optimized Fibre Channel module
The MDS 9509 Director and the MDS 9506 Director also support theGeneration 3 8-Gbps modules The switches require Supervisor-2modules and Cisco MDS NX-OS 41(1b) or above to support theGeneration 3 8-Gbps modules
For information on the tasks associated with readying the MDS 9500Series to support Generation 3 8-Gbps Fibre Channel switchingmodules refer to the Migrating to Generation 3 Modules appendix inthe Cisco MDS 9500 Series Hardware Installation Guide It presents anoverview of the Generation 3 8-Gbps modules provides usageguidelines for the modules and describes three procedures formigrating hardware and upgrading software to enable use of thesemodules in an MDS 9513 Director
For information on replacing the MDS 9513 Fabric 1 modules withFabric 2 modules refer to the Migrating to Generation 3 Modulesappendix in the Cisco MDS 9500 Series Hardware Installation Guide Itprovides information on installing new Fabric 2 modules while
Port analyzer adapter DS-PAA-2 DS-PAA A standalone Fibre Channel-to-Ethernetadapter that allows for simple transparentanalysis of Fibre Channel traffic in aswitched fabric
MDS 9000 Family
Table 1 MDS 9000 Family software and hardware modules not supported(page 2 of 2)
Component EMC part number Description Applicable products
8 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
running NX-OS Release 4x and SAN-OS Release 3x It also providesinformation on installing the MDS 9513 Fabric 2 modules andactivating higher bandwidth
Configuring Generation 3 and Generation 2 Switching ModulesThe Cisco MDS 9500 Multilayer Directors are designed to operatewith any combination of Cisco MDS 9000 Generation 2 andGeneration 3 modules However there are limitations to considerwhen combining the various modules and supervisors in the CiscoMDS 9500 Series platform chassis The references listed in this sectionprovide specific information about configurations that combinedifferent modules and supervisors
For information on configuring Generation 2 and Generation 3switching modules refer to the Configuring Generation 2 andGeneration 3 Switching Modules chapter in the Cisco MDS 9000Family CLI Configuration Guide
For information on port index availability refer to the ldquoPort IndexAvailabilityrdquo section in the Product Overview chapter of the CiscoMDS 9500 Series Hardware Installation Guide
For information on Cisco MDS 9000 hardware and softwarecompatibility refer to the EMC Support Matrix available through E-LabInteroperability Navigator (ELN) at httpelabnavigatorEMCcom
MDS 9000 Chassis and Module Support in Cisco MDS NX-OS 5xTable 2 lists the MDS hardware chassis supported by Cisco MDSNX-OS 5x
Table 2 Cisco MDS NX-OS 5x Chassis Support Matrix
Switch NX-OS 5x Support
MDS 9513 Yes
MDS 9509 Yes
MDS 9506 Yes
MDS 9222i Yes
MDS 9216i No
9
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Table 3 lists the MDS hardware modules supported by Cisco MDSNX-OS 5x
MDS 9216A No
MDS 9216 No
MDS 9148 Yes
MDS 9134 Yes
MDS 9124 Yes
MDS 9140 No
MDS 9120 No
Table 2 Cisco MDS NX-OS 5x Chassis Support Matrix
Switch NX-OS 5x Support
Table 3 Module Support Matrix for Cisco MDS NX-OS 5x (page 1 of 2)
Module DescriptionMDS 9500Series MDS 9222i
DS-X9530-SF2A-K9 MDS 9500 Supervisor-2A Module Yes NA
DS-X9530-SF2-K9 MDS 9500 Supervisor-2 Module Yes NA
DS-X9530-SF1-K9 MDS 9500 Supervisor-1 Module No NA
DS-X9224-96K9 24-port 8-Gbps Fibre Channel Switching Module Yesa No
DS-X9248-96K9 48-port 8-Gbps Fibre Channel Switching Module Yesa No
DS-X9248-48K9 444-port Host Optimized 8-Gbps Fibre ChannelSwitching Module
Yes Yes
DS-X9316-SSNK9 16-Port Storage Services Node (SSN-16) Yes Yes
DS-X9304-18K9 184-Port Multiprotocol Services Module(MSM-184)
Yes Yes
DS-X9112 12-port 4-Gbps Fibre Channel Switching Module Yes Yes
DS-X9124 24-port 4-Gbps Fibre Channel Switching Module Yes Yes
DS-X9148 48-port 4-Gbps Fibre Channel Switching Module Yes Yes
DS-X9704 4-port 10-Gbps Fibre Channel Switching Module Yes Yes
10 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Migrating from Supervisor-1 Modules to Supervisor-2 ModulesAs of Cisco MDS SAN-OS Release 30(1) the Cisco MDS 9509 and9506 Directors support both Supervisor-1 and Supervisor-2 modulesSupervisor-1 and Supervisor-2 modules cannot be installed in thesame switch except during migration Both the active and standbysupervisor modules must be of the same type either Supervisor-1 orSupervisor-2 modules For Cisco MDS 9513 Directors bothsupervisor modules must be Supervisor-2 modules
CAUTION
Migrating your supervisor modules is a disruptive operation
Note Migrating from Supervisor-2 modules to Supervisor-1 modules is not supported
To migrate from a Supervisor-1 module to a Supervisor-2 module refer to the step-by-step instructions in the Cisco MDS 9000 NX-OS Release 41(x) and SAN-OS 3(x) Software Upgrade and Downgrade Guide
DS-X9302-14K9 142-port Multiprotocol Services (MPS-142)Module
No No
DS-X9016 16-port 1- 2-Gbps Fibre Channel SwitchingModule
No No
DS-X9032 32-port 1- 2-Gbps Fibre Channel SwitchingModule
No No
DS-X9032-SSM 32-port Storage Services Module (SSM) No No
DS-X9308-SMIP 8-port 1- 2-Gbps IP Switching Module No No
DS-X9304-SMIP 4-port 1- 2-Gbps IP Switching Module No No
a Requires DS-13SLT-FAB2 in the MDS 9513
Table 3 Module Support Matrix for Cisco MDS NX-OS 5x (page 2 of 2)
Module DescriptionMDS 9500Series MDS 9222i
11
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Software Download ProcessUse the software download procedure to upgrade to a later versionor downgrade to an earlier version of an operating system Thissection describes the software download process for the Cisco MDSNX-OS software and includes the following topics
ldquoDetermining the Software Versionrdquo on page 11
ldquoDownloading Softwarerdquo on page 11
ldquoSelecting the Correct Software Image for an MDS 9100 SeriesSwitchrdquo on page 12
ldquoSelecting the Correct Software Image for an MDS 9200 SeriesSwitchrdquo on page 13
ldquoSelecting the Correct Software Image for an MDS 9500 SeriesSwitchrdquo on page 13
Determining the Software VersionTo determine the version of Cisco MDS NX-OS or SAN-OS softwarecurrently running on a Cisco MDS 9000 Family switch using the CLIlog in to the switch and enter the show version EXEC command
To determine the version of Cisco MDS NX-OS or SAN-OS softwarecurrently running on a Cisco MDS 9000 Family switch using theFabric Manager view the Switches tab in the Information pane locatethe switch using the IP address logical name or WWN and check itsversion in the Release column
Note EMC strongly recommends that you use the latest qualified softwarerelease for all MDS 9000 Family products Refer to the EMC Support Matrixavailable through E-Lab Interoperability Navigator (ELN) athttpelabnavigatorEMCcom for the latest information on qualifiedfirmware revisions
Downloading SoftwareThe Cisco MDS NX-OS software is designed for mission-critical highavailability environments To realize the benefits of nondisruptiveupgrades on the Cisco MDS 9500 Directors we highly recommendthat you install dual supervisor modules
12 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Before performing upgrades submit all requested changes to theEMC Global Services CCA change control process so that anypotential operating environment impacts can be analyzedbeforehand
EMC personnel should also refer to the Connectrix MDS 9000 FamilySoftware Image Upgrade Instructions for a complete list of prerequisitesThis document is available on the Global Services websitehttpwwwcsisusEMCcom under Application Download AreaESN Product Information Connectrix MDS 9000 Family EMCpersonnel can download the Software Images from the GlobalServices website httpwwwcsisusEMCcom under ApplicationDownload Area ESN Product Information Connectrix MDS 9000Family
See the following sections in this release note for details on how youcan nondisruptively upgrade your Cisco MDS 9000 switch Issuingthe install all command from the CLI or using Fabric Manager toperform the downgrade enables the compatibility check The checkindicates if the upgrade can happen nondisruptively or disruptivelydepending on the current configuration of your switch and thereason
Compatibility check is doneModule bootable Impact Install-type Reason------ -------- -------------- ------------ ------
1 yes non-disruptive rolling2 yes disruptive rolling Hitless upgrade is not supported3 yes disruptive rolling Hitless upgrade is not supported4 yes non-disruptive rolling5 yes non-disruptive reset6 yes non-disruptive reset
Selecting the Correct Software Image for an MDS 9100 Series SwitchThe system and kickstart image that you use for an MDS 9100 seriesswitch depends on which switch you use as shown in Table 4
Table 4 Software Images for MDS 9100 Series Switches
Cisco MDS 9100 Series Switch Type Naming Convention
9124 and 9134 Filename begins with m9100-s2ek9
9148 Filename begins with m9100-s3ek9
13
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Selecting the Correct Software Image for an MDS 9200 Series SwitchThe system and kickstart image that you use for an MDS 9200 seriesswitch depends on which switch you use as shown in Table 5
Selecting the Correct Software Image for an MDS 9500 Series SwitchThe system and kickstart image that you use for an MDS 9500 Seriesswitch depends on whether the switch is based on a Supervisor-1module or a Supervisor-2 module as shown in Table 6
Use the show module command to display the type of supervisormodule in the switch The following is sample output from the showmodule command on a Supervisor 2 module
Table 5 Software Images for MDS 9200 Series Switches
Cisco MDS 9200 Series Switch Type Naming Convention
9222i Filename begins with m9200-s2ek9
Table 6 Software Images for Supervisor Type
Cisco MDS 9500 Series Switch Type Supervisor Module Type Naming Convention
9513 9509 and 9506 Supervisor-2 module Filename begins with m9500-sf2ek9
14 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
switch show moduleMod Ports Module-Type Model Status--- ----- -------------------------------- ------------------ ------------7 0 SupervisorFabric-2 DS-X9530-SF2-K9 active 8 0 SupervisorFabric-2 DS-X9530-SF2-K9 ha-standby
Upgrading Your Cisco MDS NX-OS Software ImageThis section lists the guidelines recommended for upgrading yourCisco MDS NX-OS software image and includes the following topics
ldquoGeneral Upgrading Guidelinesrdquo on page 14
ldquoDowngrading Your Cisco MDS SAN-OS Software Imagerdquo onpage 18
Note Before you begin the upgrade process review the list of chassis andmodules that NX-OS Release 50(4b) supports See the ldquoMDS 9000 Chassisand Module Support in Cisco MDS NX-OS 5xrdquo on page 8
Note For detailed instructions for performing a software upgrade usingCisco Fabric Manager see the Cisco Fabric Manager Release Notes forRelease 50(4b) which is available from the following websitehttpPowerlinkEMCcom
General Upgrading Guidelines
Note To upgrade to NX-OS Release 50(4b) you must be running NX-OSRelease 4x If you are running SAN-OS Release 32(3a) or earlier firstupgrade to SAN-OS Release 33(x) then NX-OS Release 4x and thenupgrade to NX-OS Release 50(4b)
Use the following guidelines when upgrading to Cisco MDS NX-OSRelease 5x
Install and configure dual supervisor modules
Issue the show install all impact upgrade-image CLI command todetermine if your upgrade will be nondisruptive
15
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Be aware of the impact of an upgrade on VSAN 4079 if you areupgrading from SAN-OS Release 3x to NX-OS 50(4b) See theldquoUpgrading Effect on VSAN 4079rdquo on page 17
Follow the recommended guidelines for upgrading a Cisco MDS9124 or MDS 9134 Switch as described in ldquoUpgrading a CiscoMDS 9124 or MDS 9134 switchrdquo on page 18
Take note of the affect of upgrades on MDS 9500 series switchesthat have active IOA flows as described in ldquoMDS 9500 seriesupgrades with active IOA flowsrdquo on page 18
Be aware that some features impact whether an upgrade isdisruptive or nondisruptive
bull Fibre Channel Ports Traffic on Fibre Channel ports can benondisruptively upgraded See Table 7 on page 16 for thenondisruptive upgrade path for all NX-OS and SAN-OSreleases
bull Storage Services Intelligent storage services traffic such asSANTap NASB and FC write acceleration is disruptedduring an upgrade Fibre Channel traffic is not
bull Gigabit Ethernet Ports Traffic on Gigabit Ethernet ports isdisrupted during an upgrade or downgrade This includes theGigabit Ethernet ports on the MSM-184 module and the MDS9222i switch Those nodes that are members of VSANs traversingan FCIP ISL are impacted and a fabric reconfiguration occursiSCSI initiators connected to the Gigabit Ethernet ports loseconnectivity to iSCSI targets while the upgrade is in progress
bull FICON If you have FICON enabled the upgrade path isdifferent See Table 6 on page 13
Use Table 7 to determine your nondisruptive upgrade path to Cisco MDSNX-OS Release 50(4b) find the image release number you are currentlyusing in the Current column of the table and use the path recommended
16 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Note The software upgrade information in Table 7 applies only to FibreChannel switching traffic Upgrading system software disrupts IP traffic andSSM intelligent services traffic
MDS NX-OS Release 50(4b) is not a FICON-qualified release
Table 7 Nondisruptive Upgrade Path to Cisco MDS NX-OS Release 50(4b)
Current Nondisruptive Upgrade Path
NX-OS 50(4) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 50(1a) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(7b) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(5) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(3) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(1b) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(1a) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 41(3a) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 41(1b) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
SAN-OS 33(4a) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
NX-OS 33(4) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 33(3) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 33(2) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 33(1c) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 32(3a) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 32(2c) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 32(1a) Upgrade to SAN-OS Release then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 31(3a) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 31(2) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
17
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Use Table 8 to determine your FICON nondisruptive upgrade path toCisco MDS NX-OS Release 42(7b) Find the image release numberyou are currently using in the Current Release with FICON Enabledcolumn of the table and use the path recommended
Note For more information on the FICON qualified NX-OS releases refer tothe EMC Support Matrix available through E-Lab Interoperability Navigator(ELN) at httpelabnavigatorEMCcom
Upgrading Effect on VSAN 4079If you are upgrading to NX-OS Release 50(4b) and you have notcreated VSAN 4079 the NX-OS software will automatically createVSAN 4079 and reserve it for EVFP use If VSAN 4079 is reserved forEVFP use the switchport trunk allowed vsan command will filterout VSAN 4079 from the allowed list as shown in the followingexample
switch(config-if) switchport trunk allowed vsan1-40801-40784080switch(config-if)
If you have created VSAN 4079 the upgrade to NX-OS Release50(4b) will have no affect on VSAN 4079
If you downgrade to a release of NX-OS lower than 41(x) afterNX-OS Release 50(4b) creates VSAN 4079 and reserves it for EVFPuse the VSAN will no longer be reserved
Table 8 FICON Nondisruptive Upgrade Path to NX-OS Release 42(7b)
Current Release withFICON Enabled Upgrade Path
NX-OS 42(1b) You can nondisruptively upgrade directly to NX-OS Release 42(7b)
NX-OS 41(1c) You can nondisruptively upgrade directly to NX-OS Release 42(7b)
SAN-OS 33(1c) You can nondisruptively upgrade directly to NX-OS Release 42(7b)
18 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Upgrading a Cisco MDS 9124 or MDS 9134 switchIf you are upgrading from Cisco MDS SAN-OS Release 31(1) to CiscoNX-OS Release 4x before upgrading to NX-OS Release 50(4b) on aCisco MDS 9124 or MDS 9134 switch follow these guidelines
During the upgrade configuration is not allowed and the fabric isexpected to be stable
The Fabric Shortest Path First (FSPF) timers must be configured tothe default value of 20 seconds otherwise the nondisruptiveupgrade is blocked to ensure that the maximum down toim forthe control plane can be 80 seconds
If there are any CFS commits in the fabric the nondisruptiveupgrade will fail
If there is a zone server merge in progress in the fabric thenondisruptive upgrde will fail
If a service terminates the nondisruptive upgrade the showinstall all failure-reason command can display the reason thatthe nondisruptive upgrade cannot proceed
If there is not enough memory in the system to load the newimages the upgrade will be made disruptive due to insufficientresources and the user will be notified in the compativility table
MDS 9500 series upgrades with active IOA flowsWhen upgading an MDS 9500 series switch that has active IOA flowsthose flows may be interrupted during the supervisor moduleswitchover To workaround this issue you have to enablespanning-tree portfast on the interface on the catalyst connected tothe management interface of the activestandby supervisor for theinterface to come up fast without causing the cluster to lose quorum
Downgrading Your Cisco MDS SAN-OS Software ImageThis section lists the guidelines recommended for downgrading yourCisco MDS SAN-OS software image and includes the followingtopics
ldquoGeneral downgrading guidelinesrdquo on page 19
19
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
General downgrading guidelinesUse the following guidelines to nondisruptively downgrade yourCisco MDS NX-OS Release 50(4b)
Install and configure dual supervisor modules
Issue the system no acl-adjacency-sharing execute command todisable acl adjacency usage on Generation 2 and Generation 1modules If this command fails reduce the number of zones IVRzones TE ports or a combination of these in the system and issuethe command again
Disable all features not supported by the downgrade release Usethe show incompatibility system downgrade-image command todetermine what you need to disable
bull If you are running in interoperability mode two such featuresare the Reliable Commit Service and Full Zone DatabaseDistribution They can be disabled by running thesecommand in config term mode
no zone rcs enableno zoneset capability distribute full
Use the show install all impact downgrade-image command todetermine if your downgrade will be nondisruptive
Be aware that some features impact whether a downgrade isdisruptive or nondisruptive
bull Fibre Channel Ports Traffic on Fibre Channel ports can benondisruptively downgraded See Table 9 on page 20 for thenondisruptive downgrade path for all SAN-OS releases
bull Storage Services Intelligent storage services traffic such asSANTap NASB and FC write acceleration is disruptedduring a downgrade Fibre Channel traffic is not
bull Gigabit Ethernet Ports Traffic on Gigabit Ethernet ports isdisrupted during a downgrade This includes the GigabitEthernet ports on the MSM-184 module and the MDS 9222iswitch Those nodes that are members of VSANs traversing anFCIP ISL are impacted and a fabric reconfiguration occursiSCSI initiators connected to the Gigabit Ethernet ports loseconnectivity to iSCSI targets while the downgrade is inprogress
20 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
bull FICON If you have FICON enabled the downgrade path isdifferent See Table 10 on page 21
Note A downgrade from NX-OS Release 4x to SAN-OS Release 33(1c) is notsupported on MDS switches when FC-Redirect based applications such asData Mobility Manager or Storage Media Encryption are configured in thefabric if either of the following conditions are satisfied
1 A target for which FC-Redirect is configured is connected locally and thereare Generation 1 modules with ISLs configured in the switch
2 A host for which FC-redirect is configured is connected locally ona Generation 1 module
If these conditions exist remove the application configuration forthese targets and hosts before proceeding with the downgrade
Use Table 9 on page 20 to determine the nondisruptive downgradepath from Cisco NX-OS Release 50(4b) Find the NX-OS or SAN-OSimage you want to downgrade to in the To SAN-OSNX-OS Releasecolumn of the table and use the path recommended
Note The software downgrade information in Table 10 on page 21 appliesonly to Fibre Channel switching traffic Downgrading system softwaredisrupts IP and SSM intelligent services traffic
Table 9 Nondisruptive Downgrade Path from NX-OS Release 50(4b) (page 1 of2)
To SAN-OS NX-OSRelease Nondisruptive Downgrade Path
NX-OS 50(4) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 50(1a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(7b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(5) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(3) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(1b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(1a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 41(3a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
21
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Use Table 10 to determine your nondisruptive downgrade path if youhave FICON enabled from Cisco NX-OS Release 42(7b) Find the imagerelease number you are currently using in the Current Release withFICON Enabled column of the table and use the path recommended
NX-OS 41(1b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
SAN-OS 33(5a) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33())
SAN-OS 33(5) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(4a) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
NX-OS 33(4) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(3) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
NX-OS 33(2) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(1c) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 32(3a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 32(x)
SAN-OS 32(2c) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 32(x)
SAN-OS 32(1a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
SAN-OS 31(3a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
SAN-OS 31(2) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
Table 9 Nondisruptive Downgrade Path from NX-OS Release 50(4b) (page 2 of2)
To SAN-OS NX-OSRelease Nondisruptive Downgrade Path
Table 10 FICON Downgrade Path from NX-OS Release 42(7b)
To SAN-OSNX-OS Release withFICON Enabled Downgrade Path
NX-OS 42(1b) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
NX-OS 41(1c) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
SAN-OS 33(1c) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
22 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Best practicesLog messages are not saved across system reboots or power outagesTherefore EMC recommends that customers configure a SyslogServer in order to redirect and capture all log messages on a remoteserver For more information please refer to the Cisco MDS 9000Family Configuration Guide available at
httpwwwciscocomenUSproductsps5989products_support_series_homehtml
Maximum ports per chassisTable 11 shows the maximum ports per chassis
a V2 indicates a 9506 or 9509 with Generation-2 Supervisors The presence of anygeneration one module in a switch will limit the maximum port count to 252This includes the 16-port 32-port 14+2 IPS4 and IPS8 cards
Known problems and limitationsFor a list of problems with this release please refer to the CiscoRelease notes located at
httpwwwciscocomenUSproductsps5989prod_release_notes_listhtml
Limitations and restrictionsThe following limitations and restrictions apply to all switches in theCisco MDS 9000 Family unless a limitation for a specific switch isstated
ldquoStorage Media Encryption (SME) limitationsrdquo on page 24
Table 11 Maximum ports per chassis
Chassis Maximum number of ports
MDS 9506-V2 192a
MDS 9509-V2 336
MDS 9513 528
23
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
ldquoSME configuration limitsrdquo on page 24
ldquoDeleting Cisco SME interfacesrdquo on page 25
ldquoCisco MDS 9124 and 9134 Multilayer fabric switchesrdquo on page 25
ldquoN-Port virtualization configuration limitsrdquo on page 25
ldquoMaximum number of zones supported in Interop Mode 4rdquo onpage 25
ldquoIPv6rdquo on page 26
ldquoIP-ACL supportrdquo on page 26
ldquoUser Rolesrdquo on page 26
ldquoUsing a RSA Version 1 Key for SSH Following an Upgraderdquo onpage 27
ldquoApplying Zone Configurations to VSAN 1rdquo on page 27
ldquoInterVSAN Routingrdquo on page 28
ldquoRSPAN Traffic Not Supported on CTS Ports on 8-GbpsSwitching Modulesrdquo on page 28
ldquoIO Accelerator Feature Limitationsrdquo on page 28
ldquoSupport for FCIP Compression Modesrdquo on page 28
ldquoSaving Copies of the Running Kickstart and System Imagesrdquo onpage 29
ldquoConfiguring Buffer Credits on a Generation 2 or Generation 3Modulerdquo on page 29
ldquoStorage services module power budgetrdquo on page 29
ldquoiSCSI proxy initiator in Celerra HighRoad environmentsrdquo onpage 30
ldquoHPUX N_port IDrdquo on page 30
ldquoInteroperability limitationsrdquo on page 31
ldquoNASBrdquo on page 31
ldquoReserved VSAN Range and Isolated VSAN Range Guidelinesrdquoon page 31
ldquoSymmetrix VMax limitationsrdquo on page 32
ldquoStorage Applications on the MSM-184rdquo on page 32
ldquoDowngrading with fport-channel-trunk enabledrdquo on page 32
ldquoLDAP Authenticationrdquo on page 33
24 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
ldquoMDS-9148 limitationsrdquo on page 33
Storage Media Encryption (SME) limitationsAn SME node can only belong to one cluster Adding the node tomore than one cluster will cause problems
Currently there is no prevention or warning in place when an attemptis made to add a node to multiple clusters
SME configuration limitsTable 12 lists the SME configuration limits for this release
Table 12 SME configuration limits
Configuration Limits
Number of switches in the fabric 10
Number of clusters per switch 1
Switches in a cluster 4
Fabrics in a cluster 2
Modules in a switch 11
Cisco MSM-184 modules in a cluster 32
Initiator-Target-LUNs (ITLs) 1024
LUNs behind a target 32
Host and target ports in a cluster 128
Number of hosts per target 128
Tape backup groups per cluster 2
Volume groups in a tape backup group 4
Cisco Key Management Center ( of keys) 32K
Targets per switch that can be FC-redirected 32
25
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Deleting Cisco SME interfacesA Cisco SME interface can be deleted from the cluster only after theinterface is administratively shut-down and all related tasksassociated with the interface shut-down are complete
Cisco MDS 9124 and 9134 Multilayer fabric switchesThe Cisco MDS 9124 and 9134 Multilayer fabric switches do notsupport the following Cisco MDS SAN-OS features
IVR Remote Span Translative loop support FCCmdash no generation quench reaction only
In addition the following features have these limits
VSANs mdash 16 maximum SPAN mdash 1 session maximum
N-Port virtualization configuration limitsThe NPV features have maximum configuration limits Table 13shows the verified and maximum limits for the NPV switchesrunning NX-OS Release 5x
Maximum number of zones supported in Interop Mode 4In interop mode 4 the maximum number of zones that is supportedin an active zone set is 2047 due to limitations in the connectedvendor switch When IVR is used in interop mode 4 the maximumnumber of zones supported including IVR zones in the active zoneset is 2047 The limit for the maximum number of IVR zones perVSAN is 250 zones (two members per zone)
Table 13 NPV features limitations
Feature Verified limits Maximum limits
FLOGIs or F Disc per NPV port group 114 114
NPV switches per NPV core switch 105 105
FLOGIs per line card on NPV core switch 400 400
26 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
IPv6The management port on Cisco MDS switches supports oneuser-configured IPv6 address but does not supportauto-configuration of an IPv6 address
IP-ACL supportDo not apply IP-ACLs to only one member of a PortChannel groupApply IP-ACLs to the entire channel group
If IP-ACLs are already configured in a Gigabit Ethernet interface youcannot add this interface to a Ethernet PortChannel group
Refer to the Cisco MDS 9000 Family Configuration Guide
User RolesIn SAN-OS Release 33(x) and earlier when a user belongs to a rolewhich has a VSAN policy set to Deny and the role allows access to aspecific set of VSANs (for example 1 through 10) the user isrestricted from performing the configuration clear execute anddebug commands which had a VSAN parameter outside thisspecified set Beginning with NX-OS Release 41(1b) these users arestill prevented from performing configuration clear execute anddebug commands as before however they are allowed to performshow commands for all VSANs The ability to execute the showcommand addresses the following
In a network environment users often need to view informationin other VSANs even though they do not have permission tomodify configurations in those VSANs
This behavior makes Cisco MDS 9000 Series switches consistentwith other Cisco products such as Cisco Nexus 7000 Seriesswitches that exhibit the same behavior for those roles (whenthey apply to the VLAN policy)
27
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Using a RSA Version 1 Key for SSH Following an UpgradeFor security reasons NX-OS Release 42(x) and higher does notsupport RSA version 1 keys As a result if you upgrade from anearlier version that did support RSA version 1 keys and you hadconfigured a RSA version 1 key for SSH then you will not be able tolog in through SSH following the upgrade
If you have a RSA version 1 key configured for SSH beforeupgrading to NX-OS Release 42(x) or higher follow these steps
1 Disable SSH
2 Create RSA version 2 DSA keys
3 Enable SSH
4 Delete any RSA version 1 keys on any remote SSH clients andreplace the version 1 keys with the new version 2 keys from theswitch
Proceed with the upgrade to NX-OS Release 42(x) or higher
If you upgrade before disabling SSH and creating RSA version 2 keysfollow these steps
1 Open a Telnet session and log in through the console
2 Issue the no feature ssh command to disable SSH
3 Issue the ssh key rsa 1024 command to create RSA version 2 keys
4 Issue the feature ssh command to enable SSH
Applying Zone Configurations to VSAN 1In the setup script you can configure system default values for thedefault-zone to be permit or deny and you can configure defaultvalues for the zone distribution method and for the zone mode
These default settings are applied when a new VSAN is createdHowever the settings will not take effect on VSAN 1 because it existsprior to running the setup script Therefore when you need thosesettings for VSAN 1 you must explicitly issue the followingcommands
zone default-zone permit vsan 1 zoneset distribute full vsan 1 zone mode enhanced vsan 1
28 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
InterVSAN RoutingWhen using InterVSAN Routing (IVR) it is recommended to enableCisco Fabric Services (CFS) on all IVR-enabled switches Failure to doso may cause mismatched active zone sets if an error occurs duringzone set activation
RSPAN Traffic Not Supported on CTS Ports on 8-Gbps Switching ModulesAn inter-switch link (ISL) that is enabled for Cisco TrustSec (CTS)encryption must be brought up in non-CTS mode to support remoteSPAN (RSPAN) traffic on the following modules
DS-X9248-96K9 Cisco MDS 9000 48-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9224-96K9 Cisco MDS 9000 24-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9248-48K9 Cisco MDS 9000 444-Port Host-Optimized8-Gbps Fibre Channel Switching Module
If the ISL link is brought up with CTS enabled random packets dropsof both RSPAN traffic and normal traffic will occur on the receiverport switch
IO Accelerator Feature LimitationsIOA does not support the following NX-OS features
IVR flows
Devices with NPV and NPIV enabled
F port trunking
bull F port channeling
Support for FCIP Compression ModesIn Cisco NX-OS Release 42(1b) and higher FCIP compression mode 1and compression mode 3 are not supported on the Cisco MSM-184module and on the SSN-16 module
29
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Saving Copies of the Running Kickstart and System ImagesAfter you upgrade to MDS NX-OS Release 42(1b) or higher you arenot allowed to delete rename move or overwrite the kickstart andsystem images that are in the current system bootvar settings on anactive or standby MDS Supervisor-2 module on any Cisco MDS 9500Series switch This restriction does not apply to the integratedsupervisor module on the MDS 9200 and MDS 9100 series switches
Configuring Buffer Credits on a Generation 2 or Generation 3 ModuleWhen you configure port mode to auto or E on a Generation 2module one of the ports will not come up for the followingconfiguration
Port Mode auto or E for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E on a Generation 3module one or two of the ports will not come up for the followingconfiguration
Port Mode auto or E for the first half of the ports the second halfof the ports or for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E for all ports in the globalbuffer pool you need to reconfigure buffer credits on one or more ofthe ports The total number of buffer credits configured for all theports in the global buffer pool should be reduced by 64
Storage services module power budgetThe MDS 9509 does not have the power budget to run seven SSMcards EMC recommends a maximum of four SSMs in one 9509Customers wishing to use more than four SSMs in one chassis shouldrefer to the Cisco MDS 9000 documentation on the Ciscocom websiteto validate that there is enough power available for their desiredconfiguration
30 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Note Upgrading to the 3000 watt power supplies will alleviate thiscondition
iSCSI proxy initiator in Celerra HighRoad environmentsEMC supports the iSCSI proxy initiator feature in Celerrareg
HighRoadreg environments In proxy initiator mode one Fibre Channelinitiator is used for all iSCSI clients who access the switch via thesame iSCSI interface (iscsi33 for example)
The initiators will use the PWWN assigned to the iSCSI interface TheiSCSI interface to which an iSCSI client will logon to is configured inthe client and must be permitted by the virtual target configured forthat initiator
The current session environment supported on the MDS is
300 sessions per port 1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no InitialR2T=yes
Refer to the specific initiator support documentation on how to setthe parameters The implementation will not perform properly ifthese bits are not set
Refer to the MDS documentation for more information regarding theconfiguration of the iSCSI proxy initiator at the following Ciscowebsite
httpwwwciscocomenUSproducts
HPUX N_port IDThe N_port ID port value of 255 (0xFF) has special meaning forHP-UX A N_port ID (FC_ID) can not be returned from a switch thatcontains this value for the N_port ID (FC_ID) port value for a HP-UXinitiator or HP-UX target port Port ID value of 255 (0xFF) cannot be
31
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
configured for HP-UX initiator port and HP-UX target ports whenconfiguring MDS FC_IDs The port_ID value is the third byte of theFC_ID
Interoperability limitationsRefer to the EMC Support Matrix (ESM) and the EMC Networked Storage Topology Guide for modes of operation and caveats
NASBThe NASB feature requires that the backup application load the tapedrive with a compatible tape cartridge prior to configuring NASB inthe backup VSAN
Reserved VSAN Range and Isolated VSAN Range GuidelinesOn an NPV switch with a trunking configuration on any interface or ona regular switch where the feature fport_channel_trunk command hasbeen issued to enable the F PortChannel feature follow theseconfiguration guidelines for reserved VSANs and the isolated VSAN
bull If trunk mode is on for any of the interfaces or NP PortChannelis up the reserved VSANs are 3040 to 4078 and they are notavailable for user configuration
bull The Exchange Virtual Fabric Protocol (EVFP) isolated VSAN is4079 and it is not available for user configuration
bull VSAN 4079 will be impacted by an upgrade to NX-OS Release42(3) depending on whether or not VSAN 4079 was createdprior to the upgrade See theldquoUpgrading Effect on VSAN 4079rdquoon page 17
The following VSAN IDs are assigned in the Fibre Channel Framingand Signaling (FC-FS) interface standard
VF_ID Value Value Description
00h Do not use as a Virtual FabricIdentifier
001h EFFh Available as a Virtual FabricIdentifier
F00h FEEh Reserved
32 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Symmetrix VMax limitationsAt the time of this writing the following features are not supportedfor use with the Symmetrix VMax
FCIP Write Acceleration
The NX-OS IOA functionality is only supported with the Q2 SREnginuity release 5874229182 or higher
For the most up to date status please refer to the current revision ofthese Release Notes on httpPowerlinkemccom and the EMCSupport Matrix available through E-Lab Interoperability Navigator (ELN) athttpelabnavigatorEMCcom
Storage Applications on the MSM-184The MDS 9000 184-Port Multiservice Module (MSM-184) does notsupport multiple concurrent storage applications Only oneapplication can run on the MSM-184 at a time
Downgrading with fport-channel-trunk enabledIf you are running MDS NX-OS Release 42(x) or higher with thefport-channel-trunk feature enabled and you downgrade to anyNX-OS 41(1x) release the installer performs a nondisruptivedowngrade even though the fport-channel-trunk feature is notsupported in NX-OS 41(1x) releases
As a result the switch is in an inconsistent state and the ports maynot function properly
FEFh Control VF-ID (see FibreChannel Link Services (FC-LS)and Fibre Channel SwitchFabric Generation 4 (FC-SW-4)standards)
FF0h FFEh Vendor specific
FFFh Do not use as a Virtual FabricIdentifier
FEFh = 4079
33
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
If you are in this state a workaround is to reboot the switch followingthe upgrade
LDAP AuthenticationThere is currently a limitation in the LDAP server configuration CLIthat prevents the use of an OU with spaces in the name Normallythese OU names could be surrounded by quotation marks howeverquotation marks are not supported by the ldap-server command
MDS-9148 limitationsThe Cisco MDS 9148 Multilayer Fabric Switch does not support thefollowing NX-OS features
Medium and Long range 4GB Agilent
IVR
Remote Span
Translative loop support
FCC - no generation quench reaction only
FC-Redirect
In addition the following features have these limits
VSANS - 31 maximum
SPAN - 1 session maximum
Technical notesThe following sections provide further information on technicalnotes
EMC Email Home for Cisco MDS switchesInstallation and Trouble shooting instructions can be found in thedocumentation located at the EMC Customer Service Internalwebsite
httpwwwcsisusemccomcsweb2esnesnhomehtmConnectrix20MDS20900020Family
34 EMC Connectrix MDS 9000 NX-OS Release Notes
Technical notes
Customers requiring installation of this solution should contact theirEMC Customer Engineer to assist with the installation and providethe documentation
Supported iSCSI sessionsThe current iSCSI session environment supported on the MDS is
300 sessions per port
1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no
InitialR2T=yes
Upgrading Cisco SAN-OSThere are several methods available for upgrading SAN-OS SoftwareEMC personnel are strongly recommended that all upgrades be doneby the Automated One-Step Upgrade using the install all
command EMC personnel should refer to the Connectrix MDS 9000Family Software Image Upgrade Instructions for a complete list ofprerequisites and instructions for performing the upgrade Thisdocument along with tftp software is available on the GlobalServices website at httpwwwcsisusEMCcom under ApplicationDownload Area ESN Product Information Connectrix MDS 9000Family
The Software Upgrade Wizard is an option for upgrades While theinstall all is the preferred method the Software Install Wizard canalso be used
Supported configuration parametersFor the most up-to-date information refer to the EMC Support Matrixavailable through E-Lab Interoperability Navigator athttpelabnavigatoremccom for the latest information onsupported configurations
35
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
Supported zoning parametersRefer to the EMC Networked Storage Topology Guide for the mostup-to-date information on supported zoning parameters
At the time these notes were published the following parameterswere supported
20 VSANs 5 Hops 2000 Unique members per physical infrastructure 1000 Zonesets per physical infrastructure 2000 Zones per physical infrastructure 1 FCIP tunnel
Supported IVR parameters IVR zone members 1000 IVR zones 1000 IVR zone sets 32 VSANS 20 IVR enabled switches 64
An RPQ can be submitted for any configurations that exceed thislimit
Managing zone changes in multiswitch fabricsZoning changes may be made through Fabric Manager or CLI Whenaccessing Fabric Manager or CLI the user does so from the point ofview of one switch That is Fabric Manager and CLI are accessed byentering the IP address of one switch in the fabric
When zoning changes are made the applicable VSAN and zone setdata is propagated to the rest of the switches in the fabric via the ISLs
When zoning changes are made to a VSAN the zone set data ispropagated to the rest of the switches in the fabric via the ISLs Bydefault only the active zone set information is relayed to all switchesin the VSAN If the user accesses the Fabric Manager and CLI fromanother switch in the fabric the new VSAN and zone set informationwill not be viewable To view the active and inactive zone set on theother switches in the fabric the user must log in to the CLI and issuea command from the EXEC prompt
36 EMC Connectrix MDS 9000 NX-OS Release Notes
Documentation
Example The following is an example of copying VSAN 1 through 20 zoningdata
CiscoMDS_name zone copy active full vsan 1-20
CiscoMDS_name conf t
Enter configuration commands one per line End with CNTL Z
CiscoMDS_name(config) zoneset distribute full vsan 1-20
CiscoMDS_name(config)
Note This command needs to be issued on all switches in the fabric one timeonly
This is a nondisruptive command After issuing the commands theuser will now see the active and inactive zone sets for the specifiedVSANs on any switch that is chosen from which to manage the fabric
After a zoning change is made save the running configuration to thestartup configuration
DocumentationSend documentation comments to mdsfeedback-doccom
Product DocumentationAs of NX-OS Release 42(1a) software configuration information isavailable in new feature-specific configuration guides for thefollowing information
System management
Interfaces
Fabric
Quality of service
Security
IP services
High availability and redundancy
37
Software media organization and files
EMC Connectrix MDS 9000 NX-OS Release Notes
The information in these new guides previously existed in the CiscoMDS 9000 Family CLI Configuration Guide That configuration guideremains available on Ciscocom and should be used for all softwarereleases prior to NX-OS Release 42(1a) Configuration guidesaddress the features introduced in or available in a particular releaseSelect and view the configuration guide that pertains to the softwareinstalled in your switch
In addition Fabric Manager information has been removed from theMDS NX-OS Release Notes (this document) and placed intostandalone Fabric Manager Release Notes that support both CiscoMDS 9000 Family switches and Cisco Nexus 5000 Series switchesThe Cisco Fabric Manager Release Notes are available onhttpPowerlinkemccom and from the following website
httpwwwciscocomenUSpartnerproductsps10495prod_release_notes_listhtml
Technical supportThese release notes complement a Cisco documentation set EachCisco document refers to where to get help However for any itemssupplied by EMC see ldquoTroubleshooting and getting helprdquo onpage 38
Software media organization and filesFor information on related software environment and systemrequirements refer to the EMC Support Matrix on EMC Powerlink at
httpPowerlinkEMCcom
InstallationFor hardware installation information refer to the Cisco MDS HWInstallation Guides available at Ciscocom
For EMC-specific installation information refer to ldquoEnvironment andsystem requirementsrdquo on page 5 in this document
38 EMC Connectrix MDS 9000 NX-OS Release Notes
Troubleshooting and getting help
Troubleshooting and getting helpEMC support product and licensing information can be obtained asfollows
Product information mdash For documentation release notes softwareupdates or for information about EMC products licensing andservice go to the EMC Powerlink website (registration required) at
httpPowerlinkEMCcom
Technical support mdash For technical support go to EMC CustomerService on Powerlink To open a service request through Powerlinkyou must have a valid support agreement Please contact your EMCsales representative for details about obtaining a valid supportagreement or to answer any questions about your account
Copyright copy 2011 EMC Corporation All rights reserved
EMC believes the information in this publication is accurate as of its publication date The information issubject to change without notice
THE INFORMATION IN THIS PUBLICATION IS PROVIDED ldquoAS ISrdquo EMC CORPORATION MAKES NOREPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION INTHIS PUBLICATION AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OFMERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Use copying and distribution of any EMC software described in this publication requires an applicablesoftware license
For the most up-to-date regulatory document for your product line go to the Technical Documentation andAdvisories section on EMC Powerlink
For the most up-to-date listing of EMC product names see EMC Corporation Trademarks on EMCcom
All other trademarks used herein are the property of their respective owners
4 EMC Connectrix MDS 9000 NX-OS Release Notes
Fixed problems
Boot over SAN is not supported with IVR NAT Caching Services Module Cisco Call Home Cisco MDS Data Mobility Manager (DMM) for the Cisco MDS
9000 Common Information Model Fabric Binding on any McData switch is not supported for Interop
mode four Fabric-Device Management Interface Installation of the 9513 into the EC-1500 cabinet Installation of the 9124 into the EC-1700-C abinet No heterogeneous fabrics supported with SME No disk encryption supported with SME IPSEC iSCSI 16 and 32 port cards are not supported in a 9222i IPsec with Ipv6 Tunneling (IPv4 and v6) is not supported on the same interface iSNS Cloud Discovery LUN Zoning in Fabric NPV on any stand-alone switches Offline data restore tool Proxy Initiator (limited to 1800) Read-Only Zones Storage Management Initiative Specification (SMI-S) 110
support Transceiver and Calibration Information Trespass support VRRP TACACS is not supported for switch-to-switch authentication NDMP backup with IOA is not supported at this time Secure Erase
Note To obtain the most up-to-date information on EMC supportedconfigurations reference the most current release notes available athttpPowerlinkEMCcom and the EMC Support Matrix available throughE-Lab Interoperability Navigator at httpelabnavigatorEMCcom
Fixed problemsCisco-specific caveats for resolved problems can be found in theCisco release-noted documentation with the equivalent firmwarelevel at the following Cisco website
5
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
httpwwwciscocomenUSpartnerproductsps10495prod_release_notes_listhtml
Note Cisco makes all release notes past and present available on thiswebsite
Environment and system requirementsThis section describes the system requirements for MDS NX-OSRelease 50(4b) and includes the following topics
Hardware Supported and Minimum Software Required Determining the Software Version Upgrade Prerequisites Software Upgrade Mechanisms Image Upgrade Matrix Best Practices Maximum ports per Chassis
Telco 2 post racksNote that the 9509 and 9513 should not be used in a 2 post Telco rackdue to weight considerations Refer to the Cisco MDS 9000 HardwareInstallation Guides on httpwwwciscocom for more information
EC-1700 configuration informationConfiguration information appears in the Connectrix EC-1700 CabinetInstallation and Setup Manual on the EMC Powerlinkreg website
Note Currently only the MDS 9509 and 9513 are supported in the EC-1700-Ccabinet The MDS 9124 is not supported in the EC-1700-C
8Gb Power RequirementsEven though Cisco director class models may operate at 100 to 240VAC in configurations consisting of 8 Gb modules 200-240 VAC ishighly recommended Operating at lower voltages will decrease thenumber of modules that may be installed in your chassis
6 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
For more information on power requirements please refer toAppendix C of the Cisco MDS 9500 Series Hardware Installation Guide
Hardware and software componentsEMC supported hardware and software modules are listed in CiscoNX-OS 50(4b) release notes located on the Cisco web site
Note Table 1 lists the MDS 9000 Family software and hardware componentsthat are not supported by EMC as well as the comparable NX-OS partnumbers
For older NX-OS part numbers see prior existing versions of SAN OSrelease notes
Table 1 MDS 9000 Family software and hardware modules not supported(page 1 of 2)
Component EMC part number Description Applicable products
Service modules DS-X9304-18FK9 18-port Fibre Channel4-port GigabitEthernet Multiservice FIPS (MSFM-184)module
MDS 9500 Series and9200 Series
Optics DS-X2-FC10G-ER X2SC optics 10-Gbps Fibre Channel forExtended Reach (40 km)
MDS 9500 Series and9200 Series exceptfor the MDS 9216
DS-X2-E10G-SR X2SC optics 10-Gbps Ethernet for ShortReach
DS-X2-FC10G_CX4 X2CX-4 optics 10-Gbps Fibre Channelcopper
LC-type fiber-optic SFP DS-SFP-GE-T 1-Gbps Ethernet SFP MDS 9000 Family
CWDM DS-CWDM-xxxx Gigabit Ethernet and 4-Gbps FibreChannel SFP LC interface xxxx nmwhere xxxx = 1470 1490 1510 15301550 1570 1590 or 1610 nm
DS-CWDM-MUX-4 Adddrop multiplexer for four CWDMwavelengths
DS-CWDM-MUX-8 Adddrop multiplexer for eight CWDMwavelengths
DS-CWDMCHASSIS Two slot chassis for CWDM adddropmultiplexers
7
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Note EMC personnel can obtain a complete list of Cisco part numbers fromthe Product Support Bulletins available under the ProductTechnicalInformation section of the EMC Global Services website athttpwwwcsisusEMCcomMyGSiVisitURLaspurl=10137
Support for the Generation 3 ModulesThe MDS 9513 Director requires Cisco MDS NX-OS 41(1b) or laterand the MDS 9513 Fabric 2 modules to support the MDS 9000 48-port8-Gbps Fibre Channel module and the MDS 9000 24-port 8-GbpsFibre Channel module
The MDS 9513 Director requires Cisco MDS NX-OS 41(1b) or laterbut does not require the MDS 9513 Fabric 2 modules to support theMDS 9000 444-port 8-Gbps Host-optimized Fibre Channel module
The MDS 9509 Director and the MDS 9506 Director also support theGeneration 3 8-Gbps modules The switches require Supervisor-2modules and Cisco MDS NX-OS 41(1b) or above to support theGeneration 3 8-Gbps modules
For information on the tasks associated with readying the MDS 9500Series to support Generation 3 8-Gbps Fibre Channel switchingmodules refer to the Migrating to Generation 3 Modules appendix inthe Cisco MDS 9500 Series Hardware Installation Guide It presents anoverview of the Generation 3 8-Gbps modules provides usageguidelines for the modules and describes three procedures formigrating hardware and upgrading software to enable use of thesemodules in an MDS 9513 Director
For information on replacing the MDS 9513 Fabric 1 modules withFabric 2 modules refer to the Migrating to Generation 3 Modulesappendix in the Cisco MDS 9500 Series Hardware Installation Guide Itprovides information on installing new Fabric 2 modules while
Port analyzer adapter DS-PAA-2 DS-PAA A standalone Fibre Channel-to-Ethernetadapter that allows for simple transparentanalysis of Fibre Channel traffic in aswitched fabric
MDS 9000 Family
Table 1 MDS 9000 Family software and hardware modules not supported(page 2 of 2)
Component EMC part number Description Applicable products
8 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
running NX-OS Release 4x and SAN-OS Release 3x It also providesinformation on installing the MDS 9513 Fabric 2 modules andactivating higher bandwidth
Configuring Generation 3 and Generation 2 Switching ModulesThe Cisco MDS 9500 Multilayer Directors are designed to operatewith any combination of Cisco MDS 9000 Generation 2 andGeneration 3 modules However there are limitations to considerwhen combining the various modules and supervisors in the CiscoMDS 9500 Series platform chassis The references listed in this sectionprovide specific information about configurations that combinedifferent modules and supervisors
For information on configuring Generation 2 and Generation 3switching modules refer to the Configuring Generation 2 andGeneration 3 Switching Modules chapter in the Cisco MDS 9000Family CLI Configuration Guide
For information on port index availability refer to the ldquoPort IndexAvailabilityrdquo section in the Product Overview chapter of the CiscoMDS 9500 Series Hardware Installation Guide
For information on Cisco MDS 9000 hardware and softwarecompatibility refer to the EMC Support Matrix available through E-LabInteroperability Navigator (ELN) at httpelabnavigatorEMCcom
MDS 9000 Chassis and Module Support in Cisco MDS NX-OS 5xTable 2 lists the MDS hardware chassis supported by Cisco MDSNX-OS 5x
Table 2 Cisco MDS NX-OS 5x Chassis Support Matrix
Switch NX-OS 5x Support
MDS 9513 Yes
MDS 9509 Yes
MDS 9506 Yes
MDS 9222i Yes
MDS 9216i No
9
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Table 3 lists the MDS hardware modules supported by Cisco MDSNX-OS 5x
MDS 9216A No
MDS 9216 No
MDS 9148 Yes
MDS 9134 Yes
MDS 9124 Yes
MDS 9140 No
MDS 9120 No
Table 2 Cisco MDS NX-OS 5x Chassis Support Matrix
Switch NX-OS 5x Support
Table 3 Module Support Matrix for Cisco MDS NX-OS 5x (page 1 of 2)
Module DescriptionMDS 9500Series MDS 9222i
DS-X9530-SF2A-K9 MDS 9500 Supervisor-2A Module Yes NA
DS-X9530-SF2-K9 MDS 9500 Supervisor-2 Module Yes NA
DS-X9530-SF1-K9 MDS 9500 Supervisor-1 Module No NA
DS-X9224-96K9 24-port 8-Gbps Fibre Channel Switching Module Yesa No
DS-X9248-96K9 48-port 8-Gbps Fibre Channel Switching Module Yesa No
DS-X9248-48K9 444-port Host Optimized 8-Gbps Fibre ChannelSwitching Module
Yes Yes
DS-X9316-SSNK9 16-Port Storage Services Node (SSN-16) Yes Yes
DS-X9304-18K9 184-Port Multiprotocol Services Module(MSM-184)
Yes Yes
DS-X9112 12-port 4-Gbps Fibre Channel Switching Module Yes Yes
DS-X9124 24-port 4-Gbps Fibre Channel Switching Module Yes Yes
DS-X9148 48-port 4-Gbps Fibre Channel Switching Module Yes Yes
DS-X9704 4-port 10-Gbps Fibre Channel Switching Module Yes Yes
10 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Migrating from Supervisor-1 Modules to Supervisor-2 ModulesAs of Cisco MDS SAN-OS Release 30(1) the Cisco MDS 9509 and9506 Directors support both Supervisor-1 and Supervisor-2 modulesSupervisor-1 and Supervisor-2 modules cannot be installed in thesame switch except during migration Both the active and standbysupervisor modules must be of the same type either Supervisor-1 orSupervisor-2 modules For Cisco MDS 9513 Directors bothsupervisor modules must be Supervisor-2 modules
CAUTION
Migrating your supervisor modules is a disruptive operation
Note Migrating from Supervisor-2 modules to Supervisor-1 modules is not supported
To migrate from a Supervisor-1 module to a Supervisor-2 module refer to the step-by-step instructions in the Cisco MDS 9000 NX-OS Release 41(x) and SAN-OS 3(x) Software Upgrade and Downgrade Guide
DS-X9302-14K9 142-port Multiprotocol Services (MPS-142)Module
No No
DS-X9016 16-port 1- 2-Gbps Fibre Channel SwitchingModule
No No
DS-X9032 32-port 1- 2-Gbps Fibre Channel SwitchingModule
No No
DS-X9032-SSM 32-port Storage Services Module (SSM) No No
DS-X9308-SMIP 8-port 1- 2-Gbps IP Switching Module No No
DS-X9304-SMIP 4-port 1- 2-Gbps IP Switching Module No No
a Requires DS-13SLT-FAB2 in the MDS 9513
Table 3 Module Support Matrix for Cisco MDS NX-OS 5x (page 2 of 2)
Module DescriptionMDS 9500Series MDS 9222i
11
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Software Download ProcessUse the software download procedure to upgrade to a later versionor downgrade to an earlier version of an operating system Thissection describes the software download process for the Cisco MDSNX-OS software and includes the following topics
ldquoDetermining the Software Versionrdquo on page 11
ldquoDownloading Softwarerdquo on page 11
ldquoSelecting the Correct Software Image for an MDS 9100 SeriesSwitchrdquo on page 12
ldquoSelecting the Correct Software Image for an MDS 9200 SeriesSwitchrdquo on page 13
ldquoSelecting the Correct Software Image for an MDS 9500 SeriesSwitchrdquo on page 13
Determining the Software VersionTo determine the version of Cisco MDS NX-OS or SAN-OS softwarecurrently running on a Cisco MDS 9000 Family switch using the CLIlog in to the switch and enter the show version EXEC command
To determine the version of Cisco MDS NX-OS or SAN-OS softwarecurrently running on a Cisco MDS 9000 Family switch using theFabric Manager view the Switches tab in the Information pane locatethe switch using the IP address logical name or WWN and check itsversion in the Release column
Note EMC strongly recommends that you use the latest qualified softwarerelease for all MDS 9000 Family products Refer to the EMC Support Matrixavailable through E-Lab Interoperability Navigator (ELN) athttpelabnavigatorEMCcom for the latest information on qualifiedfirmware revisions
Downloading SoftwareThe Cisco MDS NX-OS software is designed for mission-critical highavailability environments To realize the benefits of nondisruptiveupgrades on the Cisco MDS 9500 Directors we highly recommendthat you install dual supervisor modules
12 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Before performing upgrades submit all requested changes to theEMC Global Services CCA change control process so that anypotential operating environment impacts can be analyzedbeforehand
EMC personnel should also refer to the Connectrix MDS 9000 FamilySoftware Image Upgrade Instructions for a complete list of prerequisitesThis document is available on the Global Services websitehttpwwwcsisusEMCcom under Application Download AreaESN Product Information Connectrix MDS 9000 Family EMCpersonnel can download the Software Images from the GlobalServices website httpwwwcsisusEMCcom under ApplicationDownload Area ESN Product Information Connectrix MDS 9000Family
See the following sections in this release note for details on how youcan nondisruptively upgrade your Cisco MDS 9000 switch Issuingthe install all command from the CLI or using Fabric Manager toperform the downgrade enables the compatibility check The checkindicates if the upgrade can happen nondisruptively or disruptivelydepending on the current configuration of your switch and thereason
Compatibility check is doneModule bootable Impact Install-type Reason------ -------- -------------- ------------ ------
1 yes non-disruptive rolling2 yes disruptive rolling Hitless upgrade is not supported3 yes disruptive rolling Hitless upgrade is not supported4 yes non-disruptive rolling5 yes non-disruptive reset6 yes non-disruptive reset
Selecting the Correct Software Image for an MDS 9100 Series SwitchThe system and kickstart image that you use for an MDS 9100 seriesswitch depends on which switch you use as shown in Table 4
Table 4 Software Images for MDS 9100 Series Switches
Cisco MDS 9100 Series Switch Type Naming Convention
9124 and 9134 Filename begins with m9100-s2ek9
9148 Filename begins with m9100-s3ek9
13
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Selecting the Correct Software Image for an MDS 9200 Series SwitchThe system and kickstart image that you use for an MDS 9200 seriesswitch depends on which switch you use as shown in Table 5
Selecting the Correct Software Image for an MDS 9500 Series SwitchThe system and kickstart image that you use for an MDS 9500 Seriesswitch depends on whether the switch is based on a Supervisor-1module or a Supervisor-2 module as shown in Table 6
Use the show module command to display the type of supervisormodule in the switch The following is sample output from the showmodule command on a Supervisor 2 module
Table 5 Software Images for MDS 9200 Series Switches
Cisco MDS 9200 Series Switch Type Naming Convention
9222i Filename begins with m9200-s2ek9
Table 6 Software Images for Supervisor Type
Cisco MDS 9500 Series Switch Type Supervisor Module Type Naming Convention
9513 9509 and 9506 Supervisor-2 module Filename begins with m9500-sf2ek9
14 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
switch show moduleMod Ports Module-Type Model Status--- ----- -------------------------------- ------------------ ------------7 0 SupervisorFabric-2 DS-X9530-SF2-K9 active 8 0 SupervisorFabric-2 DS-X9530-SF2-K9 ha-standby
Upgrading Your Cisco MDS NX-OS Software ImageThis section lists the guidelines recommended for upgrading yourCisco MDS NX-OS software image and includes the following topics
ldquoGeneral Upgrading Guidelinesrdquo on page 14
ldquoDowngrading Your Cisco MDS SAN-OS Software Imagerdquo onpage 18
Note Before you begin the upgrade process review the list of chassis andmodules that NX-OS Release 50(4b) supports See the ldquoMDS 9000 Chassisand Module Support in Cisco MDS NX-OS 5xrdquo on page 8
Note For detailed instructions for performing a software upgrade usingCisco Fabric Manager see the Cisco Fabric Manager Release Notes forRelease 50(4b) which is available from the following websitehttpPowerlinkEMCcom
General Upgrading Guidelines
Note To upgrade to NX-OS Release 50(4b) you must be running NX-OSRelease 4x If you are running SAN-OS Release 32(3a) or earlier firstupgrade to SAN-OS Release 33(x) then NX-OS Release 4x and thenupgrade to NX-OS Release 50(4b)
Use the following guidelines when upgrading to Cisco MDS NX-OSRelease 5x
Install and configure dual supervisor modules
Issue the show install all impact upgrade-image CLI command todetermine if your upgrade will be nondisruptive
15
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Be aware of the impact of an upgrade on VSAN 4079 if you areupgrading from SAN-OS Release 3x to NX-OS 50(4b) See theldquoUpgrading Effect on VSAN 4079rdquo on page 17
Follow the recommended guidelines for upgrading a Cisco MDS9124 or MDS 9134 Switch as described in ldquoUpgrading a CiscoMDS 9124 or MDS 9134 switchrdquo on page 18
Take note of the affect of upgrades on MDS 9500 series switchesthat have active IOA flows as described in ldquoMDS 9500 seriesupgrades with active IOA flowsrdquo on page 18
Be aware that some features impact whether an upgrade isdisruptive or nondisruptive
bull Fibre Channel Ports Traffic on Fibre Channel ports can benondisruptively upgraded See Table 7 on page 16 for thenondisruptive upgrade path for all NX-OS and SAN-OSreleases
bull Storage Services Intelligent storage services traffic such asSANTap NASB and FC write acceleration is disruptedduring an upgrade Fibre Channel traffic is not
bull Gigabit Ethernet Ports Traffic on Gigabit Ethernet ports isdisrupted during an upgrade or downgrade This includes theGigabit Ethernet ports on the MSM-184 module and the MDS9222i switch Those nodes that are members of VSANs traversingan FCIP ISL are impacted and a fabric reconfiguration occursiSCSI initiators connected to the Gigabit Ethernet ports loseconnectivity to iSCSI targets while the upgrade is in progress
bull FICON If you have FICON enabled the upgrade path isdifferent See Table 6 on page 13
Use Table 7 to determine your nondisruptive upgrade path to Cisco MDSNX-OS Release 50(4b) find the image release number you are currentlyusing in the Current column of the table and use the path recommended
16 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Note The software upgrade information in Table 7 applies only to FibreChannel switching traffic Upgrading system software disrupts IP traffic andSSM intelligent services traffic
MDS NX-OS Release 50(4b) is not a FICON-qualified release
Table 7 Nondisruptive Upgrade Path to Cisco MDS NX-OS Release 50(4b)
Current Nondisruptive Upgrade Path
NX-OS 50(4) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 50(1a) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(7b) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(5) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(3) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(1b) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(1a) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 41(3a) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 41(1b) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
SAN-OS 33(4a) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
NX-OS 33(4) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 33(3) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 33(2) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 33(1c) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 32(3a) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 32(2c) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 32(1a) Upgrade to SAN-OS Release then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 31(3a) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 31(2) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
17
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Use Table 8 to determine your FICON nondisruptive upgrade path toCisco MDS NX-OS Release 42(7b) Find the image release numberyou are currently using in the Current Release with FICON Enabledcolumn of the table and use the path recommended
Note For more information on the FICON qualified NX-OS releases refer tothe EMC Support Matrix available through E-Lab Interoperability Navigator(ELN) at httpelabnavigatorEMCcom
Upgrading Effect on VSAN 4079If you are upgrading to NX-OS Release 50(4b) and you have notcreated VSAN 4079 the NX-OS software will automatically createVSAN 4079 and reserve it for EVFP use If VSAN 4079 is reserved forEVFP use the switchport trunk allowed vsan command will filterout VSAN 4079 from the allowed list as shown in the followingexample
switch(config-if) switchport trunk allowed vsan1-40801-40784080switch(config-if)
If you have created VSAN 4079 the upgrade to NX-OS Release50(4b) will have no affect on VSAN 4079
If you downgrade to a release of NX-OS lower than 41(x) afterNX-OS Release 50(4b) creates VSAN 4079 and reserves it for EVFPuse the VSAN will no longer be reserved
Table 8 FICON Nondisruptive Upgrade Path to NX-OS Release 42(7b)
Current Release withFICON Enabled Upgrade Path
NX-OS 42(1b) You can nondisruptively upgrade directly to NX-OS Release 42(7b)
NX-OS 41(1c) You can nondisruptively upgrade directly to NX-OS Release 42(7b)
SAN-OS 33(1c) You can nondisruptively upgrade directly to NX-OS Release 42(7b)
18 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Upgrading a Cisco MDS 9124 or MDS 9134 switchIf you are upgrading from Cisco MDS SAN-OS Release 31(1) to CiscoNX-OS Release 4x before upgrading to NX-OS Release 50(4b) on aCisco MDS 9124 or MDS 9134 switch follow these guidelines
During the upgrade configuration is not allowed and the fabric isexpected to be stable
The Fabric Shortest Path First (FSPF) timers must be configured tothe default value of 20 seconds otherwise the nondisruptiveupgrade is blocked to ensure that the maximum down toim forthe control plane can be 80 seconds
If there are any CFS commits in the fabric the nondisruptiveupgrade will fail
If there is a zone server merge in progress in the fabric thenondisruptive upgrde will fail
If a service terminates the nondisruptive upgrade the showinstall all failure-reason command can display the reason thatthe nondisruptive upgrade cannot proceed
If there is not enough memory in the system to load the newimages the upgrade will be made disruptive due to insufficientresources and the user will be notified in the compativility table
MDS 9500 series upgrades with active IOA flowsWhen upgading an MDS 9500 series switch that has active IOA flowsthose flows may be interrupted during the supervisor moduleswitchover To workaround this issue you have to enablespanning-tree portfast on the interface on the catalyst connected tothe management interface of the activestandby supervisor for theinterface to come up fast without causing the cluster to lose quorum
Downgrading Your Cisco MDS SAN-OS Software ImageThis section lists the guidelines recommended for downgrading yourCisco MDS SAN-OS software image and includes the followingtopics
ldquoGeneral downgrading guidelinesrdquo on page 19
19
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
General downgrading guidelinesUse the following guidelines to nondisruptively downgrade yourCisco MDS NX-OS Release 50(4b)
Install and configure dual supervisor modules
Issue the system no acl-adjacency-sharing execute command todisable acl adjacency usage on Generation 2 and Generation 1modules If this command fails reduce the number of zones IVRzones TE ports or a combination of these in the system and issuethe command again
Disable all features not supported by the downgrade release Usethe show incompatibility system downgrade-image command todetermine what you need to disable
bull If you are running in interoperability mode two such featuresare the Reliable Commit Service and Full Zone DatabaseDistribution They can be disabled by running thesecommand in config term mode
no zone rcs enableno zoneset capability distribute full
Use the show install all impact downgrade-image command todetermine if your downgrade will be nondisruptive
Be aware that some features impact whether a downgrade isdisruptive or nondisruptive
bull Fibre Channel Ports Traffic on Fibre Channel ports can benondisruptively downgraded See Table 9 on page 20 for thenondisruptive downgrade path for all SAN-OS releases
bull Storage Services Intelligent storage services traffic such asSANTap NASB and FC write acceleration is disruptedduring a downgrade Fibre Channel traffic is not
bull Gigabit Ethernet Ports Traffic on Gigabit Ethernet ports isdisrupted during a downgrade This includes the GigabitEthernet ports on the MSM-184 module and the MDS 9222iswitch Those nodes that are members of VSANs traversing anFCIP ISL are impacted and a fabric reconfiguration occursiSCSI initiators connected to the Gigabit Ethernet ports loseconnectivity to iSCSI targets while the downgrade is inprogress
20 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
bull FICON If you have FICON enabled the downgrade path isdifferent See Table 10 on page 21
Note A downgrade from NX-OS Release 4x to SAN-OS Release 33(1c) is notsupported on MDS switches when FC-Redirect based applications such asData Mobility Manager or Storage Media Encryption are configured in thefabric if either of the following conditions are satisfied
1 A target for which FC-Redirect is configured is connected locally and thereare Generation 1 modules with ISLs configured in the switch
2 A host for which FC-redirect is configured is connected locally ona Generation 1 module
If these conditions exist remove the application configuration forthese targets and hosts before proceeding with the downgrade
Use Table 9 on page 20 to determine the nondisruptive downgradepath from Cisco NX-OS Release 50(4b) Find the NX-OS or SAN-OSimage you want to downgrade to in the To SAN-OSNX-OS Releasecolumn of the table and use the path recommended
Note The software downgrade information in Table 10 on page 21 appliesonly to Fibre Channel switching traffic Downgrading system softwaredisrupts IP and SSM intelligent services traffic
Table 9 Nondisruptive Downgrade Path from NX-OS Release 50(4b) (page 1 of2)
To SAN-OS NX-OSRelease Nondisruptive Downgrade Path
NX-OS 50(4) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 50(1a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(7b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(5) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(3) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(1b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(1a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 41(3a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
21
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Use Table 10 to determine your nondisruptive downgrade path if youhave FICON enabled from Cisco NX-OS Release 42(7b) Find the imagerelease number you are currently using in the Current Release withFICON Enabled column of the table and use the path recommended
NX-OS 41(1b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
SAN-OS 33(5a) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33())
SAN-OS 33(5) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(4a) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
NX-OS 33(4) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(3) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
NX-OS 33(2) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(1c) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 32(3a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 32(x)
SAN-OS 32(2c) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 32(x)
SAN-OS 32(1a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
SAN-OS 31(3a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
SAN-OS 31(2) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
Table 9 Nondisruptive Downgrade Path from NX-OS Release 50(4b) (page 2 of2)
To SAN-OS NX-OSRelease Nondisruptive Downgrade Path
Table 10 FICON Downgrade Path from NX-OS Release 42(7b)
To SAN-OSNX-OS Release withFICON Enabled Downgrade Path
NX-OS 42(1b) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
NX-OS 41(1c) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
SAN-OS 33(1c) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
22 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Best practicesLog messages are not saved across system reboots or power outagesTherefore EMC recommends that customers configure a SyslogServer in order to redirect and capture all log messages on a remoteserver For more information please refer to the Cisco MDS 9000Family Configuration Guide available at
httpwwwciscocomenUSproductsps5989products_support_series_homehtml
Maximum ports per chassisTable 11 shows the maximum ports per chassis
a V2 indicates a 9506 or 9509 with Generation-2 Supervisors The presence of anygeneration one module in a switch will limit the maximum port count to 252This includes the 16-port 32-port 14+2 IPS4 and IPS8 cards
Known problems and limitationsFor a list of problems with this release please refer to the CiscoRelease notes located at
httpwwwciscocomenUSproductsps5989prod_release_notes_listhtml
Limitations and restrictionsThe following limitations and restrictions apply to all switches in theCisco MDS 9000 Family unless a limitation for a specific switch isstated
ldquoStorage Media Encryption (SME) limitationsrdquo on page 24
Table 11 Maximum ports per chassis
Chassis Maximum number of ports
MDS 9506-V2 192a
MDS 9509-V2 336
MDS 9513 528
23
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
ldquoSME configuration limitsrdquo on page 24
ldquoDeleting Cisco SME interfacesrdquo on page 25
ldquoCisco MDS 9124 and 9134 Multilayer fabric switchesrdquo on page 25
ldquoN-Port virtualization configuration limitsrdquo on page 25
ldquoMaximum number of zones supported in Interop Mode 4rdquo onpage 25
ldquoIPv6rdquo on page 26
ldquoIP-ACL supportrdquo on page 26
ldquoUser Rolesrdquo on page 26
ldquoUsing a RSA Version 1 Key for SSH Following an Upgraderdquo onpage 27
ldquoApplying Zone Configurations to VSAN 1rdquo on page 27
ldquoInterVSAN Routingrdquo on page 28
ldquoRSPAN Traffic Not Supported on CTS Ports on 8-GbpsSwitching Modulesrdquo on page 28
ldquoIO Accelerator Feature Limitationsrdquo on page 28
ldquoSupport for FCIP Compression Modesrdquo on page 28
ldquoSaving Copies of the Running Kickstart and System Imagesrdquo onpage 29
ldquoConfiguring Buffer Credits on a Generation 2 or Generation 3Modulerdquo on page 29
ldquoStorage services module power budgetrdquo on page 29
ldquoiSCSI proxy initiator in Celerra HighRoad environmentsrdquo onpage 30
ldquoHPUX N_port IDrdquo on page 30
ldquoInteroperability limitationsrdquo on page 31
ldquoNASBrdquo on page 31
ldquoReserved VSAN Range and Isolated VSAN Range Guidelinesrdquoon page 31
ldquoSymmetrix VMax limitationsrdquo on page 32
ldquoStorage Applications on the MSM-184rdquo on page 32
ldquoDowngrading with fport-channel-trunk enabledrdquo on page 32
ldquoLDAP Authenticationrdquo on page 33
24 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
ldquoMDS-9148 limitationsrdquo on page 33
Storage Media Encryption (SME) limitationsAn SME node can only belong to one cluster Adding the node tomore than one cluster will cause problems
Currently there is no prevention or warning in place when an attemptis made to add a node to multiple clusters
SME configuration limitsTable 12 lists the SME configuration limits for this release
Table 12 SME configuration limits
Configuration Limits
Number of switches in the fabric 10
Number of clusters per switch 1
Switches in a cluster 4
Fabrics in a cluster 2
Modules in a switch 11
Cisco MSM-184 modules in a cluster 32
Initiator-Target-LUNs (ITLs) 1024
LUNs behind a target 32
Host and target ports in a cluster 128
Number of hosts per target 128
Tape backup groups per cluster 2
Volume groups in a tape backup group 4
Cisco Key Management Center ( of keys) 32K
Targets per switch that can be FC-redirected 32
25
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Deleting Cisco SME interfacesA Cisco SME interface can be deleted from the cluster only after theinterface is administratively shut-down and all related tasksassociated with the interface shut-down are complete
Cisco MDS 9124 and 9134 Multilayer fabric switchesThe Cisco MDS 9124 and 9134 Multilayer fabric switches do notsupport the following Cisco MDS SAN-OS features
IVR Remote Span Translative loop support FCCmdash no generation quench reaction only
In addition the following features have these limits
VSANs mdash 16 maximum SPAN mdash 1 session maximum
N-Port virtualization configuration limitsThe NPV features have maximum configuration limits Table 13shows the verified and maximum limits for the NPV switchesrunning NX-OS Release 5x
Maximum number of zones supported in Interop Mode 4In interop mode 4 the maximum number of zones that is supportedin an active zone set is 2047 due to limitations in the connectedvendor switch When IVR is used in interop mode 4 the maximumnumber of zones supported including IVR zones in the active zoneset is 2047 The limit for the maximum number of IVR zones perVSAN is 250 zones (two members per zone)
Table 13 NPV features limitations
Feature Verified limits Maximum limits
FLOGIs or F Disc per NPV port group 114 114
NPV switches per NPV core switch 105 105
FLOGIs per line card on NPV core switch 400 400
26 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
IPv6The management port on Cisco MDS switches supports oneuser-configured IPv6 address but does not supportauto-configuration of an IPv6 address
IP-ACL supportDo not apply IP-ACLs to only one member of a PortChannel groupApply IP-ACLs to the entire channel group
If IP-ACLs are already configured in a Gigabit Ethernet interface youcannot add this interface to a Ethernet PortChannel group
Refer to the Cisco MDS 9000 Family Configuration Guide
User RolesIn SAN-OS Release 33(x) and earlier when a user belongs to a rolewhich has a VSAN policy set to Deny and the role allows access to aspecific set of VSANs (for example 1 through 10) the user isrestricted from performing the configuration clear execute anddebug commands which had a VSAN parameter outside thisspecified set Beginning with NX-OS Release 41(1b) these users arestill prevented from performing configuration clear execute anddebug commands as before however they are allowed to performshow commands for all VSANs The ability to execute the showcommand addresses the following
In a network environment users often need to view informationin other VSANs even though they do not have permission tomodify configurations in those VSANs
This behavior makes Cisco MDS 9000 Series switches consistentwith other Cisco products such as Cisco Nexus 7000 Seriesswitches that exhibit the same behavior for those roles (whenthey apply to the VLAN policy)
27
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Using a RSA Version 1 Key for SSH Following an UpgradeFor security reasons NX-OS Release 42(x) and higher does notsupport RSA version 1 keys As a result if you upgrade from anearlier version that did support RSA version 1 keys and you hadconfigured a RSA version 1 key for SSH then you will not be able tolog in through SSH following the upgrade
If you have a RSA version 1 key configured for SSH beforeupgrading to NX-OS Release 42(x) or higher follow these steps
1 Disable SSH
2 Create RSA version 2 DSA keys
3 Enable SSH
4 Delete any RSA version 1 keys on any remote SSH clients andreplace the version 1 keys with the new version 2 keys from theswitch
Proceed with the upgrade to NX-OS Release 42(x) or higher
If you upgrade before disabling SSH and creating RSA version 2 keysfollow these steps
1 Open a Telnet session and log in through the console
2 Issue the no feature ssh command to disable SSH
3 Issue the ssh key rsa 1024 command to create RSA version 2 keys
4 Issue the feature ssh command to enable SSH
Applying Zone Configurations to VSAN 1In the setup script you can configure system default values for thedefault-zone to be permit or deny and you can configure defaultvalues for the zone distribution method and for the zone mode
These default settings are applied when a new VSAN is createdHowever the settings will not take effect on VSAN 1 because it existsprior to running the setup script Therefore when you need thosesettings for VSAN 1 you must explicitly issue the followingcommands
zone default-zone permit vsan 1 zoneset distribute full vsan 1 zone mode enhanced vsan 1
28 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
InterVSAN RoutingWhen using InterVSAN Routing (IVR) it is recommended to enableCisco Fabric Services (CFS) on all IVR-enabled switches Failure to doso may cause mismatched active zone sets if an error occurs duringzone set activation
RSPAN Traffic Not Supported on CTS Ports on 8-Gbps Switching ModulesAn inter-switch link (ISL) that is enabled for Cisco TrustSec (CTS)encryption must be brought up in non-CTS mode to support remoteSPAN (RSPAN) traffic on the following modules
DS-X9248-96K9 Cisco MDS 9000 48-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9224-96K9 Cisco MDS 9000 24-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9248-48K9 Cisco MDS 9000 444-Port Host-Optimized8-Gbps Fibre Channel Switching Module
If the ISL link is brought up with CTS enabled random packets dropsof both RSPAN traffic and normal traffic will occur on the receiverport switch
IO Accelerator Feature LimitationsIOA does not support the following NX-OS features
IVR flows
Devices with NPV and NPIV enabled
F port trunking
bull F port channeling
Support for FCIP Compression ModesIn Cisco NX-OS Release 42(1b) and higher FCIP compression mode 1and compression mode 3 are not supported on the Cisco MSM-184module and on the SSN-16 module
29
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Saving Copies of the Running Kickstart and System ImagesAfter you upgrade to MDS NX-OS Release 42(1b) or higher you arenot allowed to delete rename move or overwrite the kickstart andsystem images that are in the current system bootvar settings on anactive or standby MDS Supervisor-2 module on any Cisco MDS 9500Series switch This restriction does not apply to the integratedsupervisor module on the MDS 9200 and MDS 9100 series switches
Configuring Buffer Credits on a Generation 2 or Generation 3 ModuleWhen you configure port mode to auto or E on a Generation 2module one of the ports will not come up for the followingconfiguration
Port Mode auto or E for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E on a Generation 3module one or two of the ports will not come up for the followingconfiguration
Port Mode auto or E for the first half of the ports the second halfof the ports or for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E for all ports in the globalbuffer pool you need to reconfigure buffer credits on one or more ofthe ports The total number of buffer credits configured for all theports in the global buffer pool should be reduced by 64
Storage services module power budgetThe MDS 9509 does not have the power budget to run seven SSMcards EMC recommends a maximum of four SSMs in one 9509Customers wishing to use more than four SSMs in one chassis shouldrefer to the Cisco MDS 9000 documentation on the Ciscocom websiteto validate that there is enough power available for their desiredconfiguration
30 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Note Upgrading to the 3000 watt power supplies will alleviate thiscondition
iSCSI proxy initiator in Celerra HighRoad environmentsEMC supports the iSCSI proxy initiator feature in Celerrareg
HighRoadreg environments In proxy initiator mode one Fibre Channelinitiator is used for all iSCSI clients who access the switch via thesame iSCSI interface (iscsi33 for example)
The initiators will use the PWWN assigned to the iSCSI interface TheiSCSI interface to which an iSCSI client will logon to is configured inthe client and must be permitted by the virtual target configured forthat initiator
The current session environment supported on the MDS is
300 sessions per port 1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no InitialR2T=yes
Refer to the specific initiator support documentation on how to setthe parameters The implementation will not perform properly ifthese bits are not set
Refer to the MDS documentation for more information regarding theconfiguration of the iSCSI proxy initiator at the following Ciscowebsite
httpwwwciscocomenUSproducts
HPUX N_port IDThe N_port ID port value of 255 (0xFF) has special meaning forHP-UX A N_port ID (FC_ID) can not be returned from a switch thatcontains this value for the N_port ID (FC_ID) port value for a HP-UXinitiator or HP-UX target port Port ID value of 255 (0xFF) cannot be
31
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
configured for HP-UX initiator port and HP-UX target ports whenconfiguring MDS FC_IDs The port_ID value is the third byte of theFC_ID
Interoperability limitationsRefer to the EMC Support Matrix (ESM) and the EMC Networked Storage Topology Guide for modes of operation and caveats
NASBThe NASB feature requires that the backup application load the tapedrive with a compatible tape cartridge prior to configuring NASB inthe backup VSAN
Reserved VSAN Range and Isolated VSAN Range GuidelinesOn an NPV switch with a trunking configuration on any interface or ona regular switch where the feature fport_channel_trunk command hasbeen issued to enable the F PortChannel feature follow theseconfiguration guidelines for reserved VSANs and the isolated VSAN
bull If trunk mode is on for any of the interfaces or NP PortChannelis up the reserved VSANs are 3040 to 4078 and they are notavailable for user configuration
bull The Exchange Virtual Fabric Protocol (EVFP) isolated VSAN is4079 and it is not available for user configuration
bull VSAN 4079 will be impacted by an upgrade to NX-OS Release42(3) depending on whether or not VSAN 4079 was createdprior to the upgrade See theldquoUpgrading Effect on VSAN 4079rdquoon page 17
The following VSAN IDs are assigned in the Fibre Channel Framingand Signaling (FC-FS) interface standard
VF_ID Value Value Description
00h Do not use as a Virtual FabricIdentifier
001h EFFh Available as a Virtual FabricIdentifier
F00h FEEh Reserved
32 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Symmetrix VMax limitationsAt the time of this writing the following features are not supportedfor use with the Symmetrix VMax
FCIP Write Acceleration
The NX-OS IOA functionality is only supported with the Q2 SREnginuity release 5874229182 or higher
For the most up to date status please refer to the current revision ofthese Release Notes on httpPowerlinkemccom and the EMCSupport Matrix available through E-Lab Interoperability Navigator (ELN) athttpelabnavigatorEMCcom
Storage Applications on the MSM-184The MDS 9000 184-Port Multiservice Module (MSM-184) does notsupport multiple concurrent storage applications Only oneapplication can run on the MSM-184 at a time
Downgrading with fport-channel-trunk enabledIf you are running MDS NX-OS Release 42(x) or higher with thefport-channel-trunk feature enabled and you downgrade to anyNX-OS 41(1x) release the installer performs a nondisruptivedowngrade even though the fport-channel-trunk feature is notsupported in NX-OS 41(1x) releases
As a result the switch is in an inconsistent state and the ports maynot function properly
FEFh Control VF-ID (see FibreChannel Link Services (FC-LS)and Fibre Channel SwitchFabric Generation 4 (FC-SW-4)standards)
FF0h FFEh Vendor specific
FFFh Do not use as a Virtual FabricIdentifier
FEFh = 4079
33
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
If you are in this state a workaround is to reboot the switch followingthe upgrade
LDAP AuthenticationThere is currently a limitation in the LDAP server configuration CLIthat prevents the use of an OU with spaces in the name Normallythese OU names could be surrounded by quotation marks howeverquotation marks are not supported by the ldap-server command
MDS-9148 limitationsThe Cisco MDS 9148 Multilayer Fabric Switch does not support thefollowing NX-OS features
Medium and Long range 4GB Agilent
IVR
Remote Span
Translative loop support
FCC - no generation quench reaction only
FC-Redirect
In addition the following features have these limits
VSANS - 31 maximum
SPAN - 1 session maximum
Technical notesThe following sections provide further information on technicalnotes
EMC Email Home for Cisco MDS switchesInstallation and Trouble shooting instructions can be found in thedocumentation located at the EMC Customer Service Internalwebsite
httpwwwcsisusemccomcsweb2esnesnhomehtmConnectrix20MDS20900020Family
34 EMC Connectrix MDS 9000 NX-OS Release Notes
Technical notes
Customers requiring installation of this solution should contact theirEMC Customer Engineer to assist with the installation and providethe documentation
Supported iSCSI sessionsThe current iSCSI session environment supported on the MDS is
300 sessions per port
1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no
InitialR2T=yes
Upgrading Cisco SAN-OSThere are several methods available for upgrading SAN-OS SoftwareEMC personnel are strongly recommended that all upgrades be doneby the Automated One-Step Upgrade using the install all
command EMC personnel should refer to the Connectrix MDS 9000Family Software Image Upgrade Instructions for a complete list ofprerequisites and instructions for performing the upgrade Thisdocument along with tftp software is available on the GlobalServices website at httpwwwcsisusEMCcom under ApplicationDownload Area ESN Product Information Connectrix MDS 9000Family
The Software Upgrade Wizard is an option for upgrades While theinstall all is the preferred method the Software Install Wizard canalso be used
Supported configuration parametersFor the most up-to-date information refer to the EMC Support Matrixavailable through E-Lab Interoperability Navigator athttpelabnavigatoremccom for the latest information onsupported configurations
35
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
Supported zoning parametersRefer to the EMC Networked Storage Topology Guide for the mostup-to-date information on supported zoning parameters
At the time these notes were published the following parameterswere supported
20 VSANs 5 Hops 2000 Unique members per physical infrastructure 1000 Zonesets per physical infrastructure 2000 Zones per physical infrastructure 1 FCIP tunnel
Supported IVR parameters IVR zone members 1000 IVR zones 1000 IVR zone sets 32 VSANS 20 IVR enabled switches 64
An RPQ can be submitted for any configurations that exceed thislimit
Managing zone changes in multiswitch fabricsZoning changes may be made through Fabric Manager or CLI Whenaccessing Fabric Manager or CLI the user does so from the point ofview of one switch That is Fabric Manager and CLI are accessed byentering the IP address of one switch in the fabric
When zoning changes are made the applicable VSAN and zone setdata is propagated to the rest of the switches in the fabric via the ISLs
When zoning changes are made to a VSAN the zone set data ispropagated to the rest of the switches in the fabric via the ISLs Bydefault only the active zone set information is relayed to all switchesin the VSAN If the user accesses the Fabric Manager and CLI fromanother switch in the fabric the new VSAN and zone set informationwill not be viewable To view the active and inactive zone set on theother switches in the fabric the user must log in to the CLI and issuea command from the EXEC prompt
36 EMC Connectrix MDS 9000 NX-OS Release Notes
Documentation
Example The following is an example of copying VSAN 1 through 20 zoningdata
CiscoMDS_name zone copy active full vsan 1-20
CiscoMDS_name conf t
Enter configuration commands one per line End with CNTL Z
CiscoMDS_name(config) zoneset distribute full vsan 1-20
CiscoMDS_name(config)
Note This command needs to be issued on all switches in the fabric one timeonly
This is a nondisruptive command After issuing the commands theuser will now see the active and inactive zone sets for the specifiedVSANs on any switch that is chosen from which to manage the fabric
After a zoning change is made save the running configuration to thestartup configuration
DocumentationSend documentation comments to mdsfeedback-doccom
Product DocumentationAs of NX-OS Release 42(1a) software configuration information isavailable in new feature-specific configuration guides for thefollowing information
System management
Interfaces
Fabric
Quality of service
Security
IP services
High availability and redundancy
37
Software media organization and files
EMC Connectrix MDS 9000 NX-OS Release Notes
The information in these new guides previously existed in the CiscoMDS 9000 Family CLI Configuration Guide That configuration guideremains available on Ciscocom and should be used for all softwarereleases prior to NX-OS Release 42(1a) Configuration guidesaddress the features introduced in or available in a particular releaseSelect and view the configuration guide that pertains to the softwareinstalled in your switch
In addition Fabric Manager information has been removed from theMDS NX-OS Release Notes (this document) and placed intostandalone Fabric Manager Release Notes that support both CiscoMDS 9000 Family switches and Cisco Nexus 5000 Series switchesThe Cisco Fabric Manager Release Notes are available onhttpPowerlinkemccom and from the following website
httpwwwciscocomenUSpartnerproductsps10495prod_release_notes_listhtml
Technical supportThese release notes complement a Cisco documentation set EachCisco document refers to where to get help However for any itemssupplied by EMC see ldquoTroubleshooting and getting helprdquo onpage 38
Software media organization and filesFor information on related software environment and systemrequirements refer to the EMC Support Matrix on EMC Powerlink at
httpPowerlinkEMCcom
InstallationFor hardware installation information refer to the Cisco MDS HWInstallation Guides available at Ciscocom
For EMC-specific installation information refer to ldquoEnvironment andsystem requirementsrdquo on page 5 in this document
38 EMC Connectrix MDS 9000 NX-OS Release Notes
Troubleshooting and getting help
Troubleshooting and getting helpEMC support product and licensing information can be obtained asfollows
Product information mdash For documentation release notes softwareupdates or for information about EMC products licensing andservice go to the EMC Powerlink website (registration required) at
httpPowerlinkEMCcom
Technical support mdash For technical support go to EMC CustomerService on Powerlink To open a service request through Powerlinkyou must have a valid support agreement Please contact your EMCsales representative for details about obtaining a valid supportagreement or to answer any questions about your account
Copyright copy 2011 EMC Corporation All rights reserved
EMC believes the information in this publication is accurate as of its publication date The information issubject to change without notice
THE INFORMATION IN THIS PUBLICATION IS PROVIDED ldquoAS ISrdquo EMC CORPORATION MAKES NOREPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION INTHIS PUBLICATION AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OFMERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Use copying and distribution of any EMC software described in this publication requires an applicablesoftware license
For the most up-to-date regulatory document for your product line go to the Technical Documentation andAdvisories section on EMC Powerlink
For the most up-to-date listing of EMC product names see EMC Corporation Trademarks on EMCcom
All other trademarks used herein are the property of their respective owners
5
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
httpwwwciscocomenUSpartnerproductsps10495prod_release_notes_listhtml
Note Cisco makes all release notes past and present available on thiswebsite
Environment and system requirementsThis section describes the system requirements for MDS NX-OSRelease 50(4b) and includes the following topics
Hardware Supported and Minimum Software Required Determining the Software Version Upgrade Prerequisites Software Upgrade Mechanisms Image Upgrade Matrix Best Practices Maximum ports per Chassis
Telco 2 post racksNote that the 9509 and 9513 should not be used in a 2 post Telco rackdue to weight considerations Refer to the Cisco MDS 9000 HardwareInstallation Guides on httpwwwciscocom for more information
EC-1700 configuration informationConfiguration information appears in the Connectrix EC-1700 CabinetInstallation and Setup Manual on the EMC Powerlinkreg website
Note Currently only the MDS 9509 and 9513 are supported in the EC-1700-Ccabinet The MDS 9124 is not supported in the EC-1700-C
8Gb Power RequirementsEven though Cisco director class models may operate at 100 to 240VAC in configurations consisting of 8 Gb modules 200-240 VAC ishighly recommended Operating at lower voltages will decrease thenumber of modules that may be installed in your chassis
6 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
For more information on power requirements please refer toAppendix C of the Cisco MDS 9500 Series Hardware Installation Guide
Hardware and software componentsEMC supported hardware and software modules are listed in CiscoNX-OS 50(4b) release notes located on the Cisco web site
Note Table 1 lists the MDS 9000 Family software and hardware componentsthat are not supported by EMC as well as the comparable NX-OS partnumbers
For older NX-OS part numbers see prior existing versions of SAN OSrelease notes
Table 1 MDS 9000 Family software and hardware modules not supported(page 1 of 2)
Component EMC part number Description Applicable products
Service modules DS-X9304-18FK9 18-port Fibre Channel4-port GigabitEthernet Multiservice FIPS (MSFM-184)module
MDS 9500 Series and9200 Series
Optics DS-X2-FC10G-ER X2SC optics 10-Gbps Fibre Channel forExtended Reach (40 km)
MDS 9500 Series and9200 Series exceptfor the MDS 9216
DS-X2-E10G-SR X2SC optics 10-Gbps Ethernet for ShortReach
DS-X2-FC10G_CX4 X2CX-4 optics 10-Gbps Fibre Channelcopper
LC-type fiber-optic SFP DS-SFP-GE-T 1-Gbps Ethernet SFP MDS 9000 Family
CWDM DS-CWDM-xxxx Gigabit Ethernet and 4-Gbps FibreChannel SFP LC interface xxxx nmwhere xxxx = 1470 1490 1510 15301550 1570 1590 or 1610 nm
DS-CWDM-MUX-4 Adddrop multiplexer for four CWDMwavelengths
DS-CWDM-MUX-8 Adddrop multiplexer for eight CWDMwavelengths
DS-CWDMCHASSIS Two slot chassis for CWDM adddropmultiplexers
7
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Note EMC personnel can obtain a complete list of Cisco part numbers fromthe Product Support Bulletins available under the ProductTechnicalInformation section of the EMC Global Services website athttpwwwcsisusEMCcomMyGSiVisitURLaspurl=10137
Support for the Generation 3 ModulesThe MDS 9513 Director requires Cisco MDS NX-OS 41(1b) or laterand the MDS 9513 Fabric 2 modules to support the MDS 9000 48-port8-Gbps Fibre Channel module and the MDS 9000 24-port 8-GbpsFibre Channel module
The MDS 9513 Director requires Cisco MDS NX-OS 41(1b) or laterbut does not require the MDS 9513 Fabric 2 modules to support theMDS 9000 444-port 8-Gbps Host-optimized Fibre Channel module
The MDS 9509 Director and the MDS 9506 Director also support theGeneration 3 8-Gbps modules The switches require Supervisor-2modules and Cisco MDS NX-OS 41(1b) or above to support theGeneration 3 8-Gbps modules
For information on the tasks associated with readying the MDS 9500Series to support Generation 3 8-Gbps Fibre Channel switchingmodules refer to the Migrating to Generation 3 Modules appendix inthe Cisco MDS 9500 Series Hardware Installation Guide It presents anoverview of the Generation 3 8-Gbps modules provides usageguidelines for the modules and describes three procedures formigrating hardware and upgrading software to enable use of thesemodules in an MDS 9513 Director
For information on replacing the MDS 9513 Fabric 1 modules withFabric 2 modules refer to the Migrating to Generation 3 Modulesappendix in the Cisco MDS 9500 Series Hardware Installation Guide Itprovides information on installing new Fabric 2 modules while
Port analyzer adapter DS-PAA-2 DS-PAA A standalone Fibre Channel-to-Ethernetadapter that allows for simple transparentanalysis of Fibre Channel traffic in aswitched fabric
MDS 9000 Family
Table 1 MDS 9000 Family software and hardware modules not supported(page 2 of 2)
Component EMC part number Description Applicable products
8 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
running NX-OS Release 4x and SAN-OS Release 3x It also providesinformation on installing the MDS 9513 Fabric 2 modules andactivating higher bandwidth
Configuring Generation 3 and Generation 2 Switching ModulesThe Cisco MDS 9500 Multilayer Directors are designed to operatewith any combination of Cisco MDS 9000 Generation 2 andGeneration 3 modules However there are limitations to considerwhen combining the various modules and supervisors in the CiscoMDS 9500 Series platform chassis The references listed in this sectionprovide specific information about configurations that combinedifferent modules and supervisors
For information on configuring Generation 2 and Generation 3switching modules refer to the Configuring Generation 2 andGeneration 3 Switching Modules chapter in the Cisco MDS 9000Family CLI Configuration Guide
For information on port index availability refer to the ldquoPort IndexAvailabilityrdquo section in the Product Overview chapter of the CiscoMDS 9500 Series Hardware Installation Guide
For information on Cisco MDS 9000 hardware and softwarecompatibility refer to the EMC Support Matrix available through E-LabInteroperability Navigator (ELN) at httpelabnavigatorEMCcom
MDS 9000 Chassis and Module Support in Cisco MDS NX-OS 5xTable 2 lists the MDS hardware chassis supported by Cisco MDSNX-OS 5x
Table 2 Cisco MDS NX-OS 5x Chassis Support Matrix
Switch NX-OS 5x Support
MDS 9513 Yes
MDS 9509 Yes
MDS 9506 Yes
MDS 9222i Yes
MDS 9216i No
9
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Table 3 lists the MDS hardware modules supported by Cisco MDSNX-OS 5x
MDS 9216A No
MDS 9216 No
MDS 9148 Yes
MDS 9134 Yes
MDS 9124 Yes
MDS 9140 No
MDS 9120 No
Table 2 Cisco MDS NX-OS 5x Chassis Support Matrix
Switch NX-OS 5x Support
Table 3 Module Support Matrix for Cisco MDS NX-OS 5x (page 1 of 2)
Module DescriptionMDS 9500Series MDS 9222i
DS-X9530-SF2A-K9 MDS 9500 Supervisor-2A Module Yes NA
DS-X9530-SF2-K9 MDS 9500 Supervisor-2 Module Yes NA
DS-X9530-SF1-K9 MDS 9500 Supervisor-1 Module No NA
DS-X9224-96K9 24-port 8-Gbps Fibre Channel Switching Module Yesa No
DS-X9248-96K9 48-port 8-Gbps Fibre Channel Switching Module Yesa No
DS-X9248-48K9 444-port Host Optimized 8-Gbps Fibre ChannelSwitching Module
Yes Yes
DS-X9316-SSNK9 16-Port Storage Services Node (SSN-16) Yes Yes
DS-X9304-18K9 184-Port Multiprotocol Services Module(MSM-184)
Yes Yes
DS-X9112 12-port 4-Gbps Fibre Channel Switching Module Yes Yes
DS-X9124 24-port 4-Gbps Fibre Channel Switching Module Yes Yes
DS-X9148 48-port 4-Gbps Fibre Channel Switching Module Yes Yes
DS-X9704 4-port 10-Gbps Fibre Channel Switching Module Yes Yes
10 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Migrating from Supervisor-1 Modules to Supervisor-2 ModulesAs of Cisco MDS SAN-OS Release 30(1) the Cisco MDS 9509 and9506 Directors support both Supervisor-1 and Supervisor-2 modulesSupervisor-1 and Supervisor-2 modules cannot be installed in thesame switch except during migration Both the active and standbysupervisor modules must be of the same type either Supervisor-1 orSupervisor-2 modules For Cisco MDS 9513 Directors bothsupervisor modules must be Supervisor-2 modules
CAUTION
Migrating your supervisor modules is a disruptive operation
Note Migrating from Supervisor-2 modules to Supervisor-1 modules is not supported
To migrate from a Supervisor-1 module to a Supervisor-2 module refer to the step-by-step instructions in the Cisco MDS 9000 NX-OS Release 41(x) and SAN-OS 3(x) Software Upgrade and Downgrade Guide
DS-X9302-14K9 142-port Multiprotocol Services (MPS-142)Module
No No
DS-X9016 16-port 1- 2-Gbps Fibre Channel SwitchingModule
No No
DS-X9032 32-port 1- 2-Gbps Fibre Channel SwitchingModule
No No
DS-X9032-SSM 32-port Storage Services Module (SSM) No No
DS-X9308-SMIP 8-port 1- 2-Gbps IP Switching Module No No
DS-X9304-SMIP 4-port 1- 2-Gbps IP Switching Module No No
a Requires DS-13SLT-FAB2 in the MDS 9513
Table 3 Module Support Matrix for Cisco MDS NX-OS 5x (page 2 of 2)
Module DescriptionMDS 9500Series MDS 9222i
11
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Software Download ProcessUse the software download procedure to upgrade to a later versionor downgrade to an earlier version of an operating system Thissection describes the software download process for the Cisco MDSNX-OS software and includes the following topics
ldquoDetermining the Software Versionrdquo on page 11
ldquoDownloading Softwarerdquo on page 11
ldquoSelecting the Correct Software Image for an MDS 9100 SeriesSwitchrdquo on page 12
ldquoSelecting the Correct Software Image for an MDS 9200 SeriesSwitchrdquo on page 13
ldquoSelecting the Correct Software Image for an MDS 9500 SeriesSwitchrdquo on page 13
Determining the Software VersionTo determine the version of Cisco MDS NX-OS or SAN-OS softwarecurrently running on a Cisco MDS 9000 Family switch using the CLIlog in to the switch and enter the show version EXEC command
To determine the version of Cisco MDS NX-OS or SAN-OS softwarecurrently running on a Cisco MDS 9000 Family switch using theFabric Manager view the Switches tab in the Information pane locatethe switch using the IP address logical name or WWN and check itsversion in the Release column
Note EMC strongly recommends that you use the latest qualified softwarerelease for all MDS 9000 Family products Refer to the EMC Support Matrixavailable through E-Lab Interoperability Navigator (ELN) athttpelabnavigatorEMCcom for the latest information on qualifiedfirmware revisions
Downloading SoftwareThe Cisco MDS NX-OS software is designed for mission-critical highavailability environments To realize the benefits of nondisruptiveupgrades on the Cisco MDS 9500 Directors we highly recommendthat you install dual supervisor modules
12 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Before performing upgrades submit all requested changes to theEMC Global Services CCA change control process so that anypotential operating environment impacts can be analyzedbeforehand
EMC personnel should also refer to the Connectrix MDS 9000 FamilySoftware Image Upgrade Instructions for a complete list of prerequisitesThis document is available on the Global Services websitehttpwwwcsisusEMCcom under Application Download AreaESN Product Information Connectrix MDS 9000 Family EMCpersonnel can download the Software Images from the GlobalServices website httpwwwcsisusEMCcom under ApplicationDownload Area ESN Product Information Connectrix MDS 9000Family
See the following sections in this release note for details on how youcan nondisruptively upgrade your Cisco MDS 9000 switch Issuingthe install all command from the CLI or using Fabric Manager toperform the downgrade enables the compatibility check The checkindicates if the upgrade can happen nondisruptively or disruptivelydepending on the current configuration of your switch and thereason
Compatibility check is doneModule bootable Impact Install-type Reason------ -------- -------------- ------------ ------
1 yes non-disruptive rolling2 yes disruptive rolling Hitless upgrade is not supported3 yes disruptive rolling Hitless upgrade is not supported4 yes non-disruptive rolling5 yes non-disruptive reset6 yes non-disruptive reset
Selecting the Correct Software Image for an MDS 9100 Series SwitchThe system and kickstart image that you use for an MDS 9100 seriesswitch depends on which switch you use as shown in Table 4
Table 4 Software Images for MDS 9100 Series Switches
Cisco MDS 9100 Series Switch Type Naming Convention
9124 and 9134 Filename begins with m9100-s2ek9
9148 Filename begins with m9100-s3ek9
13
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Selecting the Correct Software Image for an MDS 9200 Series SwitchThe system and kickstart image that you use for an MDS 9200 seriesswitch depends on which switch you use as shown in Table 5
Selecting the Correct Software Image for an MDS 9500 Series SwitchThe system and kickstart image that you use for an MDS 9500 Seriesswitch depends on whether the switch is based on a Supervisor-1module or a Supervisor-2 module as shown in Table 6
Use the show module command to display the type of supervisormodule in the switch The following is sample output from the showmodule command on a Supervisor 2 module
Table 5 Software Images for MDS 9200 Series Switches
Cisco MDS 9200 Series Switch Type Naming Convention
9222i Filename begins with m9200-s2ek9
Table 6 Software Images for Supervisor Type
Cisco MDS 9500 Series Switch Type Supervisor Module Type Naming Convention
9513 9509 and 9506 Supervisor-2 module Filename begins with m9500-sf2ek9
14 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
switch show moduleMod Ports Module-Type Model Status--- ----- -------------------------------- ------------------ ------------7 0 SupervisorFabric-2 DS-X9530-SF2-K9 active 8 0 SupervisorFabric-2 DS-X9530-SF2-K9 ha-standby
Upgrading Your Cisco MDS NX-OS Software ImageThis section lists the guidelines recommended for upgrading yourCisco MDS NX-OS software image and includes the following topics
ldquoGeneral Upgrading Guidelinesrdquo on page 14
ldquoDowngrading Your Cisco MDS SAN-OS Software Imagerdquo onpage 18
Note Before you begin the upgrade process review the list of chassis andmodules that NX-OS Release 50(4b) supports See the ldquoMDS 9000 Chassisand Module Support in Cisco MDS NX-OS 5xrdquo on page 8
Note For detailed instructions for performing a software upgrade usingCisco Fabric Manager see the Cisco Fabric Manager Release Notes forRelease 50(4b) which is available from the following websitehttpPowerlinkEMCcom
General Upgrading Guidelines
Note To upgrade to NX-OS Release 50(4b) you must be running NX-OSRelease 4x If you are running SAN-OS Release 32(3a) or earlier firstupgrade to SAN-OS Release 33(x) then NX-OS Release 4x and thenupgrade to NX-OS Release 50(4b)
Use the following guidelines when upgrading to Cisco MDS NX-OSRelease 5x
Install and configure dual supervisor modules
Issue the show install all impact upgrade-image CLI command todetermine if your upgrade will be nondisruptive
15
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Be aware of the impact of an upgrade on VSAN 4079 if you areupgrading from SAN-OS Release 3x to NX-OS 50(4b) See theldquoUpgrading Effect on VSAN 4079rdquo on page 17
Follow the recommended guidelines for upgrading a Cisco MDS9124 or MDS 9134 Switch as described in ldquoUpgrading a CiscoMDS 9124 or MDS 9134 switchrdquo on page 18
Take note of the affect of upgrades on MDS 9500 series switchesthat have active IOA flows as described in ldquoMDS 9500 seriesupgrades with active IOA flowsrdquo on page 18
Be aware that some features impact whether an upgrade isdisruptive or nondisruptive
bull Fibre Channel Ports Traffic on Fibre Channel ports can benondisruptively upgraded See Table 7 on page 16 for thenondisruptive upgrade path for all NX-OS and SAN-OSreleases
bull Storage Services Intelligent storage services traffic such asSANTap NASB and FC write acceleration is disruptedduring an upgrade Fibre Channel traffic is not
bull Gigabit Ethernet Ports Traffic on Gigabit Ethernet ports isdisrupted during an upgrade or downgrade This includes theGigabit Ethernet ports on the MSM-184 module and the MDS9222i switch Those nodes that are members of VSANs traversingan FCIP ISL are impacted and a fabric reconfiguration occursiSCSI initiators connected to the Gigabit Ethernet ports loseconnectivity to iSCSI targets while the upgrade is in progress
bull FICON If you have FICON enabled the upgrade path isdifferent See Table 6 on page 13
Use Table 7 to determine your nondisruptive upgrade path to Cisco MDSNX-OS Release 50(4b) find the image release number you are currentlyusing in the Current column of the table and use the path recommended
16 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Note The software upgrade information in Table 7 applies only to FibreChannel switching traffic Upgrading system software disrupts IP traffic andSSM intelligent services traffic
MDS NX-OS Release 50(4b) is not a FICON-qualified release
Table 7 Nondisruptive Upgrade Path to Cisco MDS NX-OS Release 50(4b)
Current Nondisruptive Upgrade Path
NX-OS 50(4) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 50(1a) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(7b) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(5) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(3) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(1b) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(1a) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 41(3a) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 41(1b) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
SAN-OS 33(4a) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
NX-OS 33(4) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 33(3) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 33(2) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 33(1c) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 32(3a) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 32(2c) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 32(1a) Upgrade to SAN-OS Release then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 31(3a) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 31(2) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
17
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Use Table 8 to determine your FICON nondisruptive upgrade path toCisco MDS NX-OS Release 42(7b) Find the image release numberyou are currently using in the Current Release with FICON Enabledcolumn of the table and use the path recommended
Note For more information on the FICON qualified NX-OS releases refer tothe EMC Support Matrix available through E-Lab Interoperability Navigator(ELN) at httpelabnavigatorEMCcom
Upgrading Effect on VSAN 4079If you are upgrading to NX-OS Release 50(4b) and you have notcreated VSAN 4079 the NX-OS software will automatically createVSAN 4079 and reserve it for EVFP use If VSAN 4079 is reserved forEVFP use the switchport trunk allowed vsan command will filterout VSAN 4079 from the allowed list as shown in the followingexample
switch(config-if) switchport trunk allowed vsan1-40801-40784080switch(config-if)
If you have created VSAN 4079 the upgrade to NX-OS Release50(4b) will have no affect on VSAN 4079
If you downgrade to a release of NX-OS lower than 41(x) afterNX-OS Release 50(4b) creates VSAN 4079 and reserves it for EVFPuse the VSAN will no longer be reserved
Table 8 FICON Nondisruptive Upgrade Path to NX-OS Release 42(7b)
Current Release withFICON Enabled Upgrade Path
NX-OS 42(1b) You can nondisruptively upgrade directly to NX-OS Release 42(7b)
NX-OS 41(1c) You can nondisruptively upgrade directly to NX-OS Release 42(7b)
SAN-OS 33(1c) You can nondisruptively upgrade directly to NX-OS Release 42(7b)
18 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Upgrading a Cisco MDS 9124 or MDS 9134 switchIf you are upgrading from Cisco MDS SAN-OS Release 31(1) to CiscoNX-OS Release 4x before upgrading to NX-OS Release 50(4b) on aCisco MDS 9124 or MDS 9134 switch follow these guidelines
During the upgrade configuration is not allowed and the fabric isexpected to be stable
The Fabric Shortest Path First (FSPF) timers must be configured tothe default value of 20 seconds otherwise the nondisruptiveupgrade is blocked to ensure that the maximum down toim forthe control plane can be 80 seconds
If there are any CFS commits in the fabric the nondisruptiveupgrade will fail
If there is a zone server merge in progress in the fabric thenondisruptive upgrde will fail
If a service terminates the nondisruptive upgrade the showinstall all failure-reason command can display the reason thatthe nondisruptive upgrade cannot proceed
If there is not enough memory in the system to load the newimages the upgrade will be made disruptive due to insufficientresources and the user will be notified in the compativility table
MDS 9500 series upgrades with active IOA flowsWhen upgading an MDS 9500 series switch that has active IOA flowsthose flows may be interrupted during the supervisor moduleswitchover To workaround this issue you have to enablespanning-tree portfast on the interface on the catalyst connected tothe management interface of the activestandby supervisor for theinterface to come up fast without causing the cluster to lose quorum
Downgrading Your Cisco MDS SAN-OS Software ImageThis section lists the guidelines recommended for downgrading yourCisco MDS SAN-OS software image and includes the followingtopics
ldquoGeneral downgrading guidelinesrdquo on page 19
19
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
General downgrading guidelinesUse the following guidelines to nondisruptively downgrade yourCisco MDS NX-OS Release 50(4b)
Install and configure dual supervisor modules
Issue the system no acl-adjacency-sharing execute command todisable acl adjacency usage on Generation 2 and Generation 1modules If this command fails reduce the number of zones IVRzones TE ports or a combination of these in the system and issuethe command again
Disable all features not supported by the downgrade release Usethe show incompatibility system downgrade-image command todetermine what you need to disable
bull If you are running in interoperability mode two such featuresare the Reliable Commit Service and Full Zone DatabaseDistribution They can be disabled by running thesecommand in config term mode
no zone rcs enableno zoneset capability distribute full
Use the show install all impact downgrade-image command todetermine if your downgrade will be nondisruptive
Be aware that some features impact whether a downgrade isdisruptive or nondisruptive
bull Fibre Channel Ports Traffic on Fibre Channel ports can benondisruptively downgraded See Table 9 on page 20 for thenondisruptive downgrade path for all SAN-OS releases
bull Storage Services Intelligent storage services traffic such asSANTap NASB and FC write acceleration is disruptedduring a downgrade Fibre Channel traffic is not
bull Gigabit Ethernet Ports Traffic on Gigabit Ethernet ports isdisrupted during a downgrade This includes the GigabitEthernet ports on the MSM-184 module and the MDS 9222iswitch Those nodes that are members of VSANs traversing anFCIP ISL are impacted and a fabric reconfiguration occursiSCSI initiators connected to the Gigabit Ethernet ports loseconnectivity to iSCSI targets while the downgrade is inprogress
20 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
bull FICON If you have FICON enabled the downgrade path isdifferent See Table 10 on page 21
Note A downgrade from NX-OS Release 4x to SAN-OS Release 33(1c) is notsupported on MDS switches when FC-Redirect based applications such asData Mobility Manager or Storage Media Encryption are configured in thefabric if either of the following conditions are satisfied
1 A target for which FC-Redirect is configured is connected locally and thereare Generation 1 modules with ISLs configured in the switch
2 A host for which FC-redirect is configured is connected locally ona Generation 1 module
If these conditions exist remove the application configuration forthese targets and hosts before proceeding with the downgrade
Use Table 9 on page 20 to determine the nondisruptive downgradepath from Cisco NX-OS Release 50(4b) Find the NX-OS or SAN-OSimage you want to downgrade to in the To SAN-OSNX-OS Releasecolumn of the table and use the path recommended
Note The software downgrade information in Table 10 on page 21 appliesonly to Fibre Channel switching traffic Downgrading system softwaredisrupts IP and SSM intelligent services traffic
Table 9 Nondisruptive Downgrade Path from NX-OS Release 50(4b) (page 1 of2)
To SAN-OS NX-OSRelease Nondisruptive Downgrade Path
NX-OS 50(4) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 50(1a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(7b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(5) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(3) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(1b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(1a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 41(3a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
21
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Use Table 10 to determine your nondisruptive downgrade path if youhave FICON enabled from Cisco NX-OS Release 42(7b) Find the imagerelease number you are currently using in the Current Release withFICON Enabled column of the table and use the path recommended
NX-OS 41(1b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
SAN-OS 33(5a) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33())
SAN-OS 33(5) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(4a) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
NX-OS 33(4) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(3) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
NX-OS 33(2) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(1c) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 32(3a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 32(x)
SAN-OS 32(2c) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 32(x)
SAN-OS 32(1a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
SAN-OS 31(3a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
SAN-OS 31(2) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
Table 9 Nondisruptive Downgrade Path from NX-OS Release 50(4b) (page 2 of2)
To SAN-OS NX-OSRelease Nondisruptive Downgrade Path
Table 10 FICON Downgrade Path from NX-OS Release 42(7b)
To SAN-OSNX-OS Release withFICON Enabled Downgrade Path
NX-OS 42(1b) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
NX-OS 41(1c) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
SAN-OS 33(1c) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
22 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Best practicesLog messages are not saved across system reboots or power outagesTherefore EMC recommends that customers configure a SyslogServer in order to redirect and capture all log messages on a remoteserver For more information please refer to the Cisco MDS 9000Family Configuration Guide available at
httpwwwciscocomenUSproductsps5989products_support_series_homehtml
Maximum ports per chassisTable 11 shows the maximum ports per chassis
a V2 indicates a 9506 or 9509 with Generation-2 Supervisors The presence of anygeneration one module in a switch will limit the maximum port count to 252This includes the 16-port 32-port 14+2 IPS4 and IPS8 cards
Known problems and limitationsFor a list of problems with this release please refer to the CiscoRelease notes located at
httpwwwciscocomenUSproductsps5989prod_release_notes_listhtml
Limitations and restrictionsThe following limitations and restrictions apply to all switches in theCisco MDS 9000 Family unless a limitation for a specific switch isstated
ldquoStorage Media Encryption (SME) limitationsrdquo on page 24
Table 11 Maximum ports per chassis
Chassis Maximum number of ports
MDS 9506-V2 192a
MDS 9509-V2 336
MDS 9513 528
23
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
ldquoSME configuration limitsrdquo on page 24
ldquoDeleting Cisco SME interfacesrdquo on page 25
ldquoCisco MDS 9124 and 9134 Multilayer fabric switchesrdquo on page 25
ldquoN-Port virtualization configuration limitsrdquo on page 25
ldquoMaximum number of zones supported in Interop Mode 4rdquo onpage 25
ldquoIPv6rdquo on page 26
ldquoIP-ACL supportrdquo on page 26
ldquoUser Rolesrdquo on page 26
ldquoUsing a RSA Version 1 Key for SSH Following an Upgraderdquo onpage 27
ldquoApplying Zone Configurations to VSAN 1rdquo on page 27
ldquoInterVSAN Routingrdquo on page 28
ldquoRSPAN Traffic Not Supported on CTS Ports on 8-GbpsSwitching Modulesrdquo on page 28
ldquoIO Accelerator Feature Limitationsrdquo on page 28
ldquoSupport for FCIP Compression Modesrdquo on page 28
ldquoSaving Copies of the Running Kickstart and System Imagesrdquo onpage 29
ldquoConfiguring Buffer Credits on a Generation 2 or Generation 3Modulerdquo on page 29
ldquoStorage services module power budgetrdquo on page 29
ldquoiSCSI proxy initiator in Celerra HighRoad environmentsrdquo onpage 30
ldquoHPUX N_port IDrdquo on page 30
ldquoInteroperability limitationsrdquo on page 31
ldquoNASBrdquo on page 31
ldquoReserved VSAN Range and Isolated VSAN Range Guidelinesrdquoon page 31
ldquoSymmetrix VMax limitationsrdquo on page 32
ldquoStorage Applications on the MSM-184rdquo on page 32
ldquoDowngrading with fport-channel-trunk enabledrdquo on page 32
ldquoLDAP Authenticationrdquo on page 33
24 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
ldquoMDS-9148 limitationsrdquo on page 33
Storage Media Encryption (SME) limitationsAn SME node can only belong to one cluster Adding the node tomore than one cluster will cause problems
Currently there is no prevention or warning in place when an attemptis made to add a node to multiple clusters
SME configuration limitsTable 12 lists the SME configuration limits for this release
Table 12 SME configuration limits
Configuration Limits
Number of switches in the fabric 10
Number of clusters per switch 1
Switches in a cluster 4
Fabrics in a cluster 2
Modules in a switch 11
Cisco MSM-184 modules in a cluster 32
Initiator-Target-LUNs (ITLs) 1024
LUNs behind a target 32
Host and target ports in a cluster 128
Number of hosts per target 128
Tape backup groups per cluster 2
Volume groups in a tape backup group 4
Cisco Key Management Center ( of keys) 32K
Targets per switch that can be FC-redirected 32
25
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Deleting Cisco SME interfacesA Cisco SME interface can be deleted from the cluster only after theinterface is administratively shut-down and all related tasksassociated with the interface shut-down are complete
Cisco MDS 9124 and 9134 Multilayer fabric switchesThe Cisco MDS 9124 and 9134 Multilayer fabric switches do notsupport the following Cisco MDS SAN-OS features
IVR Remote Span Translative loop support FCCmdash no generation quench reaction only
In addition the following features have these limits
VSANs mdash 16 maximum SPAN mdash 1 session maximum
N-Port virtualization configuration limitsThe NPV features have maximum configuration limits Table 13shows the verified and maximum limits for the NPV switchesrunning NX-OS Release 5x
Maximum number of zones supported in Interop Mode 4In interop mode 4 the maximum number of zones that is supportedin an active zone set is 2047 due to limitations in the connectedvendor switch When IVR is used in interop mode 4 the maximumnumber of zones supported including IVR zones in the active zoneset is 2047 The limit for the maximum number of IVR zones perVSAN is 250 zones (two members per zone)
Table 13 NPV features limitations
Feature Verified limits Maximum limits
FLOGIs or F Disc per NPV port group 114 114
NPV switches per NPV core switch 105 105
FLOGIs per line card on NPV core switch 400 400
26 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
IPv6The management port on Cisco MDS switches supports oneuser-configured IPv6 address but does not supportauto-configuration of an IPv6 address
IP-ACL supportDo not apply IP-ACLs to only one member of a PortChannel groupApply IP-ACLs to the entire channel group
If IP-ACLs are already configured in a Gigabit Ethernet interface youcannot add this interface to a Ethernet PortChannel group
Refer to the Cisco MDS 9000 Family Configuration Guide
User RolesIn SAN-OS Release 33(x) and earlier when a user belongs to a rolewhich has a VSAN policy set to Deny and the role allows access to aspecific set of VSANs (for example 1 through 10) the user isrestricted from performing the configuration clear execute anddebug commands which had a VSAN parameter outside thisspecified set Beginning with NX-OS Release 41(1b) these users arestill prevented from performing configuration clear execute anddebug commands as before however they are allowed to performshow commands for all VSANs The ability to execute the showcommand addresses the following
In a network environment users often need to view informationin other VSANs even though they do not have permission tomodify configurations in those VSANs
This behavior makes Cisco MDS 9000 Series switches consistentwith other Cisco products such as Cisco Nexus 7000 Seriesswitches that exhibit the same behavior for those roles (whenthey apply to the VLAN policy)
27
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Using a RSA Version 1 Key for SSH Following an UpgradeFor security reasons NX-OS Release 42(x) and higher does notsupport RSA version 1 keys As a result if you upgrade from anearlier version that did support RSA version 1 keys and you hadconfigured a RSA version 1 key for SSH then you will not be able tolog in through SSH following the upgrade
If you have a RSA version 1 key configured for SSH beforeupgrading to NX-OS Release 42(x) or higher follow these steps
1 Disable SSH
2 Create RSA version 2 DSA keys
3 Enable SSH
4 Delete any RSA version 1 keys on any remote SSH clients andreplace the version 1 keys with the new version 2 keys from theswitch
Proceed with the upgrade to NX-OS Release 42(x) or higher
If you upgrade before disabling SSH and creating RSA version 2 keysfollow these steps
1 Open a Telnet session and log in through the console
2 Issue the no feature ssh command to disable SSH
3 Issue the ssh key rsa 1024 command to create RSA version 2 keys
4 Issue the feature ssh command to enable SSH
Applying Zone Configurations to VSAN 1In the setup script you can configure system default values for thedefault-zone to be permit or deny and you can configure defaultvalues for the zone distribution method and for the zone mode
These default settings are applied when a new VSAN is createdHowever the settings will not take effect on VSAN 1 because it existsprior to running the setup script Therefore when you need thosesettings for VSAN 1 you must explicitly issue the followingcommands
zone default-zone permit vsan 1 zoneset distribute full vsan 1 zone mode enhanced vsan 1
28 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
InterVSAN RoutingWhen using InterVSAN Routing (IVR) it is recommended to enableCisco Fabric Services (CFS) on all IVR-enabled switches Failure to doso may cause mismatched active zone sets if an error occurs duringzone set activation
RSPAN Traffic Not Supported on CTS Ports on 8-Gbps Switching ModulesAn inter-switch link (ISL) that is enabled for Cisco TrustSec (CTS)encryption must be brought up in non-CTS mode to support remoteSPAN (RSPAN) traffic on the following modules
DS-X9248-96K9 Cisco MDS 9000 48-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9224-96K9 Cisco MDS 9000 24-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9248-48K9 Cisco MDS 9000 444-Port Host-Optimized8-Gbps Fibre Channel Switching Module
If the ISL link is brought up with CTS enabled random packets dropsof both RSPAN traffic and normal traffic will occur on the receiverport switch
IO Accelerator Feature LimitationsIOA does not support the following NX-OS features
IVR flows
Devices with NPV and NPIV enabled
F port trunking
bull F port channeling
Support for FCIP Compression ModesIn Cisco NX-OS Release 42(1b) and higher FCIP compression mode 1and compression mode 3 are not supported on the Cisco MSM-184module and on the SSN-16 module
29
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Saving Copies of the Running Kickstart and System ImagesAfter you upgrade to MDS NX-OS Release 42(1b) or higher you arenot allowed to delete rename move or overwrite the kickstart andsystem images that are in the current system bootvar settings on anactive or standby MDS Supervisor-2 module on any Cisco MDS 9500Series switch This restriction does not apply to the integratedsupervisor module on the MDS 9200 and MDS 9100 series switches
Configuring Buffer Credits on a Generation 2 or Generation 3 ModuleWhen you configure port mode to auto or E on a Generation 2module one of the ports will not come up for the followingconfiguration
Port Mode auto or E for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E on a Generation 3module one or two of the ports will not come up for the followingconfiguration
Port Mode auto or E for the first half of the ports the second halfof the ports or for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E for all ports in the globalbuffer pool you need to reconfigure buffer credits on one or more ofthe ports The total number of buffer credits configured for all theports in the global buffer pool should be reduced by 64
Storage services module power budgetThe MDS 9509 does not have the power budget to run seven SSMcards EMC recommends a maximum of four SSMs in one 9509Customers wishing to use more than four SSMs in one chassis shouldrefer to the Cisco MDS 9000 documentation on the Ciscocom websiteto validate that there is enough power available for their desiredconfiguration
30 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Note Upgrading to the 3000 watt power supplies will alleviate thiscondition
iSCSI proxy initiator in Celerra HighRoad environmentsEMC supports the iSCSI proxy initiator feature in Celerrareg
HighRoadreg environments In proxy initiator mode one Fibre Channelinitiator is used for all iSCSI clients who access the switch via thesame iSCSI interface (iscsi33 for example)
The initiators will use the PWWN assigned to the iSCSI interface TheiSCSI interface to which an iSCSI client will logon to is configured inthe client and must be permitted by the virtual target configured forthat initiator
The current session environment supported on the MDS is
300 sessions per port 1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no InitialR2T=yes
Refer to the specific initiator support documentation on how to setthe parameters The implementation will not perform properly ifthese bits are not set
Refer to the MDS documentation for more information regarding theconfiguration of the iSCSI proxy initiator at the following Ciscowebsite
httpwwwciscocomenUSproducts
HPUX N_port IDThe N_port ID port value of 255 (0xFF) has special meaning forHP-UX A N_port ID (FC_ID) can not be returned from a switch thatcontains this value for the N_port ID (FC_ID) port value for a HP-UXinitiator or HP-UX target port Port ID value of 255 (0xFF) cannot be
31
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
configured for HP-UX initiator port and HP-UX target ports whenconfiguring MDS FC_IDs The port_ID value is the third byte of theFC_ID
Interoperability limitationsRefer to the EMC Support Matrix (ESM) and the EMC Networked Storage Topology Guide for modes of operation and caveats
NASBThe NASB feature requires that the backup application load the tapedrive with a compatible tape cartridge prior to configuring NASB inthe backup VSAN
Reserved VSAN Range and Isolated VSAN Range GuidelinesOn an NPV switch with a trunking configuration on any interface or ona regular switch where the feature fport_channel_trunk command hasbeen issued to enable the F PortChannel feature follow theseconfiguration guidelines for reserved VSANs and the isolated VSAN
bull If trunk mode is on for any of the interfaces or NP PortChannelis up the reserved VSANs are 3040 to 4078 and they are notavailable for user configuration
bull The Exchange Virtual Fabric Protocol (EVFP) isolated VSAN is4079 and it is not available for user configuration
bull VSAN 4079 will be impacted by an upgrade to NX-OS Release42(3) depending on whether or not VSAN 4079 was createdprior to the upgrade See theldquoUpgrading Effect on VSAN 4079rdquoon page 17
The following VSAN IDs are assigned in the Fibre Channel Framingand Signaling (FC-FS) interface standard
VF_ID Value Value Description
00h Do not use as a Virtual FabricIdentifier
001h EFFh Available as a Virtual FabricIdentifier
F00h FEEh Reserved
32 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Symmetrix VMax limitationsAt the time of this writing the following features are not supportedfor use with the Symmetrix VMax
FCIP Write Acceleration
The NX-OS IOA functionality is only supported with the Q2 SREnginuity release 5874229182 or higher
For the most up to date status please refer to the current revision ofthese Release Notes on httpPowerlinkemccom and the EMCSupport Matrix available through E-Lab Interoperability Navigator (ELN) athttpelabnavigatorEMCcom
Storage Applications on the MSM-184The MDS 9000 184-Port Multiservice Module (MSM-184) does notsupport multiple concurrent storage applications Only oneapplication can run on the MSM-184 at a time
Downgrading with fport-channel-trunk enabledIf you are running MDS NX-OS Release 42(x) or higher with thefport-channel-trunk feature enabled and you downgrade to anyNX-OS 41(1x) release the installer performs a nondisruptivedowngrade even though the fport-channel-trunk feature is notsupported in NX-OS 41(1x) releases
As a result the switch is in an inconsistent state and the ports maynot function properly
FEFh Control VF-ID (see FibreChannel Link Services (FC-LS)and Fibre Channel SwitchFabric Generation 4 (FC-SW-4)standards)
FF0h FFEh Vendor specific
FFFh Do not use as a Virtual FabricIdentifier
FEFh = 4079
33
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
If you are in this state a workaround is to reboot the switch followingthe upgrade
LDAP AuthenticationThere is currently a limitation in the LDAP server configuration CLIthat prevents the use of an OU with spaces in the name Normallythese OU names could be surrounded by quotation marks howeverquotation marks are not supported by the ldap-server command
MDS-9148 limitationsThe Cisco MDS 9148 Multilayer Fabric Switch does not support thefollowing NX-OS features
Medium and Long range 4GB Agilent
IVR
Remote Span
Translative loop support
FCC - no generation quench reaction only
FC-Redirect
In addition the following features have these limits
VSANS - 31 maximum
SPAN - 1 session maximum
Technical notesThe following sections provide further information on technicalnotes
EMC Email Home for Cisco MDS switchesInstallation and Trouble shooting instructions can be found in thedocumentation located at the EMC Customer Service Internalwebsite
httpwwwcsisusemccomcsweb2esnesnhomehtmConnectrix20MDS20900020Family
34 EMC Connectrix MDS 9000 NX-OS Release Notes
Technical notes
Customers requiring installation of this solution should contact theirEMC Customer Engineer to assist with the installation and providethe documentation
Supported iSCSI sessionsThe current iSCSI session environment supported on the MDS is
300 sessions per port
1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no
InitialR2T=yes
Upgrading Cisco SAN-OSThere are several methods available for upgrading SAN-OS SoftwareEMC personnel are strongly recommended that all upgrades be doneby the Automated One-Step Upgrade using the install all
command EMC personnel should refer to the Connectrix MDS 9000Family Software Image Upgrade Instructions for a complete list ofprerequisites and instructions for performing the upgrade Thisdocument along with tftp software is available on the GlobalServices website at httpwwwcsisusEMCcom under ApplicationDownload Area ESN Product Information Connectrix MDS 9000Family
The Software Upgrade Wizard is an option for upgrades While theinstall all is the preferred method the Software Install Wizard canalso be used
Supported configuration parametersFor the most up-to-date information refer to the EMC Support Matrixavailable through E-Lab Interoperability Navigator athttpelabnavigatoremccom for the latest information onsupported configurations
35
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
Supported zoning parametersRefer to the EMC Networked Storage Topology Guide for the mostup-to-date information on supported zoning parameters
At the time these notes were published the following parameterswere supported
20 VSANs 5 Hops 2000 Unique members per physical infrastructure 1000 Zonesets per physical infrastructure 2000 Zones per physical infrastructure 1 FCIP tunnel
Supported IVR parameters IVR zone members 1000 IVR zones 1000 IVR zone sets 32 VSANS 20 IVR enabled switches 64
An RPQ can be submitted for any configurations that exceed thislimit
Managing zone changes in multiswitch fabricsZoning changes may be made through Fabric Manager or CLI Whenaccessing Fabric Manager or CLI the user does so from the point ofview of one switch That is Fabric Manager and CLI are accessed byentering the IP address of one switch in the fabric
When zoning changes are made the applicable VSAN and zone setdata is propagated to the rest of the switches in the fabric via the ISLs
When zoning changes are made to a VSAN the zone set data ispropagated to the rest of the switches in the fabric via the ISLs Bydefault only the active zone set information is relayed to all switchesin the VSAN If the user accesses the Fabric Manager and CLI fromanother switch in the fabric the new VSAN and zone set informationwill not be viewable To view the active and inactive zone set on theother switches in the fabric the user must log in to the CLI and issuea command from the EXEC prompt
36 EMC Connectrix MDS 9000 NX-OS Release Notes
Documentation
Example The following is an example of copying VSAN 1 through 20 zoningdata
CiscoMDS_name zone copy active full vsan 1-20
CiscoMDS_name conf t
Enter configuration commands one per line End with CNTL Z
CiscoMDS_name(config) zoneset distribute full vsan 1-20
CiscoMDS_name(config)
Note This command needs to be issued on all switches in the fabric one timeonly
This is a nondisruptive command After issuing the commands theuser will now see the active and inactive zone sets for the specifiedVSANs on any switch that is chosen from which to manage the fabric
After a zoning change is made save the running configuration to thestartup configuration
DocumentationSend documentation comments to mdsfeedback-doccom
Product DocumentationAs of NX-OS Release 42(1a) software configuration information isavailable in new feature-specific configuration guides for thefollowing information
System management
Interfaces
Fabric
Quality of service
Security
IP services
High availability and redundancy
37
Software media organization and files
EMC Connectrix MDS 9000 NX-OS Release Notes
The information in these new guides previously existed in the CiscoMDS 9000 Family CLI Configuration Guide That configuration guideremains available on Ciscocom and should be used for all softwarereleases prior to NX-OS Release 42(1a) Configuration guidesaddress the features introduced in or available in a particular releaseSelect and view the configuration guide that pertains to the softwareinstalled in your switch
In addition Fabric Manager information has been removed from theMDS NX-OS Release Notes (this document) and placed intostandalone Fabric Manager Release Notes that support both CiscoMDS 9000 Family switches and Cisco Nexus 5000 Series switchesThe Cisco Fabric Manager Release Notes are available onhttpPowerlinkemccom and from the following website
httpwwwciscocomenUSpartnerproductsps10495prod_release_notes_listhtml
Technical supportThese release notes complement a Cisco documentation set EachCisco document refers to where to get help However for any itemssupplied by EMC see ldquoTroubleshooting and getting helprdquo onpage 38
Software media organization and filesFor information on related software environment and systemrequirements refer to the EMC Support Matrix on EMC Powerlink at
httpPowerlinkEMCcom
InstallationFor hardware installation information refer to the Cisco MDS HWInstallation Guides available at Ciscocom
For EMC-specific installation information refer to ldquoEnvironment andsystem requirementsrdquo on page 5 in this document
38 EMC Connectrix MDS 9000 NX-OS Release Notes
Troubleshooting and getting help
Troubleshooting and getting helpEMC support product and licensing information can be obtained asfollows
Product information mdash For documentation release notes softwareupdates or for information about EMC products licensing andservice go to the EMC Powerlink website (registration required) at
httpPowerlinkEMCcom
Technical support mdash For technical support go to EMC CustomerService on Powerlink To open a service request through Powerlinkyou must have a valid support agreement Please contact your EMCsales representative for details about obtaining a valid supportagreement or to answer any questions about your account
Copyright copy 2011 EMC Corporation All rights reserved
EMC believes the information in this publication is accurate as of its publication date The information issubject to change without notice
THE INFORMATION IN THIS PUBLICATION IS PROVIDED ldquoAS ISrdquo EMC CORPORATION MAKES NOREPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION INTHIS PUBLICATION AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OFMERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Use copying and distribution of any EMC software described in this publication requires an applicablesoftware license
For the most up-to-date regulatory document for your product line go to the Technical Documentation andAdvisories section on EMC Powerlink
For the most up-to-date listing of EMC product names see EMC Corporation Trademarks on EMCcom
All other trademarks used herein are the property of their respective owners
6 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
For more information on power requirements please refer toAppendix C of the Cisco MDS 9500 Series Hardware Installation Guide
Hardware and software componentsEMC supported hardware and software modules are listed in CiscoNX-OS 50(4b) release notes located on the Cisco web site
Note Table 1 lists the MDS 9000 Family software and hardware componentsthat are not supported by EMC as well as the comparable NX-OS partnumbers
For older NX-OS part numbers see prior existing versions of SAN OSrelease notes
Table 1 MDS 9000 Family software and hardware modules not supported(page 1 of 2)
Component EMC part number Description Applicable products
Service modules DS-X9304-18FK9 18-port Fibre Channel4-port GigabitEthernet Multiservice FIPS (MSFM-184)module
MDS 9500 Series and9200 Series
Optics DS-X2-FC10G-ER X2SC optics 10-Gbps Fibre Channel forExtended Reach (40 km)
MDS 9500 Series and9200 Series exceptfor the MDS 9216
DS-X2-E10G-SR X2SC optics 10-Gbps Ethernet for ShortReach
DS-X2-FC10G_CX4 X2CX-4 optics 10-Gbps Fibre Channelcopper
LC-type fiber-optic SFP DS-SFP-GE-T 1-Gbps Ethernet SFP MDS 9000 Family
CWDM DS-CWDM-xxxx Gigabit Ethernet and 4-Gbps FibreChannel SFP LC interface xxxx nmwhere xxxx = 1470 1490 1510 15301550 1570 1590 or 1610 nm
DS-CWDM-MUX-4 Adddrop multiplexer for four CWDMwavelengths
DS-CWDM-MUX-8 Adddrop multiplexer for eight CWDMwavelengths
DS-CWDMCHASSIS Two slot chassis for CWDM adddropmultiplexers
7
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Note EMC personnel can obtain a complete list of Cisco part numbers fromthe Product Support Bulletins available under the ProductTechnicalInformation section of the EMC Global Services website athttpwwwcsisusEMCcomMyGSiVisitURLaspurl=10137
Support for the Generation 3 ModulesThe MDS 9513 Director requires Cisco MDS NX-OS 41(1b) or laterand the MDS 9513 Fabric 2 modules to support the MDS 9000 48-port8-Gbps Fibre Channel module and the MDS 9000 24-port 8-GbpsFibre Channel module
The MDS 9513 Director requires Cisco MDS NX-OS 41(1b) or laterbut does not require the MDS 9513 Fabric 2 modules to support theMDS 9000 444-port 8-Gbps Host-optimized Fibre Channel module
The MDS 9509 Director and the MDS 9506 Director also support theGeneration 3 8-Gbps modules The switches require Supervisor-2modules and Cisco MDS NX-OS 41(1b) or above to support theGeneration 3 8-Gbps modules
For information on the tasks associated with readying the MDS 9500Series to support Generation 3 8-Gbps Fibre Channel switchingmodules refer to the Migrating to Generation 3 Modules appendix inthe Cisco MDS 9500 Series Hardware Installation Guide It presents anoverview of the Generation 3 8-Gbps modules provides usageguidelines for the modules and describes three procedures formigrating hardware and upgrading software to enable use of thesemodules in an MDS 9513 Director
For information on replacing the MDS 9513 Fabric 1 modules withFabric 2 modules refer to the Migrating to Generation 3 Modulesappendix in the Cisco MDS 9500 Series Hardware Installation Guide Itprovides information on installing new Fabric 2 modules while
Port analyzer adapter DS-PAA-2 DS-PAA A standalone Fibre Channel-to-Ethernetadapter that allows for simple transparentanalysis of Fibre Channel traffic in aswitched fabric
MDS 9000 Family
Table 1 MDS 9000 Family software and hardware modules not supported(page 2 of 2)
Component EMC part number Description Applicable products
8 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
running NX-OS Release 4x and SAN-OS Release 3x It also providesinformation on installing the MDS 9513 Fabric 2 modules andactivating higher bandwidth
Configuring Generation 3 and Generation 2 Switching ModulesThe Cisco MDS 9500 Multilayer Directors are designed to operatewith any combination of Cisco MDS 9000 Generation 2 andGeneration 3 modules However there are limitations to considerwhen combining the various modules and supervisors in the CiscoMDS 9500 Series platform chassis The references listed in this sectionprovide specific information about configurations that combinedifferent modules and supervisors
For information on configuring Generation 2 and Generation 3switching modules refer to the Configuring Generation 2 andGeneration 3 Switching Modules chapter in the Cisco MDS 9000Family CLI Configuration Guide
For information on port index availability refer to the ldquoPort IndexAvailabilityrdquo section in the Product Overview chapter of the CiscoMDS 9500 Series Hardware Installation Guide
For information on Cisco MDS 9000 hardware and softwarecompatibility refer to the EMC Support Matrix available through E-LabInteroperability Navigator (ELN) at httpelabnavigatorEMCcom
MDS 9000 Chassis and Module Support in Cisco MDS NX-OS 5xTable 2 lists the MDS hardware chassis supported by Cisco MDSNX-OS 5x
Table 2 Cisco MDS NX-OS 5x Chassis Support Matrix
Switch NX-OS 5x Support
MDS 9513 Yes
MDS 9509 Yes
MDS 9506 Yes
MDS 9222i Yes
MDS 9216i No
9
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Table 3 lists the MDS hardware modules supported by Cisco MDSNX-OS 5x
MDS 9216A No
MDS 9216 No
MDS 9148 Yes
MDS 9134 Yes
MDS 9124 Yes
MDS 9140 No
MDS 9120 No
Table 2 Cisco MDS NX-OS 5x Chassis Support Matrix
Switch NX-OS 5x Support
Table 3 Module Support Matrix for Cisco MDS NX-OS 5x (page 1 of 2)
Module DescriptionMDS 9500Series MDS 9222i
DS-X9530-SF2A-K9 MDS 9500 Supervisor-2A Module Yes NA
DS-X9530-SF2-K9 MDS 9500 Supervisor-2 Module Yes NA
DS-X9530-SF1-K9 MDS 9500 Supervisor-1 Module No NA
DS-X9224-96K9 24-port 8-Gbps Fibre Channel Switching Module Yesa No
DS-X9248-96K9 48-port 8-Gbps Fibre Channel Switching Module Yesa No
DS-X9248-48K9 444-port Host Optimized 8-Gbps Fibre ChannelSwitching Module
Yes Yes
DS-X9316-SSNK9 16-Port Storage Services Node (SSN-16) Yes Yes
DS-X9304-18K9 184-Port Multiprotocol Services Module(MSM-184)
Yes Yes
DS-X9112 12-port 4-Gbps Fibre Channel Switching Module Yes Yes
DS-X9124 24-port 4-Gbps Fibre Channel Switching Module Yes Yes
DS-X9148 48-port 4-Gbps Fibre Channel Switching Module Yes Yes
DS-X9704 4-port 10-Gbps Fibre Channel Switching Module Yes Yes
10 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Migrating from Supervisor-1 Modules to Supervisor-2 ModulesAs of Cisco MDS SAN-OS Release 30(1) the Cisco MDS 9509 and9506 Directors support both Supervisor-1 and Supervisor-2 modulesSupervisor-1 and Supervisor-2 modules cannot be installed in thesame switch except during migration Both the active and standbysupervisor modules must be of the same type either Supervisor-1 orSupervisor-2 modules For Cisco MDS 9513 Directors bothsupervisor modules must be Supervisor-2 modules
CAUTION
Migrating your supervisor modules is a disruptive operation
Note Migrating from Supervisor-2 modules to Supervisor-1 modules is not supported
To migrate from a Supervisor-1 module to a Supervisor-2 module refer to the step-by-step instructions in the Cisco MDS 9000 NX-OS Release 41(x) and SAN-OS 3(x) Software Upgrade and Downgrade Guide
DS-X9302-14K9 142-port Multiprotocol Services (MPS-142)Module
No No
DS-X9016 16-port 1- 2-Gbps Fibre Channel SwitchingModule
No No
DS-X9032 32-port 1- 2-Gbps Fibre Channel SwitchingModule
No No
DS-X9032-SSM 32-port Storage Services Module (SSM) No No
DS-X9308-SMIP 8-port 1- 2-Gbps IP Switching Module No No
DS-X9304-SMIP 4-port 1- 2-Gbps IP Switching Module No No
a Requires DS-13SLT-FAB2 in the MDS 9513
Table 3 Module Support Matrix for Cisco MDS NX-OS 5x (page 2 of 2)
Module DescriptionMDS 9500Series MDS 9222i
11
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Software Download ProcessUse the software download procedure to upgrade to a later versionor downgrade to an earlier version of an operating system Thissection describes the software download process for the Cisco MDSNX-OS software and includes the following topics
ldquoDetermining the Software Versionrdquo on page 11
ldquoDownloading Softwarerdquo on page 11
ldquoSelecting the Correct Software Image for an MDS 9100 SeriesSwitchrdquo on page 12
ldquoSelecting the Correct Software Image for an MDS 9200 SeriesSwitchrdquo on page 13
ldquoSelecting the Correct Software Image for an MDS 9500 SeriesSwitchrdquo on page 13
Determining the Software VersionTo determine the version of Cisco MDS NX-OS or SAN-OS softwarecurrently running on a Cisco MDS 9000 Family switch using the CLIlog in to the switch and enter the show version EXEC command
To determine the version of Cisco MDS NX-OS or SAN-OS softwarecurrently running on a Cisco MDS 9000 Family switch using theFabric Manager view the Switches tab in the Information pane locatethe switch using the IP address logical name or WWN and check itsversion in the Release column
Note EMC strongly recommends that you use the latest qualified softwarerelease for all MDS 9000 Family products Refer to the EMC Support Matrixavailable through E-Lab Interoperability Navigator (ELN) athttpelabnavigatorEMCcom for the latest information on qualifiedfirmware revisions
Downloading SoftwareThe Cisco MDS NX-OS software is designed for mission-critical highavailability environments To realize the benefits of nondisruptiveupgrades on the Cisco MDS 9500 Directors we highly recommendthat you install dual supervisor modules
12 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Before performing upgrades submit all requested changes to theEMC Global Services CCA change control process so that anypotential operating environment impacts can be analyzedbeforehand
EMC personnel should also refer to the Connectrix MDS 9000 FamilySoftware Image Upgrade Instructions for a complete list of prerequisitesThis document is available on the Global Services websitehttpwwwcsisusEMCcom under Application Download AreaESN Product Information Connectrix MDS 9000 Family EMCpersonnel can download the Software Images from the GlobalServices website httpwwwcsisusEMCcom under ApplicationDownload Area ESN Product Information Connectrix MDS 9000Family
See the following sections in this release note for details on how youcan nondisruptively upgrade your Cisco MDS 9000 switch Issuingthe install all command from the CLI or using Fabric Manager toperform the downgrade enables the compatibility check The checkindicates if the upgrade can happen nondisruptively or disruptivelydepending on the current configuration of your switch and thereason
Compatibility check is doneModule bootable Impact Install-type Reason------ -------- -------------- ------------ ------
1 yes non-disruptive rolling2 yes disruptive rolling Hitless upgrade is not supported3 yes disruptive rolling Hitless upgrade is not supported4 yes non-disruptive rolling5 yes non-disruptive reset6 yes non-disruptive reset
Selecting the Correct Software Image for an MDS 9100 Series SwitchThe system and kickstart image that you use for an MDS 9100 seriesswitch depends on which switch you use as shown in Table 4
Table 4 Software Images for MDS 9100 Series Switches
Cisco MDS 9100 Series Switch Type Naming Convention
9124 and 9134 Filename begins with m9100-s2ek9
9148 Filename begins with m9100-s3ek9
13
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Selecting the Correct Software Image for an MDS 9200 Series SwitchThe system and kickstart image that you use for an MDS 9200 seriesswitch depends on which switch you use as shown in Table 5
Selecting the Correct Software Image for an MDS 9500 Series SwitchThe system and kickstart image that you use for an MDS 9500 Seriesswitch depends on whether the switch is based on a Supervisor-1module or a Supervisor-2 module as shown in Table 6
Use the show module command to display the type of supervisormodule in the switch The following is sample output from the showmodule command on a Supervisor 2 module
Table 5 Software Images for MDS 9200 Series Switches
Cisco MDS 9200 Series Switch Type Naming Convention
9222i Filename begins with m9200-s2ek9
Table 6 Software Images for Supervisor Type
Cisco MDS 9500 Series Switch Type Supervisor Module Type Naming Convention
9513 9509 and 9506 Supervisor-2 module Filename begins with m9500-sf2ek9
14 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
switch show moduleMod Ports Module-Type Model Status--- ----- -------------------------------- ------------------ ------------7 0 SupervisorFabric-2 DS-X9530-SF2-K9 active 8 0 SupervisorFabric-2 DS-X9530-SF2-K9 ha-standby
Upgrading Your Cisco MDS NX-OS Software ImageThis section lists the guidelines recommended for upgrading yourCisco MDS NX-OS software image and includes the following topics
ldquoGeneral Upgrading Guidelinesrdquo on page 14
ldquoDowngrading Your Cisco MDS SAN-OS Software Imagerdquo onpage 18
Note Before you begin the upgrade process review the list of chassis andmodules that NX-OS Release 50(4b) supports See the ldquoMDS 9000 Chassisand Module Support in Cisco MDS NX-OS 5xrdquo on page 8
Note For detailed instructions for performing a software upgrade usingCisco Fabric Manager see the Cisco Fabric Manager Release Notes forRelease 50(4b) which is available from the following websitehttpPowerlinkEMCcom
General Upgrading Guidelines
Note To upgrade to NX-OS Release 50(4b) you must be running NX-OSRelease 4x If you are running SAN-OS Release 32(3a) or earlier firstupgrade to SAN-OS Release 33(x) then NX-OS Release 4x and thenupgrade to NX-OS Release 50(4b)
Use the following guidelines when upgrading to Cisco MDS NX-OSRelease 5x
Install and configure dual supervisor modules
Issue the show install all impact upgrade-image CLI command todetermine if your upgrade will be nondisruptive
15
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Be aware of the impact of an upgrade on VSAN 4079 if you areupgrading from SAN-OS Release 3x to NX-OS 50(4b) See theldquoUpgrading Effect on VSAN 4079rdquo on page 17
Follow the recommended guidelines for upgrading a Cisco MDS9124 or MDS 9134 Switch as described in ldquoUpgrading a CiscoMDS 9124 or MDS 9134 switchrdquo on page 18
Take note of the affect of upgrades on MDS 9500 series switchesthat have active IOA flows as described in ldquoMDS 9500 seriesupgrades with active IOA flowsrdquo on page 18
Be aware that some features impact whether an upgrade isdisruptive or nondisruptive
bull Fibre Channel Ports Traffic on Fibre Channel ports can benondisruptively upgraded See Table 7 on page 16 for thenondisruptive upgrade path for all NX-OS and SAN-OSreleases
bull Storage Services Intelligent storage services traffic such asSANTap NASB and FC write acceleration is disruptedduring an upgrade Fibre Channel traffic is not
bull Gigabit Ethernet Ports Traffic on Gigabit Ethernet ports isdisrupted during an upgrade or downgrade This includes theGigabit Ethernet ports on the MSM-184 module and the MDS9222i switch Those nodes that are members of VSANs traversingan FCIP ISL are impacted and a fabric reconfiguration occursiSCSI initiators connected to the Gigabit Ethernet ports loseconnectivity to iSCSI targets while the upgrade is in progress
bull FICON If you have FICON enabled the upgrade path isdifferent See Table 6 on page 13
Use Table 7 to determine your nondisruptive upgrade path to Cisco MDSNX-OS Release 50(4b) find the image release number you are currentlyusing in the Current column of the table and use the path recommended
16 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Note The software upgrade information in Table 7 applies only to FibreChannel switching traffic Upgrading system software disrupts IP traffic andSSM intelligent services traffic
MDS NX-OS Release 50(4b) is not a FICON-qualified release
Table 7 Nondisruptive Upgrade Path to Cisco MDS NX-OS Release 50(4b)
Current Nondisruptive Upgrade Path
NX-OS 50(4) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 50(1a) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(7b) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(5) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(3) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(1b) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(1a) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 41(3a) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 41(1b) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
SAN-OS 33(4a) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
NX-OS 33(4) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 33(3) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 33(2) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 33(1c) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 32(3a) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 32(2c) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 32(1a) Upgrade to SAN-OS Release then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 31(3a) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 31(2) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
17
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Use Table 8 to determine your FICON nondisruptive upgrade path toCisco MDS NX-OS Release 42(7b) Find the image release numberyou are currently using in the Current Release with FICON Enabledcolumn of the table and use the path recommended
Note For more information on the FICON qualified NX-OS releases refer tothe EMC Support Matrix available through E-Lab Interoperability Navigator(ELN) at httpelabnavigatorEMCcom
Upgrading Effect on VSAN 4079If you are upgrading to NX-OS Release 50(4b) and you have notcreated VSAN 4079 the NX-OS software will automatically createVSAN 4079 and reserve it for EVFP use If VSAN 4079 is reserved forEVFP use the switchport trunk allowed vsan command will filterout VSAN 4079 from the allowed list as shown in the followingexample
switch(config-if) switchport trunk allowed vsan1-40801-40784080switch(config-if)
If you have created VSAN 4079 the upgrade to NX-OS Release50(4b) will have no affect on VSAN 4079
If you downgrade to a release of NX-OS lower than 41(x) afterNX-OS Release 50(4b) creates VSAN 4079 and reserves it for EVFPuse the VSAN will no longer be reserved
Table 8 FICON Nondisruptive Upgrade Path to NX-OS Release 42(7b)
Current Release withFICON Enabled Upgrade Path
NX-OS 42(1b) You can nondisruptively upgrade directly to NX-OS Release 42(7b)
NX-OS 41(1c) You can nondisruptively upgrade directly to NX-OS Release 42(7b)
SAN-OS 33(1c) You can nondisruptively upgrade directly to NX-OS Release 42(7b)
18 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Upgrading a Cisco MDS 9124 or MDS 9134 switchIf you are upgrading from Cisco MDS SAN-OS Release 31(1) to CiscoNX-OS Release 4x before upgrading to NX-OS Release 50(4b) on aCisco MDS 9124 or MDS 9134 switch follow these guidelines
During the upgrade configuration is not allowed and the fabric isexpected to be stable
The Fabric Shortest Path First (FSPF) timers must be configured tothe default value of 20 seconds otherwise the nondisruptiveupgrade is blocked to ensure that the maximum down toim forthe control plane can be 80 seconds
If there are any CFS commits in the fabric the nondisruptiveupgrade will fail
If there is a zone server merge in progress in the fabric thenondisruptive upgrde will fail
If a service terminates the nondisruptive upgrade the showinstall all failure-reason command can display the reason thatthe nondisruptive upgrade cannot proceed
If there is not enough memory in the system to load the newimages the upgrade will be made disruptive due to insufficientresources and the user will be notified in the compativility table
MDS 9500 series upgrades with active IOA flowsWhen upgading an MDS 9500 series switch that has active IOA flowsthose flows may be interrupted during the supervisor moduleswitchover To workaround this issue you have to enablespanning-tree portfast on the interface on the catalyst connected tothe management interface of the activestandby supervisor for theinterface to come up fast without causing the cluster to lose quorum
Downgrading Your Cisco MDS SAN-OS Software ImageThis section lists the guidelines recommended for downgrading yourCisco MDS SAN-OS software image and includes the followingtopics
ldquoGeneral downgrading guidelinesrdquo on page 19
19
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
General downgrading guidelinesUse the following guidelines to nondisruptively downgrade yourCisco MDS NX-OS Release 50(4b)
Install and configure dual supervisor modules
Issue the system no acl-adjacency-sharing execute command todisable acl adjacency usage on Generation 2 and Generation 1modules If this command fails reduce the number of zones IVRzones TE ports or a combination of these in the system and issuethe command again
Disable all features not supported by the downgrade release Usethe show incompatibility system downgrade-image command todetermine what you need to disable
bull If you are running in interoperability mode two such featuresare the Reliable Commit Service and Full Zone DatabaseDistribution They can be disabled by running thesecommand in config term mode
no zone rcs enableno zoneset capability distribute full
Use the show install all impact downgrade-image command todetermine if your downgrade will be nondisruptive
Be aware that some features impact whether a downgrade isdisruptive or nondisruptive
bull Fibre Channel Ports Traffic on Fibre Channel ports can benondisruptively downgraded See Table 9 on page 20 for thenondisruptive downgrade path for all SAN-OS releases
bull Storage Services Intelligent storage services traffic such asSANTap NASB and FC write acceleration is disruptedduring a downgrade Fibre Channel traffic is not
bull Gigabit Ethernet Ports Traffic on Gigabit Ethernet ports isdisrupted during a downgrade This includes the GigabitEthernet ports on the MSM-184 module and the MDS 9222iswitch Those nodes that are members of VSANs traversing anFCIP ISL are impacted and a fabric reconfiguration occursiSCSI initiators connected to the Gigabit Ethernet ports loseconnectivity to iSCSI targets while the downgrade is inprogress
20 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
bull FICON If you have FICON enabled the downgrade path isdifferent See Table 10 on page 21
Note A downgrade from NX-OS Release 4x to SAN-OS Release 33(1c) is notsupported on MDS switches when FC-Redirect based applications such asData Mobility Manager or Storage Media Encryption are configured in thefabric if either of the following conditions are satisfied
1 A target for which FC-Redirect is configured is connected locally and thereare Generation 1 modules with ISLs configured in the switch
2 A host for which FC-redirect is configured is connected locally ona Generation 1 module
If these conditions exist remove the application configuration forthese targets and hosts before proceeding with the downgrade
Use Table 9 on page 20 to determine the nondisruptive downgradepath from Cisco NX-OS Release 50(4b) Find the NX-OS or SAN-OSimage you want to downgrade to in the To SAN-OSNX-OS Releasecolumn of the table and use the path recommended
Note The software downgrade information in Table 10 on page 21 appliesonly to Fibre Channel switching traffic Downgrading system softwaredisrupts IP and SSM intelligent services traffic
Table 9 Nondisruptive Downgrade Path from NX-OS Release 50(4b) (page 1 of2)
To SAN-OS NX-OSRelease Nondisruptive Downgrade Path
NX-OS 50(4) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 50(1a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(7b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(5) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(3) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(1b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(1a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 41(3a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
21
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Use Table 10 to determine your nondisruptive downgrade path if youhave FICON enabled from Cisco NX-OS Release 42(7b) Find the imagerelease number you are currently using in the Current Release withFICON Enabled column of the table and use the path recommended
NX-OS 41(1b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
SAN-OS 33(5a) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33())
SAN-OS 33(5) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(4a) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
NX-OS 33(4) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(3) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
NX-OS 33(2) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(1c) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 32(3a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 32(x)
SAN-OS 32(2c) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 32(x)
SAN-OS 32(1a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
SAN-OS 31(3a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
SAN-OS 31(2) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
Table 9 Nondisruptive Downgrade Path from NX-OS Release 50(4b) (page 2 of2)
To SAN-OS NX-OSRelease Nondisruptive Downgrade Path
Table 10 FICON Downgrade Path from NX-OS Release 42(7b)
To SAN-OSNX-OS Release withFICON Enabled Downgrade Path
NX-OS 42(1b) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
NX-OS 41(1c) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
SAN-OS 33(1c) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
22 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Best practicesLog messages are not saved across system reboots or power outagesTherefore EMC recommends that customers configure a SyslogServer in order to redirect and capture all log messages on a remoteserver For more information please refer to the Cisco MDS 9000Family Configuration Guide available at
httpwwwciscocomenUSproductsps5989products_support_series_homehtml
Maximum ports per chassisTable 11 shows the maximum ports per chassis
a V2 indicates a 9506 or 9509 with Generation-2 Supervisors The presence of anygeneration one module in a switch will limit the maximum port count to 252This includes the 16-port 32-port 14+2 IPS4 and IPS8 cards
Known problems and limitationsFor a list of problems with this release please refer to the CiscoRelease notes located at
httpwwwciscocomenUSproductsps5989prod_release_notes_listhtml
Limitations and restrictionsThe following limitations and restrictions apply to all switches in theCisco MDS 9000 Family unless a limitation for a specific switch isstated
ldquoStorage Media Encryption (SME) limitationsrdquo on page 24
Table 11 Maximum ports per chassis
Chassis Maximum number of ports
MDS 9506-V2 192a
MDS 9509-V2 336
MDS 9513 528
23
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
ldquoSME configuration limitsrdquo on page 24
ldquoDeleting Cisco SME interfacesrdquo on page 25
ldquoCisco MDS 9124 and 9134 Multilayer fabric switchesrdquo on page 25
ldquoN-Port virtualization configuration limitsrdquo on page 25
ldquoMaximum number of zones supported in Interop Mode 4rdquo onpage 25
ldquoIPv6rdquo on page 26
ldquoIP-ACL supportrdquo on page 26
ldquoUser Rolesrdquo on page 26
ldquoUsing a RSA Version 1 Key for SSH Following an Upgraderdquo onpage 27
ldquoApplying Zone Configurations to VSAN 1rdquo on page 27
ldquoInterVSAN Routingrdquo on page 28
ldquoRSPAN Traffic Not Supported on CTS Ports on 8-GbpsSwitching Modulesrdquo on page 28
ldquoIO Accelerator Feature Limitationsrdquo on page 28
ldquoSupport for FCIP Compression Modesrdquo on page 28
ldquoSaving Copies of the Running Kickstart and System Imagesrdquo onpage 29
ldquoConfiguring Buffer Credits on a Generation 2 or Generation 3Modulerdquo on page 29
ldquoStorage services module power budgetrdquo on page 29
ldquoiSCSI proxy initiator in Celerra HighRoad environmentsrdquo onpage 30
ldquoHPUX N_port IDrdquo on page 30
ldquoInteroperability limitationsrdquo on page 31
ldquoNASBrdquo on page 31
ldquoReserved VSAN Range and Isolated VSAN Range Guidelinesrdquoon page 31
ldquoSymmetrix VMax limitationsrdquo on page 32
ldquoStorage Applications on the MSM-184rdquo on page 32
ldquoDowngrading with fport-channel-trunk enabledrdquo on page 32
ldquoLDAP Authenticationrdquo on page 33
24 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
ldquoMDS-9148 limitationsrdquo on page 33
Storage Media Encryption (SME) limitationsAn SME node can only belong to one cluster Adding the node tomore than one cluster will cause problems
Currently there is no prevention or warning in place when an attemptis made to add a node to multiple clusters
SME configuration limitsTable 12 lists the SME configuration limits for this release
Table 12 SME configuration limits
Configuration Limits
Number of switches in the fabric 10
Number of clusters per switch 1
Switches in a cluster 4
Fabrics in a cluster 2
Modules in a switch 11
Cisco MSM-184 modules in a cluster 32
Initiator-Target-LUNs (ITLs) 1024
LUNs behind a target 32
Host and target ports in a cluster 128
Number of hosts per target 128
Tape backup groups per cluster 2
Volume groups in a tape backup group 4
Cisco Key Management Center ( of keys) 32K
Targets per switch that can be FC-redirected 32
25
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Deleting Cisco SME interfacesA Cisco SME interface can be deleted from the cluster only after theinterface is administratively shut-down and all related tasksassociated with the interface shut-down are complete
Cisco MDS 9124 and 9134 Multilayer fabric switchesThe Cisco MDS 9124 and 9134 Multilayer fabric switches do notsupport the following Cisco MDS SAN-OS features
IVR Remote Span Translative loop support FCCmdash no generation quench reaction only
In addition the following features have these limits
VSANs mdash 16 maximum SPAN mdash 1 session maximum
N-Port virtualization configuration limitsThe NPV features have maximum configuration limits Table 13shows the verified and maximum limits for the NPV switchesrunning NX-OS Release 5x
Maximum number of zones supported in Interop Mode 4In interop mode 4 the maximum number of zones that is supportedin an active zone set is 2047 due to limitations in the connectedvendor switch When IVR is used in interop mode 4 the maximumnumber of zones supported including IVR zones in the active zoneset is 2047 The limit for the maximum number of IVR zones perVSAN is 250 zones (two members per zone)
Table 13 NPV features limitations
Feature Verified limits Maximum limits
FLOGIs or F Disc per NPV port group 114 114
NPV switches per NPV core switch 105 105
FLOGIs per line card on NPV core switch 400 400
26 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
IPv6The management port on Cisco MDS switches supports oneuser-configured IPv6 address but does not supportauto-configuration of an IPv6 address
IP-ACL supportDo not apply IP-ACLs to only one member of a PortChannel groupApply IP-ACLs to the entire channel group
If IP-ACLs are already configured in a Gigabit Ethernet interface youcannot add this interface to a Ethernet PortChannel group
Refer to the Cisco MDS 9000 Family Configuration Guide
User RolesIn SAN-OS Release 33(x) and earlier when a user belongs to a rolewhich has a VSAN policy set to Deny and the role allows access to aspecific set of VSANs (for example 1 through 10) the user isrestricted from performing the configuration clear execute anddebug commands which had a VSAN parameter outside thisspecified set Beginning with NX-OS Release 41(1b) these users arestill prevented from performing configuration clear execute anddebug commands as before however they are allowed to performshow commands for all VSANs The ability to execute the showcommand addresses the following
In a network environment users often need to view informationin other VSANs even though they do not have permission tomodify configurations in those VSANs
This behavior makes Cisco MDS 9000 Series switches consistentwith other Cisco products such as Cisco Nexus 7000 Seriesswitches that exhibit the same behavior for those roles (whenthey apply to the VLAN policy)
27
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Using a RSA Version 1 Key for SSH Following an UpgradeFor security reasons NX-OS Release 42(x) and higher does notsupport RSA version 1 keys As a result if you upgrade from anearlier version that did support RSA version 1 keys and you hadconfigured a RSA version 1 key for SSH then you will not be able tolog in through SSH following the upgrade
If you have a RSA version 1 key configured for SSH beforeupgrading to NX-OS Release 42(x) or higher follow these steps
1 Disable SSH
2 Create RSA version 2 DSA keys
3 Enable SSH
4 Delete any RSA version 1 keys on any remote SSH clients andreplace the version 1 keys with the new version 2 keys from theswitch
Proceed with the upgrade to NX-OS Release 42(x) or higher
If you upgrade before disabling SSH and creating RSA version 2 keysfollow these steps
1 Open a Telnet session and log in through the console
2 Issue the no feature ssh command to disable SSH
3 Issue the ssh key rsa 1024 command to create RSA version 2 keys
4 Issue the feature ssh command to enable SSH
Applying Zone Configurations to VSAN 1In the setup script you can configure system default values for thedefault-zone to be permit or deny and you can configure defaultvalues for the zone distribution method and for the zone mode
These default settings are applied when a new VSAN is createdHowever the settings will not take effect on VSAN 1 because it existsprior to running the setup script Therefore when you need thosesettings for VSAN 1 you must explicitly issue the followingcommands
zone default-zone permit vsan 1 zoneset distribute full vsan 1 zone mode enhanced vsan 1
28 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
InterVSAN RoutingWhen using InterVSAN Routing (IVR) it is recommended to enableCisco Fabric Services (CFS) on all IVR-enabled switches Failure to doso may cause mismatched active zone sets if an error occurs duringzone set activation
RSPAN Traffic Not Supported on CTS Ports on 8-Gbps Switching ModulesAn inter-switch link (ISL) that is enabled for Cisco TrustSec (CTS)encryption must be brought up in non-CTS mode to support remoteSPAN (RSPAN) traffic on the following modules
DS-X9248-96K9 Cisco MDS 9000 48-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9224-96K9 Cisco MDS 9000 24-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9248-48K9 Cisco MDS 9000 444-Port Host-Optimized8-Gbps Fibre Channel Switching Module
If the ISL link is brought up with CTS enabled random packets dropsof both RSPAN traffic and normal traffic will occur on the receiverport switch
IO Accelerator Feature LimitationsIOA does not support the following NX-OS features
IVR flows
Devices with NPV and NPIV enabled
F port trunking
bull F port channeling
Support for FCIP Compression ModesIn Cisco NX-OS Release 42(1b) and higher FCIP compression mode 1and compression mode 3 are not supported on the Cisco MSM-184module and on the SSN-16 module
29
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Saving Copies of the Running Kickstart and System ImagesAfter you upgrade to MDS NX-OS Release 42(1b) or higher you arenot allowed to delete rename move or overwrite the kickstart andsystem images that are in the current system bootvar settings on anactive or standby MDS Supervisor-2 module on any Cisco MDS 9500Series switch This restriction does not apply to the integratedsupervisor module on the MDS 9200 and MDS 9100 series switches
Configuring Buffer Credits on a Generation 2 or Generation 3 ModuleWhen you configure port mode to auto or E on a Generation 2module one of the ports will not come up for the followingconfiguration
Port Mode auto or E for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E on a Generation 3module one or two of the ports will not come up for the followingconfiguration
Port Mode auto or E for the first half of the ports the second halfof the ports or for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E for all ports in the globalbuffer pool you need to reconfigure buffer credits on one or more ofthe ports The total number of buffer credits configured for all theports in the global buffer pool should be reduced by 64
Storage services module power budgetThe MDS 9509 does not have the power budget to run seven SSMcards EMC recommends a maximum of four SSMs in one 9509Customers wishing to use more than four SSMs in one chassis shouldrefer to the Cisco MDS 9000 documentation on the Ciscocom websiteto validate that there is enough power available for their desiredconfiguration
30 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Note Upgrading to the 3000 watt power supplies will alleviate thiscondition
iSCSI proxy initiator in Celerra HighRoad environmentsEMC supports the iSCSI proxy initiator feature in Celerrareg
HighRoadreg environments In proxy initiator mode one Fibre Channelinitiator is used for all iSCSI clients who access the switch via thesame iSCSI interface (iscsi33 for example)
The initiators will use the PWWN assigned to the iSCSI interface TheiSCSI interface to which an iSCSI client will logon to is configured inthe client and must be permitted by the virtual target configured forthat initiator
The current session environment supported on the MDS is
300 sessions per port 1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no InitialR2T=yes
Refer to the specific initiator support documentation on how to setthe parameters The implementation will not perform properly ifthese bits are not set
Refer to the MDS documentation for more information regarding theconfiguration of the iSCSI proxy initiator at the following Ciscowebsite
httpwwwciscocomenUSproducts
HPUX N_port IDThe N_port ID port value of 255 (0xFF) has special meaning forHP-UX A N_port ID (FC_ID) can not be returned from a switch thatcontains this value for the N_port ID (FC_ID) port value for a HP-UXinitiator or HP-UX target port Port ID value of 255 (0xFF) cannot be
31
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
configured for HP-UX initiator port and HP-UX target ports whenconfiguring MDS FC_IDs The port_ID value is the third byte of theFC_ID
Interoperability limitationsRefer to the EMC Support Matrix (ESM) and the EMC Networked Storage Topology Guide for modes of operation and caveats
NASBThe NASB feature requires that the backup application load the tapedrive with a compatible tape cartridge prior to configuring NASB inthe backup VSAN
Reserved VSAN Range and Isolated VSAN Range GuidelinesOn an NPV switch with a trunking configuration on any interface or ona regular switch where the feature fport_channel_trunk command hasbeen issued to enable the F PortChannel feature follow theseconfiguration guidelines for reserved VSANs and the isolated VSAN
bull If trunk mode is on for any of the interfaces or NP PortChannelis up the reserved VSANs are 3040 to 4078 and they are notavailable for user configuration
bull The Exchange Virtual Fabric Protocol (EVFP) isolated VSAN is4079 and it is not available for user configuration
bull VSAN 4079 will be impacted by an upgrade to NX-OS Release42(3) depending on whether or not VSAN 4079 was createdprior to the upgrade See theldquoUpgrading Effect on VSAN 4079rdquoon page 17
The following VSAN IDs are assigned in the Fibre Channel Framingand Signaling (FC-FS) interface standard
VF_ID Value Value Description
00h Do not use as a Virtual FabricIdentifier
001h EFFh Available as a Virtual FabricIdentifier
F00h FEEh Reserved
32 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Symmetrix VMax limitationsAt the time of this writing the following features are not supportedfor use with the Symmetrix VMax
FCIP Write Acceleration
The NX-OS IOA functionality is only supported with the Q2 SREnginuity release 5874229182 or higher
For the most up to date status please refer to the current revision ofthese Release Notes on httpPowerlinkemccom and the EMCSupport Matrix available through E-Lab Interoperability Navigator (ELN) athttpelabnavigatorEMCcom
Storage Applications on the MSM-184The MDS 9000 184-Port Multiservice Module (MSM-184) does notsupport multiple concurrent storage applications Only oneapplication can run on the MSM-184 at a time
Downgrading with fport-channel-trunk enabledIf you are running MDS NX-OS Release 42(x) or higher with thefport-channel-trunk feature enabled and you downgrade to anyNX-OS 41(1x) release the installer performs a nondisruptivedowngrade even though the fport-channel-trunk feature is notsupported in NX-OS 41(1x) releases
As a result the switch is in an inconsistent state and the ports maynot function properly
FEFh Control VF-ID (see FibreChannel Link Services (FC-LS)and Fibre Channel SwitchFabric Generation 4 (FC-SW-4)standards)
FF0h FFEh Vendor specific
FFFh Do not use as a Virtual FabricIdentifier
FEFh = 4079
33
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
If you are in this state a workaround is to reboot the switch followingthe upgrade
LDAP AuthenticationThere is currently a limitation in the LDAP server configuration CLIthat prevents the use of an OU with spaces in the name Normallythese OU names could be surrounded by quotation marks howeverquotation marks are not supported by the ldap-server command
MDS-9148 limitationsThe Cisco MDS 9148 Multilayer Fabric Switch does not support thefollowing NX-OS features
Medium and Long range 4GB Agilent
IVR
Remote Span
Translative loop support
FCC - no generation quench reaction only
FC-Redirect
In addition the following features have these limits
VSANS - 31 maximum
SPAN - 1 session maximum
Technical notesThe following sections provide further information on technicalnotes
EMC Email Home for Cisco MDS switchesInstallation and Trouble shooting instructions can be found in thedocumentation located at the EMC Customer Service Internalwebsite
httpwwwcsisusemccomcsweb2esnesnhomehtmConnectrix20MDS20900020Family
34 EMC Connectrix MDS 9000 NX-OS Release Notes
Technical notes
Customers requiring installation of this solution should contact theirEMC Customer Engineer to assist with the installation and providethe documentation
Supported iSCSI sessionsThe current iSCSI session environment supported on the MDS is
300 sessions per port
1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no
InitialR2T=yes
Upgrading Cisco SAN-OSThere are several methods available for upgrading SAN-OS SoftwareEMC personnel are strongly recommended that all upgrades be doneby the Automated One-Step Upgrade using the install all
command EMC personnel should refer to the Connectrix MDS 9000Family Software Image Upgrade Instructions for a complete list ofprerequisites and instructions for performing the upgrade Thisdocument along with tftp software is available on the GlobalServices website at httpwwwcsisusEMCcom under ApplicationDownload Area ESN Product Information Connectrix MDS 9000Family
The Software Upgrade Wizard is an option for upgrades While theinstall all is the preferred method the Software Install Wizard canalso be used
Supported configuration parametersFor the most up-to-date information refer to the EMC Support Matrixavailable through E-Lab Interoperability Navigator athttpelabnavigatoremccom for the latest information onsupported configurations
35
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
Supported zoning parametersRefer to the EMC Networked Storage Topology Guide for the mostup-to-date information on supported zoning parameters
At the time these notes were published the following parameterswere supported
20 VSANs 5 Hops 2000 Unique members per physical infrastructure 1000 Zonesets per physical infrastructure 2000 Zones per physical infrastructure 1 FCIP tunnel
Supported IVR parameters IVR zone members 1000 IVR zones 1000 IVR zone sets 32 VSANS 20 IVR enabled switches 64
An RPQ can be submitted for any configurations that exceed thislimit
Managing zone changes in multiswitch fabricsZoning changes may be made through Fabric Manager or CLI Whenaccessing Fabric Manager or CLI the user does so from the point ofview of one switch That is Fabric Manager and CLI are accessed byentering the IP address of one switch in the fabric
When zoning changes are made the applicable VSAN and zone setdata is propagated to the rest of the switches in the fabric via the ISLs
When zoning changes are made to a VSAN the zone set data ispropagated to the rest of the switches in the fabric via the ISLs Bydefault only the active zone set information is relayed to all switchesin the VSAN If the user accesses the Fabric Manager and CLI fromanother switch in the fabric the new VSAN and zone set informationwill not be viewable To view the active and inactive zone set on theother switches in the fabric the user must log in to the CLI and issuea command from the EXEC prompt
36 EMC Connectrix MDS 9000 NX-OS Release Notes
Documentation
Example The following is an example of copying VSAN 1 through 20 zoningdata
CiscoMDS_name zone copy active full vsan 1-20
CiscoMDS_name conf t
Enter configuration commands one per line End with CNTL Z
CiscoMDS_name(config) zoneset distribute full vsan 1-20
CiscoMDS_name(config)
Note This command needs to be issued on all switches in the fabric one timeonly
This is a nondisruptive command After issuing the commands theuser will now see the active and inactive zone sets for the specifiedVSANs on any switch that is chosen from which to manage the fabric
After a zoning change is made save the running configuration to thestartup configuration
DocumentationSend documentation comments to mdsfeedback-doccom
Product DocumentationAs of NX-OS Release 42(1a) software configuration information isavailable in new feature-specific configuration guides for thefollowing information
System management
Interfaces
Fabric
Quality of service
Security
IP services
High availability and redundancy
37
Software media organization and files
EMC Connectrix MDS 9000 NX-OS Release Notes
The information in these new guides previously existed in the CiscoMDS 9000 Family CLI Configuration Guide That configuration guideremains available on Ciscocom and should be used for all softwarereleases prior to NX-OS Release 42(1a) Configuration guidesaddress the features introduced in or available in a particular releaseSelect and view the configuration guide that pertains to the softwareinstalled in your switch
In addition Fabric Manager information has been removed from theMDS NX-OS Release Notes (this document) and placed intostandalone Fabric Manager Release Notes that support both CiscoMDS 9000 Family switches and Cisco Nexus 5000 Series switchesThe Cisco Fabric Manager Release Notes are available onhttpPowerlinkemccom and from the following website
httpwwwciscocomenUSpartnerproductsps10495prod_release_notes_listhtml
Technical supportThese release notes complement a Cisco documentation set EachCisco document refers to where to get help However for any itemssupplied by EMC see ldquoTroubleshooting and getting helprdquo onpage 38
Software media organization and filesFor information on related software environment and systemrequirements refer to the EMC Support Matrix on EMC Powerlink at
httpPowerlinkEMCcom
InstallationFor hardware installation information refer to the Cisco MDS HWInstallation Guides available at Ciscocom
For EMC-specific installation information refer to ldquoEnvironment andsystem requirementsrdquo on page 5 in this document
38 EMC Connectrix MDS 9000 NX-OS Release Notes
Troubleshooting and getting help
Troubleshooting and getting helpEMC support product and licensing information can be obtained asfollows
Product information mdash For documentation release notes softwareupdates or for information about EMC products licensing andservice go to the EMC Powerlink website (registration required) at
httpPowerlinkEMCcom
Technical support mdash For technical support go to EMC CustomerService on Powerlink To open a service request through Powerlinkyou must have a valid support agreement Please contact your EMCsales representative for details about obtaining a valid supportagreement or to answer any questions about your account
Copyright copy 2011 EMC Corporation All rights reserved
EMC believes the information in this publication is accurate as of its publication date The information issubject to change without notice
THE INFORMATION IN THIS PUBLICATION IS PROVIDED ldquoAS ISrdquo EMC CORPORATION MAKES NOREPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION INTHIS PUBLICATION AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OFMERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Use copying and distribution of any EMC software described in this publication requires an applicablesoftware license
For the most up-to-date regulatory document for your product line go to the Technical Documentation andAdvisories section on EMC Powerlink
For the most up-to-date listing of EMC product names see EMC Corporation Trademarks on EMCcom
All other trademarks used herein are the property of their respective owners
7
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Note EMC personnel can obtain a complete list of Cisco part numbers fromthe Product Support Bulletins available under the ProductTechnicalInformation section of the EMC Global Services website athttpwwwcsisusEMCcomMyGSiVisitURLaspurl=10137
Support for the Generation 3 ModulesThe MDS 9513 Director requires Cisco MDS NX-OS 41(1b) or laterand the MDS 9513 Fabric 2 modules to support the MDS 9000 48-port8-Gbps Fibre Channel module and the MDS 9000 24-port 8-GbpsFibre Channel module
The MDS 9513 Director requires Cisco MDS NX-OS 41(1b) or laterbut does not require the MDS 9513 Fabric 2 modules to support theMDS 9000 444-port 8-Gbps Host-optimized Fibre Channel module
The MDS 9509 Director and the MDS 9506 Director also support theGeneration 3 8-Gbps modules The switches require Supervisor-2modules and Cisco MDS NX-OS 41(1b) or above to support theGeneration 3 8-Gbps modules
For information on the tasks associated with readying the MDS 9500Series to support Generation 3 8-Gbps Fibre Channel switchingmodules refer to the Migrating to Generation 3 Modules appendix inthe Cisco MDS 9500 Series Hardware Installation Guide It presents anoverview of the Generation 3 8-Gbps modules provides usageguidelines for the modules and describes three procedures formigrating hardware and upgrading software to enable use of thesemodules in an MDS 9513 Director
For information on replacing the MDS 9513 Fabric 1 modules withFabric 2 modules refer to the Migrating to Generation 3 Modulesappendix in the Cisco MDS 9500 Series Hardware Installation Guide Itprovides information on installing new Fabric 2 modules while
Port analyzer adapter DS-PAA-2 DS-PAA A standalone Fibre Channel-to-Ethernetadapter that allows for simple transparentanalysis of Fibre Channel traffic in aswitched fabric
MDS 9000 Family
Table 1 MDS 9000 Family software and hardware modules not supported(page 2 of 2)
Component EMC part number Description Applicable products
8 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
running NX-OS Release 4x and SAN-OS Release 3x It also providesinformation on installing the MDS 9513 Fabric 2 modules andactivating higher bandwidth
Configuring Generation 3 and Generation 2 Switching ModulesThe Cisco MDS 9500 Multilayer Directors are designed to operatewith any combination of Cisco MDS 9000 Generation 2 andGeneration 3 modules However there are limitations to considerwhen combining the various modules and supervisors in the CiscoMDS 9500 Series platform chassis The references listed in this sectionprovide specific information about configurations that combinedifferent modules and supervisors
For information on configuring Generation 2 and Generation 3switching modules refer to the Configuring Generation 2 andGeneration 3 Switching Modules chapter in the Cisco MDS 9000Family CLI Configuration Guide
For information on port index availability refer to the ldquoPort IndexAvailabilityrdquo section in the Product Overview chapter of the CiscoMDS 9500 Series Hardware Installation Guide
For information on Cisco MDS 9000 hardware and softwarecompatibility refer to the EMC Support Matrix available through E-LabInteroperability Navigator (ELN) at httpelabnavigatorEMCcom
MDS 9000 Chassis and Module Support in Cisco MDS NX-OS 5xTable 2 lists the MDS hardware chassis supported by Cisco MDSNX-OS 5x
Table 2 Cisco MDS NX-OS 5x Chassis Support Matrix
Switch NX-OS 5x Support
MDS 9513 Yes
MDS 9509 Yes
MDS 9506 Yes
MDS 9222i Yes
MDS 9216i No
9
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Table 3 lists the MDS hardware modules supported by Cisco MDSNX-OS 5x
MDS 9216A No
MDS 9216 No
MDS 9148 Yes
MDS 9134 Yes
MDS 9124 Yes
MDS 9140 No
MDS 9120 No
Table 2 Cisco MDS NX-OS 5x Chassis Support Matrix
Switch NX-OS 5x Support
Table 3 Module Support Matrix for Cisco MDS NX-OS 5x (page 1 of 2)
Module DescriptionMDS 9500Series MDS 9222i
DS-X9530-SF2A-K9 MDS 9500 Supervisor-2A Module Yes NA
DS-X9530-SF2-K9 MDS 9500 Supervisor-2 Module Yes NA
DS-X9530-SF1-K9 MDS 9500 Supervisor-1 Module No NA
DS-X9224-96K9 24-port 8-Gbps Fibre Channel Switching Module Yesa No
DS-X9248-96K9 48-port 8-Gbps Fibre Channel Switching Module Yesa No
DS-X9248-48K9 444-port Host Optimized 8-Gbps Fibre ChannelSwitching Module
Yes Yes
DS-X9316-SSNK9 16-Port Storage Services Node (SSN-16) Yes Yes
DS-X9304-18K9 184-Port Multiprotocol Services Module(MSM-184)
Yes Yes
DS-X9112 12-port 4-Gbps Fibre Channel Switching Module Yes Yes
DS-X9124 24-port 4-Gbps Fibre Channel Switching Module Yes Yes
DS-X9148 48-port 4-Gbps Fibre Channel Switching Module Yes Yes
DS-X9704 4-port 10-Gbps Fibre Channel Switching Module Yes Yes
10 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Migrating from Supervisor-1 Modules to Supervisor-2 ModulesAs of Cisco MDS SAN-OS Release 30(1) the Cisco MDS 9509 and9506 Directors support both Supervisor-1 and Supervisor-2 modulesSupervisor-1 and Supervisor-2 modules cannot be installed in thesame switch except during migration Both the active and standbysupervisor modules must be of the same type either Supervisor-1 orSupervisor-2 modules For Cisco MDS 9513 Directors bothsupervisor modules must be Supervisor-2 modules
CAUTION
Migrating your supervisor modules is a disruptive operation
Note Migrating from Supervisor-2 modules to Supervisor-1 modules is not supported
To migrate from a Supervisor-1 module to a Supervisor-2 module refer to the step-by-step instructions in the Cisco MDS 9000 NX-OS Release 41(x) and SAN-OS 3(x) Software Upgrade and Downgrade Guide
DS-X9302-14K9 142-port Multiprotocol Services (MPS-142)Module
No No
DS-X9016 16-port 1- 2-Gbps Fibre Channel SwitchingModule
No No
DS-X9032 32-port 1- 2-Gbps Fibre Channel SwitchingModule
No No
DS-X9032-SSM 32-port Storage Services Module (SSM) No No
DS-X9308-SMIP 8-port 1- 2-Gbps IP Switching Module No No
DS-X9304-SMIP 4-port 1- 2-Gbps IP Switching Module No No
a Requires DS-13SLT-FAB2 in the MDS 9513
Table 3 Module Support Matrix for Cisco MDS NX-OS 5x (page 2 of 2)
Module DescriptionMDS 9500Series MDS 9222i
11
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Software Download ProcessUse the software download procedure to upgrade to a later versionor downgrade to an earlier version of an operating system Thissection describes the software download process for the Cisco MDSNX-OS software and includes the following topics
ldquoDetermining the Software Versionrdquo on page 11
ldquoDownloading Softwarerdquo on page 11
ldquoSelecting the Correct Software Image for an MDS 9100 SeriesSwitchrdquo on page 12
ldquoSelecting the Correct Software Image for an MDS 9200 SeriesSwitchrdquo on page 13
ldquoSelecting the Correct Software Image for an MDS 9500 SeriesSwitchrdquo on page 13
Determining the Software VersionTo determine the version of Cisco MDS NX-OS or SAN-OS softwarecurrently running on a Cisco MDS 9000 Family switch using the CLIlog in to the switch and enter the show version EXEC command
To determine the version of Cisco MDS NX-OS or SAN-OS softwarecurrently running on a Cisco MDS 9000 Family switch using theFabric Manager view the Switches tab in the Information pane locatethe switch using the IP address logical name or WWN and check itsversion in the Release column
Note EMC strongly recommends that you use the latest qualified softwarerelease for all MDS 9000 Family products Refer to the EMC Support Matrixavailable through E-Lab Interoperability Navigator (ELN) athttpelabnavigatorEMCcom for the latest information on qualifiedfirmware revisions
Downloading SoftwareThe Cisco MDS NX-OS software is designed for mission-critical highavailability environments To realize the benefits of nondisruptiveupgrades on the Cisco MDS 9500 Directors we highly recommendthat you install dual supervisor modules
12 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Before performing upgrades submit all requested changes to theEMC Global Services CCA change control process so that anypotential operating environment impacts can be analyzedbeforehand
EMC personnel should also refer to the Connectrix MDS 9000 FamilySoftware Image Upgrade Instructions for a complete list of prerequisitesThis document is available on the Global Services websitehttpwwwcsisusEMCcom under Application Download AreaESN Product Information Connectrix MDS 9000 Family EMCpersonnel can download the Software Images from the GlobalServices website httpwwwcsisusEMCcom under ApplicationDownload Area ESN Product Information Connectrix MDS 9000Family
See the following sections in this release note for details on how youcan nondisruptively upgrade your Cisco MDS 9000 switch Issuingthe install all command from the CLI or using Fabric Manager toperform the downgrade enables the compatibility check The checkindicates if the upgrade can happen nondisruptively or disruptivelydepending on the current configuration of your switch and thereason
Compatibility check is doneModule bootable Impact Install-type Reason------ -------- -------------- ------------ ------
1 yes non-disruptive rolling2 yes disruptive rolling Hitless upgrade is not supported3 yes disruptive rolling Hitless upgrade is not supported4 yes non-disruptive rolling5 yes non-disruptive reset6 yes non-disruptive reset
Selecting the Correct Software Image for an MDS 9100 Series SwitchThe system and kickstart image that you use for an MDS 9100 seriesswitch depends on which switch you use as shown in Table 4
Table 4 Software Images for MDS 9100 Series Switches
Cisco MDS 9100 Series Switch Type Naming Convention
9124 and 9134 Filename begins with m9100-s2ek9
9148 Filename begins with m9100-s3ek9
13
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Selecting the Correct Software Image for an MDS 9200 Series SwitchThe system and kickstart image that you use for an MDS 9200 seriesswitch depends on which switch you use as shown in Table 5
Selecting the Correct Software Image for an MDS 9500 Series SwitchThe system and kickstart image that you use for an MDS 9500 Seriesswitch depends on whether the switch is based on a Supervisor-1module or a Supervisor-2 module as shown in Table 6
Use the show module command to display the type of supervisormodule in the switch The following is sample output from the showmodule command on a Supervisor 2 module
Table 5 Software Images for MDS 9200 Series Switches
Cisco MDS 9200 Series Switch Type Naming Convention
9222i Filename begins with m9200-s2ek9
Table 6 Software Images for Supervisor Type
Cisco MDS 9500 Series Switch Type Supervisor Module Type Naming Convention
9513 9509 and 9506 Supervisor-2 module Filename begins with m9500-sf2ek9
14 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
switch show moduleMod Ports Module-Type Model Status--- ----- -------------------------------- ------------------ ------------7 0 SupervisorFabric-2 DS-X9530-SF2-K9 active 8 0 SupervisorFabric-2 DS-X9530-SF2-K9 ha-standby
Upgrading Your Cisco MDS NX-OS Software ImageThis section lists the guidelines recommended for upgrading yourCisco MDS NX-OS software image and includes the following topics
ldquoGeneral Upgrading Guidelinesrdquo on page 14
ldquoDowngrading Your Cisco MDS SAN-OS Software Imagerdquo onpage 18
Note Before you begin the upgrade process review the list of chassis andmodules that NX-OS Release 50(4b) supports See the ldquoMDS 9000 Chassisand Module Support in Cisco MDS NX-OS 5xrdquo on page 8
Note For detailed instructions for performing a software upgrade usingCisco Fabric Manager see the Cisco Fabric Manager Release Notes forRelease 50(4b) which is available from the following websitehttpPowerlinkEMCcom
General Upgrading Guidelines
Note To upgrade to NX-OS Release 50(4b) you must be running NX-OSRelease 4x If you are running SAN-OS Release 32(3a) or earlier firstupgrade to SAN-OS Release 33(x) then NX-OS Release 4x and thenupgrade to NX-OS Release 50(4b)
Use the following guidelines when upgrading to Cisco MDS NX-OSRelease 5x
Install and configure dual supervisor modules
Issue the show install all impact upgrade-image CLI command todetermine if your upgrade will be nondisruptive
15
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Be aware of the impact of an upgrade on VSAN 4079 if you areupgrading from SAN-OS Release 3x to NX-OS 50(4b) See theldquoUpgrading Effect on VSAN 4079rdquo on page 17
Follow the recommended guidelines for upgrading a Cisco MDS9124 or MDS 9134 Switch as described in ldquoUpgrading a CiscoMDS 9124 or MDS 9134 switchrdquo on page 18
Take note of the affect of upgrades on MDS 9500 series switchesthat have active IOA flows as described in ldquoMDS 9500 seriesupgrades with active IOA flowsrdquo on page 18
Be aware that some features impact whether an upgrade isdisruptive or nondisruptive
bull Fibre Channel Ports Traffic on Fibre Channel ports can benondisruptively upgraded See Table 7 on page 16 for thenondisruptive upgrade path for all NX-OS and SAN-OSreleases
bull Storage Services Intelligent storage services traffic such asSANTap NASB and FC write acceleration is disruptedduring an upgrade Fibre Channel traffic is not
bull Gigabit Ethernet Ports Traffic on Gigabit Ethernet ports isdisrupted during an upgrade or downgrade This includes theGigabit Ethernet ports on the MSM-184 module and the MDS9222i switch Those nodes that are members of VSANs traversingan FCIP ISL are impacted and a fabric reconfiguration occursiSCSI initiators connected to the Gigabit Ethernet ports loseconnectivity to iSCSI targets while the upgrade is in progress
bull FICON If you have FICON enabled the upgrade path isdifferent See Table 6 on page 13
Use Table 7 to determine your nondisruptive upgrade path to Cisco MDSNX-OS Release 50(4b) find the image release number you are currentlyusing in the Current column of the table and use the path recommended
16 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Note The software upgrade information in Table 7 applies only to FibreChannel switching traffic Upgrading system software disrupts IP traffic andSSM intelligent services traffic
MDS NX-OS Release 50(4b) is not a FICON-qualified release
Table 7 Nondisruptive Upgrade Path to Cisco MDS NX-OS Release 50(4b)
Current Nondisruptive Upgrade Path
NX-OS 50(4) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 50(1a) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(7b) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(5) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(3) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(1b) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(1a) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 41(3a) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 41(1b) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
SAN-OS 33(4a) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
NX-OS 33(4) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 33(3) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 33(2) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 33(1c) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 32(3a) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 32(2c) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 32(1a) Upgrade to SAN-OS Release then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 31(3a) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 31(2) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
17
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Use Table 8 to determine your FICON nondisruptive upgrade path toCisco MDS NX-OS Release 42(7b) Find the image release numberyou are currently using in the Current Release with FICON Enabledcolumn of the table and use the path recommended
Note For more information on the FICON qualified NX-OS releases refer tothe EMC Support Matrix available through E-Lab Interoperability Navigator(ELN) at httpelabnavigatorEMCcom
Upgrading Effect on VSAN 4079If you are upgrading to NX-OS Release 50(4b) and you have notcreated VSAN 4079 the NX-OS software will automatically createVSAN 4079 and reserve it for EVFP use If VSAN 4079 is reserved forEVFP use the switchport trunk allowed vsan command will filterout VSAN 4079 from the allowed list as shown in the followingexample
switch(config-if) switchport trunk allowed vsan1-40801-40784080switch(config-if)
If you have created VSAN 4079 the upgrade to NX-OS Release50(4b) will have no affect on VSAN 4079
If you downgrade to a release of NX-OS lower than 41(x) afterNX-OS Release 50(4b) creates VSAN 4079 and reserves it for EVFPuse the VSAN will no longer be reserved
Table 8 FICON Nondisruptive Upgrade Path to NX-OS Release 42(7b)
Current Release withFICON Enabled Upgrade Path
NX-OS 42(1b) You can nondisruptively upgrade directly to NX-OS Release 42(7b)
NX-OS 41(1c) You can nondisruptively upgrade directly to NX-OS Release 42(7b)
SAN-OS 33(1c) You can nondisruptively upgrade directly to NX-OS Release 42(7b)
18 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Upgrading a Cisco MDS 9124 or MDS 9134 switchIf you are upgrading from Cisco MDS SAN-OS Release 31(1) to CiscoNX-OS Release 4x before upgrading to NX-OS Release 50(4b) on aCisco MDS 9124 or MDS 9134 switch follow these guidelines
During the upgrade configuration is not allowed and the fabric isexpected to be stable
The Fabric Shortest Path First (FSPF) timers must be configured tothe default value of 20 seconds otherwise the nondisruptiveupgrade is blocked to ensure that the maximum down toim forthe control plane can be 80 seconds
If there are any CFS commits in the fabric the nondisruptiveupgrade will fail
If there is a zone server merge in progress in the fabric thenondisruptive upgrde will fail
If a service terminates the nondisruptive upgrade the showinstall all failure-reason command can display the reason thatthe nondisruptive upgrade cannot proceed
If there is not enough memory in the system to load the newimages the upgrade will be made disruptive due to insufficientresources and the user will be notified in the compativility table
MDS 9500 series upgrades with active IOA flowsWhen upgading an MDS 9500 series switch that has active IOA flowsthose flows may be interrupted during the supervisor moduleswitchover To workaround this issue you have to enablespanning-tree portfast on the interface on the catalyst connected tothe management interface of the activestandby supervisor for theinterface to come up fast without causing the cluster to lose quorum
Downgrading Your Cisco MDS SAN-OS Software ImageThis section lists the guidelines recommended for downgrading yourCisco MDS SAN-OS software image and includes the followingtopics
ldquoGeneral downgrading guidelinesrdquo on page 19
19
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
General downgrading guidelinesUse the following guidelines to nondisruptively downgrade yourCisco MDS NX-OS Release 50(4b)
Install and configure dual supervisor modules
Issue the system no acl-adjacency-sharing execute command todisable acl adjacency usage on Generation 2 and Generation 1modules If this command fails reduce the number of zones IVRzones TE ports or a combination of these in the system and issuethe command again
Disable all features not supported by the downgrade release Usethe show incompatibility system downgrade-image command todetermine what you need to disable
bull If you are running in interoperability mode two such featuresare the Reliable Commit Service and Full Zone DatabaseDistribution They can be disabled by running thesecommand in config term mode
no zone rcs enableno zoneset capability distribute full
Use the show install all impact downgrade-image command todetermine if your downgrade will be nondisruptive
Be aware that some features impact whether a downgrade isdisruptive or nondisruptive
bull Fibre Channel Ports Traffic on Fibre Channel ports can benondisruptively downgraded See Table 9 on page 20 for thenondisruptive downgrade path for all SAN-OS releases
bull Storage Services Intelligent storage services traffic such asSANTap NASB and FC write acceleration is disruptedduring a downgrade Fibre Channel traffic is not
bull Gigabit Ethernet Ports Traffic on Gigabit Ethernet ports isdisrupted during a downgrade This includes the GigabitEthernet ports on the MSM-184 module and the MDS 9222iswitch Those nodes that are members of VSANs traversing anFCIP ISL are impacted and a fabric reconfiguration occursiSCSI initiators connected to the Gigabit Ethernet ports loseconnectivity to iSCSI targets while the downgrade is inprogress
20 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
bull FICON If you have FICON enabled the downgrade path isdifferent See Table 10 on page 21
Note A downgrade from NX-OS Release 4x to SAN-OS Release 33(1c) is notsupported on MDS switches when FC-Redirect based applications such asData Mobility Manager or Storage Media Encryption are configured in thefabric if either of the following conditions are satisfied
1 A target for which FC-Redirect is configured is connected locally and thereare Generation 1 modules with ISLs configured in the switch
2 A host for which FC-redirect is configured is connected locally ona Generation 1 module
If these conditions exist remove the application configuration forthese targets and hosts before proceeding with the downgrade
Use Table 9 on page 20 to determine the nondisruptive downgradepath from Cisco NX-OS Release 50(4b) Find the NX-OS or SAN-OSimage you want to downgrade to in the To SAN-OSNX-OS Releasecolumn of the table and use the path recommended
Note The software downgrade information in Table 10 on page 21 appliesonly to Fibre Channel switching traffic Downgrading system softwaredisrupts IP and SSM intelligent services traffic
Table 9 Nondisruptive Downgrade Path from NX-OS Release 50(4b) (page 1 of2)
To SAN-OS NX-OSRelease Nondisruptive Downgrade Path
NX-OS 50(4) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 50(1a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(7b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(5) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(3) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(1b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(1a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 41(3a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
21
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Use Table 10 to determine your nondisruptive downgrade path if youhave FICON enabled from Cisco NX-OS Release 42(7b) Find the imagerelease number you are currently using in the Current Release withFICON Enabled column of the table and use the path recommended
NX-OS 41(1b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
SAN-OS 33(5a) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33())
SAN-OS 33(5) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(4a) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
NX-OS 33(4) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(3) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
NX-OS 33(2) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(1c) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 32(3a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 32(x)
SAN-OS 32(2c) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 32(x)
SAN-OS 32(1a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
SAN-OS 31(3a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
SAN-OS 31(2) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
Table 9 Nondisruptive Downgrade Path from NX-OS Release 50(4b) (page 2 of2)
To SAN-OS NX-OSRelease Nondisruptive Downgrade Path
Table 10 FICON Downgrade Path from NX-OS Release 42(7b)
To SAN-OSNX-OS Release withFICON Enabled Downgrade Path
NX-OS 42(1b) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
NX-OS 41(1c) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
SAN-OS 33(1c) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
22 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Best practicesLog messages are not saved across system reboots or power outagesTherefore EMC recommends that customers configure a SyslogServer in order to redirect and capture all log messages on a remoteserver For more information please refer to the Cisco MDS 9000Family Configuration Guide available at
httpwwwciscocomenUSproductsps5989products_support_series_homehtml
Maximum ports per chassisTable 11 shows the maximum ports per chassis
a V2 indicates a 9506 or 9509 with Generation-2 Supervisors The presence of anygeneration one module in a switch will limit the maximum port count to 252This includes the 16-port 32-port 14+2 IPS4 and IPS8 cards
Known problems and limitationsFor a list of problems with this release please refer to the CiscoRelease notes located at
httpwwwciscocomenUSproductsps5989prod_release_notes_listhtml
Limitations and restrictionsThe following limitations and restrictions apply to all switches in theCisco MDS 9000 Family unless a limitation for a specific switch isstated
ldquoStorage Media Encryption (SME) limitationsrdquo on page 24
Table 11 Maximum ports per chassis
Chassis Maximum number of ports
MDS 9506-V2 192a
MDS 9509-V2 336
MDS 9513 528
23
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
ldquoSME configuration limitsrdquo on page 24
ldquoDeleting Cisco SME interfacesrdquo on page 25
ldquoCisco MDS 9124 and 9134 Multilayer fabric switchesrdquo on page 25
ldquoN-Port virtualization configuration limitsrdquo on page 25
ldquoMaximum number of zones supported in Interop Mode 4rdquo onpage 25
ldquoIPv6rdquo on page 26
ldquoIP-ACL supportrdquo on page 26
ldquoUser Rolesrdquo on page 26
ldquoUsing a RSA Version 1 Key for SSH Following an Upgraderdquo onpage 27
ldquoApplying Zone Configurations to VSAN 1rdquo on page 27
ldquoInterVSAN Routingrdquo on page 28
ldquoRSPAN Traffic Not Supported on CTS Ports on 8-GbpsSwitching Modulesrdquo on page 28
ldquoIO Accelerator Feature Limitationsrdquo on page 28
ldquoSupport for FCIP Compression Modesrdquo on page 28
ldquoSaving Copies of the Running Kickstart and System Imagesrdquo onpage 29
ldquoConfiguring Buffer Credits on a Generation 2 or Generation 3Modulerdquo on page 29
ldquoStorage services module power budgetrdquo on page 29
ldquoiSCSI proxy initiator in Celerra HighRoad environmentsrdquo onpage 30
ldquoHPUX N_port IDrdquo on page 30
ldquoInteroperability limitationsrdquo on page 31
ldquoNASBrdquo on page 31
ldquoReserved VSAN Range and Isolated VSAN Range Guidelinesrdquoon page 31
ldquoSymmetrix VMax limitationsrdquo on page 32
ldquoStorage Applications on the MSM-184rdquo on page 32
ldquoDowngrading with fport-channel-trunk enabledrdquo on page 32
ldquoLDAP Authenticationrdquo on page 33
24 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
ldquoMDS-9148 limitationsrdquo on page 33
Storage Media Encryption (SME) limitationsAn SME node can only belong to one cluster Adding the node tomore than one cluster will cause problems
Currently there is no prevention or warning in place when an attemptis made to add a node to multiple clusters
SME configuration limitsTable 12 lists the SME configuration limits for this release
Table 12 SME configuration limits
Configuration Limits
Number of switches in the fabric 10
Number of clusters per switch 1
Switches in a cluster 4
Fabrics in a cluster 2
Modules in a switch 11
Cisco MSM-184 modules in a cluster 32
Initiator-Target-LUNs (ITLs) 1024
LUNs behind a target 32
Host and target ports in a cluster 128
Number of hosts per target 128
Tape backup groups per cluster 2
Volume groups in a tape backup group 4
Cisco Key Management Center ( of keys) 32K
Targets per switch that can be FC-redirected 32
25
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Deleting Cisco SME interfacesA Cisco SME interface can be deleted from the cluster only after theinterface is administratively shut-down and all related tasksassociated with the interface shut-down are complete
Cisco MDS 9124 and 9134 Multilayer fabric switchesThe Cisco MDS 9124 and 9134 Multilayer fabric switches do notsupport the following Cisco MDS SAN-OS features
IVR Remote Span Translative loop support FCCmdash no generation quench reaction only
In addition the following features have these limits
VSANs mdash 16 maximum SPAN mdash 1 session maximum
N-Port virtualization configuration limitsThe NPV features have maximum configuration limits Table 13shows the verified and maximum limits for the NPV switchesrunning NX-OS Release 5x
Maximum number of zones supported in Interop Mode 4In interop mode 4 the maximum number of zones that is supportedin an active zone set is 2047 due to limitations in the connectedvendor switch When IVR is used in interop mode 4 the maximumnumber of zones supported including IVR zones in the active zoneset is 2047 The limit for the maximum number of IVR zones perVSAN is 250 zones (two members per zone)
Table 13 NPV features limitations
Feature Verified limits Maximum limits
FLOGIs or F Disc per NPV port group 114 114
NPV switches per NPV core switch 105 105
FLOGIs per line card on NPV core switch 400 400
26 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
IPv6The management port on Cisco MDS switches supports oneuser-configured IPv6 address but does not supportauto-configuration of an IPv6 address
IP-ACL supportDo not apply IP-ACLs to only one member of a PortChannel groupApply IP-ACLs to the entire channel group
If IP-ACLs are already configured in a Gigabit Ethernet interface youcannot add this interface to a Ethernet PortChannel group
Refer to the Cisco MDS 9000 Family Configuration Guide
User RolesIn SAN-OS Release 33(x) and earlier when a user belongs to a rolewhich has a VSAN policy set to Deny and the role allows access to aspecific set of VSANs (for example 1 through 10) the user isrestricted from performing the configuration clear execute anddebug commands which had a VSAN parameter outside thisspecified set Beginning with NX-OS Release 41(1b) these users arestill prevented from performing configuration clear execute anddebug commands as before however they are allowed to performshow commands for all VSANs The ability to execute the showcommand addresses the following
In a network environment users often need to view informationin other VSANs even though they do not have permission tomodify configurations in those VSANs
This behavior makes Cisco MDS 9000 Series switches consistentwith other Cisco products such as Cisco Nexus 7000 Seriesswitches that exhibit the same behavior for those roles (whenthey apply to the VLAN policy)
27
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Using a RSA Version 1 Key for SSH Following an UpgradeFor security reasons NX-OS Release 42(x) and higher does notsupport RSA version 1 keys As a result if you upgrade from anearlier version that did support RSA version 1 keys and you hadconfigured a RSA version 1 key for SSH then you will not be able tolog in through SSH following the upgrade
If you have a RSA version 1 key configured for SSH beforeupgrading to NX-OS Release 42(x) or higher follow these steps
1 Disable SSH
2 Create RSA version 2 DSA keys
3 Enable SSH
4 Delete any RSA version 1 keys on any remote SSH clients andreplace the version 1 keys with the new version 2 keys from theswitch
Proceed with the upgrade to NX-OS Release 42(x) or higher
If you upgrade before disabling SSH and creating RSA version 2 keysfollow these steps
1 Open a Telnet session and log in through the console
2 Issue the no feature ssh command to disable SSH
3 Issue the ssh key rsa 1024 command to create RSA version 2 keys
4 Issue the feature ssh command to enable SSH
Applying Zone Configurations to VSAN 1In the setup script you can configure system default values for thedefault-zone to be permit or deny and you can configure defaultvalues for the zone distribution method and for the zone mode
These default settings are applied when a new VSAN is createdHowever the settings will not take effect on VSAN 1 because it existsprior to running the setup script Therefore when you need thosesettings for VSAN 1 you must explicitly issue the followingcommands
zone default-zone permit vsan 1 zoneset distribute full vsan 1 zone mode enhanced vsan 1
28 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
InterVSAN RoutingWhen using InterVSAN Routing (IVR) it is recommended to enableCisco Fabric Services (CFS) on all IVR-enabled switches Failure to doso may cause mismatched active zone sets if an error occurs duringzone set activation
RSPAN Traffic Not Supported on CTS Ports on 8-Gbps Switching ModulesAn inter-switch link (ISL) that is enabled for Cisco TrustSec (CTS)encryption must be brought up in non-CTS mode to support remoteSPAN (RSPAN) traffic on the following modules
DS-X9248-96K9 Cisco MDS 9000 48-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9224-96K9 Cisco MDS 9000 24-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9248-48K9 Cisco MDS 9000 444-Port Host-Optimized8-Gbps Fibre Channel Switching Module
If the ISL link is brought up with CTS enabled random packets dropsof both RSPAN traffic and normal traffic will occur on the receiverport switch
IO Accelerator Feature LimitationsIOA does not support the following NX-OS features
IVR flows
Devices with NPV and NPIV enabled
F port trunking
bull F port channeling
Support for FCIP Compression ModesIn Cisco NX-OS Release 42(1b) and higher FCIP compression mode 1and compression mode 3 are not supported on the Cisco MSM-184module and on the SSN-16 module
29
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Saving Copies of the Running Kickstart and System ImagesAfter you upgrade to MDS NX-OS Release 42(1b) or higher you arenot allowed to delete rename move or overwrite the kickstart andsystem images that are in the current system bootvar settings on anactive or standby MDS Supervisor-2 module on any Cisco MDS 9500Series switch This restriction does not apply to the integratedsupervisor module on the MDS 9200 and MDS 9100 series switches
Configuring Buffer Credits on a Generation 2 or Generation 3 ModuleWhen you configure port mode to auto or E on a Generation 2module one of the ports will not come up for the followingconfiguration
Port Mode auto or E for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E on a Generation 3module one or two of the ports will not come up for the followingconfiguration
Port Mode auto or E for the first half of the ports the second halfof the ports or for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E for all ports in the globalbuffer pool you need to reconfigure buffer credits on one or more ofthe ports The total number of buffer credits configured for all theports in the global buffer pool should be reduced by 64
Storage services module power budgetThe MDS 9509 does not have the power budget to run seven SSMcards EMC recommends a maximum of four SSMs in one 9509Customers wishing to use more than four SSMs in one chassis shouldrefer to the Cisco MDS 9000 documentation on the Ciscocom websiteto validate that there is enough power available for their desiredconfiguration
30 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Note Upgrading to the 3000 watt power supplies will alleviate thiscondition
iSCSI proxy initiator in Celerra HighRoad environmentsEMC supports the iSCSI proxy initiator feature in Celerrareg
HighRoadreg environments In proxy initiator mode one Fibre Channelinitiator is used for all iSCSI clients who access the switch via thesame iSCSI interface (iscsi33 for example)
The initiators will use the PWWN assigned to the iSCSI interface TheiSCSI interface to which an iSCSI client will logon to is configured inthe client and must be permitted by the virtual target configured forthat initiator
The current session environment supported on the MDS is
300 sessions per port 1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no InitialR2T=yes
Refer to the specific initiator support documentation on how to setthe parameters The implementation will not perform properly ifthese bits are not set
Refer to the MDS documentation for more information regarding theconfiguration of the iSCSI proxy initiator at the following Ciscowebsite
httpwwwciscocomenUSproducts
HPUX N_port IDThe N_port ID port value of 255 (0xFF) has special meaning forHP-UX A N_port ID (FC_ID) can not be returned from a switch thatcontains this value for the N_port ID (FC_ID) port value for a HP-UXinitiator or HP-UX target port Port ID value of 255 (0xFF) cannot be
31
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
configured for HP-UX initiator port and HP-UX target ports whenconfiguring MDS FC_IDs The port_ID value is the third byte of theFC_ID
Interoperability limitationsRefer to the EMC Support Matrix (ESM) and the EMC Networked Storage Topology Guide for modes of operation and caveats
NASBThe NASB feature requires that the backup application load the tapedrive with a compatible tape cartridge prior to configuring NASB inthe backup VSAN
Reserved VSAN Range and Isolated VSAN Range GuidelinesOn an NPV switch with a trunking configuration on any interface or ona regular switch where the feature fport_channel_trunk command hasbeen issued to enable the F PortChannel feature follow theseconfiguration guidelines for reserved VSANs and the isolated VSAN
bull If trunk mode is on for any of the interfaces or NP PortChannelis up the reserved VSANs are 3040 to 4078 and they are notavailable for user configuration
bull The Exchange Virtual Fabric Protocol (EVFP) isolated VSAN is4079 and it is not available for user configuration
bull VSAN 4079 will be impacted by an upgrade to NX-OS Release42(3) depending on whether or not VSAN 4079 was createdprior to the upgrade See theldquoUpgrading Effect on VSAN 4079rdquoon page 17
The following VSAN IDs are assigned in the Fibre Channel Framingand Signaling (FC-FS) interface standard
VF_ID Value Value Description
00h Do not use as a Virtual FabricIdentifier
001h EFFh Available as a Virtual FabricIdentifier
F00h FEEh Reserved
32 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Symmetrix VMax limitationsAt the time of this writing the following features are not supportedfor use with the Symmetrix VMax
FCIP Write Acceleration
The NX-OS IOA functionality is only supported with the Q2 SREnginuity release 5874229182 or higher
For the most up to date status please refer to the current revision ofthese Release Notes on httpPowerlinkemccom and the EMCSupport Matrix available through E-Lab Interoperability Navigator (ELN) athttpelabnavigatorEMCcom
Storage Applications on the MSM-184The MDS 9000 184-Port Multiservice Module (MSM-184) does notsupport multiple concurrent storage applications Only oneapplication can run on the MSM-184 at a time
Downgrading with fport-channel-trunk enabledIf you are running MDS NX-OS Release 42(x) or higher with thefport-channel-trunk feature enabled and you downgrade to anyNX-OS 41(1x) release the installer performs a nondisruptivedowngrade even though the fport-channel-trunk feature is notsupported in NX-OS 41(1x) releases
As a result the switch is in an inconsistent state and the ports maynot function properly
FEFh Control VF-ID (see FibreChannel Link Services (FC-LS)and Fibre Channel SwitchFabric Generation 4 (FC-SW-4)standards)
FF0h FFEh Vendor specific
FFFh Do not use as a Virtual FabricIdentifier
FEFh = 4079
33
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
If you are in this state a workaround is to reboot the switch followingthe upgrade
LDAP AuthenticationThere is currently a limitation in the LDAP server configuration CLIthat prevents the use of an OU with spaces in the name Normallythese OU names could be surrounded by quotation marks howeverquotation marks are not supported by the ldap-server command
MDS-9148 limitationsThe Cisco MDS 9148 Multilayer Fabric Switch does not support thefollowing NX-OS features
Medium and Long range 4GB Agilent
IVR
Remote Span
Translative loop support
FCC - no generation quench reaction only
FC-Redirect
In addition the following features have these limits
VSANS - 31 maximum
SPAN - 1 session maximum
Technical notesThe following sections provide further information on technicalnotes
EMC Email Home for Cisco MDS switchesInstallation and Trouble shooting instructions can be found in thedocumentation located at the EMC Customer Service Internalwebsite
httpwwwcsisusemccomcsweb2esnesnhomehtmConnectrix20MDS20900020Family
34 EMC Connectrix MDS 9000 NX-OS Release Notes
Technical notes
Customers requiring installation of this solution should contact theirEMC Customer Engineer to assist with the installation and providethe documentation
Supported iSCSI sessionsThe current iSCSI session environment supported on the MDS is
300 sessions per port
1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no
InitialR2T=yes
Upgrading Cisco SAN-OSThere are several methods available for upgrading SAN-OS SoftwareEMC personnel are strongly recommended that all upgrades be doneby the Automated One-Step Upgrade using the install all
command EMC personnel should refer to the Connectrix MDS 9000Family Software Image Upgrade Instructions for a complete list ofprerequisites and instructions for performing the upgrade Thisdocument along with tftp software is available on the GlobalServices website at httpwwwcsisusEMCcom under ApplicationDownload Area ESN Product Information Connectrix MDS 9000Family
The Software Upgrade Wizard is an option for upgrades While theinstall all is the preferred method the Software Install Wizard canalso be used
Supported configuration parametersFor the most up-to-date information refer to the EMC Support Matrixavailable through E-Lab Interoperability Navigator athttpelabnavigatoremccom for the latest information onsupported configurations
35
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
Supported zoning parametersRefer to the EMC Networked Storage Topology Guide for the mostup-to-date information on supported zoning parameters
At the time these notes were published the following parameterswere supported
20 VSANs 5 Hops 2000 Unique members per physical infrastructure 1000 Zonesets per physical infrastructure 2000 Zones per physical infrastructure 1 FCIP tunnel
Supported IVR parameters IVR zone members 1000 IVR zones 1000 IVR zone sets 32 VSANS 20 IVR enabled switches 64
An RPQ can be submitted for any configurations that exceed thislimit
Managing zone changes in multiswitch fabricsZoning changes may be made through Fabric Manager or CLI Whenaccessing Fabric Manager or CLI the user does so from the point ofview of one switch That is Fabric Manager and CLI are accessed byentering the IP address of one switch in the fabric
When zoning changes are made the applicable VSAN and zone setdata is propagated to the rest of the switches in the fabric via the ISLs
When zoning changes are made to a VSAN the zone set data ispropagated to the rest of the switches in the fabric via the ISLs Bydefault only the active zone set information is relayed to all switchesin the VSAN If the user accesses the Fabric Manager and CLI fromanother switch in the fabric the new VSAN and zone set informationwill not be viewable To view the active and inactive zone set on theother switches in the fabric the user must log in to the CLI and issuea command from the EXEC prompt
36 EMC Connectrix MDS 9000 NX-OS Release Notes
Documentation
Example The following is an example of copying VSAN 1 through 20 zoningdata
CiscoMDS_name zone copy active full vsan 1-20
CiscoMDS_name conf t
Enter configuration commands one per line End with CNTL Z
CiscoMDS_name(config) zoneset distribute full vsan 1-20
CiscoMDS_name(config)
Note This command needs to be issued on all switches in the fabric one timeonly
This is a nondisruptive command After issuing the commands theuser will now see the active and inactive zone sets for the specifiedVSANs on any switch that is chosen from which to manage the fabric
After a zoning change is made save the running configuration to thestartup configuration
DocumentationSend documentation comments to mdsfeedback-doccom
Product DocumentationAs of NX-OS Release 42(1a) software configuration information isavailable in new feature-specific configuration guides for thefollowing information
System management
Interfaces
Fabric
Quality of service
Security
IP services
High availability and redundancy
37
Software media organization and files
EMC Connectrix MDS 9000 NX-OS Release Notes
The information in these new guides previously existed in the CiscoMDS 9000 Family CLI Configuration Guide That configuration guideremains available on Ciscocom and should be used for all softwarereleases prior to NX-OS Release 42(1a) Configuration guidesaddress the features introduced in or available in a particular releaseSelect and view the configuration guide that pertains to the softwareinstalled in your switch
In addition Fabric Manager information has been removed from theMDS NX-OS Release Notes (this document) and placed intostandalone Fabric Manager Release Notes that support both CiscoMDS 9000 Family switches and Cisco Nexus 5000 Series switchesThe Cisco Fabric Manager Release Notes are available onhttpPowerlinkemccom and from the following website
httpwwwciscocomenUSpartnerproductsps10495prod_release_notes_listhtml
Technical supportThese release notes complement a Cisco documentation set EachCisco document refers to where to get help However for any itemssupplied by EMC see ldquoTroubleshooting and getting helprdquo onpage 38
Software media organization and filesFor information on related software environment and systemrequirements refer to the EMC Support Matrix on EMC Powerlink at
httpPowerlinkEMCcom
InstallationFor hardware installation information refer to the Cisco MDS HWInstallation Guides available at Ciscocom
For EMC-specific installation information refer to ldquoEnvironment andsystem requirementsrdquo on page 5 in this document
38 EMC Connectrix MDS 9000 NX-OS Release Notes
Troubleshooting and getting help
Troubleshooting and getting helpEMC support product and licensing information can be obtained asfollows
Product information mdash For documentation release notes softwareupdates or for information about EMC products licensing andservice go to the EMC Powerlink website (registration required) at
httpPowerlinkEMCcom
Technical support mdash For technical support go to EMC CustomerService on Powerlink To open a service request through Powerlinkyou must have a valid support agreement Please contact your EMCsales representative for details about obtaining a valid supportagreement or to answer any questions about your account
Copyright copy 2011 EMC Corporation All rights reserved
EMC believes the information in this publication is accurate as of its publication date The information issubject to change without notice
THE INFORMATION IN THIS PUBLICATION IS PROVIDED ldquoAS ISrdquo EMC CORPORATION MAKES NOREPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION INTHIS PUBLICATION AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OFMERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Use copying and distribution of any EMC software described in this publication requires an applicablesoftware license
For the most up-to-date regulatory document for your product line go to the Technical Documentation andAdvisories section on EMC Powerlink
For the most up-to-date listing of EMC product names see EMC Corporation Trademarks on EMCcom
All other trademarks used herein are the property of their respective owners
8 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
running NX-OS Release 4x and SAN-OS Release 3x It also providesinformation on installing the MDS 9513 Fabric 2 modules andactivating higher bandwidth
Configuring Generation 3 and Generation 2 Switching ModulesThe Cisco MDS 9500 Multilayer Directors are designed to operatewith any combination of Cisco MDS 9000 Generation 2 andGeneration 3 modules However there are limitations to considerwhen combining the various modules and supervisors in the CiscoMDS 9500 Series platform chassis The references listed in this sectionprovide specific information about configurations that combinedifferent modules and supervisors
For information on configuring Generation 2 and Generation 3switching modules refer to the Configuring Generation 2 andGeneration 3 Switching Modules chapter in the Cisco MDS 9000Family CLI Configuration Guide
For information on port index availability refer to the ldquoPort IndexAvailabilityrdquo section in the Product Overview chapter of the CiscoMDS 9500 Series Hardware Installation Guide
For information on Cisco MDS 9000 hardware and softwarecompatibility refer to the EMC Support Matrix available through E-LabInteroperability Navigator (ELN) at httpelabnavigatorEMCcom
MDS 9000 Chassis and Module Support in Cisco MDS NX-OS 5xTable 2 lists the MDS hardware chassis supported by Cisco MDSNX-OS 5x
Table 2 Cisco MDS NX-OS 5x Chassis Support Matrix
Switch NX-OS 5x Support
MDS 9513 Yes
MDS 9509 Yes
MDS 9506 Yes
MDS 9222i Yes
MDS 9216i No
9
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Table 3 lists the MDS hardware modules supported by Cisco MDSNX-OS 5x
MDS 9216A No
MDS 9216 No
MDS 9148 Yes
MDS 9134 Yes
MDS 9124 Yes
MDS 9140 No
MDS 9120 No
Table 2 Cisco MDS NX-OS 5x Chassis Support Matrix
Switch NX-OS 5x Support
Table 3 Module Support Matrix for Cisco MDS NX-OS 5x (page 1 of 2)
Module DescriptionMDS 9500Series MDS 9222i
DS-X9530-SF2A-K9 MDS 9500 Supervisor-2A Module Yes NA
DS-X9530-SF2-K9 MDS 9500 Supervisor-2 Module Yes NA
DS-X9530-SF1-K9 MDS 9500 Supervisor-1 Module No NA
DS-X9224-96K9 24-port 8-Gbps Fibre Channel Switching Module Yesa No
DS-X9248-96K9 48-port 8-Gbps Fibre Channel Switching Module Yesa No
DS-X9248-48K9 444-port Host Optimized 8-Gbps Fibre ChannelSwitching Module
Yes Yes
DS-X9316-SSNK9 16-Port Storage Services Node (SSN-16) Yes Yes
DS-X9304-18K9 184-Port Multiprotocol Services Module(MSM-184)
Yes Yes
DS-X9112 12-port 4-Gbps Fibre Channel Switching Module Yes Yes
DS-X9124 24-port 4-Gbps Fibre Channel Switching Module Yes Yes
DS-X9148 48-port 4-Gbps Fibre Channel Switching Module Yes Yes
DS-X9704 4-port 10-Gbps Fibre Channel Switching Module Yes Yes
10 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Migrating from Supervisor-1 Modules to Supervisor-2 ModulesAs of Cisco MDS SAN-OS Release 30(1) the Cisco MDS 9509 and9506 Directors support both Supervisor-1 and Supervisor-2 modulesSupervisor-1 and Supervisor-2 modules cannot be installed in thesame switch except during migration Both the active and standbysupervisor modules must be of the same type either Supervisor-1 orSupervisor-2 modules For Cisco MDS 9513 Directors bothsupervisor modules must be Supervisor-2 modules
CAUTION
Migrating your supervisor modules is a disruptive operation
Note Migrating from Supervisor-2 modules to Supervisor-1 modules is not supported
To migrate from a Supervisor-1 module to a Supervisor-2 module refer to the step-by-step instructions in the Cisco MDS 9000 NX-OS Release 41(x) and SAN-OS 3(x) Software Upgrade and Downgrade Guide
DS-X9302-14K9 142-port Multiprotocol Services (MPS-142)Module
No No
DS-X9016 16-port 1- 2-Gbps Fibre Channel SwitchingModule
No No
DS-X9032 32-port 1- 2-Gbps Fibre Channel SwitchingModule
No No
DS-X9032-SSM 32-port Storage Services Module (SSM) No No
DS-X9308-SMIP 8-port 1- 2-Gbps IP Switching Module No No
DS-X9304-SMIP 4-port 1- 2-Gbps IP Switching Module No No
a Requires DS-13SLT-FAB2 in the MDS 9513
Table 3 Module Support Matrix for Cisco MDS NX-OS 5x (page 2 of 2)
Module DescriptionMDS 9500Series MDS 9222i
11
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Software Download ProcessUse the software download procedure to upgrade to a later versionor downgrade to an earlier version of an operating system Thissection describes the software download process for the Cisco MDSNX-OS software and includes the following topics
ldquoDetermining the Software Versionrdquo on page 11
ldquoDownloading Softwarerdquo on page 11
ldquoSelecting the Correct Software Image for an MDS 9100 SeriesSwitchrdquo on page 12
ldquoSelecting the Correct Software Image for an MDS 9200 SeriesSwitchrdquo on page 13
ldquoSelecting the Correct Software Image for an MDS 9500 SeriesSwitchrdquo on page 13
Determining the Software VersionTo determine the version of Cisco MDS NX-OS or SAN-OS softwarecurrently running on a Cisco MDS 9000 Family switch using the CLIlog in to the switch and enter the show version EXEC command
To determine the version of Cisco MDS NX-OS or SAN-OS softwarecurrently running on a Cisco MDS 9000 Family switch using theFabric Manager view the Switches tab in the Information pane locatethe switch using the IP address logical name or WWN and check itsversion in the Release column
Note EMC strongly recommends that you use the latest qualified softwarerelease for all MDS 9000 Family products Refer to the EMC Support Matrixavailable through E-Lab Interoperability Navigator (ELN) athttpelabnavigatorEMCcom for the latest information on qualifiedfirmware revisions
Downloading SoftwareThe Cisco MDS NX-OS software is designed for mission-critical highavailability environments To realize the benefits of nondisruptiveupgrades on the Cisco MDS 9500 Directors we highly recommendthat you install dual supervisor modules
12 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Before performing upgrades submit all requested changes to theEMC Global Services CCA change control process so that anypotential operating environment impacts can be analyzedbeforehand
EMC personnel should also refer to the Connectrix MDS 9000 FamilySoftware Image Upgrade Instructions for a complete list of prerequisitesThis document is available on the Global Services websitehttpwwwcsisusEMCcom under Application Download AreaESN Product Information Connectrix MDS 9000 Family EMCpersonnel can download the Software Images from the GlobalServices website httpwwwcsisusEMCcom under ApplicationDownload Area ESN Product Information Connectrix MDS 9000Family
See the following sections in this release note for details on how youcan nondisruptively upgrade your Cisco MDS 9000 switch Issuingthe install all command from the CLI or using Fabric Manager toperform the downgrade enables the compatibility check The checkindicates if the upgrade can happen nondisruptively or disruptivelydepending on the current configuration of your switch and thereason
Compatibility check is doneModule bootable Impact Install-type Reason------ -------- -------------- ------------ ------
1 yes non-disruptive rolling2 yes disruptive rolling Hitless upgrade is not supported3 yes disruptive rolling Hitless upgrade is not supported4 yes non-disruptive rolling5 yes non-disruptive reset6 yes non-disruptive reset
Selecting the Correct Software Image for an MDS 9100 Series SwitchThe system and kickstart image that you use for an MDS 9100 seriesswitch depends on which switch you use as shown in Table 4
Table 4 Software Images for MDS 9100 Series Switches
Cisco MDS 9100 Series Switch Type Naming Convention
9124 and 9134 Filename begins with m9100-s2ek9
9148 Filename begins with m9100-s3ek9
13
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Selecting the Correct Software Image for an MDS 9200 Series SwitchThe system and kickstart image that you use for an MDS 9200 seriesswitch depends on which switch you use as shown in Table 5
Selecting the Correct Software Image for an MDS 9500 Series SwitchThe system and kickstart image that you use for an MDS 9500 Seriesswitch depends on whether the switch is based on a Supervisor-1module or a Supervisor-2 module as shown in Table 6
Use the show module command to display the type of supervisormodule in the switch The following is sample output from the showmodule command on a Supervisor 2 module
Table 5 Software Images for MDS 9200 Series Switches
Cisco MDS 9200 Series Switch Type Naming Convention
9222i Filename begins with m9200-s2ek9
Table 6 Software Images for Supervisor Type
Cisco MDS 9500 Series Switch Type Supervisor Module Type Naming Convention
9513 9509 and 9506 Supervisor-2 module Filename begins with m9500-sf2ek9
14 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
switch show moduleMod Ports Module-Type Model Status--- ----- -------------------------------- ------------------ ------------7 0 SupervisorFabric-2 DS-X9530-SF2-K9 active 8 0 SupervisorFabric-2 DS-X9530-SF2-K9 ha-standby
Upgrading Your Cisco MDS NX-OS Software ImageThis section lists the guidelines recommended for upgrading yourCisco MDS NX-OS software image and includes the following topics
ldquoGeneral Upgrading Guidelinesrdquo on page 14
ldquoDowngrading Your Cisco MDS SAN-OS Software Imagerdquo onpage 18
Note Before you begin the upgrade process review the list of chassis andmodules that NX-OS Release 50(4b) supports See the ldquoMDS 9000 Chassisand Module Support in Cisco MDS NX-OS 5xrdquo on page 8
Note For detailed instructions for performing a software upgrade usingCisco Fabric Manager see the Cisco Fabric Manager Release Notes forRelease 50(4b) which is available from the following websitehttpPowerlinkEMCcom
General Upgrading Guidelines
Note To upgrade to NX-OS Release 50(4b) you must be running NX-OSRelease 4x If you are running SAN-OS Release 32(3a) or earlier firstupgrade to SAN-OS Release 33(x) then NX-OS Release 4x and thenupgrade to NX-OS Release 50(4b)
Use the following guidelines when upgrading to Cisco MDS NX-OSRelease 5x
Install and configure dual supervisor modules
Issue the show install all impact upgrade-image CLI command todetermine if your upgrade will be nondisruptive
15
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Be aware of the impact of an upgrade on VSAN 4079 if you areupgrading from SAN-OS Release 3x to NX-OS 50(4b) See theldquoUpgrading Effect on VSAN 4079rdquo on page 17
Follow the recommended guidelines for upgrading a Cisco MDS9124 or MDS 9134 Switch as described in ldquoUpgrading a CiscoMDS 9124 or MDS 9134 switchrdquo on page 18
Take note of the affect of upgrades on MDS 9500 series switchesthat have active IOA flows as described in ldquoMDS 9500 seriesupgrades with active IOA flowsrdquo on page 18
Be aware that some features impact whether an upgrade isdisruptive or nondisruptive
bull Fibre Channel Ports Traffic on Fibre Channel ports can benondisruptively upgraded See Table 7 on page 16 for thenondisruptive upgrade path for all NX-OS and SAN-OSreleases
bull Storage Services Intelligent storage services traffic such asSANTap NASB and FC write acceleration is disruptedduring an upgrade Fibre Channel traffic is not
bull Gigabit Ethernet Ports Traffic on Gigabit Ethernet ports isdisrupted during an upgrade or downgrade This includes theGigabit Ethernet ports on the MSM-184 module and the MDS9222i switch Those nodes that are members of VSANs traversingan FCIP ISL are impacted and a fabric reconfiguration occursiSCSI initiators connected to the Gigabit Ethernet ports loseconnectivity to iSCSI targets while the upgrade is in progress
bull FICON If you have FICON enabled the upgrade path isdifferent See Table 6 on page 13
Use Table 7 to determine your nondisruptive upgrade path to Cisco MDSNX-OS Release 50(4b) find the image release number you are currentlyusing in the Current column of the table and use the path recommended
16 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Note The software upgrade information in Table 7 applies only to FibreChannel switching traffic Upgrading system software disrupts IP traffic andSSM intelligent services traffic
MDS NX-OS Release 50(4b) is not a FICON-qualified release
Table 7 Nondisruptive Upgrade Path to Cisco MDS NX-OS Release 50(4b)
Current Nondisruptive Upgrade Path
NX-OS 50(4) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 50(1a) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(7b) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(5) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(3) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(1b) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(1a) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 41(3a) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 41(1b) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
SAN-OS 33(4a) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
NX-OS 33(4) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 33(3) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 33(2) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 33(1c) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 32(3a) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 32(2c) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 32(1a) Upgrade to SAN-OS Release then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 31(3a) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 31(2) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
17
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Use Table 8 to determine your FICON nondisruptive upgrade path toCisco MDS NX-OS Release 42(7b) Find the image release numberyou are currently using in the Current Release with FICON Enabledcolumn of the table and use the path recommended
Note For more information on the FICON qualified NX-OS releases refer tothe EMC Support Matrix available through E-Lab Interoperability Navigator(ELN) at httpelabnavigatorEMCcom
Upgrading Effect on VSAN 4079If you are upgrading to NX-OS Release 50(4b) and you have notcreated VSAN 4079 the NX-OS software will automatically createVSAN 4079 and reserve it for EVFP use If VSAN 4079 is reserved forEVFP use the switchport trunk allowed vsan command will filterout VSAN 4079 from the allowed list as shown in the followingexample
switch(config-if) switchport trunk allowed vsan1-40801-40784080switch(config-if)
If you have created VSAN 4079 the upgrade to NX-OS Release50(4b) will have no affect on VSAN 4079
If you downgrade to a release of NX-OS lower than 41(x) afterNX-OS Release 50(4b) creates VSAN 4079 and reserves it for EVFPuse the VSAN will no longer be reserved
Table 8 FICON Nondisruptive Upgrade Path to NX-OS Release 42(7b)
Current Release withFICON Enabled Upgrade Path
NX-OS 42(1b) You can nondisruptively upgrade directly to NX-OS Release 42(7b)
NX-OS 41(1c) You can nondisruptively upgrade directly to NX-OS Release 42(7b)
SAN-OS 33(1c) You can nondisruptively upgrade directly to NX-OS Release 42(7b)
18 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Upgrading a Cisco MDS 9124 or MDS 9134 switchIf you are upgrading from Cisco MDS SAN-OS Release 31(1) to CiscoNX-OS Release 4x before upgrading to NX-OS Release 50(4b) on aCisco MDS 9124 or MDS 9134 switch follow these guidelines
During the upgrade configuration is not allowed and the fabric isexpected to be stable
The Fabric Shortest Path First (FSPF) timers must be configured tothe default value of 20 seconds otherwise the nondisruptiveupgrade is blocked to ensure that the maximum down toim forthe control plane can be 80 seconds
If there are any CFS commits in the fabric the nondisruptiveupgrade will fail
If there is a zone server merge in progress in the fabric thenondisruptive upgrde will fail
If a service terminates the nondisruptive upgrade the showinstall all failure-reason command can display the reason thatthe nondisruptive upgrade cannot proceed
If there is not enough memory in the system to load the newimages the upgrade will be made disruptive due to insufficientresources and the user will be notified in the compativility table
MDS 9500 series upgrades with active IOA flowsWhen upgading an MDS 9500 series switch that has active IOA flowsthose flows may be interrupted during the supervisor moduleswitchover To workaround this issue you have to enablespanning-tree portfast on the interface on the catalyst connected tothe management interface of the activestandby supervisor for theinterface to come up fast without causing the cluster to lose quorum
Downgrading Your Cisco MDS SAN-OS Software ImageThis section lists the guidelines recommended for downgrading yourCisco MDS SAN-OS software image and includes the followingtopics
ldquoGeneral downgrading guidelinesrdquo on page 19
19
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
General downgrading guidelinesUse the following guidelines to nondisruptively downgrade yourCisco MDS NX-OS Release 50(4b)
Install and configure dual supervisor modules
Issue the system no acl-adjacency-sharing execute command todisable acl adjacency usage on Generation 2 and Generation 1modules If this command fails reduce the number of zones IVRzones TE ports or a combination of these in the system and issuethe command again
Disable all features not supported by the downgrade release Usethe show incompatibility system downgrade-image command todetermine what you need to disable
bull If you are running in interoperability mode two such featuresare the Reliable Commit Service and Full Zone DatabaseDistribution They can be disabled by running thesecommand in config term mode
no zone rcs enableno zoneset capability distribute full
Use the show install all impact downgrade-image command todetermine if your downgrade will be nondisruptive
Be aware that some features impact whether a downgrade isdisruptive or nondisruptive
bull Fibre Channel Ports Traffic on Fibre Channel ports can benondisruptively downgraded See Table 9 on page 20 for thenondisruptive downgrade path for all SAN-OS releases
bull Storage Services Intelligent storage services traffic such asSANTap NASB and FC write acceleration is disruptedduring a downgrade Fibre Channel traffic is not
bull Gigabit Ethernet Ports Traffic on Gigabit Ethernet ports isdisrupted during a downgrade This includes the GigabitEthernet ports on the MSM-184 module and the MDS 9222iswitch Those nodes that are members of VSANs traversing anFCIP ISL are impacted and a fabric reconfiguration occursiSCSI initiators connected to the Gigabit Ethernet ports loseconnectivity to iSCSI targets while the downgrade is inprogress
20 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
bull FICON If you have FICON enabled the downgrade path isdifferent See Table 10 on page 21
Note A downgrade from NX-OS Release 4x to SAN-OS Release 33(1c) is notsupported on MDS switches when FC-Redirect based applications such asData Mobility Manager or Storage Media Encryption are configured in thefabric if either of the following conditions are satisfied
1 A target for which FC-Redirect is configured is connected locally and thereare Generation 1 modules with ISLs configured in the switch
2 A host for which FC-redirect is configured is connected locally ona Generation 1 module
If these conditions exist remove the application configuration forthese targets and hosts before proceeding with the downgrade
Use Table 9 on page 20 to determine the nondisruptive downgradepath from Cisco NX-OS Release 50(4b) Find the NX-OS or SAN-OSimage you want to downgrade to in the To SAN-OSNX-OS Releasecolumn of the table and use the path recommended
Note The software downgrade information in Table 10 on page 21 appliesonly to Fibre Channel switching traffic Downgrading system softwaredisrupts IP and SSM intelligent services traffic
Table 9 Nondisruptive Downgrade Path from NX-OS Release 50(4b) (page 1 of2)
To SAN-OS NX-OSRelease Nondisruptive Downgrade Path
NX-OS 50(4) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 50(1a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(7b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(5) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(3) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(1b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(1a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 41(3a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
21
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Use Table 10 to determine your nondisruptive downgrade path if youhave FICON enabled from Cisco NX-OS Release 42(7b) Find the imagerelease number you are currently using in the Current Release withFICON Enabled column of the table and use the path recommended
NX-OS 41(1b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
SAN-OS 33(5a) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33())
SAN-OS 33(5) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(4a) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
NX-OS 33(4) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(3) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
NX-OS 33(2) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(1c) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 32(3a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 32(x)
SAN-OS 32(2c) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 32(x)
SAN-OS 32(1a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
SAN-OS 31(3a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
SAN-OS 31(2) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
Table 9 Nondisruptive Downgrade Path from NX-OS Release 50(4b) (page 2 of2)
To SAN-OS NX-OSRelease Nondisruptive Downgrade Path
Table 10 FICON Downgrade Path from NX-OS Release 42(7b)
To SAN-OSNX-OS Release withFICON Enabled Downgrade Path
NX-OS 42(1b) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
NX-OS 41(1c) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
SAN-OS 33(1c) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
22 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Best practicesLog messages are not saved across system reboots or power outagesTherefore EMC recommends that customers configure a SyslogServer in order to redirect and capture all log messages on a remoteserver For more information please refer to the Cisco MDS 9000Family Configuration Guide available at
httpwwwciscocomenUSproductsps5989products_support_series_homehtml
Maximum ports per chassisTable 11 shows the maximum ports per chassis
a V2 indicates a 9506 or 9509 with Generation-2 Supervisors The presence of anygeneration one module in a switch will limit the maximum port count to 252This includes the 16-port 32-port 14+2 IPS4 and IPS8 cards
Known problems and limitationsFor a list of problems with this release please refer to the CiscoRelease notes located at
httpwwwciscocomenUSproductsps5989prod_release_notes_listhtml
Limitations and restrictionsThe following limitations and restrictions apply to all switches in theCisco MDS 9000 Family unless a limitation for a specific switch isstated
ldquoStorage Media Encryption (SME) limitationsrdquo on page 24
Table 11 Maximum ports per chassis
Chassis Maximum number of ports
MDS 9506-V2 192a
MDS 9509-V2 336
MDS 9513 528
23
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
ldquoSME configuration limitsrdquo on page 24
ldquoDeleting Cisco SME interfacesrdquo on page 25
ldquoCisco MDS 9124 and 9134 Multilayer fabric switchesrdquo on page 25
ldquoN-Port virtualization configuration limitsrdquo on page 25
ldquoMaximum number of zones supported in Interop Mode 4rdquo onpage 25
ldquoIPv6rdquo on page 26
ldquoIP-ACL supportrdquo on page 26
ldquoUser Rolesrdquo on page 26
ldquoUsing a RSA Version 1 Key for SSH Following an Upgraderdquo onpage 27
ldquoApplying Zone Configurations to VSAN 1rdquo on page 27
ldquoInterVSAN Routingrdquo on page 28
ldquoRSPAN Traffic Not Supported on CTS Ports on 8-GbpsSwitching Modulesrdquo on page 28
ldquoIO Accelerator Feature Limitationsrdquo on page 28
ldquoSupport for FCIP Compression Modesrdquo on page 28
ldquoSaving Copies of the Running Kickstart and System Imagesrdquo onpage 29
ldquoConfiguring Buffer Credits on a Generation 2 or Generation 3Modulerdquo on page 29
ldquoStorage services module power budgetrdquo on page 29
ldquoiSCSI proxy initiator in Celerra HighRoad environmentsrdquo onpage 30
ldquoHPUX N_port IDrdquo on page 30
ldquoInteroperability limitationsrdquo on page 31
ldquoNASBrdquo on page 31
ldquoReserved VSAN Range and Isolated VSAN Range Guidelinesrdquoon page 31
ldquoSymmetrix VMax limitationsrdquo on page 32
ldquoStorage Applications on the MSM-184rdquo on page 32
ldquoDowngrading with fport-channel-trunk enabledrdquo on page 32
ldquoLDAP Authenticationrdquo on page 33
24 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
ldquoMDS-9148 limitationsrdquo on page 33
Storage Media Encryption (SME) limitationsAn SME node can only belong to one cluster Adding the node tomore than one cluster will cause problems
Currently there is no prevention or warning in place when an attemptis made to add a node to multiple clusters
SME configuration limitsTable 12 lists the SME configuration limits for this release
Table 12 SME configuration limits
Configuration Limits
Number of switches in the fabric 10
Number of clusters per switch 1
Switches in a cluster 4
Fabrics in a cluster 2
Modules in a switch 11
Cisco MSM-184 modules in a cluster 32
Initiator-Target-LUNs (ITLs) 1024
LUNs behind a target 32
Host and target ports in a cluster 128
Number of hosts per target 128
Tape backup groups per cluster 2
Volume groups in a tape backup group 4
Cisco Key Management Center ( of keys) 32K
Targets per switch that can be FC-redirected 32
25
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Deleting Cisco SME interfacesA Cisco SME interface can be deleted from the cluster only after theinterface is administratively shut-down and all related tasksassociated with the interface shut-down are complete
Cisco MDS 9124 and 9134 Multilayer fabric switchesThe Cisco MDS 9124 and 9134 Multilayer fabric switches do notsupport the following Cisco MDS SAN-OS features
IVR Remote Span Translative loop support FCCmdash no generation quench reaction only
In addition the following features have these limits
VSANs mdash 16 maximum SPAN mdash 1 session maximum
N-Port virtualization configuration limitsThe NPV features have maximum configuration limits Table 13shows the verified and maximum limits for the NPV switchesrunning NX-OS Release 5x
Maximum number of zones supported in Interop Mode 4In interop mode 4 the maximum number of zones that is supportedin an active zone set is 2047 due to limitations in the connectedvendor switch When IVR is used in interop mode 4 the maximumnumber of zones supported including IVR zones in the active zoneset is 2047 The limit for the maximum number of IVR zones perVSAN is 250 zones (two members per zone)
Table 13 NPV features limitations
Feature Verified limits Maximum limits
FLOGIs or F Disc per NPV port group 114 114
NPV switches per NPV core switch 105 105
FLOGIs per line card on NPV core switch 400 400
26 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
IPv6The management port on Cisco MDS switches supports oneuser-configured IPv6 address but does not supportauto-configuration of an IPv6 address
IP-ACL supportDo not apply IP-ACLs to only one member of a PortChannel groupApply IP-ACLs to the entire channel group
If IP-ACLs are already configured in a Gigabit Ethernet interface youcannot add this interface to a Ethernet PortChannel group
Refer to the Cisco MDS 9000 Family Configuration Guide
User RolesIn SAN-OS Release 33(x) and earlier when a user belongs to a rolewhich has a VSAN policy set to Deny and the role allows access to aspecific set of VSANs (for example 1 through 10) the user isrestricted from performing the configuration clear execute anddebug commands which had a VSAN parameter outside thisspecified set Beginning with NX-OS Release 41(1b) these users arestill prevented from performing configuration clear execute anddebug commands as before however they are allowed to performshow commands for all VSANs The ability to execute the showcommand addresses the following
In a network environment users often need to view informationin other VSANs even though they do not have permission tomodify configurations in those VSANs
This behavior makes Cisco MDS 9000 Series switches consistentwith other Cisco products such as Cisco Nexus 7000 Seriesswitches that exhibit the same behavior for those roles (whenthey apply to the VLAN policy)
27
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Using a RSA Version 1 Key for SSH Following an UpgradeFor security reasons NX-OS Release 42(x) and higher does notsupport RSA version 1 keys As a result if you upgrade from anearlier version that did support RSA version 1 keys and you hadconfigured a RSA version 1 key for SSH then you will not be able tolog in through SSH following the upgrade
If you have a RSA version 1 key configured for SSH beforeupgrading to NX-OS Release 42(x) or higher follow these steps
1 Disable SSH
2 Create RSA version 2 DSA keys
3 Enable SSH
4 Delete any RSA version 1 keys on any remote SSH clients andreplace the version 1 keys with the new version 2 keys from theswitch
Proceed with the upgrade to NX-OS Release 42(x) or higher
If you upgrade before disabling SSH and creating RSA version 2 keysfollow these steps
1 Open a Telnet session and log in through the console
2 Issue the no feature ssh command to disable SSH
3 Issue the ssh key rsa 1024 command to create RSA version 2 keys
4 Issue the feature ssh command to enable SSH
Applying Zone Configurations to VSAN 1In the setup script you can configure system default values for thedefault-zone to be permit or deny and you can configure defaultvalues for the zone distribution method and for the zone mode
These default settings are applied when a new VSAN is createdHowever the settings will not take effect on VSAN 1 because it existsprior to running the setup script Therefore when you need thosesettings for VSAN 1 you must explicitly issue the followingcommands
zone default-zone permit vsan 1 zoneset distribute full vsan 1 zone mode enhanced vsan 1
28 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
InterVSAN RoutingWhen using InterVSAN Routing (IVR) it is recommended to enableCisco Fabric Services (CFS) on all IVR-enabled switches Failure to doso may cause mismatched active zone sets if an error occurs duringzone set activation
RSPAN Traffic Not Supported on CTS Ports on 8-Gbps Switching ModulesAn inter-switch link (ISL) that is enabled for Cisco TrustSec (CTS)encryption must be brought up in non-CTS mode to support remoteSPAN (RSPAN) traffic on the following modules
DS-X9248-96K9 Cisco MDS 9000 48-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9224-96K9 Cisco MDS 9000 24-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9248-48K9 Cisco MDS 9000 444-Port Host-Optimized8-Gbps Fibre Channel Switching Module
If the ISL link is brought up with CTS enabled random packets dropsof both RSPAN traffic and normal traffic will occur on the receiverport switch
IO Accelerator Feature LimitationsIOA does not support the following NX-OS features
IVR flows
Devices with NPV and NPIV enabled
F port trunking
bull F port channeling
Support for FCIP Compression ModesIn Cisco NX-OS Release 42(1b) and higher FCIP compression mode 1and compression mode 3 are not supported on the Cisco MSM-184module and on the SSN-16 module
29
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Saving Copies of the Running Kickstart and System ImagesAfter you upgrade to MDS NX-OS Release 42(1b) or higher you arenot allowed to delete rename move or overwrite the kickstart andsystem images that are in the current system bootvar settings on anactive or standby MDS Supervisor-2 module on any Cisco MDS 9500Series switch This restriction does not apply to the integratedsupervisor module on the MDS 9200 and MDS 9100 series switches
Configuring Buffer Credits on a Generation 2 or Generation 3 ModuleWhen you configure port mode to auto or E on a Generation 2module one of the ports will not come up for the followingconfiguration
Port Mode auto or E for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E on a Generation 3module one or two of the ports will not come up for the followingconfiguration
Port Mode auto or E for the first half of the ports the second halfof the ports or for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E for all ports in the globalbuffer pool you need to reconfigure buffer credits on one or more ofthe ports The total number of buffer credits configured for all theports in the global buffer pool should be reduced by 64
Storage services module power budgetThe MDS 9509 does not have the power budget to run seven SSMcards EMC recommends a maximum of four SSMs in one 9509Customers wishing to use more than four SSMs in one chassis shouldrefer to the Cisco MDS 9000 documentation on the Ciscocom websiteto validate that there is enough power available for their desiredconfiguration
30 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Note Upgrading to the 3000 watt power supplies will alleviate thiscondition
iSCSI proxy initiator in Celerra HighRoad environmentsEMC supports the iSCSI proxy initiator feature in Celerrareg
HighRoadreg environments In proxy initiator mode one Fibre Channelinitiator is used for all iSCSI clients who access the switch via thesame iSCSI interface (iscsi33 for example)
The initiators will use the PWWN assigned to the iSCSI interface TheiSCSI interface to which an iSCSI client will logon to is configured inthe client and must be permitted by the virtual target configured forthat initiator
The current session environment supported on the MDS is
300 sessions per port 1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no InitialR2T=yes
Refer to the specific initiator support documentation on how to setthe parameters The implementation will not perform properly ifthese bits are not set
Refer to the MDS documentation for more information regarding theconfiguration of the iSCSI proxy initiator at the following Ciscowebsite
httpwwwciscocomenUSproducts
HPUX N_port IDThe N_port ID port value of 255 (0xFF) has special meaning forHP-UX A N_port ID (FC_ID) can not be returned from a switch thatcontains this value for the N_port ID (FC_ID) port value for a HP-UXinitiator or HP-UX target port Port ID value of 255 (0xFF) cannot be
31
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
configured for HP-UX initiator port and HP-UX target ports whenconfiguring MDS FC_IDs The port_ID value is the third byte of theFC_ID
Interoperability limitationsRefer to the EMC Support Matrix (ESM) and the EMC Networked Storage Topology Guide for modes of operation and caveats
NASBThe NASB feature requires that the backup application load the tapedrive with a compatible tape cartridge prior to configuring NASB inthe backup VSAN
Reserved VSAN Range and Isolated VSAN Range GuidelinesOn an NPV switch with a trunking configuration on any interface or ona regular switch where the feature fport_channel_trunk command hasbeen issued to enable the F PortChannel feature follow theseconfiguration guidelines for reserved VSANs and the isolated VSAN
bull If trunk mode is on for any of the interfaces or NP PortChannelis up the reserved VSANs are 3040 to 4078 and they are notavailable for user configuration
bull The Exchange Virtual Fabric Protocol (EVFP) isolated VSAN is4079 and it is not available for user configuration
bull VSAN 4079 will be impacted by an upgrade to NX-OS Release42(3) depending on whether or not VSAN 4079 was createdprior to the upgrade See theldquoUpgrading Effect on VSAN 4079rdquoon page 17
The following VSAN IDs are assigned in the Fibre Channel Framingand Signaling (FC-FS) interface standard
VF_ID Value Value Description
00h Do not use as a Virtual FabricIdentifier
001h EFFh Available as a Virtual FabricIdentifier
F00h FEEh Reserved
32 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Symmetrix VMax limitationsAt the time of this writing the following features are not supportedfor use with the Symmetrix VMax
FCIP Write Acceleration
The NX-OS IOA functionality is only supported with the Q2 SREnginuity release 5874229182 or higher
For the most up to date status please refer to the current revision ofthese Release Notes on httpPowerlinkemccom and the EMCSupport Matrix available through E-Lab Interoperability Navigator (ELN) athttpelabnavigatorEMCcom
Storage Applications on the MSM-184The MDS 9000 184-Port Multiservice Module (MSM-184) does notsupport multiple concurrent storage applications Only oneapplication can run on the MSM-184 at a time
Downgrading with fport-channel-trunk enabledIf you are running MDS NX-OS Release 42(x) or higher with thefport-channel-trunk feature enabled and you downgrade to anyNX-OS 41(1x) release the installer performs a nondisruptivedowngrade even though the fport-channel-trunk feature is notsupported in NX-OS 41(1x) releases
As a result the switch is in an inconsistent state and the ports maynot function properly
FEFh Control VF-ID (see FibreChannel Link Services (FC-LS)and Fibre Channel SwitchFabric Generation 4 (FC-SW-4)standards)
FF0h FFEh Vendor specific
FFFh Do not use as a Virtual FabricIdentifier
FEFh = 4079
33
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
If you are in this state a workaround is to reboot the switch followingthe upgrade
LDAP AuthenticationThere is currently a limitation in the LDAP server configuration CLIthat prevents the use of an OU with spaces in the name Normallythese OU names could be surrounded by quotation marks howeverquotation marks are not supported by the ldap-server command
MDS-9148 limitationsThe Cisco MDS 9148 Multilayer Fabric Switch does not support thefollowing NX-OS features
Medium and Long range 4GB Agilent
IVR
Remote Span
Translative loop support
FCC - no generation quench reaction only
FC-Redirect
In addition the following features have these limits
VSANS - 31 maximum
SPAN - 1 session maximum
Technical notesThe following sections provide further information on technicalnotes
EMC Email Home for Cisco MDS switchesInstallation and Trouble shooting instructions can be found in thedocumentation located at the EMC Customer Service Internalwebsite
httpwwwcsisusemccomcsweb2esnesnhomehtmConnectrix20MDS20900020Family
34 EMC Connectrix MDS 9000 NX-OS Release Notes
Technical notes
Customers requiring installation of this solution should contact theirEMC Customer Engineer to assist with the installation and providethe documentation
Supported iSCSI sessionsThe current iSCSI session environment supported on the MDS is
300 sessions per port
1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no
InitialR2T=yes
Upgrading Cisco SAN-OSThere are several methods available for upgrading SAN-OS SoftwareEMC personnel are strongly recommended that all upgrades be doneby the Automated One-Step Upgrade using the install all
command EMC personnel should refer to the Connectrix MDS 9000Family Software Image Upgrade Instructions for a complete list ofprerequisites and instructions for performing the upgrade Thisdocument along with tftp software is available on the GlobalServices website at httpwwwcsisusEMCcom under ApplicationDownload Area ESN Product Information Connectrix MDS 9000Family
The Software Upgrade Wizard is an option for upgrades While theinstall all is the preferred method the Software Install Wizard canalso be used
Supported configuration parametersFor the most up-to-date information refer to the EMC Support Matrixavailable through E-Lab Interoperability Navigator athttpelabnavigatoremccom for the latest information onsupported configurations
35
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
Supported zoning parametersRefer to the EMC Networked Storage Topology Guide for the mostup-to-date information on supported zoning parameters
At the time these notes were published the following parameterswere supported
20 VSANs 5 Hops 2000 Unique members per physical infrastructure 1000 Zonesets per physical infrastructure 2000 Zones per physical infrastructure 1 FCIP tunnel
Supported IVR parameters IVR zone members 1000 IVR zones 1000 IVR zone sets 32 VSANS 20 IVR enabled switches 64
An RPQ can be submitted for any configurations that exceed thislimit
Managing zone changes in multiswitch fabricsZoning changes may be made through Fabric Manager or CLI Whenaccessing Fabric Manager or CLI the user does so from the point ofview of one switch That is Fabric Manager and CLI are accessed byentering the IP address of one switch in the fabric
When zoning changes are made the applicable VSAN and zone setdata is propagated to the rest of the switches in the fabric via the ISLs
When zoning changes are made to a VSAN the zone set data ispropagated to the rest of the switches in the fabric via the ISLs Bydefault only the active zone set information is relayed to all switchesin the VSAN If the user accesses the Fabric Manager and CLI fromanother switch in the fabric the new VSAN and zone set informationwill not be viewable To view the active and inactive zone set on theother switches in the fabric the user must log in to the CLI and issuea command from the EXEC prompt
36 EMC Connectrix MDS 9000 NX-OS Release Notes
Documentation
Example The following is an example of copying VSAN 1 through 20 zoningdata
CiscoMDS_name zone copy active full vsan 1-20
CiscoMDS_name conf t
Enter configuration commands one per line End with CNTL Z
CiscoMDS_name(config) zoneset distribute full vsan 1-20
CiscoMDS_name(config)
Note This command needs to be issued on all switches in the fabric one timeonly
This is a nondisruptive command After issuing the commands theuser will now see the active and inactive zone sets for the specifiedVSANs on any switch that is chosen from which to manage the fabric
After a zoning change is made save the running configuration to thestartup configuration
DocumentationSend documentation comments to mdsfeedback-doccom
Product DocumentationAs of NX-OS Release 42(1a) software configuration information isavailable in new feature-specific configuration guides for thefollowing information
System management
Interfaces
Fabric
Quality of service
Security
IP services
High availability and redundancy
37
Software media organization and files
EMC Connectrix MDS 9000 NX-OS Release Notes
The information in these new guides previously existed in the CiscoMDS 9000 Family CLI Configuration Guide That configuration guideremains available on Ciscocom and should be used for all softwarereleases prior to NX-OS Release 42(1a) Configuration guidesaddress the features introduced in or available in a particular releaseSelect and view the configuration guide that pertains to the softwareinstalled in your switch
In addition Fabric Manager information has been removed from theMDS NX-OS Release Notes (this document) and placed intostandalone Fabric Manager Release Notes that support both CiscoMDS 9000 Family switches and Cisco Nexus 5000 Series switchesThe Cisco Fabric Manager Release Notes are available onhttpPowerlinkemccom and from the following website
httpwwwciscocomenUSpartnerproductsps10495prod_release_notes_listhtml
Technical supportThese release notes complement a Cisco documentation set EachCisco document refers to where to get help However for any itemssupplied by EMC see ldquoTroubleshooting and getting helprdquo onpage 38
Software media organization and filesFor information on related software environment and systemrequirements refer to the EMC Support Matrix on EMC Powerlink at
httpPowerlinkEMCcom
InstallationFor hardware installation information refer to the Cisco MDS HWInstallation Guides available at Ciscocom
For EMC-specific installation information refer to ldquoEnvironment andsystem requirementsrdquo on page 5 in this document
38 EMC Connectrix MDS 9000 NX-OS Release Notes
Troubleshooting and getting help
Troubleshooting and getting helpEMC support product and licensing information can be obtained asfollows
Product information mdash For documentation release notes softwareupdates or for information about EMC products licensing andservice go to the EMC Powerlink website (registration required) at
httpPowerlinkEMCcom
Technical support mdash For technical support go to EMC CustomerService on Powerlink To open a service request through Powerlinkyou must have a valid support agreement Please contact your EMCsales representative for details about obtaining a valid supportagreement or to answer any questions about your account
Copyright copy 2011 EMC Corporation All rights reserved
EMC believes the information in this publication is accurate as of its publication date The information issubject to change without notice
THE INFORMATION IN THIS PUBLICATION IS PROVIDED ldquoAS ISrdquo EMC CORPORATION MAKES NOREPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION INTHIS PUBLICATION AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OFMERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Use copying and distribution of any EMC software described in this publication requires an applicablesoftware license
For the most up-to-date regulatory document for your product line go to the Technical Documentation andAdvisories section on EMC Powerlink
For the most up-to-date listing of EMC product names see EMC Corporation Trademarks on EMCcom
All other trademarks used herein are the property of their respective owners
9
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Table 3 lists the MDS hardware modules supported by Cisco MDSNX-OS 5x
MDS 9216A No
MDS 9216 No
MDS 9148 Yes
MDS 9134 Yes
MDS 9124 Yes
MDS 9140 No
MDS 9120 No
Table 2 Cisco MDS NX-OS 5x Chassis Support Matrix
Switch NX-OS 5x Support
Table 3 Module Support Matrix for Cisco MDS NX-OS 5x (page 1 of 2)
Module DescriptionMDS 9500Series MDS 9222i
DS-X9530-SF2A-K9 MDS 9500 Supervisor-2A Module Yes NA
DS-X9530-SF2-K9 MDS 9500 Supervisor-2 Module Yes NA
DS-X9530-SF1-K9 MDS 9500 Supervisor-1 Module No NA
DS-X9224-96K9 24-port 8-Gbps Fibre Channel Switching Module Yesa No
DS-X9248-96K9 48-port 8-Gbps Fibre Channel Switching Module Yesa No
DS-X9248-48K9 444-port Host Optimized 8-Gbps Fibre ChannelSwitching Module
Yes Yes
DS-X9316-SSNK9 16-Port Storage Services Node (SSN-16) Yes Yes
DS-X9304-18K9 184-Port Multiprotocol Services Module(MSM-184)
Yes Yes
DS-X9112 12-port 4-Gbps Fibre Channel Switching Module Yes Yes
DS-X9124 24-port 4-Gbps Fibre Channel Switching Module Yes Yes
DS-X9148 48-port 4-Gbps Fibre Channel Switching Module Yes Yes
DS-X9704 4-port 10-Gbps Fibre Channel Switching Module Yes Yes
10 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Migrating from Supervisor-1 Modules to Supervisor-2 ModulesAs of Cisco MDS SAN-OS Release 30(1) the Cisco MDS 9509 and9506 Directors support both Supervisor-1 and Supervisor-2 modulesSupervisor-1 and Supervisor-2 modules cannot be installed in thesame switch except during migration Both the active and standbysupervisor modules must be of the same type either Supervisor-1 orSupervisor-2 modules For Cisco MDS 9513 Directors bothsupervisor modules must be Supervisor-2 modules
CAUTION
Migrating your supervisor modules is a disruptive operation
Note Migrating from Supervisor-2 modules to Supervisor-1 modules is not supported
To migrate from a Supervisor-1 module to a Supervisor-2 module refer to the step-by-step instructions in the Cisco MDS 9000 NX-OS Release 41(x) and SAN-OS 3(x) Software Upgrade and Downgrade Guide
DS-X9302-14K9 142-port Multiprotocol Services (MPS-142)Module
No No
DS-X9016 16-port 1- 2-Gbps Fibre Channel SwitchingModule
No No
DS-X9032 32-port 1- 2-Gbps Fibre Channel SwitchingModule
No No
DS-X9032-SSM 32-port Storage Services Module (SSM) No No
DS-X9308-SMIP 8-port 1- 2-Gbps IP Switching Module No No
DS-X9304-SMIP 4-port 1- 2-Gbps IP Switching Module No No
a Requires DS-13SLT-FAB2 in the MDS 9513
Table 3 Module Support Matrix for Cisco MDS NX-OS 5x (page 2 of 2)
Module DescriptionMDS 9500Series MDS 9222i
11
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Software Download ProcessUse the software download procedure to upgrade to a later versionor downgrade to an earlier version of an operating system Thissection describes the software download process for the Cisco MDSNX-OS software and includes the following topics
ldquoDetermining the Software Versionrdquo on page 11
ldquoDownloading Softwarerdquo on page 11
ldquoSelecting the Correct Software Image for an MDS 9100 SeriesSwitchrdquo on page 12
ldquoSelecting the Correct Software Image for an MDS 9200 SeriesSwitchrdquo on page 13
ldquoSelecting the Correct Software Image for an MDS 9500 SeriesSwitchrdquo on page 13
Determining the Software VersionTo determine the version of Cisco MDS NX-OS or SAN-OS softwarecurrently running on a Cisco MDS 9000 Family switch using the CLIlog in to the switch and enter the show version EXEC command
To determine the version of Cisco MDS NX-OS or SAN-OS softwarecurrently running on a Cisco MDS 9000 Family switch using theFabric Manager view the Switches tab in the Information pane locatethe switch using the IP address logical name or WWN and check itsversion in the Release column
Note EMC strongly recommends that you use the latest qualified softwarerelease for all MDS 9000 Family products Refer to the EMC Support Matrixavailable through E-Lab Interoperability Navigator (ELN) athttpelabnavigatorEMCcom for the latest information on qualifiedfirmware revisions
Downloading SoftwareThe Cisco MDS NX-OS software is designed for mission-critical highavailability environments To realize the benefits of nondisruptiveupgrades on the Cisco MDS 9500 Directors we highly recommendthat you install dual supervisor modules
12 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Before performing upgrades submit all requested changes to theEMC Global Services CCA change control process so that anypotential operating environment impacts can be analyzedbeforehand
EMC personnel should also refer to the Connectrix MDS 9000 FamilySoftware Image Upgrade Instructions for a complete list of prerequisitesThis document is available on the Global Services websitehttpwwwcsisusEMCcom under Application Download AreaESN Product Information Connectrix MDS 9000 Family EMCpersonnel can download the Software Images from the GlobalServices website httpwwwcsisusEMCcom under ApplicationDownload Area ESN Product Information Connectrix MDS 9000Family
See the following sections in this release note for details on how youcan nondisruptively upgrade your Cisco MDS 9000 switch Issuingthe install all command from the CLI or using Fabric Manager toperform the downgrade enables the compatibility check The checkindicates if the upgrade can happen nondisruptively or disruptivelydepending on the current configuration of your switch and thereason
Compatibility check is doneModule bootable Impact Install-type Reason------ -------- -------------- ------------ ------
1 yes non-disruptive rolling2 yes disruptive rolling Hitless upgrade is not supported3 yes disruptive rolling Hitless upgrade is not supported4 yes non-disruptive rolling5 yes non-disruptive reset6 yes non-disruptive reset
Selecting the Correct Software Image for an MDS 9100 Series SwitchThe system and kickstart image that you use for an MDS 9100 seriesswitch depends on which switch you use as shown in Table 4
Table 4 Software Images for MDS 9100 Series Switches
Cisco MDS 9100 Series Switch Type Naming Convention
9124 and 9134 Filename begins with m9100-s2ek9
9148 Filename begins with m9100-s3ek9
13
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Selecting the Correct Software Image for an MDS 9200 Series SwitchThe system and kickstart image that you use for an MDS 9200 seriesswitch depends on which switch you use as shown in Table 5
Selecting the Correct Software Image for an MDS 9500 Series SwitchThe system and kickstart image that you use for an MDS 9500 Seriesswitch depends on whether the switch is based on a Supervisor-1module or a Supervisor-2 module as shown in Table 6
Use the show module command to display the type of supervisormodule in the switch The following is sample output from the showmodule command on a Supervisor 2 module
Table 5 Software Images for MDS 9200 Series Switches
Cisco MDS 9200 Series Switch Type Naming Convention
9222i Filename begins with m9200-s2ek9
Table 6 Software Images for Supervisor Type
Cisco MDS 9500 Series Switch Type Supervisor Module Type Naming Convention
9513 9509 and 9506 Supervisor-2 module Filename begins with m9500-sf2ek9
14 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
switch show moduleMod Ports Module-Type Model Status--- ----- -------------------------------- ------------------ ------------7 0 SupervisorFabric-2 DS-X9530-SF2-K9 active 8 0 SupervisorFabric-2 DS-X9530-SF2-K9 ha-standby
Upgrading Your Cisco MDS NX-OS Software ImageThis section lists the guidelines recommended for upgrading yourCisco MDS NX-OS software image and includes the following topics
ldquoGeneral Upgrading Guidelinesrdquo on page 14
ldquoDowngrading Your Cisco MDS SAN-OS Software Imagerdquo onpage 18
Note Before you begin the upgrade process review the list of chassis andmodules that NX-OS Release 50(4b) supports See the ldquoMDS 9000 Chassisand Module Support in Cisco MDS NX-OS 5xrdquo on page 8
Note For detailed instructions for performing a software upgrade usingCisco Fabric Manager see the Cisco Fabric Manager Release Notes forRelease 50(4b) which is available from the following websitehttpPowerlinkEMCcom
General Upgrading Guidelines
Note To upgrade to NX-OS Release 50(4b) you must be running NX-OSRelease 4x If you are running SAN-OS Release 32(3a) or earlier firstupgrade to SAN-OS Release 33(x) then NX-OS Release 4x and thenupgrade to NX-OS Release 50(4b)
Use the following guidelines when upgrading to Cisco MDS NX-OSRelease 5x
Install and configure dual supervisor modules
Issue the show install all impact upgrade-image CLI command todetermine if your upgrade will be nondisruptive
15
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Be aware of the impact of an upgrade on VSAN 4079 if you areupgrading from SAN-OS Release 3x to NX-OS 50(4b) See theldquoUpgrading Effect on VSAN 4079rdquo on page 17
Follow the recommended guidelines for upgrading a Cisco MDS9124 or MDS 9134 Switch as described in ldquoUpgrading a CiscoMDS 9124 or MDS 9134 switchrdquo on page 18
Take note of the affect of upgrades on MDS 9500 series switchesthat have active IOA flows as described in ldquoMDS 9500 seriesupgrades with active IOA flowsrdquo on page 18
Be aware that some features impact whether an upgrade isdisruptive or nondisruptive
bull Fibre Channel Ports Traffic on Fibre Channel ports can benondisruptively upgraded See Table 7 on page 16 for thenondisruptive upgrade path for all NX-OS and SAN-OSreleases
bull Storage Services Intelligent storage services traffic such asSANTap NASB and FC write acceleration is disruptedduring an upgrade Fibre Channel traffic is not
bull Gigabit Ethernet Ports Traffic on Gigabit Ethernet ports isdisrupted during an upgrade or downgrade This includes theGigabit Ethernet ports on the MSM-184 module and the MDS9222i switch Those nodes that are members of VSANs traversingan FCIP ISL are impacted and a fabric reconfiguration occursiSCSI initiators connected to the Gigabit Ethernet ports loseconnectivity to iSCSI targets while the upgrade is in progress
bull FICON If you have FICON enabled the upgrade path isdifferent See Table 6 on page 13
Use Table 7 to determine your nondisruptive upgrade path to Cisco MDSNX-OS Release 50(4b) find the image release number you are currentlyusing in the Current column of the table and use the path recommended
16 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Note The software upgrade information in Table 7 applies only to FibreChannel switching traffic Upgrading system software disrupts IP traffic andSSM intelligent services traffic
MDS NX-OS Release 50(4b) is not a FICON-qualified release
Table 7 Nondisruptive Upgrade Path to Cisco MDS NX-OS Release 50(4b)
Current Nondisruptive Upgrade Path
NX-OS 50(4) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 50(1a) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(7b) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(5) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(3) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(1b) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(1a) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 41(3a) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 41(1b) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
SAN-OS 33(4a) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
NX-OS 33(4) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 33(3) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 33(2) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 33(1c) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 32(3a) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 32(2c) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 32(1a) Upgrade to SAN-OS Release then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 31(3a) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 31(2) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
17
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Use Table 8 to determine your FICON nondisruptive upgrade path toCisco MDS NX-OS Release 42(7b) Find the image release numberyou are currently using in the Current Release with FICON Enabledcolumn of the table and use the path recommended
Note For more information on the FICON qualified NX-OS releases refer tothe EMC Support Matrix available through E-Lab Interoperability Navigator(ELN) at httpelabnavigatorEMCcom
Upgrading Effect on VSAN 4079If you are upgrading to NX-OS Release 50(4b) and you have notcreated VSAN 4079 the NX-OS software will automatically createVSAN 4079 and reserve it for EVFP use If VSAN 4079 is reserved forEVFP use the switchport trunk allowed vsan command will filterout VSAN 4079 from the allowed list as shown in the followingexample
switch(config-if) switchport trunk allowed vsan1-40801-40784080switch(config-if)
If you have created VSAN 4079 the upgrade to NX-OS Release50(4b) will have no affect on VSAN 4079
If you downgrade to a release of NX-OS lower than 41(x) afterNX-OS Release 50(4b) creates VSAN 4079 and reserves it for EVFPuse the VSAN will no longer be reserved
Table 8 FICON Nondisruptive Upgrade Path to NX-OS Release 42(7b)
Current Release withFICON Enabled Upgrade Path
NX-OS 42(1b) You can nondisruptively upgrade directly to NX-OS Release 42(7b)
NX-OS 41(1c) You can nondisruptively upgrade directly to NX-OS Release 42(7b)
SAN-OS 33(1c) You can nondisruptively upgrade directly to NX-OS Release 42(7b)
18 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Upgrading a Cisco MDS 9124 or MDS 9134 switchIf you are upgrading from Cisco MDS SAN-OS Release 31(1) to CiscoNX-OS Release 4x before upgrading to NX-OS Release 50(4b) on aCisco MDS 9124 or MDS 9134 switch follow these guidelines
During the upgrade configuration is not allowed and the fabric isexpected to be stable
The Fabric Shortest Path First (FSPF) timers must be configured tothe default value of 20 seconds otherwise the nondisruptiveupgrade is blocked to ensure that the maximum down toim forthe control plane can be 80 seconds
If there are any CFS commits in the fabric the nondisruptiveupgrade will fail
If there is a zone server merge in progress in the fabric thenondisruptive upgrde will fail
If a service terminates the nondisruptive upgrade the showinstall all failure-reason command can display the reason thatthe nondisruptive upgrade cannot proceed
If there is not enough memory in the system to load the newimages the upgrade will be made disruptive due to insufficientresources and the user will be notified in the compativility table
MDS 9500 series upgrades with active IOA flowsWhen upgading an MDS 9500 series switch that has active IOA flowsthose flows may be interrupted during the supervisor moduleswitchover To workaround this issue you have to enablespanning-tree portfast on the interface on the catalyst connected tothe management interface of the activestandby supervisor for theinterface to come up fast without causing the cluster to lose quorum
Downgrading Your Cisco MDS SAN-OS Software ImageThis section lists the guidelines recommended for downgrading yourCisco MDS SAN-OS software image and includes the followingtopics
ldquoGeneral downgrading guidelinesrdquo on page 19
19
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
General downgrading guidelinesUse the following guidelines to nondisruptively downgrade yourCisco MDS NX-OS Release 50(4b)
Install and configure dual supervisor modules
Issue the system no acl-adjacency-sharing execute command todisable acl adjacency usage on Generation 2 and Generation 1modules If this command fails reduce the number of zones IVRzones TE ports or a combination of these in the system and issuethe command again
Disable all features not supported by the downgrade release Usethe show incompatibility system downgrade-image command todetermine what you need to disable
bull If you are running in interoperability mode two such featuresare the Reliable Commit Service and Full Zone DatabaseDistribution They can be disabled by running thesecommand in config term mode
no zone rcs enableno zoneset capability distribute full
Use the show install all impact downgrade-image command todetermine if your downgrade will be nondisruptive
Be aware that some features impact whether a downgrade isdisruptive or nondisruptive
bull Fibre Channel Ports Traffic on Fibre Channel ports can benondisruptively downgraded See Table 9 on page 20 for thenondisruptive downgrade path for all SAN-OS releases
bull Storage Services Intelligent storage services traffic such asSANTap NASB and FC write acceleration is disruptedduring a downgrade Fibre Channel traffic is not
bull Gigabit Ethernet Ports Traffic on Gigabit Ethernet ports isdisrupted during a downgrade This includes the GigabitEthernet ports on the MSM-184 module and the MDS 9222iswitch Those nodes that are members of VSANs traversing anFCIP ISL are impacted and a fabric reconfiguration occursiSCSI initiators connected to the Gigabit Ethernet ports loseconnectivity to iSCSI targets while the downgrade is inprogress
20 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
bull FICON If you have FICON enabled the downgrade path isdifferent See Table 10 on page 21
Note A downgrade from NX-OS Release 4x to SAN-OS Release 33(1c) is notsupported on MDS switches when FC-Redirect based applications such asData Mobility Manager or Storage Media Encryption are configured in thefabric if either of the following conditions are satisfied
1 A target for which FC-Redirect is configured is connected locally and thereare Generation 1 modules with ISLs configured in the switch
2 A host for which FC-redirect is configured is connected locally ona Generation 1 module
If these conditions exist remove the application configuration forthese targets and hosts before proceeding with the downgrade
Use Table 9 on page 20 to determine the nondisruptive downgradepath from Cisco NX-OS Release 50(4b) Find the NX-OS or SAN-OSimage you want to downgrade to in the To SAN-OSNX-OS Releasecolumn of the table and use the path recommended
Note The software downgrade information in Table 10 on page 21 appliesonly to Fibre Channel switching traffic Downgrading system softwaredisrupts IP and SSM intelligent services traffic
Table 9 Nondisruptive Downgrade Path from NX-OS Release 50(4b) (page 1 of2)
To SAN-OS NX-OSRelease Nondisruptive Downgrade Path
NX-OS 50(4) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 50(1a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(7b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(5) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(3) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(1b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(1a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 41(3a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
21
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Use Table 10 to determine your nondisruptive downgrade path if youhave FICON enabled from Cisco NX-OS Release 42(7b) Find the imagerelease number you are currently using in the Current Release withFICON Enabled column of the table and use the path recommended
NX-OS 41(1b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
SAN-OS 33(5a) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33())
SAN-OS 33(5) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(4a) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
NX-OS 33(4) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(3) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
NX-OS 33(2) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(1c) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 32(3a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 32(x)
SAN-OS 32(2c) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 32(x)
SAN-OS 32(1a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
SAN-OS 31(3a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
SAN-OS 31(2) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
Table 9 Nondisruptive Downgrade Path from NX-OS Release 50(4b) (page 2 of2)
To SAN-OS NX-OSRelease Nondisruptive Downgrade Path
Table 10 FICON Downgrade Path from NX-OS Release 42(7b)
To SAN-OSNX-OS Release withFICON Enabled Downgrade Path
NX-OS 42(1b) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
NX-OS 41(1c) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
SAN-OS 33(1c) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
22 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Best practicesLog messages are not saved across system reboots or power outagesTherefore EMC recommends that customers configure a SyslogServer in order to redirect and capture all log messages on a remoteserver For more information please refer to the Cisco MDS 9000Family Configuration Guide available at
httpwwwciscocomenUSproductsps5989products_support_series_homehtml
Maximum ports per chassisTable 11 shows the maximum ports per chassis
a V2 indicates a 9506 or 9509 with Generation-2 Supervisors The presence of anygeneration one module in a switch will limit the maximum port count to 252This includes the 16-port 32-port 14+2 IPS4 and IPS8 cards
Known problems and limitationsFor a list of problems with this release please refer to the CiscoRelease notes located at
httpwwwciscocomenUSproductsps5989prod_release_notes_listhtml
Limitations and restrictionsThe following limitations and restrictions apply to all switches in theCisco MDS 9000 Family unless a limitation for a specific switch isstated
ldquoStorage Media Encryption (SME) limitationsrdquo on page 24
Table 11 Maximum ports per chassis
Chassis Maximum number of ports
MDS 9506-V2 192a
MDS 9509-V2 336
MDS 9513 528
23
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
ldquoSME configuration limitsrdquo on page 24
ldquoDeleting Cisco SME interfacesrdquo on page 25
ldquoCisco MDS 9124 and 9134 Multilayer fabric switchesrdquo on page 25
ldquoN-Port virtualization configuration limitsrdquo on page 25
ldquoMaximum number of zones supported in Interop Mode 4rdquo onpage 25
ldquoIPv6rdquo on page 26
ldquoIP-ACL supportrdquo on page 26
ldquoUser Rolesrdquo on page 26
ldquoUsing a RSA Version 1 Key for SSH Following an Upgraderdquo onpage 27
ldquoApplying Zone Configurations to VSAN 1rdquo on page 27
ldquoInterVSAN Routingrdquo on page 28
ldquoRSPAN Traffic Not Supported on CTS Ports on 8-GbpsSwitching Modulesrdquo on page 28
ldquoIO Accelerator Feature Limitationsrdquo on page 28
ldquoSupport for FCIP Compression Modesrdquo on page 28
ldquoSaving Copies of the Running Kickstart and System Imagesrdquo onpage 29
ldquoConfiguring Buffer Credits on a Generation 2 or Generation 3Modulerdquo on page 29
ldquoStorage services module power budgetrdquo on page 29
ldquoiSCSI proxy initiator in Celerra HighRoad environmentsrdquo onpage 30
ldquoHPUX N_port IDrdquo on page 30
ldquoInteroperability limitationsrdquo on page 31
ldquoNASBrdquo on page 31
ldquoReserved VSAN Range and Isolated VSAN Range Guidelinesrdquoon page 31
ldquoSymmetrix VMax limitationsrdquo on page 32
ldquoStorage Applications on the MSM-184rdquo on page 32
ldquoDowngrading with fport-channel-trunk enabledrdquo on page 32
ldquoLDAP Authenticationrdquo on page 33
24 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
ldquoMDS-9148 limitationsrdquo on page 33
Storage Media Encryption (SME) limitationsAn SME node can only belong to one cluster Adding the node tomore than one cluster will cause problems
Currently there is no prevention or warning in place when an attemptis made to add a node to multiple clusters
SME configuration limitsTable 12 lists the SME configuration limits for this release
Table 12 SME configuration limits
Configuration Limits
Number of switches in the fabric 10
Number of clusters per switch 1
Switches in a cluster 4
Fabrics in a cluster 2
Modules in a switch 11
Cisco MSM-184 modules in a cluster 32
Initiator-Target-LUNs (ITLs) 1024
LUNs behind a target 32
Host and target ports in a cluster 128
Number of hosts per target 128
Tape backup groups per cluster 2
Volume groups in a tape backup group 4
Cisco Key Management Center ( of keys) 32K
Targets per switch that can be FC-redirected 32
25
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Deleting Cisco SME interfacesA Cisco SME interface can be deleted from the cluster only after theinterface is administratively shut-down and all related tasksassociated with the interface shut-down are complete
Cisco MDS 9124 and 9134 Multilayer fabric switchesThe Cisco MDS 9124 and 9134 Multilayer fabric switches do notsupport the following Cisco MDS SAN-OS features
IVR Remote Span Translative loop support FCCmdash no generation quench reaction only
In addition the following features have these limits
VSANs mdash 16 maximum SPAN mdash 1 session maximum
N-Port virtualization configuration limitsThe NPV features have maximum configuration limits Table 13shows the verified and maximum limits for the NPV switchesrunning NX-OS Release 5x
Maximum number of zones supported in Interop Mode 4In interop mode 4 the maximum number of zones that is supportedin an active zone set is 2047 due to limitations in the connectedvendor switch When IVR is used in interop mode 4 the maximumnumber of zones supported including IVR zones in the active zoneset is 2047 The limit for the maximum number of IVR zones perVSAN is 250 zones (two members per zone)
Table 13 NPV features limitations
Feature Verified limits Maximum limits
FLOGIs or F Disc per NPV port group 114 114
NPV switches per NPV core switch 105 105
FLOGIs per line card on NPV core switch 400 400
26 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
IPv6The management port on Cisco MDS switches supports oneuser-configured IPv6 address but does not supportauto-configuration of an IPv6 address
IP-ACL supportDo not apply IP-ACLs to only one member of a PortChannel groupApply IP-ACLs to the entire channel group
If IP-ACLs are already configured in a Gigabit Ethernet interface youcannot add this interface to a Ethernet PortChannel group
Refer to the Cisco MDS 9000 Family Configuration Guide
User RolesIn SAN-OS Release 33(x) and earlier when a user belongs to a rolewhich has a VSAN policy set to Deny and the role allows access to aspecific set of VSANs (for example 1 through 10) the user isrestricted from performing the configuration clear execute anddebug commands which had a VSAN parameter outside thisspecified set Beginning with NX-OS Release 41(1b) these users arestill prevented from performing configuration clear execute anddebug commands as before however they are allowed to performshow commands for all VSANs The ability to execute the showcommand addresses the following
In a network environment users often need to view informationin other VSANs even though they do not have permission tomodify configurations in those VSANs
This behavior makes Cisco MDS 9000 Series switches consistentwith other Cisco products such as Cisco Nexus 7000 Seriesswitches that exhibit the same behavior for those roles (whenthey apply to the VLAN policy)
27
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Using a RSA Version 1 Key for SSH Following an UpgradeFor security reasons NX-OS Release 42(x) and higher does notsupport RSA version 1 keys As a result if you upgrade from anearlier version that did support RSA version 1 keys and you hadconfigured a RSA version 1 key for SSH then you will not be able tolog in through SSH following the upgrade
If you have a RSA version 1 key configured for SSH beforeupgrading to NX-OS Release 42(x) or higher follow these steps
1 Disable SSH
2 Create RSA version 2 DSA keys
3 Enable SSH
4 Delete any RSA version 1 keys on any remote SSH clients andreplace the version 1 keys with the new version 2 keys from theswitch
Proceed with the upgrade to NX-OS Release 42(x) or higher
If you upgrade before disabling SSH and creating RSA version 2 keysfollow these steps
1 Open a Telnet session and log in through the console
2 Issue the no feature ssh command to disable SSH
3 Issue the ssh key rsa 1024 command to create RSA version 2 keys
4 Issue the feature ssh command to enable SSH
Applying Zone Configurations to VSAN 1In the setup script you can configure system default values for thedefault-zone to be permit or deny and you can configure defaultvalues for the zone distribution method and for the zone mode
These default settings are applied when a new VSAN is createdHowever the settings will not take effect on VSAN 1 because it existsprior to running the setup script Therefore when you need thosesettings for VSAN 1 you must explicitly issue the followingcommands
zone default-zone permit vsan 1 zoneset distribute full vsan 1 zone mode enhanced vsan 1
28 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
InterVSAN RoutingWhen using InterVSAN Routing (IVR) it is recommended to enableCisco Fabric Services (CFS) on all IVR-enabled switches Failure to doso may cause mismatched active zone sets if an error occurs duringzone set activation
RSPAN Traffic Not Supported on CTS Ports on 8-Gbps Switching ModulesAn inter-switch link (ISL) that is enabled for Cisco TrustSec (CTS)encryption must be brought up in non-CTS mode to support remoteSPAN (RSPAN) traffic on the following modules
DS-X9248-96K9 Cisco MDS 9000 48-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9224-96K9 Cisco MDS 9000 24-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9248-48K9 Cisco MDS 9000 444-Port Host-Optimized8-Gbps Fibre Channel Switching Module
If the ISL link is brought up with CTS enabled random packets dropsof both RSPAN traffic and normal traffic will occur on the receiverport switch
IO Accelerator Feature LimitationsIOA does not support the following NX-OS features
IVR flows
Devices with NPV and NPIV enabled
F port trunking
bull F port channeling
Support for FCIP Compression ModesIn Cisco NX-OS Release 42(1b) and higher FCIP compression mode 1and compression mode 3 are not supported on the Cisco MSM-184module and on the SSN-16 module
29
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Saving Copies of the Running Kickstart and System ImagesAfter you upgrade to MDS NX-OS Release 42(1b) or higher you arenot allowed to delete rename move or overwrite the kickstart andsystem images that are in the current system bootvar settings on anactive or standby MDS Supervisor-2 module on any Cisco MDS 9500Series switch This restriction does not apply to the integratedsupervisor module on the MDS 9200 and MDS 9100 series switches
Configuring Buffer Credits on a Generation 2 or Generation 3 ModuleWhen you configure port mode to auto or E on a Generation 2module one of the ports will not come up for the followingconfiguration
Port Mode auto or E for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E on a Generation 3module one or two of the ports will not come up for the followingconfiguration
Port Mode auto or E for the first half of the ports the second halfof the ports or for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E for all ports in the globalbuffer pool you need to reconfigure buffer credits on one or more ofthe ports The total number of buffer credits configured for all theports in the global buffer pool should be reduced by 64
Storage services module power budgetThe MDS 9509 does not have the power budget to run seven SSMcards EMC recommends a maximum of four SSMs in one 9509Customers wishing to use more than four SSMs in one chassis shouldrefer to the Cisco MDS 9000 documentation on the Ciscocom websiteto validate that there is enough power available for their desiredconfiguration
30 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Note Upgrading to the 3000 watt power supplies will alleviate thiscondition
iSCSI proxy initiator in Celerra HighRoad environmentsEMC supports the iSCSI proxy initiator feature in Celerrareg
HighRoadreg environments In proxy initiator mode one Fibre Channelinitiator is used for all iSCSI clients who access the switch via thesame iSCSI interface (iscsi33 for example)
The initiators will use the PWWN assigned to the iSCSI interface TheiSCSI interface to which an iSCSI client will logon to is configured inthe client and must be permitted by the virtual target configured forthat initiator
The current session environment supported on the MDS is
300 sessions per port 1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no InitialR2T=yes
Refer to the specific initiator support documentation on how to setthe parameters The implementation will not perform properly ifthese bits are not set
Refer to the MDS documentation for more information regarding theconfiguration of the iSCSI proxy initiator at the following Ciscowebsite
httpwwwciscocomenUSproducts
HPUX N_port IDThe N_port ID port value of 255 (0xFF) has special meaning forHP-UX A N_port ID (FC_ID) can not be returned from a switch thatcontains this value for the N_port ID (FC_ID) port value for a HP-UXinitiator or HP-UX target port Port ID value of 255 (0xFF) cannot be
31
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
configured for HP-UX initiator port and HP-UX target ports whenconfiguring MDS FC_IDs The port_ID value is the third byte of theFC_ID
Interoperability limitationsRefer to the EMC Support Matrix (ESM) and the EMC Networked Storage Topology Guide for modes of operation and caveats
NASBThe NASB feature requires that the backup application load the tapedrive with a compatible tape cartridge prior to configuring NASB inthe backup VSAN
Reserved VSAN Range and Isolated VSAN Range GuidelinesOn an NPV switch with a trunking configuration on any interface or ona regular switch where the feature fport_channel_trunk command hasbeen issued to enable the F PortChannel feature follow theseconfiguration guidelines for reserved VSANs and the isolated VSAN
bull If trunk mode is on for any of the interfaces or NP PortChannelis up the reserved VSANs are 3040 to 4078 and they are notavailable for user configuration
bull The Exchange Virtual Fabric Protocol (EVFP) isolated VSAN is4079 and it is not available for user configuration
bull VSAN 4079 will be impacted by an upgrade to NX-OS Release42(3) depending on whether or not VSAN 4079 was createdprior to the upgrade See theldquoUpgrading Effect on VSAN 4079rdquoon page 17
The following VSAN IDs are assigned in the Fibre Channel Framingand Signaling (FC-FS) interface standard
VF_ID Value Value Description
00h Do not use as a Virtual FabricIdentifier
001h EFFh Available as a Virtual FabricIdentifier
F00h FEEh Reserved
32 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Symmetrix VMax limitationsAt the time of this writing the following features are not supportedfor use with the Symmetrix VMax
FCIP Write Acceleration
The NX-OS IOA functionality is only supported with the Q2 SREnginuity release 5874229182 or higher
For the most up to date status please refer to the current revision ofthese Release Notes on httpPowerlinkemccom and the EMCSupport Matrix available through E-Lab Interoperability Navigator (ELN) athttpelabnavigatorEMCcom
Storage Applications on the MSM-184The MDS 9000 184-Port Multiservice Module (MSM-184) does notsupport multiple concurrent storage applications Only oneapplication can run on the MSM-184 at a time
Downgrading with fport-channel-trunk enabledIf you are running MDS NX-OS Release 42(x) or higher with thefport-channel-trunk feature enabled and you downgrade to anyNX-OS 41(1x) release the installer performs a nondisruptivedowngrade even though the fport-channel-trunk feature is notsupported in NX-OS 41(1x) releases
As a result the switch is in an inconsistent state and the ports maynot function properly
FEFh Control VF-ID (see FibreChannel Link Services (FC-LS)and Fibre Channel SwitchFabric Generation 4 (FC-SW-4)standards)
FF0h FFEh Vendor specific
FFFh Do not use as a Virtual FabricIdentifier
FEFh = 4079
33
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
If you are in this state a workaround is to reboot the switch followingthe upgrade
LDAP AuthenticationThere is currently a limitation in the LDAP server configuration CLIthat prevents the use of an OU with spaces in the name Normallythese OU names could be surrounded by quotation marks howeverquotation marks are not supported by the ldap-server command
MDS-9148 limitationsThe Cisco MDS 9148 Multilayer Fabric Switch does not support thefollowing NX-OS features
Medium and Long range 4GB Agilent
IVR
Remote Span
Translative loop support
FCC - no generation quench reaction only
FC-Redirect
In addition the following features have these limits
VSANS - 31 maximum
SPAN - 1 session maximum
Technical notesThe following sections provide further information on technicalnotes
EMC Email Home for Cisco MDS switchesInstallation and Trouble shooting instructions can be found in thedocumentation located at the EMC Customer Service Internalwebsite
httpwwwcsisusemccomcsweb2esnesnhomehtmConnectrix20MDS20900020Family
34 EMC Connectrix MDS 9000 NX-OS Release Notes
Technical notes
Customers requiring installation of this solution should contact theirEMC Customer Engineer to assist with the installation and providethe documentation
Supported iSCSI sessionsThe current iSCSI session environment supported on the MDS is
300 sessions per port
1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no
InitialR2T=yes
Upgrading Cisco SAN-OSThere are several methods available for upgrading SAN-OS SoftwareEMC personnel are strongly recommended that all upgrades be doneby the Automated One-Step Upgrade using the install all
command EMC personnel should refer to the Connectrix MDS 9000Family Software Image Upgrade Instructions for a complete list ofprerequisites and instructions for performing the upgrade Thisdocument along with tftp software is available on the GlobalServices website at httpwwwcsisusEMCcom under ApplicationDownload Area ESN Product Information Connectrix MDS 9000Family
The Software Upgrade Wizard is an option for upgrades While theinstall all is the preferred method the Software Install Wizard canalso be used
Supported configuration parametersFor the most up-to-date information refer to the EMC Support Matrixavailable through E-Lab Interoperability Navigator athttpelabnavigatoremccom for the latest information onsupported configurations
35
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
Supported zoning parametersRefer to the EMC Networked Storage Topology Guide for the mostup-to-date information on supported zoning parameters
At the time these notes were published the following parameterswere supported
20 VSANs 5 Hops 2000 Unique members per physical infrastructure 1000 Zonesets per physical infrastructure 2000 Zones per physical infrastructure 1 FCIP tunnel
Supported IVR parameters IVR zone members 1000 IVR zones 1000 IVR zone sets 32 VSANS 20 IVR enabled switches 64
An RPQ can be submitted for any configurations that exceed thislimit
Managing zone changes in multiswitch fabricsZoning changes may be made through Fabric Manager or CLI Whenaccessing Fabric Manager or CLI the user does so from the point ofview of one switch That is Fabric Manager and CLI are accessed byentering the IP address of one switch in the fabric
When zoning changes are made the applicable VSAN and zone setdata is propagated to the rest of the switches in the fabric via the ISLs
When zoning changes are made to a VSAN the zone set data ispropagated to the rest of the switches in the fabric via the ISLs Bydefault only the active zone set information is relayed to all switchesin the VSAN If the user accesses the Fabric Manager and CLI fromanother switch in the fabric the new VSAN and zone set informationwill not be viewable To view the active and inactive zone set on theother switches in the fabric the user must log in to the CLI and issuea command from the EXEC prompt
36 EMC Connectrix MDS 9000 NX-OS Release Notes
Documentation
Example The following is an example of copying VSAN 1 through 20 zoningdata
CiscoMDS_name zone copy active full vsan 1-20
CiscoMDS_name conf t
Enter configuration commands one per line End with CNTL Z
CiscoMDS_name(config) zoneset distribute full vsan 1-20
CiscoMDS_name(config)
Note This command needs to be issued on all switches in the fabric one timeonly
This is a nondisruptive command After issuing the commands theuser will now see the active and inactive zone sets for the specifiedVSANs on any switch that is chosen from which to manage the fabric
After a zoning change is made save the running configuration to thestartup configuration
DocumentationSend documentation comments to mdsfeedback-doccom
Product DocumentationAs of NX-OS Release 42(1a) software configuration information isavailable in new feature-specific configuration guides for thefollowing information
System management
Interfaces
Fabric
Quality of service
Security
IP services
High availability and redundancy
37
Software media organization and files
EMC Connectrix MDS 9000 NX-OS Release Notes
The information in these new guides previously existed in the CiscoMDS 9000 Family CLI Configuration Guide That configuration guideremains available on Ciscocom and should be used for all softwarereleases prior to NX-OS Release 42(1a) Configuration guidesaddress the features introduced in or available in a particular releaseSelect and view the configuration guide that pertains to the softwareinstalled in your switch
In addition Fabric Manager information has been removed from theMDS NX-OS Release Notes (this document) and placed intostandalone Fabric Manager Release Notes that support both CiscoMDS 9000 Family switches and Cisco Nexus 5000 Series switchesThe Cisco Fabric Manager Release Notes are available onhttpPowerlinkemccom and from the following website
httpwwwciscocomenUSpartnerproductsps10495prod_release_notes_listhtml
Technical supportThese release notes complement a Cisco documentation set EachCisco document refers to where to get help However for any itemssupplied by EMC see ldquoTroubleshooting and getting helprdquo onpage 38
Software media organization and filesFor information on related software environment and systemrequirements refer to the EMC Support Matrix on EMC Powerlink at
httpPowerlinkEMCcom
InstallationFor hardware installation information refer to the Cisco MDS HWInstallation Guides available at Ciscocom
For EMC-specific installation information refer to ldquoEnvironment andsystem requirementsrdquo on page 5 in this document
38 EMC Connectrix MDS 9000 NX-OS Release Notes
Troubleshooting and getting help
Troubleshooting and getting helpEMC support product and licensing information can be obtained asfollows
Product information mdash For documentation release notes softwareupdates or for information about EMC products licensing andservice go to the EMC Powerlink website (registration required) at
httpPowerlinkEMCcom
Technical support mdash For technical support go to EMC CustomerService on Powerlink To open a service request through Powerlinkyou must have a valid support agreement Please contact your EMCsales representative for details about obtaining a valid supportagreement or to answer any questions about your account
Copyright copy 2011 EMC Corporation All rights reserved
EMC believes the information in this publication is accurate as of its publication date The information issubject to change without notice
THE INFORMATION IN THIS PUBLICATION IS PROVIDED ldquoAS ISrdquo EMC CORPORATION MAKES NOREPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION INTHIS PUBLICATION AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OFMERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Use copying and distribution of any EMC software described in this publication requires an applicablesoftware license
For the most up-to-date regulatory document for your product line go to the Technical Documentation andAdvisories section on EMC Powerlink
For the most up-to-date listing of EMC product names see EMC Corporation Trademarks on EMCcom
All other trademarks used herein are the property of their respective owners
10 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Migrating from Supervisor-1 Modules to Supervisor-2 ModulesAs of Cisco MDS SAN-OS Release 30(1) the Cisco MDS 9509 and9506 Directors support both Supervisor-1 and Supervisor-2 modulesSupervisor-1 and Supervisor-2 modules cannot be installed in thesame switch except during migration Both the active and standbysupervisor modules must be of the same type either Supervisor-1 orSupervisor-2 modules For Cisco MDS 9513 Directors bothsupervisor modules must be Supervisor-2 modules
CAUTION
Migrating your supervisor modules is a disruptive operation
Note Migrating from Supervisor-2 modules to Supervisor-1 modules is not supported
To migrate from a Supervisor-1 module to a Supervisor-2 module refer to the step-by-step instructions in the Cisco MDS 9000 NX-OS Release 41(x) and SAN-OS 3(x) Software Upgrade and Downgrade Guide
DS-X9302-14K9 142-port Multiprotocol Services (MPS-142)Module
No No
DS-X9016 16-port 1- 2-Gbps Fibre Channel SwitchingModule
No No
DS-X9032 32-port 1- 2-Gbps Fibre Channel SwitchingModule
No No
DS-X9032-SSM 32-port Storage Services Module (SSM) No No
DS-X9308-SMIP 8-port 1- 2-Gbps IP Switching Module No No
DS-X9304-SMIP 4-port 1- 2-Gbps IP Switching Module No No
a Requires DS-13SLT-FAB2 in the MDS 9513
Table 3 Module Support Matrix for Cisco MDS NX-OS 5x (page 2 of 2)
Module DescriptionMDS 9500Series MDS 9222i
11
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Software Download ProcessUse the software download procedure to upgrade to a later versionor downgrade to an earlier version of an operating system Thissection describes the software download process for the Cisco MDSNX-OS software and includes the following topics
ldquoDetermining the Software Versionrdquo on page 11
ldquoDownloading Softwarerdquo on page 11
ldquoSelecting the Correct Software Image for an MDS 9100 SeriesSwitchrdquo on page 12
ldquoSelecting the Correct Software Image for an MDS 9200 SeriesSwitchrdquo on page 13
ldquoSelecting the Correct Software Image for an MDS 9500 SeriesSwitchrdquo on page 13
Determining the Software VersionTo determine the version of Cisco MDS NX-OS or SAN-OS softwarecurrently running on a Cisco MDS 9000 Family switch using the CLIlog in to the switch and enter the show version EXEC command
To determine the version of Cisco MDS NX-OS or SAN-OS softwarecurrently running on a Cisco MDS 9000 Family switch using theFabric Manager view the Switches tab in the Information pane locatethe switch using the IP address logical name or WWN and check itsversion in the Release column
Note EMC strongly recommends that you use the latest qualified softwarerelease for all MDS 9000 Family products Refer to the EMC Support Matrixavailable through E-Lab Interoperability Navigator (ELN) athttpelabnavigatorEMCcom for the latest information on qualifiedfirmware revisions
Downloading SoftwareThe Cisco MDS NX-OS software is designed for mission-critical highavailability environments To realize the benefits of nondisruptiveupgrades on the Cisco MDS 9500 Directors we highly recommendthat you install dual supervisor modules
12 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Before performing upgrades submit all requested changes to theEMC Global Services CCA change control process so that anypotential operating environment impacts can be analyzedbeforehand
EMC personnel should also refer to the Connectrix MDS 9000 FamilySoftware Image Upgrade Instructions for a complete list of prerequisitesThis document is available on the Global Services websitehttpwwwcsisusEMCcom under Application Download AreaESN Product Information Connectrix MDS 9000 Family EMCpersonnel can download the Software Images from the GlobalServices website httpwwwcsisusEMCcom under ApplicationDownload Area ESN Product Information Connectrix MDS 9000Family
See the following sections in this release note for details on how youcan nondisruptively upgrade your Cisco MDS 9000 switch Issuingthe install all command from the CLI or using Fabric Manager toperform the downgrade enables the compatibility check The checkindicates if the upgrade can happen nondisruptively or disruptivelydepending on the current configuration of your switch and thereason
Compatibility check is doneModule bootable Impact Install-type Reason------ -------- -------------- ------------ ------
1 yes non-disruptive rolling2 yes disruptive rolling Hitless upgrade is not supported3 yes disruptive rolling Hitless upgrade is not supported4 yes non-disruptive rolling5 yes non-disruptive reset6 yes non-disruptive reset
Selecting the Correct Software Image for an MDS 9100 Series SwitchThe system and kickstart image that you use for an MDS 9100 seriesswitch depends on which switch you use as shown in Table 4
Table 4 Software Images for MDS 9100 Series Switches
Cisco MDS 9100 Series Switch Type Naming Convention
9124 and 9134 Filename begins with m9100-s2ek9
9148 Filename begins with m9100-s3ek9
13
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Selecting the Correct Software Image for an MDS 9200 Series SwitchThe system and kickstart image that you use for an MDS 9200 seriesswitch depends on which switch you use as shown in Table 5
Selecting the Correct Software Image for an MDS 9500 Series SwitchThe system and kickstart image that you use for an MDS 9500 Seriesswitch depends on whether the switch is based on a Supervisor-1module or a Supervisor-2 module as shown in Table 6
Use the show module command to display the type of supervisormodule in the switch The following is sample output from the showmodule command on a Supervisor 2 module
Table 5 Software Images for MDS 9200 Series Switches
Cisco MDS 9200 Series Switch Type Naming Convention
9222i Filename begins with m9200-s2ek9
Table 6 Software Images for Supervisor Type
Cisco MDS 9500 Series Switch Type Supervisor Module Type Naming Convention
9513 9509 and 9506 Supervisor-2 module Filename begins with m9500-sf2ek9
14 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
switch show moduleMod Ports Module-Type Model Status--- ----- -------------------------------- ------------------ ------------7 0 SupervisorFabric-2 DS-X9530-SF2-K9 active 8 0 SupervisorFabric-2 DS-X9530-SF2-K9 ha-standby
Upgrading Your Cisco MDS NX-OS Software ImageThis section lists the guidelines recommended for upgrading yourCisco MDS NX-OS software image and includes the following topics
ldquoGeneral Upgrading Guidelinesrdquo on page 14
ldquoDowngrading Your Cisco MDS SAN-OS Software Imagerdquo onpage 18
Note Before you begin the upgrade process review the list of chassis andmodules that NX-OS Release 50(4b) supports See the ldquoMDS 9000 Chassisand Module Support in Cisco MDS NX-OS 5xrdquo on page 8
Note For detailed instructions for performing a software upgrade usingCisco Fabric Manager see the Cisco Fabric Manager Release Notes forRelease 50(4b) which is available from the following websitehttpPowerlinkEMCcom
General Upgrading Guidelines
Note To upgrade to NX-OS Release 50(4b) you must be running NX-OSRelease 4x If you are running SAN-OS Release 32(3a) or earlier firstupgrade to SAN-OS Release 33(x) then NX-OS Release 4x and thenupgrade to NX-OS Release 50(4b)
Use the following guidelines when upgrading to Cisco MDS NX-OSRelease 5x
Install and configure dual supervisor modules
Issue the show install all impact upgrade-image CLI command todetermine if your upgrade will be nondisruptive
15
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Be aware of the impact of an upgrade on VSAN 4079 if you areupgrading from SAN-OS Release 3x to NX-OS 50(4b) See theldquoUpgrading Effect on VSAN 4079rdquo on page 17
Follow the recommended guidelines for upgrading a Cisco MDS9124 or MDS 9134 Switch as described in ldquoUpgrading a CiscoMDS 9124 or MDS 9134 switchrdquo on page 18
Take note of the affect of upgrades on MDS 9500 series switchesthat have active IOA flows as described in ldquoMDS 9500 seriesupgrades with active IOA flowsrdquo on page 18
Be aware that some features impact whether an upgrade isdisruptive or nondisruptive
bull Fibre Channel Ports Traffic on Fibre Channel ports can benondisruptively upgraded See Table 7 on page 16 for thenondisruptive upgrade path for all NX-OS and SAN-OSreleases
bull Storage Services Intelligent storage services traffic such asSANTap NASB and FC write acceleration is disruptedduring an upgrade Fibre Channel traffic is not
bull Gigabit Ethernet Ports Traffic on Gigabit Ethernet ports isdisrupted during an upgrade or downgrade This includes theGigabit Ethernet ports on the MSM-184 module and the MDS9222i switch Those nodes that are members of VSANs traversingan FCIP ISL are impacted and a fabric reconfiguration occursiSCSI initiators connected to the Gigabit Ethernet ports loseconnectivity to iSCSI targets while the upgrade is in progress
bull FICON If you have FICON enabled the upgrade path isdifferent See Table 6 on page 13
Use Table 7 to determine your nondisruptive upgrade path to Cisco MDSNX-OS Release 50(4b) find the image release number you are currentlyusing in the Current column of the table and use the path recommended
16 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Note The software upgrade information in Table 7 applies only to FibreChannel switching traffic Upgrading system software disrupts IP traffic andSSM intelligent services traffic
MDS NX-OS Release 50(4b) is not a FICON-qualified release
Table 7 Nondisruptive Upgrade Path to Cisco MDS NX-OS Release 50(4b)
Current Nondisruptive Upgrade Path
NX-OS 50(4) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 50(1a) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(7b) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(5) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(3) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(1b) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(1a) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 41(3a) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 41(1b) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
SAN-OS 33(4a) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
NX-OS 33(4) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 33(3) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 33(2) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 33(1c) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 32(3a) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 32(2c) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 32(1a) Upgrade to SAN-OS Release then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 31(3a) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 31(2) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
17
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Use Table 8 to determine your FICON nondisruptive upgrade path toCisco MDS NX-OS Release 42(7b) Find the image release numberyou are currently using in the Current Release with FICON Enabledcolumn of the table and use the path recommended
Note For more information on the FICON qualified NX-OS releases refer tothe EMC Support Matrix available through E-Lab Interoperability Navigator(ELN) at httpelabnavigatorEMCcom
Upgrading Effect on VSAN 4079If you are upgrading to NX-OS Release 50(4b) and you have notcreated VSAN 4079 the NX-OS software will automatically createVSAN 4079 and reserve it for EVFP use If VSAN 4079 is reserved forEVFP use the switchport trunk allowed vsan command will filterout VSAN 4079 from the allowed list as shown in the followingexample
switch(config-if) switchport trunk allowed vsan1-40801-40784080switch(config-if)
If you have created VSAN 4079 the upgrade to NX-OS Release50(4b) will have no affect on VSAN 4079
If you downgrade to a release of NX-OS lower than 41(x) afterNX-OS Release 50(4b) creates VSAN 4079 and reserves it for EVFPuse the VSAN will no longer be reserved
Table 8 FICON Nondisruptive Upgrade Path to NX-OS Release 42(7b)
Current Release withFICON Enabled Upgrade Path
NX-OS 42(1b) You can nondisruptively upgrade directly to NX-OS Release 42(7b)
NX-OS 41(1c) You can nondisruptively upgrade directly to NX-OS Release 42(7b)
SAN-OS 33(1c) You can nondisruptively upgrade directly to NX-OS Release 42(7b)
18 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Upgrading a Cisco MDS 9124 or MDS 9134 switchIf you are upgrading from Cisco MDS SAN-OS Release 31(1) to CiscoNX-OS Release 4x before upgrading to NX-OS Release 50(4b) on aCisco MDS 9124 or MDS 9134 switch follow these guidelines
During the upgrade configuration is not allowed and the fabric isexpected to be stable
The Fabric Shortest Path First (FSPF) timers must be configured tothe default value of 20 seconds otherwise the nondisruptiveupgrade is blocked to ensure that the maximum down toim forthe control plane can be 80 seconds
If there are any CFS commits in the fabric the nondisruptiveupgrade will fail
If there is a zone server merge in progress in the fabric thenondisruptive upgrde will fail
If a service terminates the nondisruptive upgrade the showinstall all failure-reason command can display the reason thatthe nondisruptive upgrade cannot proceed
If there is not enough memory in the system to load the newimages the upgrade will be made disruptive due to insufficientresources and the user will be notified in the compativility table
MDS 9500 series upgrades with active IOA flowsWhen upgading an MDS 9500 series switch that has active IOA flowsthose flows may be interrupted during the supervisor moduleswitchover To workaround this issue you have to enablespanning-tree portfast on the interface on the catalyst connected tothe management interface of the activestandby supervisor for theinterface to come up fast without causing the cluster to lose quorum
Downgrading Your Cisco MDS SAN-OS Software ImageThis section lists the guidelines recommended for downgrading yourCisco MDS SAN-OS software image and includes the followingtopics
ldquoGeneral downgrading guidelinesrdquo on page 19
19
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
General downgrading guidelinesUse the following guidelines to nondisruptively downgrade yourCisco MDS NX-OS Release 50(4b)
Install and configure dual supervisor modules
Issue the system no acl-adjacency-sharing execute command todisable acl adjacency usage on Generation 2 and Generation 1modules If this command fails reduce the number of zones IVRzones TE ports or a combination of these in the system and issuethe command again
Disable all features not supported by the downgrade release Usethe show incompatibility system downgrade-image command todetermine what you need to disable
bull If you are running in interoperability mode two such featuresare the Reliable Commit Service and Full Zone DatabaseDistribution They can be disabled by running thesecommand in config term mode
no zone rcs enableno zoneset capability distribute full
Use the show install all impact downgrade-image command todetermine if your downgrade will be nondisruptive
Be aware that some features impact whether a downgrade isdisruptive or nondisruptive
bull Fibre Channel Ports Traffic on Fibre Channel ports can benondisruptively downgraded See Table 9 on page 20 for thenondisruptive downgrade path for all SAN-OS releases
bull Storage Services Intelligent storage services traffic such asSANTap NASB and FC write acceleration is disruptedduring a downgrade Fibre Channel traffic is not
bull Gigabit Ethernet Ports Traffic on Gigabit Ethernet ports isdisrupted during a downgrade This includes the GigabitEthernet ports on the MSM-184 module and the MDS 9222iswitch Those nodes that are members of VSANs traversing anFCIP ISL are impacted and a fabric reconfiguration occursiSCSI initiators connected to the Gigabit Ethernet ports loseconnectivity to iSCSI targets while the downgrade is inprogress
20 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
bull FICON If you have FICON enabled the downgrade path isdifferent See Table 10 on page 21
Note A downgrade from NX-OS Release 4x to SAN-OS Release 33(1c) is notsupported on MDS switches when FC-Redirect based applications such asData Mobility Manager or Storage Media Encryption are configured in thefabric if either of the following conditions are satisfied
1 A target for which FC-Redirect is configured is connected locally and thereare Generation 1 modules with ISLs configured in the switch
2 A host for which FC-redirect is configured is connected locally ona Generation 1 module
If these conditions exist remove the application configuration forthese targets and hosts before proceeding with the downgrade
Use Table 9 on page 20 to determine the nondisruptive downgradepath from Cisco NX-OS Release 50(4b) Find the NX-OS or SAN-OSimage you want to downgrade to in the To SAN-OSNX-OS Releasecolumn of the table and use the path recommended
Note The software downgrade information in Table 10 on page 21 appliesonly to Fibre Channel switching traffic Downgrading system softwaredisrupts IP and SSM intelligent services traffic
Table 9 Nondisruptive Downgrade Path from NX-OS Release 50(4b) (page 1 of2)
To SAN-OS NX-OSRelease Nondisruptive Downgrade Path
NX-OS 50(4) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 50(1a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(7b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(5) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(3) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(1b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(1a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 41(3a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
21
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Use Table 10 to determine your nondisruptive downgrade path if youhave FICON enabled from Cisco NX-OS Release 42(7b) Find the imagerelease number you are currently using in the Current Release withFICON Enabled column of the table and use the path recommended
NX-OS 41(1b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
SAN-OS 33(5a) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33())
SAN-OS 33(5) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(4a) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
NX-OS 33(4) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(3) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
NX-OS 33(2) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(1c) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 32(3a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 32(x)
SAN-OS 32(2c) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 32(x)
SAN-OS 32(1a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
SAN-OS 31(3a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
SAN-OS 31(2) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
Table 9 Nondisruptive Downgrade Path from NX-OS Release 50(4b) (page 2 of2)
To SAN-OS NX-OSRelease Nondisruptive Downgrade Path
Table 10 FICON Downgrade Path from NX-OS Release 42(7b)
To SAN-OSNX-OS Release withFICON Enabled Downgrade Path
NX-OS 42(1b) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
NX-OS 41(1c) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
SAN-OS 33(1c) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
22 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Best practicesLog messages are not saved across system reboots or power outagesTherefore EMC recommends that customers configure a SyslogServer in order to redirect and capture all log messages on a remoteserver For more information please refer to the Cisco MDS 9000Family Configuration Guide available at
httpwwwciscocomenUSproductsps5989products_support_series_homehtml
Maximum ports per chassisTable 11 shows the maximum ports per chassis
a V2 indicates a 9506 or 9509 with Generation-2 Supervisors The presence of anygeneration one module in a switch will limit the maximum port count to 252This includes the 16-port 32-port 14+2 IPS4 and IPS8 cards
Known problems and limitationsFor a list of problems with this release please refer to the CiscoRelease notes located at
httpwwwciscocomenUSproductsps5989prod_release_notes_listhtml
Limitations and restrictionsThe following limitations and restrictions apply to all switches in theCisco MDS 9000 Family unless a limitation for a specific switch isstated
ldquoStorage Media Encryption (SME) limitationsrdquo on page 24
Table 11 Maximum ports per chassis
Chassis Maximum number of ports
MDS 9506-V2 192a
MDS 9509-V2 336
MDS 9513 528
23
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
ldquoSME configuration limitsrdquo on page 24
ldquoDeleting Cisco SME interfacesrdquo on page 25
ldquoCisco MDS 9124 and 9134 Multilayer fabric switchesrdquo on page 25
ldquoN-Port virtualization configuration limitsrdquo on page 25
ldquoMaximum number of zones supported in Interop Mode 4rdquo onpage 25
ldquoIPv6rdquo on page 26
ldquoIP-ACL supportrdquo on page 26
ldquoUser Rolesrdquo on page 26
ldquoUsing a RSA Version 1 Key for SSH Following an Upgraderdquo onpage 27
ldquoApplying Zone Configurations to VSAN 1rdquo on page 27
ldquoInterVSAN Routingrdquo on page 28
ldquoRSPAN Traffic Not Supported on CTS Ports on 8-GbpsSwitching Modulesrdquo on page 28
ldquoIO Accelerator Feature Limitationsrdquo on page 28
ldquoSupport for FCIP Compression Modesrdquo on page 28
ldquoSaving Copies of the Running Kickstart and System Imagesrdquo onpage 29
ldquoConfiguring Buffer Credits on a Generation 2 or Generation 3Modulerdquo on page 29
ldquoStorage services module power budgetrdquo on page 29
ldquoiSCSI proxy initiator in Celerra HighRoad environmentsrdquo onpage 30
ldquoHPUX N_port IDrdquo on page 30
ldquoInteroperability limitationsrdquo on page 31
ldquoNASBrdquo on page 31
ldquoReserved VSAN Range and Isolated VSAN Range Guidelinesrdquoon page 31
ldquoSymmetrix VMax limitationsrdquo on page 32
ldquoStorage Applications on the MSM-184rdquo on page 32
ldquoDowngrading with fport-channel-trunk enabledrdquo on page 32
ldquoLDAP Authenticationrdquo on page 33
24 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
ldquoMDS-9148 limitationsrdquo on page 33
Storage Media Encryption (SME) limitationsAn SME node can only belong to one cluster Adding the node tomore than one cluster will cause problems
Currently there is no prevention or warning in place when an attemptis made to add a node to multiple clusters
SME configuration limitsTable 12 lists the SME configuration limits for this release
Table 12 SME configuration limits
Configuration Limits
Number of switches in the fabric 10
Number of clusters per switch 1
Switches in a cluster 4
Fabrics in a cluster 2
Modules in a switch 11
Cisco MSM-184 modules in a cluster 32
Initiator-Target-LUNs (ITLs) 1024
LUNs behind a target 32
Host and target ports in a cluster 128
Number of hosts per target 128
Tape backup groups per cluster 2
Volume groups in a tape backup group 4
Cisco Key Management Center ( of keys) 32K
Targets per switch that can be FC-redirected 32
25
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Deleting Cisco SME interfacesA Cisco SME interface can be deleted from the cluster only after theinterface is administratively shut-down and all related tasksassociated with the interface shut-down are complete
Cisco MDS 9124 and 9134 Multilayer fabric switchesThe Cisco MDS 9124 and 9134 Multilayer fabric switches do notsupport the following Cisco MDS SAN-OS features
IVR Remote Span Translative loop support FCCmdash no generation quench reaction only
In addition the following features have these limits
VSANs mdash 16 maximum SPAN mdash 1 session maximum
N-Port virtualization configuration limitsThe NPV features have maximum configuration limits Table 13shows the verified and maximum limits for the NPV switchesrunning NX-OS Release 5x
Maximum number of zones supported in Interop Mode 4In interop mode 4 the maximum number of zones that is supportedin an active zone set is 2047 due to limitations in the connectedvendor switch When IVR is used in interop mode 4 the maximumnumber of zones supported including IVR zones in the active zoneset is 2047 The limit for the maximum number of IVR zones perVSAN is 250 zones (two members per zone)
Table 13 NPV features limitations
Feature Verified limits Maximum limits
FLOGIs or F Disc per NPV port group 114 114
NPV switches per NPV core switch 105 105
FLOGIs per line card on NPV core switch 400 400
26 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
IPv6The management port on Cisco MDS switches supports oneuser-configured IPv6 address but does not supportauto-configuration of an IPv6 address
IP-ACL supportDo not apply IP-ACLs to only one member of a PortChannel groupApply IP-ACLs to the entire channel group
If IP-ACLs are already configured in a Gigabit Ethernet interface youcannot add this interface to a Ethernet PortChannel group
Refer to the Cisco MDS 9000 Family Configuration Guide
User RolesIn SAN-OS Release 33(x) and earlier when a user belongs to a rolewhich has a VSAN policy set to Deny and the role allows access to aspecific set of VSANs (for example 1 through 10) the user isrestricted from performing the configuration clear execute anddebug commands which had a VSAN parameter outside thisspecified set Beginning with NX-OS Release 41(1b) these users arestill prevented from performing configuration clear execute anddebug commands as before however they are allowed to performshow commands for all VSANs The ability to execute the showcommand addresses the following
In a network environment users often need to view informationin other VSANs even though they do not have permission tomodify configurations in those VSANs
This behavior makes Cisco MDS 9000 Series switches consistentwith other Cisco products such as Cisco Nexus 7000 Seriesswitches that exhibit the same behavior for those roles (whenthey apply to the VLAN policy)
27
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Using a RSA Version 1 Key for SSH Following an UpgradeFor security reasons NX-OS Release 42(x) and higher does notsupport RSA version 1 keys As a result if you upgrade from anearlier version that did support RSA version 1 keys and you hadconfigured a RSA version 1 key for SSH then you will not be able tolog in through SSH following the upgrade
If you have a RSA version 1 key configured for SSH beforeupgrading to NX-OS Release 42(x) or higher follow these steps
1 Disable SSH
2 Create RSA version 2 DSA keys
3 Enable SSH
4 Delete any RSA version 1 keys on any remote SSH clients andreplace the version 1 keys with the new version 2 keys from theswitch
Proceed with the upgrade to NX-OS Release 42(x) or higher
If you upgrade before disabling SSH and creating RSA version 2 keysfollow these steps
1 Open a Telnet session and log in through the console
2 Issue the no feature ssh command to disable SSH
3 Issue the ssh key rsa 1024 command to create RSA version 2 keys
4 Issue the feature ssh command to enable SSH
Applying Zone Configurations to VSAN 1In the setup script you can configure system default values for thedefault-zone to be permit or deny and you can configure defaultvalues for the zone distribution method and for the zone mode
These default settings are applied when a new VSAN is createdHowever the settings will not take effect on VSAN 1 because it existsprior to running the setup script Therefore when you need thosesettings for VSAN 1 you must explicitly issue the followingcommands
zone default-zone permit vsan 1 zoneset distribute full vsan 1 zone mode enhanced vsan 1
28 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
InterVSAN RoutingWhen using InterVSAN Routing (IVR) it is recommended to enableCisco Fabric Services (CFS) on all IVR-enabled switches Failure to doso may cause mismatched active zone sets if an error occurs duringzone set activation
RSPAN Traffic Not Supported on CTS Ports on 8-Gbps Switching ModulesAn inter-switch link (ISL) that is enabled for Cisco TrustSec (CTS)encryption must be brought up in non-CTS mode to support remoteSPAN (RSPAN) traffic on the following modules
DS-X9248-96K9 Cisco MDS 9000 48-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9224-96K9 Cisco MDS 9000 24-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9248-48K9 Cisco MDS 9000 444-Port Host-Optimized8-Gbps Fibre Channel Switching Module
If the ISL link is brought up with CTS enabled random packets dropsof both RSPAN traffic and normal traffic will occur on the receiverport switch
IO Accelerator Feature LimitationsIOA does not support the following NX-OS features
IVR flows
Devices with NPV and NPIV enabled
F port trunking
bull F port channeling
Support for FCIP Compression ModesIn Cisco NX-OS Release 42(1b) and higher FCIP compression mode 1and compression mode 3 are not supported on the Cisco MSM-184module and on the SSN-16 module
29
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Saving Copies of the Running Kickstart and System ImagesAfter you upgrade to MDS NX-OS Release 42(1b) or higher you arenot allowed to delete rename move or overwrite the kickstart andsystem images that are in the current system bootvar settings on anactive or standby MDS Supervisor-2 module on any Cisco MDS 9500Series switch This restriction does not apply to the integratedsupervisor module on the MDS 9200 and MDS 9100 series switches
Configuring Buffer Credits on a Generation 2 or Generation 3 ModuleWhen you configure port mode to auto or E on a Generation 2module one of the ports will not come up for the followingconfiguration
Port Mode auto or E for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E on a Generation 3module one or two of the ports will not come up for the followingconfiguration
Port Mode auto or E for the first half of the ports the second halfof the ports or for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E for all ports in the globalbuffer pool you need to reconfigure buffer credits on one or more ofthe ports The total number of buffer credits configured for all theports in the global buffer pool should be reduced by 64
Storage services module power budgetThe MDS 9509 does not have the power budget to run seven SSMcards EMC recommends a maximum of four SSMs in one 9509Customers wishing to use more than four SSMs in one chassis shouldrefer to the Cisco MDS 9000 documentation on the Ciscocom websiteto validate that there is enough power available for their desiredconfiguration
30 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Note Upgrading to the 3000 watt power supplies will alleviate thiscondition
iSCSI proxy initiator in Celerra HighRoad environmentsEMC supports the iSCSI proxy initiator feature in Celerrareg
HighRoadreg environments In proxy initiator mode one Fibre Channelinitiator is used for all iSCSI clients who access the switch via thesame iSCSI interface (iscsi33 for example)
The initiators will use the PWWN assigned to the iSCSI interface TheiSCSI interface to which an iSCSI client will logon to is configured inthe client and must be permitted by the virtual target configured forthat initiator
The current session environment supported on the MDS is
300 sessions per port 1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no InitialR2T=yes
Refer to the specific initiator support documentation on how to setthe parameters The implementation will not perform properly ifthese bits are not set
Refer to the MDS documentation for more information regarding theconfiguration of the iSCSI proxy initiator at the following Ciscowebsite
httpwwwciscocomenUSproducts
HPUX N_port IDThe N_port ID port value of 255 (0xFF) has special meaning forHP-UX A N_port ID (FC_ID) can not be returned from a switch thatcontains this value for the N_port ID (FC_ID) port value for a HP-UXinitiator or HP-UX target port Port ID value of 255 (0xFF) cannot be
31
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
configured for HP-UX initiator port and HP-UX target ports whenconfiguring MDS FC_IDs The port_ID value is the third byte of theFC_ID
Interoperability limitationsRefer to the EMC Support Matrix (ESM) and the EMC Networked Storage Topology Guide for modes of operation and caveats
NASBThe NASB feature requires that the backup application load the tapedrive with a compatible tape cartridge prior to configuring NASB inthe backup VSAN
Reserved VSAN Range and Isolated VSAN Range GuidelinesOn an NPV switch with a trunking configuration on any interface or ona regular switch where the feature fport_channel_trunk command hasbeen issued to enable the F PortChannel feature follow theseconfiguration guidelines for reserved VSANs and the isolated VSAN
bull If trunk mode is on for any of the interfaces or NP PortChannelis up the reserved VSANs are 3040 to 4078 and they are notavailable for user configuration
bull The Exchange Virtual Fabric Protocol (EVFP) isolated VSAN is4079 and it is not available for user configuration
bull VSAN 4079 will be impacted by an upgrade to NX-OS Release42(3) depending on whether or not VSAN 4079 was createdprior to the upgrade See theldquoUpgrading Effect on VSAN 4079rdquoon page 17
The following VSAN IDs are assigned in the Fibre Channel Framingand Signaling (FC-FS) interface standard
VF_ID Value Value Description
00h Do not use as a Virtual FabricIdentifier
001h EFFh Available as a Virtual FabricIdentifier
F00h FEEh Reserved
32 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Symmetrix VMax limitationsAt the time of this writing the following features are not supportedfor use with the Symmetrix VMax
FCIP Write Acceleration
The NX-OS IOA functionality is only supported with the Q2 SREnginuity release 5874229182 or higher
For the most up to date status please refer to the current revision ofthese Release Notes on httpPowerlinkemccom and the EMCSupport Matrix available through E-Lab Interoperability Navigator (ELN) athttpelabnavigatorEMCcom
Storage Applications on the MSM-184The MDS 9000 184-Port Multiservice Module (MSM-184) does notsupport multiple concurrent storage applications Only oneapplication can run on the MSM-184 at a time
Downgrading with fport-channel-trunk enabledIf you are running MDS NX-OS Release 42(x) or higher with thefport-channel-trunk feature enabled and you downgrade to anyNX-OS 41(1x) release the installer performs a nondisruptivedowngrade even though the fport-channel-trunk feature is notsupported in NX-OS 41(1x) releases
As a result the switch is in an inconsistent state and the ports maynot function properly
FEFh Control VF-ID (see FibreChannel Link Services (FC-LS)and Fibre Channel SwitchFabric Generation 4 (FC-SW-4)standards)
FF0h FFEh Vendor specific
FFFh Do not use as a Virtual FabricIdentifier
FEFh = 4079
33
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
If you are in this state a workaround is to reboot the switch followingthe upgrade
LDAP AuthenticationThere is currently a limitation in the LDAP server configuration CLIthat prevents the use of an OU with spaces in the name Normallythese OU names could be surrounded by quotation marks howeverquotation marks are not supported by the ldap-server command
MDS-9148 limitationsThe Cisco MDS 9148 Multilayer Fabric Switch does not support thefollowing NX-OS features
Medium and Long range 4GB Agilent
IVR
Remote Span
Translative loop support
FCC - no generation quench reaction only
FC-Redirect
In addition the following features have these limits
VSANS - 31 maximum
SPAN - 1 session maximum
Technical notesThe following sections provide further information on technicalnotes
EMC Email Home for Cisco MDS switchesInstallation and Trouble shooting instructions can be found in thedocumentation located at the EMC Customer Service Internalwebsite
httpwwwcsisusemccomcsweb2esnesnhomehtmConnectrix20MDS20900020Family
34 EMC Connectrix MDS 9000 NX-OS Release Notes
Technical notes
Customers requiring installation of this solution should contact theirEMC Customer Engineer to assist with the installation and providethe documentation
Supported iSCSI sessionsThe current iSCSI session environment supported on the MDS is
300 sessions per port
1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no
InitialR2T=yes
Upgrading Cisco SAN-OSThere are several methods available for upgrading SAN-OS SoftwareEMC personnel are strongly recommended that all upgrades be doneby the Automated One-Step Upgrade using the install all
command EMC personnel should refer to the Connectrix MDS 9000Family Software Image Upgrade Instructions for a complete list ofprerequisites and instructions for performing the upgrade Thisdocument along with tftp software is available on the GlobalServices website at httpwwwcsisusEMCcom under ApplicationDownload Area ESN Product Information Connectrix MDS 9000Family
The Software Upgrade Wizard is an option for upgrades While theinstall all is the preferred method the Software Install Wizard canalso be used
Supported configuration parametersFor the most up-to-date information refer to the EMC Support Matrixavailable through E-Lab Interoperability Navigator athttpelabnavigatoremccom for the latest information onsupported configurations
35
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
Supported zoning parametersRefer to the EMC Networked Storage Topology Guide for the mostup-to-date information on supported zoning parameters
At the time these notes were published the following parameterswere supported
20 VSANs 5 Hops 2000 Unique members per physical infrastructure 1000 Zonesets per physical infrastructure 2000 Zones per physical infrastructure 1 FCIP tunnel
Supported IVR parameters IVR zone members 1000 IVR zones 1000 IVR zone sets 32 VSANS 20 IVR enabled switches 64
An RPQ can be submitted for any configurations that exceed thislimit
Managing zone changes in multiswitch fabricsZoning changes may be made through Fabric Manager or CLI Whenaccessing Fabric Manager or CLI the user does so from the point ofview of one switch That is Fabric Manager and CLI are accessed byentering the IP address of one switch in the fabric
When zoning changes are made the applicable VSAN and zone setdata is propagated to the rest of the switches in the fabric via the ISLs
When zoning changes are made to a VSAN the zone set data ispropagated to the rest of the switches in the fabric via the ISLs Bydefault only the active zone set information is relayed to all switchesin the VSAN If the user accesses the Fabric Manager and CLI fromanother switch in the fabric the new VSAN and zone set informationwill not be viewable To view the active and inactive zone set on theother switches in the fabric the user must log in to the CLI and issuea command from the EXEC prompt
36 EMC Connectrix MDS 9000 NX-OS Release Notes
Documentation
Example The following is an example of copying VSAN 1 through 20 zoningdata
CiscoMDS_name zone copy active full vsan 1-20
CiscoMDS_name conf t
Enter configuration commands one per line End with CNTL Z
CiscoMDS_name(config) zoneset distribute full vsan 1-20
CiscoMDS_name(config)
Note This command needs to be issued on all switches in the fabric one timeonly
This is a nondisruptive command After issuing the commands theuser will now see the active and inactive zone sets for the specifiedVSANs on any switch that is chosen from which to manage the fabric
After a zoning change is made save the running configuration to thestartup configuration
DocumentationSend documentation comments to mdsfeedback-doccom
Product DocumentationAs of NX-OS Release 42(1a) software configuration information isavailable in new feature-specific configuration guides for thefollowing information
System management
Interfaces
Fabric
Quality of service
Security
IP services
High availability and redundancy
37
Software media organization and files
EMC Connectrix MDS 9000 NX-OS Release Notes
The information in these new guides previously existed in the CiscoMDS 9000 Family CLI Configuration Guide That configuration guideremains available on Ciscocom and should be used for all softwarereleases prior to NX-OS Release 42(1a) Configuration guidesaddress the features introduced in or available in a particular releaseSelect and view the configuration guide that pertains to the softwareinstalled in your switch
In addition Fabric Manager information has been removed from theMDS NX-OS Release Notes (this document) and placed intostandalone Fabric Manager Release Notes that support both CiscoMDS 9000 Family switches and Cisco Nexus 5000 Series switchesThe Cisco Fabric Manager Release Notes are available onhttpPowerlinkemccom and from the following website
httpwwwciscocomenUSpartnerproductsps10495prod_release_notes_listhtml
Technical supportThese release notes complement a Cisco documentation set EachCisco document refers to where to get help However for any itemssupplied by EMC see ldquoTroubleshooting and getting helprdquo onpage 38
Software media organization and filesFor information on related software environment and systemrequirements refer to the EMC Support Matrix on EMC Powerlink at
httpPowerlinkEMCcom
InstallationFor hardware installation information refer to the Cisco MDS HWInstallation Guides available at Ciscocom
For EMC-specific installation information refer to ldquoEnvironment andsystem requirementsrdquo on page 5 in this document
38 EMC Connectrix MDS 9000 NX-OS Release Notes
Troubleshooting and getting help
Troubleshooting and getting helpEMC support product and licensing information can be obtained asfollows
Product information mdash For documentation release notes softwareupdates or for information about EMC products licensing andservice go to the EMC Powerlink website (registration required) at
httpPowerlinkEMCcom
Technical support mdash For technical support go to EMC CustomerService on Powerlink To open a service request through Powerlinkyou must have a valid support agreement Please contact your EMCsales representative for details about obtaining a valid supportagreement or to answer any questions about your account
Copyright copy 2011 EMC Corporation All rights reserved
EMC believes the information in this publication is accurate as of its publication date The information issubject to change without notice
THE INFORMATION IN THIS PUBLICATION IS PROVIDED ldquoAS ISrdquo EMC CORPORATION MAKES NOREPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION INTHIS PUBLICATION AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OFMERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Use copying and distribution of any EMC software described in this publication requires an applicablesoftware license
For the most up-to-date regulatory document for your product line go to the Technical Documentation andAdvisories section on EMC Powerlink
For the most up-to-date listing of EMC product names see EMC Corporation Trademarks on EMCcom
All other trademarks used herein are the property of their respective owners
11
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Software Download ProcessUse the software download procedure to upgrade to a later versionor downgrade to an earlier version of an operating system Thissection describes the software download process for the Cisco MDSNX-OS software and includes the following topics
ldquoDetermining the Software Versionrdquo on page 11
ldquoDownloading Softwarerdquo on page 11
ldquoSelecting the Correct Software Image for an MDS 9100 SeriesSwitchrdquo on page 12
ldquoSelecting the Correct Software Image for an MDS 9200 SeriesSwitchrdquo on page 13
ldquoSelecting the Correct Software Image for an MDS 9500 SeriesSwitchrdquo on page 13
Determining the Software VersionTo determine the version of Cisco MDS NX-OS or SAN-OS softwarecurrently running on a Cisco MDS 9000 Family switch using the CLIlog in to the switch and enter the show version EXEC command
To determine the version of Cisco MDS NX-OS or SAN-OS softwarecurrently running on a Cisco MDS 9000 Family switch using theFabric Manager view the Switches tab in the Information pane locatethe switch using the IP address logical name or WWN and check itsversion in the Release column
Note EMC strongly recommends that you use the latest qualified softwarerelease for all MDS 9000 Family products Refer to the EMC Support Matrixavailable through E-Lab Interoperability Navigator (ELN) athttpelabnavigatorEMCcom for the latest information on qualifiedfirmware revisions
Downloading SoftwareThe Cisco MDS NX-OS software is designed for mission-critical highavailability environments To realize the benefits of nondisruptiveupgrades on the Cisco MDS 9500 Directors we highly recommendthat you install dual supervisor modules
12 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Before performing upgrades submit all requested changes to theEMC Global Services CCA change control process so that anypotential operating environment impacts can be analyzedbeforehand
EMC personnel should also refer to the Connectrix MDS 9000 FamilySoftware Image Upgrade Instructions for a complete list of prerequisitesThis document is available on the Global Services websitehttpwwwcsisusEMCcom under Application Download AreaESN Product Information Connectrix MDS 9000 Family EMCpersonnel can download the Software Images from the GlobalServices website httpwwwcsisusEMCcom under ApplicationDownload Area ESN Product Information Connectrix MDS 9000Family
See the following sections in this release note for details on how youcan nondisruptively upgrade your Cisco MDS 9000 switch Issuingthe install all command from the CLI or using Fabric Manager toperform the downgrade enables the compatibility check The checkindicates if the upgrade can happen nondisruptively or disruptivelydepending on the current configuration of your switch and thereason
Compatibility check is doneModule bootable Impact Install-type Reason------ -------- -------------- ------------ ------
1 yes non-disruptive rolling2 yes disruptive rolling Hitless upgrade is not supported3 yes disruptive rolling Hitless upgrade is not supported4 yes non-disruptive rolling5 yes non-disruptive reset6 yes non-disruptive reset
Selecting the Correct Software Image for an MDS 9100 Series SwitchThe system and kickstart image that you use for an MDS 9100 seriesswitch depends on which switch you use as shown in Table 4
Table 4 Software Images for MDS 9100 Series Switches
Cisco MDS 9100 Series Switch Type Naming Convention
9124 and 9134 Filename begins with m9100-s2ek9
9148 Filename begins with m9100-s3ek9
13
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Selecting the Correct Software Image for an MDS 9200 Series SwitchThe system and kickstart image that you use for an MDS 9200 seriesswitch depends on which switch you use as shown in Table 5
Selecting the Correct Software Image for an MDS 9500 Series SwitchThe system and kickstart image that you use for an MDS 9500 Seriesswitch depends on whether the switch is based on a Supervisor-1module or a Supervisor-2 module as shown in Table 6
Use the show module command to display the type of supervisormodule in the switch The following is sample output from the showmodule command on a Supervisor 2 module
Table 5 Software Images for MDS 9200 Series Switches
Cisco MDS 9200 Series Switch Type Naming Convention
9222i Filename begins with m9200-s2ek9
Table 6 Software Images for Supervisor Type
Cisco MDS 9500 Series Switch Type Supervisor Module Type Naming Convention
9513 9509 and 9506 Supervisor-2 module Filename begins with m9500-sf2ek9
14 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
switch show moduleMod Ports Module-Type Model Status--- ----- -------------------------------- ------------------ ------------7 0 SupervisorFabric-2 DS-X9530-SF2-K9 active 8 0 SupervisorFabric-2 DS-X9530-SF2-K9 ha-standby
Upgrading Your Cisco MDS NX-OS Software ImageThis section lists the guidelines recommended for upgrading yourCisco MDS NX-OS software image and includes the following topics
ldquoGeneral Upgrading Guidelinesrdquo on page 14
ldquoDowngrading Your Cisco MDS SAN-OS Software Imagerdquo onpage 18
Note Before you begin the upgrade process review the list of chassis andmodules that NX-OS Release 50(4b) supports See the ldquoMDS 9000 Chassisand Module Support in Cisco MDS NX-OS 5xrdquo on page 8
Note For detailed instructions for performing a software upgrade usingCisco Fabric Manager see the Cisco Fabric Manager Release Notes forRelease 50(4b) which is available from the following websitehttpPowerlinkEMCcom
General Upgrading Guidelines
Note To upgrade to NX-OS Release 50(4b) you must be running NX-OSRelease 4x If you are running SAN-OS Release 32(3a) or earlier firstupgrade to SAN-OS Release 33(x) then NX-OS Release 4x and thenupgrade to NX-OS Release 50(4b)
Use the following guidelines when upgrading to Cisco MDS NX-OSRelease 5x
Install and configure dual supervisor modules
Issue the show install all impact upgrade-image CLI command todetermine if your upgrade will be nondisruptive
15
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Be aware of the impact of an upgrade on VSAN 4079 if you areupgrading from SAN-OS Release 3x to NX-OS 50(4b) See theldquoUpgrading Effect on VSAN 4079rdquo on page 17
Follow the recommended guidelines for upgrading a Cisco MDS9124 or MDS 9134 Switch as described in ldquoUpgrading a CiscoMDS 9124 or MDS 9134 switchrdquo on page 18
Take note of the affect of upgrades on MDS 9500 series switchesthat have active IOA flows as described in ldquoMDS 9500 seriesupgrades with active IOA flowsrdquo on page 18
Be aware that some features impact whether an upgrade isdisruptive or nondisruptive
bull Fibre Channel Ports Traffic on Fibre Channel ports can benondisruptively upgraded See Table 7 on page 16 for thenondisruptive upgrade path for all NX-OS and SAN-OSreleases
bull Storage Services Intelligent storage services traffic such asSANTap NASB and FC write acceleration is disruptedduring an upgrade Fibre Channel traffic is not
bull Gigabit Ethernet Ports Traffic on Gigabit Ethernet ports isdisrupted during an upgrade or downgrade This includes theGigabit Ethernet ports on the MSM-184 module and the MDS9222i switch Those nodes that are members of VSANs traversingan FCIP ISL are impacted and a fabric reconfiguration occursiSCSI initiators connected to the Gigabit Ethernet ports loseconnectivity to iSCSI targets while the upgrade is in progress
bull FICON If you have FICON enabled the upgrade path isdifferent See Table 6 on page 13
Use Table 7 to determine your nondisruptive upgrade path to Cisco MDSNX-OS Release 50(4b) find the image release number you are currentlyusing in the Current column of the table and use the path recommended
16 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Note The software upgrade information in Table 7 applies only to FibreChannel switching traffic Upgrading system software disrupts IP traffic andSSM intelligent services traffic
MDS NX-OS Release 50(4b) is not a FICON-qualified release
Table 7 Nondisruptive Upgrade Path to Cisco MDS NX-OS Release 50(4b)
Current Nondisruptive Upgrade Path
NX-OS 50(4) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 50(1a) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(7b) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(5) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(3) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(1b) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(1a) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 41(3a) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 41(1b) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
SAN-OS 33(4a) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
NX-OS 33(4) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 33(3) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 33(2) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 33(1c) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 32(3a) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 32(2c) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 32(1a) Upgrade to SAN-OS Release then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 31(3a) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 31(2) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
17
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Use Table 8 to determine your FICON nondisruptive upgrade path toCisco MDS NX-OS Release 42(7b) Find the image release numberyou are currently using in the Current Release with FICON Enabledcolumn of the table and use the path recommended
Note For more information on the FICON qualified NX-OS releases refer tothe EMC Support Matrix available through E-Lab Interoperability Navigator(ELN) at httpelabnavigatorEMCcom
Upgrading Effect on VSAN 4079If you are upgrading to NX-OS Release 50(4b) and you have notcreated VSAN 4079 the NX-OS software will automatically createVSAN 4079 and reserve it for EVFP use If VSAN 4079 is reserved forEVFP use the switchport trunk allowed vsan command will filterout VSAN 4079 from the allowed list as shown in the followingexample
switch(config-if) switchport trunk allowed vsan1-40801-40784080switch(config-if)
If you have created VSAN 4079 the upgrade to NX-OS Release50(4b) will have no affect on VSAN 4079
If you downgrade to a release of NX-OS lower than 41(x) afterNX-OS Release 50(4b) creates VSAN 4079 and reserves it for EVFPuse the VSAN will no longer be reserved
Table 8 FICON Nondisruptive Upgrade Path to NX-OS Release 42(7b)
Current Release withFICON Enabled Upgrade Path
NX-OS 42(1b) You can nondisruptively upgrade directly to NX-OS Release 42(7b)
NX-OS 41(1c) You can nondisruptively upgrade directly to NX-OS Release 42(7b)
SAN-OS 33(1c) You can nondisruptively upgrade directly to NX-OS Release 42(7b)
18 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Upgrading a Cisco MDS 9124 or MDS 9134 switchIf you are upgrading from Cisco MDS SAN-OS Release 31(1) to CiscoNX-OS Release 4x before upgrading to NX-OS Release 50(4b) on aCisco MDS 9124 or MDS 9134 switch follow these guidelines
During the upgrade configuration is not allowed and the fabric isexpected to be stable
The Fabric Shortest Path First (FSPF) timers must be configured tothe default value of 20 seconds otherwise the nondisruptiveupgrade is blocked to ensure that the maximum down toim forthe control plane can be 80 seconds
If there are any CFS commits in the fabric the nondisruptiveupgrade will fail
If there is a zone server merge in progress in the fabric thenondisruptive upgrde will fail
If a service terminates the nondisruptive upgrade the showinstall all failure-reason command can display the reason thatthe nondisruptive upgrade cannot proceed
If there is not enough memory in the system to load the newimages the upgrade will be made disruptive due to insufficientresources and the user will be notified in the compativility table
MDS 9500 series upgrades with active IOA flowsWhen upgading an MDS 9500 series switch that has active IOA flowsthose flows may be interrupted during the supervisor moduleswitchover To workaround this issue you have to enablespanning-tree portfast on the interface on the catalyst connected tothe management interface of the activestandby supervisor for theinterface to come up fast without causing the cluster to lose quorum
Downgrading Your Cisco MDS SAN-OS Software ImageThis section lists the guidelines recommended for downgrading yourCisco MDS SAN-OS software image and includes the followingtopics
ldquoGeneral downgrading guidelinesrdquo on page 19
19
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
General downgrading guidelinesUse the following guidelines to nondisruptively downgrade yourCisco MDS NX-OS Release 50(4b)
Install and configure dual supervisor modules
Issue the system no acl-adjacency-sharing execute command todisable acl adjacency usage on Generation 2 and Generation 1modules If this command fails reduce the number of zones IVRzones TE ports or a combination of these in the system and issuethe command again
Disable all features not supported by the downgrade release Usethe show incompatibility system downgrade-image command todetermine what you need to disable
bull If you are running in interoperability mode two such featuresare the Reliable Commit Service and Full Zone DatabaseDistribution They can be disabled by running thesecommand in config term mode
no zone rcs enableno zoneset capability distribute full
Use the show install all impact downgrade-image command todetermine if your downgrade will be nondisruptive
Be aware that some features impact whether a downgrade isdisruptive or nondisruptive
bull Fibre Channel Ports Traffic on Fibre Channel ports can benondisruptively downgraded See Table 9 on page 20 for thenondisruptive downgrade path for all SAN-OS releases
bull Storage Services Intelligent storage services traffic such asSANTap NASB and FC write acceleration is disruptedduring a downgrade Fibre Channel traffic is not
bull Gigabit Ethernet Ports Traffic on Gigabit Ethernet ports isdisrupted during a downgrade This includes the GigabitEthernet ports on the MSM-184 module and the MDS 9222iswitch Those nodes that are members of VSANs traversing anFCIP ISL are impacted and a fabric reconfiguration occursiSCSI initiators connected to the Gigabit Ethernet ports loseconnectivity to iSCSI targets while the downgrade is inprogress
20 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
bull FICON If you have FICON enabled the downgrade path isdifferent See Table 10 on page 21
Note A downgrade from NX-OS Release 4x to SAN-OS Release 33(1c) is notsupported on MDS switches when FC-Redirect based applications such asData Mobility Manager or Storage Media Encryption are configured in thefabric if either of the following conditions are satisfied
1 A target for which FC-Redirect is configured is connected locally and thereare Generation 1 modules with ISLs configured in the switch
2 A host for which FC-redirect is configured is connected locally ona Generation 1 module
If these conditions exist remove the application configuration forthese targets and hosts before proceeding with the downgrade
Use Table 9 on page 20 to determine the nondisruptive downgradepath from Cisco NX-OS Release 50(4b) Find the NX-OS or SAN-OSimage you want to downgrade to in the To SAN-OSNX-OS Releasecolumn of the table and use the path recommended
Note The software downgrade information in Table 10 on page 21 appliesonly to Fibre Channel switching traffic Downgrading system softwaredisrupts IP and SSM intelligent services traffic
Table 9 Nondisruptive Downgrade Path from NX-OS Release 50(4b) (page 1 of2)
To SAN-OS NX-OSRelease Nondisruptive Downgrade Path
NX-OS 50(4) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 50(1a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(7b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(5) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(3) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(1b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(1a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 41(3a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
21
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Use Table 10 to determine your nondisruptive downgrade path if youhave FICON enabled from Cisco NX-OS Release 42(7b) Find the imagerelease number you are currently using in the Current Release withFICON Enabled column of the table and use the path recommended
NX-OS 41(1b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
SAN-OS 33(5a) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33())
SAN-OS 33(5) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(4a) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
NX-OS 33(4) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(3) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
NX-OS 33(2) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(1c) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 32(3a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 32(x)
SAN-OS 32(2c) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 32(x)
SAN-OS 32(1a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
SAN-OS 31(3a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
SAN-OS 31(2) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
Table 9 Nondisruptive Downgrade Path from NX-OS Release 50(4b) (page 2 of2)
To SAN-OS NX-OSRelease Nondisruptive Downgrade Path
Table 10 FICON Downgrade Path from NX-OS Release 42(7b)
To SAN-OSNX-OS Release withFICON Enabled Downgrade Path
NX-OS 42(1b) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
NX-OS 41(1c) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
SAN-OS 33(1c) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
22 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Best practicesLog messages are not saved across system reboots or power outagesTherefore EMC recommends that customers configure a SyslogServer in order to redirect and capture all log messages on a remoteserver For more information please refer to the Cisco MDS 9000Family Configuration Guide available at
httpwwwciscocomenUSproductsps5989products_support_series_homehtml
Maximum ports per chassisTable 11 shows the maximum ports per chassis
a V2 indicates a 9506 or 9509 with Generation-2 Supervisors The presence of anygeneration one module in a switch will limit the maximum port count to 252This includes the 16-port 32-port 14+2 IPS4 and IPS8 cards
Known problems and limitationsFor a list of problems with this release please refer to the CiscoRelease notes located at
httpwwwciscocomenUSproductsps5989prod_release_notes_listhtml
Limitations and restrictionsThe following limitations and restrictions apply to all switches in theCisco MDS 9000 Family unless a limitation for a specific switch isstated
ldquoStorage Media Encryption (SME) limitationsrdquo on page 24
Table 11 Maximum ports per chassis
Chassis Maximum number of ports
MDS 9506-V2 192a
MDS 9509-V2 336
MDS 9513 528
23
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
ldquoSME configuration limitsrdquo on page 24
ldquoDeleting Cisco SME interfacesrdquo on page 25
ldquoCisco MDS 9124 and 9134 Multilayer fabric switchesrdquo on page 25
ldquoN-Port virtualization configuration limitsrdquo on page 25
ldquoMaximum number of zones supported in Interop Mode 4rdquo onpage 25
ldquoIPv6rdquo on page 26
ldquoIP-ACL supportrdquo on page 26
ldquoUser Rolesrdquo on page 26
ldquoUsing a RSA Version 1 Key for SSH Following an Upgraderdquo onpage 27
ldquoApplying Zone Configurations to VSAN 1rdquo on page 27
ldquoInterVSAN Routingrdquo on page 28
ldquoRSPAN Traffic Not Supported on CTS Ports on 8-GbpsSwitching Modulesrdquo on page 28
ldquoIO Accelerator Feature Limitationsrdquo on page 28
ldquoSupport for FCIP Compression Modesrdquo on page 28
ldquoSaving Copies of the Running Kickstart and System Imagesrdquo onpage 29
ldquoConfiguring Buffer Credits on a Generation 2 or Generation 3Modulerdquo on page 29
ldquoStorage services module power budgetrdquo on page 29
ldquoiSCSI proxy initiator in Celerra HighRoad environmentsrdquo onpage 30
ldquoHPUX N_port IDrdquo on page 30
ldquoInteroperability limitationsrdquo on page 31
ldquoNASBrdquo on page 31
ldquoReserved VSAN Range and Isolated VSAN Range Guidelinesrdquoon page 31
ldquoSymmetrix VMax limitationsrdquo on page 32
ldquoStorage Applications on the MSM-184rdquo on page 32
ldquoDowngrading with fport-channel-trunk enabledrdquo on page 32
ldquoLDAP Authenticationrdquo on page 33
24 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
ldquoMDS-9148 limitationsrdquo on page 33
Storage Media Encryption (SME) limitationsAn SME node can only belong to one cluster Adding the node tomore than one cluster will cause problems
Currently there is no prevention or warning in place when an attemptis made to add a node to multiple clusters
SME configuration limitsTable 12 lists the SME configuration limits for this release
Table 12 SME configuration limits
Configuration Limits
Number of switches in the fabric 10
Number of clusters per switch 1
Switches in a cluster 4
Fabrics in a cluster 2
Modules in a switch 11
Cisco MSM-184 modules in a cluster 32
Initiator-Target-LUNs (ITLs) 1024
LUNs behind a target 32
Host and target ports in a cluster 128
Number of hosts per target 128
Tape backup groups per cluster 2
Volume groups in a tape backup group 4
Cisco Key Management Center ( of keys) 32K
Targets per switch that can be FC-redirected 32
25
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Deleting Cisco SME interfacesA Cisco SME interface can be deleted from the cluster only after theinterface is administratively shut-down and all related tasksassociated with the interface shut-down are complete
Cisco MDS 9124 and 9134 Multilayer fabric switchesThe Cisco MDS 9124 and 9134 Multilayer fabric switches do notsupport the following Cisco MDS SAN-OS features
IVR Remote Span Translative loop support FCCmdash no generation quench reaction only
In addition the following features have these limits
VSANs mdash 16 maximum SPAN mdash 1 session maximum
N-Port virtualization configuration limitsThe NPV features have maximum configuration limits Table 13shows the verified and maximum limits for the NPV switchesrunning NX-OS Release 5x
Maximum number of zones supported in Interop Mode 4In interop mode 4 the maximum number of zones that is supportedin an active zone set is 2047 due to limitations in the connectedvendor switch When IVR is used in interop mode 4 the maximumnumber of zones supported including IVR zones in the active zoneset is 2047 The limit for the maximum number of IVR zones perVSAN is 250 zones (two members per zone)
Table 13 NPV features limitations
Feature Verified limits Maximum limits
FLOGIs or F Disc per NPV port group 114 114
NPV switches per NPV core switch 105 105
FLOGIs per line card on NPV core switch 400 400
26 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
IPv6The management port on Cisco MDS switches supports oneuser-configured IPv6 address but does not supportauto-configuration of an IPv6 address
IP-ACL supportDo not apply IP-ACLs to only one member of a PortChannel groupApply IP-ACLs to the entire channel group
If IP-ACLs are already configured in a Gigabit Ethernet interface youcannot add this interface to a Ethernet PortChannel group
Refer to the Cisco MDS 9000 Family Configuration Guide
User RolesIn SAN-OS Release 33(x) and earlier when a user belongs to a rolewhich has a VSAN policy set to Deny and the role allows access to aspecific set of VSANs (for example 1 through 10) the user isrestricted from performing the configuration clear execute anddebug commands which had a VSAN parameter outside thisspecified set Beginning with NX-OS Release 41(1b) these users arestill prevented from performing configuration clear execute anddebug commands as before however they are allowed to performshow commands for all VSANs The ability to execute the showcommand addresses the following
In a network environment users often need to view informationin other VSANs even though they do not have permission tomodify configurations in those VSANs
This behavior makes Cisco MDS 9000 Series switches consistentwith other Cisco products such as Cisco Nexus 7000 Seriesswitches that exhibit the same behavior for those roles (whenthey apply to the VLAN policy)
27
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Using a RSA Version 1 Key for SSH Following an UpgradeFor security reasons NX-OS Release 42(x) and higher does notsupport RSA version 1 keys As a result if you upgrade from anearlier version that did support RSA version 1 keys and you hadconfigured a RSA version 1 key for SSH then you will not be able tolog in through SSH following the upgrade
If you have a RSA version 1 key configured for SSH beforeupgrading to NX-OS Release 42(x) or higher follow these steps
1 Disable SSH
2 Create RSA version 2 DSA keys
3 Enable SSH
4 Delete any RSA version 1 keys on any remote SSH clients andreplace the version 1 keys with the new version 2 keys from theswitch
Proceed with the upgrade to NX-OS Release 42(x) or higher
If you upgrade before disabling SSH and creating RSA version 2 keysfollow these steps
1 Open a Telnet session and log in through the console
2 Issue the no feature ssh command to disable SSH
3 Issue the ssh key rsa 1024 command to create RSA version 2 keys
4 Issue the feature ssh command to enable SSH
Applying Zone Configurations to VSAN 1In the setup script you can configure system default values for thedefault-zone to be permit or deny and you can configure defaultvalues for the zone distribution method and for the zone mode
These default settings are applied when a new VSAN is createdHowever the settings will not take effect on VSAN 1 because it existsprior to running the setup script Therefore when you need thosesettings for VSAN 1 you must explicitly issue the followingcommands
zone default-zone permit vsan 1 zoneset distribute full vsan 1 zone mode enhanced vsan 1
28 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
InterVSAN RoutingWhen using InterVSAN Routing (IVR) it is recommended to enableCisco Fabric Services (CFS) on all IVR-enabled switches Failure to doso may cause mismatched active zone sets if an error occurs duringzone set activation
RSPAN Traffic Not Supported on CTS Ports on 8-Gbps Switching ModulesAn inter-switch link (ISL) that is enabled for Cisco TrustSec (CTS)encryption must be brought up in non-CTS mode to support remoteSPAN (RSPAN) traffic on the following modules
DS-X9248-96K9 Cisco MDS 9000 48-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9224-96K9 Cisco MDS 9000 24-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9248-48K9 Cisco MDS 9000 444-Port Host-Optimized8-Gbps Fibre Channel Switching Module
If the ISL link is brought up with CTS enabled random packets dropsof both RSPAN traffic and normal traffic will occur on the receiverport switch
IO Accelerator Feature LimitationsIOA does not support the following NX-OS features
IVR flows
Devices with NPV and NPIV enabled
F port trunking
bull F port channeling
Support for FCIP Compression ModesIn Cisco NX-OS Release 42(1b) and higher FCIP compression mode 1and compression mode 3 are not supported on the Cisco MSM-184module and on the SSN-16 module
29
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Saving Copies of the Running Kickstart and System ImagesAfter you upgrade to MDS NX-OS Release 42(1b) or higher you arenot allowed to delete rename move or overwrite the kickstart andsystem images that are in the current system bootvar settings on anactive or standby MDS Supervisor-2 module on any Cisco MDS 9500Series switch This restriction does not apply to the integratedsupervisor module on the MDS 9200 and MDS 9100 series switches
Configuring Buffer Credits on a Generation 2 or Generation 3 ModuleWhen you configure port mode to auto or E on a Generation 2module one of the ports will not come up for the followingconfiguration
Port Mode auto or E for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E on a Generation 3module one or two of the ports will not come up for the followingconfiguration
Port Mode auto or E for the first half of the ports the second halfof the ports or for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E for all ports in the globalbuffer pool you need to reconfigure buffer credits on one or more ofthe ports The total number of buffer credits configured for all theports in the global buffer pool should be reduced by 64
Storage services module power budgetThe MDS 9509 does not have the power budget to run seven SSMcards EMC recommends a maximum of four SSMs in one 9509Customers wishing to use more than four SSMs in one chassis shouldrefer to the Cisco MDS 9000 documentation on the Ciscocom websiteto validate that there is enough power available for their desiredconfiguration
30 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Note Upgrading to the 3000 watt power supplies will alleviate thiscondition
iSCSI proxy initiator in Celerra HighRoad environmentsEMC supports the iSCSI proxy initiator feature in Celerrareg
HighRoadreg environments In proxy initiator mode one Fibre Channelinitiator is used for all iSCSI clients who access the switch via thesame iSCSI interface (iscsi33 for example)
The initiators will use the PWWN assigned to the iSCSI interface TheiSCSI interface to which an iSCSI client will logon to is configured inthe client and must be permitted by the virtual target configured forthat initiator
The current session environment supported on the MDS is
300 sessions per port 1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no InitialR2T=yes
Refer to the specific initiator support documentation on how to setthe parameters The implementation will not perform properly ifthese bits are not set
Refer to the MDS documentation for more information regarding theconfiguration of the iSCSI proxy initiator at the following Ciscowebsite
httpwwwciscocomenUSproducts
HPUX N_port IDThe N_port ID port value of 255 (0xFF) has special meaning forHP-UX A N_port ID (FC_ID) can not be returned from a switch thatcontains this value for the N_port ID (FC_ID) port value for a HP-UXinitiator or HP-UX target port Port ID value of 255 (0xFF) cannot be
31
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
configured for HP-UX initiator port and HP-UX target ports whenconfiguring MDS FC_IDs The port_ID value is the third byte of theFC_ID
Interoperability limitationsRefer to the EMC Support Matrix (ESM) and the EMC Networked Storage Topology Guide for modes of operation and caveats
NASBThe NASB feature requires that the backup application load the tapedrive with a compatible tape cartridge prior to configuring NASB inthe backup VSAN
Reserved VSAN Range and Isolated VSAN Range GuidelinesOn an NPV switch with a trunking configuration on any interface or ona regular switch where the feature fport_channel_trunk command hasbeen issued to enable the F PortChannel feature follow theseconfiguration guidelines for reserved VSANs and the isolated VSAN
bull If trunk mode is on for any of the interfaces or NP PortChannelis up the reserved VSANs are 3040 to 4078 and they are notavailable for user configuration
bull The Exchange Virtual Fabric Protocol (EVFP) isolated VSAN is4079 and it is not available for user configuration
bull VSAN 4079 will be impacted by an upgrade to NX-OS Release42(3) depending on whether or not VSAN 4079 was createdprior to the upgrade See theldquoUpgrading Effect on VSAN 4079rdquoon page 17
The following VSAN IDs are assigned in the Fibre Channel Framingand Signaling (FC-FS) interface standard
VF_ID Value Value Description
00h Do not use as a Virtual FabricIdentifier
001h EFFh Available as a Virtual FabricIdentifier
F00h FEEh Reserved
32 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Symmetrix VMax limitationsAt the time of this writing the following features are not supportedfor use with the Symmetrix VMax
FCIP Write Acceleration
The NX-OS IOA functionality is only supported with the Q2 SREnginuity release 5874229182 or higher
For the most up to date status please refer to the current revision ofthese Release Notes on httpPowerlinkemccom and the EMCSupport Matrix available through E-Lab Interoperability Navigator (ELN) athttpelabnavigatorEMCcom
Storage Applications on the MSM-184The MDS 9000 184-Port Multiservice Module (MSM-184) does notsupport multiple concurrent storage applications Only oneapplication can run on the MSM-184 at a time
Downgrading with fport-channel-trunk enabledIf you are running MDS NX-OS Release 42(x) or higher with thefport-channel-trunk feature enabled and you downgrade to anyNX-OS 41(1x) release the installer performs a nondisruptivedowngrade even though the fport-channel-trunk feature is notsupported in NX-OS 41(1x) releases
As a result the switch is in an inconsistent state and the ports maynot function properly
FEFh Control VF-ID (see FibreChannel Link Services (FC-LS)and Fibre Channel SwitchFabric Generation 4 (FC-SW-4)standards)
FF0h FFEh Vendor specific
FFFh Do not use as a Virtual FabricIdentifier
FEFh = 4079
33
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
If you are in this state a workaround is to reboot the switch followingthe upgrade
LDAP AuthenticationThere is currently a limitation in the LDAP server configuration CLIthat prevents the use of an OU with spaces in the name Normallythese OU names could be surrounded by quotation marks howeverquotation marks are not supported by the ldap-server command
MDS-9148 limitationsThe Cisco MDS 9148 Multilayer Fabric Switch does not support thefollowing NX-OS features
Medium and Long range 4GB Agilent
IVR
Remote Span
Translative loop support
FCC - no generation quench reaction only
FC-Redirect
In addition the following features have these limits
VSANS - 31 maximum
SPAN - 1 session maximum
Technical notesThe following sections provide further information on technicalnotes
EMC Email Home for Cisco MDS switchesInstallation and Trouble shooting instructions can be found in thedocumentation located at the EMC Customer Service Internalwebsite
httpwwwcsisusemccomcsweb2esnesnhomehtmConnectrix20MDS20900020Family
34 EMC Connectrix MDS 9000 NX-OS Release Notes
Technical notes
Customers requiring installation of this solution should contact theirEMC Customer Engineer to assist with the installation and providethe documentation
Supported iSCSI sessionsThe current iSCSI session environment supported on the MDS is
300 sessions per port
1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no
InitialR2T=yes
Upgrading Cisco SAN-OSThere are several methods available for upgrading SAN-OS SoftwareEMC personnel are strongly recommended that all upgrades be doneby the Automated One-Step Upgrade using the install all
command EMC personnel should refer to the Connectrix MDS 9000Family Software Image Upgrade Instructions for a complete list ofprerequisites and instructions for performing the upgrade Thisdocument along with tftp software is available on the GlobalServices website at httpwwwcsisusEMCcom under ApplicationDownload Area ESN Product Information Connectrix MDS 9000Family
The Software Upgrade Wizard is an option for upgrades While theinstall all is the preferred method the Software Install Wizard canalso be used
Supported configuration parametersFor the most up-to-date information refer to the EMC Support Matrixavailable through E-Lab Interoperability Navigator athttpelabnavigatoremccom for the latest information onsupported configurations
35
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
Supported zoning parametersRefer to the EMC Networked Storage Topology Guide for the mostup-to-date information on supported zoning parameters
At the time these notes were published the following parameterswere supported
20 VSANs 5 Hops 2000 Unique members per physical infrastructure 1000 Zonesets per physical infrastructure 2000 Zones per physical infrastructure 1 FCIP tunnel
Supported IVR parameters IVR zone members 1000 IVR zones 1000 IVR zone sets 32 VSANS 20 IVR enabled switches 64
An RPQ can be submitted for any configurations that exceed thislimit
Managing zone changes in multiswitch fabricsZoning changes may be made through Fabric Manager or CLI Whenaccessing Fabric Manager or CLI the user does so from the point ofview of one switch That is Fabric Manager and CLI are accessed byentering the IP address of one switch in the fabric
When zoning changes are made the applicable VSAN and zone setdata is propagated to the rest of the switches in the fabric via the ISLs
When zoning changes are made to a VSAN the zone set data ispropagated to the rest of the switches in the fabric via the ISLs Bydefault only the active zone set information is relayed to all switchesin the VSAN If the user accesses the Fabric Manager and CLI fromanother switch in the fabric the new VSAN and zone set informationwill not be viewable To view the active and inactive zone set on theother switches in the fabric the user must log in to the CLI and issuea command from the EXEC prompt
36 EMC Connectrix MDS 9000 NX-OS Release Notes
Documentation
Example The following is an example of copying VSAN 1 through 20 zoningdata
CiscoMDS_name zone copy active full vsan 1-20
CiscoMDS_name conf t
Enter configuration commands one per line End with CNTL Z
CiscoMDS_name(config) zoneset distribute full vsan 1-20
CiscoMDS_name(config)
Note This command needs to be issued on all switches in the fabric one timeonly
This is a nondisruptive command After issuing the commands theuser will now see the active and inactive zone sets for the specifiedVSANs on any switch that is chosen from which to manage the fabric
After a zoning change is made save the running configuration to thestartup configuration
DocumentationSend documentation comments to mdsfeedback-doccom
Product DocumentationAs of NX-OS Release 42(1a) software configuration information isavailable in new feature-specific configuration guides for thefollowing information
System management
Interfaces
Fabric
Quality of service
Security
IP services
High availability and redundancy
37
Software media organization and files
EMC Connectrix MDS 9000 NX-OS Release Notes
The information in these new guides previously existed in the CiscoMDS 9000 Family CLI Configuration Guide That configuration guideremains available on Ciscocom and should be used for all softwarereleases prior to NX-OS Release 42(1a) Configuration guidesaddress the features introduced in or available in a particular releaseSelect and view the configuration guide that pertains to the softwareinstalled in your switch
In addition Fabric Manager information has been removed from theMDS NX-OS Release Notes (this document) and placed intostandalone Fabric Manager Release Notes that support both CiscoMDS 9000 Family switches and Cisco Nexus 5000 Series switchesThe Cisco Fabric Manager Release Notes are available onhttpPowerlinkemccom and from the following website
httpwwwciscocomenUSpartnerproductsps10495prod_release_notes_listhtml
Technical supportThese release notes complement a Cisco documentation set EachCisco document refers to where to get help However for any itemssupplied by EMC see ldquoTroubleshooting and getting helprdquo onpage 38
Software media organization and filesFor information on related software environment and systemrequirements refer to the EMC Support Matrix on EMC Powerlink at
httpPowerlinkEMCcom
InstallationFor hardware installation information refer to the Cisco MDS HWInstallation Guides available at Ciscocom
For EMC-specific installation information refer to ldquoEnvironment andsystem requirementsrdquo on page 5 in this document
38 EMC Connectrix MDS 9000 NX-OS Release Notes
Troubleshooting and getting help
Troubleshooting and getting helpEMC support product and licensing information can be obtained asfollows
Product information mdash For documentation release notes softwareupdates or for information about EMC products licensing andservice go to the EMC Powerlink website (registration required) at
httpPowerlinkEMCcom
Technical support mdash For technical support go to EMC CustomerService on Powerlink To open a service request through Powerlinkyou must have a valid support agreement Please contact your EMCsales representative for details about obtaining a valid supportagreement or to answer any questions about your account
Copyright copy 2011 EMC Corporation All rights reserved
EMC believes the information in this publication is accurate as of its publication date The information issubject to change without notice
THE INFORMATION IN THIS PUBLICATION IS PROVIDED ldquoAS ISrdquo EMC CORPORATION MAKES NOREPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION INTHIS PUBLICATION AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OFMERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Use copying and distribution of any EMC software described in this publication requires an applicablesoftware license
For the most up-to-date regulatory document for your product line go to the Technical Documentation andAdvisories section on EMC Powerlink
For the most up-to-date listing of EMC product names see EMC Corporation Trademarks on EMCcom
All other trademarks used herein are the property of their respective owners
12 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Before performing upgrades submit all requested changes to theEMC Global Services CCA change control process so that anypotential operating environment impacts can be analyzedbeforehand
EMC personnel should also refer to the Connectrix MDS 9000 FamilySoftware Image Upgrade Instructions for a complete list of prerequisitesThis document is available on the Global Services websitehttpwwwcsisusEMCcom under Application Download AreaESN Product Information Connectrix MDS 9000 Family EMCpersonnel can download the Software Images from the GlobalServices website httpwwwcsisusEMCcom under ApplicationDownload Area ESN Product Information Connectrix MDS 9000Family
See the following sections in this release note for details on how youcan nondisruptively upgrade your Cisco MDS 9000 switch Issuingthe install all command from the CLI or using Fabric Manager toperform the downgrade enables the compatibility check The checkindicates if the upgrade can happen nondisruptively or disruptivelydepending on the current configuration of your switch and thereason
Compatibility check is doneModule bootable Impact Install-type Reason------ -------- -------------- ------------ ------
1 yes non-disruptive rolling2 yes disruptive rolling Hitless upgrade is not supported3 yes disruptive rolling Hitless upgrade is not supported4 yes non-disruptive rolling5 yes non-disruptive reset6 yes non-disruptive reset
Selecting the Correct Software Image for an MDS 9100 Series SwitchThe system and kickstart image that you use for an MDS 9100 seriesswitch depends on which switch you use as shown in Table 4
Table 4 Software Images for MDS 9100 Series Switches
Cisco MDS 9100 Series Switch Type Naming Convention
9124 and 9134 Filename begins with m9100-s2ek9
9148 Filename begins with m9100-s3ek9
13
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Selecting the Correct Software Image for an MDS 9200 Series SwitchThe system and kickstart image that you use for an MDS 9200 seriesswitch depends on which switch you use as shown in Table 5
Selecting the Correct Software Image for an MDS 9500 Series SwitchThe system and kickstart image that you use for an MDS 9500 Seriesswitch depends on whether the switch is based on a Supervisor-1module or a Supervisor-2 module as shown in Table 6
Use the show module command to display the type of supervisormodule in the switch The following is sample output from the showmodule command on a Supervisor 2 module
Table 5 Software Images for MDS 9200 Series Switches
Cisco MDS 9200 Series Switch Type Naming Convention
9222i Filename begins with m9200-s2ek9
Table 6 Software Images for Supervisor Type
Cisco MDS 9500 Series Switch Type Supervisor Module Type Naming Convention
9513 9509 and 9506 Supervisor-2 module Filename begins with m9500-sf2ek9
14 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
switch show moduleMod Ports Module-Type Model Status--- ----- -------------------------------- ------------------ ------------7 0 SupervisorFabric-2 DS-X9530-SF2-K9 active 8 0 SupervisorFabric-2 DS-X9530-SF2-K9 ha-standby
Upgrading Your Cisco MDS NX-OS Software ImageThis section lists the guidelines recommended for upgrading yourCisco MDS NX-OS software image and includes the following topics
ldquoGeneral Upgrading Guidelinesrdquo on page 14
ldquoDowngrading Your Cisco MDS SAN-OS Software Imagerdquo onpage 18
Note Before you begin the upgrade process review the list of chassis andmodules that NX-OS Release 50(4b) supports See the ldquoMDS 9000 Chassisand Module Support in Cisco MDS NX-OS 5xrdquo on page 8
Note For detailed instructions for performing a software upgrade usingCisco Fabric Manager see the Cisco Fabric Manager Release Notes forRelease 50(4b) which is available from the following websitehttpPowerlinkEMCcom
General Upgrading Guidelines
Note To upgrade to NX-OS Release 50(4b) you must be running NX-OSRelease 4x If you are running SAN-OS Release 32(3a) or earlier firstupgrade to SAN-OS Release 33(x) then NX-OS Release 4x and thenupgrade to NX-OS Release 50(4b)
Use the following guidelines when upgrading to Cisco MDS NX-OSRelease 5x
Install and configure dual supervisor modules
Issue the show install all impact upgrade-image CLI command todetermine if your upgrade will be nondisruptive
15
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Be aware of the impact of an upgrade on VSAN 4079 if you areupgrading from SAN-OS Release 3x to NX-OS 50(4b) See theldquoUpgrading Effect on VSAN 4079rdquo on page 17
Follow the recommended guidelines for upgrading a Cisco MDS9124 or MDS 9134 Switch as described in ldquoUpgrading a CiscoMDS 9124 or MDS 9134 switchrdquo on page 18
Take note of the affect of upgrades on MDS 9500 series switchesthat have active IOA flows as described in ldquoMDS 9500 seriesupgrades with active IOA flowsrdquo on page 18
Be aware that some features impact whether an upgrade isdisruptive or nondisruptive
bull Fibre Channel Ports Traffic on Fibre Channel ports can benondisruptively upgraded See Table 7 on page 16 for thenondisruptive upgrade path for all NX-OS and SAN-OSreleases
bull Storage Services Intelligent storage services traffic such asSANTap NASB and FC write acceleration is disruptedduring an upgrade Fibre Channel traffic is not
bull Gigabit Ethernet Ports Traffic on Gigabit Ethernet ports isdisrupted during an upgrade or downgrade This includes theGigabit Ethernet ports on the MSM-184 module and the MDS9222i switch Those nodes that are members of VSANs traversingan FCIP ISL are impacted and a fabric reconfiguration occursiSCSI initiators connected to the Gigabit Ethernet ports loseconnectivity to iSCSI targets while the upgrade is in progress
bull FICON If you have FICON enabled the upgrade path isdifferent See Table 6 on page 13
Use Table 7 to determine your nondisruptive upgrade path to Cisco MDSNX-OS Release 50(4b) find the image release number you are currentlyusing in the Current column of the table and use the path recommended
16 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Note The software upgrade information in Table 7 applies only to FibreChannel switching traffic Upgrading system software disrupts IP traffic andSSM intelligent services traffic
MDS NX-OS Release 50(4b) is not a FICON-qualified release
Table 7 Nondisruptive Upgrade Path to Cisco MDS NX-OS Release 50(4b)
Current Nondisruptive Upgrade Path
NX-OS 50(4) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 50(1a) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(7b) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(5) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(3) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(1b) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(1a) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 41(3a) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 41(1b) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
SAN-OS 33(4a) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
NX-OS 33(4) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 33(3) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 33(2) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 33(1c) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 32(3a) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 32(2c) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 32(1a) Upgrade to SAN-OS Release then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 31(3a) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 31(2) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
17
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Use Table 8 to determine your FICON nondisruptive upgrade path toCisco MDS NX-OS Release 42(7b) Find the image release numberyou are currently using in the Current Release with FICON Enabledcolumn of the table and use the path recommended
Note For more information on the FICON qualified NX-OS releases refer tothe EMC Support Matrix available through E-Lab Interoperability Navigator(ELN) at httpelabnavigatorEMCcom
Upgrading Effect on VSAN 4079If you are upgrading to NX-OS Release 50(4b) and you have notcreated VSAN 4079 the NX-OS software will automatically createVSAN 4079 and reserve it for EVFP use If VSAN 4079 is reserved forEVFP use the switchport trunk allowed vsan command will filterout VSAN 4079 from the allowed list as shown in the followingexample
switch(config-if) switchport trunk allowed vsan1-40801-40784080switch(config-if)
If you have created VSAN 4079 the upgrade to NX-OS Release50(4b) will have no affect on VSAN 4079
If you downgrade to a release of NX-OS lower than 41(x) afterNX-OS Release 50(4b) creates VSAN 4079 and reserves it for EVFPuse the VSAN will no longer be reserved
Table 8 FICON Nondisruptive Upgrade Path to NX-OS Release 42(7b)
Current Release withFICON Enabled Upgrade Path
NX-OS 42(1b) You can nondisruptively upgrade directly to NX-OS Release 42(7b)
NX-OS 41(1c) You can nondisruptively upgrade directly to NX-OS Release 42(7b)
SAN-OS 33(1c) You can nondisruptively upgrade directly to NX-OS Release 42(7b)
18 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Upgrading a Cisco MDS 9124 or MDS 9134 switchIf you are upgrading from Cisco MDS SAN-OS Release 31(1) to CiscoNX-OS Release 4x before upgrading to NX-OS Release 50(4b) on aCisco MDS 9124 or MDS 9134 switch follow these guidelines
During the upgrade configuration is not allowed and the fabric isexpected to be stable
The Fabric Shortest Path First (FSPF) timers must be configured tothe default value of 20 seconds otherwise the nondisruptiveupgrade is blocked to ensure that the maximum down toim forthe control plane can be 80 seconds
If there are any CFS commits in the fabric the nondisruptiveupgrade will fail
If there is a zone server merge in progress in the fabric thenondisruptive upgrde will fail
If a service terminates the nondisruptive upgrade the showinstall all failure-reason command can display the reason thatthe nondisruptive upgrade cannot proceed
If there is not enough memory in the system to load the newimages the upgrade will be made disruptive due to insufficientresources and the user will be notified in the compativility table
MDS 9500 series upgrades with active IOA flowsWhen upgading an MDS 9500 series switch that has active IOA flowsthose flows may be interrupted during the supervisor moduleswitchover To workaround this issue you have to enablespanning-tree portfast on the interface on the catalyst connected tothe management interface of the activestandby supervisor for theinterface to come up fast without causing the cluster to lose quorum
Downgrading Your Cisco MDS SAN-OS Software ImageThis section lists the guidelines recommended for downgrading yourCisco MDS SAN-OS software image and includes the followingtopics
ldquoGeneral downgrading guidelinesrdquo on page 19
19
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
General downgrading guidelinesUse the following guidelines to nondisruptively downgrade yourCisco MDS NX-OS Release 50(4b)
Install and configure dual supervisor modules
Issue the system no acl-adjacency-sharing execute command todisable acl adjacency usage on Generation 2 and Generation 1modules If this command fails reduce the number of zones IVRzones TE ports or a combination of these in the system and issuethe command again
Disable all features not supported by the downgrade release Usethe show incompatibility system downgrade-image command todetermine what you need to disable
bull If you are running in interoperability mode two such featuresare the Reliable Commit Service and Full Zone DatabaseDistribution They can be disabled by running thesecommand in config term mode
no zone rcs enableno zoneset capability distribute full
Use the show install all impact downgrade-image command todetermine if your downgrade will be nondisruptive
Be aware that some features impact whether a downgrade isdisruptive or nondisruptive
bull Fibre Channel Ports Traffic on Fibre Channel ports can benondisruptively downgraded See Table 9 on page 20 for thenondisruptive downgrade path for all SAN-OS releases
bull Storage Services Intelligent storage services traffic such asSANTap NASB and FC write acceleration is disruptedduring a downgrade Fibre Channel traffic is not
bull Gigabit Ethernet Ports Traffic on Gigabit Ethernet ports isdisrupted during a downgrade This includes the GigabitEthernet ports on the MSM-184 module and the MDS 9222iswitch Those nodes that are members of VSANs traversing anFCIP ISL are impacted and a fabric reconfiguration occursiSCSI initiators connected to the Gigabit Ethernet ports loseconnectivity to iSCSI targets while the downgrade is inprogress
20 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
bull FICON If you have FICON enabled the downgrade path isdifferent See Table 10 on page 21
Note A downgrade from NX-OS Release 4x to SAN-OS Release 33(1c) is notsupported on MDS switches when FC-Redirect based applications such asData Mobility Manager or Storage Media Encryption are configured in thefabric if either of the following conditions are satisfied
1 A target for which FC-Redirect is configured is connected locally and thereare Generation 1 modules with ISLs configured in the switch
2 A host for which FC-redirect is configured is connected locally ona Generation 1 module
If these conditions exist remove the application configuration forthese targets and hosts before proceeding with the downgrade
Use Table 9 on page 20 to determine the nondisruptive downgradepath from Cisco NX-OS Release 50(4b) Find the NX-OS or SAN-OSimage you want to downgrade to in the To SAN-OSNX-OS Releasecolumn of the table and use the path recommended
Note The software downgrade information in Table 10 on page 21 appliesonly to Fibre Channel switching traffic Downgrading system softwaredisrupts IP and SSM intelligent services traffic
Table 9 Nondisruptive Downgrade Path from NX-OS Release 50(4b) (page 1 of2)
To SAN-OS NX-OSRelease Nondisruptive Downgrade Path
NX-OS 50(4) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 50(1a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(7b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(5) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(3) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(1b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(1a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 41(3a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
21
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Use Table 10 to determine your nondisruptive downgrade path if youhave FICON enabled from Cisco NX-OS Release 42(7b) Find the imagerelease number you are currently using in the Current Release withFICON Enabled column of the table and use the path recommended
NX-OS 41(1b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
SAN-OS 33(5a) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33())
SAN-OS 33(5) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(4a) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
NX-OS 33(4) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(3) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
NX-OS 33(2) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(1c) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 32(3a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 32(x)
SAN-OS 32(2c) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 32(x)
SAN-OS 32(1a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
SAN-OS 31(3a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
SAN-OS 31(2) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
Table 9 Nondisruptive Downgrade Path from NX-OS Release 50(4b) (page 2 of2)
To SAN-OS NX-OSRelease Nondisruptive Downgrade Path
Table 10 FICON Downgrade Path from NX-OS Release 42(7b)
To SAN-OSNX-OS Release withFICON Enabled Downgrade Path
NX-OS 42(1b) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
NX-OS 41(1c) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
SAN-OS 33(1c) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
22 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Best practicesLog messages are not saved across system reboots or power outagesTherefore EMC recommends that customers configure a SyslogServer in order to redirect and capture all log messages on a remoteserver For more information please refer to the Cisco MDS 9000Family Configuration Guide available at
httpwwwciscocomenUSproductsps5989products_support_series_homehtml
Maximum ports per chassisTable 11 shows the maximum ports per chassis
a V2 indicates a 9506 or 9509 with Generation-2 Supervisors The presence of anygeneration one module in a switch will limit the maximum port count to 252This includes the 16-port 32-port 14+2 IPS4 and IPS8 cards
Known problems and limitationsFor a list of problems with this release please refer to the CiscoRelease notes located at
httpwwwciscocomenUSproductsps5989prod_release_notes_listhtml
Limitations and restrictionsThe following limitations and restrictions apply to all switches in theCisco MDS 9000 Family unless a limitation for a specific switch isstated
ldquoStorage Media Encryption (SME) limitationsrdquo on page 24
Table 11 Maximum ports per chassis
Chassis Maximum number of ports
MDS 9506-V2 192a
MDS 9509-V2 336
MDS 9513 528
23
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
ldquoSME configuration limitsrdquo on page 24
ldquoDeleting Cisco SME interfacesrdquo on page 25
ldquoCisco MDS 9124 and 9134 Multilayer fabric switchesrdquo on page 25
ldquoN-Port virtualization configuration limitsrdquo on page 25
ldquoMaximum number of zones supported in Interop Mode 4rdquo onpage 25
ldquoIPv6rdquo on page 26
ldquoIP-ACL supportrdquo on page 26
ldquoUser Rolesrdquo on page 26
ldquoUsing a RSA Version 1 Key for SSH Following an Upgraderdquo onpage 27
ldquoApplying Zone Configurations to VSAN 1rdquo on page 27
ldquoInterVSAN Routingrdquo on page 28
ldquoRSPAN Traffic Not Supported on CTS Ports on 8-GbpsSwitching Modulesrdquo on page 28
ldquoIO Accelerator Feature Limitationsrdquo on page 28
ldquoSupport for FCIP Compression Modesrdquo on page 28
ldquoSaving Copies of the Running Kickstart and System Imagesrdquo onpage 29
ldquoConfiguring Buffer Credits on a Generation 2 or Generation 3Modulerdquo on page 29
ldquoStorage services module power budgetrdquo on page 29
ldquoiSCSI proxy initiator in Celerra HighRoad environmentsrdquo onpage 30
ldquoHPUX N_port IDrdquo on page 30
ldquoInteroperability limitationsrdquo on page 31
ldquoNASBrdquo on page 31
ldquoReserved VSAN Range and Isolated VSAN Range Guidelinesrdquoon page 31
ldquoSymmetrix VMax limitationsrdquo on page 32
ldquoStorage Applications on the MSM-184rdquo on page 32
ldquoDowngrading with fport-channel-trunk enabledrdquo on page 32
ldquoLDAP Authenticationrdquo on page 33
24 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
ldquoMDS-9148 limitationsrdquo on page 33
Storage Media Encryption (SME) limitationsAn SME node can only belong to one cluster Adding the node tomore than one cluster will cause problems
Currently there is no prevention or warning in place when an attemptis made to add a node to multiple clusters
SME configuration limitsTable 12 lists the SME configuration limits for this release
Table 12 SME configuration limits
Configuration Limits
Number of switches in the fabric 10
Number of clusters per switch 1
Switches in a cluster 4
Fabrics in a cluster 2
Modules in a switch 11
Cisco MSM-184 modules in a cluster 32
Initiator-Target-LUNs (ITLs) 1024
LUNs behind a target 32
Host and target ports in a cluster 128
Number of hosts per target 128
Tape backup groups per cluster 2
Volume groups in a tape backup group 4
Cisco Key Management Center ( of keys) 32K
Targets per switch that can be FC-redirected 32
25
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Deleting Cisco SME interfacesA Cisco SME interface can be deleted from the cluster only after theinterface is administratively shut-down and all related tasksassociated with the interface shut-down are complete
Cisco MDS 9124 and 9134 Multilayer fabric switchesThe Cisco MDS 9124 and 9134 Multilayer fabric switches do notsupport the following Cisco MDS SAN-OS features
IVR Remote Span Translative loop support FCCmdash no generation quench reaction only
In addition the following features have these limits
VSANs mdash 16 maximum SPAN mdash 1 session maximum
N-Port virtualization configuration limitsThe NPV features have maximum configuration limits Table 13shows the verified and maximum limits for the NPV switchesrunning NX-OS Release 5x
Maximum number of zones supported in Interop Mode 4In interop mode 4 the maximum number of zones that is supportedin an active zone set is 2047 due to limitations in the connectedvendor switch When IVR is used in interop mode 4 the maximumnumber of zones supported including IVR zones in the active zoneset is 2047 The limit for the maximum number of IVR zones perVSAN is 250 zones (two members per zone)
Table 13 NPV features limitations
Feature Verified limits Maximum limits
FLOGIs or F Disc per NPV port group 114 114
NPV switches per NPV core switch 105 105
FLOGIs per line card on NPV core switch 400 400
26 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
IPv6The management port on Cisco MDS switches supports oneuser-configured IPv6 address but does not supportauto-configuration of an IPv6 address
IP-ACL supportDo not apply IP-ACLs to only one member of a PortChannel groupApply IP-ACLs to the entire channel group
If IP-ACLs are already configured in a Gigabit Ethernet interface youcannot add this interface to a Ethernet PortChannel group
Refer to the Cisco MDS 9000 Family Configuration Guide
User RolesIn SAN-OS Release 33(x) and earlier when a user belongs to a rolewhich has a VSAN policy set to Deny and the role allows access to aspecific set of VSANs (for example 1 through 10) the user isrestricted from performing the configuration clear execute anddebug commands which had a VSAN parameter outside thisspecified set Beginning with NX-OS Release 41(1b) these users arestill prevented from performing configuration clear execute anddebug commands as before however they are allowed to performshow commands for all VSANs The ability to execute the showcommand addresses the following
In a network environment users often need to view informationin other VSANs even though they do not have permission tomodify configurations in those VSANs
This behavior makes Cisco MDS 9000 Series switches consistentwith other Cisco products such as Cisco Nexus 7000 Seriesswitches that exhibit the same behavior for those roles (whenthey apply to the VLAN policy)
27
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Using a RSA Version 1 Key for SSH Following an UpgradeFor security reasons NX-OS Release 42(x) and higher does notsupport RSA version 1 keys As a result if you upgrade from anearlier version that did support RSA version 1 keys and you hadconfigured a RSA version 1 key for SSH then you will not be able tolog in through SSH following the upgrade
If you have a RSA version 1 key configured for SSH beforeupgrading to NX-OS Release 42(x) or higher follow these steps
1 Disable SSH
2 Create RSA version 2 DSA keys
3 Enable SSH
4 Delete any RSA version 1 keys on any remote SSH clients andreplace the version 1 keys with the new version 2 keys from theswitch
Proceed with the upgrade to NX-OS Release 42(x) or higher
If you upgrade before disabling SSH and creating RSA version 2 keysfollow these steps
1 Open a Telnet session and log in through the console
2 Issue the no feature ssh command to disable SSH
3 Issue the ssh key rsa 1024 command to create RSA version 2 keys
4 Issue the feature ssh command to enable SSH
Applying Zone Configurations to VSAN 1In the setup script you can configure system default values for thedefault-zone to be permit or deny and you can configure defaultvalues for the zone distribution method and for the zone mode
These default settings are applied when a new VSAN is createdHowever the settings will not take effect on VSAN 1 because it existsprior to running the setup script Therefore when you need thosesettings for VSAN 1 you must explicitly issue the followingcommands
zone default-zone permit vsan 1 zoneset distribute full vsan 1 zone mode enhanced vsan 1
28 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
InterVSAN RoutingWhen using InterVSAN Routing (IVR) it is recommended to enableCisco Fabric Services (CFS) on all IVR-enabled switches Failure to doso may cause mismatched active zone sets if an error occurs duringzone set activation
RSPAN Traffic Not Supported on CTS Ports on 8-Gbps Switching ModulesAn inter-switch link (ISL) that is enabled for Cisco TrustSec (CTS)encryption must be brought up in non-CTS mode to support remoteSPAN (RSPAN) traffic on the following modules
DS-X9248-96K9 Cisco MDS 9000 48-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9224-96K9 Cisco MDS 9000 24-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9248-48K9 Cisco MDS 9000 444-Port Host-Optimized8-Gbps Fibre Channel Switching Module
If the ISL link is brought up with CTS enabled random packets dropsof both RSPAN traffic and normal traffic will occur on the receiverport switch
IO Accelerator Feature LimitationsIOA does not support the following NX-OS features
IVR flows
Devices with NPV and NPIV enabled
F port trunking
bull F port channeling
Support for FCIP Compression ModesIn Cisco NX-OS Release 42(1b) and higher FCIP compression mode 1and compression mode 3 are not supported on the Cisco MSM-184module and on the SSN-16 module
29
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Saving Copies of the Running Kickstart and System ImagesAfter you upgrade to MDS NX-OS Release 42(1b) or higher you arenot allowed to delete rename move or overwrite the kickstart andsystem images that are in the current system bootvar settings on anactive or standby MDS Supervisor-2 module on any Cisco MDS 9500Series switch This restriction does not apply to the integratedsupervisor module on the MDS 9200 and MDS 9100 series switches
Configuring Buffer Credits on a Generation 2 or Generation 3 ModuleWhen you configure port mode to auto or E on a Generation 2module one of the ports will not come up for the followingconfiguration
Port Mode auto or E for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E on a Generation 3module one or two of the ports will not come up for the followingconfiguration
Port Mode auto or E for the first half of the ports the second halfof the ports or for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E for all ports in the globalbuffer pool you need to reconfigure buffer credits on one or more ofthe ports The total number of buffer credits configured for all theports in the global buffer pool should be reduced by 64
Storage services module power budgetThe MDS 9509 does not have the power budget to run seven SSMcards EMC recommends a maximum of four SSMs in one 9509Customers wishing to use more than four SSMs in one chassis shouldrefer to the Cisco MDS 9000 documentation on the Ciscocom websiteto validate that there is enough power available for their desiredconfiguration
30 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Note Upgrading to the 3000 watt power supplies will alleviate thiscondition
iSCSI proxy initiator in Celerra HighRoad environmentsEMC supports the iSCSI proxy initiator feature in Celerrareg
HighRoadreg environments In proxy initiator mode one Fibre Channelinitiator is used for all iSCSI clients who access the switch via thesame iSCSI interface (iscsi33 for example)
The initiators will use the PWWN assigned to the iSCSI interface TheiSCSI interface to which an iSCSI client will logon to is configured inthe client and must be permitted by the virtual target configured forthat initiator
The current session environment supported on the MDS is
300 sessions per port 1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no InitialR2T=yes
Refer to the specific initiator support documentation on how to setthe parameters The implementation will not perform properly ifthese bits are not set
Refer to the MDS documentation for more information regarding theconfiguration of the iSCSI proxy initiator at the following Ciscowebsite
httpwwwciscocomenUSproducts
HPUX N_port IDThe N_port ID port value of 255 (0xFF) has special meaning forHP-UX A N_port ID (FC_ID) can not be returned from a switch thatcontains this value for the N_port ID (FC_ID) port value for a HP-UXinitiator or HP-UX target port Port ID value of 255 (0xFF) cannot be
31
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
configured for HP-UX initiator port and HP-UX target ports whenconfiguring MDS FC_IDs The port_ID value is the third byte of theFC_ID
Interoperability limitationsRefer to the EMC Support Matrix (ESM) and the EMC Networked Storage Topology Guide for modes of operation and caveats
NASBThe NASB feature requires that the backup application load the tapedrive with a compatible tape cartridge prior to configuring NASB inthe backup VSAN
Reserved VSAN Range and Isolated VSAN Range GuidelinesOn an NPV switch with a trunking configuration on any interface or ona regular switch where the feature fport_channel_trunk command hasbeen issued to enable the F PortChannel feature follow theseconfiguration guidelines for reserved VSANs and the isolated VSAN
bull If trunk mode is on for any of the interfaces or NP PortChannelis up the reserved VSANs are 3040 to 4078 and they are notavailable for user configuration
bull The Exchange Virtual Fabric Protocol (EVFP) isolated VSAN is4079 and it is not available for user configuration
bull VSAN 4079 will be impacted by an upgrade to NX-OS Release42(3) depending on whether or not VSAN 4079 was createdprior to the upgrade See theldquoUpgrading Effect on VSAN 4079rdquoon page 17
The following VSAN IDs are assigned in the Fibre Channel Framingand Signaling (FC-FS) interface standard
VF_ID Value Value Description
00h Do not use as a Virtual FabricIdentifier
001h EFFh Available as a Virtual FabricIdentifier
F00h FEEh Reserved
32 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Symmetrix VMax limitationsAt the time of this writing the following features are not supportedfor use with the Symmetrix VMax
FCIP Write Acceleration
The NX-OS IOA functionality is only supported with the Q2 SREnginuity release 5874229182 or higher
For the most up to date status please refer to the current revision ofthese Release Notes on httpPowerlinkemccom and the EMCSupport Matrix available through E-Lab Interoperability Navigator (ELN) athttpelabnavigatorEMCcom
Storage Applications on the MSM-184The MDS 9000 184-Port Multiservice Module (MSM-184) does notsupport multiple concurrent storage applications Only oneapplication can run on the MSM-184 at a time
Downgrading with fport-channel-trunk enabledIf you are running MDS NX-OS Release 42(x) or higher with thefport-channel-trunk feature enabled and you downgrade to anyNX-OS 41(1x) release the installer performs a nondisruptivedowngrade even though the fport-channel-trunk feature is notsupported in NX-OS 41(1x) releases
As a result the switch is in an inconsistent state and the ports maynot function properly
FEFh Control VF-ID (see FibreChannel Link Services (FC-LS)and Fibre Channel SwitchFabric Generation 4 (FC-SW-4)standards)
FF0h FFEh Vendor specific
FFFh Do not use as a Virtual FabricIdentifier
FEFh = 4079
33
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
If you are in this state a workaround is to reboot the switch followingthe upgrade
LDAP AuthenticationThere is currently a limitation in the LDAP server configuration CLIthat prevents the use of an OU with spaces in the name Normallythese OU names could be surrounded by quotation marks howeverquotation marks are not supported by the ldap-server command
MDS-9148 limitationsThe Cisco MDS 9148 Multilayer Fabric Switch does not support thefollowing NX-OS features
Medium and Long range 4GB Agilent
IVR
Remote Span
Translative loop support
FCC - no generation quench reaction only
FC-Redirect
In addition the following features have these limits
VSANS - 31 maximum
SPAN - 1 session maximum
Technical notesThe following sections provide further information on technicalnotes
EMC Email Home for Cisco MDS switchesInstallation and Trouble shooting instructions can be found in thedocumentation located at the EMC Customer Service Internalwebsite
httpwwwcsisusemccomcsweb2esnesnhomehtmConnectrix20MDS20900020Family
34 EMC Connectrix MDS 9000 NX-OS Release Notes
Technical notes
Customers requiring installation of this solution should contact theirEMC Customer Engineer to assist with the installation and providethe documentation
Supported iSCSI sessionsThe current iSCSI session environment supported on the MDS is
300 sessions per port
1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no
InitialR2T=yes
Upgrading Cisco SAN-OSThere are several methods available for upgrading SAN-OS SoftwareEMC personnel are strongly recommended that all upgrades be doneby the Automated One-Step Upgrade using the install all
command EMC personnel should refer to the Connectrix MDS 9000Family Software Image Upgrade Instructions for a complete list ofprerequisites and instructions for performing the upgrade Thisdocument along with tftp software is available on the GlobalServices website at httpwwwcsisusEMCcom under ApplicationDownload Area ESN Product Information Connectrix MDS 9000Family
The Software Upgrade Wizard is an option for upgrades While theinstall all is the preferred method the Software Install Wizard canalso be used
Supported configuration parametersFor the most up-to-date information refer to the EMC Support Matrixavailable through E-Lab Interoperability Navigator athttpelabnavigatoremccom for the latest information onsupported configurations
35
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
Supported zoning parametersRefer to the EMC Networked Storage Topology Guide for the mostup-to-date information on supported zoning parameters
At the time these notes were published the following parameterswere supported
20 VSANs 5 Hops 2000 Unique members per physical infrastructure 1000 Zonesets per physical infrastructure 2000 Zones per physical infrastructure 1 FCIP tunnel
Supported IVR parameters IVR zone members 1000 IVR zones 1000 IVR zone sets 32 VSANS 20 IVR enabled switches 64
An RPQ can be submitted for any configurations that exceed thislimit
Managing zone changes in multiswitch fabricsZoning changes may be made through Fabric Manager or CLI Whenaccessing Fabric Manager or CLI the user does so from the point ofview of one switch That is Fabric Manager and CLI are accessed byentering the IP address of one switch in the fabric
When zoning changes are made the applicable VSAN and zone setdata is propagated to the rest of the switches in the fabric via the ISLs
When zoning changes are made to a VSAN the zone set data ispropagated to the rest of the switches in the fabric via the ISLs Bydefault only the active zone set information is relayed to all switchesin the VSAN If the user accesses the Fabric Manager and CLI fromanother switch in the fabric the new VSAN and zone set informationwill not be viewable To view the active and inactive zone set on theother switches in the fabric the user must log in to the CLI and issuea command from the EXEC prompt
36 EMC Connectrix MDS 9000 NX-OS Release Notes
Documentation
Example The following is an example of copying VSAN 1 through 20 zoningdata
CiscoMDS_name zone copy active full vsan 1-20
CiscoMDS_name conf t
Enter configuration commands one per line End with CNTL Z
CiscoMDS_name(config) zoneset distribute full vsan 1-20
CiscoMDS_name(config)
Note This command needs to be issued on all switches in the fabric one timeonly
This is a nondisruptive command After issuing the commands theuser will now see the active and inactive zone sets for the specifiedVSANs on any switch that is chosen from which to manage the fabric
After a zoning change is made save the running configuration to thestartup configuration
DocumentationSend documentation comments to mdsfeedback-doccom
Product DocumentationAs of NX-OS Release 42(1a) software configuration information isavailable in new feature-specific configuration guides for thefollowing information
System management
Interfaces
Fabric
Quality of service
Security
IP services
High availability and redundancy
37
Software media organization and files
EMC Connectrix MDS 9000 NX-OS Release Notes
The information in these new guides previously existed in the CiscoMDS 9000 Family CLI Configuration Guide That configuration guideremains available on Ciscocom and should be used for all softwarereleases prior to NX-OS Release 42(1a) Configuration guidesaddress the features introduced in or available in a particular releaseSelect and view the configuration guide that pertains to the softwareinstalled in your switch
In addition Fabric Manager information has been removed from theMDS NX-OS Release Notes (this document) and placed intostandalone Fabric Manager Release Notes that support both CiscoMDS 9000 Family switches and Cisco Nexus 5000 Series switchesThe Cisco Fabric Manager Release Notes are available onhttpPowerlinkemccom and from the following website
httpwwwciscocomenUSpartnerproductsps10495prod_release_notes_listhtml
Technical supportThese release notes complement a Cisco documentation set EachCisco document refers to where to get help However for any itemssupplied by EMC see ldquoTroubleshooting and getting helprdquo onpage 38
Software media organization and filesFor information on related software environment and systemrequirements refer to the EMC Support Matrix on EMC Powerlink at
httpPowerlinkEMCcom
InstallationFor hardware installation information refer to the Cisco MDS HWInstallation Guides available at Ciscocom
For EMC-specific installation information refer to ldquoEnvironment andsystem requirementsrdquo on page 5 in this document
38 EMC Connectrix MDS 9000 NX-OS Release Notes
Troubleshooting and getting help
Troubleshooting and getting helpEMC support product and licensing information can be obtained asfollows
Product information mdash For documentation release notes softwareupdates or for information about EMC products licensing andservice go to the EMC Powerlink website (registration required) at
httpPowerlinkEMCcom
Technical support mdash For technical support go to EMC CustomerService on Powerlink To open a service request through Powerlinkyou must have a valid support agreement Please contact your EMCsales representative for details about obtaining a valid supportagreement or to answer any questions about your account
Copyright copy 2011 EMC Corporation All rights reserved
EMC believes the information in this publication is accurate as of its publication date The information issubject to change without notice
THE INFORMATION IN THIS PUBLICATION IS PROVIDED ldquoAS ISrdquo EMC CORPORATION MAKES NOREPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION INTHIS PUBLICATION AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OFMERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Use copying and distribution of any EMC software described in this publication requires an applicablesoftware license
For the most up-to-date regulatory document for your product line go to the Technical Documentation andAdvisories section on EMC Powerlink
For the most up-to-date listing of EMC product names see EMC Corporation Trademarks on EMCcom
All other trademarks used herein are the property of their respective owners
13
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Selecting the Correct Software Image for an MDS 9200 Series SwitchThe system and kickstart image that you use for an MDS 9200 seriesswitch depends on which switch you use as shown in Table 5
Selecting the Correct Software Image for an MDS 9500 Series SwitchThe system and kickstart image that you use for an MDS 9500 Seriesswitch depends on whether the switch is based on a Supervisor-1module or a Supervisor-2 module as shown in Table 6
Use the show module command to display the type of supervisormodule in the switch The following is sample output from the showmodule command on a Supervisor 2 module
Table 5 Software Images for MDS 9200 Series Switches
Cisco MDS 9200 Series Switch Type Naming Convention
9222i Filename begins with m9200-s2ek9
Table 6 Software Images for Supervisor Type
Cisco MDS 9500 Series Switch Type Supervisor Module Type Naming Convention
9513 9509 and 9506 Supervisor-2 module Filename begins with m9500-sf2ek9
14 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
switch show moduleMod Ports Module-Type Model Status--- ----- -------------------------------- ------------------ ------------7 0 SupervisorFabric-2 DS-X9530-SF2-K9 active 8 0 SupervisorFabric-2 DS-X9530-SF2-K9 ha-standby
Upgrading Your Cisco MDS NX-OS Software ImageThis section lists the guidelines recommended for upgrading yourCisco MDS NX-OS software image and includes the following topics
ldquoGeneral Upgrading Guidelinesrdquo on page 14
ldquoDowngrading Your Cisco MDS SAN-OS Software Imagerdquo onpage 18
Note Before you begin the upgrade process review the list of chassis andmodules that NX-OS Release 50(4b) supports See the ldquoMDS 9000 Chassisand Module Support in Cisco MDS NX-OS 5xrdquo on page 8
Note For detailed instructions for performing a software upgrade usingCisco Fabric Manager see the Cisco Fabric Manager Release Notes forRelease 50(4b) which is available from the following websitehttpPowerlinkEMCcom
General Upgrading Guidelines
Note To upgrade to NX-OS Release 50(4b) you must be running NX-OSRelease 4x If you are running SAN-OS Release 32(3a) or earlier firstupgrade to SAN-OS Release 33(x) then NX-OS Release 4x and thenupgrade to NX-OS Release 50(4b)
Use the following guidelines when upgrading to Cisco MDS NX-OSRelease 5x
Install and configure dual supervisor modules
Issue the show install all impact upgrade-image CLI command todetermine if your upgrade will be nondisruptive
15
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Be aware of the impact of an upgrade on VSAN 4079 if you areupgrading from SAN-OS Release 3x to NX-OS 50(4b) See theldquoUpgrading Effect on VSAN 4079rdquo on page 17
Follow the recommended guidelines for upgrading a Cisco MDS9124 or MDS 9134 Switch as described in ldquoUpgrading a CiscoMDS 9124 or MDS 9134 switchrdquo on page 18
Take note of the affect of upgrades on MDS 9500 series switchesthat have active IOA flows as described in ldquoMDS 9500 seriesupgrades with active IOA flowsrdquo on page 18
Be aware that some features impact whether an upgrade isdisruptive or nondisruptive
bull Fibre Channel Ports Traffic on Fibre Channel ports can benondisruptively upgraded See Table 7 on page 16 for thenondisruptive upgrade path for all NX-OS and SAN-OSreleases
bull Storage Services Intelligent storage services traffic such asSANTap NASB and FC write acceleration is disruptedduring an upgrade Fibre Channel traffic is not
bull Gigabit Ethernet Ports Traffic on Gigabit Ethernet ports isdisrupted during an upgrade or downgrade This includes theGigabit Ethernet ports on the MSM-184 module and the MDS9222i switch Those nodes that are members of VSANs traversingan FCIP ISL are impacted and a fabric reconfiguration occursiSCSI initiators connected to the Gigabit Ethernet ports loseconnectivity to iSCSI targets while the upgrade is in progress
bull FICON If you have FICON enabled the upgrade path isdifferent See Table 6 on page 13
Use Table 7 to determine your nondisruptive upgrade path to Cisco MDSNX-OS Release 50(4b) find the image release number you are currentlyusing in the Current column of the table and use the path recommended
16 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Note The software upgrade information in Table 7 applies only to FibreChannel switching traffic Upgrading system software disrupts IP traffic andSSM intelligent services traffic
MDS NX-OS Release 50(4b) is not a FICON-qualified release
Table 7 Nondisruptive Upgrade Path to Cisco MDS NX-OS Release 50(4b)
Current Nondisruptive Upgrade Path
NX-OS 50(4) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 50(1a) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(7b) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(5) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(3) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(1b) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(1a) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 41(3a) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 41(1b) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
SAN-OS 33(4a) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
NX-OS 33(4) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 33(3) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 33(2) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 33(1c) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 32(3a) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 32(2c) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 32(1a) Upgrade to SAN-OS Release then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 31(3a) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 31(2) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
17
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Use Table 8 to determine your FICON nondisruptive upgrade path toCisco MDS NX-OS Release 42(7b) Find the image release numberyou are currently using in the Current Release with FICON Enabledcolumn of the table and use the path recommended
Note For more information on the FICON qualified NX-OS releases refer tothe EMC Support Matrix available through E-Lab Interoperability Navigator(ELN) at httpelabnavigatorEMCcom
Upgrading Effect on VSAN 4079If you are upgrading to NX-OS Release 50(4b) and you have notcreated VSAN 4079 the NX-OS software will automatically createVSAN 4079 and reserve it for EVFP use If VSAN 4079 is reserved forEVFP use the switchport trunk allowed vsan command will filterout VSAN 4079 from the allowed list as shown in the followingexample
switch(config-if) switchport trunk allowed vsan1-40801-40784080switch(config-if)
If you have created VSAN 4079 the upgrade to NX-OS Release50(4b) will have no affect on VSAN 4079
If you downgrade to a release of NX-OS lower than 41(x) afterNX-OS Release 50(4b) creates VSAN 4079 and reserves it for EVFPuse the VSAN will no longer be reserved
Table 8 FICON Nondisruptive Upgrade Path to NX-OS Release 42(7b)
Current Release withFICON Enabled Upgrade Path
NX-OS 42(1b) You can nondisruptively upgrade directly to NX-OS Release 42(7b)
NX-OS 41(1c) You can nondisruptively upgrade directly to NX-OS Release 42(7b)
SAN-OS 33(1c) You can nondisruptively upgrade directly to NX-OS Release 42(7b)
18 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Upgrading a Cisco MDS 9124 or MDS 9134 switchIf you are upgrading from Cisco MDS SAN-OS Release 31(1) to CiscoNX-OS Release 4x before upgrading to NX-OS Release 50(4b) on aCisco MDS 9124 or MDS 9134 switch follow these guidelines
During the upgrade configuration is not allowed and the fabric isexpected to be stable
The Fabric Shortest Path First (FSPF) timers must be configured tothe default value of 20 seconds otherwise the nondisruptiveupgrade is blocked to ensure that the maximum down toim forthe control plane can be 80 seconds
If there are any CFS commits in the fabric the nondisruptiveupgrade will fail
If there is a zone server merge in progress in the fabric thenondisruptive upgrde will fail
If a service terminates the nondisruptive upgrade the showinstall all failure-reason command can display the reason thatthe nondisruptive upgrade cannot proceed
If there is not enough memory in the system to load the newimages the upgrade will be made disruptive due to insufficientresources and the user will be notified in the compativility table
MDS 9500 series upgrades with active IOA flowsWhen upgading an MDS 9500 series switch that has active IOA flowsthose flows may be interrupted during the supervisor moduleswitchover To workaround this issue you have to enablespanning-tree portfast on the interface on the catalyst connected tothe management interface of the activestandby supervisor for theinterface to come up fast without causing the cluster to lose quorum
Downgrading Your Cisco MDS SAN-OS Software ImageThis section lists the guidelines recommended for downgrading yourCisco MDS SAN-OS software image and includes the followingtopics
ldquoGeneral downgrading guidelinesrdquo on page 19
19
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
General downgrading guidelinesUse the following guidelines to nondisruptively downgrade yourCisco MDS NX-OS Release 50(4b)
Install and configure dual supervisor modules
Issue the system no acl-adjacency-sharing execute command todisable acl adjacency usage on Generation 2 and Generation 1modules If this command fails reduce the number of zones IVRzones TE ports or a combination of these in the system and issuethe command again
Disable all features not supported by the downgrade release Usethe show incompatibility system downgrade-image command todetermine what you need to disable
bull If you are running in interoperability mode two such featuresare the Reliable Commit Service and Full Zone DatabaseDistribution They can be disabled by running thesecommand in config term mode
no zone rcs enableno zoneset capability distribute full
Use the show install all impact downgrade-image command todetermine if your downgrade will be nondisruptive
Be aware that some features impact whether a downgrade isdisruptive or nondisruptive
bull Fibre Channel Ports Traffic on Fibre Channel ports can benondisruptively downgraded See Table 9 on page 20 for thenondisruptive downgrade path for all SAN-OS releases
bull Storage Services Intelligent storage services traffic such asSANTap NASB and FC write acceleration is disruptedduring a downgrade Fibre Channel traffic is not
bull Gigabit Ethernet Ports Traffic on Gigabit Ethernet ports isdisrupted during a downgrade This includes the GigabitEthernet ports on the MSM-184 module and the MDS 9222iswitch Those nodes that are members of VSANs traversing anFCIP ISL are impacted and a fabric reconfiguration occursiSCSI initiators connected to the Gigabit Ethernet ports loseconnectivity to iSCSI targets while the downgrade is inprogress
20 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
bull FICON If you have FICON enabled the downgrade path isdifferent See Table 10 on page 21
Note A downgrade from NX-OS Release 4x to SAN-OS Release 33(1c) is notsupported on MDS switches when FC-Redirect based applications such asData Mobility Manager or Storage Media Encryption are configured in thefabric if either of the following conditions are satisfied
1 A target for which FC-Redirect is configured is connected locally and thereare Generation 1 modules with ISLs configured in the switch
2 A host for which FC-redirect is configured is connected locally ona Generation 1 module
If these conditions exist remove the application configuration forthese targets and hosts before proceeding with the downgrade
Use Table 9 on page 20 to determine the nondisruptive downgradepath from Cisco NX-OS Release 50(4b) Find the NX-OS or SAN-OSimage you want to downgrade to in the To SAN-OSNX-OS Releasecolumn of the table and use the path recommended
Note The software downgrade information in Table 10 on page 21 appliesonly to Fibre Channel switching traffic Downgrading system softwaredisrupts IP and SSM intelligent services traffic
Table 9 Nondisruptive Downgrade Path from NX-OS Release 50(4b) (page 1 of2)
To SAN-OS NX-OSRelease Nondisruptive Downgrade Path
NX-OS 50(4) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 50(1a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(7b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(5) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(3) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(1b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(1a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 41(3a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
21
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Use Table 10 to determine your nondisruptive downgrade path if youhave FICON enabled from Cisco NX-OS Release 42(7b) Find the imagerelease number you are currently using in the Current Release withFICON Enabled column of the table and use the path recommended
NX-OS 41(1b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
SAN-OS 33(5a) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33())
SAN-OS 33(5) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(4a) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
NX-OS 33(4) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(3) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
NX-OS 33(2) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(1c) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 32(3a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 32(x)
SAN-OS 32(2c) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 32(x)
SAN-OS 32(1a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
SAN-OS 31(3a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
SAN-OS 31(2) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
Table 9 Nondisruptive Downgrade Path from NX-OS Release 50(4b) (page 2 of2)
To SAN-OS NX-OSRelease Nondisruptive Downgrade Path
Table 10 FICON Downgrade Path from NX-OS Release 42(7b)
To SAN-OSNX-OS Release withFICON Enabled Downgrade Path
NX-OS 42(1b) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
NX-OS 41(1c) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
SAN-OS 33(1c) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
22 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Best practicesLog messages are not saved across system reboots or power outagesTherefore EMC recommends that customers configure a SyslogServer in order to redirect and capture all log messages on a remoteserver For more information please refer to the Cisco MDS 9000Family Configuration Guide available at
httpwwwciscocomenUSproductsps5989products_support_series_homehtml
Maximum ports per chassisTable 11 shows the maximum ports per chassis
a V2 indicates a 9506 or 9509 with Generation-2 Supervisors The presence of anygeneration one module in a switch will limit the maximum port count to 252This includes the 16-port 32-port 14+2 IPS4 and IPS8 cards
Known problems and limitationsFor a list of problems with this release please refer to the CiscoRelease notes located at
httpwwwciscocomenUSproductsps5989prod_release_notes_listhtml
Limitations and restrictionsThe following limitations and restrictions apply to all switches in theCisco MDS 9000 Family unless a limitation for a specific switch isstated
ldquoStorage Media Encryption (SME) limitationsrdquo on page 24
Table 11 Maximum ports per chassis
Chassis Maximum number of ports
MDS 9506-V2 192a
MDS 9509-V2 336
MDS 9513 528
23
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
ldquoSME configuration limitsrdquo on page 24
ldquoDeleting Cisco SME interfacesrdquo on page 25
ldquoCisco MDS 9124 and 9134 Multilayer fabric switchesrdquo on page 25
ldquoN-Port virtualization configuration limitsrdquo on page 25
ldquoMaximum number of zones supported in Interop Mode 4rdquo onpage 25
ldquoIPv6rdquo on page 26
ldquoIP-ACL supportrdquo on page 26
ldquoUser Rolesrdquo on page 26
ldquoUsing a RSA Version 1 Key for SSH Following an Upgraderdquo onpage 27
ldquoApplying Zone Configurations to VSAN 1rdquo on page 27
ldquoInterVSAN Routingrdquo on page 28
ldquoRSPAN Traffic Not Supported on CTS Ports on 8-GbpsSwitching Modulesrdquo on page 28
ldquoIO Accelerator Feature Limitationsrdquo on page 28
ldquoSupport for FCIP Compression Modesrdquo on page 28
ldquoSaving Copies of the Running Kickstart and System Imagesrdquo onpage 29
ldquoConfiguring Buffer Credits on a Generation 2 or Generation 3Modulerdquo on page 29
ldquoStorage services module power budgetrdquo on page 29
ldquoiSCSI proxy initiator in Celerra HighRoad environmentsrdquo onpage 30
ldquoHPUX N_port IDrdquo on page 30
ldquoInteroperability limitationsrdquo on page 31
ldquoNASBrdquo on page 31
ldquoReserved VSAN Range and Isolated VSAN Range Guidelinesrdquoon page 31
ldquoSymmetrix VMax limitationsrdquo on page 32
ldquoStorage Applications on the MSM-184rdquo on page 32
ldquoDowngrading with fport-channel-trunk enabledrdquo on page 32
ldquoLDAP Authenticationrdquo on page 33
24 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
ldquoMDS-9148 limitationsrdquo on page 33
Storage Media Encryption (SME) limitationsAn SME node can only belong to one cluster Adding the node tomore than one cluster will cause problems
Currently there is no prevention or warning in place when an attemptis made to add a node to multiple clusters
SME configuration limitsTable 12 lists the SME configuration limits for this release
Table 12 SME configuration limits
Configuration Limits
Number of switches in the fabric 10
Number of clusters per switch 1
Switches in a cluster 4
Fabrics in a cluster 2
Modules in a switch 11
Cisco MSM-184 modules in a cluster 32
Initiator-Target-LUNs (ITLs) 1024
LUNs behind a target 32
Host and target ports in a cluster 128
Number of hosts per target 128
Tape backup groups per cluster 2
Volume groups in a tape backup group 4
Cisco Key Management Center ( of keys) 32K
Targets per switch that can be FC-redirected 32
25
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Deleting Cisco SME interfacesA Cisco SME interface can be deleted from the cluster only after theinterface is administratively shut-down and all related tasksassociated with the interface shut-down are complete
Cisco MDS 9124 and 9134 Multilayer fabric switchesThe Cisco MDS 9124 and 9134 Multilayer fabric switches do notsupport the following Cisco MDS SAN-OS features
IVR Remote Span Translative loop support FCCmdash no generation quench reaction only
In addition the following features have these limits
VSANs mdash 16 maximum SPAN mdash 1 session maximum
N-Port virtualization configuration limitsThe NPV features have maximum configuration limits Table 13shows the verified and maximum limits for the NPV switchesrunning NX-OS Release 5x
Maximum number of zones supported in Interop Mode 4In interop mode 4 the maximum number of zones that is supportedin an active zone set is 2047 due to limitations in the connectedvendor switch When IVR is used in interop mode 4 the maximumnumber of zones supported including IVR zones in the active zoneset is 2047 The limit for the maximum number of IVR zones perVSAN is 250 zones (two members per zone)
Table 13 NPV features limitations
Feature Verified limits Maximum limits
FLOGIs or F Disc per NPV port group 114 114
NPV switches per NPV core switch 105 105
FLOGIs per line card on NPV core switch 400 400
26 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
IPv6The management port on Cisco MDS switches supports oneuser-configured IPv6 address but does not supportauto-configuration of an IPv6 address
IP-ACL supportDo not apply IP-ACLs to only one member of a PortChannel groupApply IP-ACLs to the entire channel group
If IP-ACLs are already configured in a Gigabit Ethernet interface youcannot add this interface to a Ethernet PortChannel group
Refer to the Cisco MDS 9000 Family Configuration Guide
User RolesIn SAN-OS Release 33(x) and earlier when a user belongs to a rolewhich has a VSAN policy set to Deny and the role allows access to aspecific set of VSANs (for example 1 through 10) the user isrestricted from performing the configuration clear execute anddebug commands which had a VSAN parameter outside thisspecified set Beginning with NX-OS Release 41(1b) these users arestill prevented from performing configuration clear execute anddebug commands as before however they are allowed to performshow commands for all VSANs The ability to execute the showcommand addresses the following
In a network environment users often need to view informationin other VSANs even though they do not have permission tomodify configurations in those VSANs
This behavior makes Cisco MDS 9000 Series switches consistentwith other Cisco products such as Cisco Nexus 7000 Seriesswitches that exhibit the same behavior for those roles (whenthey apply to the VLAN policy)
27
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Using a RSA Version 1 Key for SSH Following an UpgradeFor security reasons NX-OS Release 42(x) and higher does notsupport RSA version 1 keys As a result if you upgrade from anearlier version that did support RSA version 1 keys and you hadconfigured a RSA version 1 key for SSH then you will not be able tolog in through SSH following the upgrade
If you have a RSA version 1 key configured for SSH beforeupgrading to NX-OS Release 42(x) or higher follow these steps
1 Disable SSH
2 Create RSA version 2 DSA keys
3 Enable SSH
4 Delete any RSA version 1 keys on any remote SSH clients andreplace the version 1 keys with the new version 2 keys from theswitch
Proceed with the upgrade to NX-OS Release 42(x) or higher
If you upgrade before disabling SSH and creating RSA version 2 keysfollow these steps
1 Open a Telnet session and log in through the console
2 Issue the no feature ssh command to disable SSH
3 Issue the ssh key rsa 1024 command to create RSA version 2 keys
4 Issue the feature ssh command to enable SSH
Applying Zone Configurations to VSAN 1In the setup script you can configure system default values for thedefault-zone to be permit or deny and you can configure defaultvalues for the zone distribution method and for the zone mode
These default settings are applied when a new VSAN is createdHowever the settings will not take effect on VSAN 1 because it existsprior to running the setup script Therefore when you need thosesettings for VSAN 1 you must explicitly issue the followingcommands
zone default-zone permit vsan 1 zoneset distribute full vsan 1 zone mode enhanced vsan 1
28 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
InterVSAN RoutingWhen using InterVSAN Routing (IVR) it is recommended to enableCisco Fabric Services (CFS) on all IVR-enabled switches Failure to doso may cause mismatched active zone sets if an error occurs duringzone set activation
RSPAN Traffic Not Supported on CTS Ports on 8-Gbps Switching ModulesAn inter-switch link (ISL) that is enabled for Cisco TrustSec (CTS)encryption must be brought up in non-CTS mode to support remoteSPAN (RSPAN) traffic on the following modules
DS-X9248-96K9 Cisco MDS 9000 48-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9224-96K9 Cisco MDS 9000 24-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9248-48K9 Cisco MDS 9000 444-Port Host-Optimized8-Gbps Fibre Channel Switching Module
If the ISL link is brought up with CTS enabled random packets dropsof both RSPAN traffic and normal traffic will occur on the receiverport switch
IO Accelerator Feature LimitationsIOA does not support the following NX-OS features
IVR flows
Devices with NPV and NPIV enabled
F port trunking
bull F port channeling
Support for FCIP Compression ModesIn Cisco NX-OS Release 42(1b) and higher FCIP compression mode 1and compression mode 3 are not supported on the Cisco MSM-184module and on the SSN-16 module
29
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Saving Copies of the Running Kickstart and System ImagesAfter you upgrade to MDS NX-OS Release 42(1b) or higher you arenot allowed to delete rename move or overwrite the kickstart andsystem images that are in the current system bootvar settings on anactive or standby MDS Supervisor-2 module on any Cisco MDS 9500Series switch This restriction does not apply to the integratedsupervisor module on the MDS 9200 and MDS 9100 series switches
Configuring Buffer Credits on a Generation 2 or Generation 3 ModuleWhen you configure port mode to auto or E on a Generation 2module one of the ports will not come up for the followingconfiguration
Port Mode auto or E for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E on a Generation 3module one or two of the ports will not come up for the followingconfiguration
Port Mode auto or E for the first half of the ports the second halfof the ports or for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E for all ports in the globalbuffer pool you need to reconfigure buffer credits on one or more ofthe ports The total number of buffer credits configured for all theports in the global buffer pool should be reduced by 64
Storage services module power budgetThe MDS 9509 does not have the power budget to run seven SSMcards EMC recommends a maximum of four SSMs in one 9509Customers wishing to use more than four SSMs in one chassis shouldrefer to the Cisco MDS 9000 documentation on the Ciscocom websiteto validate that there is enough power available for their desiredconfiguration
30 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Note Upgrading to the 3000 watt power supplies will alleviate thiscondition
iSCSI proxy initiator in Celerra HighRoad environmentsEMC supports the iSCSI proxy initiator feature in Celerrareg
HighRoadreg environments In proxy initiator mode one Fibre Channelinitiator is used for all iSCSI clients who access the switch via thesame iSCSI interface (iscsi33 for example)
The initiators will use the PWWN assigned to the iSCSI interface TheiSCSI interface to which an iSCSI client will logon to is configured inthe client and must be permitted by the virtual target configured forthat initiator
The current session environment supported on the MDS is
300 sessions per port 1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no InitialR2T=yes
Refer to the specific initiator support documentation on how to setthe parameters The implementation will not perform properly ifthese bits are not set
Refer to the MDS documentation for more information regarding theconfiguration of the iSCSI proxy initiator at the following Ciscowebsite
httpwwwciscocomenUSproducts
HPUX N_port IDThe N_port ID port value of 255 (0xFF) has special meaning forHP-UX A N_port ID (FC_ID) can not be returned from a switch thatcontains this value for the N_port ID (FC_ID) port value for a HP-UXinitiator or HP-UX target port Port ID value of 255 (0xFF) cannot be
31
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
configured for HP-UX initiator port and HP-UX target ports whenconfiguring MDS FC_IDs The port_ID value is the third byte of theFC_ID
Interoperability limitationsRefer to the EMC Support Matrix (ESM) and the EMC Networked Storage Topology Guide for modes of operation and caveats
NASBThe NASB feature requires that the backup application load the tapedrive with a compatible tape cartridge prior to configuring NASB inthe backup VSAN
Reserved VSAN Range and Isolated VSAN Range GuidelinesOn an NPV switch with a trunking configuration on any interface or ona regular switch where the feature fport_channel_trunk command hasbeen issued to enable the F PortChannel feature follow theseconfiguration guidelines for reserved VSANs and the isolated VSAN
bull If trunk mode is on for any of the interfaces or NP PortChannelis up the reserved VSANs are 3040 to 4078 and they are notavailable for user configuration
bull The Exchange Virtual Fabric Protocol (EVFP) isolated VSAN is4079 and it is not available for user configuration
bull VSAN 4079 will be impacted by an upgrade to NX-OS Release42(3) depending on whether or not VSAN 4079 was createdprior to the upgrade See theldquoUpgrading Effect on VSAN 4079rdquoon page 17
The following VSAN IDs are assigned in the Fibre Channel Framingand Signaling (FC-FS) interface standard
VF_ID Value Value Description
00h Do not use as a Virtual FabricIdentifier
001h EFFh Available as a Virtual FabricIdentifier
F00h FEEh Reserved
32 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Symmetrix VMax limitationsAt the time of this writing the following features are not supportedfor use with the Symmetrix VMax
FCIP Write Acceleration
The NX-OS IOA functionality is only supported with the Q2 SREnginuity release 5874229182 or higher
For the most up to date status please refer to the current revision ofthese Release Notes on httpPowerlinkemccom and the EMCSupport Matrix available through E-Lab Interoperability Navigator (ELN) athttpelabnavigatorEMCcom
Storage Applications on the MSM-184The MDS 9000 184-Port Multiservice Module (MSM-184) does notsupport multiple concurrent storage applications Only oneapplication can run on the MSM-184 at a time
Downgrading with fport-channel-trunk enabledIf you are running MDS NX-OS Release 42(x) or higher with thefport-channel-trunk feature enabled and you downgrade to anyNX-OS 41(1x) release the installer performs a nondisruptivedowngrade even though the fport-channel-trunk feature is notsupported in NX-OS 41(1x) releases
As a result the switch is in an inconsistent state and the ports maynot function properly
FEFh Control VF-ID (see FibreChannel Link Services (FC-LS)and Fibre Channel SwitchFabric Generation 4 (FC-SW-4)standards)
FF0h FFEh Vendor specific
FFFh Do not use as a Virtual FabricIdentifier
FEFh = 4079
33
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
If you are in this state a workaround is to reboot the switch followingthe upgrade
LDAP AuthenticationThere is currently a limitation in the LDAP server configuration CLIthat prevents the use of an OU with spaces in the name Normallythese OU names could be surrounded by quotation marks howeverquotation marks are not supported by the ldap-server command
MDS-9148 limitationsThe Cisco MDS 9148 Multilayer Fabric Switch does not support thefollowing NX-OS features
Medium and Long range 4GB Agilent
IVR
Remote Span
Translative loop support
FCC - no generation quench reaction only
FC-Redirect
In addition the following features have these limits
VSANS - 31 maximum
SPAN - 1 session maximum
Technical notesThe following sections provide further information on technicalnotes
EMC Email Home for Cisco MDS switchesInstallation and Trouble shooting instructions can be found in thedocumentation located at the EMC Customer Service Internalwebsite
httpwwwcsisusemccomcsweb2esnesnhomehtmConnectrix20MDS20900020Family
34 EMC Connectrix MDS 9000 NX-OS Release Notes
Technical notes
Customers requiring installation of this solution should contact theirEMC Customer Engineer to assist with the installation and providethe documentation
Supported iSCSI sessionsThe current iSCSI session environment supported on the MDS is
300 sessions per port
1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no
InitialR2T=yes
Upgrading Cisco SAN-OSThere are several methods available for upgrading SAN-OS SoftwareEMC personnel are strongly recommended that all upgrades be doneby the Automated One-Step Upgrade using the install all
command EMC personnel should refer to the Connectrix MDS 9000Family Software Image Upgrade Instructions for a complete list ofprerequisites and instructions for performing the upgrade Thisdocument along with tftp software is available on the GlobalServices website at httpwwwcsisusEMCcom under ApplicationDownload Area ESN Product Information Connectrix MDS 9000Family
The Software Upgrade Wizard is an option for upgrades While theinstall all is the preferred method the Software Install Wizard canalso be used
Supported configuration parametersFor the most up-to-date information refer to the EMC Support Matrixavailable through E-Lab Interoperability Navigator athttpelabnavigatoremccom for the latest information onsupported configurations
35
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
Supported zoning parametersRefer to the EMC Networked Storage Topology Guide for the mostup-to-date information on supported zoning parameters
At the time these notes were published the following parameterswere supported
20 VSANs 5 Hops 2000 Unique members per physical infrastructure 1000 Zonesets per physical infrastructure 2000 Zones per physical infrastructure 1 FCIP tunnel
Supported IVR parameters IVR zone members 1000 IVR zones 1000 IVR zone sets 32 VSANS 20 IVR enabled switches 64
An RPQ can be submitted for any configurations that exceed thislimit
Managing zone changes in multiswitch fabricsZoning changes may be made through Fabric Manager or CLI Whenaccessing Fabric Manager or CLI the user does so from the point ofview of one switch That is Fabric Manager and CLI are accessed byentering the IP address of one switch in the fabric
When zoning changes are made the applicable VSAN and zone setdata is propagated to the rest of the switches in the fabric via the ISLs
When zoning changes are made to a VSAN the zone set data ispropagated to the rest of the switches in the fabric via the ISLs Bydefault only the active zone set information is relayed to all switchesin the VSAN If the user accesses the Fabric Manager and CLI fromanother switch in the fabric the new VSAN and zone set informationwill not be viewable To view the active and inactive zone set on theother switches in the fabric the user must log in to the CLI and issuea command from the EXEC prompt
36 EMC Connectrix MDS 9000 NX-OS Release Notes
Documentation
Example The following is an example of copying VSAN 1 through 20 zoningdata
CiscoMDS_name zone copy active full vsan 1-20
CiscoMDS_name conf t
Enter configuration commands one per line End with CNTL Z
CiscoMDS_name(config) zoneset distribute full vsan 1-20
CiscoMDS_name(config)
Note This command needs to be issued on all switches in the fabric one timeonly
This is a nondisruptive command After issuing the commands theuser will now see the active and inactive zone sets for the specifiedVSANs on any switch that is chosen from which to manage the fabric
After a zoning change is made save the running configuration to thestartup configuration
DocumentationSend documentation comments to mdsfeedback-doccom
Product DocumentationAs of NX-OS Release 42(1a) software configuration information isavailable in new feature-specific configuration guides for thefollowing information
System management
Interfaces
Fabric
Quality of service
Security
IP services
High availability and redundancy
37
Software media organization and files
EMC Connectrix MDS 9000 NX-OS Release Notes
The information in these new guides previously existed in the CiscoMDS 9000 Family CLI Configuration Guide That configuration guideremains available on Ciscocom and should be used for all softwarereleases prior to NX-OS Release 42(1a) Configuration guidesaddress the features introduced in or available in a particular releaseSelect and view the configuration guide that pertains to the softwareinstalled in your switch
In addition Fabric Manager information has been removed from theMDS NX-OS Release Notes (this document) and placed intostandalone Fabric Manager Release Notes that support both CiscoMDS 9000 Family switches and Cisco Nexus 5000 Series switchesThe Cisco Fabric Manager Release Notes are available onhttpPowerlinkemccom and from the following website
httpwwwciscocomenUSpartnerproductsps10495prod_release_notes_listhtml
Technical supportThese release notes complement a Cisco documentation set EachCisco document refers to where to get help However for any itemssupplied by EMC see ldquoTroubleshooting and getting helprdquo onpage 38
Software media organization and filesFor information on related software environment and systemrequirements refer to the EMC Support Matrix on EMC Powerlink at
httpPowerlinkEMCcom
InstallationFor hardware installation information refer to the Cisco MDS HWInstallation Guides available at Ciscocom
For EMC-specific installation information refer to ldquoEnvironment andsystem requirementsrdquo on page 5 in this document
38 EMC Connectrix MDS 9000 NX-OS Release Notes
Troubleshooting and getting help
Troubleshooting and getting helpEMC support product and licensing information can be obtained asfollows
Product information mdash For documentation release notes softwareupdates or for information about EMC products licensing andservice go to the EMC Powerlink website (registration required) at
httpPowerlinkEMCcom
Technical support mdash For technical support go to EMC CustomerService on Powerlink To open a service request through Powerlinkyou must have a valid support agreement Please contact your EMCsales representative for details about obtaining a valid supportagreement or to answer any questions about your account
Copyright copy 2011 EMC Corporation All rights reserved
EMC believes the information in this publication is accurate as of its publication date The information issubject to change without notice
THE INFORMATION IN THIS PUBLICATION IS PROVIDED ldquoAS ISrdquo EMC CORPORATION MAKES NOREPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION INTHIS PUBLICATION AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OFMERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Use copying and distribution of any EMC software described in this publication requires an applicablesoftware license
For the most up-to-date regulatory document for your product line go to the Technical Documentation andAdvisories section on EMC Powerlink
For the most up-to-date listing of EMC product names see EMC Corporation Trademarks on EMCcom
All other trademarks used herein are the property of their respective owners
14 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
switch show moduleMod Ports Module-Type Model Status--- ----- -------------------------------- ------------------ ------------7 0 SupervisorFabric-2 DS-X9530-SF2-K9 active 8 0 SupervisorFabric-2 DS-X9530-SF2-K9 ha-standby
Upgrading Your Cisco MDS NX-OS Software ImageThis section lists the guidelines recommended for upgrading yourCisco MDS NX-OS software image and includes the following topics
ldquoGeneral Upgrading Guidelinesrdquo on page 14
ldquoDowngrading Your Cisco MDS SAN-OS Software Imagerdquo onpage 18
Note Before you begin the upgrade process review the list of chassis andmodules that NX-OS Release 50(4b) supports See the ldquoMDS 9000 Chassisand Module Support in Cisco MDS NX-OS 5xrdquo on page 8
Note For detailed instructions for performing a software upgrade usingCisco Fabric Manager see the Cisco Fabric Manager Release Notes forRelease 50(4b) which is available from the following websitehttpPowerlinkEMCcom
General Upgrading Guidelines
Note To upgrade to NX-OS Release 50(4b) you must be running NX-OSRelease 4x If you are running SAN-OS Release 32(3a) or earlier firstupgrade to SAN-OS Release 33(x) then NX-OS Release 4x and thenupgrade to NX-OS Release 50(4b)
Use the following guidelines when upgrading to Cisco MDS NX-OSRelease 5x
Install and configure dual supervisor modules
Issue the show install all impact upgrade-image CLI command todetermine if your upgrade will be nondisruptive
15
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Be aware of the impact of an upgrade on VSAN 4079 if you areupgrading from SAN-OS Release 3x to NX-OS 50(4b) See theldquoUpgrading Effect on VSAN 4079rdquo on page 17
Follow the recommended guidelines for upgrading a Cisco MDS9124 or MDS 9134 Switch as described in ldquoUpgrading a CiscoMDS 9124 or MDS 9134 switchrdquo on page 18
Take note of the affect of upgrades on MDS 9500 series switchesthat have active IOA flows as described in ldquoMDS 9500 seriesupgrades with active IOA flowsrdquo on page 18
Be aware that some features impact whether an upgrade isdisruptive or nondisruptive
bull Fibre Channel Ports Traffic on Fibre Channel ports can benondisruptively upgraded See Table 7 on page 16 for thenondisruptive upgrade path for all NX-OS and SAN-OSreleases
bull Storage Services Intelligent storage services traffic such asSANTap NASB and FC write acceleration is disruptedduring an upgrade Fibre Channel traffic is not
bull Gigabit Ethernet Ports Traffic on Gigabit Ethernet ports isdisrupted during an upgrade or downgrade This includes theGigabit Ethernet ports on the MSM-184 module and the MDS9222i switch Those nodes that are members of VSANs traversingan FCIP ISL are impacted and a fabric reconfiguration occursiSCSI initiators connected to the Gigabit Ethernet ports loseconnectivity to iSCSI targets while the upgrade is in progress
bull FICON If you have FICON enabled the upgrade path isdifferent See Table 6 on page 13
Use Table 7 to determine your nondisruptive upgrade path to Cisco MDSNX-OS Release 50(4b) find the image release number you are currentlyusing in the Current column of the table and use the path recommended
16 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Note The software upgrade information in Table 7 applies only to FibreChannel switching traffic Upgrading system software disrupts IP traffic andSSM intelligent services traffic
MDS NX-OS Release 50(4b) is not a FICON-qualified release
Table 7 Nondisruptive Upgrade Path to Cisco MDS NX-OS Release 50(4b)
Current Nondisruptive Upgrade Path
NX-OS 50(4) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 50(1a) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(7b) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(5) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(3) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(1b) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(1a) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 41(3a) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 41(1b) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
SAN-OS 33(4a) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
NX-OS 33(4) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 33(3) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 33(2) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 33(1c) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 32(3a) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 32(2c) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 32(1a) Upgrade to SAN-OS Release then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 31(3a) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 31(2) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
17
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Use Table 8 to determine your FICON nondisruptive upgrade path toCisco MDS NX-OS Release 42(7b) Find the image release numberyou are currently using in the Current Release with FICON Enabledcolumn of the table and use the path recommended
Note For more information on the FICON qualified NX-OS releases refer tothe EMC Support Matrix available through E-Lab Interoperability Navigator(ELN) at httpelabnavigatorEMCcom
Upgrading Effect on VSAN 4079If you are upgrading to NX-OS Release 50(4b) and you have notcreated VSAN 4079 the NX-OS software will automatically createVSAN 4079 and reserve it for EVFP use If VSAN 4079 is reserved forEVFP use the switchport trunk allowed vsan command will filterout VSAN 4079 from the allowed list as shown in the followingexample
switch(config-if) switchport trunk allowed vsan1-40801-40784080switch(config-if)
If you have created VSAN 4079 the upgrade to NX-OS Release50(4b) will have no affect on VSAN 4079
If you downgrade to a release of NX-OS lower than 41(x) afterNX-OS Release 50(4b) creates VSAN 4079 and reserves it for EVFPuse the VSAN will no longer be reserved
Table 8 FICON Nondisruptive Upgrade Path to NX-OS Release 42(7b)
Current Release withFICON Enabled Upgrade Path
NX-OS 42(1b) You can nondisruptively upgrade directly to NX-OS Release 42(7b)
NX-OS 41(1c) You can nondisruptively upgrade directly to NX-OS Release 42(7b)
SAN-OS 33(1c) You can nondisruptively upgrade directly to NX-OS Release 42(7b)
18 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Upgrading a Cisco MDS 9124 or MDS 9134 switchIf you are upgrading from Cisco MDS SAN-OS Release 31(1) to CiscoNX-OS Release 4x before upgrading to NX-OS Release 50(4b) on aCisco MDS 9124 or MDS 9134 switch follow these guidelines
During the upgrade configuration is not allowed and the fabric isexpected to be stable
The Fabric Shortest Path First (FSPF) timers must be configured tothe default value of 20 seconds otherwise the nondisruptiveupgrade is blocked to ensure that the maximum down toim forthe control plane can be 80 seconds
If there are any CFS commits in the fabric the nondisruptiveupgrade will fail
If there is a zone server merge in progress in the fabric thenondisruptive upgrde will fail
If a service terminates the nondisruptive upgrade the showinstall all failure-reason command can display the reason thatthe nondisruptive upgrade cannot proceed
If there is not enough memory in the system to load the newimages the upgrade will be made disruptive due to insufficientresources and the user will be notified in the compativility table
MDS 9500 series upgrades with active IOA flowsWhen upgading an MDS 9500 series switch that has active IOA flowsthose flows may be interrupted during the supervisor moduleswitchover To workaround this issue you have to enablespanning-tree portfast on the interface on the catalyst connected tothe management interface of the activestandby supervisor for theinterface to come up fast without causing the cluster to lose quorum
Downgrading Your Cisco MDS SAN-OS Software ImageThis section lists the guidelines recommended for downgrading yourCisco MDS SAN-OS software image and includes the followingtopics
ldquoGeneral downgrading guidelinesrdquo on page 19
19
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
General downgrading guidelinesUse the following guidelines to nondisruptively downgrade yourCisco MDS NX-OS Release 50(4b)
Install and configure dual supervisor modules
Issue the system no acl-adjacency-sharing execute command todisable acl adjacency usage on Generation 2 and Generation 1modules If this command fails reduce the number of zones IVRzones TE ports or a combination of these in the system and issuethe command again
Disable all features not supported by the downgrade release Usethe show incompatibility system downgrade-image command todetermine what you need to disable
bull If you are running in interoperability mode two such featuresare the Reliable Commit Service and Full Zone DatabaseDistribution They can be disabled by running thesecommand in config term mode
no zone rcs enableno zoneset capability distribute full
Use the show install all impact downgrade-image command todetermine if your downgrade will be nondisruptive
Be aware that some features impact whether a downgrade isdisruptive or nondisruptive
bull Fibre Channel Ports Traffic on Fibre Channel ports can benondisruptively downgraded See Table 9 on page 20 for thenondisruptive downgrade path for all SAN-OS releases
bull Storage Services Intelligent storage services traffic such asSANTap NASB and FC write acceleration is disruptedduring a downgrade Fibre Channel traffic is not
bull Gigabit Ethernet Ports Traffic on Gigabit Ethernet ports isdisrupted during a downgrade This includes the GigabitEthernet ports on the MSM-184 module and the MDS 9222iswitch Those nodes that are members of VSANs traversing anFCIP ISL are impacted and a fabric reconfiguration occursiSCSI initiators connected to the Gigabit Ethernet ports loseconnectivity to iSCSI targets while the downgrade is inprogress
20 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
bull FICON If you have FICON enabled the downgrade path isdifferent See Table 10 on page 21
Note A downgrade from NX-OS Release 4x to SAN-OS Release 33(1c) is notsupported on MDS switches when FC-Redirect based applications such asData Mobility Manager or Storage Media Encryption are configured in thefabric if either of the following conditions are satisfied
1 A target for which FC-Redirect is configured is connected locally and thereare Generation 1 modules with ISLs configured in the switch
2 A host for which FC-redirect is configured is connected locally ona Generation 1 module
If these conditions exist remove the application configuration forthese targets and hosts before proceeding with the downgrade
Use Table 9 on page 20 to determine the nondisruptive downgradepath from Cisco NX-OS Release 50(4b) Find the NX-OS or SAN-OSimage you want to downgrade to in the To SAN-OSNX-OS Releasecolumn of the table and use the path recommended
Note The software downgrade information in Table 10 on page 21 appliesonly to Fibre Channel switching traffic Downgrading system softwaredisrupts IP and SSM intelligent services traffic
Table 9 Nondisruptive Downgrade Path from NX-OS Release 50(4b) (page 1 of2)
To SAN-OS NX-OSRelease Nondisruptive Downgrade Path
NX-OS 50(4) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 50(1a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(7b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(5) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(3) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(1b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(1a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 41(3a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
21
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Use Table 10 to determine your nondisruptive downgrade path if youhave FICON enabled from Cisco NX-OS Release 42(7b) Find the imagerelease number you are currently using in the Current Release withFICON Enabled column of the table and use the path recommended
NX-OS 41(1b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
SAN-OS 33(5a) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33())
SAN-OS 33(5) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(4a) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
NX-OS 33(4) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(3) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
NX-OS 33(2) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(1c) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 32(3a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 32(x)
SAN-OS 32(2c) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 32(x)
SAN-OS 32(1a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
SAN-OS 31(3a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
SAN-OS 31(2) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
Table 9 Nondisruptive Downgrade Path from NX-OS Release 50(4b) (page 2 of2)
To SAN-OS NX-OSRelease Nondisruptive Downgrade Path
Table 10 FICON Downgrade Path from NX-OS Release 42(7b)
To SAN-OSNX-OS Release withFICON Enabled Downgrade Path
NX-OS 42(1b) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
NX-OS 41(1c) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
SAN-OS 33(1c) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
22 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Best practicesLog messages are not saved across system reboots or power outagesTherefore EMC recommends that customers configure a SyslogServer in order to redirect and capture all log messages on a remoteserver For more information please refer to the Cisco MDS 9000Family Configuration Guide available at
httpwwwciscocomenUSproductsps5989products_support_series_homehtml
Maximum ports per chassisTable 11 shows the maximum ports per chassis
a V2 indicates a 9506 or 9509 with Generation-2 Supervisors The presence of anygeneration one module in a switch will limit the maximum port count to 252This includes the 16-port 32-port 14+2 IPS4 and IPS8 cards
Known problems and limitationsFor a list of problems with this release please refer to the CiscoRelease notes located at
httpwwwciscocomenUSproductsps5989prod_release_notes_listhtml
Limitations and restrictionsThe following limitations and restrictions apply to all switches in theCisco MDS 9000 Family unless a limitation for a specific switch isstated
ldquoStorage Media Encryption (SME) limitationsrdquo on page 24
Table 11 Maximum ports per chassis
Chassis Maximum number of ports
MDS 9506-V2 192a
MDS 9509-V2 336
MDS 9513 528
23
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
ldquoSME configuration limitsrdquo on page 24
ldquoDeleting Cisco SME interfacesrdquo on page 25
ldquoCisco MDS 9124 and 9134 Multilayer fabric switchesrdquo on page 25
ldquoN-Port virtualization configuration limitsrdquo on page 25
ldquoMaximum number of zones supported in Interop Mode 4rdquo onpage 25
ldquoIPv6rdquo on page 26
ldquoIP-ACL supportrdquo on page 26
ldquoUser Rolesrdquo on page 26
ldquoUsing a RSA Version 1 Key for SSH Following an Upgraderdquo onpage 27
ldquoApplying Zone Configurations to VSAN 1rdquo on page 27
ldquoInterVSAN Routingrdquo on page 28
ldquoRSPAN Traffic Not Supported on CTS Ports on 8-GbpsSwitching Modulesrdquo on page 28
ldquoIO Accelerator Feature Limitationsrdquo on page 28
ldquoSupport for FCIP Compression Modesrdquo on page 28
ldquoSaving Copies of the Running Kickstart and System Imagesrdquo onpage 29
ldquoConfiguring Buffer Credits on a Generation 2 or Generation 3Modulerdquo on page 29
ldquoStorage services module power budgetrdquo on page 29
ldquoiSCSI proxy initiator in Celerra HighRoad environmentsrdquo onpage 30
ldquoHPUX N_port IDrdquo on page 30
ldquoInteroperability limitationsrdquo on page 31
ldquoNASBrdquo on page 31
ldquoReserved VSAN Range and Isolated VSAN Range Guidelinesrdquoon page 31
ldquoSymmetrix VMax limitationsrdquo on page 32
ldquoStorage Applications on the MSM-184rdquo on page 32
ldquoDowngrading with fport-channel-trunk enabledrdquo on page 32
ldquoLDAP Authenticationrdquo on page 33
24 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
ldquoMDS-9148 limitationsrdquo on page 33
Storage Media Encryption (SME) limitationsAn SME node can only belong to one cluster Adding the node tomore than one cluster will cause problems
Currently there is no prevention or warning in place when an attemptis made to add a node to multiple clusters
SME configuration limitsTable 12 lists the SME configuration limits for this release
Table 12 SME configuration limits
Configuration Limits
Number of switches in the fabric 10
Number of clusters per switch 1
Switches in a cluster 4
Fabrics in a cluster 2
Modules in a switch 11
Cisco MSM-184 modules in a cluster 32
Initiator-Target-LUNs (ITLs) 1024
LUNs behind a target 32
Host and target ports in a cluster 128
Number of hosts per target 128
Tape backup groups per cluster 2
Volume groups in a tape backup group 4
Cisco Key Management Center ( of keys) 32K
Targets per switch that can be FC-redirected 32
25
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Deleting Cisco SME interfacesA Cisco SME interface can be deleted from the cluster only after theinterface is administratively shut-down and all related tasksassociated with the interface shut-down are complete
Cisco MDS 9124 and 9134 Multilayer fabric switchesThe Cisco MDS 9124 and 9134 Multilayer fabric switches do notsupport the following Cisco MDS SAN-OS features
IVR Remote Span Translative loop support FCCmdash no generation quench reaction only
In addition the following features have these limits
VSANs mdash 16 maximum SPAN mdash 1 session maximum
N-Port virtualization configuration limitsThe NPV features have maximum configuration limits Table 13shows the verified and maximum limits for the NPV switchesrunning NX-OS Release 5x
Maximum number of zones supported in Interop Mode 4In interop mode 4 the maximum number of zones that is supportedin an active zone set is 2047 due to limitations in the connectedvendor switch When IVR is used in interop mode 4 the maximumnumber of zones supported including IVR zones in the active zoneset is 2047 The limit for the maximum number of IVR zones perVSAN is 250 zones (two members per zone)
Table 13 NPV features limitations
Feature Verified limits Maximum limits
FLOGIs or F Disc per NPV port group 114 114
NPV switches per NPV core switch 105 105
FLOGIs per line card on NPV core switch 400 400
26 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
IPv6The management port on Cisco MDS switches supports oneuser-configured IPv6 address but does not supportauto-configuration of an IPv6 address
IP-ACL supportDo not apply IP-ACLs to only one member of a PortChannel groupApply IP-ACLs to the entire channel group
If IP-ACLs are already configured in a Gigabit Ethernet interface youcannot add this interface to a Ethernet PortChannel group
Refer to the Cisco MDS 9000 Family Configuration Guide
User RolesIn SAN-OS Release 33(x) and earlier when a user belongs to a rolewhich has a VSAN policy set to Deny and the role allows access to aspecific set of VSANs (for example 1 through 10) the user isrestricted from performing the configuration clear execute anddebug commands which had a VSAN parameter outside thisspecified set Beginning with NX-OS Release 41(1b) these users arestill prevented from performing configuration clear execute anddebug commands as before however they are allowed to performshow commands for all VSANs The ability to execute the showcommand addresses the following
In a network environment users often need to view informationin other VSANs even though they do not have permission tomodify configurations in those VSANs
This behavior makes Cisco MDS 9000 Series switches consistentwith other Cisco products such as Cisco Nexus 7000 Seriesswitches that exhibit the same behavior for those roles (whenthey apply to the VLAN policy)
27
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Using a RSA Version 1 Key for SSH Following an UpgradeFor security reasons NX-OS Release 42(x) and higher does notsupport RSA version 1 keys As a result if you upgrade from anearlier version that did support RSA version 1 keys and you hadconfigured a RSA version 1 key for SSH then you will not be able tolog in through SSH following the upgrade
If you have a RSA version 1 key configured for SSH beforeupgrading to NX-OS Release 42(x) or higher follow these steps
1 Disable SSH
2 Create RSA version 2 DSA keys
3 Enable SSH
4 Delete any RSA version 1 keys on any remote SSH clients andreplace the version 1 keys with the new version 2 keys from theswitch
Proceed with the upgrade to NX-OS Release 42(x) or higher
If you upgrade before disabling SSH and creating RSA version 2 keysfollow these steps
1 Open a Telnet session and log in through the console
2 Issue the no feature ssh command to disable SSH
3 Issue the ssh key rsa 1024 command to create RSA version 2 keys
4 Issue the feature ssh command to enable SSH
Applying Zone Configurations to VSAN 1In the setup script you can configure system default values for thedefault-zone to be permit or deny and you can configure defaultvalues for the zone distribution method and for the zone mode
These default settings are applied when a new VSAN is createdHowever the settings will not take effect on VSAN 1 because it existsprior to running the setup script Therefore when you need thosesettings for VSAN 1 you must explicitly issue the followingcommands
zone default-zone permit vsan 1 zoneset distribute full vsan 1 zone mode enhanced vsan 1
28 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
InterVSAN RoutingWhen using InterVSAN Routing (IVR) it is recommended to enableCisco Fabric Services (CFS) on all IVR-enabled switches Failure to doso may cause mismatched active zone sets if an error occurs duringzone set activation
RSPAN Traffic Not Supported on CTS Ports on 8-Gbps Switching ModulesAn inter-switch link (ISL) that is enabled for Cisco TrustSec (CTS)encryption must be brought up in non-CTS mode to support remoteSPAN (RSPAN) traffic on the following modules
DS-X9248-96K9 Cisco MDS 9000 48-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9224-96K9 Cisco MDS 9000 24-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9248-48K9 Cisco MDS 9000 444-Port Host-Optimized8-Gbps Fibre Channel Switching Module
If the ISL link is brought up with CTS enabled random packets dropsof both RSPAN traffic and normal traffic will occur on the receiverport switch
IO Accelerator Feature LimitationsIOA does not support the following NX-OS features
IVR flows
Devices with NPV and NPIV enabled
F port trunking
bull F port channeling
Support for FCIP Compression ModesIn Cisco NX-OS Release 42(1b) and higher FCIP compression mode 1and compression mode 3 are not supported on the Cisco MSM-184module and on the SSN-16 module
29
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Saving Copies of the Running Kickstart and System ImagesAfter you upgrade to MDS NX-OS Release 42(1b) or higher you arenot allowed to delete rename move or overwrite the kickstart andsystem images that are in the current system bootvar settings on anactive or standby MDS Supervisor-2 module on any Cisco MDS 9500Series switch This restriction does not apply to the integratedsupervisor module on the MDS 9200 and MDS 9100 series switches
Configuring Buffer Credits on a Generation 2 or Generation 3 ModuleWhen you configure port mode to auto or E on a Generation 2module one of the ports will not come up for the followingconfiguration
Port Mode auto or E for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E on a Generation 3module one or two of the ports will not come up for the followingconfiguration
Port Mode auto or E for the first half of the ports the second halfof the ports or for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E for all ports in the globalbuffer pool you need to reconfigure buffer credits on one or more ofthe ports The total number of buffer credits configured for all theports in the global buffer pool should be reduced by 64
Storage services module power budgetThe MDS 9509 does not have the power budget to run seven SSMcards EMC recommends a maximum of four SSMs in one 9509Customers wishing to use more than four SSMs in one chassis shouldrefer to the Cisco MDS 9000 documentation on the Ciscocom websiteto validate that there is enough power available for their desiredconfiguration
30 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Note Upgrading to the 3000 watt power supplies will alleviate thiscondition
iSCSI proxy initiator in Celerra HighRoad environmentsEMC supports the iSCSI proxy initiator feature in Celerrareg
HighRoadreg environments In proxy initiator mode one Fibre Channelinitiator is used for all iSCSI clients who access the switch via thesame iSCSI interface (iscsi33 for example)
The initiators will use the PWWN assigned to the iSCSI interface TheiSCSI interface to which an iSCSI client will logon to is configured inthe client and must be permitted by the virtual target configured forthat initiator
The current session environment supported on the MDS is
300 sessions per port 1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no InitialR2T=yes
Refer to the specific initiator support documentation on how to setthe parameters The implementation will not perform properly ifthese bits are not set
Refer to the MDS documentation for more information regarding theconfiguration of the iSCSI proxy initiator at the following Ciscowebsite
httpwwwciscocomenUSproducts
HPUX N_port IDThe N_port ID port value of 255 (0xFF) has special meaning forHP-UX A N_port ID (FC_ID) can not be returned from a switch thatcontains this value for the N_port ID (FC_ID) port value for a HP-UXinitiator or HP-UX target port Port ID value of 255 (0xFF) cannot be
31
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
configured for HP-UX initiator port and HP-UX target ports whenconfiguring MDS FC_IDs The port_ID value is the third byte of theFC_ID
Interoperability limitationsRefer to the EMC Support Matrix (ESM) and the EMC Networked Storage Topology Guide for modes of operation and caveats
NASBThe NASB feature requires that the backup application load the tapedrive with a compatible tape cartridge prior to configuring NASB inthe backup VSAN
Reserved VSAN Range and Isolated VSAN Range GuidelinesOn an NPV switch with a trunking configuration on any interface or ona regular switch where the feature fport_channel_trunk command hasbeen issued to enable the F PortChannel feature follow theseconfiguration guidelines for reserved VSANs and the isolated VSAN
bull If trunk mode is on for any of the interfaces or NP PortChannelis up the reserved VSANs are 3040 to 4078 and they are notavailable for user configuration
bull The Exchange Virtual Fabric Protocol (EVFP) isolated VSAN is4079 and it is not available for user configuration
bull VSAN 4079 will be impacted by an upgrade to NX-OS Release42(3) depending on whether or not VSAN 4079 was createdprior to the upgrade See theldquoUpgrading Effect on VSAN 4079rdquoon page 17
The following VSAN IDs are assigned in the Fibre Channel Framingand Signaling (FC-FS) interface standard
VF_ID Value Value Description
00h Do not use as a Virtual FabricIdentifier
001h EFFh Available as a Virtual FabricIdentifier
F00h FEEh Reserved
32 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Symmetrix VMax limitationsAt the time of this writing the following features are not supportedfor use with the Symmetrix VMax
FCIP Write Acceleration
The NX-OS IOA functionality is only supported with the Q2 SREnginuity release 5874229182 or higher
For the most up to date status please refer to the current revision ofthese Release Notes on httpPowerlinkemccom and the EMCSupport Matrix available through E-Lab Interoperability Navigator (ELN) athttpelabnavigatorEMCcom
Storage Applications on the MSM-184The MDS 9000 184-Port Multiservice Module (MSM-184) does notsupport multiple concurrent storage applications Only oneapplication can run on the MSM-184 at a time
Downgrading with fport-channel-trunk enabledIf you are running MDS NX-OS Release 42(x) or higher with thefport-channel-trunk feature enabled and you downgrade to anyNX-OS 41(1x) release the installer performs a nondisruptivedowngrade even though the fport-channel-trunk feature is notsupported in NX-OS 41(1x) releases
As a result the switch is in an inconsistent state and the ports maynot function properly
FEFh Control VF-ID (see FibreChannel Link Services (FC-LS)and Fibre Channel SwitchFabric Generation 4 (FC-SW-4)standards)
FF0h FFEh Vendor specific
FFFh Do not use as a Virtual FabricIdentifier
FEFh = 4079
33
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
If you are in this state a workaround is to reboot the switch followingthe upgrade
LDAP AuthenticationThere is currently a limitation in the LDAP server configuration CLIthat prevents the use of an OU with spaces in the name Normallythese OU names could be surrounded by quotation marks howeverquotation marks are not supported by the ldap-server command
MDS-9148 limitationsThe Cisco MDS 9148 Multilayer Fabric Switch does not support thefollowing NX-OS features
Medium and Long range 4GB Agilent
IVR
Remote Span
Translative loop support
FCC - no generation quench reaction only
FC-Redirect
In addition the following features have these limits
VSANS - 31 maximum
SPAN - 1 session maximum
Technical notesThe following sections provide further information on technicalnotes
EMC Email Home for Cisco MDS switchesInstallation and Trouble shooting instructions can be found in thedocumentation located at the EMC Customer Service Internalwebsite
httpwwwcsisusemccomcsweb2esnesnhomehtmConnectrix20MDS20900020Family
34 EMC Connectrix MDS 9000 NX-OS Release Notes
Technical notes
Customers requiring installation of this solution should contact theirEMC Customer Engineer to assist with the installation and providethe documentation
Supported iSCSI sessionsThe current iSCSI session environment supported on the MDS is
300 sessions per port
1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no
InitialR2T=yes
Upgrading Cisco SAN-OSThere are several methods available for upgrading SAN-OS SoftwareEMC personnel are strongly recommended that all upgrades be doneby the Automated One-Step Upgrade using the install all
command EMC personnel should refer to the Connectrix MDS 9000Family Software Image Upgrade Instructions for a complete list ofprerequisites and instructions for performing the upgrade Thisdocument along with tftp software is available on the GlobalServices website at httpwwwcsisusEMCcom under ApplicationDownload Area ESN Product Information Connectrix MDS 9000Family
The Software Upgrade Wizard is an option for upgrades While theinstall all is the preferred method the Software Install Wizard canalso be used
Supported configuration parametersFor the most up-to-date information refer to the EMC Support Matrixavailable through E-Lab Interoperability Navigator athttpelabnavigatoremccom for the latest information onsupported configurations
35
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
Supported zoning parametersRefer to the EMC Networked Storage Topology Guide for the mostup-to-date information on supported zoning parameters
At the time these notes were published the following parameterswere supported
20 VSANs 5 Hops 2000 Unique members per physical infrastructure 1000 Zonesets per physical infrastructure 2000 Zones per physical infrastructure 1 FCIP tunnel
Supported IVR parameters IVR zone members 1000 IVR zones 1000 IVR zone sets 32 VSANS 20 IVR enabled switches 64
An RPQ can be submitted for any configurations that exceed thislimit
Managing zone changes in multiswitch fabricsZoning changes may be made through Fabric Manager or CLI Whenaccessing Fabric Manager or CLI the user does so from the point ofview of one switch That is Fabric Manager and CLI are accessed byentering the IP address of one switch in the fabric
When zoning changes are made the applicable VSAN and zone setdata is propagated to the rest of the switches in the fabric via the ISLs
When zoning changes are made to a VSAN the zone set data ispropagated to the rest of the switches in the fabric via the ISLs Bydefault only the active zone set information is relayed to all switchesin the VSAN If the user accesses the Fabric Manager and CLI fromanother switch in the fabric the new VSAN and zone set informationwill not be viewable To view the active and inactive zone set on theother switches in the fabric the user must log in to the CLI and issuea command from the EXEC prompt
36 EMC Connectrix MDS 9000 NX-OS Release Notes
Documentation
Example The following is an example of copying VSAN 1 through 20 zoningdata
CiscoMDS_name zone copy active full vsan 1-20
CiscoMDS_name conf t
Enter configuration commands one per line End with CNTL Z
CiscoMDS_name(config) zoneset distribute full vsan 1-20
CiscoMDS_name(config)
Note This command needs to be issued on all switches in the fabric one timeonly
This is a nondisruptive command After issuing the commands theuser will now see the active and inactive zone sets for the specifiedVSANs on any switch that is chosen from which to manage the fabric
After a zoning change is made save the running configuration to thestartup configuration
DocumentationSend documentation comments to mdsfeedback-doccom
Product DocumentationAs of NX-OS Release 42(1a) software configuration information isavailable in new feature-specific configuration guides for thefollowing information
System management
Interfaces
Fabric
Quality of service
Security
IP services
High availability and redundancy
37
Software media organization and files
EMC Connectrix MDS 9000 NX-OS Release Notes
The information in these new guides previously existed in the CiscoMDS 9000 Family CLI Configuration Guide That configuration guideremains available on Ciscocom and should be used for all softwarereleases prior to NX-OS Release 42(1a) Configuration guidesaddress the features introduced in or available in a particular releaseSelect and view the configuration guide that pertains to the softwareinstalled in your switch
In addition Fabric Manager information has been removed from theMDS NX-OS Release Notes (this document) and placed intostandalone Fabric Manager Release Notes that support both CiscoMDS 9000 Family switches and Cisco Nexus 5000 Series switchesThe Cisco Fabric Manager Release Notes are available onhttpPowerlinkemccom and from the following website
httpwwwciscocomenUSpartnerproductsps10495prod_release_notes_listhtml
Technical supportThese release notes complement a Cisco documentation set EachCisco document refers to where to get help However for any itemssupplied by EMC see ldquoTroubleshooting and getting helprdquo onpage 38
Software media organization and filesFor information on related software environment and systemrequirements refer to the EMC Support Matrix on EMC Powerlink at
httpPowerlinkEMCcom
InstallationFor hardware installation information refer to the Cisco MDS HWInstallation Guides available at Ciscocom
For EMC-specific installation information refer to ldquoEnvironment andsystem requirementsrdquo on page 5 in this document
38 EMC Connectrix MDS 9000 NX-OS Release Notes
Troubleshooting and getting help
Troubleshooting and getting helpEMC support product and licensing information can be obtained asfollows
Product information mdash For documentation release notes softwareupdates or for information about EMC products licensing andservice go to the EMC Powerlink website (registration required) at
httpPowerlinkEMCcom
Technical support mdash For technical support go to EMC CustomerService on Powerlink To open a service request through Powerlinkyou must have a valid support agreement Please contact your EMCsales representative for details about obtaining a valid supportagreement or to answer any questions about your account
Copyright copy 2011 EMC Corporation All rights reserved
EMC believes the information in this publication is accurate as of its publication date The information issubject to change without notice
THE INFORMATION IN THIS PUBLICATION IS PROVIDED ldquoAS ISrdquo EMC CORPORATION MAKES NOREPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION INTHIS PUBLICATION AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OFMERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Use copying and distribution of any EMC software described in this publication requires an applicablesoftware license
For the most up-to-date regulatory document for your product line go to the Technical Documentation andAdvisories section on EMC Powerlink
For the most up-to-date listing of EMC product names see EMC Corporation Trademarks on EMCcom
All other trademarks used herein are the property of their respective owners
15
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Be aware of the impact of an upgrade on VSAN 4079 if you areupgrading from SAN-OS Release 3x to NX-OS 50(4b) See theldquoUpgrading Effect on VSAN 4079rdquo on page 17
Follow the recommended guidelines for upgrading a Cisco MDS9124 or MDS 9134 Switch as described in ldquoUpgrading a CiscoMDS 9124 or MDS 9134 switchrdquo on page 18
Take note of the affect of upgrades on MDS 9500 series switchesthat have active IOA flows as described in ldquoMDS 9500 seriesupgrades with active IOA flowsrdquo on page 18
Be aware that some features impact whether an upgrade isdisruptive or nondisruptive
bull Fibre Channel Ports Traffic on Fibre Channel ports can benondisruptively upgraded See Table 7 on page 16 for thenondisruptive upgrade path for all NX-OS and SAN-OSreleases
bull Storage Services Intelligent storage services traffic such asSANTap NASB and FC write acceleration is disruptedduring an upgrade Fibre Channel traffic is not
bull Gigabit Ethernet Ports Traffic on Gigabit Ethernet ports isdisrupted during an upgrade or downgrade This includes theGigabit Ethernet ports on the MSM-184 module and the MDS9222i switch Those nodes that are members of VSANs traversingan FCIP ISL are impacted and a fabric reconfiguration occursiSCSI initiators connected to the Gigabit Ethernet ports loseconnectivity to iSCSI targets while the upgrade is in progress
bull FICON If you have FICON enabled the upgrade path isdifferent See Table 6 on page 13
Use Table 7 to determine your nondisruptive upgrade path to Cisco MDSNX-OS Release 50(4b) find the image release number you are currentlyusing in the Current column of the table and use the path recommended
16 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Note The software upgrade information in Table 7 applies only to FibreChannel switching traffic Upgrading system software disrupts IP traffic andSSM intelligent services traffic
MDS NX-OS Release 50(4b) is not a FICON-qualified release
Table 7 Nondisruptive Upgrade Path to Cisco MDS NX-OS Release 50(4b)
Current Nondisruptive Upgrade Path
NX-OS 50(4) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 50(1a) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(7b) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(5) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(3) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(1b) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(1a) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 41(3a) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 41(1b) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
SAN-OS 33(4a) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
NX-OS 33(4) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 33(3) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 33(2) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 33(1c) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 32(3a) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 32(2c) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 32(1a) Upgrade to SAN-OS Release then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 31(3a) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 31(2) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
17
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Use Table 8 to determine your FICON nondisruptive upgrade path toCisco MDS NX-OS Release 42(7b) Find the image release numberyou are currently using in the Current Release with FICON Enabledcolumn of the table and use the path recommended
Note For more information on the FICON qualified NX-OS releases refer tothe EMC Support Matrix available through E-Lab Interoperability Navigator(ELN) at httpelabnavigatorEMCcom
Upgrading Effect on VSAN 4079If you are upgrading to NX-OS Release 50(4b) and you have notcreated VSAN 4079 the NX-OS software will automatically createVSAN 4079 and reserve it for EVFP use If VSAN 4079 is reserved forEVFP use the switchport trunk allowed vsan command will filterout VSAN 4079 from the allowed list as shown in the followingexample
switch(config-if) switchport trunk allowed vsan1-40801-40784080switch(config-if)
If you have created VSAN 4079 the upgrade to NX-OS Release50(4b) will have no affect on VSAN 4079
If you downgrade to a release of NX-OS lower than 41(x) afterNX-OS Release 50(4b) creates VSAN 4079 and reserves it for EVFPuse the VSAN will no longer be reserved
Table 8 FICON Nondisruptive Upgrade Path to NX-OS Release 42(7b)
Current Release withFICON Enabled Upgrade Path
NX-OS 42(1b) You can nondisruptively upgrade directly to NX-OS Release 42(7b)
NX-OS 41(1c) You can nondisruptively upgrade directly to NX-OS Release 42(7b)
SAN-OS 33(1c) You can nondisruptively upgrade directly to NX-OS Release 42(7b)
18 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Upgrading a Cisco MDS 9124 or MDS 9134 switchIf you are upgrading from Cisco MDS SAN-OS Release 31(1) to CiscoNX-OS Release 4x before upgrading to NX-OS Release 50(4b) on aCisco MDS 9124 or MDS 9134 switch follow these guidelines
During the upgrade configuration is not allowed and the fabric isexpected to be stable
The Fabric Shortest Path First (FSPF) timers must be configured tothe default value of 20 seconds otherwise the nondisruptiveupgrade is blocked to ensure that the maximum down toim forthe control plane can be 80 seconds
If there are any CFS commits in the fabric the nondisruptiveupgrade will fail
If there is a zone server merge in progress in the fabric thenondisruptive upgrde will fail
If a service terminates the nondisruptive upgrade the showinstall all failure-reason command can display the reason thatthe nondisruptive upgrade cannot proceed
If there is not enough memory in the system to load the newimages the upgrade will be made disruptive due to insufficientresources and the user will be notified in the compativility table
MDS 9500 series upgrades with active IOA flowsWhen upgading an MDS 9500 series switch that has active IOA flowsthose flows may be interrupted during the supervisor moduleswitchover To workaround this issue you have to enablespanning-tree portfast on the interface on the catalyst connected tothe management interface of the activestandby supervisor for theinterface to come up fast without causing the cluster to lose quorum
Downgrading Your Cisco MDS SAN-OS Software ImageThis section lists the guidelines recommended for downgrading yourCisco MDS SAN-OS software image and includes the followingtopics
ldquoGeneral downgrading guidelinesrdquo on page 19
19
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
General downgrading guidelinesUse the following guidelines to nondisruptively downgrade yourCisco MDS NX-OS Release 50(4b)
Install and configure dual supervisor modules
Issue the system no acl-adjacency-sharing execute command todisable acl adjacency usage on Generation 2 and Generation 1modules If this command fails reduce the number of zones IVRzones TE ports or a combination of these in the system and issuethe command again
Disable all features not supported by the downgrade release Usethe show incompatibility system downgrade-image command todetermine what you need to disable
bull If you are running in interoperability mode two such featuresare the Reliable Commit Service and Full Zone DatabaseDistribution They can be disabled by running thesecommand in config term mode
no zone rcs enableno zoneset capability distribute full
Use the show install all impact downgrade-image command todetermine if your downgrade will be nondisruptive
Be aware that some features impact whether a downgrade isdisruptive or nondisruptive
bull Fibre Channel Ports Traffic on Fibre Channel ports can benondisruptively downgraded See Table 9 on page 20 for thenondisruptive downgrade path for all SAN-OS releases
bull Storage Services Intelligent storage services traffic such asSANTap NASB and FC write acceleration is disruptedduring a downgrade Fibre Channel traffic is not
bull Gigabit Ethernet Ports Traffic on Gigabit Ethernet ports isdisrupted during a downgrade This includes the GigabitEthernet ports on the MSM-184 module and the MDS 9222iswitch Those nodes that are members of VSANs traversing anFCIP ISL are impacted and a fabric reconfiguration occursiSCSI initiators connected to the Gigabit Ethernet ports loseconnectivity to iSCSI targets while the downgrade is inprogress
20 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
bull FICON If you have FICON enabled the downgrade path isdifferent See Table 10 on page 21
Note A downgrade from NX-OS Release 4x to SAN-OS Release 33(1c) is notsupported on MDS switches when FC-Redirect based applications such asData Mobility Manager or Storage Media Encryption are configured in thefabric if either of the following conditions are satisfied
1 A target for which FC-Redirect is configured is connected locally and thereare Generation 1 modules with ISLs configured in the switch
2 A host for which FC-redirect is configured is connected locally ona Generation 1 module
If these conditions exist remove the application configuration forthese targets and hosts before proceeding with the downgrade
Use Table 9 on page 20 to determine the nondisruptive downgradepath from Cisco NX-OS Release 50(4b) Find the NX-OS or SAN-OSimage you want to downgrade to in the To SAN-OSNX-OS Releasecolumn of the table and use the path recommended
Note The software downgrade information in Table 10 on page 21 appliesonly to Fibre Channel switching traffic Downgrading system softwaredisrupts IP and SSM intelligent services traffic
Table 9 Nondisruptive Downgrade Path from NX-OS Release 50(4b) (page 1 of2)
To SAN-OS NX-OSRelease Nondisruptive Downgrade Path
NX-OS 50(4) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 50(1a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(7b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(5) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(3) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(1b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(1a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 41(3a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
21
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Use Table 10 to determine your nondisruptive downgrade path if youhave FICON enabled from Cisco NX-OS Release 42(7b) Find the imagerelease number you are currently using in the Current Release withFICON Enabled column of the table and use the path recommended
NX-OS 41(1b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
SAN-OS 33(5a) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33())
SAN-OS 33(5) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(4a) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
NX-OS 33(4) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(3) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
NX-OS 33(2) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(1c) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 32(3a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 32(x)
SAN-OS 32(2c) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 32(x)
SAN-OS 32(1a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
SAN-OS 31(3a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
SAN-OS 31(2) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
Table 9 Nondisruptive Downgrade Path from NX-OS Release 50(4b) (page 2 of2)
To SAN-OS NX-OSRelease Nondisruptive Downgrade Path
Table 10 FICON Downgrade Path from NX-OS Release 42(7b)
To SAN-OSNX-OS Release withFICON Enabled Downgrade Path
NX-OS 42(1b) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
NX-OS 41(1c) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
SAN-OS 33(1c) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
22 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Best practicesLog messages are not saved across system reboots or power outagesTherefore EMC recommends that customers configure a SyslogServer in order to redirect and capture all log messages on a remoteserver For more information please refer to the Cisco MDS 9000Family Configuration Guide available at
httpwwwciscocomenUSproductsps5989products_support_series_homehtml
Maximum ports per chassisTable 11 shows the maximum ports per chassis
a V2 indicates a 9506 or 9509 with Generation-2 Supervisors The presence of anygeneration one module in a switch will limit the maximum port count to 252This includes the 16-port 32-port 14+2 IPS4 and IPS8 cards
Known problems and limitationsFor a list of problems with this release please refer to the CiscoRelease notes located at
httpwwwciscocomenUSproductsps5989prod_release_notes_listhtml
Limitations and restrictionsThe following limitations and restrictions apply to all switches in theCisco MDS 9000 Family unless a limitation for a specific switch isstated
ldquoStorage Media Encryption (SME) limitationsrdquo on page 24
Table 11 Maximum ports per chassis
Chassis Maximum number of ports
MDS 9506-V2 192a
MDS 9509-V2 336
MDS 9513 528
23
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
ldquoSME configuration limitsrdquo on page 24
ldquoDeleting Cisco SME interfacesrdquo on page 25
ldquoCisco MDS 9124 and 9134 Multilayer fabric switchesrdquo on page 25
ldquoN-Port virtualization configuration limitsrdquo on page 25
ldquoMaximum number of zones supported in Interop Mode 4rdquo onpage 25
ldquoIPv6rdquo on page 26
ldquoIP-ACL supportrdquo on page 26
ldquoUser Rolesrdquo on page 26
ldquoUsing a RSA Version 1 Key for SSH Following an Upgraderdquo onpage 27
ldquoApplying Zone Configurations to VSAN 1rdquo on page 27
ldquoInterVSAN Routingrdquo on page 28
ldquoRSPAN Traffic Not Supported on CTS Ports on 8-GbpsSwitching Modulesrdquo on page 28
ldquoIO Accelerator Feature Limitationsrdquo on page 28
ldquoSupport for FCIP Compression Modesrdquo on page 28
ldquoSaving Copies of the Running Kickstart and System Imagesrdquo onpage 29
ldquoConfiguring Buffer Credits on a Generation 2 or Generation 3Modulerdquo on page 29
ldquoStorage services module power budgetrdquo on page 29
ldquoiSCSI proxy initiator in Celerra HighRoad environmentsrdquo onpage 30
ldquoHPUX N_port IDrdquo on page 30
ldquoInteroperability limitationsrdquo on page 31
ldquoNASBrdquo on page 31
ldquoReserved VSAN Range and Isolated VSAN Range Guidelinesrdquoon page 31
ldquoSymmetrix VMax limitationsrdquo on page 32
ldquoStorage Applications on the MSM-184rdquo on page 32
ldquoDowngrading with fport-channel-trunk enabledrdquo on page 32
ldquoLDAP Authenticationrdquo on page 33
24 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
ldquoMDS-9148 limitationsrdquo on page 33
Storage Media Encryption (SME) limitationsAn SME node can only belong to one cluster Adding the node tomore than one cluster will cause problems
Currently there is no prevention or warning in place when an attemptis made to add a node to multiple clusters
SME configuration limitsTable 12 lists the SME configuration limits for this release
Table 12 SME configuration limits
Configuration Limits
Number of switches in the fabric 10
Number of clusters per switch 1
Switches in a cluster 4
Fabrics in a cluster 2
Modules in a switch 11
Cisco MSM-184 modules in a cluster 32
Initiator-Target-LUNs (ITLs) 1024
LUNs behind a target 32
Host and target ports in a cluster 128
Number of hosts per target 128
Tape backup groups per cluster 2
Volume groups in a tape backup group 4
Cisco Key Management Center ( of keys) 32K
Targets per switch that can be FC-redirected 32
25
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Deleting Cisco SME interfacesA Cisco SME interface can be deleted from the cluster only after theinterface is administratively shut-down and all related tasksassociated with the interface shut-down are complete
Cisco MDS 9124 and 9134 Multilayer fabric switchesThe Cisco MDS 9124 and 9134 Multilayer fabric switches do notsupport the following Cisco MDS SAN-OS features
IVR Remote Span Translative loop support FCCmdash no generation quench reaction only
In addition the following features have these limits
VSANs mdash 16 maximum SPAN mdash 1 session maximum
N-Port virtualization configuration limitsThe NPV features have maximum configuration limits Table 13shows the verified and maximum limits for the NPV switchesrunning NX-OS Release 5x
Maximum number of zones supported in Interop Mode 4In interop mode 4 the maximum number of zones that is supportedin an active zone set is 2047 due to limitations in the connectedvendor switch When IVR is used in interop mode 4 the maximumnumber of zones supported including IVR zones in the active zoneset is 2047 The limit for the maximum number of IVR zones perVSAN is 250 zones (two members per zone)
Table 13 NPV features limitations
Feature Verified limits Maximum limits
FLOGIs or F Disc per NPV port group 114 114
NPV switches per NPV core switch 105 105
FLOGIs per line card on NPV core switch 400 400
26 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
IPv6The management port on Cisco MDS switches supports oneuser-configured IPv6 address but does not supportauto-configuration of an IPv6 address
IP-ACL supportDo not apply IP-ACLs to only one member of a PortChannel groupApply IP-ACLs to the entire channel group
If IP-ACLs are already configured in a Gigabit Ethernet interface youcannot add this interface to a Ethernet PortChannel group
Refer to the Cisco MDS 9000 Family Configuration Guide
User RolesIn SAN-OS Release 33(x) and earlier when a user belongs to a rolewhich has a VSAN policy set to Deny and the role allows access to aspecific set of VSANs (for example 1 through 10) the user isrestricted from performing the configuration clear execute anddebug commands which had a VSAN parameter outside thisspecified set Beginning with NX-OS Release 41(1b) these users arestill prevented from performing configuration clear execute anddebug commands as before however they are allowed to performshow commands for all VSANs The ability to execute the showcommand addresses the following
In a network environment users often need to view informationin other VSANs even though they do not have permission tomodify configurations in those VSANs
This behavior makes Cisco MDS 9000 Series switches consistentwith other Cisco products such as Cisco Nexus 7000 Seriesswitches that exhibit the same behavior for those roles (whenthey apply to the VLAN policy)
27
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Using a RSA Version 1 Key for SSH Following an UpgradeFor security reasons NX-OS Release 42(x) and higher does notsupport RSA version 1 keys As a result if you upgrade from anearlier version that did support RSA version 1 keys and you hadconfigured a RSA version 1 key for SSH then you will not be able tolog in through SSH following the upgrade
If you have a RSA version 1 key configured for SSH beforeupgrading to NX-OS Release 42(x) or higher follow these steps
1 Disable SSH
2 Create RSA version 2 DSA keys
3 Enable SSH
4 Delete any RSA version 1 keys on any remote SSH clients andreplace the version 1 keys with the new version 2 keys from theswitch
Proceed with the upgrade to NX-OS Release 42(x) or higher
If you upgrade before disabling SSH and creating RSA version 2 keysfollow these steps
1 Open a Telnet session and log in through the console
2 Issue the no feature ssh command to disable SSH
3 Issue the ssh key rsa 1024 command to create RSA version 2 keys
4 Issue the feature ssh command to enable SSH
Applying Zone Configurations to VSAN 1In the setup script you can configure system default values for thedefault-zone to be permit or deny and you can configure defaultvalues for the zone distribution method and for the zone mode
These default settings are applied when a new VSAN is createdHowever the settings will not take effect on VSAN 1 because it existsprior to running the setup script Therefore when you need thosesettings for VSAN 1 you must explicitly issue the followingcommands
zone default-zone permit vsan 1 zoneset distribute full vsan 1 zone mode enhanced vsan 1
28 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
InterVSAN RoutingWhen using InterVSAN Routing (IVR) it is recommended to enableCisco Fabric Services (CFS) on all IVR-enabled switches Failure to doso may cause mismatched active zone sets if an error occurs duringzone set activation
RSPAN Traffic Not Supported on CTS Ports on 8-Gbps Switching ModulesAn inter-switch link (ISL) that is enabled for Cisco TrustSec (CTS)encryption must be brought up in non-CTS mode to support remoteSPAN (RSPAN) traffic on the following modules
DS-X9248-96K9 Cisco MDS 9000 48-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9224-96K9 Cisco MDS 9000 24-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9248-48K9 Cisco MDS 9000 444-Port Host-Optimized8-Gbps Fibre Channel Switching Module
If the ISL link is brought up with CTS enabled random packets dropsof both RSPAN traffic and normal traffic will occur on the receiverport switch
IO Accelerator Feature LimitationsIOA does not support the following NX-OS features
IVR flows
Devices with NPV and NPIV enabled
F port trunking
bull F port channeling
Support for FCIP Compression ModesIn Cisco NX-OS Release 42(1b) and higher FCIP compression mode 1and compression mode 3 are not supported on the Cisco MSM-184module and on the SSN-16 module
29
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Saving Copies of the Running Kickstart and System ImagesAfter you upgrade to MDS NX-OS Release 42(1b) or higher you arenot allowed to delete rename move or overwrite the kickstart andsystem images that are in the current system bootvar settings on anactive or standby MDS Supervisor-2 module on any Cisco MDS 9500Series switch This restriction does not apply to the integratedsupervisor module on the MDS 9200 and MDS 9100 series switches
Configuring Buffer Credits on a Generation 2 or Generation 3 ModuleWhen you configure port mode to auto or E on a Generation 2module one of the ports will not come up for the followingconfiguration
Port Mode auto or E for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E on a Generation 3module one or two of the ports will not come up for the followingconfiguration
Port Mode auto or E for the first half of the ports the second halfof the ports or for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E for all ports in the globalbuffer pool you need to reconfigure buffer credits on one or more ofthe ports The total number of buffer credits configured for all theports in the global buffer pool should be reduced by 64
Storage services module power budgetThe MDS 9509 does not have the power budget to run seven SSMcards EMC recommends a maximum of four SSMs in one 9509Customers wishing to use more than four SSMs in one chassis shouldrefer to the Cisco MDS 9000 documentation on the Ciscocom websiteto validate that there is enough power available for their desiredconfiguration
30 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Note Upgrading to the 3000 watt power supplies will alleviate thiscondition
iSCSI proxy initiator in Celerra HighRoad environmentsEMC supports the iSCSI proxy initiator feature in Celerrareg
HighRoadreg environments In proxy initiator mode one Fibre Channelinitiator is used for all iSCSI clients who access the switch via thesame iSCSI interface (iscsi33 for example)
The initiators will use the PWWN assigned to the iSCSI interface TheiSCSI interface to which an iSCSI client will logon to is configured inthe client and must be permitted by the virtual target configured forthat initiator
The current session environment supported on the MDS is
300 sessions per port 1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no InitialR2T=yes
Refer to the specific initiator support documentation on how to setthe parameters The implementation will not perform properly ifthese bits are not set
Refer to the MDS documentation for more information regarding theconfiguration of the iSCSI proxy initiator at the following Ciscowebsite
httpwwwciscocomenUSproducts
HPUX N_port IDThe N_port ID port value of 255 (0xFF) has special meaning forHP-UX A N_port ID (FC_ID) can not be returned from a switch thatcontains this value for the N_port ID (FC_ID) port value for a HP-UXinitiator or HP-UX target port Port ID value of 255 (0xFF) cannot be
31
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
configured for HP-UX initiator port and HP-UX target ports whenconfiguring MDS FC_IDs The port_ID value is the third byte of theFC_ID
Interoperability limitationsRefer to the EMC Support Matrix (ESM) and the EMC Networked Storage Topology Guide for modes of operation and caveats
NASBThe NASB feature requires that the backup application load the tapedrive with a compatible tape cartridge prior to configuring NASB inthe backup VSAN
Reserved VSAN Range and Isolated VSAN Range GuidelinesOn an NPV switch with a trunking configuration on any interface or ona regular switch where the feature fport_channel_trunk command hasbeen issued to enable the F PortChannel feature follow theseconfiguration guidelines for reserved VSANs and the isolated VSAN
bull If trunk mode is on for any of the interfaces or NP PortChannelis up the reserved VSANs are 3040 to 4078 and they are notavailable for user configuration
bull The Exchange Virtual Fabric Protocol (EVFP) isolated VSAN is4079 and it is not available for user configuration
bull VSAN 4079 will be impacted by an upgrade to NX-OS Release42(3) depending on whether or not VSAN 4079 was createdprior to the upgrade See theldquoUpgrading Effect on VSAN 4079rdquoon page 17
The following VSAN IDs are assigned in the Fibre Channel Framingand Signaling (FC-FS) interface standard
VF_ID Value Value Description
00h Do not use as a Virtual FabricIdentifier
001h EFFh Available as a Virtual FabricIdentifier
F00h FEEh Reserved
32 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Symmetrix VMax limitationsAt the time of this writing the following features are not supportedfor use with the Symmetrix VMax
FCIP Write Acceleration
The NX-OS IOA functionality is only supported with the Q2 SREnginuity release 5874229182 or higher
For the most up to date status please refer to the current revision ofthese Release Notes on httpPowerlinkemccom and the EMCSupport Matrix available through E-Lab Interoperability Navigator (ELN) athttpelabnavigatorEMCcom
Storage Applications on the MSM-184The MDS 9000 184-Port Multiservice Module (MSM-184) does notsupport multiple concurrent storage applications Only oneapplication can run on the MSM-184 at a time
Downgrading with fport-channel-trunk enabledIf you are running MDS NX-OS Release 42(x) or higher with thefport-channel-trunk feature enabled and you downgrade to anyNX-OS 41(1x) release the installer performs a nondisruptivedowngrade even though the fport-channel-trunk feature is notsupported in NX-OS 41(1x) releases
As a result the switch is in an inconsistent state and the ports maynot function properly
FEFh Control VF-ID (see FibreChannel Link Services (FC-LS)and Fibre Channel SwitchFabric Generation 4 (FC-SW-4)standards)
FF0h FFEh Vendor specific
FFFh Do not use as a Virtual FabricIdentifier
FEFh = 4079
33
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
If you are in this state a workaround is to reboot the switch followingthe upgrade
LDAP AuthenticationThere is currently a limitation in the LDAP server configuration CLIthat prevents the use of an OU with spaces in the name Normallythese OU names could be surrounded by quotation marks howeverquotation marks are not supported by the ldap-server command
MDS-9148 limitationsThe Cisco MDS 9148 Multilayer Fabric Switch does not support thefollowing NX-OS features
Medium and Long range 4GB Agilent
IVR
Remote Span
Translative loop support
FCC - no generation quench reaction only
FC-Redirect
In addition the following features have these limits
VSANS - 31 maximum
SPAN - 1 session maximum
Technical notesThe following sections provide further information on technicalnotes
EMC Email Home for Cisco MDS switchesInstallation and Trouble shooting instructions can be found in thedocumentation located at the EMC Customer Service Internalwebsite
httpwwwcsisusemccomcsweb2esnesnhomehtmConnectrix20MDS20900020Family
34 EMC Connectrix MDS 9000 NX-OS Release Notes
Technical notes
Customers requiring installation of this solution should contact theirEMC Customer Engineer to assist with the installation and providethe documentation
Supported iSCSI sessionsThe current iSCSI session environment supported on the MDS is
300 sessions per port
1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no
InitialR2T=yes
Upgrading Cisco SAN-OSThere are several methods available for upgrading SAN-OS SoftwareEMC personnel are strongly recommended that all upgrades be doneby the Automated One-Step Upgrade using the install all
command EMC personnel should refer to the Connectrix MDS 9000Family Software Image Upgrade Instructions for a complete list ofprerequisites and instructions for performing the upgrade Thisdocument along with tftp software is available on the GlobalServices website at httpwwwcsisusEMCcom under ApplicationDownload Area ESN Product Information Connectrix MDS 9000Family
The Software Upgrade Wizard is an option for upgrades While theinstall all is the preferred method the Software Install Wizard canalso be used
Supported configuration parametersFor the most up-to-date information refer to the EMC Support Matrixavailable through E-Lab Interoperability Navigator athttpelabnavigatoremccom for the latest information onsupported configurations
35
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
Supported zoning parametersRefer to the EMC Networked Storage Topology Guide for the mostup-to-date information on supported zoning parameters
At the time these notes were published the following parameterswere supported
20 VSANs 5 Hops 2000 Unique members per physical infrastructure 1000 Zonesets per physical infrastructure 2000 Zones per physical infrastructure 1 FCIP tunnel
Supported IVR parameters IVR zone members 1000 IVR zones 1000 IVR zone sets 32 VSANS 20 IVR enabled switches 64
An RPQ can be submitted for any configurations that exceed thislimit
Managing zone changes in multiswitch fabricsZoning changes may be made through Fabric Manager or CLI Whenaccessing Fabric Manager or CLI the user does so from the point ofview of one switch That is Fabric Manager and CLI are accessed byentering the IP address of one switch in the fabric
When zoning changes are made the applicable VSAN and zone setdata is propagated to the rest of the switches in the fabric via the ISLs
When zoning changes are made to a VSAN the zone set data ispropagated to the rest of the switches in the fabric via the ISLs Bydefault only the active zone set information is relayed to all switchesin the VSAN If the user accesses the Fabric Manager and CLI fromanother switch in the fabric the new VSAN and zone set informationwill not be viewable To view the active and inactive zone set on theother switches in the fabric the user must log in to the CLI and issuea command from the EXEC prompt
36 EMC Connectrix MDS 9000 NX-OS Release Notes
Documentation
Example The following is an example of copying VSAN 1 through 20 zoningdata
CiscoMDS_name zone copy active full vsan 1-20
CiscoMDS_name conf t
Enter configuration commands one per line End with CNTL Z
CiscoMDS_name(config) zoneset distribute full vsan 1-20
CiscoMDS_name(config)
Note This command needs to be issued on all switches in the fabric one timeonly
This is a nondisruptive command After issuing the commands theuser will now see the active and inactive zone sets for the specifiedVSANs on any switch that is chosen from which to manage the fabric
After a zoning change is made save the running configuration to thestartup configuration
DocumentationSend documentation comments to mdsfeedback-doccom
Product DocumentationAs of NX-OS Release 42(1a) software configuration information isavailable in new feature-specific configuration guides for thefollowing information
System management
Interfaces
Fabric
Quality of service
Security
IP services
High availability and redundancy
37
Software media organization and files
EMC Connectrix MDS 9000 NX-OS Release Notes
The information in these new guides previously existed in the CiscoMDS 9000 Family CLI Configuration Guide That configuration guideremains available on Ciscocom and should be used for all softwarereleases prior to NX-OS Release 42(1a) Configuration guidesaddress the features introduced in or available in a particular releaseSelect and view the configuration guide that pertains to the softwareinstalled in your switch
In addition Fabric Manager information has been removed from theMDS NX-OS Release Notes (this document) and placed intostandalone Fabric Manager Release Notes that support both CiscoMDS 9000 Family switches and Cisco Nexus 5000 Series switchesThe Cisco Fabric Manager Release Notes are available onhttpPowerlinkemccom and from the following website
httpwwwciscocomenUSpartnerproductsps10495prod_release_notes_listhtml
Technical supportThese release notes complement a Cisco documentation set EachCisco document refers to where to get help However for any itemssupplied by EMC see ldquoTroubleshooting and getting helprdquo onpage 38
Software media organization and filesFor information on related software environment and systemrequirements refer to the EMC Support Matrix on EMC Powerlink at
httpPowerlinkEMCcom
InstallationFor hardware installation information refer to the Cisco MDS HWInstallation Guides available at Ciscocom
For EMC-specific installation information refer to ldquoEnvironment andsystem requirementsrdquo on page 5 in this document
38 EMC Connectrix MDS 9000 NX-OS Release Notes
Troubleshooting and getting help
Troubleshooting and getting helpEMC support product and licensing information can be obtained asfollows
Product information mdash For documentation release notes softwareupdates or for information about EMC products licensing andservice go to the EMC Powerlink website (registration required) at
httpPowerlinkEMCcom
Technical support mdash For technical support go to EMC CustomerService on Powerlink To open a service request through Powerlinkyou must have a valid support agreement Please contact your EMCsales representative for details about obtaining a valid supportagreement or to answer any questions about your account
Copyright copy 2011 EMC Corporation All rights reserved
EMC believes the information in this publication is accurate as of its publication date The information issubject to change without notice
THE INFORMATION IN THIS PUBLICATION IS PROVIDED ldquoAS ISrdquo EMC CORPORATION MAKES NOREPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION INTHIS PUBLICATION AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OFMERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Use copying and distribution of any EMC software described in this publication requires an applicablesoftware license
For the most up-to-date regulatory document for your product line go to the Technical Documentation andAdvisories section on EMC Powerlink
For the most up-to-date listing of EMC product names see EMC Corporation Trademarks on EMCcom
All other trademarks used herein are the property of their respective owners
16 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Note The software upgrade information in Table 7 applies only to FibreChannel switching traffic Upgrading system software disrupts IP traffic andSSM intelligent services traffic
MDS NX-OS Release 50(4b) is not a FICON-qualified release
Table 7 Nondisruptive Upgrade Path to Cisco MDS NX-OS Release 50(4b)
Current Nondisruptive Upgrade Path
NX-OS 50(4) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 50(1a) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(7b) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(5) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(3) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(1b) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 42(1a) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 41(3a) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
NX-OS 41(1b) You can nondisruptively upgrade directly to NX-OS Release 50(4b)
SAN-OS 33(4a) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
NX-OS 33(4) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 33(3) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 33(2) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 33(1c) Upgrade to NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 32(3a) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 32(2c) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 32(1a) Upgrade to SAN-OS Release then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 31(3a) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
SAN-OS 31(2) Upgrade to SAN-OS Release 33(x) then NX-OS 4x and then upgrade to NX-OS Release 50(4b)
17
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Use Table 8 to determine your FICON nondisruptive upgrade path toCisco MDS NX-OS Release 42(7b) Find the image release numberyou are currently using in the Current Release with FICON Enabledcolumn of the table and use the path recommended
Note For more information on the FICON qualified NX-OS releases refer tothe EMC Support Matrix available through E-Lab Interoperability Navigator(ELN) at httpelabnavigatorEMCcom
Upgrading Effect on VSAN 4079If you are upgrading to NX-OS Release 50(4b) and you have notcreated VSAN 4079 the NX-OS software will automatically createVSAN 4079 and reserve it for EVFP use If VSAN 4079 is reserved forEVFP use the switchport trunk allowed vsan command will filterout VSAN 4079 from the allowed list as shown in the followingexample
switch(config-if) switchport trunk allowed vsan1-40801-40784080switch(config-if)
If you have created VSAN 4079 the upgrade to NX-OS Release50(4b) will have no affect on VSAN 4079
If you downgrade to a release of NX-OS lower than 41(x) afterNX-OS Release 50(4b) creates VSAN 4079 and reserves it for EVFPuse the VSAN will no longer be reserved
Table 8 FICON Nondisruptive Upgrade Path to NX-OS Release 42(7b)
Current Release withFICON Enabled Upgrade Path
NX-OS 42(1b) You can nondisruptively upgrade directly to NX-OS Release 42(7b)
NX-OS 41(1c) You can nondisruptively upgrade directly to NX-OS Release 42(7b)
SAN-OS 33(1c) You can nondisruptively upgrade directly to NX-OS Release 42(7b)
18 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Upgrading a Cisco MDS 9124 or MDS 9134 switchIf you are upgrading from Cisco MDS SAN-OS Release 31(1) to CiscoNX-OS Release 4x before upgrading to NX-OS Release 50(4b) on aCisco MDS 9124 or MDS 9134 switch follow these guidelines
During the upgrade configuration is not allowed and the fabric isexpected to be stable
The Fabric Shortest Path First (FSPF) timers must be configured tothe default value of 20 seconds otherwise the nondisruptiveupgrade is blocked to ensure that the maximum down toim forthe control plane can be 80 seconds
If there are any CFS commits in the fabric the nondisruptiveupgrade will fail
If there is a zone server merge in progress in the fabric thenondisruptive upgrde will fail
If a service terminates the nondisruptive upgrade the showinstall all failure-reason command can display the reason thatthe nondisruptive upgrade cannot proceed
If there is not enough memory in the system to load the newimages the upgrade will be made disruptive due to insufficientresources and the user will be notified in the compativility table
MDS 9500 series upgrades with active IOA flowsWhen upgading an MDS 9500 series switch that has active IOA flowsthose flows may be interrupted during the supervisor moduleswitchover To workaround this issue you have to enablespanning-tree portfast on the interface on the catalyst connected tothe management interface of the activestandby supervisor for theinterface to come up fast without causing the cluster to lose quorum
Downgrading Your Cisco MDS SAN-OS Software ImageThis section lists the guidelines recommended for downgrading yourCisco MDS SAN-OS software image and includes the followingtopics
ldquoGeneral downgrading guidelinesrdquo on page 19
19
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
General downgrading guidelinesUse the following guidelines to nondisruptively downgrade yourCisco MDS NX-OS Release 50(4b)
Install and configure dual supervisor modules
Issue the system no acl-adjacency-sharing execute command todisable acl adjacency usage on Generation 2 and Generation 1modules If this command fails reduce the number of zones IVRzones TE ports or a combination of these in the system and issuethe command again
Disable all features not supported by the downgrade release Usethe show incompatibility system downgrade-image command todetermine what you need to disable
bull If you are running in interoperability mode two such featuresare the Reliable Commit Service and Full Zone DatabaseDistribution They can be disabled by running thesecommand in config term mode
no zone rcs enableno zoneset capability distribute full
Use the show install all impact downgrade-image command todetermine if your downgrade will be nondisruptive
Be aware that some features impact whether a downgrade isdisruptive or nondisruptive
bull Fibre Channel Ports Traffic on Fibre Channel ports can benondisruptively downgraded See Table 9 on page 20 for thenondisruptive downgrade path for all SAN-OS releases
bull Storage Services Intelligent storage services traffic such asSANTap NASB and FC write acceleration is disruptedduring a downgrade Fibre Channel traffic is not
bull Gigabit Ethernet Ports Traffic on Gigabit Ethernet ports isdisrupted during a downgrade This includes the GigabitEthernet ports on the MSM-184 module and the MDS 9222iswitch Those nodes that are members of VSANs traversing anFCIP ISL are impacted and a fabric reconfiguration occursiSCSI initiators connected to the Gigabit Ethernet ports loseconnectivity to iSCSI targets while the downgrade is inprogress
20 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
bull FICON If you have FICON enabled the downgrade path isdifferent See Table 10 on page 21
Note A downgrade from NX-OS Release 4x to SAN-OS Release 33(1c) is notsupported on MDS switches when FC-Redirect based applications such asData Mobility Manager or Storage Media Encryption are configured in thefabric if either of the following conditions are satisfied
1 A target for which FC-Redirect is configured is connected locally and thereare Generation 1 modules with ISLs configured in the switch
2 A host for which FC-redirect is configured is connected locally ona Generation 1 module
If these conditions exist remove the application configuration forthese targets and hosts before proceeding with the downgrade
Use Table 9 on page 20 to determine the nondisruptive downgradepath from Cisco NX-OS Release 50(4b) Find the NX-OS or SAN-OSimage you want to downgrade to in the To SAN-OSNX-OS Releasecolumn of the table and use the path recommended
Note The software downgrade information in Table 10 on page 21 appliesonly to Fibre Channel switching traffic Downgrading system softwaredisrupts IP and SSM intelligent services traffic
Table 9 Nondisruptive Downgrade Path from NX-OS Release 50(4b) (page 1 of2)
To SAN-OS NX-OSRelease Nondisruptive Downgrade Path
NX-OS 50(4) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 50(1a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(7b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(5) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(3) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(1b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(1a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 41(3a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
21
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Use Table 10 to determine your nondisruptive downgrade path if youhave FICON enabled from Cisco NX-OS Release 42(7b) Find the imagerelease number you are currently using in the Current Release withFICON Enabled column of the table and use the path recommended
NX-OS 41(1b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
SAN-OS 33(5a) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33())
SAN-OS 33(5) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(4a) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
NX-OS 33(4) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(3) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
NX-OS 33(2) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(1c) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 32(3a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 32(x)
SAN-OS 32(2c) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 32(x)
SAN-OS 32(1a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
SAN-OS 31(3a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
SAN-OS 31(2) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
Table 9 Nondisruptive Downgrade Path from NX-OS Release 50(4b) (page 2 of2)
To SAN-OS NX-OSRelease Nondisruptive Downgrade Path
Table 10 FICON Downgrade Path from NX-OS Release 42(7b)
To SAN-OSNX-OS Release withFICON Enabled Downgrade Path
NX-OS 42(1b) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
NX-OS 41(1c) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
SAN-OS 33(1c) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
22 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Best practicesLog messages are not saved across system reboots or power outagesTherefore EMC recommends that customers configure a SyslogServer in order to redirect and capture all log messages on a remoteserver For more information please refer to the Cisco MDS 9000Family Configuration Guide available at
httpwwwciscocomenUSproductsps5989products_support_series_homehtml
Maximum ports per chassisTable 11 shows the maximum ports per chassis
a V2 indicates a 9506 or 9509 with Generation-2 Supervisors The presence of anygeneration one module in a switch will limit the maximum port count to 252This includes the 16-port 32-port 14+2 IPS4 and IPS8 cards
Known problems and limitationsFor a list of problems with this release please refer to the CiscoRelease notes located at
httpwwwciscocomenUSproductsps5989prod_release_notes_listhtml
Limitations and restrictionsThe following limitations and restrictions apply to all switches in theCisco MDS 9000 Family unless a limitation for a specific switch isstated
ldquoStorage Media Encryption (SME) limitationsrdquo on page 24
Table 11 Maximum ports per chassis
Chassis Maximum number of ports
MDS 9506-V2 192a
MDS 9509-V2 336
MDS 9513 528
23
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
ldquoSME configuration limitsrdquo on page 24
ldquoDeleting Cisco SME interfacesrdquo on page 25
ldquoCisco MDS 9124 and 9134 Multilayer fabric switchesrdquo on page 25
ldquoN-Port virtualization configuration limitsrdquo on page 25
ldquoMaximum number of zones supported in Interop Mode 4rdquo onpage 25
ldquoIPv6rdquo on page 26
ldquoIP-ACL supportrdquo on page 26
ldquoUser Rolesrdquo on page 26
ldquoUsing a RSA Version 1 Key for SSH Following an Upgraderdquo onpage 27
ldquoApplying Zone Configurations to VSAN 1rdquo on page 27
ldquoInterVSAN Routingrdquo on page 28
ldquoRSPAN Traffic Not Supported on CTS Ports on 8-GbpsSwitching Modulesrdquo on page 28
ldquoIO Accelerator Feature Limitationsrdquo on page 28
ldquoSupport for FCIP Compression Modesrdquo on page 28
ldquoSaving Copies of the Running Kickstart and System Imagesrdquo onpage 29
ldquoConfiguring Buffer Credits on a Generation 2 or Generation 3Modulerdquo on page 29
ldquoStorage services module power budgetrdquo on page 29
ldquoiSCSI proxy initiator in Celerra HighRoad environmentsrdquo onpage 30
ldquoHPUX N_port IDrdquo on page 30
ldquoInteroperability limitationsrdquo on page 31
ldquoNASBrdquo on page 31
ldquoReserved VSAN Range and Isolated VSAN Range Guidelinesrdquoon page 31
ldquoSymmetrix VMax limitationsrdquo on page 32
ldquoStorage Applications on the MSM-184rdquo on page 32
ldquoDowngrading with fport-channel-trunk enabledrdquo on page 32
ldquoLDAP Authenticationrdquo on page 33
24 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
ldquoMDS-9148 limitationsrdquo on page 33
Storage Media Encryption (SME) limitationsAn SME node can only belong to one cluster Adding the node tomore than one cluster will cause problems
Currently there is no prevention or warning in place when an attemptis made to add a node to multiple clusters
SME configuration limitsTable 12 lists the SME configuration limits for this release
Table 12 SME configuration limits
Configuration Limits
Number of switches in the fabric 10
Number of clusters per switch 1
Switches in a cluster 4
Fabrics in a cluster 2
Modules in a switch 11
Cisco MSM-184 modules in a cluster 32
Initiator-Target-LUNs (ITLs) 1024
LUNs behind a target 32
Host and target ports in a cluster 128
Number of hosts per target 128
Tape backup groups per cluster 2
Volume groups in a tape backup group 4
Cisco Key Management Center ( of keys) 32K
Targets per switch that can be FC-redirected 32
25
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Deleting Cisco SME interfacesA Cisco SME interface can be deleted from the cluster only after theinterface is administratively shut-down and all related tasksassociated with the interface shut-down are complete
Cisco MDS 9124 and 9134 Multilayer fabric switchesThe Cisco MDS 9124 and 9134 Multilayer fabric switches do notsupport the following Cisco MDS SAN-OS features
IVR Remote Span Translative loop support FCCmdash no generation quench reaction only
In addition the following features have these limits
VSANs mdash 16 maximum SPAN mdash 1 session maximum
N-Port virtualization configuration limitsThe NPV features have maximum configuration limits Table 13shows the verified and maximum limits for the NPV switchesrunning NX-OS Release 5x
Maximum number of zones supported in Interop Mode 4In interop mode 4 the maximum number of zones that is supportedin an active zone set is 2047 due to limitations in the connectedvendor switch When IVR is used in interop mode 4 the maximumnumber of zones supported including IVR zones in the active zoneset is 2047 The limit for the maximum number of IVR zones perVSAN is 250 zones (two members per zone)
Table 13 NPV features limitations
Feature Verified limits Maximum limits
FLOGIs or F Disc per NPV port group 114 114
NPV switches per NPV core switch 105 105
FLOGIs per line card on NPV core switch 400 400
26 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
IPv6The management port on Cisco MDS switches supports oneuser-configured IPv6 address but does not supportauto-configuration of an IPv6 address
IP-ACL supportDo not apply IP-ACLs to only one member of a PortChannel groupApply IP-ACLs to the entire channel group
If IP-ACLs are already configured in a Gigabit Ethernet interface youcannot add this interface to a Ethernet PortChannel group
Refer to the Cisco MDS 9000 Family Configuration Guide
User RolesIn SAN-OS Release 33(x) and earlier when a user belongs to a rolewhich has a VSAN policy set to Deny and the role allows access to aspecific set of VSANs (for example 1 through 10) the user isrestricted from performing the configuration clear execute anddebug commands which had a VSAN parameter outside thisspecified set Beginning with NX-OS Release 41(1b) these users arestill prevented from performing configuration clear execute anddebug commands as before however they are allowed to performshow commands for all VSANs The ability to execute the showcommand addresses the following
In a network environment users often need to view informationin other VSANs even though they do not have permission tomodify configurations in those VSANs
This behavior makes Cisco MDS 9000 Series switches consistentwith other Cisco products such as Cisco Nexus 7000 Seriesswitches that exhibit the same behavior for those roles (whenthey apply to the VLAN policy)
27
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Using a RSA Version 1 Key for SSH Following an UpgradeFor security reasons NX-OS Release 42(x) and higher does notsupport RSA version 1 keys As a result if you upgrade from anearlier version that did support RSA version 1 keys and you hadconfigured a RSA version 1 key for SSH then you will not be able tolog in through SSH following the upgrade
If you have a RSA version 1 key configured for SSH beforeupgrading to NX-OS Release 42(x) or higher follow these steps
1 Disable SSH
2 Create RSA version 2 DSA keys
3 Enable SSH
4 Delete any RSA version 1 keys on any remote SSH clients andreplace the version 1 keys with the new version 2 keys from theswitch
Proceed with the upgrade to NX-OS Release 42(x) or higher
If you upgrade before disabling SSH and creating RSA version 2 keysfollow these steps
1 Open a Telnet session and log in through the console
2 Issue the no feature ssh command to disable SSH
3 Issue the ssh key rsa 1024 command to create RSA version 2 keys
4 Issue the feature ssh command to enable SSH
Applying Zone Configurations to VSAN 1In the setup script you can configure system default values for thedefault-zone to be permit or deny and you can configure defaultvalues for the zone distribution method and for the zone mode
These default settings are applied when a new VSAN is createdHowever the settings will not take effect on VSAN 1 because it existsprior to running the setup script Therefore when you need thosesettings for VSAN 1 you must explicitly issue the followingcommands
zone default-zone permit vsan 1 zoneset distribute full vsan 1 zone mode enhanced vsan 1
28 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
InterVSAN RoutingWhen using InterVSAN Routing (IVR) it is recommended to enableCisco Fabric Services (CFS) on all IVR-enabled switches Failure to doso may cause mismatched active zone sets if an error occurs duringzone set activation
RSPAN Traffic Not Supported on CTS Ports on 8-Gbps Switching ModulesAn inter-switch link (ISL) that is enabled for Cisco TrustSec (CTS)encryption must be brought up in non-CTS mode to support remoteSPAN (RSPAN) traffic on the following modules
DS-X9248-96K9 Cisco MDS 9000 48-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9224-96K9 Cisco MDS 9000 24-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9248-48K9 Cisco MDS 9000 444-Port Host-Optimized8-Gbps Fibre Channel Switching Module
If the ISL link is brought up with CTS enabled random packets dropsof both RSPAN traffic and normal traffic will occur on the receiverport switch
IO Accelerator Feature LimitationsIOA does not support the following NX-OS features
IVR flows
Devices with NPV and NPIV enabled
F port trunking
bull F port channeling
Support for FCIP Compression ModesIn Cisco NX-OS Release 42(1b) and higher FCIP compression mode 1and compression mode 3 are not supported on the Cisco MSM-184module and on the SSN-16 module
29
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Saving Copies of the Running Kickstart and System ImagesAfter you upgrade to MDS NX-OS Release 42(1b) or higher you arenot allowed to delete rename move or overwrite the kickstart andsystem images that are in the current system bootvar settings on anactive or standby MDS Supervisor-2 module on any Cisco MDS 9500Series switch This restriction does not apply to the integratedsupervisor module on the MDS 9200 and MDS 9100 series switches
Configuring Buffer Credits on a Generation 2 or Generation 3 ModuleWhen you configure port mode to auto or E on a Generation 2module one of the ports will not come up for the followingconfiguration
Port Mode auto or E for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E on a Generation 3module one or two of the ports will not come up for the followingconfiguration
Port Mode auto or E for the first half of the ports the second halfof the ports or for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E for all ports in the globalbuffer pool you need to reconfigure buffer credits on one or more ofthe ports The total number of buffer credits configured for all theports in the global buffer pool should be reduced by 64
Storage services module power budgetThe MDS 9509 does not have the power budget to run seven SSMcards EMC recommends a maximum of four SSMs in one 9509Customers wishing to use more than four SSMs in one chassis shouldrefer to the Cisco MDS 9000 documentation on the Ciscocom websiteto validate that there is enough power available for their desiredconfiguration
30 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Note Upgrading to the 3000 watt power supplies will alleviate thiscondition
iSCSI proxy initiator in Celerra HighRoad environmentsEMC supports the iSCSI proxy initiator feature in Celerrareg
HighRoadreg environments In proxy initiator mode one Fibre Channelinitiator is used for all iSCSI clients who access the switch via thesame iSCSI interface (iscsi33 for example)
The initiators will use the PWWN assigned to the iSCSI interface TheiSCSI interface to which an iSCSI client will logon to is configured inthe client and must be permitted by the virtual target configured forthat initiator
The current session environment supported on the MDS is
300 sessions per port 1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no InitialR2T=yes
Refer to the specific initiator support documentation on how to setthe parameters The implementation will not perform properly ifthese bits are not set
Refer to the MDS documentation for more information regarding theconfiguration of the iSCSI proxy initiator at the following Ciscowebsite
httpwwwciscocomenUSproducts
HPUX N_port IDThe N_port ID port value of 255 (0xFF) has special meaning forHP-UX A N_port ID (FC_ID) can not be returned from a switch thatcontains this value for the N_port ID (FC_ID) port value for a HP-UXinitiator or HP-UX target port Port ID value of 255 (0xFF) cannot be
31
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
configured for HP-UX initiator port and HP-UX target ports whenconfiguring MDS FC_IDs The port_ID value is the third byte of theFC_ID
Interoperability limitationsRefer to the EMC Support Matrix (ESM) and the EMC Networked Storage Topology Guide for modes of operation and caveats
NASBThe NASB feature requires that the backup application load the tapedrive with a compatible tape cartridge prior to configuring NASB inthe backup VSAN
Reserved VSAN Range and Isolated VSAN Range GuidelinesOn an NPV switch with a trunking configuration on any interface or ona regular switch where the feature fport_channel_trunk command hasbeen issued to enable the F PortChannel feature follow theseconfiguration guidelines for reserved VSANs and the isolated VSAN
bull If trunk mode is on for any of the interfaces or NP PortChannelis up the reserved VSANs are 3040 to 4078 and they are notavailable for user configuration
bull The Exchange Virtual Fabric Protocol (EVFP) isolated VSAN is4079 and it is not available for user configuration
bull VSAN 4079 will be impacted by an upgrade to NX-OS Release42(3) depending on whether or not VSAN 4079 was createdprior to the upgrade See theldquoUpgrading Effect on VSAN 4079rdquoon page 17
The following VSAN IDs are assigned in the Fibre Channel Framingand Signaling (FC-FS) interface standard
VF_ID Value Value Description
00h Do not use as a Virtual FabricIdentifier
001h EFFh Available as a Virtual FabricIdentifier
F00h FEEh Reserved
32 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Symmetrix VMax limitationsAt the time of this writing the following features are not supportedfor use with the Symmetrix VMax
FCIP Write Acceleration
The NX-OS IOA functionality is only supported with the Q2 SREnginuity release 5874229182 or higher
For the most up to date status please refer to the current revision ofthese Release Notes on httpPowerlinkemccom and the EMCSupport Matrix available through E-Lab Interoperability Navigator (ELN) athttpelabnavigatorEMCcom
Storage Applications on the MSM-184The MDS 9000 184-Port Multiservice Module (MSM-184) does notsupport multiple concurrent storage applications Only oneapplication can run on the MSM-184 at a time
Downgrading with fport-channel-trunk enabledIf you are running MDS NX-OS Release 42(x) or higher with thefport-channel-trunk feature enabled and you downgrade to anyNX-OS 41(1x) release the installer performs a nondisruptivedowngrade even though the fport-channel-trunk feature is notsupported in NX-OS 41(1x) releases
As a result the switch is in an inconsistent state and the ports maynot function properly
FEFh Control VF-ID (see FibreChannel Link Services (FC-LS)and Fibre Channel SwitchFabric Generation 4 (FC-SW-4)standards)
FF0h FFEh Vendor specific
FFFh Do not use as a Virtual FabricIdentifier
FEFh = 4079
33
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
If you are in this state a workaround is to reboot the switch followingthe upgrade
LDAP AuthenticationThere is currently a limitation in the LDAP server configuration CLIthat prevents the use of an OU with spaces in the name Normallythese OU names could be surrounded by quotation marks howeverquotation marks are not supported by the ldap-server command
MDS-9148 limitationsThe Cisco MDS 9148 Multilayer Fabric Switch does not support thefollowing NX-OS features
Medium and Long range 4GB Agilent
IVR
Remote Span
Translative loop support
FCC - no generation quench reaction only
FC-Redirect
In addition the following features have these limits
VSANS - 31 maximum
SPAN - 1 session maximum
Technical notesThe following sections provide further information on technicalnotes
EMC Email Home for Cisco MDS switchesInstallation and Trouble shooting instructions can be found in thedocumentation located at the EMC Customer Service Internalwebsite
httpwwwcsisusemccomcsweb2esnesnhomehtmConnectrix20MDS20900020Family
34 EMC Connectrix MDS 9000 NX-OS Release Notes
Technical notes
Customers requiring installation of this solution should contact theirEMC Customer Engineer to assist with the installation and providethe documentation
Supported iSCSI sessionsThe current iSCSI session environment supported on the MDS is
300 sessions per port
1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no
InitialR2T=yes
Upgrading Cisco SAN-OSThere are several methods available for upgrading SAN-OS SoftwareEMC personnel are strongly recommended that all upgrades be doneby the Automated One-Step Upgrade using the install all
command EMC personnel should refer to the Connectrix MDS 9000Family Software Image Upgrade Instructions for a complete list ofprerequisites and instructions for performing the upgrade Thisdocument along with tftp software is available on the GlobalServices website at httpwwwcsisusEMCcom under ApplicationDownload Area ESN Product Information Connectrix MDS 9000Family
The Software Upgrade Wizard is an option for upgrades While theinstall all is the preferred method the Software Install Wizard canalso be used
Supported configuration parametersFor the most up-to-date information refer to the EMC Support Matrixavailable through E-Lab Interoperability Navigator athttpelabnavigatoremccom for the latest information onsupported configurations
35
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
Supported zoning parametersRefer to the EMC Networked Storage Topology Guide for the mostup-to-date information on supported zoning parameters
At the time these notes were published the following parameterswere supported
20 VSANs 5 Hops 2000 Unique members per physical infrastructure 1000 Zonesets per physical infrastructure 2000 Zones per physical infrastructure 1 FCIP tunnel
Supported IVR parameters IVR zone members 1000 IVR zones 1000 IVR zone sets 32 VSANS 20 IVR enabled switches 64
An RPQ can be submitted for any configurations that exceed thislimit
Managing zone changes in multiswitch fabricsZoning changes may be made through Fabric Manager or CLI Whenaccessing Fabric Manager or CLI the user does so from the point ofview of one switch That is Fabric Manager and CLI are accessed byentering the IP address of one switch in the fabric
When zoning changes are made the applicable VSAN and zone setdata is propagated to the rest of the switches in the fabric via the ISLs
When zoning changes are made to a VSAN the zone set data ispropagated to the rest of the switches in the fabric via the ISLs Bydefault only the active zone set information is relayed to all switchesin the VSAN If the user accesses the Fabric Manager and CLI fromanother switch in the fabric the new VSAN and zone set informationwill not be viewable To view the active and inactive zone set on theother switches in the fabric the user must log in to the CLI and issuea command from the EXEC prompt
36 EMC Connectrix MDS 9000 NX-OS Release Notes
Documentation
Example The following is an example of copying VSAN 1 through 20 zoningdata
CiscoMDS_name zone copy active full vsan 1-20
CiscoMDS_name conf t
Enter configuration commands one per line End with CNTL Z
CiscoMDS_name(config) zoneset distribute full vsan 1-20
CiscoMDS_name(config)
Note This command needs to be issued on all switches in the fabric one timeonly
This is a nondisruptive command After issuing the commands theuser will now see the active and inactive zone sets for the specifiedVSANs on any switch that is chosen from which to manage the fabric
After a zoning change is made save the running configuration to thestartup configuration
DocumentationSend documentation comments to mdsfeedback-doccom
Product DocumentationAs of NX-OS Release 42(1a) software configuration information isavailable in new feature-specific configuration guides for thefollowing information
System management
Interfaces
Fabric
Quality of service
Security
IP services
High availability and redundancy
37
Software media organization and files
EMC Connectrix MDS 9000 NX-OS Release Notes
The information in these new guides previously existed in the CiscoMDS 9000 Family CLI Configuration Guide That configuration guideremains available on Ciscocom and should be used for all softwarereleases prior to NX-OS Release 42(1a) Configuration guidesaddress the features introduced in or available in a particular releaseSelect and view the configuration guide that pertains to the softwareinstalled in your switch
In addition Fabric Manager information has been removed from theMDS NX-OS Release Notes (this document) and placed intostandalone Fabric Manager Release Notes that support both CiscoMDS 9000 Family switches and Cisco Nexus 5000 Series switchesThe Cisco Fabric Manager Release Notes are available onhttpPowerlinkemccom and from the following website
httpwwwciscocomenUSpartnerproductsps10495prod_release_notes_listhtml
Technical supportThese release notes complement a Cisco documentation set EachCisco document refers to where to get help However for any itemssupplied by EMC see ldquoTroubleshooting and getting helprdquo onpage 38
Software media organization and filesFor information on related software environment and systemrequirements refer to the EMC Support Matrix on EMC Powerlink at
httpPowerlinkEMCcom
InstallationFor hardware installation information refer to the Cisco MDS HWInstallation Guides available at Ciscocom
For EMC-specific installation information refer to ldquoEnvironment andsystem requirementsrdquo on page 5 in this document
38 EMC Connectrix MDS 9000 NX-OS Release Notes
Troubleshooting and getting help
Troubleshooting and getting helpEMC support product and licensing information can be obtained asfollows
Product information mdash For documentation release notes softwareupdates or for information about EMC products licensing andservice go to the EMC Powerlink website (registration required) at
httpPowerlinkEMCcom
Technical support mdash For technical support go to EMC CustomerService on Powerlink To open a service request through Powerlinkyou must have a valid support agreement Please contact your EMCsales representative for details about obtaining a valid supportagreement or to answer any questions about your account
Copyright copy 2011 EMC Corporation All rights reserved
EMC believes the information in this publication is accurate as of its publication date The information issubject to change without notice
THE INFORMATION IN THIS PUBLICATION IS PROVIDED ldquoAS ISrdquo EMC CORPORATION MAKES NOREPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION INTHIS PUBLICATION AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OFMERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Use copying and distribution of any EMC software described in this publication requires an applicablesoftware license
For the most up-to-date regulatory document for your product line go to the Technical Documentation andAdvisories section on EMC Powerlink
For the most up-to-date listing of EMC product names see EMC Corporation Trademarks on EMCcom
All other trademarks used herein are the property of their respective owners
17
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Use Table 8 to determine your FICON nondisruptive upgrade path toCisco MDS NX-OS Release 42(7b) Find the image release numberyou are currently using in the Current Release with FICON Enabledcolumn of the table and use the path recommended
Note For more information on the FICON qualified NX-OS releases refer tothe EMC Support Matrix available through E-Lab Interoperability Navigator(ELN) at httpelabnavigatorEMCcom
Upgrading Effect on VSAN 4079If you are upgrading to NX-OS Release 50(4b) and you have notcreated VSAN 4079 the NX-OS software will automatically createVSAN 4079 and reserve it for EVFP use If VSAN 4079 is reserved forEVFP use the switchport trunk allowed vsan command will filterout VSAN 4079 from the allowed list as shown in the followingexample
switch(config-if) switchport trunk allowed vsan1-40801-40784080switch(config-if)
If you have created VSAN 4079 the upgrade to NX-OS Release50(4b) will have no affect on VSAN 4079
If you downgrade to a release of NX-OS lower than 41(x) afterNX-OS Release 50(4b) creates VSAN 4079 and reserves it for EVFPuse the VSAN will no longer be reserved
Table 8 FICON Nondisruptive Upgrade Path to NX-OS Release 42(7b)
Current Release withFICON Enabled Upgrade Path
NX-OS 42(1b) You can nondisruptively upgrade directly to NX-OS Release 42(7b)
NX-OS 41(1c) You can nondisruptively upgrade directly to NX-OS Release 42(7b)
SAN-OS 33(1c) You can nondisruptively upgrade directly to NX-OS Release 42(7b)
18 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Upgrading a Cisco MDS 9124 or MDS 9134 switchIf you are upgrading from Cisco MDS SAN-OS Release 31(1) to CiscoNX-OS Release 4x before upgrading to NX-OS Release 50(4b) on aCisco MDS 9124 or MDS 9134 switch follow these guidelines
During the upgrade configuration is not allowed and the fabric isexpected to be stable
The Fabric Shortest Path First (FSPF) timers must be configured tothe default value of 20 seconds otherwise the nondisruptiveupgrade is blocked to ensure that the maximum down toim forthe control plane can be 80 seconds
If there are any CFS commits in the fabric the nondisruptiveupgrade will fail
If there is a zone server merge in progress in the fabric thenondisruptive upgrde will fail
If a service terminates the nondisruptive upgrade the showinstall all failure-reason command can display the reason thatthe nondisruptive upgrade cannot proceed
If there is not enough memory in the system to load the newimages the upgrade will be made disruptive due to insufficientresources and the user will be notified in the compativility table
MDS 9500 series upgrades with active IOA flowsWhen upgading an MDS 9500 series switch that has active IOA flowsthose flows may be interrupted during the supervisor moduleswitchover To workaround this issue you have to enablespanning-tree portfast on the interface on the catalyst connected tothe management interface of the activestandby supervisor for theinterface to come up fast without causing the cluster to lose quorum
Downgrading Your Cisco MDS SAN-OS Software ImageThis section lists the guidelines recommended for downgrading yourCisco MDS SAN-OS software image and includes the followingtopics
ldquoGeneral downgrading guidelinesrdquo on page 19
19
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
General downgrading guidelinesUse the following guidelines to nondisruptively downgrade yourCisco MDS NX-OS Release 50(4b)
Install and configure dual supervisor modules
Issue the system no acl-adjacency-sharing execute command todisable acl adjacency usage on Generation 2 and Generation 1modules If this command fails reduce the number of zones IVRzones TE ports or a combination of these in the system and issuethe command again
Disable all features not supported by the downgrade release Usethe show incompatibility system downgrade-image command todetermine what you need to disable
bull If you are running in interoperability mode two such featuresare the Reliable Commit Service and Full Zone DatabaseDistribution They can be disabled by running thesecommand in config term mode
no zone rcs enableno zoneset capability distribute full
Use the show install all impact downgrade-image command todetermine if your downgrade will be nondisruptive
Be aware that some features impact whether a downgrade isdisruptive or nondisruptive
bull Fibre Channel Ports Traffic on Fibre Channel ports can benondisruptively downgraded See Table 9 on page 20 for thenondisruptive downgrade path for all SAN-OS releases
bull Storage Services Intelligent storage services traffic such asSANTap NASB and FC write acceleration is disruptedduring a downgrade Fibre Channel traffic is not
bull Gigabit Ethernet Ports Traffic on Gigabit Ethernet ports isdisrupted during a downgrade This includes the GigabitEthernet ports on the MSM-184 module and the MDS 9222iswitch Those nodes that are members of VSANs traversing anFCIP ISL are impacted and a fabric reconfiguration occursiSCSI initiators connected to the Gigabit Ethernet ports loseconnectivity to iSCSI targets while the downgrade is inprogress
20 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
bull FICON If you have FICON enabled the downgrade path isdifferent See Table 10 on page 21
Note A downgrade from NX-OS Release 4x to SAN-OS Release 33(1c) is notsupported on MDS switches when FC-Redirect based applications such asData Mobility Manager or Storage Media Encryption are configured in thefabric if either of the following conditions are satisfied
1 A target for which FC-Redirect is configured is connected locally and thereare Generation 1 modules with ISLs configured in the switch
2 A host for which FC-redirect is configured is connected locally ona Generation 1 module
If these conditions exist remove the application configuration forthese targets and hosts before proceeding with the downgrade
Use Table 9 on page 20 to determine the nondisruptive downgradepath from Cisco NX-OS Release 50(4b) Find the NX-OS or SAN-OSimage you want to downgrade to in the To SAN-OSNX-OS Releasecolumn of the table and use the path recommended
Note The software downgrade information in Table 10 on page 21 appliesonly to Fibre Channel switching traffic Downgrading system softwaredisrupts IP and SSM intelligent services traffic
Table 9 Nondisruptive Downgrade Path from NX-OS Release 50(4b) (page 1 of2)
To SAN-OS NX-OSRelease Nondisruptive Downgrade Path
NX-OS 50(4) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 50(1a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(7b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(5) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(3) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(1b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(1a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 41(3a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
21
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Use Table 10 to determine your nondisruptive downgrade path if youhave FICON enabled from Cisco NX-OS Release 42(7b) Find the imagerelease number you are currently using in the Current Release withFICON Enabled column of the table and use the path recommended
NX-OS 41(1b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
SAN-OS 33(5a) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33())
SAN-OS 33(5) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(4a) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
NX-OS 33(4) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(3) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
NX-OS 33(2) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(1c) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 32(3a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 32(x)
SAN-OS 32(2c) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 32(x)
SAN-OS 32(1a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
SAN-OS 31(3a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
SAN-OS 31(2) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
Table 9 Nondisruptive Downgrade Path from NX-OS Release 50(4b) (page 2 of2)
To SAN-OS NX-OSRelease Nondisruptive Downgrade Path
Table 10 FICON Downgrade Path from NX-OS Release 42(7b)
To SAN-OSNX-OS Release withFICON Enabled Downgrade Path
NX-OS 42(1b) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
NX-OS 41(1c) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
SAN-OS 33(1c) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
22 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Best practicesLog messages are not saved across system reboots or power outagesTherefore EMC recommends that customers configure a SyslogServer in order to redirect and capture all log messages on a remoteserver For more information please refer to the Cisco MDS 9000Family Configuration Guide available at
httpwwwciscocomenUSproductsps5989products_support_series_homehtml
Maximum ports per chassisTable 11 shows the maximum ports per chassis
a V2 indicates a 9506 or 9509 with Generation-2 Supervisors The presence of anygeneration one module in a switch will limit the maximum port count to 252This includes the 16-port 32-port 14+2 IPS4 and IPS8 cards
Known problems and limitationsFor a list of problems with this release please refer to the CiscoRelease notes located at
httpwwwciscocomenUSproductsps5989prod_release_notes_listhtml
Limitations and restrictionsThe following limitations and restrictions apply to all switches in theCisco MDS 9000 Family unless a limitation for a specific switch isstated
ldquoStorage Media Encryption (SME) limitationsrdquo on page 24
Table 11 Maximum ports per chassis
Chassis Maximum number of ports
MDS 9506-V2 192a
MDS 9509-V2 336
MDS 9513 528
23
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
ldquoSME configuration limitsrdquo on page 24
ldquoDeleting Cisco SME interfacesrdquo on page 25
ldquoCisco MDS 9124 and 9134 Multilayer fabric switchesrdquo on page 25
ldquoN-Port virtualization configuration limitsrdquo on page 25
ldquoMaximum number of zones supported in Interop Mode 4rdquo onpage 25
ldquoIPv6rdquo on page 26
ldquoIP-ACL supportrdquo on page 26
ldquoUser Rolesrdquo on page 26
ldquoUsing a RSA Version 1 Key for SSH Following an Upgraderdquo onpage 27
ldquoApplying Zone Configurations to VSAN 1rdquo on page 27
ldquoInterVSAN Routingrdquo on page 28
ldquoRSPAN Traffic Not Supported on CTS Ports on 8-GbpsSwitching Modulesrdquo on page 28
ldquoIO Accelerator Feature Limitationsrdquo on page 28
ldquoSupport for FCIP Compression Modesrdquo on page 28
ldquoSaving Copies of the Running Kickstart and System Imagesrdquo onpage 29
ldquoConfiguring Buffer Credits on a Generation 2 or Generation 3Modulerdquo on page 29
ldquoStorage services module power budgetrdquo on page 29
ldquoiSCSI proxy initiator in Celerra HighRoad environmentsrdquo onpage 30
ldquoHPUX N_port IDrdquo on page 30
ldquoInteroperability limitationsrdquo on page 31
ldquoNASBrdquo on page 31
ldquoReserved VSAN Range and Isolated VSAN Range Guidelinesrdquoon page 31
ldquoSymmetrix VMax limitationsrdquo on page 32
ldquoStorage Applications on the MSM-184rdquo on page 32
ldquoDowngrading with fport-channel-trunk enabledrdquo on page 32
ldquoLDAP Authenticationrdquo on page 33
24 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
ldquoMDS-9148 limitationsrdquo on page 33
Storage Media Encryption (SME) limitationsAn SME node can only belong to one cluster Adding the node tomore than one cluster will cause problems
Currently there is no prevention or warning in place when an attemptis made to add a node to multiple clusters
SME configuration limitsTable 12 lists the SME configuration limits for this release
Table 12 SME configuration limits
Configuration Limits
Number of switches in the fabric 10
Number of clusters per switch 1
Switches in a cluster 4
Fabrics in a cluster 2
Modules in a switch 11
Cisco MSM-184 modules in a cluster 32
Initiator-Target-LUNs (ITLs) 1024
LUNs behind a target 32
Host and target ports in a cluster 128
Number of hosts per target 128
Tape backup groups per cluster 2
Volume groups in a tape backup group 4
Cisco Key Management Center ( of keys) 32K
Targets per switch that can be FC-redirected 32
25
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Deleting Cisco SME interfacesA Cisco SME interface can be deleted from the cluster only after theinterface is administratively shut-down and all related tasksassociated with the interface shut-down are complete
Cisco MDS 9124 and 9134 Multilayer fabric switchesThe Cisco MDS 9124 and 9134 Multilayer fabric switches do notsupport the following Cisco MDS SAN-OS features
IVR Remote Span Translative loop support FCCmdash no generation quench reaction only
In addition the following features have these limits
VSANs mdash 16 maximum SPAN mdash 1 session maximum
N-Port virtualization configuration limitsThe NPV features have maximum configuration limits Table 13shows the verified and maximum limits for the NPV switchesrunning NX-OS Release 5x
Maximum number of zones supported in Interop Mode 4In interop mode 4 the maximum number of zones that is supportedin an active zone set is 2047 due to limitations in the connectedvendor switch When IVR is used in interop mode 4 the maximumnumber of zones supported including IVR zones in the active zoneset is 2047 The limit for the maximum number of IVR zones perVSAN is 250 zones (two members per zone)
Table 13 NPV features limitations
Feature Verified limits Maximum limits
FLOGIs or F Disc per NPV port group 114 114
NPV switches per NPV core switch 105 105
FLOGIs per line card on NPV core switch 400 400
26 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
IPv6The management port on Cisco MDS switches supports oneuser-configured IPv6 address but does not supportauto-configuration of an IPv6 address
IP-ACL supportDo not apply IP-ACLs to only one member of a PortChannel groupApply IP-ACLs to the entire channel group
If IP-ACLs are already configured in a Gigabit Ethernet interface youcannot add this interface to a Ethernet PortChannel group
Refer to the Cisco MDS 9000 Family Configuration Guide
User RolesIn SAN-OS Release 33(x) and earlier when a user belongs to a rolewhich has a VSAN policy set to Deny and the role allows access to aspecific set of VSANs (for example 1 through 10) the user isrestricted from performing the configuration clear execute anddebug commands which had a VSAN parameter outside thisspecified set Beginning with NX-OS Release 41(1b) these users arestill prevented from performing configuration clear execute anddebug commands as before however they are allowed to performshow commands for all VSANs The ability to execute the showcommand addresses the following
In a network environment users often need to view informationin other VSANs even though they do not have permission tomodify configurations in those VSANs
This behavior makes Cisco MDS 9000 Series switches consistentwith other Cisco products such as Cisco Nexus 7000 Seriesswitches that exhibit the same behavior for those roles (whenthey apply to the VLAN policy)
27
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Using a RSA Version 1 Key for SSH Following an UpgradeFor security reasons NX-OS Release 42(x) and higher does notsupport RSA version 1 keys As a result if you upgrade from anearlier version that did support RSA version 1 keys and you hadconfigured a RSA version 1 key for SSH then you will not be able tolog in through SSH following the upgrade
If you have a RSA version 1 key configured for SSH beforeupgrading to NX-OS Release 42(x) or higher follow these steps
1 Disable SSH
2 Create RSA version 2 DSA keys
3 Enable SSH
4 Delete any RSA version 1 keys on any remote SSH clients andreplace the version 1 keys with the new version 2 keys from theswitch
Proceed with the upgrade to NX-OS Release 42(x) or higher
If you upgrade before disabling SSH and creating RSA version 2 keysfollow these steps
1 Open a Telnet session and log in through the console
2 Issue the no feature ssh command to disable SSH
3 Issue the ssh key rsa 1024 command to create RSA version 2 keys
4 Issue the feature ssh command to enable SSH
Applying Zone Configurations to VSAN 1In the setup script you can configure system default values for thedefault-zone to be permit or deny and you can configure defaultvalues for the zone distribution method and for the zone mode
These default settings are applied when a new VSAN is createdHowever the settings will not take effect on VSAN 1 because it existsprior to running the setup script Therefore when you need thosesettings for VSAN 1 you must explicitly issue the followingcommands
zone default-zone permit vsan 1 zoneset distribute full vsan 1 zone mode enhanced vsan 1
28 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
InterVSAN RoutingWhen using InterVSAN Routing (IVR) it is recommended to enableCisco Fabric Services (CFS) on all IVR-enabled switches Failure to doso may cause mismatched active zone sets if an error occurs duringzone set activation
RSPAN Traffic Not Supported on CTS Ports on 8-Gbps Switching ModulesAn inter-switch link (ISL) that is enabled for Cisco TrustSec (CTS)encryption must be brought up in non-CTS mode to support remoteSPAN (RSPAN) traffic on the following modules
DS-X9248-96K9 Cisco MDS 9000 48-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9224-96K9 Cisco MDS 9000 24-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9248-48K9 Cisco MDS 9000 444-Port Host-Optimized8-Gbps Fibre Channel Switching Module
If the ISL link is brought up with CTS enabled random packets dropsof both RSPAN traffic and normal traffic will occur on the receiverport switch
IO Accelerator Feature LimitationsIOA does not support the following NX-OS features
IVR flows
Devices with NPV and NPIV enabled
F port trunking
bull F port channeling
Support for FCIP Compression ModesIn Cisco NX-OS Release 42(1b) and higher FCIP compression mode 1and compression mode 3 are not supported on the Cisco MSM-184module and on the SSN-16 module
29
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Saving Copies of the Running Kickstart and System ImagesAfter you upgrade to MDS NX-OS Release 42(1b) or higher you arenot allowed to delete rename move or overwrite the kickstart andsystem images that are in the current system bootvar settings on anactive or standby MDS Supervisor-2 module on any Cisco MDS 9500Series switch This restriction does not apply to the integratedsupervisor module on the MDS 9200 and MDS 9100 series switches
Configuring Buffer Credits on a Generation 2 or Generation 3 ModuleWhen you configure port mode to auto or E on a Generation 2module one of the ports will not come up for the followingconfiguration
Port Mode auto or E for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E on a Generation 3module one or two of the ports will not come up for the followingconfiguration
Port Mode auto or E for the first half of the ports the second halfof the ports or for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E for all ports in the globalbuffer pool you need to reconfigure buffer credits on one or more ofthe ports The total number of buffer credits configured for all theports in the global buffer pool should be reduced by 64
Storage services module power budgetThe MDS 9509 does not have the power budget to run seven SSMcards EMC recommends a maximum of four SSMs in one 9509Customers wishing to use more than four SSMs in one chassis shouldrefer to the Cisco MDS 9000 documentation on the Ciscocom websiteto validate that there is enough power available for their desiredconfiguration
30 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Note Upgrading to the 3000 watt power supplies will alleviate thiscondition
iSCSI proxy initiator in Celerra HighRoad environmentsEMC supports the iSCSI proxy initiator feature in Celerrareg
HighRoadreg environments In proxy initiator mode one Fibre Channelinitiator is used for all iSCSI clients who access the switch via thesame iSCSI interface (iscsi33 for example)
The initiators will use the PWWN assigned to the iSCSI interface TheiSCSI interface to which an iSCSI client will logon to is configured inthe client and must be permitted by the virtual target configured forthat initiator
The current session environment supported on the MDS is
300 sessions per port 1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no InitialR2T=yes
Refer to the specific initiator support documentation on how to setthe parameters The implementation will not perform properly ifthese bits are not set
Refer to the MDS documentation for more information regarding theconfiguration of the iSCSI proxy initiator at the following Ciscowebsite
httpwwwciscocomenUSproducts
HPUX N_port IDThe N_port ID port value of 255 (0xFF) has special meaning forHP-UX A N_port ID (FC_ID) can not be returned from a switch thatcontains this value for the N_port ID (FC_ID) port value for a HP-UXinitiator or HP-UX target port Port ID value of 255 (0xFF) cannot be
31
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
configured for HP-UX initiator port and HP-UX target ports whenconfiguring MDS FC_IDs The port_ID value is the third byte of theFC_ID
Interoperability limitationsRefer to the EMC Support Matrix (ESM) and the EMC Networked Storage Topology Guide for modes of operation and caveats
NASBThe NASB feature requires that the backup application load the tapedrive with a compatible tape cartridge prior to configuring NASB inthe backup VSAN
Reserved VSAN Range and Isolated VSAN Range GuidelinesOn an NPV switch with a trunking configuration on any interface or ona regular switch where the feature fport_channel_trunk command hasbeen issued to enable the F PortChannel feature follow theseconfiguration guidelines for reserved VSANs and the isolated VSAN
bull If trunk mode is on for any of the interfaces or NP PortChannelis up the reserved VSANs are 3040 to 4078 and they are notavailable for user configuration
bull The Exchange Virtual Fabric Protocol (EVFP) isolated VSAN is4079 and it is not available for user configuration
bull VSAN 4079 will be impacted by an upgrade to NX-OS Release42(3) depending on whether or not VSAN 4079 was createdprior to the upgrade See theldquoUpgrading Effect on VSAN 4079rdquoon page 17
The following VSAN IDs are assigned in the Fibre Channel Framingand Signaling (FC-FS) interface standard
VF_ID Value Value Description
00h Do not use as a Virtual FabricIdentifier
001h EFFh Available as a Virtual FabricIdentifier
F00h FEEh Reserved
32 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Symmetrix VMax limitationsAt the time of this writing the following features are not supportedfor use with the Symmetrix VMax
FCIP Write Acceleration
The NX-OS IOA functionality is only supported with the Q2 SREnginuity release 5874229182 or higher
For the most up to date status please refer to the current revision ofthese Release Notes on httpPowerlinkemccom and the EMCSupport Matrix available through E-Lab Interoperability Navigator (ELN) athttpelabnavigatorEMCcom
Storage Applications on the MSM-184The MDS 9000 184-Port Multiservice Module (MSM-184) does notsupport multiple concurrent storage applications Only oneapplication can run on the MSM-184 at a time
Downgrading with fport-channel-trunk enabledIf you are running MDS NX-OS Release 42(x) or higher with thefport-channel-trunk feature enabled and you downgrade to anyNX-OS 41(1x) release the installer performs a nondisruptivedowngrade even though the fport-channel-trunk feature is notsupported in NX-OS 41(1x) releases
As a result the switch is in an inconsistent state and the ports maynot function properly
FEFh Control VF-ID (see FibreChannel Link Services (FC-LS)and Fibre Channel SwitchFabric Generation 4 (FC-SW-4)standards)
FF0h FFEh Vendor specific
FFFh Do not use as a Virtual FabricIdentifier
FEFh = 4079
33
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
If you are in this state a workaround is to reboot the switch followingthe upgrade
LDAP AuthenticationThere is currently a limitation in the LDAP server configuration CLIthat prevents the use of an OU with spaces in the name Normallythese OU names could be surrounded by quotation marks howeverquotation marks are not supported by the ldap-server command
MDS-9148 limitationsThe Cisco MDS 9148 Multilayer Fabric Switch does not support thefollowing NX-OS features
Medium and Long range 4GB Agilent
IVR
Remote Span
Translative loop support
FCC - no generation quench reaction only
FC-Redirect
In addition the following features have these limits
VSANS - 31 maximum
SPAN - 1 session maximum
Technical notesThe following sections provide further information on technicalnotes
EMC Email Home for Cisco MDS switchesInstallation and Trouble shooting instructions can be found in thedocumentation located at the EMC Customer Service Internalwebsite
httpwwwcsisusemccomcsweb2esnesnhomehtmConnectrix20MDS20900020Family
34 EMC Connectrix MDS 9000 NX-OS Release Notes
Technical notes
Customers requiring installation of this solution should contact theirEMC Customer Engineer to assist with the installation and providethe documentation
Supported iSCSI sessionsThe current iSCSI session environment supported on the MDS is
300 sessions per port
1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no
InitialR2T=yes
Upgrading Cisco SAN-OSThere are several methods available for upgrading SAN-OS SoftwareEMC personnel are strongly recommended that all upgrades be doneby the Automated One-Step Upgrade using the install all
command EMC personnel should refer to the Connectrix MDS 9000Family Software Image Upgrade Instructions for a complete list ofprerequisites and instructions for performing the upgrade Thisdocument along with tftp software is available on the GlobalServices website at httpwwwcsisusEMCcom under ApplicationDownload Area ESN Product Information Connectrix MDS 9000Family
The Software Upgrade Wizard is an option for upgrades While theinstall all is the preferred method the Software Install Wizard canalso be used
Supported configuration parametersFor the most up-to-date information refer to the EMC Support Matrixavailable through E-Lab Interoperability Navigator athttpelabnavigatoremccom for the latest information onsupported configurations
35
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
Supported zoning parametersRefer to the EMC Networked Storage Topology Guide for the mostup-to-date information on supported zoning parameters
At the time these notes were published the following parameterswere supported
20 VSANs 5 Hops 2000 Unique members per physical infrastructure 1000 Zonesets per physical infrastructure 2000 Zones per physical infrastructure 1 FCIP tunnel
Supported IVR parameters IVR zone members 1000 IVR zones 1000 IVR zone sets 32 VSANS 20 IVR enabled switches 64
An RPQ can be submitted for any configurations that exceed thislimit
Managing zone changes in multiswitch fabricsZoning changes may be made through Fabric Manager or CLI Whenaccessing Fabric Manager or CLI the user does so from the point ofview of one switch That is Fabric Manager and CLI are accessed byentering the IP address of one switch in the fabric
When zoning changes are made the applicable VSAN and zone setdata is propagated to the rest of the switches in the fabric via the ISLs
When zoning changes are made to a VSAN the zone set data ispropagated to the rest of the switches in the fabric via the ISLs Bydefault only the active zone set information is relayed to all switchesin the VSAN If the user accesses the Fabric Manager and CLI fromanother switch in the fabric the new VSAN and zone set informationwill not be viewable To view the active and inactive zone set on theother switches in the fabric the user must log in to the CLI and issuea command from the EXEC prompt
36 EMC Connectrix MDS 9000 NX-OS Release Notes
Documentation
Example The following is an example of copying VSAN 1 through 20 zoningdata
CiscoMDS_name zone copy active full vsan 1-20
CiscoMDS_name conf t
Enter configuration commands one per line End with CNTL Z
CiscoMDS_name(config) zoneset distribute full vsan 1-20
CiscoMDS_name(config)
Note This command needs to be issued on all switches in the fabric one timeonly
This is a nondisruptive command After issuing the commands theuser will now see the active and inactive zone sets for the specifiedVSANs on any switch that is chosen from which to manage the fabric
After a zoning change is made save the running configuration to thestartup configuration
DocumentationSend documentation comments to mdsfeedback-doccom
Product DocumentationAs of NX-OS Release 42(1a) software configuration information isavailable in new feature-specific configuration guides for thefollowing information
System management
Interfaces
Fabric
Quality of service
Security
IP services
High availability and redundancy
37
Software media organization and files
EMC Connectrix MDS 9000 NX-OS Release Notes
The information in these new guides previously existed in the CiscoMDS 9000 Family CLI Configuration Guide That configuration guideremains available on Ciscocom and should be used for all softwarereleases prior to NX-OS Release 42(1a) Configuration guidesaddress the features introduced in or available in a particular releaseSelect and view the configuration guide that pertains to the softwareinstalled in your switch
In addition Fabric Manager information has been removed from theMDS NX-OS Release Notes (this document) and placed intostandalone Fabric Manager Release Notes that support both CiscoMDS 9000 Family switches and Cisco Nexus 5000 Series switchesThe Cisco Fabric Manager Release Notes are available onhttpPowerlinkemccom and from the following website
httpwwwciscocomenUSpartnerproductsps10495prod_release_notes_listhtml
Technical supportThese release notes complement a Cisco documentation set EachCisco document refers to where to get help However for any itemssupplied by EMC see ldquoTroubleshooting and getting helprdquo onpage 38
Software media organization and filesFor information on related software environment and systemrequirements refer to the EMC Support Matrix on EMC Powerlink at
httpPowerlinkEMCcom
InstallationFor hardware installation information refer to the Cisco MDS HWInstallation Guides available at Ciscocom
For EMC-specific installation information refer to ldquoEnvironment andsystem requirementsrdquo on page 5 in this document
38 EMC Connectrix MDS 9000 NX-OS Release Notes
Troubleshooting and getting help
Troubleshooting and getting helpEMC support product and licensing information can be obtained asfollows
Product information mdash For documentation release notes softwareupdates or for information about EMC products licensing andservice go to the EMC Powerlink website (registration required) at
httpPowerlinkEMCcom
Technical support mdash For technical support go to EMC CustomerService on Powerlink To open a service request through Powerlinkyou must have a valid support agreement Please contact your EMCsales representative for details about obtaining a valid supportagreement or to answer any questions about your account
Copyright copy 2011 EMC Corporation All rights reserved
EMC believes the information in this publication is accurate as of its publication date The information issubject to change without notice
THE INFORMATION IN THIS PUBLICATION IS PROVIDED ldquoAS ISrdquo EMC CORPORATION MAKES NOREPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION INTHIS PUBLICATION AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OFMERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Use copying and distribution of any EMC software described in this publication requires an applicablesoftware license
For the most up-to-date regulatory document for your product line go to the Technical Documentation andAdvisories section on EMC Powerlink
For the most up-to-date listing of EMC product names see EMC Corporation Trademarks on EMCcom
All other trademarks used herein are the property of their respective owners
18 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
Upgrading a Cisco MDS 9124 or MDS 9134 switchIf you are upgrading from Cisco MDS SAN-OS Release 31(1) to CiscoNX-OS Release 4x before upgrading to NX-OS Release 50(4b) on aCisco MDS 9124 or MDS 9134 switch follow these guidelines
During the upgrade configuration is not allowed and the fabric isexpected to be stable
The Fabric Shortest Path First (FSPF) timers must be configured tothe default value of 20 seconds otherwise the nondisruptiveupgrade is blocked to ensure that the maximum down toim forthe control plane can be 80 seconds
If there are any CFS commits in the fabric the nondisruptiveupgrade will fail
If there is a zone server merge in progress in the fabric thenondisruptive upgrde will fail
If a service terminates the nondisruptive upgrade the showinstall all failure-reason command can display the reason thatthe nondisruptive upgrade cannot proceed
If there is not enough memory in the system to load the newimages the upgrade will be made disruptive due to insufficientresources and the user will be notified in the compativility table
MDS 9500 series upgrades with active IOA flowsWhen upgading an MDS 9500 series switch that has active IOA flowsthose flows may be interrupted during the supervisor moduleswitchover To workaround this issue you have to enablespanning-tree portfast on the interface on the catalyst connected tothe management interface of the activestandby supervisor for theinterface to come up fast without causing the cluster to lose quorum
Downgrading Your Cisco MDS SAN-OS Software ImageThis section lists the guidelines recommended for downgrading yourCisco MDS SAN-OS software image and includes the followingtopics
ldquoGeneral downgrading guidelinesrdquo on page 19
19
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
General downgrading guidelinesUse the following guidelines to nondisruptively downgrade yourCisco MDS NX-OS Release 50(4b)
Install and configure dual supervisor modules
Issue the system no acl-adjacency-sharing execute command todisable acl adjacency usage on Generation 2 and Generation 1modules If this command fails reduce the number of zones IVRzones TE ports or a combination of these in the system and issuethe command again
Disable all features not supported by the downgrade release Usethe show incompatibility system downgrade-image command todetermine what you need to disable
bull If you are running in interoperability mode two such featuresare the Reliable Commit Service and Full Zone DatabaseDistribution They can be disabled by running thesecommand in config term mode
no zone rcs enableno zoneset capability distribute full
Use the show install all impact downgrade-image command todetermine if your downgrade will be nondisruptive
Be aware that some features impact whether a downgrade isdisruptive or nondisruptive
bull Fibre Channel Ports Traffic on Fibre Channel ports can benondisruptively downgraded See Table 9 on page 20 for thenondisruptive downgrade path for all SAN-OS releases
bull Storage Services Intelligent storage services traffic such asSANTap NASB and FC write acceleration is disruptedduring a downgrade Fibre Channel traffic is not
bull Gigabit Ethernet Ports Traffic on Gigabit Ethernet ports isdisrupted during a downgrade This includes the GigabitEthernet ports on the MSM-184 module and the MDS 9222iswitch Those nodes that are members of VSANs traversing anFCIP ISL are impacted and a fabric reconfiguration occursiSCSI initiators connected to the Gigabit Ethernet ports loseconnectivity to iSCSI targets while the downgrade is inprogress
20 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
bull FICON If you have FICON enabled the downgrade path isdifferent See Table 10 on page 21
Note A downgrade from NX-OS Release 4x to SAN-OS Release 33(1c) is notsupported on MDS switches when FC-Redirect based applications such asData Mobility Manager or Storage Media Encryption are configured in thefabric if either of the following conditions are satisfied
1 A target for which FC-Redirect is configured is connected locally and thereare Generation 1 modules with ISLs configured in the switch
2 A host for which FC-redirect is configured is connected locally ona Generation 1 module
If these conditions exist remove the application configuration forthese targets and hosts before proceeding with the downgrade
Use Table 9 on page 20 to determine the nondisruptive downgradepath from Cisco NX-OS Release 50(4b) Find the NX-OS or SAN-OSimage you want to downgrade to in the To SAN-OSNX-OS Releasecolumn of the table and use the path recommended
Note The software downgrade information in Table 10 on page 21 appliesonly to Fibre Channel switching traffic Downgrading system softwaredisrupts IP and SSM intelligent services traffic
Table 9 Nondisruptive Downgrade Path from NX-OS Release 50(4b) (page 1 of2)
To SAN-OS NX-OSRelease Nondisruptive Downgrade Path
NX-OS 50(4) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 50(1a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(7b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(5) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(3) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(1b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(1a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 41(3a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
21
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Use Table 10 to determine your nondisruptive downgrade path if youhave FICON enabled from Cisco NX-OS Release 42(7b) Find the imagerelease number you are currently using in the Current Release withFICON Enabled column of the table and use the path recommended
NX-OS 41(1b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
SAN-OS 33(5a) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33())
SAN-OS 33(5) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(4a) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
NX-OS 33(4) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(3) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
NX-OS 33(2) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(1c) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 32(3a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 32(x)
SAN-OS 32(2c) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 32(x)
SAN-OS 32(1a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
SAN-OS 31(3a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
SAN-OS 31(2) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
Table 9 Nondisruptive Downgrade Path from NX-OS Release 50(4b) (page 2 of2)
To SAN-OS NX-OSRelease Nondisruptive Downgrade Path
Table 10 FICON Downgrade Path from NX-OS Release 42(7b)
To SAN-OSNX-OS Release withFICON Enabled Downgrade Path
NX-OS 42(1b) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
NX-OS 41(1c) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
SAN-OS 33(1c) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
22 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Best practicesLog messages are not saved across system reboots or power outagesTherefore EMC recommends that customers configure a SyslogServer in order to redirect and capture all log messages on a remoteserver For more information please refer to the Cisco MDS 9000Family Configuration Guide available at
httpwwwciscocomenUSproductsps5989products_support_series_homehtml
Maximum ports per chassisTable 11 shows the maximum ports per chassis
a V2 indicates a 9506 or 9509 with Generation-2 Supervisors The presence of anygeneration one module in a switch will limit the maximum port count to 252This includes the 16-port 32-port 14+2 IPS4 and IPS8 cards
Known problems and limitationsFor a list of problems with this release please refer to the CiscoRelease notes located at
httpwwwciscocomenUSproductsps5989prod_release_notes_listhtml
Limitations and restrictionsThe following limitations and restrictions apply to all switches in theCisco MDS 9000 Family unless a limitation for a specific switch isstated
ldquoStorage Media Encryption (SME) limitationsrdquo on page 24
Table 11 Maximum ports per chassis
Chassis Maximum number of ports
MDS 9506-V2 192a
MDS 9509-V2 336
MDS 9513 528
23
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
ldquoSME configuration limitsrdquo on page 24
ldquoDeleting Cisco SME interfacesrdquo on page 25
ldquoCisco MDS 9124 and 9134 Multilayer fabric switchesrdquo on page 25
ldquoN-Port virtualization configuration limitsrdquo on page 25
ldquoMaximum number of zones supported in Interop Mode 4rdquo onpage 25
ldquoIPv6rdquo on page 26
ldquoIP-ACL supportrdquo on page 26
ldquoUser Rolesrdquo on page 26
ldquoUsing a RSA Version 1 Key for SSH Following an Upgraderdquo onpage 27
ldquoApplying Zone Configurations to VSAN 1rdquo on page 27
ldquoInterVSAN Routingrdquo on page 28
ldquoRSPAN Traffic Not Supported on CTS Ports on 8-GbpsSwitching Modulesrdquo on page 28
ldquoIO Accelerator Feature Limitationsrdquo on page 28
ldquoSupport for FCIP Compression Modesrdquo on page 28
ldquoSaving Copies of the Running Kickstart and System Imagesrdquo onpage 29
ldquoConfiguring Buffer Credits on a Generation 2 or Generation 3Modulerdquo on page 29
ldquoStorage services module power budgetrdquo on page 29
ldquoiSCSI proxy initiator in Celerra HighRoad environmentsrdquo onpage 30
ldquoHPUX N_port IDrdquo on page 30
ldquoInteroperability limitationsrdquo on page 31
ldquoNASBrdquo on page 31
ldquoReserved VSAN Range and Isolated VSAN Range Guidelinesrdquoon page 31
ldquoSymmetrix VMax limitationsrdquo on page 32
ldquoStorage Applications on the MSM-184rdquo on page 32
ldquoDowngrading with fport-channel-trunk enabledrdquo on page 32
ldquoLDAP Authenticationrdquo on page 33
24 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
ldquoMDS-9148 limitationsrdquo on page 33
Storage Media Encryption (SME) limitationsAn SME node can only belong to one cluster Adding the node tomore than one cluster will cause problems
Currently there is no prevention or warning in place when an attemptis made to add a node to multiple clusters
SME configuration limitsTable 12 lists the SME configuration limits for this release
Table 12 SME configuration limits
Configuration Limits
Number of switches in the fabric 10
Number of clusters per switch 1
Switches in a cluster 4
Fabrics in a cluster 2
Modules in a switch 11
Cisco MSM-184 modules in a cluster 32
Initiator-Target-LUNs (ITLs) 1024
LUNs behind a target 32
Host and target ports in a cluster 128
Number of hosts per target 128
Tape backup groups per cluster 2
Volume groups in a tape backup group 4
Cisco Key Management Center ( of keys) 32K
Targets per switch that can be FC-redirected 32
25
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Deleting Cisco SME interfacesA Cisco SME interface can be deleted from the cluster only after theinterface is administratively shut-down and all related tasksassociated with the interface shut-down are complete
Cisco MDS 9124 and 9134 Multilayer fabric switchesThe Cisco MDS 9124 and 9134 Multilayer fabric switches do notsupport the following Cisco MDS SAN-OS features
IVR Remote Span Translative loop support FCCmdash no generation quench reaction only
In addition the following features have these limits
VSANs mdash 16 maximum SPAN mdash 1 session maximum
N-Port virtualization configuration limitsThe NPV features have maximum configuration limits Table 13shows the verified and maximum limits for the NPV switchesrunning NX-OS Release 5x
Maximum number of zones supported in Interop Mode 4In interop mode 4 the maximum number of zones that is supportedin an active zone set is 2047 due to limitations in the connectedvendor switch When IVR is used in interop mode 4 the maximumnumber of zones supported including IVR zones in the active zoneset is 2047 The limit for the maximum number of IVR zones perVSAN is 250 zones (two members per zone)
Table 13 NPV features limitations
Feature Verified limits Maximum limits
FLOGIs or F Disc per NPV port group 114 114
NPV switches per NPV core switch 105 105
FLOGIs per line card on NPV core switch 400 400
26 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
IPv6The management port on Cisco MDS switches supports oneuser-configured IPv6 address but does not supportauto-configuration of an IPv6 address
IP-ACL supportDo not apply IP-ACLs to only one member of a PortChannel groupApply IP-ACLs to the entire channel group
If IP-ACLs are already configured in a Gigabit Ethernet interface youcannot add this interface to a Ethernet PortChannel group
Refer to the Cisco MDS 9000 Family Configuration Guide
User RolesIn SAN-OS Release 33(x) and earlier when a user belongs to a rolewhich has a VSAN policy set to Deny and the role allows access to aspecific set of VSANs (for example 1 through 10) the user isrestricted from performing the configuration clear execute anddebug commands which had a VSAN parameter outside thisspecified set Beginning with NX-OS Release 41(1b) these users arestill prevented from performing configuration clear execute anddebug commands as before however they are allowed to performshow commands for all VSANs The ability to execute the showcommand addresses the following
In a network environment users often need to view informationin other VSANs even though they do not have permission tomodify configurations in those VSANs
This behavior makes Cisco MDS 9000 Series switches consistentwith other Cisco products such as Cisco Nexus 7000 Seriesswitches that exhibit the same behavior for those roles (whenthey apply to the VLAN policy)
27
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Using a RSA Version 1 Key for SSH Following an UpgradeFor security reasons NX-OS Release 42(x) and higher does notsupport RSA version 1 keys As a result if you upgrade from anearlier version that did support RSA version 1 keys and you hadconfigured a RSA version 1 key for SSH then you will not be able tolog in through SSH following the upgrade
If you have a RSA version 1 key configured for SSH beforeupgrading to NX-OS Release 42(x) or higher follow these steps
1 Disable SSH
2 Create RSA version 2 DSA keys
3 Enable SSH
4 Delete any RSA version 1 keys on any remote SSH clients andreplace the version 1 keys with the new version 2 keys from theswitch
Proceed with the upgrade to NX-OS Release 42(x) or higher
If you upgrade before disabling SSH and creating RSA version 2 keysfollow these steps
1 Open a Telnet session and log in through the console
2 Issue the no feature ssh command to disable SSH
3 Issue the ssh key rsa 1024 command to create RSA version 2 keys
4 Issue the feature ssh command to enable SSH
Applying Zone Configurations to VSAN 1In the setup script you can configure system default values for thedefault-zone to be permit or deny and you can configure defaultvalues for the zone distribution method and for the zone mode
These default settings are applied when a new VSAN is createdHowever the settings will not take effect on VSAN 1 because it existsprior to running the setup script Therefore when you need thosesettings for VSAN 1 you must explicitly issue the followingcommands
zone default-zone permit vsan 1 zoneset distribute full vsan 1 zone mode enhanced vsan 1
28 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
InterVSAN RoutingWhen using InterVSAN Routing (IVR) it is recommended to enableCisco Fabric Services (CFS) on all IVR-enabled switches Failure to doso may cause mismatched active zone sets if an error occurs duringzone set activation
RSPAN Traffic Not Supported on CTS Ports on 8-Gbps Switching ModulesAn inter-switch link (ISL) that is enabled for Cisco TrustSec (CTS)encryption must be brought up in non-CTS mode to support remoteSPAN (RSPAN) traffic on the following modules
DS-X9248-96K9 Cisco MDS 9000 48-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9224-96K9 Cisco MDS 9000 24-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9248-48K9 Cisco MDS 9000 444-Port Host-Optimized8-Gbps Fibre Channel Switching Module
If the ISL link is brought up with CTS enabled random packets dropsof both RSPAN traffic and normal traffic will occur on the receiverport switch
IO Accelerator Feature LimitationsIOA does not support the following NX-OS features
IVR flows
Devices with NPV and NPIV enabled
F port trunking
bull F port channeling
Support for FCIP Compression ModesIn Cisco NX-OS Release 42(1b) and higher FCIP compression mode 1and compression mode 3 are not supported on the Cisco MSM-184module and on the SSN-16 module
29
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Saving Copies of the Running Kickstart and System ImagesAfter you upgrade to MDS NX-OS Release 42(1b) or higher you arenot allowed to delete rename move or overwrite the kickstart andsystem images that are in the current system bootvar settings on anactive or standby MDS Supervisor-2 module on any Cisco MDS 9500Series switch This restriction does not apply to the integratedsupervisor module on the MDS 9200 and MDS 9100 series switches
Configuring Buffer Credits on a Generation 2 or Generation 3 ModuleWhen you configure port mode to auto or E on a Generation 2module one of the ports will not come up for the followingconfiguration
Port Mode auto or E for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E on a Generation 3module one or two of the ports will not come up for the followingconfiguration
Port Mode auto or E for the first half of the ports the second halfof the ports or for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E for all ports in the globalbuffer pool you need to reconfigure buffer credits on one or more ofthe ports The total number of buffer credits configured for all theports in the global buffer pool should be reduced by 64
Storage services module power budgetThe MDS 9509 does not have the power budget to run seven SSMcards EMC recommends a maximum of four SSMs in one 9509Customers wishing to use more than four SSMs in one chassis shouldrefer to the Cisco MDS 9000 documentation on the Ciscocom websiteto validate that there is enough power available for their desiredconfiguration
30 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Note Upgrading to the 3000 watt power supplies will alleviate thiscondition
iSCSI proxy initiator in Celerra HighRoad environmentsEMC supports the iSCSI proxy initiator feature in Celerrareg
HighRoadreg environments In proxy initiator mode one Fibre Channelinitiator is used for all iSCSI clients who access the switch via thesame iSCSI interface (iscsi33 for example)
The initiators will use the PWWN assigned to the iSCSI interface TheiSCSI interface to which an iSCSI client will logon to is configured inthe client and must be permitted by the virtual target configured forthat initiator
The current session environment supported on the MDS is
300 sessions per port 1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no InitialR2T=yes
Refer to the specific initiator support documentation on how to setthe parameters The implementation will not perform properly ifthese bits are not set
Refer to the MDS documentation for more information regarding theconfiguration of the iSCSI proxy initiator at the following Ciscowebsite
httpwwwciscocomenUSproducts
HPUX N_port IDThe N_port ID port value of 255 (0xFF) has special meaning forHP-UX A N_port ID (FC_ID) can not be returned from a switch thatcontains this value for the N_port ID (FC_ID) port value for a HP-UXinitiator or HP-UX target port Port ID value of 255 (0xFF) cannot be
31
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
configured for HP-UX initiator port and HP-UX target ports whenconfiguring MDS FC_IDs The port_ID value is the third byte of theFC_ID
Interoperability limitationsRefer to the EMC Support Matrix (ESM) and the EMC Networked Storage Topology Guide for modes of operation and caveats
NASBThe NASB feature requires that the backup application load the tapedrive with a compatible tape cartridge prior to configuring NASB inthe backup VSAN
Reserved VSAN Range and Isolated VSAN Range GuidelinesOn an NPV switch with a trunking configuration on any interface or ona regular switch where the feature fport_channel_trunk command hasbeen issued to enable the F PortChannel feature follow theseconfiguration guidelines for reserved VSANs and the isolated VSAN
bull If trunk mode is on for any of the interfaces or NP PortChannelis up the reserved VSANs are 3040 to 4078 and they are notavailable for user configuration
bull The Exchange Virtual Fabric Protocol (EVFP) isolated VSAN is4079 and it is not available for user configuration
bull VSAN 4079 will be impacted by an upgrade to NX-OS Release42(3) depending on whether or not VSAN 4079 was createdprior to the upgrade See theldquoUpgrading Effect on VSAN 4079rdquoon page 17
The following VSAN IDs are assigned in the Fibre Channel Framingand Signaling (FC-FS) interface standard
VF_ID Value Value Description
00h Do not use as a Virtual FabricIdentifier
001h EFFh Available as a Virtual FabricIdentifier
F00h FEEh Reserved
32 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Symmetrix VMax limitationsAt the time of this writing the following features are not supportedfor use with the Symmetrix VMax
FCIP Write Acceleration
The NX-OS IOA functionality is only supported with the Q2 SREnginuity release 5874229182 or higher
For the most up to date status please refer to the current revision ofthese Release Notes on httpPowerlinkemccom and the EMCSupport Matrix available through E-Lab Interoperability Navigator (ELN) athttpelabnavigatorEMCcom
Storage Applications on the MSM-184The MDS 9000 184-Port Multiservice Module (MSM-184) does notsupport multiple concurrent storage applications Only oneapplication can run on the MSM-184 at a time
Downgrading with fport-channel-trunk enabledIf you are running MDS NX-OS Release 42(x) or higher with thefport-channel-trunk feature enabled and you downgrade to anyNX-OS 41(1x) release the installer performs a nondisruptivedowngrade even though the fport-channel-trunk feature is notsupported in NX-OS 41(1x) releases
As a result the switch is in an inconsistent state and the ports maynot function properly
FEFh Control VF-ID (see FibreChannel Link Services (FC-LS)and Fibre Channel SwitchFabric Generation 4 (FC-SW-4)standards)
FF0h FFEh Vendor specific
FFFh Do not use as a Virtual FabricIdentifier
FEFh = 4079
33
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
If you are in this state a workaround is to reboot the switch followingthe upgrade
LDAP AuthenticationThere is currently a limitation in the LDAP server configuration CLIthat prevents the use of an OU with spaces in the name Normallythese OU names could be surrounded by quotation marks howeverquotation marks are not supported by the ldap-server command
MDS-9148 limitationsThe Cisco MDS 9148 Multilayer Fabric Switch does not support thefollowing NX-OS features
Medium and Long range 4GB Agilent
IVR
Remote Span
Translative loop support
FCC - no generation quench reaction only
FC-Redirect
In addition the following features have these limits
VSANS - 31 maximum
SPAN - 1 session maximum
Technical notesThe following sections provide further information on technicalnotes
EMC Email Home for Cisco MDS switchesInstallation and Trouble shooting instructions can be found in thedocumentation located at the EMC Customer Service Internalwebsite
httpwwwcsisusemccomcsweb2esnesnhomehtmConnectrix20MDS20900020Family
34 EMC Connectrix MDS 9000 NX-OS Release Notes
Technical notes
Customers requiring installation of this solution should contact theirEMC Customer Engineer to assist with the installation and providethe documentation
Supported iSCSI sessionsThe current iSCSI session environment supported on the MDS is
300 sessions per port
1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no
InitialR2T=yes
Upgrading Cisco SAN-OSThere are several methods available for upgrading SAN-OS SoftwareEMC personnel are strongly recommended that all upgrades be doneby the Automated One-Step Upgrade using the install all
command EMC personnel should refer to the Connectrix MDS 9000Family Software Image Upgrade Instructions for a complete list ofprerequisites and instructions for performing the upgrade Thisdocument along with tftp software is available on the GlobalServices website at httpwwwcsisusEMCcom under ApplicationDownload Area ESN Product Information Connectrix MDS 9000Family
The Software Upgrade Wizard is an option for upgrades While theinstall all is the preferred method the Software Install Wizard canalso be used
Supported configuration parametersFor the most up-to-date information refer to the EMC Support Matrixavailable through E-Lab Interoperability Navigator athttpelabnavigatoremccom for the latest information onsupported configurations
35
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
Supported zoning parametersRefer to the EMC Networked Storage Topology Guide for the mostup-to-date information on supported zoning parameters
At the time these notes were published the following parameterswere supported
20 VSANs 5 Hops 2000 Unique members per physical infrastructure 1000 Zonesets per physical infrastructure 2000 Zones per physical infrastructure 1 FCIP tunnel
Supported IVR parameters IVR zone members 1000 IVR zones 1000 IVR zone sets 32 VSANS 20 IVR enabled switches 64
An RPQ can be submitted for any configurations that exceed thislimit
Managing zone changes in multiswitch fabricsZoning changes may be made through Fabric Manager or CLI Whenaccessing Fabric Manager or CLI the user does so from the point ofview of one switch That is Fabric Manager and CLI are accessed byentering the IP address of one switch in the fabric
When zoning changes are made the applicable VSAN and zone setdata is propagated to the rest of the switches in the fabric via the ISLs
When zoning changes are made to a VSAN the zone set data ispropagated to the rest of the switches in the fabric via the ISLs Bydefault only the active zone set information is relayed to all switchesin the VSAN If the user accesses the Fabric Manager and CLI fromanother switch in the fabric the new VSAN and zone set informationwill not be viewable To view the active and inactive zone set on theother switches in the fabric the user must log in to the CLI and issuea command from the EXEC prompt
36 EMC Connectrix MDS 9000 NX-OS Release Notes
Documentation
Example The following is an example of copying VSAN 1 through 20 zoningdata
CiscoMDS_name zone copy active full vsan 1-20
CiscoMDS_name conf t
Enter configuration commands one per line End with CNTL Z
CiscoMDS_name(config) zoneset distribute full vsan 1-20
CiscoMDS_name(config)
Note This command needs to be issued on all switches in the fabric one timeonly
This is a nondisruptive command After issuing the commands theuser will now see the active and inactive zone sets for the specifiedVSANs on any switch that is chosen from which to manage the fabric
After a zoning change is made save the running configuration to thestartup configuration
DocumentationSend documentation comments to mdsfeedback-doccom
Product DocumentationAs of NX-OS Release 42(1a) software configuration information isavailable in new feature-specific configuration guides for thefollowing information
System management
Interfaces
Fabric
Quality of service
Security
IP services
High availability and redundancy
37
Software media organization and files
EMC Connectrix MDS 9000 NX-OS Release Notes
The information in these new guides previously existed in the CiscoMDS 9000 Family CLI Configuration Guide That configuration guideremains available on Ciscocom and should be used for all softwarereleases prior to NX-OS Release 42(1a) Configuration guidesaddress the features introduced in or available in a particular releaseSelect and view the configuration guide that pertains to the softwareinstalled in your switch
In addition Fabric Manager information has been removed from theMDS NX-OS Release Notes (this document) and placed intostandalone Fabric Manager Release Notes that support both CiscoMDS 9000 Family switches and Cisco Nexus 5000 Series switchesThe Cisco Fabric Manager Release Notes are available onhttpPowerlinkemccom and from the following website
httpwwwciscocomenUSpartnerproductsps10495prod_release_notes_listhtml
Technical supportThese release notes complement a Cisco documentation set EachCisco document refers to where to get help However for any itemssupplied by EMC see ldquoTroubleshooting and getting helprdquo onpage 38
Software media organization and filesFor information on related software environment and systemrequirements refer to the EMC Support Matrix on EMC Powerlink at
httpPowerlinkEMCcom
InstallationFor hardware installation information refer to the Cisco MDS HWInstallation Guides available at Ciscocom
For EMC-specific installation information refer to ldquoEnvironment andsystem requirementsrdquo on page 5 in this document
38 EMC Connectrix MDS 9000 NX-OS Release Notes
Troubleshooting and getting help
Troubleshooting and getting helpEMC support product and licensing information can be obtained asfollows
Product information mdash For documentation release notes softwareupdates or for information about EMC products licensing andservice go to the EMC Powerlink website (registration required) at
httpPowerlinkEMCcom
Technical support mdash For technical support go to EMC CustomerService on Powerlink To open a service request through Powerlinkyou must have a valid support agreement Please contact your EMCsales representative for details about obtaining a valid supportagreement or to answer any questions about your account
Copyright copy 2011 EMC Corporation All rights reserved
EMC believes the information in this publication is accurate as of its publication date The information issubject to change without notice
THE INFORMATION IN THIS PUBLICATION IS PROVIDED ldquoAS ISrdquo EMC CORPORATION MAKES NOREPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION INTHIS PUBLICATION AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OFMERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Use copying and distribution of any EMC software described in this publication requires an applicablesoftware license
For the most up-to-date regulatory document for your product line go to the Technical Documentation andAdvisories section on EMC Powerlink
For the most up-to-date listing of EMC product names see EMC Corporation Trademarks on EMCcom
All other trademarks used herein are the property of their respective owners
19
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
General downgrading guidelinesUse the following guidelines to nondisruptively downgrade yourCisco MDS NX-OS Release 50(4b)
Install and configure dual supervisor modules
Issue the system no acl-adjacency-sharing execute command todisable acl adjacency usage on Generation 2 and Generation 1modules If this command fails reduce the number of zones IVRzones TE ports or a combination of these in the system and issuethe command again
Disable all features not supported by the downgrade release Usethe show incompatibility system downgrade-image command todetermine what you need to disable
bull If you are running in interoperability mode two such featuresare the Reliable Commit Service and Full Zone DatabaseDistribution They can be disabled by running thesecommand in config term mode
no zone rcs enableno zoneset capability distribute full
Use the show install all impact downgrade-image command todetermine if your downgrade will be nondisruptive
Be aware that some features impact whether a downgrade isdisruptive or nondisruptive
bull Fibre Channel Ports Traffic on Fibre Channel ports can benondisruptively downgraded See Table 9 on page 20 for thenondisruptive downgrade path for all SAN-OS releases
bull Storage Services Intelligent storage services traffic such asSANTap NASB and FC write acceleration is disruptedduring a downgrade Fibre Channel traffic is not
bull Gigabit Ethernet Ports Traffic on Gigabit Ethernet ports isdisrupted during a downgrade This includes the GigabitEthernet ports on the MSM-184 module and the MDS 9222iswitch Those nodes that are members of VSANs traversing anFCIP ISL are impacted and a fabric reconfiguration occursiSCSI initiators connected to the Gigabit Ethernet ports loseconnectivity to iSCSI targets while the downgrade is inprogress
20 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
bull FICON If you have FICON enabled the downgrade path isdifferent See Table 10 on page 21
Note A downgrade from NX-OS Release 4x to SAN-OS Release 33(1c) is notsupported on MDS switches when FC-Redirect based applications such asData Mobility Manager or Storage Media Encryption are configured in thefabric if either of the following conditions are satisfied
1 A target for which FC-Redirect is configured is connected locally and thereare Generation 1 modules with ISLs configured in the switch
2 A host for which FC-redirect is configured is connected locally ona Generation 1 module
If these conditions exist remove the application configuration forthese targets and hosts before proceeding with the downgrade
Use Table 9 on page 20 to determine the nondisruptive downgradepath from Cisco NX-OS Release 50(4b) Find the NX-OS or SAN-OSimage you want to downgrade to in the To SAN-OSNX-OS Releasecolumn of the table and use the path recommended
Note The software downgrade information in Table 10 on page 21 appliesonly to Fibre Channel switching traffic Downgrading system softwaredisrupts IP and SSM intelligent services traffic
Table 9 Nondisruptive Downgrade Path from NX-OS Release 50(4b) (page 1 of2)
To SAN-OS NX-OSRelease Nondisruptive Downgrade Path
NX-OS 50(4) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 50(1a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(7b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(5) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(3) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(1b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(1a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 41(3a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
21
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Use Table 10 to determine your nondisruptive downgrade path if youhave FICON enabled from Cisco NX-OS Release 42(7b) Find the imagerelease number you are currently using in the Current Release withFICON Enabled column of the table and use the path recommended
NX-OS 41(1b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
SAN-OS 33(5a) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33())
SAN-OS 33(5) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(4a) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
NX-OS 33(4) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(3) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
NX-OS 33(2) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(1c) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 32(3a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 32(x)
SAN-OS 32(2c) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 32(x)
SAN-OS 32(1a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
SAN-OS 31(3a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
SAN-OS 31(2) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
Table 9 Nondisruptive Downgrade Path from NX-OS Release 50(4b) (page 2 of2)
To SAN-OS NX-OSRelease Nondisruptive Downgrade Path
Table 10 FICON Downgrade Path from NX-OS Release 42(7b)
To SAN-OSNX-OS Release withFICON Enabled Downgrade Path
NX-OS 42(1b) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
NX-OS 41(1c) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
SAN-OS 33(1c) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
22 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Best practicesLog messages are not saved across system reboots or power outagesTherefore EMC recommends that customers configure a SyslogServer in order to redirect and capture all log messages on a remoteserver For more information please refer to the Cisco MDS 9000Family Configuration Guide available at
httpwwwciscocomenUSproductsps5989products_support_series_homehtml
Maximum ports per chassisTable 11 shows the maximum ports per chassis
a V2 indicates a 9506 or 9509 with Generation-2 Supervisors The presence of anygeneration one module in a switch will limit the maximum port count to 252This includes the 16-port 32-port 14+2 IPS4 and IPS8 cards
Known problems and limitationsFor a list of problems with this release please refer to the CiscoRelease notes located at
httpwwwciscocomenUSproductsps5989prod_release_notes_listhtml
Limitations and restrictionsThe following limitations and restrictions apply to all switches in theCisco MDS 9000 Family unless a limitation for a specific switch isstated
ldquoStorage Media Encryption (SME) limitationsrdquo on page 24
Table 11 Maximum ports per chassis
Chassis Maximum number of ports
MDS 9506-V2 192a
MDS 9509-V2 336
MDS 9513 528
23
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
ldquoSME configuration limitsrdquo on page 24
ldquoDeleting Cisco SME interfacesrdquo on page 25
ldquoCisco MDS 9124 and 9134 Multilayer fabric switchesrdquo on page 25
ldquoN-Port virtualization configuration limitsrdquo on page 25
ldquoMaximum number of zones supported in Interop Mode 4rdquo onpage 25
ldquoIPv6rdquo on page 26
ldquoIP-ACL supportrdquo on page 26
ldquoUser Rolesrdquo on page 26
ldquoUsing a RSA Version 1 Key for SSH Following an Upgraderdquo onpage 27
ldquoApplying Zone Configurations to VSAN 1rdquo on page 27
ldquoInterVSAN Routingrdquo on page 28
ldquoRSPAN Traffic Not Supported on CTS Ports on 8-GbpsSwitching Modulesrdquo on page 28
ldquoIO Accelerator Feature Limitationsrdquo on page 28
ldquoSupport for FCIP Compression Modesrdquo on page 28
ldquoSaving Copies of the Running Kickstart and System Imagesrdquo onpage 29
ldquoConfiguring Buffer Credits on a Generation 2 or Generation 3Modulerdquo on page 29
ldquoStorage services module power budgetrdquo on page 29
ldquoiSCSI proxy initiator in Celerra HighRoad environmentsrdquo onpage 30
ldquoHPUX N_port IDrdquo on page 30
ldquoInteroperability limitationsrdquo on page 31
ldquoNASBrdquo on page 31
ldquoReserved VSAN Range and Isolated VSAN Range Guidelinesrdquoon page 31
ldquoSymmetrix VMax limitationsrdquo on page 32
ldquoStorage Applications on the MSM-184rdquo on page 32
ldquoDowngrading with fport-channel-trunk enabledrdquo on page 32
ldquoLDAP Authenticationrdquo on page 33
24 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
ldquoMDS-9148 limitationsrdquo on page 33
Storage Media Encryption (SME) limitationsAn SME node can only belong to one cluster Adding the node tomore than one cluster will cause problems
Currently there is no prevention or warning in place when an attemptis made to add a node to multiple clusters
SME configuration limitsTable 12 lists the SME configuration limits for this release
Table 12 SME configuration limits
Configuration Limits
Number of switches in the fabric 10
Number of clusters per switch 1
Switches in a cluster 4
Fabrics in a cluster 2
Modules in a switch 11
Cisco MSM-184 modules in a cluster 32
Initiator-Target-LUNs (ITLs) 1024
LUNs behind a target 32
Host and target ports in a cluster 128
Number of hosts per target 128
Tape backup groups per cluster 2
Volume groups in a tape backup group 4
Cisco Key Management Center ( of keys) 32K
Targets per switch that can be FC-redirected 32
25
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Deleting Cisco SME interfacesA Cisco SME interface can be deleted from the cluster only after theinterface is administratively shut-down and all related tasksassociated with the interface shut-down are complete
Cisco MDS 9124 and 9134 Multilayer fabric switchesThe Cisco MDS 9124 and 9134 Multilayer fabric switches do notsupport the following Cisco MDS SAN-OS features
IVR Remote Span Translative loop support FCCmdash no generation quench reaction only
In addition the following features have these limits
VSANs mdash 16 maximum SPAN mdash 1 session maximum
N-Port virtualization configuration limitsThe NPV features have maximum configuration limits Table 13shows the verified and maximum limits for the NPV switchesrunning NX-OS Release 5x
Maximum number of zones supported in Interop Mode 4In interop mode 4 the maximum number of zones that is supportedin an active zone set is 2047 due to limitations in the connectedvendor switch When IVR is used in interop mode 4 the maximumnumber of zones supported including IVR zones in the active zoneset is 2047 The limit for the maximum number of IVR zones perVSAN is 250 zones (two members per zone)
Table 13 NPV features limitations
Feature Verified limits Maximum limits
FLOGIs or F Disc per NPV port group 114 114
NPV switches per NPV core switch 105 105
FLOGIs per line card on NPV core switch 400 400
26 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
IPv6The management port on Cisco MDS switches supports oneuser-configured IPv6 address but does not supportauto-configuration of an IPv6 address
IP-ACL supportDo not apply IP-ACLs to only one member of a PortChannel groupApply IP-ACLs to the entire channel group
If IP-ACLs are already configured in a Gigabit Ethernet interface youcannot add this interface to a Ethernet PortChannel group
Refer to the Cisco MDS 9000 Family Configuration Guide
User RolesIn SAN-OS Release 33(x) and earlier when a user belongs to a rolewhich has a VSAN policy set to Deny and the role allows access to aspecific set of VSANs (for example 1 through 10) the user isrestricted from performing the configuration clear execute anddebug commands which had a VSAN parameter outside thisspecified set Beginning with NX-OS Release 41(1b) these users arestill prevented from performing configuration clear execute anddebug commands as before however they are allowed to performshow commands for all VSANs The ability to execute the showcommand addresses the following
In a network environment users often need to view informationin other VSANs even though they do not have permission tomodify configurations in those VSANs
This behavior makes Cisco MDS 9000 Series switches consistentwith other Cisco products such as Cisco Nexus 7000 Seriesswitches that exhibit the same behavior for those roles (whenthey apply to the VLAN policy)
27
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Using a RSA Version 1 Key for SSH Following an UpgradeFor security reasons NX-OS Release 42(x) and higher does notsupport RSA version 1 keys As a result if you upgrade from anearlier version that did support RSA version 1 keys and you hadconfigured a RSA version 1 key for SSH then you will not be able tolog in through SSH following the upgrade
If you have a RSA version 1 key configured for SSH beforeupgrading to NX-OS Release 42(x) or higher follow these steps
1 Disable SSH
2 Create RSA version 2 DSA keys
3 Enable SSH
4 Delete any RSA version 1 keys on any remote SSH clients andreplace the version 1 keys with the new version 2 keys from theswitch
Proceed with the upgrade to NX-OS Release 42(x) or higher
If you upgrade before disabling SSH and creating RSA version 2 keysfollow these steps
1 Open a Telnet session and log in through the console
2 Issue the no feature ssh command to disable SSH
3 Issue the ssh key rsa 1024 command to create RSA version 2 keys
4 Issue the feature ssh command to enable SSH
Applying Zone Configurations to VSAN 1In the setup script you can configure system default values for thedefault-zone to be permit or deny and you can configure defaultvalues for the zone distribution method and for the zone mode
These default settings are applied when a new VSAN is createdHowever the settings will not take effect on VSAN 1 because it existsprior to running the setup script Therefore when you need thosesettings for VSAN 1 you must explicitly issue the followingcommands
zone default-zone permit vsan 1 zoneset distribute full vsan 1 zone mode enhanced vsan 1
28 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
InterVSAN RoutingWhen using InterVSAN Routing (IVR) it is recommended to enableCisco Fabric Services (CFS) on all IVR-enabled switches Failure to doso may cause mismatched active zone sets if an error occurs duringzone set activation
RSPAN Traffic Not Supported on CTS Ports on 8-Gbps Switching ModulesAn inter-switch link (ISL) that is enabled for Cisco TrustSec (CTS)encryption must be brought up in non-CTS mode to support remoteSPAN (RSPAN) traffic on the following modules
DS-X9248-96K9 Cisco MDS 9000 48-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9224-96K9 Cisco MDS 9000 24-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9248-48K9 Cisco MDS 9000 444-Port Host-Optimized8-Gbps Fibre Channel Switching Module
If the ISL link is brought up with CTS enabled random packets dropsof both RSPAN traffic and normal traffic will occur on the receiverport switch
IO Accelerator Feature LimitationsIOA does not support the following NX-OS features
IVR flows
Devices with NPV and NPIV enabled
F port trunking
bull F port channeling
Support for FCIP Compression ModesIn Cisco NX-OS Release 42(1b) and higher FCIP compression mode 1and compression mode 3 are not supported on the Cisco MSM-184module and on the SSN-16 module
29
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Saving Copies of the Running Kickstart and System ImagesAfter you upgrade to MDS NX-OS Release 42(1b) or higher you arenot allowed to delete rename move or overwrite the kickstart andsystem images that are in the current system bootvar settings on anactive or standby MDS Supervisor-2 module on any Cisco MDS 9500Series switch This restriction does not apply to the integratedsupervisor module on the MDS 9200 and MDS 9100 series switches
Configuring Buffer Credits on a Generation 2 or Generation 3 ModuleWhen you configure port mode to auto or E on a Generation 2module one of the ports will not come up for the followingconfiguration
Port Mode auto or E for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E on a Generation 3module one or two of the ports will not come up for the followingconfiguration
Port Mode auto or E for the first half of the ports the second halfof the ports or for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E for all ports in the globalbuffer pool you need to reconfigure buffer credits on one or more ofthe ports The total number of buffer credits configured for all theports in the global buffer pool should be reduced by 64
Storage services module power budgetThe MDS 9509 does not have the power budget to run seven SSMcards EMC recommends a maximum of four SSMs in one 9509Customers wishing to use more than four SSMs in one chassis shouldrefer to the Cisco MDS 9000 documentation on the Ciscocom websiteto validate that there is enough power available for their desiredconfiguration
30 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Note Upgrading to the 3000 watt power supplies will alleviate thiscondition
iSCSI proxy initiator in Celerra HighRoad environmentsEMC supports the iSCSI proxy initiator feature in Celerrareg
HighRoadreg environments In proxy initiator mode one Fibre Channelinitiator is used for all iSCSI clients who access the switch via thesame iSCSI interface (iscsi33 for example)
The initiators will use the PWWN assigned to the iSCSI interface TheiSCSI interface to which an iSCSI client will logon to is configured inthe client and must be permitted by the virtual target configured forthat initiator
The current session environment supported on the MDS is
300 sessions per port 1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no InitialR2T=yes
Refer to the specific initiator support documentation on how to setthe parameters The implementation will not perform properly ifthese bits are not set
Refer to the MDS documentation for more information regarding theconfiguration of the iSCSI proxy initiator at the following Ciscowebsite
httpwwwciscocomenUSproducts
HPUX N_port IDThe N_port ID port value of 255 (0xFF) has special meaning forHP-UX A N_port ID (FC_ID) can not be returned from a switch thatcontains this value for the N_port ID (FC_ID) port value for a HP-UXinitiator or HP-UX target port Port ID value of 255 (0xFF) cannot be
31
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
configured for HP-UX initiator port and HP-UX target ports whenconfiguring MDS FC_IDs The port_ID value is the third byte of theFC_ID
Interoperability limitationsRefer to the EMC Support Matrix (ESM) and the EMC Networked Storage Topology Guide for modes of operation and caveats
NASBThe NASB feature requires that the backup application load the tapedrive with a compatible tape cartridge prior to configuring NASB inthe backup VSAN
Reserved VSAN Range and Isolated VSAN Range GuidelinesOn an NPV switch with a trunking configuration on any interface or ona regular switch where the feature fport_channel_trunk command hasbeen issued to enable the F PortChannel feature follow theseconfiguration guidelines for reserved VSANs and the isolated VSAN
bull If trunk mode is on for any of the interfaces or NP PortChannelis up the reserved VSANs are 3040 to 4078 and they are notavailable for user configuration
bull The Exchange Virtual Fabric Protocol (EVFP) isolated VSAN is4079 and it is not available for user configuration
bull VSAN 4079 will be impacted by an upgrade to NX-OS Release42(3) depending on whether or not VSAN 4079 was createdprior to the upgrade See theldquoUpgrading Effect on VSAN 4079rdquoon page 17
The following VSAN IDs are assigned in the Fibre Channel Framingand Signaling (FC-FS) interface standard
VF_ID Value Value Description
00h Do not use as a Virtual FabricIdentifier
001h EFFh Available as a Virtual FabricIdentifier
F00h FEEh Reserved
32 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Symmetrix VMax limitationsAt the time of this writing the following features are not supportedfor use with the Symmetrix VMax
FCIP Write Acceleration
The NX-OS IOA functionality is only supported with the Q2 SREnginuity release 5874229182 or higher
For the most up to date status please refer to the current revision ofthese Release Notes on httpPowerlinkemccom and the EMCSupport Matrix available through E-Lab Interoperability Navigator (ELN) athttpelabnavigatorEMCcom
Storage Applications on the MSM-184The MDS 9000 184-Port Multiservice Module (MSM-184) does notsupport multiple concurrent storage applications Only oneapplication can run on the MSM-184 at a time
Downgrading with fport-channel-trunk enabledIf you are running MDS NX-OS Release 42(x) or higher with thefport-channel-trunk feature enabled and you downgrade to anyNX-OS 41(1x) release the installer performs a nondisruptivedowngrade even though the fport-channel-trunk feature is notsupported in NX-OS 41(1x) releases
As a result the switch is in an inconsistent state and the ports maynot function properly
FEFh Control VF-ID (see FibreChannel Link Services (FC-LS)and Fibre Channel SwitchFabric Generation 4 (FC-SW-4)standards)
FF0h FFEh Vendor specific
FFFh Do not use as a Virtual FabricIdentifier
FEFh = 4079
33
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
If you are in this state a workaround is to reboot the switch followingthe upgrade
LDAP AuthenticationThere is currently a limitation in the LDAP server configuration CLIthat prevents the use of an OU with spaces in the name Normallythese OU names could be surrounded by quotation marks howeverquotation marks are not supported by the ldap-server command
MDS-9148 limitationsThe Cisco MDS 9148 Multilayer Fabric Switch does not support thefollowing NX-OS features
Medium and Long range 4GB Agilent
IVR
Remote Span
Translative loop support
FCC - no generation quench reaction only
FC-Redirect
In addition the following features have these limits
VSANS - 31 maximum
SPAN - 1 session maximum
Technical notesThe following sections provide further information on technicalnotes
EMC Email Home for Cisco MDS switchesInstallation and Trouble shooting instructions can be found in thedocumentation located at the EMC Customer Service Internalwebsite
httpwwwcsisusemccomcsweb2esnesnhomehtmConnectrix20MDS20900020Family
34 EMC Connectrix MDS 9000 NX-OS Release Notes
Technical notes
Customers requiring installation of this solution should contact theirEMC Customer Engineer to assist with the installation and providethe documentation
Supported iSCSI sessionsThe current iSCSI session environment supported on the MDS is
300 sessions per port
1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no
InitialR2T=yes
Upgrading Cisco SAN-OSThere are several methods available for upgrading SAN-OS SoftwareEMC personnel are strongly recommended that all upgrades be doneby the Automated One-Step Upgrade using the install all
command EMC personnel should refer to the Connectrix MDS 9000Family Software Image Upgrade Instructions for a complete list ofprerequisites and instructions for performing the upgrade Thisdocument along with tftp software is available on the GlobalServices website at httpwwwcsisusEMCcom under ApplicationDownload Area ESN Product Information Connectrix MDS 9000Family
The Software Upgrade Wizard is an option for upgrades While theinstall all is the preferred method the Software Install Wizard canalso be used
Supported configuration parametersFor the most up-to-date information refer to the EMC Support Matrixavailable through E-Lab Interoperability Navigator athttpelabnavigatoremccom for the latest information onsupported configurations
35
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
Supported zoning parametersRefer to the EMC Networked Storage Topology Guide for the mostup-to-date information on supported zoning parameters
At the time these notes were published the following parameterswere supported
20 VSANs 5 Hops 2000 Unique members per physical infrastructure 1000 Zonesets per physical infrastructure 2000 Zones per physical infrastructure 1 FCIP tunnel
Supported IVR parameters IVR zone members 1000 IVR zones 1000 IVR zone sets 32 VSANS 20 IVR enabled switches 64
An RPQ can be submitted for any configurations that exceed thislimit
Managing zone changes in multiswitch fabricsZoning changes may be made through Fabric Manager or CLI Whenaccessing Fabric Manager or CLI the user does so from the point ofview of one switch That is Fabric Manager and CLI are accessed byentering the IP address of one switch in the fabric
When zoning changes are made the applicable VSAN and zone setdata is propagated to the rest of the switches in the fabric via the ISLs
When zoning changes are made to a VSAN the zone set data ispropagated to the rest of the switches in the fabric via the ISLs Bydefault only the active zone set information is relayed to all switchesin the VSAN If the user accesses the Fabric Manager and CLI fromanother switch in the fabric the new VSAN and zone set informationwill not be viewable To view the active and inactive zone set on theother switches in the fabric the user must log in to the CLI and issuea command from the EXEC prompt
36 EMC Connectrix MDS 9000 NX-OS Release Notes
Documentation
Example The following is an example of copying VSAN 1 through 20 zoningdata
CiscoMDS_name zone copy active full vsan 1-20
CiscoMDS_name conf t
Enter configuration commands one per line End with CNTL Z
CiscoMDS_name(config) zoneset distribute full vsan 1-20
CiscoMDS_name(config)
Note This command needs to be issued on all switches in the fabric one timeonly
This is a nondisruptive command After issuing the commands theuser will now see the active and inactive zone sets for the specifiedVSANs on any switch that is chosen from which to manage the fabric
After a zoning change is made save the running configuration to thestartup configuration
DocumentationSend documentation comments to mdsfeedback-doccom
Product DocumentationAs of NX-OS Release 42(1a) software configuration information isavailable in new feature-specific configuration guides for thefollowing information
System management
Interfaces
Fabric
Quality of service
Security
IP services
High availability and redundancy
37
Software media organization and files
EMC Connectrix MDS 9000 NX-OS Release Notes
The information in these new guides previously existed in the CiscoMDS 9000 Family CLI Configuration Guide That configuration guideremains available on Ciscocom and should be used for all softwarereleases prior to NX-OS Release 42(1a) Configuration guidesaddress the features introduced in or available in a particular releaseSelect and view the configuration guide that pertains to the softwareinstalled in your switch
In addition Fabric Manager information has been removed from theMDS NX-OS Release Notes (this document) and placed intostandalone Fabric Manager Release Notes that support both CiscoMDS 9000 Family switches and Cisco Nexus 5000 Series switchesThe Cisco Fabric Manager Release Notes are available onhttpPowerlinkemccom and from the following website
httpwwwciscocomenUSpartnerproductsps10495prod_release_notes_listhtml
Technical supportThese release notes complement a Cisco documentation set EachCisco document refers to where to get help However for any itemssupplied by EMC see ldquoTroubleshooting and getting helprdquo onpage 38
Software media organization and filesFor information on related software environment and systemrequirements refer to the EMC Support Matrix on EMC Powerlink at
httpPowerlinkEMCcom
InstallationFor hardware installation information refer to the Cisco MDS HWInstallation Guides available at Ciscocom
For EMC-specific installation information refer to ldquoEnvironment andsystem requirementsrdquo on page 5 in this document
38 EMC Connectrix MDS 9000 NX-OS Release Notes
Troubleshooting and getting help
Troubleshooting and getting helpEMC support product and licensing information can be obtained asfollows
Product information mdash For documentation release notes softwareupdates or for information about EMC products licensing andservice go to the EMC Powerlink website (registration required) at
httpPowerlinkEMCcom
Technical support mdash For technical support go to EMC CustomerService on Powerlink To open a service request through Powerlinkyou must have a valid support agreement Please contact your EMCsales representative for details about obtaining a valid supportagreement or to answer any questions about your account
Copyright copy 2011 EMC Corporation All rights reserved
EMC believes the information in this publication is accurate as of its publication date The information issubject to change without notice
THE INFORMATION IN THIS PUBLICATION IS PROVIDED ldquoAS ISrdquo EMC CORPORATION MAKES NOREPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION INTHIS PUBLICATION AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OFMERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Use copying and distribution of any EMC software described in this publication requires an applicablesoftware license
For the most up-to-date regulatory document for your product line go to the Technical Documentation andAdvisories section on EMC Powerlink
For the most up-to-date listing of EMC product names see EMC Corporation Trademarks on EMCcom
All other trademarks used herein are the property of their respective owners
20 EMC Connectrix MDS 9000 NX-OS Release Notes
Environment and system requirements
bull FICON If you have FICON enabled the downgrade path isdifferent See Table 10 on page 21
Note A downgrade from NX-OS Release 4x to SAN-OS Release 33(1c) is notsupported on MDS switches when FC-Redirect based applications such asData Mobility Manager or Storage Media Encryption are configured in thefabric if either of the following conditions are satisfied
1 A target for which FC-Redirect is configured is connected locally and thereare Generation 1 modules with ISLs configured in the switch
2 A host for which FC-redirect is configured is connected locally ona Generation 1 module
If these conditions exist remove the application configuration forthese targets and hosts before proceeding with the downgrade
Use Table 9 on page 20 to determine the nondisruptive downgradepath from Cisco NX-OS Release 50(4b) Find the NX-OS or SAN-OSimage you want to downgrade to in the To SAN-OSNX-OS Releasecolumn of the table and use the path recommended
Note The software downgrade information in Table 10 on page 21 appliesonly to Fibre Channel switching traffic Downgrading system softwaredisrupts IP and SSM intelligent services traffic
Table 9 Nondisruptive Downgrade Path from NX-OS Release 50(4b) (page 1 of2)
To SAN-OS NX-OSRelease Nondisruptive Downgrade Path
NX-OS 50(4) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 50(1a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(7b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(5) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(3) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(1b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 42(1a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
NX-OS 41(3a) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
21
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Use Table 10 to determine your nondisruptive downgrade path if youhave FICON enabled from Cisco NX-OS Release 42(7b) Find the imagerelease number you are currently using in the Current Release withFICON Enabled column of the table and use the path recommended
NX-OS 41(1b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
SAN-OS 33(5a) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33())
SAN-OS 33(5) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(4a) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
NX-OS 33(4) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(3) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
NX-OS 33(2) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(1c) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 32(3a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 32(x)
SAN-OS 32(2c) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 32(x)
SAN-OS 32(1a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
SAN-OS 31(3a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
SAN-OS 31(2) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
Table 9 Nondisruptive Downgrade Path from NX-OS Release 50(4b) (page 2 of2)
To SAN-OS NX-OSRelease Nondisruptive Downgrade Path
Table 10 FICON Downgrade Path from NX-OS Release 42(7b)
To SAN-OSNX-OS Release withFICON Enabled Downgrade Path
NX-OS 42(1b) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
NX-OS 41(1c) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
SAN-OS 33(1c) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
22 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Best practicesLog messages are not saved across system reboots or power outagesTherefore EMC recommends that customers configure a SyslogServer in order to redirect and capture all log messages on a remoteserver For more information please refer to the Cisco MDS 9000Family Configuration Guide available at
httpwwwciscocomenUSproductsps5989products_support_series_homehtml
Maximum ports per chassisTable 11 shows the maximum ports per chassis
a V2 indicates a 9506 or 9509 with Generation-2 Supervisors The presence of anygeneration one module in a switch will limit the maximum port count to 252This includes the 16-port 32-port 14+2 IPS4 and IPS8 cards
Known problems and limitationsFor a list of problems with this release please refer to the CiscoRelease notes located at
httpwwwciscocomenUSproductsps5989prod_release_notes_listhtml
Limitations and restrictionsThe following limitations and restrictions apply to all switches in theCisco MDS 9000 Family unless a limitation for a specific switch isstated
ldquoStorage Media Encryption (SME) limitationsrdquo on page 24
Table 11 Maximum ports per chassis
Chassis Maximum number of ports
MDS 9506-V2 192a
MDS 9509-V2 336
MDS 9513 528
23
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
ldquoSME configuration limitsrdquo on page 24
ldquoDeleting Cisco SME interfacesrdquo on page 25
ldquoCisco MDS 9124 and 9134 Multilayer fabric switchesrdquo on page 25
ldquoN-Port virtualization configuration limitsrdquo on page 25
ldquoMaximum number of zones supported in Interop Mode 4rdquo onpage 25
ldquoIPv6rdquo on page 26
ldquoIP-ACL supportrdquo on page 26
ldquoUser Rolesrdquo on page 26
ldquoUsing a RSA Version 1 Key for SSH Following an Upgraderdquo onpage 27
ldquoApplying Zone Configurations to VSAN 1rdquo on page 27
ldquoInterVSAN Routingrdquo on page 28
ldquoRSPAN Traffic Not Supported on CTS Ports on 8-GbpsSwitching Modulesrdquo on page 28
ldquoIO Accelerator Feature Limitationsrdquo on page 28
ldquoSupport for FCIP Compression Modesrdquo on page 28
ldquoSaving Copies of the Running Kickstart and System Imagesrdquo onpage 29
ldquoConfiguring Buffer Credits on a Generation 2 or Generation 3Modulerdquo on page 29
ldquoStorage services module power budgetrdquo on page 29
ldquoiSCSI proxy initiator in Celerra HighRoad environmentsrdquo onpage 30
ldquoHPUX N_port IDrdquo on page 30
ldquoInteroperability limitationsrdquo on page 31
ldquoNASBrdquo on page 31
ldquoReserved VSAN Range and Isolated VSAN Range Guidelinesrdquoon page 31
ldquoSymmetrix VMax limitationsrdquo on page 32
ldquoStorage Applications on the MSM-184rdquo on page 32
ldquoDowngrading with fport-channel-trunk enabledrdquo on page 32
ldquoLDAP Authenticationrdquo on page 33
24 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
ldquoMDS-9148 limitationsrdquo on page 33
Storage Media Encryption (SME) limitationsAn SME node can only belong to one cluster Adding the node tomore than one cluster will cause problems
Currently there is no prevention or warning in place when an attemptis made to add a node to multiple clusters
SME configuration limitsTable 12 lists the SME configuration limits for this release
Table 12 SME configuration limits
Configuration Limits
Number of switches in the fabric 10
Number of clusters per switch 1
Switches in a cluster 4
Fabrics in a cluster 2
Modules in a switch 11
Cisco MSM-184 modules in a cluster 32
Initiator-Target-LUNs (ITLs) 1024
LUNs behind a target 32
Host and target ports in a cluster 128
Number of hosts per target 128
Tape backup groups per cluster 2
Volume groups in a tape backup group 4
Cisco Key Management Center ( of keys) 32K
Targets per switch that can be FC-redirected 32
25
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Deleting Cisco SME interfacesA Cisco SME interface can be deleted from the cluster only after theinterface is administratively shut-down and all related tasksassociated with the interface shut-down are complete
Cisco MDS 9124 and 9134 Multilayer fabric switchesThe Cisco MDS 9124 and 9134 Multilayer fabric switches do notsupport the following Cisco MDS SAN-OS features
IVR Remote Span Translative loop support FCCmdash no generation quench reaction only
In addition the following features have these limits
VSANs mdash 16 maximum SPAN mdash 1 session maximum
N-Port virtualization configuration limitsThe NPV features have maximum configuration limits Table 13shows the verified and maximum limits for the NPV switchesrunning NX-OS Release 5x
Maximum number of zones supported in Interop Mode 4In interop mode 4 the maximum number of zones that is supportedin an active zone set is 2047 due to limitations in the connectedvendor switch When IVR is used in interop mode 4 the maximumnumber of zones supported including IVR zones in the active zoneset is 2047 The limit for the maximum number of IVR zones perVSAN is 250 zones (two members per zone)
Table 13 NPV features limitations
Feature Verified limits Maximum limits
FLOGIs or F Disc per NPV port group 114 114
NPV switches per NPV core switch 105 105
FLOGIs per line card on NPV core switch 400 400
26 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
IPv6The management port on Cisco MDS switches supports oneuser-configured IPv6 address but does not supportauto-configuration of an IPv6 address
IP-ACL supportDo not apply IP-ACLs to only one member of a PortChannel groupApply IP-ACLs to the entire channel group
If IP-ACLs are already configured in a Gigabit Ethernet interface youcannot add this interface to a Ethernet PortChannel group
Refer to the Cisco MDS 9000 Family Configuration Guide
User RolesIn SAN-OS Release 33(x) and earlier when a user belongs to a rolewhich has a VSAN policy set to Deny and the role allows access to aspecific set of VSANs (for example 1 through 10) the user isrestricted from performing the configuration clear execute anddebug commands which had a VSAN parameter outside thisspecified set Beginning with NX-OS Release 41(1b) these users arestill prevented from performing configuration clear execute anddebug commands as before however they are allowed to performshow commands for all VSANs The ability to execute the showcommand addresses the following
In a network environment users often need to view informationin other VSANs even though they do not have permission tomodify configurations in those VSANs
This behavior makes Cisco MDS 9000 Series switches consistentwith other Cisco products such as Cisco Nexus 7000 Seriesswitches that exhibit the same behavior for those roles (whenthey apply to the VLAN policy)
27
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Using a RSA Version 1 Key for SSH Following an UpgradeFor security reasons NX-OS Release 42(x) and higher does notsupport RSA version 1 keys As a result if you upgrade from anearlier version that did support RSA version 1 keys and you hadconfigured a RSA version 1 key for SSH then you will not be able tolog in through SSH following the upgrade
If you have a RSA version 1 key configured for SSH beforeupgrading to NX-OS Release 42(x) or higher follow these steps
1 Disable SSH
2 Create RSA version 2 DSA keys
3 Enable SSH
4 Delete any RSA version 1 keys on any remote SSH clients andreplace the version 1 keys with the new version 2 keys from theswitch
Proceed with the upgrade to NX-OS Release 42(x) or higher
If you upgrade before disabling SSH and creating RSA version 2 keysfollow these steps
1 Open a Telnet session and log in through the console
2 Issue the no feature ssh command to disable SSH
3 Issue the ssh key rsa 1024 command to create RSA version 2 keys
4 Issue the feature ssh command to enable SSH
Applying Zone Configurations to VSAN 1In the setup script you can configure system default values for thedefault-zone to be permit or deny and you can configure defaultvalues for the zone distribution method and for the zone mode
These default settings are applied when a new VSAN is createdHowever the settings will not take effect on VSAN 1 because it existsprior to running the setup script Therefore when you need thosesettings for VSAN 1 you must explicitly issue the followingcommands
zone default-zone permit vsan 1 zoneset distribute full vsan 1 zone mode enhanced vsan 1
28 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
InterVSAN RoutingWhen using InterVSAN Routing (IVR) it is recommended to enableCisco Fabric Services (CFS) on all IVR-enabled switches Failure to doso may cause mismatched active zone sets if an error occurs duringzone set activation
RSPAN Traffic Not Supported on CTS Ports on 8-Gbps Switching ModulesAn inter-switch link (ISL) that is enabled for Cisco TrustSec (CTS)encryption must be brought up in non-CTS mode to support remoteSPAN (RSPAN) traffic on the following modules
DS-X9248-96K9 Cisco MDS 9000 48-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9224-96K9 Cisco MDS 9000 24-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9248-48K9 Cisco MDS 9000 444-Port Host-Optimized8-Gbps Fibre Channel Switching Module
If the ISL link is brought up with CTS enabled random packets dropsof both RSPAN traffic and normal traffic will occur on the receiverport switch
IO Accelerator Feature LimitationsIOA does not support the following NX-OS features
IVR flows
Devices with NPV and NPIV enabled
F port trunking
bull F port channeling
Support for FCIP Compression ModesIn Cisco NX-OS Release 42(1b) and higher FCIP compression mode 1and compression mode 3 are not supported on the Cisco MSM-184module and on the SSN-16 module
29
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Saving Copies of the Running Kickstart and System ImagesAfter you upgrade to MDS NX-OS Release 42(1b) or higher you arenot allowed to delete rename move or overwrite the kickstart andsystem images that are in the current system bootvar settings on anactive or standby MDS Supervisor-2 module on any Cisco MDS 9500Series switch This restriction does not apply to the integratedsupervisor module on the MDS 9200 and MDS 9100 series switches
Configuring Buffer Credits on a Generation 2 or Generation 3 ModuleWhen you configure port mode to auto or E on a Generation 2module one of the ports will not come up for the followingconfiguration
Port Mode auto or E for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E on a Generation 3module one or two of the ports will not come up for the followingconfiguration
Port Mode auto or E for the first half of the ports the second halfof the ports or for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E for all ports in the globalbuffer pool you need to reconfigure buffer credits on one or more ofthe ports The total number of buffer credits configured for all theports in the global buffer pool should be reduced by 64
Storage services module power budgetThe MDS 9509 does not have the power budget to run seven SSMcards EMC recommends a maximum of four SSMs in one 9509Customers wishing to use more than four SSMs in one chassis shouldrefer to the Cisco MDS 9000 documentation on the Ciscocom websiteto validate that there is enough power available for their desiredconfiguration
30 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Note Upgrading to the 3000 watt power supplies will alleviate thiscondition
iSCSI proxy initiator in Celerra HighRoad environmentsEMC supports the iSCSI proxy initiator feature in Celerrareg
HighRoadreg environments In proxy initiator mode one Fibre Channelinitiator is used for all iSCSI clients who access the switch via thesame iSCSI interface (iscsi33 for example)
The initiators will use the PWWN assigned to the iSCSI interface TheiSCSI interface to which an iSCSI client will logon to is configured inthe client and must be permitted by the virtual target configured forthat initiator
The current session environment supported on the MDS is
300 sessions per port 1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no InitialR2T=yes
Refer to the specific initiator support documentation on how to setthe parameters The implementation will not perform properly ifthese bits are not set
Refer to the MDS documentation for more information regarding theconfiguration of the iSCSI proxy initiator at the following Ciscowebsite
httpwwwciscocomenUSproducts
HPUX N_port IDThe N_port ID port value of 255 (0xFF) has special meaning forHP-UX A N_port ID (FC_ID) can not be returned from a switch thatcontains this value for the N_port ID (FC_ID) port value for a HP-UXinitiator or HP-UX target port Port ID value of 255 (0xFF) cannot be
31
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
configured for HP-UX initiator port and HP-UX target ports whenconfiguring MDS FC_IDs The port_ID value is the third byte of theFC_ID
Interoperability limitationsRefer to the EMC Support Matrix (ESM) and the EMC Networked Storage Topology Guide for modes of operation and caveats
NASBThe NASB feature requires that the backup application load the tapedrive with a compatible tape cartridge prior to configuring NASB inthe backup VSAN
Reserved VSAN Range and Isolated VSAN Range GuidelinesOn an NPV switch with a trunking configuration on any interface or ona regular switch where the feature fport_channel_trunk command hasbeen issued to enable the F PortChannel feature follow theseconfiguration guidelines for reserved VSANs and the isolated VSAN
bull If trunk mode is on for any of the interfaces or NP PortChannelis up the reserved VSANs are 3040 to 4078 and they are notavailable for user configuration
bull The Exchange Virtual Fabric Protocol (EVFP) isolated VSAN is4079 and it is not available for user configuration
bull VSAN 4079 will be impacted by an upgrade to NX-OS Release42(3) depending on whether or not VSAN 4079 was createdprior to the upgrade See theldquoUpgrading Effect on VSAN 4079rdquoon page 17
The following VSAN IDs are assigned in the Fibre Channel Framingand Signaling (FC-FS) interface standard
VF_ID Value Value Description
00h Do not use as a Virtual FabricIdentifier
001h EFFh Available as a Virtual FabricIdentifier
F00h FEEh Reserved
32 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Symmetrix VMax limitationsAt the time of this writing the following features are not supportedfor use with the Symmetrix VMax
FCIP Write Acceleration
The NX-OS IOA functionality is only supported with the Q2 SREnginuity release 5874229182 or higher
For the most up to date status please refer to the current revision ofthese Release Notes on httpPowerlinkemccom and the EMCSupport Matrix available through E-Lab Interoperability Navigator (ELN) athttpelabnavigatorEMCcom
Storage Applications on the MSM-184The MDS 9000 184-Port Multiservice Module (MSM-184) does notsupport multiple concurrent storage applications Only oneapplication can run on the MSM-184 at a time
Downgrading with fport-channel-trunk enabledIf you are running MDS NX-OS Release 42(x) or higher with thefport-channel-trunk feature enabled and you downgrade to anyNX-OS 41(1x) release the installer performs a nondisruptivedowngrade even though the fport-channel-trunk feature is notsupported in NX-OS 41(1x) releases
As a result the switch is in an inconsistent state and the ports maynot function properly
FEFh Control VF-ID (see FibreChannel Link Services (FC-LS)and Fibre Channel SwitchFabric Generation 4 (FC-SW-4)standards)
FF0h FFEh Vendor specific
FFFh Do not use as a Virtual FabricIdentifier
FEFh = 4079
33
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
If you are in this state a workaround is to reboot the switch followingthe upgrade
LDAP AuthenticationThere is currently a limitation in the LDAP server configuration CLIthat prevents the use of an OU with spaces in the name Normallythese OU names could be surrounded by quotation marks howeverquotation marks are not supported by the ldap-server command
MDS-9148 limitationsThe Cisco MDS 9148 Multilayer Fabric Switch does not support thefollowing NX-OS features
Medium and Long range 4GB Agilent
IVR
Remote Span
Translative loop support
FCC - no generation quench reaction only
FC-Redirect
In addition the following features have these limits
VSANS - 31 maximum
SPAN - 1 session maximum
Technical notesThe following sections provide further information on technicalnotes
EMC Email Home for Cisco MDS switchesInstallation and Trouble shooting instructions can be found in thedocumentation located at the EMC Customer Service Internalwebsite
httpwwwcsisusemccomcsweb2esnesnhomehtmConnectrix20MDS20900020Family
34 EMC Connectrix MDS 9000 NX-OS Release Notes
Technical notes
Customers requiring installation of this solution should contact theirEMC Customer Engineer to assist with the installation and providethe documentation
Supported iSCSI sessionsThe current iSCSI session environment supported on the MDS is
300 sessions per port
1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no
InitialR2T=yes
Upgrading Cisco SAN-OSThere are several methods available for upgrading SAN-OS SoftwareEMC personnel are strongly recommended that all upgrades be doneby the Automated One-Step Upgrade using the install all
command EMC personnel should refer to the Connectrix MDS 9000Family Software Image Upgrade Instructions for a complete list ofprerequisites and instructions for performing the upgrade Thisdocument along with tftp software is available on the GlobalServices website at httpwwwcsisusEMCcom under ApplicationDownload Area ESN Product Information Connectrix MDS 9000Family
The Software Upgrade Wizard is an option for upgrades While theinstall all is the preferred method the Software Install Wizard canalso be used
Supported configuration parametersFor the most up-to-date information refer to the EMC Support Matrixavailable through E-Lab Interoperability Navigator athttpelabnavigatoremccom for the latest information onsupported configurations
35
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
Supported zoning parametersRefer to the EMC Networked Storage Topology Guide for the mostup-to-date information on supported zoning parameters
At the time these notes were published the following parameterswere supported
20 VSANs 5 Hops 2000 Unique members per physical infrastructure 1000 Zonesets per physical infrastructure 2000 Zones per physical infrastructure 1 FCIP tunnel
Supported IVR parameters IVR zone members 1000 IVR zones 1000 IVR zone sets 32 VSANS 20 IVR enabled switches 64
An RPQ can be submitted for any configurations that exceed thislimit
Managing zone changes in multiswitch fabricsZoning changes may be made through Fabric Manager or CLI Whenaccessing Fabric Manager or CLI the user does so from the point ofview of one switch That is Fabric Manager and CLI are accessed byentering the IP address of one switch in the fabric
When zoning changes are made the applicable VSAN and zone setdata is propagated to the rest of the switches in the fabric via the ISLs
When zoning changes are made to a VSAN the zone set data ispropagated to the rest of the switches in the fabric via the ISLs Bydefault only the active zone set information is relayed to all switchesin the VSAN If the user accesses the Fabric Manager and CLI fromanother switch in the fabric the new VSAN and zone set informationwill not be viewable To view the active and inactive zone set on theother switches in the fabric the user must log in to the CLI and issuea command from the EXEC prompt
36 EMC Connectrix MDS 9000 NX-OS Release Notes
Documentation
Example The following is an example of copying VSAN 1 through 20 zoningdata
CiscoMDS_name zone copy active full vsan 1-20
CiscoMDS_name conf t
Enter configuration commands one per line End with CNTL Z
CiscoMDS_name(config) zoneset distribute full vsan 1-20
CiscoMDS_name(config)
Note This command needs to be issued on all switches in the fabric one timeonly
This is a nondisruptive command After issuing the commands theuser will now see the active and inactive zone sets for the specifiedVSANs on any switch that is chosen from which to manage the fabric
After a zoning change is made save the running configuration to thestartup configuration
DocumentationSend documentation comments to mdsfeedback-doccom
Product DocumentationAs of NX-OS Release 42(1a) software configuration information isavailable in new feature-specific configuration guides for thefollowing information
System management
Interfaces
Fabric
Quality of service
Security
IP services
High availability and redundancy
37
Software media organization and files
EMC Connectrix MDS 9000 NX-OS Release Notes
The information in these new guides previously existed in the CiscoMDS 9000 Family CLI Configuration Guide That configuration guideremains available on Ciscocom and should be used for all softwarereleases prior to NX-OS Release 42(1a) Configuration guidesaddress the features introduced in or available in a particular releaseSelect and view the configuration guide that pertains to the softwareinstalled in your switch
In addition Fabric Manager information has been removed from theMDS NX-OS Release Notes (this document) and placed intostandalone Fabric Manager Release Notes that support both CiscoMDS 9000 Family switches and Cisco Nexus 5000 Series switchesThe Cisco Fabric Manager Release Notes are available onhttpPowerlinkemccom and from the following website
httpwwwciscocomenUSpartnerproductsps10495prod_release_notes_listhtml
Technical supportThese release notes complement a Cisco documentation set EachCisco document refers to where to get help However for any itemssupplied by EMC see ldquoTroubleshooting and getting helprdquo onpage 38
Software media organization and filesFor information on related software environment and systemrequirements refer to the EMC Support Matrix on EMC Powerlink at
httpPowerlinkEMCcom
InstallationFor hardware installation information refer to the Cisco MDS HWInstallation Guides available at Ciscocom
For EMC-specific installation information refer to ldquoEnvironment andsystem requirementsrdquo on page 5 in this document
38 EMC Connectrix MDS 9000 NX-OS Release Notes
Troubleshooting and getting help
Troubleshooting and getting helpEMC support product and licensing information can be obtained asfollows
Product information mdash For documentation release notes softwareupdates or for information about EMC products licensing andservice go to the EMC Powerlink website (registration required) at
httpPowerlinkEMCcom
Technical support mdash For technical support go to EMC CustomerService on Powerlink To open a service request through Powerlinkyou must have a valid support agreement Please contact your EMCsales representative for details about obtaining a valid supportagreement or to answer any questions about your account
Copyright copy 2011 EMC Corporation All rights reserved
EMC believes the information in this publication is accurate as of its publication date The information issubject to change without notice
THE INFORMATION IN THIS PUBLICATION IS PROVIDED ldquoAS ISrdquo EMC CORPORATION MAKES NOREPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION INTHIS PUBLICATION AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OFMERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Use copying and distribution of any EMC software described in this publication requires an applicablesoftware license
For the most up-to-date regulatory document for your product line go to the Technical Documentation andAdvisories section on EMC Powerlink
For the most up-to-date listing of EMC product names see EMC Corporation Trademarks on EMCcom
All other trademarks used herein are the property of their respective owners
21
Environment and system requirements
EMC Connectrix MDS 9000 NX-OS Release Notes
Use Table 10 to determine your nondisruptive downgrade path if youhave FICON enabled from Cisco NX-OS Release 42(7b) Find the imagerelease number you are currently using in the Current Release withFICON Enabled column of the table and use the path recommended
NX-OS 41(1b) You can nondisruptively downgrade directly from NX-OS Release 50(4b)
SAN-OS 33(5a) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33())
SAN-OS 33(5) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(4a) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
NX-OS 33(4) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(3) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
NX-OS 33(2) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 33(1c) Downgrade to NX-OS Release 4x and then downgrade to SAN-OS 33(x)
SAN-OS 32(3a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 32(x)
SAN-OS 32(2c) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 32(x)
SAN-OS 32(1a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
SAN-OS 31(3a) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
SAN-OS 31(2) Downgrade to NX-OS Release 4x then downgrade to SAN-OS Release Release 31(x)
Table 9 Nondisruptive Downgrade Path from NX-OS Release 50(4b) (page 2 of2)
To SAN-OS NX-OSRelease Nondisruptive Downgrade Path
Table 10 FICON Downgrade Path from NX-OS Release 42(7b)
To SAN-OSNX-OS Release withFICON Enabled Downgrade Path
NX-OS 42(1b) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
NX-OS 41(1c) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
SAN-OS 33(1c) You can nondisruptively downgrade directly from NX-OS Release 42(7b)
22 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Best practicesLog messages are not saved across system reboots or power outagesTherefore EMC recommends that customers configure a SyslogServer in order to redirect and capture all log messages on a remoteserver For more information please refer to the Cisco MDS 9000Family Configuration Guide available at
httpwwwciscocomenUSproductsps5989products_support_series_homehtml
Maximum ports per chassisTable 11 shows the maximum ports per chassis
a V2 indicates a 9506 or 9509 with Generation-2 Supervisors The presence of anygeneration one module in a switch will limit the maximum port count to 252This includes the 16-port 32-port 14+2 IPS4 and IPS8 cards
Known problems and limitationsFor a list of problems with this release please refer to the CiscoRelease notes located at
httpwwwciscocomenUSproductsps5989prod_release_notes_listhtml
Limitations and restrictionsThe following limitations and restrictions apply to all switches in theCisco MDS 9000 Family unless a limitation for a specific switch isstated
ldquoStorage Media Encryption (SME) limitationsrdquo on page 24
Table 11 Maximum ports per chassis
Chassis Maximum number of ports
MDS 9506-V2 192a
MDS 9509-V2 336
MDS 9513 528
23
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
ldquoSME configuration limitsrdquo on page 24
ldquoDeleting Cisco SME interfacesrdquo on page 25
ldquoCisco MDS 9124 and 9134 Multilayer fabric switchesrdquo on page 25
ldquoN-Port virtualization configuration limitsrdquo on page 25
ldquoMaximum number of zones supported in Interop Mode 4rdquo onpage 25
ldquoIPv6rdquo on page 26
ldquoIP-ACL supportrdquo on page 26
ldquoUser Rolesrdquo on page 26
ldquoUsing a RSA Version 1 Key for SSH Following an Upgraderdquo onpage 27
ldquoApplying Zone Configurations to VSAN 1rdquo on page 27
ldquoInterVSAN Routingrdquo on page 28
ldquoRSPAN Traffic Not Supported on CTS Ports on 8-GbpsSwitching Modulesrdquo on page 28
ldquoIO Accelerator Feature Limitationsrdquo on page 28
ldquoSupport for FCIP Compression Modesrdquo on page 28
ldquoSaving Copies of the Running Kickstart and System Imagesrdquo onpage 29
ldquoConfiguring Buffer Credits on a Generation 2 or Generation 3Modulerdquo on page 29
ldquoStorage services module power budgetrdquo on page 29
ldquoiSCSI proxy initiator in Celerra HighRoad environmentsrdquo onpage 30
ldquoHPUX N_port IDrdquo on page 30
ldquoInteroperability limitationsrdquo on page 31
ldquoNASBrdquo on page 31
ldquoReserved VSAN Range and Isolated VSAN Range Guidelinesrdquoon page 31
ldquoSymmetrix VMax limitationsrdquo on page 32
ldquoStorage Applications on the MSM-184rdquo on page 32
ldquoDowngrading with fport-channel-trunk enabledrdquo on page 32
ldquoLDAP Authenticationrdquo on page 33
24 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
ldquoMDS-9148 limitationsrdquo on page 33
Storage Media Encryption (SME) limitationsAn SME node can only belong to one cluster Adding the node tomore than one cluster will cause problems
Currently there is no prevention or warning in place when an attemptis made to add a node to multiple clusters
SME configuration limitsTable 12 lists the SME configuration limits for this release
Table 12 SME configuration limits
Configuration Limits
Number of switches in the fabric 10
Number of clusters per switch 1
Switches in a cluster 4
Fabrics in a cluster 2
Modules in a switch 11
Cisco MSM-184 modules in a cluster 32
Initiator-Target-LUNs (ITLs) 1024
LUNs behind a target 32
Host and target ports in a cluster 128
Number of hosts per target 128
Tape backup groups per cluster 2
Volume groups in a tape backup group 4
Cisco Key Management Center ( of keys) 32K
Targets per switch that can be FC-redirected 32
25
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Deleting Cisco SME interfacesA Cisco SME interface can be deleted from the cluster only after theinterface is administratively shut-down and all related tasksassociated with the interface shut-down are complete
Cisco MDS 9124 and 9134 Multilayer fabric switchesThe Cisco MDS 9124 and 9134 Multilayer fabric switches do notsupport the following Cisco MDS SAN-OS features
IVR Remote Span Translative loop support FCCmdash no generation quench reaction only
In addition the following features have these limits
VSANs mdash 16 maximum SPAN mdash 1 session maximum
N-Port virtualization configuration limitsThe NPV features have maximum configuration limits Table 13shows the verified and maximum limits for the NPV switchesrunning NX-OS Release 5x
Maximum number of zones supported in Interop Mode 4In interop mode 4 the maximum number of zones that is supportedin an active zone set is 2047 due to limitations in the connectedvendor switch When IVR is used in interop mode 4 the maximumnumber of zones supported including IVR zones in the active zoneset is 2047 The limit for the maximum number of IVR zones perVSAN is 250 zones (two members per zone)
Table 13 NPV features limitations
Feature Verified limits Maximum limits
FLOGIs or F Disc per NPV port group 114 114
NPV switches per NPV core switch 105 105
FLOGIs per line card on NPV core switch 400 400
26 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
IPv6The management port on Cisco MDS switches supports oneuser-configured IPv6 address but does not supportauto-configuration of an IPv6 address
IP-ACL supportDo not apply IP-ACLs to only one member of a PortChannel groupApply IP-ACLs to the entire channel group
If IP-ACLs are already configured in a Gigabit Ethernet interface youcannot add this interface to a Ethernet PortChannel group
Refer to the Cisco MDS 9000 Family Configuration Guide
User RolesIn SAN-OS Release 33(x) and earlier when a user belongs to a rolewhich has a VSAN policy set to Deny and the role allows access to aspecific set of VSANs (for example 1 through 10) the user isrestricted from performing the configuration clear execute anddebug commands which had a VSAN parameter outside thisspecified set Beginning with NX-OS Release 41(1b) these users arestill prevented from performing configuration clear execute anddebug commands as before however they are allowed to performshow commands for all VSANs The ability to execute the showcommand addresses the following
In a network environment users often need to view informationin other VSANs even though they do not have permission tomodify configurations in those VSANs
This behavior makes Cisco MDS 9000 Series switches consistentwith other Cisco products such as Cisco Nexus 7000 Seriesswitches that exhibit the same behavior for those roles (whenthey apply to the VLAN policy)
27
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Using a RSA Version 1 Key for SSH Following an UpgradeFor security reasons NX-OS Release 42(x) and higher does notsupport RSA version 1 keys As a result if you upgrade from anearlier version that did support RSA version 1 keys and you hadconfigured a RSA version 1 key for SSH then you will not be able tolog in through SSH following the upgrade
If you have a RSA version 1 key configured for SSH beforeupgrading to NX-OS Release 42(x) or higher follow these steps
1 Disable SSH
2 Create RSA version 2 DSA keys
3 Enable SSH
4 Delete any RSA version 1 keys on any remote SSH clients andreplace the version 1 keys with the new version 2 keys from theswitch
Proceed with the upgrade to NX-OS Release 42(x) or higher
If you upgrade before disabling SSH and creating RSA version 2 keysfollow these steps
1 Open a Telnet session and log in through the console
2 Issue the no feature ssh command to disable SSH
3 Issue the ssh key rsa 1024 command to create RSA version 2 keys
4 Issue the feature ssh command to enable SSH
Applying Zone Configurations to VSAN 1In the setup script you can configure system default values for thedefault-zone to be permit or deny and you can configure defaultvalues for the zone distribution method and for the zone mode
These default settings are applied when a new VSAN is createdHowever the settings will not take effect on VSAN 1 because it existsprior to running the setup script Therefore when you need thosesettings for VSAN 1 you must explicitly issue the followingcommands
zone default-zone permit vsan 1 zoneset distribute full vsan 1 zone mode enhanced vsan 1
28 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
InterVSAN RoutingWhen using InterVSAN Routing (IVR) it is recommended to enableCisco Fabric Services (CFS) on all IVR-enabled switches Failure to doso may cause mismatched active zone sets if an error occurs duringzone set activation
RSPAN Traffic Not Supported on CTS Ports on 8-Gbps Switching ModulesAn inter-switch link (ISL) that is enabled for Cisco TrustSec (CTS)encryption must be brought up in non-CTS mode to support remoteSPAN (RSPAN) traffic on the following modules
DS-X9248-96K9 Cisco MDS 9000 48-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9224-96K9 Cisco MDS 9000 24-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9248-48K9 Cisco MDS 9000 444-Port Host-Optimized8-Gbps Fibre Channel Switching Module
If the ISL link is brought up with CTS enabled random packets dropsof both RSPAN traffic and normal traffic will occur on the receiverport switch
IO Accelerator Feature LimitationsIOA does not support the following NX-OS features
IVR flows
Devices with NPV and NPIV enabled
F port trunking
bull F port channeling
Support for FCIP Compression ModesIn Cisco NX-OS Release 42(1b) and higher FCIP compression mode 1and compression mode 3 are not supported on the Cisco MSM-184module and on the SSN-16 module
29
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Saving Copies of the Running Kickstart and System ImagesAfter you upgrade to MDS NX-OS Release 42(1b) or higher you arenot allowed to delete rename move or overwrite the kickstart andsystem images that are in the current system bootvar settings on anactive or standby MDS Supervisor-2 module on any Cisco MDS 9500Series switch This restriction does not apply to the integratedsupervisor module on the MDS 9200 and MDS 9100 series switches
Configuring Buffer Credits on a Generation 2 or Generation 3 ModuleWhen you configure port mode to auto or E on a Generation 2module one of the ports will not come up for the followingconfiguration
Port Mode auto or E for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E on a Generation 3module one or two of the ports will not come up for the followingconfiguration
Port Mode auto or E for the first half of the ports the second halfof the ports or for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E for all ports in the globalbuffer pool you need to reconfigure buffer credits on one or more ofthe ports The total number of buffer credits configured for all theports in the global buffer pool should be reduced by 64
Storage services module power budgetThe MDS 9509 does not have the power budget to run seven SSMcards EMC recommends a maximum of four SSMs in one 9509Customers wishing to use more than four SSMs in one chassis shouldrefer to the Cisco MDS 9000 documentation on the Ciscocom websiteto validate that there is enough power available for their desiredconfiguration
30 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Note Upgrading to the 3000 watt power supplies will alleviate thiscondition
iSCSI proxy initiator in Celerra HighRoad environmentsEMC supports the iSCSI proxy initiator feature in Celerrareg
HighRoadreg environments In proxy initiator mode one Fibre Channelinitiator is used for all iSCSI clients who access the switch via thesame iSCSI interface (iscsi33 for example)
The initiators will use the PWWN assigned to the iSCSI interface TheiSCSI interface to which an iSCSI client will logon to is configured inthe client and must be permitted by the virtual target configured forthat initiator
The current session environment supported on the MDS is
300 sessions per port 1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no InitialR2T=yes
Refer to the specific initiator support documentation on how to setthe parameters The implementation will not perform properly ifthese bits are not set
Refer to the MDS documentation for more information regarding theconfiguration of the iSCSI proxy initiator at the following Ciscowebsite
httpwwwciscocomenUSproducts
HPUX N_port IDThe N_port ID port value of 255 (0xFF) has special meaning forHP-UX A N_port ID (FC_ID) can not be returned from a switch thatcontains this value for the N_port ID (FC_ID) port value for a HP-UXinitiator or HP-UX target port Port ID value of 255 (0xFF) cannot be
31
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
configured for HP-UX initiator port and HP-UX target ports whenconfiguring MDS FC_IDs The port_ID value is the third byte of theFC_ID
Interoperability limitationsRefer to the EMC Support Matrix (ESM) and the EMC Networked Storage Topology Guide for modes of operation and caveats
NASBThe NASB feature requires that the backup application load the tapedrive with a compatible tape cartridge prior to configuring NASB inthe backup VSAN
Reserved VSAN Range and Isolated VSAN Range GuidelinesOn an NPV switch with a trunking configuration on any interface or ona regular switch where the feature fport_channel_trunk command hasbeen issued to enable the F PortChannel feature follow theseconfiguration guidelines for reserved VSANs and the isolated VSAN
bull If trunk mode is on for any of the interfaces or NP PortChannelis up the reserved VSANs are 3040 to 4078 and they are notavailable for user configuration
bull The Exchange Virtual Fabric Protocol (EVFP) isolated VSAN is4079 and it is not available for user configuration
bull VSAN 4079 will be impacted by an upgrade to NX-OS Release42(3) depending on whether or not VSAN 4079 was createdprior to the upgrade See theldquoUpgrading Effect on VSAN 4079rdquoon page 17
The following VSAN IDs are assigned in the Fibre Channel Framingand Signaling (FC-FS) interface standard
VF_ID Value Value Description
00h Do not use as a Virtual FabricIdentifier
001h EFFh Available as a Virtual FabricIdentifier
F00h FEEh Reserved
32 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Symmetrix VMax limitationsAt the time of this writing the following features are not supportedfor use with the Symmetrix VMax
FCIP Write Acceleration
The NX-OS IOA functionality is only supported with the Q2 SREnginuity release 5874229182 or higher
For the most up to date status please refer to the current revision ofthese Release Notes on httpPowerlinkemccom and the EMCSupport Matrix available through E-Lab Interoperability Navigator (ELN) athttpelabnavigatorEMCcom
Storage Applications on the MSM-184The MDS 9000 184-Port Multiservice Module (MSM-184) does notsupport multiple concurrent storage applications Only oneapplication can run on the MSM-184 at a time
Downgrading with fport-channel-trunk enabledIf you are running MDS NX-OS Release 42(x) or higher with thefport-channel-trunk feature enabled and you downgrade to anyNX-OS 41(1x) release the installer performs a nondisruptivedowngrade even though the fport-channel-trunk feature is notsupported in NX-OS 41(1x) releases
As a result the switch is in an inconsistent state and the ports maynot function properly
FEFh Control VF-ID (see FibreChannel Link Services (FC-LS)and Fibre Channel SwitchFabric Generation 4 (FC-SW-4)standards)
FF0h FFEh Vendor specific
FFFh Do not use as a Virtual FabricIdentifier
FEFh = 4079
33
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
If you are in this state a workaround is to reboot the switch followingthe upgrade
LDAP AuthenticationThere is currently a limitation in the LDAP server configuration CLIthat prevents the use of an OU with spaces in the name Normallythese OU names could be surrounded by quotation marks howeverquotation marks are not supported by the ldap-server command
MDS-9148 limitationsThe Cisco MDS 9148 Multilayer Fabric Switch does not support thefollowing NX-OS features
Medium and Long range 4GB Agilent
IVR
Remote Span
Translative loop support
FCC - no generation quench reaction only
FC-Redirect
In addition the following features have these limits
VSANS - 31 maximum
SPAN - 1 session maximum
Technical notesThe following sections provide further information on technicalnotes
EMC Email Home for Cisco MDS switchesInstallation and Trouble shooting instructions can be found in thedocumentation located at the EMC Customer Service Internalwebsite
httpwwwcsisusemccomcsweb2esnesnhomehtmConnectrix20MDS20900020Family
34 EMC Connectrix MDS 9000 NX-OS Release Notes
Technical notes
Customers requiring installation of this solution should contact theirEMC Customer Engineer to assist with the installation and providethe documentation
Supported iSCSI sessionsThe current iSCSI session environment supported on the MDS is
300 sessions per port
1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no
InitialR2T=yes
Upgrading Cisco SAN-OSThere are several methods available for upgrading SAN-OS SoftwareEMC personnel are strongly recommended that all upgrades be doneby the Automated One-Step Upgrade using the install all
command EMC personnel should refer to the Connectrix MDS 9000Family Software Image Upgrade Instructions for a complete list ofprerequisites and instructions for performing the upgrade Thisdocument along with tftp software is available on the GlobalServices website at httpwwwcsisusEMCcom under ApplicationDownload Area ESN Product Information Connectrix MDS 9000Family
The Software Upgrade Wizard is an option for upgrades While theinstall all is the preferred method the Software Install Wizard canalso be used
Supported configuration parametersFor the most up-to-date information refer to the EMC Support Matrixavailable through E-Lab Interoperability Navigator athttpelabnavigatoremccom for the latest information onsupported configurations
35
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
Supported zoning parametersRefer to the EMC Networked Storage Topology Guide for the mostup-to-date information on supported zoning parameters
At the time these notes were published the following parameterswere supported
20 VSANs 5 Hops 2000 Unique members per physical infrastructure 1000 Zonesets per physical infrastructure 2000 Zones per physical infrastructure 1 FCIP tunnel
Supported IVR parameters IVR zone members 1000 IVR zones 1000 IVR zone sets 32 VSANS 20 IVR enabled switches 64
An RPQ can be submitted for any configurations that exceed thislimit
Managing zone changes in multiswitch fabricsZoning changes may be made through Fabric Manager or CLI Whenaccessing Fabric Manager or CLI the user does so from the point ofview of one switch That is Fabric Manager and CLI are accessed byentering the IP address of one switch in the fabric
When zoning changes are made the applicable VSAN and zone setdata is propagated to the rest of the switches in the fabric via the ISLs
When zoning changes are made to a VSAN the zone set data ispropagated to the rest of the switches in the fabric via the ISLs Bydefault only the active zone set information is relayed to all switchesin the VSAN If the user accesses the Fabric Manager and CLI fromanother switch in the fabric the new VSAN and zone set informationwill not be viewable To view the active and inactive zone set on theother switches in the fabric the user must log in to the CLI and issuea command from the EXEC prompt
36 EMC Connectrix MDS 9000 NX-OS Release Notes
Documentation
Example The following is an example of copying VSAN 1 through 20 zoningdata
CiscoMDS_name zone copy active full vsan 1-20
CiscoMDS_name conf t
Enter configuration commands one per line End with CNTL Z
CiscoMDS_name(config) zoneset distribute full vsan 1-20
CiscoMDS_name(config)
Note This command needs to be issued on all switches in the fabric one timeonly
This is a nondisruptive command After issuing the commands theuser will now see the active and inactive zone sets for the specifiedVSANs on any switch that is chosen from which to manage the fabric
After a zoning change is made save the running configuration to thestartup configuration
DocumentationSend documentation comments to mdsfeedback-doccom
Product DocumentationAs of NX-OS Release 42(1a) software configuration information isavailable in new feature-specific configuration guides for thefollowing information
System management
Interfaces
Fabric
Quality of service
Security
IP services
High availability and redundancy
37
Software media organization and files
EMC Connectrix MDS 9000 NX-OS Release Notes
The information in these new guides previously existed in the CiscoMDS 9000 Family CLI Configuration Guide That configuration guideremains available on Ciscocom and should be used for all softwarereleases prior to NX-OS Release 42(1a) Configuration guidesaddress the features introduced in or available in a particular releaseSelect and view the configuration guide that pertains to the softwareinstalled in your switch
In addition Fabric Manager information has been removed from theMDS NX-OS Release Notes (this document) and placed intostandalone Fabric Manager Release Notes that support both CiscoMDS 9000 Family switches and Cisco Nexus 5000 Series switchesThe Cisco Fabric Manager Release Notes are available onhttpPowerlinkemccom and from the following website
httpwwwciscocomenUSpartnerproductsps10495prod_release_notes_listhtml
Technical supportThese release notes complement a Cisco documentation set EachCisco document refers to where to get help However for any itemssupplied by EMC see ldquoTroubleshooting and getting helprdquo onpage 38
Software media organization and filesFor information on related software environment and systemrequirements refer to the EMC Support Matrix on EMC Powerlink at
httpPowerlinkEMCcom
InstallationFor hardware installation information refer to the Cisco MDS HWInstallation Guides available at Ciscocom
For EMC-specific installation information refer to ldquoEnvironment andsystem requirementsrdquo on page 5 in this document
38 EMC Connectrix MDS 9000 NX-OS Release Notes
Troubleshooting and getting help
Troubleshooting and getting helpEMC support product and licensing information can be obtained asfollows
Product information mdash For documentation release notes softwareupdates or for information about EMC products licensing andservice go to the EMC Powerlink website (registration required) at
httpPowerlinkEMCcom
Technical support mdash For technical support go to EMC CustomerService on Powerlink To open a service request through Powerlinkyou must have a valid support agreement Please contact your EMCsales representative for details about obtaining a valid supportagreement or to answer any questions about your account
Copyright copy 2011 EMC Corporation All rights reserved
EMC believes the information in this publication is accurate as of its publication date The information issubject to change without notice
THE INFORMATION IN THIS PUBLICATION IS PROVIDED ldquoAS ISrdquo EMC CORPORATION MAKES NOREPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION INTHIS PUBLICATION AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OFMERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Use copying and distribution of any EMC software described in this publication requires an applicablesoftware license
For the most up-to-date regulatory document for your product line go to the Technical Documentation andAdvisories section on EMC Powerlink
For the most up-to-date listing of EMC product names see EMC Corporation Trademarks on EMCcom
All other trademarks used herein are the property of their respective owners
22 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Best practicesLog messages are not saved across system reboots or power outagesTherefore EMC recommends that customers configure a SyslogServer in order to redirect and capture all log messages on a remoteserver For more information please refer to the Cisco MDS 9000Family Configuration Guide available at
httpwwwciscocomenUSproductsps5989products_support_series_homehtml
Maximum ports per chassisTable 11 shows the maximum ports per chassis
a V2 indicates a 9506 or 9509 with Generation-2 Supervisors The presence of anygeneration one module in a switch will limit the maximum port count to 252This includes the 16-port 32-port 14+2 IPS4 and IPS8 cards
Known problems and limitationsFor a list of problems with this release please refer to the CiscoRelease notes located at
httpwwwciscocomenUSproductsps5989prod_release_notes_listhtml
Limitations and restrictionsThe following limitations and restrictions apply to all switches in theCisco MDS 9000 Family unless a limitation for a specific switch isstated
ldquoStorage Media Encryption (SME) limitationsrdquo on page 24
Table 11 Maximum ports per chassis
Chassis Maximum number of ports
MDS 9506-V2 192a
MDS 9509-V2 336
MDS 9513 528
23
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
ldquoSME configuration limitsrdquo on page 24
ldquoDeleting Cisco SME interfacesrdquo on page 25
ldquoCisco MDS 9124 and 9134 Multilayer fabric switchesrdquo on page 25
ldquoN-Port virtualization configuration limitsrdquo on page 25
ldquoMaximum number of zones supported in Interop Mode 4rdquo onpage 25
ldquoIPv6rdquo on page 26
ldquoIP-ACL supportrdquo on page 26
ldquoUser Rolesrdquo on page 26
ldquoUsing a RSA Version 1 Key for SSH Following an Upgraderdquo onpage 27
ldquoApplying Zone Configurations to VSAN 1rdquo on page 27
ldquoInterVSAN Routingrdquo on page 28
ldquoRSPAN Traffic Not Supported on CTS Ports on 8-GbpsSwitching Modulesrdquo on page 28
ldquoIO Accelerator Feature Limitationsrdquo on page 28
ldquoSupport for FCIP Compression Modesrdquo on page 28
ldquoSaving Copies of the Running Kickstart and System Imagesrdquo onpage 29
ldquoConfiguring Buffer Credits on a Generation 2 or Generation 3Modulerdquo on page 29
ldquoStorage services module power budgetrdquo on page 29
ldquoiSCSI proxy initiator in Celerra HighRoad environmentsrdquo onpage 30
ldquoHPUX N_port IDrdquo on page 30
ldquoInteroperability limitationsrdquo on page 31
ldquoNASBrdquo on page 31
ldquoReserved VSAN Range and Isolated VSAN Range Guidelinesrdquoon page 31
ldquoSymmetrix VMax limitationsrdquo on page 32
ldquoStorage Applications on the MSM-184rdquo on page 32
ldquoDowngrading with fport-channel-trunk enabledrdquo on page 32
ldquoLDAP Authenticationrdquo on page 33
24 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
ldquoMDS-9148 limitationsrdquo on page 33
Storage Media Encryption (SME) limitationsAn SME node can only belong to one cluster Adding the node tomore than one cluster will cause problems
Currently there is no prevention or warning in place when an attemptis made to add a node to multiple clusters
SME configuration limitsTable 12 lists the SME configuration limits for this release
Table 12 SME configuration limits
Configuration Limits
Number of switches in the fabric 10
Number of clusters per switch 1
Switches in a cluster 4
Fabrics in a cluster 2
Modules in a switch 11
Cisco MSM-184 modules in a cluster 32
Initiator-Target-LUNs (ITLs) 1024
LUNs behind a target 32
Host and target ports in a cluster 128
Number of hosts per target 128
Tape backup groups per cluster 2
Volume groups in a tape backup group 4
Cisco Key Management Center ( of keys) 32K
Targets per switch that can be FC-redirected 32
25
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Deleting Cisco SME interfacesA Cisco SME interface can be deleted from the cluster only after theinterface is administratively shut-down and all related tasksassociated with the interface shut-down are complete
Cisco MDS 9124 and 9134 Multilayer fabric switchesThe Cisco MDS 9124 and 9134 Multilayer fabric switches do notsupport the following Cisco MDS SAN-OS features
IVR Remote Span Translative loop support FCCmdash no generation quench reaction only
In addition the following features have these limits
VSANs mdash 16 maximum SPAN mdash 1 session maximum
N-Port virtualization configuration limitsThe NPV features have maximum configuration limits Table 13shows the verified and maximum limits for the NPV switchesrunning NX-OS Release 5x
Maximum number of zones supported in Interop Mode 4In interop mode 4 the maximum number of zones that is supportedin an active zone set is 2047 due to limitations in the connectedvendor switch When IVR is used in interop mode 4 the maximumnumber of zones supported including IVR zones in the active zoneset is 2047 The limit for the maximum number of IVR zones perVSAN is 250 zones (two members per zone)
Table 13 NPV features limitations
Feature Verified limits Maximum limits
FLOGIs or F Disc per NPV port group 114 114
NPV switches per NPV core switch 105 105
FLOGIs per line card on NPV core switch 400 400
26 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
IPv6The management port on Cisco MDS switches supports oneuser-configured IPv6 address but does not supportauto-configuration of an IPv6 address
IP-ACL supportDo not apply IP-ACLs to only one member of a PortChannel groupApply IP-ACLs to the entire channel group
If IP-ACLs are already configured in a Gigabit Ethernet interface youcannot add this interface to a Ethernet PortChannel group
Refer to the Cisco MDS 9000 Family Configuration Guide
User RolesIn SAN-OS Release 33(x) and earlier when a user belongs to a rolewhich has a VSAN policy set to Deny and the role allows access to aspecific set of VSANs (for example 1 through 10) the user isrestricted from performing the configuration clear execute anddebug commands which had a VSAN parameter outside thisspecified set Beginning with NX-OS Release 41(1b) these users arestill prevented from performing configuration clear execute anddebug commands as before however they are allowed to performshow commands for all VSANs The ability to execute the showcommand addresses the following
In a network environment users often need to view informationin other VSANs even though they do not have permission tomodify configurations in those VSANs
This behavior makes Cisco MDS 9000 Series switches consistentwith other Cisco products such as Cisco Nexus 7000 Seriesswitches that exhibit the same behavior for those roles (whenthey apply to the VLAN policy)
27
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Using a RSA Version 1 Key for SSH Following an UpgradeFor security reasons NX-OS Release 42(x) and higher does notsupport RSA version 1 keys As a result if you upgrade from anearlier version that did support RSA version 1 keys and you hadconfigured a RSA version 1 key for SSH then you will not be able tolog in through SSH following the upgrade
If you have a RSA version 1 key configured for SSH beforeupgrading to NX-OS Release 42(x) or higher follow these steps
1 Disable SSH
2 Create RSA version 2 DSA keys
3 Enable SSH
4 Delete any RSA version 1 keys on any remote SSH clients andreplace the version 1 keys with the new version 2 keys from theswitch
Proceed with the upgrade to NX-OS Release 42(x) or higher
If you upgrade before disabling SSH and creating RSA version 2 keysfollow these steps
1 Open a Telnet session and log in through the console
2 Issue the no feature ssh command to disable SSH
3 Issue the ssh key rsa 1024 command to create RSA version 2 keys
4 Issue the feature ssh command to enable SSH
Applying Zone Configurations to VSAN 1In the setup script you can configure system default values for thedefault-zone to be permit or deny and you can configure defaultvalues for the zone distribution method and for the zone mode
These default settings are applied when a new VSAN is createdHowever the settings will not take effect on VSAN 1 because it existsprior to running the setup script Therefore when you need thosesettings for VSAN 1 you must explicitly issue the followingcommands
zone default-zone permit vsan 1 zoneset distribute full vsan 1 zone mode enhanced vsan 1
28 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
InterVSAN RoutingWhen using InterVSAN Routing (IVR) it is recommended to enableCisco Fabric Services (CFS) on all IVR-enabled switches Failure to doso may cause mismatched active zone sets if an error occurs duringzone set activation
RSPAN Traffic Not Supported on CTS Ports on 8-Gbps Switching ModulesAn inter-switch link (ISL) that is enabled for Cisco TrustSec (CTS)encryption must be brought up in non-CTS mode to support remoteSPAN (RSPAN) traffic on the following modules
DS-X9248-96K9 Cisco MDS 9000 48-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9224-96K9 Cisco MDS 9000 24-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9248-48K9 Cisco MDS 9000 444-Port Host-Optimized8-Gbps Fibre Channel Switching Module
If the ISL link is brought up with CTS enabled random packets dropsof both RSPAN traffic and normal traffic will occur on the receiverport switch
IO Accelerator Feature LimitationsIOA does not support the following NX-OS features
IVR flows
Devices with NPV and NPIV enabled
F port trunking
bull F port channeling
Support for FCIP Compression ModesIn Cisco NX-OS Release 42(1b) and higher FCIP compression mode 1and compression mode 3 are not supported on the Cisco MSM-184module and on the SSN-16 module
29
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Saving Copies of the Running Kickstart and System ImagesAfter you upgrade to MDS NX-OS Release 42(1b) or higher you arenot allowed to delete rename move or overwrite the kickstart andsystem images that are in the current system bootvar settings on anactive or standby MDS Supervisor-2 module on any Cisco MDS 9500Series switch This restriction does not apply to the integratedsupervisor module on the MDS 9200 and MDS 9100 series switches
Configuring Buffer Credits on a Generation 2 or Generation 3 ModuleWhen you configure port mode to auto or E on a Generation 2module one of the ports will not come up for the followingconfiguration
Port Mode auto or E for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E on a Generation 3module one or two of the ports will not come up for the followingconfiguration
Port Mode auto or E for the first half of the ports the second halfof the ports or for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E for all ports in the globalbuffer pool you need to reconfigure buffer credits on one or more ofthe ports The total number of buffer credits configured for all theports in the global buffer pool should be reduced by 64
Storage services module power budgetThe MDS 9509 does not have the power budget to run seven SSMcards EMC recommends a maximum of four SSMs in one 9509Customers wishing to use more than four SSMs in one chassis shouldrefer to the Cisco MDS 9000 documentation on the Ciscocom websiteto validate that there is enough power available for their desiredconfiguration
30 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Note Upgrading to the 3000 watt power supplies will alleviate thiscondition
iSCSI proxy initiator in Celerra HighRoad environmentsEMC supports the iSCSI proxy initiator feature in Celerrareg
HighRoadreg environments In proxy initiator mode one Fibre Channelinitiator is used for all iSCSI clients who access the switch via thesame iSCSI interface (iscsi33 for example)
The initiators will use the PWWN assigned to the iSCSI interface TheiSCSI interface to which an iSCSI client will logon to is configured inthe client and must be permitted by the virtual target configured forthat initiator
The current session environment supported on the MDS is
300 sessions per port 1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no InitialR2T=yes
Refer to the specific initiator support documentation on how to setthe parameters The implementation will not perform properly ifthese bits are not set
Refer to the MDS documentation for more information regarding theconfiguration of the iSCSI proxy initiator at the following Ciscowebsite
httpwwwciscocomenUSproducts
HPUX N_port IDThe N_port ID port value of 255 (0xFF) has special meaning forHP-UX A N_port ID (FC_ID) can not be returned from a switch thatcontains this value for the N_port ID (FC_ID) port value for a HP-UXinitiator or HP-UX target port Port ID value of 255 (0xFF) cannot be
31
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
configured for HP-UX initiator port and HP-UX target ports whenconfiguring MDS FC_IDs The port_ID value is the third byte of theFC_ID
Interoperability limitationsRefer to the EMC Support Matrix (ESM) and the EMC Networked Storage Topology Guide for modes of operation and caveats
NASBThe NASB feature requires that the backup application load the tapedrive with a compatible tape cartridge prior to configuring NASB inthe backup VSAN
Reserved VSAN Range and Isolated VSAN Range GuidelinesOn an NPV switch with a trunking configuration on any interface or ona regular switch where the feature fport_channel_trunk command hasbeen issued to enable the F PortChannel feature follow theseconfiguration guidelines for reserved VSANs and the isolated VSAN
bull If trunk mode is on for any of the interfaces or NP PortChannelis up the reserved VSANs are 3040 to 4078 and they are notavailable for user configuration
bull The Exchange Virtual Fabric Protocol (EVFP) isolated VSAN is4079 and it is not available for user configuration
bull VSAN 4079 will be impacted by an upgrade to NX-OS Release42(3) depending on whether or not VSAN 4079 was createdprior to the upgrade See theldquoUpgrading Effect on VSAN 4079rdquoon page 17
The following VSAN IDs are assigned in the Fibre Channel Framingand Signaling (FC-FS) interface standard
VF_ID Value Value Description
00h Do not use as a Virtual FabricIdentifier
001h EFFh Available as a Virtual FabricIdentifier
F00h FEEh Reserved
32 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Symmetrix VMax limitationsAt the time of this writing the following features are not supportedfor use with the Symmetrix VMax
FCIP Write Acceleration
The NX-OS IOA functionality is only supported with the Q2 SREnginuity release 5874229182 or higher
For the most up to date status please refer to the current revision ofthese Release Notes on httpPowerlinkemccom and the EMCSupport Matrix available through E-Lab Interoperability Navigator (ELN) athttpelabnavigatorEMCcom
Storage Applications on the MSM-184The MDS 9000 184-Port Multiservice Module (MSM-184) does notsupport multiple concurrent storage applications Only oneapplication can run on the MSM-184 at a time
Downgrading with fport-channel-trunk enabledIf you are running MDS NX-OS Release 42(x) or higher with thefport-channel-trunk feature enabled and you downgrade to anyNX-OS 41(1x) release the installer performs a nondisruptivedowngrade even though the fport-channel-trunk feature is notsupported in NX-OS 41(1x) releases
As a result the switch is in an inconsistent state and the ports maynot function properly
FEFh Control VF-ID (see FibreChannel Link Services (FC-LS)and Fibre Channel SwitchFabric Generation 4 (FC-SW-4)standards)
FF0h FFEh Vendor specific
FFFh Do not use as a Virtual FabricIdentifier
FEFh = 4079
33
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
If you are in this state a workaround is to reboot the switch followingthe upgrade
LDAP AuthenticationThere is currently a limitation in the LDAP server configuration CLIthat prevents the use of an OU with spaces in the name Normallythese OU names could be surrounded by quotation marks howeverquotation marks are not supported by the ldap-server command
MDS-9148 limitationsThe Cisco MDS 9148 Multilayer Fabric Switch does not support thefollowing NX-OS features
Medium and Long range 4GB Agilent
IVR
Remote Span
Translative loop support
FCC - no generation quench reaction only
FC-Redirect
In addition the following features have these limits
VSANS - 31 maximum
SPAN - 1 session maximum
Technical notesThe following sections provide further information on technicalnotes
EMC Email Home for Cisco MDS switchesInstallation and Trouble shooting instructions can be found in thedocumentation located at the EMC Customer Service Internalwebsite
httpwwwcsisusemccomcsweb2esnesnhomehtmConnectrix20MDS20900020Family
34 EMC Connectrix MDS 9000 NX-OS Release Notes
Technical notes
Customers requiring installation of this solution should contact theirEMC Customer Engineer to assist with the installation and providethe documentation
Supported iSCSI sessionsThe current iSCSI session environment supported on the MDS is
300 sessions per port
1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no
InitialR2T=yes
Upgrading Cisco SAN-OSThere are several methods available for upgrading SAN-OS SoftwareEMC personnel are strongly recommended that all upgrades be doneby the Automated One-Step Upgrade using the install all
command EMC personnel should refer to the Connectrix MDS 9000Family Software Image Upgrade Instructions for a complete list ofprerequisites and instructions for performing the upgrade Thisdocument along with tftp software is available on the GlobalServices website at httpwwwcsisusEMCcom under ApplicationDownload Area ESN Product Information Connectrix MDS 9000Family
The Software Upgrade Wizard is an option for upgrades While theinstall all is the preferred method the Software Install Wizard canalso be used
Supported configuration parametersFor the most up-to-date information refer to the EMC Support Matrixavailable through E-Lab Interoperability Navigator athttpelabnavigatoremccom for the latest information onsupported configurations
35
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
Supported zoning parametersRefer to the EMC Networked Storage Topology Guide for the mostup-to-date information on supported zoning parameters
At the time these notes were published the following parameterswere supported
20 VSANs 5 Hops 2000 Unique members per physical infrastructure 1000 Zonesets per physical infrastructure 2000 Zones per physical infrastructure 1 FCIP tunnel
Supported IVR parameters IVR zone members 1000 IVR zones 1000 IVR zone sets 32 VSANS 20 IVR enabled switches 64
An RPQ can be submitted for any configurations that exceed thislimit
Managing zone changes in multiswitch fabricsZoning changes may be made through Fabric Manager or CLI Whenaccessing Fabric Manager or CLI the user does so from the point ofview of one switch That is Fabric Manager and CLI are accessed byentering the IP address of one switch in the fabric
When zoning changes are made the applicable VSAN and zone setdata is propagated to the rest of the switches in the fabric via the ISLs
When zoning changes are made to a VSAN the zone set data ispropagated to the rest of the switches in the fabric via the ISLs Bydefault only the active zone set information is relayed to all switchesin the VSAN If the user accesses the Fabric Manager and CLI fromanother switch in the fabric the new VSAN and zone set informationwill not be viewable To view the active and inactive zone set on theother switches in the fabric the user must log in to the CLI and issuea command from the EXEC prompt
36 EMC Connectrix MDS 9000 NX-OS Release Notes
Documentation
Example The following is an example of copying VSAN 1 through 20 zoningdata
CiscoMDS_name zone copy active full vsan 1-20
CiscoMDS_name conf t
Enter configuration commands one per line End with CNTL Z
CiscoMDS_name(config) zoneset distribute full vsan 1-20
CiscoMDS_name(config)
Note This command needs to be issued on all switches in the fabric one timeonly
This is a nondisruptive command After issuing the commands theuser will now see the active and inactive zone sets for the specifiedVSANs on any switch that is chosen from which to manage the fabric
After a zoning change is made save the running configuration to thestartup configuration
DocumentationSend documentation comments to mdsfeedback-doccom
Product DocumentationAs of NX-OS Release 42(1a) software configuration information isavailable in new feature-specific configuration guides for thefollowing information
System management
Interfaces
Fabric
Quality of service
Security
IP services
High availability and redundancy
37
Software media organization and files
EMC Connectrix MDS 9000 NX-OS Release Notes
The information in these new guides previously existed in the CiscoMDS 9000 Family CLI Configuration Guide That configuration guideremains available on Ciscocom and should be used for all softwarereleases prior to NX-OS Release 42(1a) Configuration guidesaddress the features introduced in or available in a particular releaseSelect and view the configuration guide that pertains to the softwareinstalled in your switch
In addition Fabric Manager information has been removed from theMDS NX-OS Release Notes (this document) and placed intostandalone Fabric Manager Release Notes that support both CiscoMDS 9000 Family switches and Cisco Nexus 5000 Series switchesThe Cisco Fabric Manager Release Notes are available onhttpPowerlinkemccom and from the following website
httpwwwciscocomenUSpartnerproductsps10495prod_release_notes_listhtml
Technical supportThese release notes complement a Cisco documentation set EachCisco document refers to where to get help However for any itemssupplied by EMC see ldquoTroubleshooting and getting helprdquo onpage 38
Software media organization and filesFor information on related software environment and systemrequirements refer to the EMC Support Matrix on EMC Powerlink at
httpPowerlinkEMCcom
InstallationFor hardware installation information refer to the Cisco MDS HWInstallation Guides available at Ciscocom
For EMC-specific installation information refer to ldquoEnvironment andsystem requirementsrdquo on page 5 in this document
38 EMC Connectrix MDS 9000 NX-OS Release Notes
Troubleshooting and getting help
Troubleshooting and getting helpEMC support product and licensing information can be obtained asfollows
Product information mdash For documentation release notes softwareupdates or for information about EMC products licensing andservice go to the EMC Powerlink website (registration required) at
httpPowerlinkEMCcom
Technical support mdash For technical support go to EMC CustomerService on Powerlink To open a service request through Powerlinkyou must have a valid support agreement Please contact your EMCsales representative for details about obtaining a valid supportagreement or to answer any questions about your account
Copyright copy 2011 EMC Corporation All rights reserved
EMC believes the information in this publication is accurate as of its publication date The information issubject to change without notice
THE INFORMATION IN THIS PUBLICATION IS PROVIDED ldquoAS ISrdquo EMC CORPORATION MAKES NOREPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION INTHIS PUBLICATION AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OFMERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Use copying and distribution of any EMC software described in this publication requires an applicablesoftware license
For the most up-to-date regulatory document for your product line go to the Technical Documentation andAdvisories section on EMC Powerlink
For the most up-to-date listing of EMC product names see EMC Corporation Trademarks on EMCcom
All other trademarks used herein are the property of their respective owners
23
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
ldquoSME configuration limitsrdquo on page 24
ldquoDeleting Cisco SME interfacesrdquo on page 25
ldquoCisco MDS 9124 and 9134 Multilayer fabric switchesrdquo on page 25
ldquoN-Port virtualization configuration limitsrdquo on page 25
ldquoMaximum number of zones supported in Interop Mode 4rdquo onpage 25
ldquoIPv6rdquo on page 26
ldquoIP-ACL supportrdquo on page 26
ldquoUser Rolesrdquo on page 26
ldquoUsing a RSA Version 1 Key for SSH Following an Upgraderdquo onpage 27
ldquoApplying Zone Configurations to VSAN 1rdquo on page 27
ldquoInterVSAN Routingrdquo on page 28
ldquoRSPAN Traffic Not Supported on CTS Ports on 8-GbpsSwitching Modulesrdquo on page 28
ldquoIO Accelerator Feature Limitationsrdquo on page 28
ldquoSupport for FCIP Compression Modesrdquo on page 28
ldquoSaving Copies of the Running Kickstart and System Imagesrdquo onpage 29
ldquoConfiguring Buffer Credits on a Generation 2 or Generation 3Modulerdquo on page 29
ldquoStorage services module power budgetrdquo on page 29
ldquoiSCSI proxy initiator in Celerra HighRoad environmentsrdquo onpage 30
ldquoHPUX N_port IDrdquo on page 30
ldquoInteroperability limitationsrdquo on page 31
ldquoNASBrdquo on page 31
ldquoReserved VSAN Range and Isolated VSAN Range Guidelinesrdquoon page 31
ldquoSymmetrix VMax limitationsrdquo on page 32
ldquoStorage Applications on the MSM-184rdquo on page 32
ldquoDowngrading with fport-channel-trunk enabledrdquo on page 32
ldquoLDAP Authenticationrdquo on page 33
24 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
ldquoMDS-9148 limitationsrdquo on page 33
Storage Media Encryption (SME) limitationsAn SME node can only belong to one cluster Adding the node tomore than one cluster will cause problems
Currently there is no prevention or warning in place when an attemptis made to add a node to multiple clusters
SME configuration limitsTable 12 lists the SME configuration limits for this release
Table 12 SME configuration limits
Configuration Limits
Number of switches in the fabric 10
Number of clusters per switch 1
Switches in a cluster 4
Fabrics in a cluster 2
Modules in a switch 11
Cisco MSM-184 modules in a cluster 32
Initiator-Target-LUNs (ITLs) 1024
LUNs behind a target 32
Host and target ports in a cluster 128
Number of hosts per target 128
Tape backup groups per cluster 2
Volume groups in a tape backup group 4
Cisco Key Management Center ( of keys) 32K
Targets per switch that can be FC-redirected 32
25
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Deleting Cisco SME interfacesA Cisco SME interface can be deleted from the cluster only after theinterface is administratively shut-down and all related tasksassociated with the interface shut-down are complete
Cisco MDS 9124 and 9134 Multilayer fabric switchesThe Cisco MDS 9124 and 9134 Multilayer fabric switches do notsupport the following Cisco MDS SAN-OS features
IVR Remote Span Translative loop support FCCmdash no generation quench reaction only
In addition the following features have these limits
VSANs mdash 16 maximum SPAN mdash 1 session maximum
N-Port virtualization configuration limitsThe NPV features have maximum configuration limits Table 13shows the verified and maximum limits for the NPV switchesrunning NX-OS Release 5x
Maximum number of zones supported in Interop Mode 4In interop mode 4 the maximum number of zones that is supportedin an active zone set is 2047 due to limitations in the connectedvendor switch When IVR is used in interop mode 4 the maximumnumber of zones supported including IVR zones in the active zoneset is 2047 The limit for the maximum number of IVR zones perVSAN is 250 zones (two members per zone)
Table 13 NPV features limitations
Feature Verified limits Maximum limits
FLOGIs or F Disc per NPV port group 114 114
NPV switches per NPV core switch 105 105
FLOGIs per line card on NPV core switch 400 400
26 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
IPv6The management port on Cisco MDS switches supports oneuser-configured IPv6 address but does not supportauto-configuration of an IPv6 address
IP-ACL supportDo not apply IP-ACLs to only one member of a PortChannel groupApply IP-ACLs to the entire channel group
If IP-ACLs are already configured in a Gigabit Ethernet interface youcannot add this interface to a Ethernet PortChannel group
Refer to the Cisco MDS 9000 Family Configuration Guide
User RolesIn SAN-OS Release 33(x) and earlier when a user belongs to a rolewhich has a VSAN policy set to Deny and the role allows access to aspecific set of VSANs (for example 1 through 10) the user isrestricted from performing the configuration clear execute anddebug commands which had a VSAN parameter outside thisspecified set Beginning with NX-OS Release 41(1b) these users arestill prevented from performing configuration clear execute anddebug commands as before however they are allowed to performshow commands for all VSANs The ability to execute the showcommand addresses the following
In a network environment users often need to view informationin other VSANs even though they do not have permission tomodify configurations in those VSANs
This behavior makes Cisco MDS 9000 Series switches consistentwith other Cisco products such as Cisco Nexus 7000 Seriesswitches that exhibit the same behavior for those roles (whenthey apply to the VLAN policy)
27
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Using a RSA Version 1 Key for SSH Following an UpgradeFor security reasons NX-OS Release 42(x) and higher does notsupport RSA version 1 keys As a result if you upgrade from anearlier version that did support RSA version 1 keys and you hadconfigured a RSA version 1 key for SSH then you will not be able tolog in through SSH following the upgrade
If you have a RSA version 1 key configured for SSH beforeupgrading to NX-OS Release 42(x) or higher follow these steps
1 Disable SSH
2 Create RSA version 2 DSA keys
3 Enable SSH
4 Delete any RSA version 1 keys on any remote SSH clients andreplace the version 1 keys with the new version 2 keys from theswitch
Proceed with the upgrade to NX-OS Release 42(x) or higher
If you upgrade before disabling SSH and creating RSA version 2 keysfollow these steps
1 Open a Telnet session and log in through the console
2 Issue the no feature ssh command to disable SSH
3 Issue the ssh key rsa 1024 command to create RSA version 2 keys
4 Issue the feature ssh command to enable SSH
Applying Zone Configurations to VSAN 1In the setup script you can configure system default values for thedefault-zone to be permit or deny and you can configure defaultvalues for the zone distribution method and for the zone mode
These default settings are applied when a new VSAN is createdHowever the settings will not take effect on VSAN 1 because it existsprior to running the setup script Therefore when you need thosesettings for VSAN 1 you must explicitly issue the followingcommands
zone default-zone permit vsan 1 zoneset distribute full vsan 1 zone mode enhanced vsan 1
28 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
InterVSAN RoutingWhen using InterVSAN Routing (IVR) it is recommended to enableCisco Fabric Services (CFS) on all IVR-enabled switches Failure to doso may cause mismatched active zone sets if an error occurs duringzone set activation
RSPAN Traffic Not Supported on CTS Ports on 8-Gbps Switching ModulesAn inter-switch link (ISL) that is enabled for Cisco TrustSec (CTS)encryption must be brought up in non-CTS mode to support remoteSPAN (RSPAN) traffic on the following modules
DS-X9248-96K9 Cisco MDS 9000 48-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9224-96K9 Cisco MDS 9000 24-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9248-48K9 Cisco MDS 9000 444-Port Host-Optimized8-Gbps Fibre Channel Switching Module
If the ISL link is brought up with CTS enabled random packets dropsof both RSPAN traffic and normal traffic will occur on the receiverport switch
IO Accelerator Feature LimitationsIOA does not support the following NX-OS features
IVR flows
Devices with NPV and NPIV enabled
F port trunking
bull F port channeling
Support for FCIP Compression ModesIn Cisco NX-OS Release 42(1b) and higher FCIP compression mode 1and compression mode 3 are not supported on the Cisco MSM-184module and on the SSN-16 module
29
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Saving Copies of the Running Kickstart and System ImagesAfter you upgrade to MDS NX-OS Release 42(1b) or higher you arenot allowed to delete rename move or overwrite the kickstart andsystem images that are in the current system bootvar settings on anactive or standby MDS Supervisor-2 module on any Cisco MDS 9500Series switch This restriction does not apply to the integratedsupervisor module on the MDS 9200 and MDS 9100 series switches
Configuring Buffer Credits on a Generation 2 or Generation 3 ModuleWhen you configure port mode to auto or E on a Generation 2module one of the ports will not come up for the followingconfiguration
Port Mode auto or E for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E on a Generation 3module one or two of the ports will not come up for the followingconfiguration
Port Mode auto or E for the first half of the ports the second halfof the ports or for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E for all ports in the globalbuffer pool you need to reconfigure buffer credits on one or more ofthe ports The total number of buffer credits configured for all theports in the global buffer pool should be reduced by 64
Storage services module power budgetThe MDS 9509 does not have the power budget to run seven SSMcards EMC recommends a maximum of four SSMs in one 9509Customers wishing to use more than four SSMs in one chassis shouldrefer to the Cisco MDS 9000 documentation on the Ciscocom websiteto validate that there is enough power available for their desiredconfiguration
30 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Note Upgrading to the 3000 watt power supplies will alleviate thiscondition
iSCSI proxy initiator in Celerra HighRoad environmentsEMC supports the iSCSI proxy initiator feature in Celerrareg
HighRoadreg environments In proxy initiator mode one Fibre Channelinitiator is used for all iSCSI clients who access the switch via thesame iSCSI interface (iscsi33 for example)
The initiators will use the PWWN assigned to the iSCSI interface TheiSCSI interface to which an iSCSI client will logon to is configured inthe client and must be permitted by the virtual target configured forthat initiator
The current session environment supported on the MDS is
300 sessions per port 1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no InitialR2T=yes
Refer to the specific initiator support documentation on how to setthe parameters The implementation will not perform properly ifthese bits are not set
Refer to the MDS documentation for more information regarding theconfiguration of the iSCSI proxy initiator at the following Ciscowebsite
httpwwwciscocomenUSproducts
HPUX N_port IDThe N_port ID port value of 255 (0xFF) has special meaning forHP-UX A N_port ID (FC_ID) can not be returned from a switch thatcontains this value for the N_port ID (FC_ID) port value for a HP-UXinitiator or HP-UX target port Port ID value of 255 (0xFF) cannot be
31
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
configured for HP-UX initiator port and HP-UX target ports whenconfiguring MDS FC_IDs The port_ID value is the third byte of theFC_ID
Interoperability limitationsRefer to the EMC Support Matrix (ESM) and the EMC Networked Storage Topology Guide for modes of operation and caveats
NASBThe NASB feature requires that the backup application load the tapedrive with a compatible tape cartridge prior to configuring NASB inthe backup VSAN
Reserved VSAN Range and Isolated VSAN Range GuidelinesOn an NPV switch with a trunking configuration on any interface or ona regular switch where the feature fport_channel_trunk command hasbeen issued to enable the F PortChannel feature follow theseconfiguration guidelines for reserved VSANs and the isolated VSAN
bull If trunk mode is on for any of the interfaces or NP PortChannelis up the reserved VSANs are 3040 to 4078 and they are notavailable for user configuration
bull The Exchange Virtual Fabric Protocol (EVFP) isolated VSAN is4079 and it is not available for user configuration
bull VSAN 4079 will be impacted by an upgrade to NX-OS Release42(3) depending on whether or not VSAN 4079 was createdprior to the upgrade See theldquoUpgrading Effect on VSAN 4079rdquoon page 17
The following VSAN IDs are assigned in the Fibre Channel Framingand Signaling (FC-FS) interface standard
VF_ID Value Value Description
00h Do not use as a Virtual FabricIdentifier
001h EFFh Available as a Virtual FabricIdentifier
F00h FEEh Reserved
32 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Symmetrix VMax limitationsAt the time of this writing the following features are not supportedfor use with the Symmetrix VMax
FCIP Write Acceleration
The NX-OS IOA functionality is only supported with the Q2 SREnginuity release 5874229182 or higher
For the most up to date status please refer to the current revision ofthese Release Notes on httpPowerlinkemccom and the EMCSupport Matrix available through E-Lab Interoperability Navigator (ELN) athttpelabnavigatorEMCcom
Storage Applications on the MSM-184The MDS 9000 184-Port Multiservice Module (MSM-184) does notsupport multiple concurrent storage applications Only oneapplication can run on the MSM-184 at a time
Downgrading with fport-channel-trunk enabledIf you are running MDS NX-OS Release 42(x) or higher with thefport-channel-trunk feature enabled and you downgrade to anyNX-OS 41(1x) release the installer performs a nondisruptivedowngrade even though the fport-channel-trunk feature is notsupported in NX-OS 41(1x) releases
As a result the switch is in an inconsistent state and the ports maynot function properly
FEFh Control VF-ID (see FibreChannel Link Services (FC-LS)and Fibre Channel SwitchFabric Generation 4 (FC-SW-4)standards)
FF0h FFEh Vendor specific
FFFh Do not use as a Virtual FabricIdentifier
FEFh = 4079
33
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
If you are in this state a workaround is to reboot the switch followingthe upgrade
LDAP AuthenticationThere is currently a limitation in the LDAP server configuration CLIthat prevents the use of an OU with spaces in the name Normallythese OU names could be surrounded by quotation marks howeverquotation marks are not supported by the ldap-server command
MDS-9148 limitationsThe Cisco MDS 9148 Multilayer Fabric Switch does not support thefollowing NX-OS features
Medium and Long range 4GB Agilent
IVR
Remote Span
Translative loop support
FCC - no generation quench reaction only
FC-Redirect
In addition the following features have these limits
VSANS - 31 maximum
SPAN - 1 session maximum
Technical notesThe following sections provide further information on technicalnotes
EMC Email Home for Cisco MDS switchesInstallation and Trouble shooting instructions can be found in thedocumentation located at the EMC Customer Service Internalwebsite
httpwwwcsisusemccomcsweb2esnesnhomehtmConnectrix20MDS20900020Family
34 EMC Connectrix MDS 9000 NX-OS Release Notes
Technical notes
Customers requiring installation of this solution should contact theirEMC Customer Engineer to assist with the installation and providethe documentation
Supported iSCSI sessionsThe current iSCSI session environment supported on the MDS is
300 sessions per port
1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no
InitialR2T=yes
Upgrading Cisco SAN-OSThere are several methods available for upgrading SAN-OS SoftwareEMC personnel are strongly recommended that all upgrades be doneby the Automated One-Step Upgrade using the install all
command EMC personnel should refer to the Connectrix MDS 9000Family Software Image Upgrade Instructions for a complete list ofprerequisites and instructions for performing the upgrade Thisdocument along with tftp software is available on the GlobalServices website at httpwwwcsisusEMCcom under ApplicationDownload Area ESN Product Information Connectrix MDS 9000Family
The Software Upgrade Wizard is an option for upgrades While theinstall all is the preferred method the Software Install Wizard canalso be used
Supported configuration parametersFor the most up-to-date information refer to the EMC Support Matrixavailable through E-Lab Interoperability Navigator athttpelabnavigatoremccom for the latest information onsupported configurations
35
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
Supported zoning parametersRefer to the EMC Networked Storage Topology Guide for the mostup-to-date information on supported zoning parameters
At the time these notes were published the following parameterswere supported
20 VSANs 5 Hops 2000 Unique members per physical infrastructure 1000 Zonesets per physical infrastructure 2000 Zones per physical infrastructure 1 FCIP tunnel
Supported IVR parameters IVR zone members 1000 IVR zones 1000 IVR zone sets 32 VSANS 20 IVR enabled switches 64
An RPQ can be submitted for any configurations that exceed thislimit
Managing zone changes in multiswitch fabricsZoning changes may be made through Fabric Manager or CLI Whenaccessing Fabric Manager or CLI the user does so from the point ofview of one switch That is Fabric Manager and CLI are accessed byentering the IP address of one switch in the fabric
When zoning changes are made the applicable VSAN and zone setdata is propagated to the rest of the switches in the fabric via the ISLs
When zoning changes are made to a VSAN the zone set data ispropagated to the rest of the switches in the fabric via the ISLs Bydefault only the active zone set information is relayed to all switchesin the VSAN If the user accesses the Fabric Manager and CLI fromanother switch in the fabric the new VSAN and zone set informationwill not be viewable To view the active and inactive zone set on theother switches in the fabric the user must log in to the CLI and issuea command from the EXEC prompt
36 EMC Connectrix MDS 9000 NX-OS Release Notes
Documentation
Example The following is an example of copying VSAN 1 through 20 zoningdata
CiscoMDS_name zone copy active full vsan 1-20
CiscoMDS_name conf t
Enter configuration commands one per line End with CNTL Z
CiscoMDS_name(config) zoneset distribute full vsan 1-20
CiscoMDS_name(config)
Note This command needs to be issued on all switches in the fabric one timeonly
This is a nondisruptive command After issuing the commands theuser will now see the active and inactive zone sets for the specifiedVSANs on any switch that is chosen from which to manage the fabric
After a zoning change is made save the running configuration to thestartup configuration
DocumentationSend documentation comments to mdsfeedback-doccom
Product DocumentationAs of NX-OS Release 42(1a) software configuration information isavailable in new feature-specific configuration guides for thefollowing information
System management
Interfaces
Fabric
Quality of service
Security
IP services
High availability and redundancy
37
Software media organization and files
EMC Connectrix MDS 9000 NX-OS Release Notes
The information in these new guides previously existed in the CiscoMDS 9000 Family CLI Configuration Guide That configuration guideremains available on Ciscocom and should be used for all softwarereleases prior to NX-OS Release 42(1a) Configuration guidesaddress the features introduced in or available in a particular releaseSelect and view the configuration guide that pertains to the softwareinstalled in your switch
In addition Fabric Manager information has been removed from theMDS NX-OS Release Notes (this document) and placed intostandalone Fabric Manager Release Notes that support both CiscoMDS 9000 Family switches and Cisco Nexus 5000 Series switchesThe Cisco Fabric Manager Release Notes are available onhttpPowerlinkemccom and from the following website
httpwwwciscocomenUSpartnerproductsps10495prod_release_notes_listhtml
Technical supportThese release notes complement a Cisco documentation set EachCisco document refers to where to get help However for any itemssupplied by EMC see ldquoTroubleshooting and getting helprdquo onpage 38
Software media organization and filesFor information on related software environment and systemrequirements refer to the EMC Support Matrix on EMC Powerlink at
httpPowerlinkEMCcom
InstallationFor hardware installation information refer to the Cisco MDS HWInstallation Guides available at Ciscocom
For EMC-specific installation information refer to ldquoEnvironment andsystem requirementsrdquo on page 5 in this document
38 EMC Connectrix MDS 9000 NX-OS Release Notes
Troubleshooting and getting help
Troubleshooting and getting helpEMC support product and licensing information can be obtained asfollows
Product information mdash For documentation release notes softwareupdates or for information about EMC products licensing andservice go to the EMC Powerlink website (registration required) at
httpPowerlinkEMCcom
Technical support mdash For technical support go to EMC CustomerService on Powerlink To open a service request through Powerlinkyou must have a valid support agreement Please contact your EMCsales representative for details about obtaining a valid supportagreement or to answer any questions about your account
Copyright copy 2011 EMC Corporation All rights reserved
EMC believes the information in this publication is accurate as of its publication date The information issubject to change without notice
THE INFORMATION IN THIS PUBLICATION IS PROVIDED ldquoAS ISrdquo EMC CORPORATION MAKES NOREPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION INTHIS PUBLICATION AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OFMERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Use copying and distribution of any EMC software described in this publication requires an applicablesoftware license
For the most up-to-date regulatory document for your product line go to the Technical Documentation andAdvisories section on EMC Powerlink
For the most up-to-date listing of EMC product names see EMC Corporation Trademarks on EMCcom
All other trademarks used herein are the property of their respective owners
24 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
ldquoMDS-9148 limitationsrdquo on page 33
Storage Media Encryption (SME) limitationsAn SME node can only belong to one cluster Adding the node tomore than one cluster will cause problems
Currently there is no prevention or warning in place when an attemptis made to add a node to multiple clusters
SME configuration limitsTable 12 lists the SME configuration limits for this release
Table 12 SME configuration limits
Configuration Limits
Number of switches in the fabric 10
Number of clusters per switch 1
Switches in a cluster 4
Fabrics in a cluster 2
Modules in a switch 11
Cisco MSM-184 modules in a cluster 32
Initiator-Target-LUNs (ITLs) 1024
LUNs behind a target 32
Host and target ports in a cluster 128
Number of hosts per target 128
Tape backup groups per cluster 2
Volume groups in a tape backup group 4
Cisco Key Management Center ( of keys) 32K
Targets per switch that can be FC-redirected 32
25
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Deleting Cisco SME interfacesA Cisco SME interface can be deleted from the cluster only after theinterface is administratively shut-down and all related tasksassociated with the interface shut-down are complete
Cisco MDS 9124 and 9134 Multilayer fabric switchesThe Cisco MDS 9124 and 9134 Multilayer fabric switches do notsupport the following Cisco MDS SAN-OS features
IVR Remote Span Translative loop support FCCmdash no generation quench reaction only
In addition the following features have these limits
VSANs mdash 16 maximum SPAN mdash 1 session maximum
N-Port virtualization configuration limitsThe NPV features have maximum configuration limits Table 13shows the verified and maximum limits for the NPV switchesrunning NX-OS Release 5x
Maximum number of zones supported in Interop Mode 4In interop mode 4 the maximum number of zones that is supportedin an active zone set is 2047 due to limitations in the connectedvendor switch When IVR is used in interop mode 4 the maximumnumber of zones supported including IVR zones in the active zoneset is 2047 The limit for the maximum number of IVR zones perVSAN is 250 zones (two members per zone)
Table 13 NPV features limitations
Feature Verified limits Maximum limits
FLOGIs or F Disc per NPV port group 114 114
NPV switches per NPV core switch 105 105
FLOGIs per line card on NPV core switch 400 400
26 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
IPv6The management port on Cisco MDS switches supports oneuser-configured IPv6 address but does not supportauto-configuration of an IPv6 address
IP-ACL supportDo not apply IP-ACLs to only one member of a PortChannel groupApply IP-ACLs to the entire channel group
If IP-ACLs are already configured in a Gigabit Ethernet interface youcannot add this interface to a Ethernet PortChannel group
Refer to the Cisco MDS 9000 Family Configuration Guide
User RolesIn SAN-OS Release 33(x) and earlier when a user belongs to a rolewhich has a VSAN policy set to Deny and the role allows access to aspecific set of VSANs (for example 1 through 10) the user isrestricted from performing the configuration clear execute anddebug commands which had a VSAN parameter outside thisspecified set Beginning with NX-OS Release 41(1b) these users arestill prevented from performing configuration clear execute anddebug commands as before however they are allowed to performshow commands for all VSANs The ability to execute the showcommand addresses the following
In a network environment users often need to view informationin other VSANs even though they do not have permission tomodify configurations in those VSANs
This behavior makes Cisco MDS 9000 Series switches consistentwith other Cisco products such as Cisco Nexus 7000 Seriesswitches that exhibit the same behavior for those roles (whenthey apply to the VLAN policy)
27
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Using a RSA Version 1 Key for SSH Following an UpgradeFor security reasons NX-OS Release 42(x) and higher does notsupport RSA version 1 keys As a result if you upgrade from anearlier version that did support RSA version 1 keys and you hadconfigured a RSA version 1 key for SSH then you will not be able tolog in through SSH following the upgrade
If you have a RSA version 1 key configured for SSH beforeupgrading to NX-OS Release 42(x) or higher follow these steps
1 Disable SSH
2 Create RSA version 2 DSA keys
3 Enable SSH
4 Delete any RSA version 1 keys on any remote SSH clients andreplace the version 1 keys with the new version 2 keys from theswitch
Proceed with the upgrade to NX-OS Release 42(x) or higher
If you upgrade before disabling SSH and creating RSA version 2 keysfollow these steps
1 Open a Telnet session and log in through the console
2 Issue the no feature ssh command to disable SSH
3 Issue the ssh key rsa 1024 command to create RSA version 2 keys
4 Issue the feature ssh command to enable SSH
Applying Zone Configurations to VSAN 1In the setup script you can configure system default values for thedefault-zone to be permit or deny and you can configure defaultvalues for the zone distribution method and for the zone mode
These default settings are applied when a new VSAN is createdHowever the settings will not take effect on VSAN 1 because it existsprior to running the setup script Therefore when you need thosesettings for VSAN 1 you must explicitly issue the followingcommands
zone default-zone permit vsan 1 zoneset distribute full vsan 1 zone mode enhanced vsan 1
28 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
InterVSAN RoutingWhen using InterVSAN Routing (IVR) it is recommended to enableCisco Fabric Services (CFS) on all IVR-enabled switches Failure to doso may cause mismatched active zone sets if an error occurs duringzone set activation
RSPAN Traffic Not Supported on CTS Ports on 8-Gbps Switching ModulesAn inter-switch link (ISL) that is enabled for Cisco TrustSec (CTS)encryption must be brought up in non-CTS mode to support remoteSPAN (RSPAN) traffic on the following modules
DS-X9248-96K9 Cisco MDS 9000 48-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9224-96K9 Cisco MDS 9000 24-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9248-48K9 Cisco MDS 9000 444-Port Host-Optimized8-Gbps Fibre Channel Switching Module
If the ISL link is brought up with CTS enabled random packets dropsof both RSPAN traffic and normal traffic will occur on the receiverport switch
IO Accelerator Feature LimitationsIOA does not support the following NX-OS features
IVR flows
Devices with NPV and NPIV enabled
F port trunking
bull F port channeling
Support for FCIP Compression ModesIn Cisco NX-OS Release 42(1b) and higher FCIP compression mode 1and compression mode 3 are not supported on the Cisco MSM-184module and on the SSN-16 module
29
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Saving Copies of the Running Kickstart and System ImagesAfter you upgrade to MDS NX-OS Release 42(1b) or higher you arenot allowed to delete rename move or overwrite the kickstart andsystem images that are in the current system bootvar settings on anactive or standby MDS Supervisor-2 module on any Cisco MDS 9500Series switch This restriction does not apply to the integratedsupervisor module on the MDS 9200 and MDS 9100 series switches
Configuring Buffer Credits on a Generation 2 or Generation 3 ModuleWhen you configure port mode to auto or E on a Generation 2module one of the ports will not come up for the followingconfiguration
Port Mode auto or E for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E on a Generation 3module one or two of the ports will not come up for the followingconfiguration
Port Mode auto or E for the first half of the ports the second halfof the ports or for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E for all ports in the globalbuffer pool you need to reconfigure buffer credits on one or more ofthe ports The total number of buffer credits configured for all theports in the global buffer pool should be reduced by 64
Storage services module power budgetThe MDS 9509 does not have the power budget to run seven SSMcards EMC recommends a maximum of four SSMs in one 9509Customers wishing to use more than four SSMs in one chassis shouldrefer to the Cisco MDS 9000 documentation on the Ciscocom websiteto validate that there is enough power available for their desiredconfiguration
30 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Note Upgrading to the 3000 watt power supplies will alleviate thiscondition
iSCSI proxy initiator in Celerra HighRoad environmentsEMC supports the iSCSI proxy initiator feature in Celerrareg
HighRoadreg environments In proxy initiator mode one Fibre Channelinitiator is used for all iSCSI clients who access the switch via thesame iSCSI interface (iscsi33 for example)
The initiators will use the PWWN assigned to the iSCSI interface TheiSCSI interface to which an iSCSI client will logon to is configured inthe client and must be permitted by the virtual target configured forthat initiator
The current session environment supported on the MDS is
300 sessions per port 1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no InitialR2T=yes
Refer to the specific initiator support documentation on how to setthe parameters The implementation will not perform properly ifthese bits are not set
Refer to the MDS documentation for more information regarding theconfiguration of the iSCSI proxy initiator at the following Ciscowebsite
httpwwwciscocomenUSproducts
HPUX N_port IDThe N_port ID port value of 255 (0xFF) has special meaning forHP-UX A N_port ID (FC_ID) can not be returned from a switch thatcontains this value for the N_port ID (FC_ID) port value for a HP-UXinitiator or HP-UX target port Port ID value of 255 (0xFF) cannot be
31
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
configured for HP-UX initiator port and HP-UX target ports whenconfiguring MDS FC_IDs The port_ID value is the third byte of theFC_ID
Interoperability limitationsRefer to the EMC Support Matrix (ESM) and the EMC Networked Storage Topology Guide for modes of operation and caveats
NASBThe NASB feature requires that the backup application load the tapedrive with a compatible tape cartridge prior to configuring NASB inthe backup VSAN
Reserved VSAN Range and Isolated VSAN Range GuidelinesOn an NPV switch with a trunking configuration on any interface or ona regular switch where the feature fport_channel_trunk command hasbeen issued to enable the F PortChannel feature follow theseconfiguration guidelines for reserved VSANs and the isolated VSAN
bull If trunk mode is on for any of the interfaces or NP PortChannelis up the reserved VSANs are 3040 to 4078 and they are notavailable for user configuration
bull The Exchange Virtual Fabric Protocol (EVFP) isolated VSAN is4079 and it is not available for user configuration
bull VSAN 4079 will be impacted by an upgrade to NX-OS Release42(3) depending on whether or not VSAN 4079 was createdprior to the upgrade See theldquoUpgrading Effect on VSAN 4079rdquoon page 17
The following VSAN IDs are assigned in the Fibre Channel Framingand Signaling (FC-FS) interface standard
VF_ID Value Value Description
00h Do not use as a Virtual FabricIdentifier
001h EFFh Available as a Virtual FabricIdentifier
F00h FEEh Reserved
32 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Symmetrix VMax limitationsAt the time of this writing the following features are not supportedfor use with the Symmetrix VMax
FCIP Write Acceleration
The NX-OS IOA functionality is only supported with the Q2 SREnginuity release 5874229182 or higher
For the most up to date status please refer to the current revision ofthese Release Notes on httpPowerlinkemccom and the EMCSupport Matrix available through E-Lab Interoperability Navigator (ELN) athttpelabnavigatorEMCcom
Storage Applications on the MSM-184The MDS 9000 184-Port Multiservice Module (MSM-184) does notsupport multiple concurrent storage applications Only oneapplication can run on the MSM-184 at a time
Downgrading with fport-channel-trunk enabledIf you are running MDS NX-OS Release 42(x) or higher with thefport-channel-trunk feature enabled and you downgrade to anyNX-OS 41(1x) release the installer performs a nondisruptivedowngrade even though the fport-channel-trunk feature is notsupported in NX-OS 41(1x) releases
As a result the switch is in an inconsistent state and the ports maynot function properly
FEFh Control VF-ID (see FibreChannel Link Services (FC-LS)and Fibre Channel SwitchFabric Generation 4 (FC-SW-4)standards)
FF0h FFEh Vendor specific
FFFh Do not use as a Virtual FabricIdentifier
FEFh = 4079
33
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
If you are in this state a workaround is to reboot the switch followingthe upgrade
LDAP AuthenticationThere is currently a limitation in the LDAP server configuration CLIthat prevents the use of an OU with spaces in the name Normallythese OU names could be surrounded by quotation marks howeverquotation marks are not supported by the ldap-server command
MDS-9148 limitationsThe Cisco MDS 9148 Multilayer Fabric Switch does not support thefollowing NX-OS features
Medium and Long range 4GB Agilent
IVR
Remote Span
Translative loop support
FCC - no generation quench reaction only
FC-Redirect
In addition the following features have these limits
VSANS - 31 maximum
SPAN - 1 session maximum
Technical notesThe following sections provide further information on technicalnotes
EMC Email Home for Cisco MDS switchesInstallation and Trouble shooting instructions can be found in thedocumentation located at the EMC Customer Service Internalwebsite
httpwwwcsisusemccomcsweb2esnesnhomehtmConnectrix20MDS20900020Family
34 EMC Connectrix MDS 9000 NX-OS Release Notes
Technical notes
Customers requiring installation of this solution should contact theirEMC Customer Engineer to assist with the installation and providethe documentation
Supported iSCSI sessionsThe current iSCSI session environment supported on the MDS is
300 sessions per port
1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no
InitialR2T=yes
Upgrading Cisco SAN-OSThere are several methods available for upgrading SAN-OS SoftwareEMC personnel are strongly recommended that all upgrades be doneby the Automated One-Step Upgrade using the install all
command EMC personnel should refer to the Connectrix MDS 9000Family Software Image Upgrade Instructions for a complete list ofprerequisites and instructions for performing the upgrade Thisdocument along with tftp software is available on the GlobalServices website at httpwwwcsisusEMCcom under ApplicationDownload Area ESN Product Information Connectrix MDS 9000Family
The Software Upgrade Wizard is an option for upgrades While theinstall all is the preferred method the Software Install Wizard canalso be used
Supported configuration parametersFor the most up-to-date information refer to the EMC Support Matrixavailable through E-Lab Interoperability Navigator athttpelabnavigatoremccom for the latest information onsupported configurations
35
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
Supported zoning parametersRefer to the EMC Networked Storage Topology Guide for the mostup-to-date information on supported zoning parameters
At the time these notes were published the following parameterswere supported
20 VSANs 5 Hops 2000 Unique members per physical infrastructure 1000 Zonesets per physical infrastructure 2000 Zones per physical infrastructure 1 FCIP tunnel
Supported IVR parameters IVR zone members 1000 IVR zones 1000 IVR zone sets 32 VSANS 20 IVR enabled switches 64
An RPQ can be submitted for any configurations that exceed thislimit
Managing zone changes in multiswitch fabricsZoning changes may be made through Fabric Manager or CLI Whenaccessing Fabric Manager or CLI the user does so from the point ofview of one switch That is Fabric Manager and CLI are accessed byentering the IP address of one switch in the fabric
When zoning changes are made the applicable VSAN and zone setdata is propagated to the rest of the switches in the fabric via the ISLs
When zoning changes are made to a VSAN the zone set data ispropagated to the rest of the switches in the fabric via the ISLs Bydefault only the active zone set information is relayed to all switchesin the VSAN If the user accesses the Fabric Manager and CLI fromanother switch in the fabric the new VSAN and zone set informationwill not be viewable To view the active and inactive zone set on theother switches in the fabric the user must log in to the CLI and issuea command from the EXEC prompt
36 EMC Connectrix MDS 9000 NX-OS Release Notes
Documentation
Example The following is an example of copying VSAN 1 through 20 zoningdata
CiscoMDS_name zone copy active full vsan 1-20
CiscoMDS_name conf t
Enter configuration commands one per line End with CNTL Z
CiscoMDS_name(config) zoneset distribute full vsan 1-20
CiscoMDS_name(config)
Note This command needs to be issued on all switches in the fabric one timeonly
This is a nondisruptive command After issuing the commands theuser will now see the active and inactive zone sets for the specifiedVSANs on any switch that is chosen from which to manage the fabric
After a zoning change is made save the running configuration to thestartup configuration
DocumentationSend documentation comments to mdsfeedback-doccom
Product DocumentationAs of NX-OS Release 42(1a) software configuration information isavailable in new feature-specific configuration guides for thefollowing information
System management
Interfaces
Fabric
Quality of service
Security
IP services
High availability and redundancy
37
Software media organization and files
EMC Connectrix MDS 9000 NX-OS Release Notes
The information in these new guides previously existed in the CiscoMDS 9000 Family CLI Configuration Guide That configuration guideremains available on Ciscocom and should be used for all softwarereleases prior to NX-OS Release 42(1a) Configuration guidesaddress the features introduced in or available in a particular releaseSelect and view the configuration guide that pertains to the softwareinstalled in your switch
In addition Fabric Manager information has been removed from theMDS NX-OS Release Notes (this document) and placed intostandalone Fabric Manager Release Notes that support both CiscoMDS 9000 Family switches and Cisco Nexus 5000 Series switchesThe Cisco Fabric Manager Release Notes are available onhttpPowerlinkemccom and from the following website
httpwwwciscocomenUSpartnerproductsps10495prod_release_notes_listhtml
Technical supportThese release notes complement a Cisco documentation set EachCisco document refers to where to get help However for any itemssupplied by EMC see ldquoTroubleshooting and getting helprdquo onpage 38
Software media organization and filesFor information on related software environment and systemrequirements refer to the EMC Support Matrix on EMC Powerlink at
httpPowerlinkEMCcom
InstallationFor hardware installation information refer to the Cisco MDS HWInstallation Guides available at Ciscocom
For EMC-specific installation information refer to ldquoEnvironment andsystem requirementsrdquo on page 5 in this document
38 EMC Connectrix MDS 9000 NX-OS Release Notes
Troubleshooting and getting help
Troubleshooting and getting helpEMC support product and licensing information can be obtained asfollows
Product information mdash For documentation release notes softwareupdates or for information about EMC products licensing andservice go to the EMC Powerlink website (registration required) at
httpPowerlinkEMCcom
Technical support mdash For technical support go to EMC CustomerService on Powerlink To open a service request through Powerlinkyou must have a valid support agreement Please contact your EMCsales representative for details about obtaining a valid supportagreement or to answer any questions about your account
Copyright copy 2011 EMC Corporation All rights reserved
EMC believes the information in this publication is accurate as of its publication date The information issubject to change without notice
THE INFORMATION IN THIS PUBLICATION IS PROVIDED ldquoAS ISrdquo EMC CORPORATION MAKES NOREPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION INTHIS PUBLICATION AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OFMERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Use copying and distribution of any EMC software described in this publication requires an applicablesoftware license
For the most up-to-date regulatory document for your product line go to the Technical Documentation andAdvisories section on EMC Powerlink
For the most up-to-date listing of EMC product names see EMC Corporation Trademarks on EMCcom
All other trademarks used herein are the property of their respective owners
25
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Deleting Cisco SME interfacesA Cisco SME interface can be deleted from the cluster only after theinterface is administratively shut-down and all related tasksassociated with the interface shut-down are complete
Cisco MDS 9124 and 9134 Multilayer fabric switchesThe Cisco MDS 9124 and 9134 Multilayer fabric switches do notsupport the following Cisco MDS SAN-OS features
IVR Remote Span Translative loop support FCCmdash no generation quench reaction only
In addition the following features have these limits
VSANs mdash 16 maximum SPAN mdash 1 session maximum
N-Port virtualization configuration limitsThe NPV features have maximum configuration limits Table 13shows the verified and maximum limits for the NPV switchesrunning NX-OS Release 5x
Maximum number of zones supported in Interop Mode 4In interop mode 4 the maximum number of zones that is supportedin an active zone set is 2047 due to limitations in the connectedvendor switch When IVR is used in interop mode 4 the maximumnumber of zones supported including IVR zones in the active zoneset is 2047 The limit for the maximum number of IVR zones perVSAN is 250 zones (two members per zone)
Table 13 NPV features limitations
Feature Verified limits Maximum limits
FLOGIs or F Disc per NPV port group 114 114
NPV switches per NPV core switch 105 105
FLOGIs per line card on NPV core switch 400 400
26 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
IPv6The management port on Cisco MDS switches supports oneuser-configured IPv6 address but does not supportauto-configuration of an IPv6 address
IP-ACL supportDo not apply IP-ACLs to only one member of a PortChannel groupApply IP-ACLs to the entire channel group
If IP-ACLs are already configured in a Gigabit Ethernet interface youcannot add this interface to a Ethernet PortChannel group
Refer to the Cisco MDS 9000 Family Configuration Guide
User RolesIn SAN-OS Release 33(x) and earlier when a user belongs to a rolewhich has a VSAN policy set to Deny and the role allows access to aspecific set of VSANs (for example 1 through 10) the user isrestricted from performing the configuration clear execute anddebug commands which had a VSAN parameter outside thisspecified set Beginning with NX-OS Release 41(1b) these users arestill prevented from performing configuration clear execute anddebug commands as before however they are allowed to performshow commands for all VSANs The ability to execute the showcommand addresses the following
In a network environment users often need to view informationin other VSANs even though they do not have permission tomodify configurations in those VSANs
This behavior makes Cisco MDS 9000 Series switches consistentwith other Cisco products such as Cisco Nexus 7000 Seriesswitches that exhibit the same behavior for those roles (whenthey apply to the VLAN policy)
27
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Using a RSA Version 1 Key for SSH Following an UpgradeFor security reasons NX-OS Release 42(x) and higher does notsupport RSA version 1 keys As a result if you upgrade from anearlier version that did support RSA version 1 keys and you hadconfigured a RSA version 1 key for SSH then you will not be able tolog in through SSH following the upgrade
If you have a RSA version 1 key configured for SSH beforeupgrading to NX-OS Release 42(x) or higher follow these steps
1 Disable SSH
2 Create RSA version 2 DSA keys
3 Enable SSH
4 Delete any RSA version 1 keys on any remote SSH clients andreplace the version 1 keys with the new version 2 keys from theswitch
Proceed with the upgrade to NX-OS Release 42(x) or higher
If you upgrade before disabling SSH and creating RSA version 2 keysfollow these steps
1 Open a Telnet session and log in through the console
2 Issue the no feature ssh command to disable SSH
3 Issue the ssh key rsa 1024 command to create RSA version 2 keys
4 Issue the feature ssh command to enable SSH
Applying Zone Configurations to VSAN 1In the setup script you can configure system default values for thedefault-zone to be permit or deny and you can configure defaultvalues for the zone distribution method and for the zone mode
These default settings are applied when a new VSAN is createdHowever the settings will not take effect on VSAN 1 because it existsprior to running the setup script Therefore when you need thosesettings for VSAN 1 you must explicitly issue the followingcommands
zone default-zone permit vsan 1 zoneset distribute full vsan 1 zone mode enhanced vsan 1
28 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
InterVSAN RoutingWhen using InterVSAN Routing (IVR) it is recommended to enableCisco Fabric Services (CFS) on all IVR-enabled switches Failure to doso may cause mismatched active zone sets if an error occurs duringzone set activation
RSPAN Traffic Not Supported on CTS Ports on 8-Gbps Switching ModulesAn inter-switch link (ISL) that is enabled for Cisco TrustSec (CTS)encryption must be brought up in non-CTS mode to support remoteSPAN (RSPAN) traffic on the following modules
DS-X9248-96K9 Cisco MDS 9000 48-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9224-96K9 Cisco MDS 9000 24-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9248-48K9 Cisco MDS 9000 444-Port Host-Optimized8-Gbps Fibre Channel Switching Module
If the ISL link is brought up with CTS enabled random packets dropsof both RSPAN traffic and normal traffic will occur on the receiverport switch
IO Accelerator Feature LimitationsIOA does not support the following NX-OS features
IVR flows
Devices with NPV and NPIV enabled
F port trunking
bull F port channeling
Support for FCIP Compression ModesIn Cisco NX-OS Release 42(1b) and higher FCIP compression mode 1and compression mode 3 are not supported on the Cisco MSM-184module and on the SSN-16 module
29
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Saving Copies of the Running Kickstart and System ImagesAfter you upgrade to MDS NX-OS Release 42(1b) or higher you arenot allowed to delete rename move or overwrite the kickstart andsystem images that are in the current system bootvar settings on anactive or standby MDS Supervisor-2 module on any Cisco MDS 9500Series switch This restriction does not apply to the integratedsupervisor module on the MDS 9200 and MDS 9100 series switches
Configuring Buffer Credits on a Generation 2 or Generation 3 ModuleWhen you configure port mode to auto or E on a Generation 2module one of the ports will not come up for the followingconfiguration
Port Mode auto or E for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E on a Generation 3module one or two of the ports will not come up for the followingconfiguration
Port Mode auto or E for the first half of the ports the second halfof the ports or for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E for all ports in the globalbuffer pool you need to reconfigure buffer credits on one or more ofthe ports The total number of buffer credits configured for all theports in the global buffer pool should be reduced by 64
Storage services module power budgetThe MDS 9509 does not have the power budget to run seven SSMcards EMC recommends a maximum of four SSMs in one 9509Customers wishing to use more than four SSMs in one chassis shouldrefer to the Cisco MDS 9000 documentation on the Ciscocom websiteto validate that there is enough power available for their desiredconfiguration
30 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Note Upgrading to the 3000 watt power supplies will alleviate thiscondition
iSCSI proxy initiator in Celerra HighRoad environmentsEMC supports the iSCSI proxy initiator feature in Celerrareg
HighRoadreg environments In proxy initiator mode one Fibre Channelinitiator is used for all iSCSI clients who access the switch via thesame iSCSI interface (iscsi33 for example)
The initiators will use the PWWN assigned to the iSCSI interface TheiSCSI interface to which an iSCSI client will logon to is configured inthe client and must be permitted by the virtual target configured forthat initiator
The current session environment supported on the MDS is
300 sessions per port 1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no InitialR2T=yes
Refer to the specific initiator support documentation on how to setthe parameters The implementation will not perform properly ifthese bits are not set
Refer to the MDS documentation for more information regarding theconfiguration of the iSCSI proxy initiator at the following Ciscowebsite
httpwwwciscocomenUSproducts
HPUX N_port IDThe N_port ID port value of 255 (0xFF) has special meaning forHP-UX A N_port ID (FC_ID) can not be returned from a switch thatcontains this value for the N_port ID (FC_ID) port value for a HP-UXinitiator or HP-UX target port Port ID value of 255 (0xFF) cannot be
31
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
configured for HP-UX initiator port and HP-UX target ports whenconfiguring MDS FC_IDs The port_ID value is the third byte of theFC_ID
Interoperability limitationsRefer to the EMC Support Matrix (ESM) and the EMC Networked Storage Topology Guide for modes of operation and caveats
NASBThe NASB feature requires that the backup application load the tapedrive with a compatible tape cartridge prior to configuring NASB inthe backup VSAN
Reserved VSAN Range and Isolated VSAN Range GuidelinesOn an NPV switch with a trunking configuration on any interface or ona regular switch where the feature fport_channel_trunk command hasbeen issued to enable the F PortChannel feature follow theseconfiguration guidelines for reserved VSANs and the isolated VSAN
bull If trunk mode is on for any of the interfaces or NP PortChannelis up the reserved VSANs are 3040 to 4078 and they are notavailable for user configuration
bull The Exchange Virtual Fabric Protocol (EVFP) isolated VSAN is4079 and it is not available for user configuration
bull VSAN 4079 will be impacted by an upgrade to NX-OS Release42(3) depending on whether or not VSAN 4079 was createdprior to the upgrade See theldquoUpgrading Effect on VSAN 4079rdquoon page 17
The following VSAN IDs are assigned in the Fibre Channel Framingand Signaling (FC-FS) interface standard
VF_ID Value Value Description
00h Do not use as a Virtual FabricIdentifier
001h EFFh Available as a Virtual FabricIdentifier
F00h FEEh Reserved
32 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Symmetrix VMax limitationsAt the time of this writing the following features are not supportedfor use with the Symmetrix VMax
FCIP Write Acceleration
The NX-OS IOA functionality is only supported with the Q2 SREnginuity release 5874229182 or higher
For the most up to date status please refer to the current revision ofthese Release Notes on httpPowerlinkemccom and the EMCSupport Matrix available through E-Lab Interoperability Navigator (ELN) athttpelabnavigatorEMCcom
Storage Applications on the MSM-184The MDS 9000 184-Port Multiservice Module (MSM-184) does notsupport multiple concurrent storage applications Only oneapplication can run on the MSM-184 at a time
Downgrading with fport-channel-trunk enabledIf you are running MDS NX-OS Release 42(x) or higher with thefport-channel-trunk feature enabled and you downgrade to anyNX-OS 41(1x) release the installer performs a nondisruptivedowngrade even though the fport-channel-trunk feature is notsupported in NX-OS 41(1x) releases
As a result the switch is in an inconsistent state and the ports maynot function properly
FEFh Control VF-ID (see FibreChannel Link Services (FC-LS)and Fibre Channel SwitchFabric Generation 4 (FC-SW-4)standards)
FF0h FFEh Vendor specific
FFFh Do not use as a Virtual FabricIdentifier
FEFh = 4079
33
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
If you are in this state a workaround is to reboot the switch followingthe upgrade
LDAP AuthenticationThere is currently a limitation in the LDAP server configuration CLIthat prevents the use of an OU with spaces in the name Normallythese OU names could be surrounded by quotation marks howeverquotation marks are not supported by the ldap-server command
MDS-9148 limitationsThe Cisco MDS 9148 Multilayer Fabric Switch does not support thefollowing NX-OS features
Medium and Long range 4GB Agilent
IVR
Remote Span
Translative loop support
FCC - no generation quench reaction only
FC-Redirect
In addition the following features have these limits
VSANS - 31 maximum
SPAN - 1 session maximum
Technical notesThe following sections provide further information on technicalnotes
EMC Email Home for Cisco MDS switchesInstallation and Trouble shooting instructions can be found in thedocumentation located at the EMC Customer Service Internalwebsite
httpwwwcsisusemccomcsweb2esnesnhomehtmConnectrix20MDS20900020Family
34 EMC Connectrix MDS 9000 NX-OS Release Notes
Technical notes
Customers requiring installation of this solution should contact theirEMC Customer Engineer to assist with the installation and providethe documentation
Supported iSCSI sessionsThe current iSCSI session environment supported on the MDS is
300 sessions per port
1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no
InitialR2T=yes
Upgrading Cisco SAN-OSThere are several methods available for upgrading SAN-OS SoftwareEMC personnel are strongly recommended that all upgrades be doneby the Automated One-Step Upgrade using the install all
command EMC personnel should refer to the Connectrix MDS 9000Family Software Image Upgrade Instructions for a complete list ofprerequisites and instructions for performing the upgrade Thisdocument along with tftp software is available on the GlobalServices website at httpwwwcsisusEMCcom under ApplicationDownload Area ESN Product Information Connectrix MDS 9000Family
The Software Upgrade Wizard is an option for upgrades While theinstall all is the preferred method the Software Install Wizard canalso be used
Supported configuration parametersFor the most up-to-date information refer to the EMC Support Matrixavailable through E-Lab Interoperability Navigator athttpelabnavigatoremccom for the latest information onsupported configurations
35
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
Supported zoning parametersRefer to the EMC Networked Storage Topology Guide for the mostup-to-date information on supported zoning parameters
At the time these notes were published the following parameterswere supported
20 VSANs 5 Hops 2000 Unique members per physical infrastructure 1000 Zonesets per physical infrastructure 2000 Zones per physical infrastructure 1 FCIP tunnel
Supported IVR parameters IVR zone members 1000 IVR zones 1000 IVR zone sets 32 VSANS 20 IVR enabled switches 64
An RPQ can be submitted for any configurations that exceed thislimit
Managing zone changes in multiswitch fabricsZoning changes may be made through Fabric Manager or CLI Whenaccessing Fabric Manager or CLI the user does so from the point ofview of one switch That is Fabric Manager and CLI are accessed byentering the IP address of one switch in the fabric
When zoning changes are made the applicable VSAN and zone setdata is propagated to the rest of the switches in the fabric via the ISLs
When zoning changes are made to a VSAN the zone set data ispropagated to the rest of the switches in the fabric via the ISLs Bydefault only the active zone set information is relayed to all switchesin the VSAN If the user accesses the Fabric Manager and CLI fromanother switch in the fabric the new VSAN and zone set informationwill not be viewable To view the active and inactive zone set on theother switches in the fabric the user must log in to the CLI and issuea command from the EXEC prompt
36 EMC Connectrix MDS 9000 NX-OS Release Notes
Documentation
Example The following is an example of copying VSAN 1 through 20 zoningdata
CiscoMDS_name zone copy active full vsan 1-20
CiscoMDS_name conf t
Enter configuration commands one per line End with CNTL Z
CiscoMDS_name(config) zoneset distribute full vsan 1-20
CiscoMDS_name(config)
Note This command needs to be issued on all switches in the fabric one timeonly
This is a nondisruptive command After issuing the commands theuser will now see the active and inactive zone sets for the specifiedVSANs on any switch that is chosen from which to manage the fabric
After a zoning change is made save the running configuration to thestartup configuration
DocumentationSend documentation comments to mdsfeedback-doccom
Product DocumentationAs of NX-OS Release 42(1a) software configuration information isavailable in new feature-specific configuration guides for thefollowing information
System management
Interfaces
Fabric
Quality of service
Security
IP services
High availability and redundancy
37
Software media organization and files
EMC Connectrix MDS 9000 NX-OS Release Notes
The information in these new guides previously existed in the CiscoMDS 9000 Family CLI Configuration Guide That configuration guideremains available on Ciscocom and should be used for all softwarereleases prior to NX-OS Release 42(1a) Configuration guidesaddress the features introduced in or available in a particular releaseSelect and view the configuration guide that pertains to the softwareinstalled in your switch
In addition Fabric Manager information has been removed from theMDS NX-OS Release Notes (this document) and placed intostandalone Fabric Manager Release Notes that support both CiscoMDS 9000 Family switches and Cisco Nexus 5000 Series switchesThe Cisco Fabric Manager Release Notes are available onhttpPowerlinkemccom and from the following website
httpwwwciscocomenUSpartnerproductsps10495prod_release_notes_listhtml
Technical supportThese release notes complement a Cisco documentation set EachCisco document refers to where to get help However for any itemssupplied by EMC see ldquoTroubleshooting and getting helprdquo onpage 38
Software media organization and filesFor information on related software environment and systemrequirements refer to the EMC Support Matrix on EMC Powerlink at
httpPowerlinkEMCcom
InstallationFor hardware installation information refer to the Cisco MDS HWInstallation Guides available at Ciscocom
For EMC-specific installation information refer to ldquoEnvironment andsystem requirementsrdquo on page 5 in this document
38 EMC Connectrix MDS 9000 NX-OS Release Notes
Troubleshooting and getting help
Troubleshooting and getting helpEMC support product and licensing information can be obtained asfollows
Product information mdash For documentation release notes softwareupdates or for information about EMC products licensing andservice go to the EMC Powerlink website (registration required) at
httpPowerlinkEMCcom
Technical support mdash For technical support go to EMC CustomerService on Powerlink To open a service request through Powerlinkyou must have a valid support agreement Please contact your EMCsales representative for details about obtaining a valid supportagreement or to answer any questions about your account
Copyright copy 2011 EMC Corporation All rights reserved
EMC believes the information in this publication is accurate as of its publication date The information issubject to change without notice
THE INFORMATION IN THIS PUBLICATION IS PROVIDED ldquoAS ISrdquo EMC CORPORATION MAKES NOREPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION INTHIS PUBLICATION AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OFMERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Use copying and distribution of any EMC software described in this publication requires an applicablesoftware license
For the most up-to-date regulatory document for your product line go to the Technical Documentation andAdvisories section on EMC Powerlink
For the most up-to-date listing of EMC product names see EMC Corporation Trademarks on EMCcom
All other trademarks used herein are the property of their respective owners
26 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
IPv6The management port on Cisco MDS switches supports oneuser-configured IPv6 address but does not supportauto-configuration of an IPv6 address
IP-ACL supportDo not apply IP-ACLs to only one member of a PortChannel groupApply IP-ACLs to the entire channel group
If IP-ACLs are already configured in a Gigabit Ethernet interface youcannot add this interface to a Ethernet PortChannel group
Refer to the Cisco MDS 9000 Family Configuration Guide
User RolesIn SAN-OS Release 33(x) and earlier when a user belongs to a rolewhich has a VSAN policy set to Deny and the role allows access to aspecific set of VSANs (for example 1 through 10) the user isrestricted from performing the configuration clear execute anddebug commands which had a VSAN parameter outside thisspecified set Beginning with NX-OS Release 41(1b) these users arestill prevented from performing configuration clear execute anddebug commands as before however they are allowed to performshow commands for all VSANs The ability to execute the showcommand addresses the following
In a network environment users often need to view informationin other VSANs even though they do not have permission tomodify configurations in those VSANs
This behavior makes Cisco MDS 9000 Series switches consistentwith other Cisco products such as Cisco Nexus 7000 Seriesswitches that exhibit the same behavior for those roles (whenthey apply to the VLAN policy)
27
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Using a RSA Version 1 Key for SSH Following an UpgradeFor security reasons NX-OS Release 42(x) and higher does notsupport RSA version 1 keys As a result if you upgrade from anearlier version that did support RSA version 1 keys and you hadconfigured a RSA version 1 key for SSH then you will not be able tolog in through SSH following the upgrade
If you have a RSA version 1 key configured for SSH beforeupgrading to NX-OS Release 42(x) or higher follow these steps
1 Disable SSH
2 Create RSA version 2 DSA keys
3 Enable SSH
4 Delete any RSA version 1 keys on any remote SSH clients andreplace the version 1 keys with the new version 2 keys from theswitch
Proceed with the upgrade to NX-OS Release 42(x) or higher
If you upgrade before disabling SSH and creating RSA version 2 keysfollow these steps
1 Open a Telnet session and log in through the console
2 Issue the no feature ssh command to disable SSH
3 Issue the ssh key rsa 1024 command to create RSA version 2 keys
4 Issue the feature ssh command to enable SSH
Applying Zone Configurations to VSAN 1In the setup script you can configure system default values for thedefault-zone to be permit or deny and you can configure defaultvalues for the zone distribution method and for the zone mode
These default settings are applied when a new VSAN is createdHowever the settings will not take effect on VSAN 1 because it existsprior to running the setup script Therefore when you need thosesettings for VSAN 1 you must explicitly issue the followingcommands
zone default-zone permit vsan 1 zoneset distribute full vsan 1 zone mode enhanced vsan 1
28 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
InterVSAN RoutingWhen using InterVSAN Routing (IVR) it is recommended to enableCisco Fabric Services (CFS) on all IVR-enabled switches Failure to doso may cause mismatched active zone sets if an error occurs duringzone set activation
RSPAN Traffic Not Supported on CTS Ports on 8-Gbps Switching ModulesAn inter-switch link (ISL) that is enabled for Cisco TrustSec (CTS)encryption must be brought up in non-CTS mode to support remoteSPAN (RSPAN) traffic on the following modules
DS-X9248-96K9 Cisco MDS 9000 48-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9224-96K9 Cisco MDS 9000 24-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9248-48K9 Cisco MDS 9000 444-Port Host-Optimized8-Gbps Fibre Channel Switching Module
If the ISL link is brought up with CTS enabled random packets dropsof both RSPAN traffic and normal traffic will occur on the receiverport switch
IO Accelerator Feature LimitationsIOA does not support the following NX-OS features
IVR flows
Devices with NPV and NPIV enabled
F port trunking
bull F port channeling
Support for FCIP Compression ModesIn Cisco NX-OS Release 42(1b) and higher FCIP compression mode 1and compression mode 3 are not supported on the Cisco MSM-184module and on the SSN-16 module
29
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Saving Copies of the Running Kickstart and System ImagesAfter you upgrade to MDS NX-OS Release 42(1b) or higher you arenot allowed to delete rename move or overwrite the kickstart andsystem images that are in the current system bootvar settings on anactive or standby MDS Supervisor-2 module on any Cisco MDS 9500Series switch This restriction does not apply to the integratedsupervisor module on the MDS 9200 and MDS 9100 series switches
Configuring Buffer Credits on a Generation 2 or Generation 3 ModuleWhen you configure port mode to auto or E on a Generation 2module one of the ports will not come up for the followingconfiguration
Port Mode auto or E for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E on a Generation 3module one or two of the ports will not come up for the followingconfiguration
Port Mode auto or E for the first half of the ports the second halfof the ports or for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E for all ports in the globalbuffer pool you need to reconfigure buffer credits on one or more ofthe ports The total number of buffer credits configured for all theports in the global buffer pool should be reduced by 64
Storage services module power budgetThe MDS 9509 does not have the power budget to run seven SSMcards EMC recommends a maximum of four SSMs in one 9509Customers wishing to use more than four SSMs in one chassis shouldrefer to the Cisco MDS 9000 documentation on the Ciscocom websiteto validate that there is enough power available for their desiredconfiguration
30 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Note Upgrading to the 3000 watt power supplies will alleviate thiscondition
iSCSI proxy initiator in Celerra HighRoad environmentsEMC supports the iSCSI proxy initiator feature in Celerrareg
HighRoadreg environments In proxy initiator mode one Fibre Channelinitiator is used for all iSCSI clients who access the switch via thesame iSCSI interface (iscsi33 for example)
The initiators will use the PWWN assigned to the iSCSI interface TheiSCSI interface to which an iSCSI client will logon to is configured inthe client and must be permitted by the virtual target configured forthat initiator
The current session environment supported on the MDS is
300 sessions per port 1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no InitialR2T=yes
Refer to the specific initiator support documentation on how to setthe parameters The implementation will not perform properly ifthese bits are not set
Refer to the MDS documentation for more information regarding theconfiguration of the iSCSI proxy initiator at the following Ciscowebsite
httpwwwciscocomenUSproducts
HPUX N_port IDThe N_port ID port value of 255 (0xFF) has special meaning forHP-UX A N_port ID (FC_ID) can not be returned from a switch thatcontains this value for the N_port ID (FC_ID) port value for a HP-UXinitiator or HP-UX target port Port ID value of 255 (0xFF) cannot be
31
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
configured for HP-UX initiator port and HP-UX target ports whenconfiguring MDS FC_IDs The port_ID value is the third byte of theFC_ID
Interoperability limitationsRefer to the EMC Support Matrix (ESM) and the EMC Networked Storage Topology Guide for modes of operation and caveats
NASBThe NASB feature requires that the backup application load the tapedrive with a compatible tape cartridge prior to configuring NASB inthe backup VSAN
Reserved VSAN Range and Isolated VSAN Range GuidelinesOn an NPV switch with a trunking configuration on any interface or ona regular switch where the feature fport_channel_trunk command hasbeen issued to enable the F PortChannel feature follow theseconfiguration guidelines for reserved VSANs and the isolated VSAN
bull If trunk mode is on for any of the interfaces or NP PortChannelis up the reserved VSANs are 3040 to 4078 and they are notavailable for user configuration
bull The Exchange Virtual Fabric Protocol (EVFP) isolated VSAN is4079 and it is not available for user configuration
bull VSAN 4079 will be impacted by an upgrade to NX-OS Release42(3) depending on whether or not VSAN 4079 was createdprior to the upgrade See theldquoUpgrading Effect on VSAN 4079rdquoon page 17
The following VSAN IDs are assigned in the Fibre Channel Framingand Signaling (FC-FS) interface standard
VF_ID Value Value Description
00h Do not use as a Virtual FabricIdentifier
001h EFFh Available as a Virtual FabricIdentifier
F00h FEEh Reserved
32 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Symmetrix VMax limitationsAt the time of this writing the following features are not supportedfor use with the Symmetrix VMax
FCIP Write Acceleration
The NX-OS IOA functionality is only supported with the Q2 SREnginuity release 5874229182 or higher
For the most up to date status please refer to the current revision ofthese Release Notes on httpPowerlinkemccom and the EMCSupport Matrix available through E-Lab Interoperability Navigator (ELN) athttpelabnavigatorEMCcom
Storage Applications on the MSM-184The MDS 9000 184-Port Multiservice Module (MSM-184) does notsupport multiple concurrent storage applications Only oneapplication can run on the MSM-184 at a time
Downgrading with fport-channel-trunk enabledIf you are running MDS NX-OS Release 42(x) or higher with thefport-channel-trunk feature enabled and you downgrade to anyNX-OS 41(1x) release the installer performs a nondisruptivedowngrade even though the fport-channel-trunk feature is notsupported in NX-OS 41(1x) releases
As a result the switch is in an inconsistent state and the ports maynot function properly
FEFh Control VF-ID (see FibreChannel Link Services (FC-LS)and Fibre Channel SwitchFabric Generation 4 (FC-SW-4)standards)
FF0h FFEh Vendor specific
FFFh Do not use as a Virtual FabricIdentifier
FEFh = 4079
33
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
If you are in this state a workaround is to reboot the switch followingthe upgrade
LDAP AuthenticationThere is currently a limitation in the LDAP server configuration CLIthat prevents the use of an OU with spaces in the name Normallythese OU names could be surrounded by quotation marks howeverquotation marks are not supported by the ldap-server command
MDS-9148 limitationsThe Cisco MDS 9148 Multilayer Fabric Switch does not support thefollowing NX-OS features
Medium and Long range 4GB Agilent
IVR
Remote Span
Translative loop support
FCC - no generation quench reaction only
FC-Redirect
In addition the following features have these limits
VSANS - 31 maximum
SPAN - 1 session maximum
Technical notesThe following sections provide further information on technicalnotes
EMC Email Home for Cisco MDS switchesInstallation and Trouble shooting instructions can be found in thedocumentation located at the EMC Customer Service Internalwebsite
httpwwwcsisusemccomcsweb2esnesnhomehtmConnectrix20MDS20900020Family
34 EMC Connectrix MDS 9000 NX-OS Release Notes
Technical notes
Customers requiring installation of this solution should contact theirEMC Customer Engineer to assist with the installation and providethe documentation
Supported iSCSI sessionsThe current iSCSI session environment supported on the MDS is
300 sessions per port
1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no
InitialR2T=yes
Upgrading Cisco SAN-OSThere are several methods available for upgrading SAN-OS SoftwareEMC personnel are strongly recommended that all upgrades be doneby the Automated One-Step Upgrade using the install all
command EMC personnel should refer to the Connectrix MDS 9000Family Software Image Upgrade Instructions for a complete list ofprerequisites and instructions for performing the upgrade Thisdocument along with tftp software is available on the GlobalServices website at httpwwwcsisusEMCcom under ApplicationDownload Area ESN Product Information Connectrix MDS 9000Family
The Software Upgrade Wizard is an option for upgrades While theinstall all is the preferred method the Software Install Wizard canalso be used
Supported configuration parametersFor the most up-to-date information refer to the EMC Support Matrixavailable through E-Lab Interoperability Navigator athttpelabnavigatoremccom for the latest information onsupported configurations
35
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
Supported zoning parametersRefer to the EMC Networked Storage Topology Guide for the mostup-to-date information on supported zoning parameters
At the time these notes were published the following parameterswere supported
20 VSANs 5 Hops 2000 Unique members per physical infrastructure 1000 Zonesets per physical infrastructure 2000 Zones per physical infrastructure 1 FCIP tunnel
Supported IVR parameters IVR zone members 1000 IVR zones 1000 IVR zone sets 32 VSANS 20 IVR enabled switches 64
An RPQ can be submitted for any configurations that exceed thislimit
Managing zone changes in multiswitch fabricsZoning changes may be made through Fabric Manager or CLI Whenaccessing Fabric Manager or CLI the user does so from the point ofview of one switch That is Fabric Manager and CLI are accessed byentering the IP address of one switch in the fabric
When zoning changes are made the applicable VSAN and zone setdata is propagated to the rest of the switches in the fabric via the ISLs
When zoning changes are made to a VSAN the zone set data ispropagated to the rest of the switches in the fabric via the ISLs Bydefault only the active zone set information is relayed to all switchesin the VSAN If the user accesses the Fabric Manager and CLI fromanother switch in the fabric the new VSAN and zone set informationwill not be viewable To view the active and inactive zone set on theother switches in the fabric the user must log in to the CLI and issuea command from the EXEC prompt
36 EMC Connectrix MDS 9000 NX-OS Release Notes
Documentation
Example The following is an example of copying VSAN 1 through 20 zoningdata
CiscoMDS_name zone copy active full vsan 1-20
CiscoMDS_name conf t
Enter configuration commands one per line End with CNTL Z
CiscoMDS_name(config) zoneset distribute full vsan 1-20
CiscoMDS_name(config)
Note This command needs to be issued on all switches in the fabric one timeonly
This is a nondisruptive command After issuing the commands theuser will now see the active and inactive zone sets for the specifiedVSANs on any switch that is chosen from which to manage the fabric
After a zoning change is made save the running configuration to thestartup configuration
DocumentationSend documentation comments to mdsfeedback-doccom
Product DocumentationAs of NX-OS Release 42(1a) software configuration information isavailable in new feature-specific configuration guides for thefollowing information
System management
Interfaces
Fabric
Quality of service
Security
IP services
High availability and redundancy
37
Software media organization and files
EMC Connectrix MDS 9000 NX-OS Release Notes
The information in these new guides previously existed in the CiscoMDS 9000 Family CLI Configuration Guide That configuration guideremains available on Ciscocom and should be used for all softwarereleases prior to NX-OS Release 42(1a) Configuration guidesaddress the features introduced in or available in a particular releaseSelect and view the configuration guide that pertains to the softwareinstalled in your switch
In addition Fabric Manager information has been removed from theMDS NX-OS Release Notes (this document) and placed intostandalone Fabric Manager Release Notes that support both CiscoMDS 9000 Family switches and Cisco Nexus 5000 Series switchesThe Cisco Fabric Manager Release Notes are available onhttpPowerlinkemccom and from the following website
httpwwwciscocomenUSpartnerproductsps10495prod_release_notes_listhtml
Technical supportThese release notes complement a Cisco documentation set EachCisco document refers to where to get help However for any itemssupplied by EMC see ldquoTroubleshooting and getting helprdquo onpage 38
Software media organization and filesFor information on related software environment and systemrequirements refer to the EMC Support Matrix on EMC Powerlink at
httpPowerlinkEMCcom
InstallationFor hardware installation information refer to the Cisco MDS HWInstallation Guides available at Ciscocom
For EMC-specific installation information refer to ldquoEnvironment andsystem requirementsrdquo on page 5 in this document
38 EMC Connectrix MDS 9000 NX-OS Release Notes
Troubleshooting and getting help
Troubleshooting and getting helpEMC support product and licensing information can be obtained asfollows
Product information mdash For documentation release notes softwareupdates or for information about EMC products licensing andservice go to the EMC Powerlink website (registration required) at
httpPowerlinkEMCcom
Technical support mdash For technical support go to EMC CustomerService on Powerlink To open a service request through Powerlinkyou must have a valid support agreement Please contact your EMCsales representative for details about obtaining a valid supportagreement or to answer any questions about your account
Copyright copy 2011 EMC Corporation All rights reserved
EMC believes the information in this publication is accurate as of its publication date The information issubject to change without notice
THE INFORMATION IN THIS PUBLICATION IS PROVIDED ldquoAS ISrdquo EMC CORPORATION MAKES NOREPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION INTHIS PUBLICATION AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OFMERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Use copying and distribution of any EMC software described in this publication requires an applicablesoftware license
For the most up-to-date regulatory document for your product line go to the Technical Documentation andAdvisories section on EMC Powerlink
For the most up-to-date listing of EMC product names see EMC Corporation Trademarks on EMCcom
All other trademarks used herein are the property of their respective owners
27
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Using a RSA Version 1 Key for SSH Following an UpgradeFor security reasons NX-OS Release 42(x) and higher does notsupport RSA version 1 keys As a result if you upgrade from anearlier version that did support RSA version 1 keys and you hadconfigured a RSA version 1 key for SSH then you will not be able tolog in through SSH following the upgrade
If you have a RSA version 1 key configured for SSH beforeupgrading to NX-OS Release 42(x) or higher follow these steps
1 Disable SSH
2 Create RSA version 2 DSA keys
3 Enable SSH
4 Delete any RSA version 1 keys on any remote SSH clients andreplace the version 1 keys with the new version 2 keys from theswitch
Proceed with the upgrade to NX-OS Release 42(x) or higher
If you upgrade before disabling SSH and creating RSA version 2 keysfollow these steps
1 Open a Telnet session and log in through the console
2 Issue the no feature ssh command to disable SSH
3 Issue the ssh key rsa 1024 command to create RSA version 2 keys
4 Issue the feature ssh command to enable SSH
Applying Zone Configurations to VSAN 1In the setup script you can configure system default values for thedefault-zone to be permit or deny and you can configure defaultvalues for the zone distribution method and for the zone mode
These default settings are applied when a new VSAN is createdHowever the settings will not take effect on VSAN 1 because it existsprior to running the setup script Therefore when you need thosesettings for VSAN 1 you must explicitly issue the followingcommands
zone default-zone permit vsan 1 zoneset distribute full vsan 1 zone mode enhanced vsan 1
28 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
InterVSAN RoutingWhen using InterVSAN Routing (IVR) it is recommended to enableCisco Fabric Services (CFS) on all IVR-enabled switches Failure to doso may cause mismatched active zone sets if an error occurs duringzone set activation
RSPAN Traffic Not Supported on CTS Ports on 8-Gbps Switching ModulesAn inter-switch link (ISL) that is enabled for Cisco TrustSec (CTS)encryption must be brought up in non-CTS mode to support remoteSPAN (RSPAN) traffic on the following modules
DS-X9248-96K9 Cisco MDS 9000 48-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9224-96K9 Cisco MDS 9000 24-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9248-48K9 Cisco MDS 9000 444-Port Host-Optimized8-Gbps Fibre Channel Switching Module
If the ISL link is brought up with CTS enabled random packets dropsof both RSPAN traffic and normal traffic will occur on the receiverport switch
IO Accelerator Feature LimitationsIOA does not support the following NX-OS features
IVR flows
Devices with NPV and NPIV enabled
F port trunking
bull F port channeling
Support for FCIP Compression ModesIn Cisco NX-OS Release 42(1b) and higher FCIP compression mode 1and compression mode 3 are not supported on the Cisco MSM-184module and on the SSN-16 module
29
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Saving Copies of the Running Kickstart and System ImagesAfter you upgrade to MDS NX-OS Release 42(1b) or higher you arenot allowed to delete rename move or overwrite the kickstart andsystem images that are in the current system bootvar settings on anactive or standby MDS Supervisor-2 module on any Cisco MDS 9500Series switch This restriction does not apply to the integratedsupervisor module on the MDS 9200 and MDS 9100 series switches
Configuring Buffer Credits on a Generation 2 or Generation 3 ModuleWhen you configure port mode to auto or E on a Generation 2module one of the ports will not come up for the followingconfiguration
Port Mode auto or E for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E on a Generation 3module one or two of the ports will not come up for the followingconfiguration
Port Mode auto or E for the first half of the ports the second halfof the ports or for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E for all ports in the globalbuffer pool you need to reconfigure buffer credits on one or more ofthe ports The total number of buffer credits configured for all theports in the global buffer pool should be reduced by 64
Storage services module power budgetThe MDS 9509 does not have the power budget to run seven SSMcards EMC recommends a maximum of four SSMs in one 9509Customers wishing to use more than four SSMs in one chassis shouldrefer to the Cisco MDS 9000 documentation on the Ciscocom websiteto validate that there is enough power available for their desiredconfiguration
30 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Note Upgrading to the 3000 watt power supplies will alleviate thiscondition
iSCSI proxy initiator in Celerra HighRoad environmentsEMC supports the iSCSI proxy initiator feature in Celerrareg
HighRoadreg environments In proxy initiator mode one Fibre Channelinitiator is used for all iSCSI clients who access the switch via thesame iSCSI interface (iscsi33 for example)
The initiators will use the PWWN assigned to the iSCSI interface TheiSCSI interface to which an iSCSI client will logon to is configured inthe client and must be permitted by the virtual target configured forthat initiator
The current session environment supported on the MDS is
300 sessions per port 1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no InitialR2T=yes
Refer to the specific initiator support documentation on how to setthe parameters The implementation will not perform properly ifthese bits are not set
Refer to the MDS documentation for more information regarding theconfiguration of the iSCSI proxy initiator at the following Ciscowebsite
httpwwwciscocomenUSproducts
HPUX N_port IDThe N_port ID port value of 255 (0xFF) has special meaning forHP-UX A N_port ID (FC_ID) can not be returned from a switch thatcontains this value for the N_port ID (FC_ID) port value for a HP-UXinitiator or HP-UX target port Port ID value of 255 (0xFF) cannot be
31
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
configured for HP-UX initiator port and HP-UX target ports whenconfiguring MDS FC_IDs The port_ID value is the third byte of theFC_ID
Interoperability limitationsRefer to the EMC Support Matrix (ESM) and the EMC Networked Storage Topology Guide for modes of operation and caveats
NASBThe NASB feature requires that the backup application load the tapedrive with a compatible tape cartridge prior to configuring NASB inthe backup VSAN
Reserved VSAN Range and Isolated VSAN Range GuidelinesOn an NPV switch with a trunking configuration on any interface or ona regular switch where the feature fport_channel_trunk command hasbeen issued to enable the F PortChannel feature follow theseconfiguration guidelines for reserved VSANs and the isolated VSAN
bull If trunk mode is on for any of the interfaces or NP PortChannelis up the reserved VSANs are 3040 to 4078 and they are notavailable for user configuration
bull The Exchange Virtual Fabric Protocol (EVFP) isolated VSAN is4079 and it is not available for user configuration
bull VSAN 4079 will be impacted by an upgrade to NX-OS Release42(3) depending on whether or not VSAN 4079 was createdprior to the upgrade See theldquoUpgrading Effect on VSAN 4079rdquoon page 17
The following VSAN IDs are assigned in the Fibre Channel Framingand Signaling (FC-FS) interface standard
VF_ID Value Value Description
00h Do not use as a Virtual FabricIdentifier
001h EFFh Available as a Virtual FabricIdentifier
F00h FEEh Reserved
32 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Symmetrix VMax limitationsAt the time of this writing the following features are not supportedfor use with the Symmetrix VMax
FCIP Write Acceleration
The NX-OS IOA functionality is only supported with the Q2 SREnginuity release 5874229182 or higher
For the most up to date status please refer to the current revision ofthese Release Notes on httpPowerlinkemccom and the EMCSupport Matrix available through E-Lab Interoperability Navigator (ELN) athttpelabnavigatorEMCcom
Storage Applications on the MSM-184The MDS 9000 184-Port Multiservice Module (MSM-184) does notsupport multiple concurrent storage applications Only oneapplication can run on the MSM-184 at a time
Downgrading with fport-channel-trunk enabledIf you are running MDS NX-OS Release 42(x) or higher with thefport-channel-trunk feature enabled and you downgrade to anyNX-OS 41(1x) release the installer performs a nondisruptivedowngrade even though the fport-channel-trunk feature is notsupported in NX-OS 41(1x) releases
As a result the switch is in an inconsistent state and the ports maynot function properly
FEFh Control VF-ID (see FibreChannel Link Services (FC-LS)and Fibre Channel SwitchFabric Generation 4 (FC-SW-4)standards)
FF0h FFEh Vendor specific
FFFh Do not use as a Virtual FabricIdentifier
FEFh = 4079
33
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
If you are in this state a workaround is to reboot the switch followingthe upgrade
LDAP AuthenticationThere is currently a limitation in the LDAP server configuration CLIthat prevents the use of an OU with spaces in the name Normallythese OU names could be surrounded by quotation marks howeverquotation marks are not supported by the ldap-server command
MDS-9148 limitationsThe Cisco MDS 9148 Multilayer Fabric Switch does not support thefollowing NX-OS features
Medium and Long range 4GB Agilent
IVR
Remote Span
Translative loop support
FCC - no generation quench reaction only
FC-Redirect
In addition the following features have these limits
VSANS - 31 maximum
SPAN - 1 session maximum
Technical notesThe following sections provide further information on technicalnotes
EMC Email Home for Cisco MDS switchesInstallation and Trouble shooting instructions can be found in thedocumentation located at the EMC Customer Service Internalwebsite
httpwwwcsisusemccomcsweb2esnesnhomehtmConnectrix20MDS20900020Family
34 EMC Connectrix MDS 9000 NX-OS Release Notes
Technical notes
Customers requiring installation of this solution should contact theirEMC Customer Engineer to assist with the installation and providethe documentation
Supported iSCSI sessionsThe current iSCSI session environment supported on the MDS is
300 sessions per port
1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no
InitialR2T=yes
Upgrading Cisco SAN-OSThere are several methods available for upgrading SAN-OS SoftwareEMC personnel are strongly recommended that all upgrades be doneby the Automated One-Step Upgrade using the install all
command EMC personnel should refer to the Connectrix MDS 9000Family Software Image Upgrade Instructions for a complete list ofprerequisites and instructions for performing the upgrade Thisdocument along with tftp software is available on the GlobalServices website at httpwwwcsisusEMCcom under ApplicationDownload Area ESN Product Information Connectrix MDS 9000Family
The Software Upgrade Wizard is an option for upgrades While theinstall all is the preferred method the Software Install Wizard canalso be used
Supported configuration parametersFor the most up-to-date information refer to the EMC Support Matrixavailable through E-Lab Interoperability Navigator athttpelabnavigatoremccom for the latest information onsupported configurations
35
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
Supported zoning parametersRefer to the EMC Networked Storage Topology Guide for the mostup-to-date information on supported zoning parameters
At the time these notes were published the following parameterswere supported
20 VSANs 5 Hops 2000 Unique members per physical infrastructure 1000 Zonesets per physical infrastructure 2000 Zones per physical infrastructure 1 FCIP tunnel
Supported IVR parameters IVR zone members 1000 IVR zones 1000 IVR zone sets 32 VSANS 20 IVR enabled switches 64
An RPQ can be submitted for any configurations that exceed thislimit
Managing zone changes in multiswitch fabricsZoning changes may be made through Fabric Manager or CLI Whenaccessing Fabric Manager or CLI the user does so from the point ofview of one switch That is Fabric Manager and CLI are accessed byentering the IP address of one switch in the fabric
When zoning changes are made the applicable VSAN and zone setdata is propagated to the rest of the switches in the fabric via the ISLs
When zoning changes are made to a VSAN the zone set data ispropagated to the rest of the switches in the fabric via the ISLs Bydefault only the active zone set information is relayed to all switchesin the VSAN If the user accesses the Fabric Manager and CLI fromanother switch in the fabric the new VSAN and zone set informationwill not be viewable To view the active and inactive zone set on theother switches in the fabric the user must log in to the CLI and issuea command from the EXEC prompt
36 EMC Connectrix MDS 9000 NX-OS Release Notes
Documentation
Example The following is an example of copying VSAN 1 through 20 zoningdata
CiscoMDS_name zone copy active full vsan 1-20
CiscoMDS_name conf t
Enter configuration commands one per line End with CNTL Z
CiscoMDS_name(config) zoneset distribute full vsan 1-20
CiscoMDS_name(config)
Note This command needs to be issued on all switches in the fabric one timeonly
This is a nondisruptive command After issuing the commands theuser will now see the active and inactive zone sets for the specifiedVSANs on any switch that is chosen from which to manage the fabric
After a zoning change is made save the running configuration to thestartup configuration
DocumentationSend documentation comments to mdsfeedback-doccom
Product DocumentationAs of NX-OS Release 42(1a) software configuration information isavailable in new feature-specific configuration guides for thefollowing information
System management
Interfaces
Fabric
Quality of service
Security
IP services
High availability and redundancy
37
Software media organization and files
EMC Connectrix MDS 9000 NX-OS Release Notes
The information in these new guides previously existed in the CiscoMDS 9000 Family CLI Configuration Guide That configuration guideremains available on Ciscocom and should be used for all softwarereleases prior to NX-OS Release 42(1a) Configuration guidesaddress the features introduced in or available in a particular releaseSelect and view the configuration guide that pertains to the softwareinstalled in your switch
In addition Fabric Manager information has been removed from theMDS NX-OS Release Notes (this document) and placed intostandalone Fabric Manager Release Notes that support both CiscoMDS 9000 Family switches and Cisco Nexus 5000 Series switchesThe Cisco Fabric Manager Release Notes are available onhttpPowerlinkemccom and from the following website
httpwwwciscocomenUSpartnerproductsps10495prod_release_notes_listhtml
Technical supportThese release notes complement a Cisco documentation set EachCisco document refers to where to get help However for any itemssupplied by EMC see ldquoTroubleshooting and getting helprdquo onpage 38
Software media organization and filesFor information on related software environment and systemrequirements refer to the EMC Support Matrix on EMC Powerlink at
httpPowerlinkEMCcom
InstallationFor hardware installation information refer to the Cisco MDS HWInstallation Guides available at Ciscocom
For EMC-specific installation information refer to ldquoEnvironment andsystem requirementsrdquo on page 5 in this document
38 EMC Connectrix MDS 9000 NX-OS Release Notes
Troubleshooting and getting help
Troubleshooting and getting helpEMC support product and licensing information can be obtained asfollows
Product information mdash For documentation release notes softwareupdates or for information about EMC products licensing andservice go to the EMC Powerlink website (registration required) at
httpPowerlinkEMCcom
Technical support mdash For technical support go to EMC CustomerService on Powerlink To open a service request through Powerlinkyou must have a valid support agreement Please contact your EMCsales representative for details about obtaining a valid supportagreement or to answer any questions about your account
Copyright copy 2011 EMC Corporation All rights reserved
EMC believes the information in this publication is accurate as of its publication date The information issubject to change without notice
THE INFORMATION IN THIS PUBLICATION IS PROVIDED ldquoAS ISrdquo EMC CORPORATION MAKES NOREPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION INTHIS PUBLICATION AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OFMERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Use copying and distribution of any EMC software described in this publication requires an applicablesoftware license
For the most up-to-date regulatory document for your product line go to the Technical Documentation andAdvisories section on EMC Powerlink
For the most up-to-date listing of EMC product names see EMC Corporation Trademarks on EMCcom
All other trademarks used herein are the property of their respective owners
28 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
InterVSAN RoutingWhen using InterVSAN Routing (IVR) it is recommended to enableCisco Fabric Services (CFS) on all IVR-enabled switches Failure to doso may cause mismatched active zone sets if an error occurs duringzone set activation
RSPAN Traffic Not Supported on CTS Ports on 8-Gbps Switching ModulesAn inter-switch link (ISL) that is enabled for Cisco TrustSec (CTS)encryption must be brought up in non-CTS mode to support remoteSPAN (RSPAN) traffic on the following modules
DS-X9248-96K9 Cisco MDS 9000 48-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9224-96K9 Cisco MDS 9000 24-Port 8-Gbps Fibre ChannelSwitching Module
DS-X9248-48K9 Cisco MDS 9000 444-Port Host-Optimized8-Gbps Fibre Channel Switching Module
If the ISL link is brought up with CTS enabled random packets dropsof both RSPAN traffic and normal traffic will occur on the receiverport switch
IO Accelerator Feature LimitationsIOA does not support the following NX-OS features
IVR flows
Devices with NPV and NPIV enabled
F port trunking
bull F port channeling
Support for FCIP Compression ModesIn Cisco NX-OS Release 42(1b) and higher FCIP compression mode 1and compression mode 3 are not supported on the Cisco MSM-184module and on the SSN-16 module
29
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Saving Copies of the Running Kickstart and System ImagesAfter you upgrade to MDS NX-OS Release 42(1b) or higher you arenot allowed to delete rename move or overwrite the kickstart andsystem images that are in the current system bootvar settings on anactive or standby MDS Supervisor-2 module on any Cisco MDS 9500Series switch This restriction does not apply to the integratedsupervisor module on the MDS 9200 and MDS 9100 series switches
Configuring Buffer Credits on a Generation 2 or Generation 3 ModuleWhen you configure port mode to auto or E on a Generation 2module one of the ports will not come up for the followingconfiguration
Port Mode auto or E for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E on a Generation 3module one or two of the ports will not come up for the followingconfiguration
Port Mode auto or E for the first half of the ports the second halfof the ports or for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E for all ports in the globalbuffer pool you need to reconfigure buffer credits on one or more ofthe ports The total number of buffer credits configured for all theports in the global buffer pool should be reduced by 64
Storage services module power budgetThe MDS 9509 does not have the power budget to run seven SSMcards EMC recommends a maximum of four SSMs in one 9509Customers wishing to use more than four SSMs in one chassis shouldrefer to the Cisco MDS 9000 documentation on the Ciscocom websiteto validate that there is enough power available for their desiredconfiguration
30 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Note Upgrading to the 3000 watt power supplies will alleviate thiscondition
iSCSI proxy initiator in Celerra HighRoad environmentsEMC supports the iSCSI proxy initiator feature in Celerrareg
HighRoadreg environments In proxy initiator mode one Fibre Channelinitiator is used for all iSCSI clients who access the switch via thesame iSCSI interface (iscsi33 for example)
The initiators will use the PWWN assigned to the iSCSI interface TheiSCSI interface to which an iSCSI client will logon to is configured inthe client and must be permitted by the virtual target configured forthat initiator
The current session environment supported on the MDS is
300 sessions per port 1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no InitialR2T=yes
Refer to the specific initiator support documentation on how to setthe parameters The implementation will not perform properly ifthese bits are not set
Refer to the MDS documentation for more information regarding theconfiguration of the iSCSI proxy initiator at the following Ciscowebsite
httpwwwciscocomenUSproducts
HPUX N_port IDThe N_port ID port value of 255 (0xFF) has special meaning forHP-UX A N_port ID (FC_ID) can not be returned from a switch thatcontains this value for the N_port ID (FC_ID) port value for a HP-UXinitiator or HP-UX target port Port ID value of 255 (0xFF) cannot be
31
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
configured for HP-UX initiator port and HP-UX target ports whenconfiguring MDS FC_IDs The port_ID value is the third byte of theFC_ID
Interoperability limitationsRefer to the EMC Support Matrix (ESM) and the EMC Networked Storage Topology Guide for modes of operation and caveats
NASBThe NASB feature requires that the backup application load the tapedrive with a compatible tape cartridge prior to configuring NASB inthe backup VSAN
Reserved VSAN Range and Isolated VSAN Range GuidelinesOn an NPV switch with a trunking configuration on any interface or ona regular switch where the feature fport_channel_trunk command hasbeen issued to enable the F PortChannel feature follow theseconfiguration guidelines for reserved VSANs and the isolated VSAN
bull If trunk mode is on for any of the interfaces or NP PortChannelis up the reserved VSANs are 3040 to 4078 and they are notavailable for user configuration
bull The Exchange Virtual Fabric Protocol (EVFP) isolated VSAN is4079 and it is not available for user configuration
bull VSAN 4079 will be impacted by an upgrade to NX-OS Release42(3) depending on whether or not VSAN 4079 was createdprior to the upgrade See theldquoUpgrading Effect on VSAN 4079rdquoon page 17
The following VSAN IDs are assigned in the Fibre Channel Framingand Signaling (FC-FS) interface standard
VF_ID Value Value Description
00h Do not use as a Virtual FabricIdentifier
001h EFFh Available as a Virtual FabricIdentifier
F00h FEEh Reserved
32 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Symmetrix VMax limitationsAt the time of this writing the following features are not supportedfor use with the Symmetrix VMax
FCIP Write Acceleration
The NX-OS IOA functionality is only supported with the Q2 SREnginuity release 5874229182 or higher
For the most up to date status please refer to the current revision ofthese Release Notes on httpPowerlinkemccom and the EMCSupport Matrix available through E-Lab Interoperability Navigator (ELN) athttpelabnavigatorEMCcom
Storage Applications on the MSM-184The MDS 9000 184-Port Multiservice Module (MSM-184) does notsupport multiple concurrent storage applications Only oneapplication can run on the MSM-184 at a time
Downgrading with fport-channel-trunk enabledIf you are running MDS NX-OS Release 42(x) or higher with thefport-channel-trunk feature enabled and you downgrade to anyNX-OS 41(1x) release the installer performs a nondisruptivedowngrade even though the fport-channel-trunk feature is notsupported in NX-OS 41(1x) releases
As a result the switch is in an inconsistent state and the ports maynot function properly
FEFh Control VF-ID (see FibreChannel Link Services (FC-LS)and Fibre Channel SwitchFabric Generation 4 (FC-SW-4)standards)
FF0h FFEh Vendor specific
FFFh Do not use as a Virtual FabricIdentifier
FEFh = 4079
33
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
If you are in this state a workaround is to reboot the switch followingthe upgrade
LDAP AuthenticationThere is currently a limitation in the LDAP server configuration CLIthat prevents the use of an OU with spaces in the name Normallythese OU names could be surrounded by quotation marks howeverquotation marks are not supported by the ldap-server command
MDS-9148 limitationsThe Cisco MDS 9148 Multilayer Fabric Switch does not support thefollowing NX-OS features
Medium and Long range 4GB Agilent
IVR
Remote Span
Translative loop support
FCC - no generation quench reaction only
FC-Redirect
In addition the following features have these limits
VSANS - 31 maximum
SPAN - 1 session maximum
Technical notesThe following sections provide further information on technicalnotes
EMC Email Home for Cisco MDS switchesInstallation and Trouble shooting instructions can be found in thedocumentation located at the EMC Customer Service Internalwebsite
httpwwwcsisusemccomcsweb2esnesnhomehtmConnectrix20MDS20900020Family
34 EMC Connectrix MDS 9000 NX-OS Release Notes
Technical notes
Customers requiring installation of this solution should contact theirEMC Customer Engineer to assist with the installation and providethe documentation
Supported iSCSI sessionsThe current iSCSI session environment supported on the MDS is
300 sessions per port
1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no
InitialR2T=yes
Upgrading Cisco SAN-OSThere are several methods available for upgrading SAN-OS SoftwareEMC personnel are strongly recommended that all upgrades be doneby the Automated One-Step Upgrade using the install all
command EMC personnel should refer to the Connectrix MDS 9000Family Software Image Upgrade Instructions for a complete list ofprerequisites and instructions for performing the upgrade Thisdocument along with tftp software is available on the GlobalServices website at httpwwwcsisusEMCcom under ApplicationDownload Area ESN Product Information Connectrix MDS 9000Family
The Software Upgrade Wizard is an option for upgrades While theinstall all is the preferred method the Software Install Wizard canalso be used
Supported configuration parametersFor the most up-to-date information refer to the EMC Support Matrixavailable through E-Lab Interoperability Navigator athttpelabnavigatoremccom for the latest information onsupported configurations
35
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
Supported zoning parametersRefer to the EMC Networked Storage Topology Guide for the mostup-to-date information on supported zoning parameters
At the time these notes were published the following parameterswere supported
20 VSANs 5 Hops 2000 Unique members per physical infrastructure 1000 Zonesets per physical infrastructure 2000 Zones per physical infrastructure 1 FCIP tunnel
Supported IVR parameters IVR zone members 1000 IVR zones 1000 IVR zone sets 32 VSANS 20 IVR enabled switches 64
An RPQ can be submitted for any configurations that exceed thislimit
Managing zone changes in multiswitch fabricsZoning changes may be made through Fabric Manager or CLI Whenaccessing Fabric Manager or CLI the user does so from the point ofview of one switch That is Fabric Manager and CLI are accessed byentering the IP address of one switch in the fabric
When zoning changes are made the applicable VSAN and zone setdata is propagated to the rest of the switches in the fabric via the ISLs
When zoning changes are made to a VSAN the zone set data ispropagated to the rest of the switches in the fabric via the ISLs Bydefault only the active zone set information is relayed to all switchesin the VSAN If the user accesses the Fabric Manager and CLI fromanother switch in the fabric the new VSAN and zone set informationwill not be viewable To view the active and inactive zone set on theother switches in the fabric the user must log in to the CLI and issuea command from the EXEC prompt
36 EMC Connectrix MDS 9000 NX-OS Release Notes
Documentation
Example The following is an example of copying VSAN 1 through 20 zoningdata
CiscoMDS_name zone copy active full vsan 1-20
CiscoMDS_name conf t
Enter configuration commands one per line End with CNTL Z
CiscoMDS_name(config) zoneset distribute full vsan 1-20
CiscoMDS_name(config)
Note This command needs to be issued on all switches in the fabric one timeonly
This is a nondisruptive command After issuing the commands theuser will now see the active and inactive zone sets for the specifiedVSANs on any switch that is chosen from which to manage the fabric
After a zoning change is made save the running configuration to thestartup configuration
DocumentationSend documentation comments to mdsfeedback-doccom
Product DocumentationAs of NX-OS Release 42(1a) software configuration information isavailable in new feature-specific configuration guides for thefollowing information
System management
Interfaces
Fabric
Quality of service
Security
IP services
High availability and redundancy
37
Software media organization and files
EMC Connectrix MDS 9000 NX-OS Release Notes
The information in these new guides previously existed in the CiscoMDS 9000 Family CLI Configuration Guide That configuration guideremains available on Ciscocom and should be used for all softwarereleases prior to NX-OS Release 42(1a) Configuration guidesaddress the features introduced in or available in a particular releaseSelect and view the configuration guide that pertains to the softwareinstalled in your switch
In addition Fabric Manager information has been removed from theMDS NX-OS Release Notes (this document) and placed intostandalone Fabric Manager Release Notes that support both CiscoMDS 9000 Family switches and Cisco Nexus 5000 Series switchesThe Cisco Fabric Manager Release Notes are available onhttpPowerlinkemccom and from the following website
httpwwwciscocomenUSpartnerproductsps10495prod_release_notes_listhtml
Technical supportThese release notes complement a Cisco documentation set EachCisco document refers to where to get help However for any itemssupplied by EMC see ldquoTroubleshooting and getting helprdquo onpage 38
Software media organization and filesFor information on related software environment and systemrequirements refer to the EMC Support Matrix on EMC Powerlink at
httpPowerlinkEMCcom
InstallationFor hardware installation information refer to the Cisco MDS HWInstallation Guides available at Ciscocom
For EMC-specific installation information refer to ldquoEnvironment andsystem requirementsrdquo on page 5 in this document
38 EMC Connectrix MDS 9000 NX-OS Release Notes
Troubleshooting and getting help
Troubleshooting and getting helpEMC support product and licensing information can be obtained asfollows
Product information mdash For documentation release notes softwareupdates or for information about EMC products licensing andservice go to the EMC Powerlink website (registration required) at
httpPowerlinkEMCcom
Technical support mdash For technical support go to EMC CustomerService on Powerlink To open a service request through Powerlinkyou must have a valid support agreement Please contact your EMCsales representative for details about obtaining a valid supportagreement or to answer any questions about your account
Copyright copy 2011 EMC Corporation All rights reserved
EMC believes the information in this publication is accurate as of its publication date The information issubject to change without notice
THE INFORMATION IN THIS PUBLICATION IS PROVIDED ldquoAS ISrdquo EMC CORPORATION MAKES NOREPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION INTHIS PUBLICATION AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OFMERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Use copying and distribution of any EMC software described in this publication requires an applicablesoftware license
For the most up-to-date regulatory document for your product line go to the Technical Documentation andAdvisories section on EMC Powerlink
For the most up-to-date listing of EMC product names see EMC Corporation Trademarks on EMCcom
All other trademarks used herein are the property of their respective owners
29
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
Saving Copies of the Running Kickstart and System ImagesAfter you upgrade to MDS NX-OS Release 42(1b) or higher you arenot allowed to delete rename move or overwrite the kickstart andsystem images that are in the current system bootvar settings on anactive or standby MDS Supervisor-2 module on any Cisco MDS 9500Series switch This restriction does not apply to the integratedsupervisor module on the MDS 9200 and MDS 9100 series switches
Configuring Buffer Credits on a Generation 2 or Generation 3 ModuleWhen you configure port mode to auto or E on a Generation 2module one of the ports will not come up for the followingconfiguration
Port Mode auto or E for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E on a Generation 3module one or two of the ports will not come up for the followingconfiguration
Port Mode auto or E for the first half of the ports the second halfof the ports or for all of the ports
Rate Mode dedicated
Buffer Credits default value
When you configure port mode to auto or E for all ports in the globalbuffer pool you need to reconfigure buffer credits on one or more ofthe ports The total number of buffer credits configured for all theports in the global buffer pool should be reduced by 64
Storage services module power budgetThe MDS 9509 does not have the power budget to run seven SSMcards EMC recommends a maximum of four SSMs in one 9509Customers wishing to use more than four SSMs in one chassis shouldrefer to the Cisco MDS 9000 documentation on the Ciscocom websiteto validate that there is enough power available for their desiredconfiguration
30 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Note Upgrading to the 3000 watt power supplies will alleviate thiscondition
iSCSI proxy initiator in Celerra HighRoad environmentsEMC supports the iSCSI proxy initiator feature in Celerrareg
HighRoadreg environments In proxy initiator mode one Fibre Channelinitiator is used for all iSCSI clients who access the switch via thesame iSCSI interface (iscsi33 for example)
The initiators will use the PWWN assigned to the iSCSI interface TheiSCSI interface to which an iSCSI client will logon to is configured inthe client and must be permitted by the virtual target configured forthat initiator
The current session environment supported on the MDS is
300 sessions per port 1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no InitialR2T=yes
Refer to the specific initiator support documentation on how to setthe parameters The implementation will not perform properly ifthese bits are not set
Refer to the MDS documentation for more information regarding theconfiguration of the iSCSI proxy initiator at the following Ciscowebsite
httpwwwciscocomenUSproducts
HPUX N_port IDThe N_port ID port value of 255 (0xFF) has special meaning forHP-UX A N_port ID (FC_ID) can not be returned from a switch thatcontains this value for the N_port ID (FC_ID) port value for a HP-UXinitiator or HP-UX target port Port ID value of 255 (0xFF) cannot be
31
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
configured for HP-UX initiator port and HP-UX target ports whenconfiguring MDS FC_IDs The port_ID value is the third byte of theFC_ID
Interoperability limitationsRefer to the EMC Support Matrix (ESM) and the EMC Networked Storage Topology Guide for modes of operation and caveats
NASBThe NASB feature requires that the backup application load the tapedrive with a compatible tape cartridge prior to configuring NASB inthe backup VSAN
Reserved VSAN Range and Isolated VSAN Range GuidelinesOn an NPV switch with a trunking configuration on any interface or ona regular switch where the feature fport_channel_trunk command hasbeen issued to enable the F PortChannel feature follow theseconfiguration guidelines for reserved VSANs and the isolated VSAN
bull If trunk mode is on for any of the interfaces or NP PortChannelis up the reserved VSANs are 3040 to 4078 and they are notavailable for user configuration
bull The Exchange Virtual Fabric Protocol (EVFP) isolated VSAN is4079 and it is not available for user configuration
bull VSAN 4079 will be impacted by an upgrade to NX-OS Release42(3) depending on whether or not VSAN 4079 was createdprior to the upgrade See theldquoUpgrading Effect on VSAN 4079rdquoon page 17
The following VSAN IDs are assigned in the Fibre Channel Framingand Signaling (FC-FS) interface standard
VF_ID Value Value Description
00h Do not use as a Virtual FabricIdentifier
001h EFFh Available as a Virtual FabricIdentifier
F00h FEEh Reserved
32 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Symmetrix VMax limitationsAt the time of this writing the following features are not supportedfor use with the Symmetrix VMax
FCIP Write Acceleration
The NX-OS IOA functionality is only supported with the Q2 SREnginuity release 5874229182 or higher
For the most up to date status please refer to the current revision ofthese Release Notes on httpPowerlinkemccom and the EMCSupport Matrix available through E-Lab Interoperability Navigator (ELN) athttpelabnavigatorEMCcom
Storage Applications on the MSM-184The MDS 9000 184-Port Multiservice Module (MSM-184) does notsupport multiple concurrent storage applications Only oneapplication can run on the MSM-184 at a time
Downgrading with fport-channel-trunk enabledIf you are running MDS NX-OS Release 42(x) or higher with thefport-channel-trunk feature enabled and you downgrade to anyNX-OS 41(1x) release the installer performs a nondisruptivedowngrade even though the fport-channel-trunk feature is notsupported in NX-OS 41(1x) releases
As a result the switch is in an inconsistent state and the ports maynot function properly
FEFh Control VF-ID (see FibreChannel Link Services (FC-LS)and Fibre Channel SwitchFabric Generation 4 (FC-SW-4)standards)
FF0h FFEh Vendor specific
FFFh Do not use as a Virtual FabricIdentifier
FEFh = 4079
33
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
If you are in this state a workaround is to reboot the switch followingthe upgrade
LDAP AuthenticationThere is currently a limitation in the LDAP server configuration CLIthat prevents the use of an OU with spaces in the name Normallythese OU names could be surrounded by quotation marks howeverquotation marks are not supported by the ldap-server command
MDS-9148 limitationsThe Cisco MDS 9148 Multilayer Fabric Switch does not support thefollowing NX-OS features
Medium and Long range 4GB Agilent
IVR
Remote Span
Translative loop support
FCC - no generation quench reaction only
FC-Redirect
In addition the following features have these limits
VSANS - 31 maximum
SPAN - 1 session maximum
Technical notesThe following sections provide further information on technicalnotes
EMC Email Home for Cisco MDS switchesInstallation and Trouble shooting instructions can be found in thedocumentation located at the EMC Customer Service Internalwebsite
httpwwwcsisusemccomcsweb2esnesnhomehtmConnectrix20MDS20900020Family
34 EMC Connectrix MDS 9000 NX-OS Release Notes
Technical notes
Customers requiring installation of this solution should contact theirEMC Customer Engineer to assist with the installation and providethe documentation
Supported iSCSI sessionsThe current iSCSI session environment supported on the MDS is
300 sessions per port
1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no
InitialR2T=yes
Upgrading Cisco SAN-OSThere are several methods available for upgrading SAN-OS SoftwareEMC personnel are strongly recommended that all upgrades be doneby the Automated One-Step Upgrade using the install all
command EMC personnel should refer to the Connectrix MDS 9000Family Software Image Upgrade Instructions for a complete list ofprerequisites and instructions for performing the upgrade Thisdocument along with tftp software is available on the GlobalServices website at httpwwwcsisusEMCcom under ApplicationDownload Area ESN Product Information Connectrix MDS 9000Family
The Software Upgrade Wizard is an option for upgrades While theinstall all is the preferred method the Software Install Wizard canalso be used
Supported configuration parametersFor the most up-to-date information refer to the EMC Support Matrixavailable through E-Lab Interoperability Navigator athttpelabnavigatoremccom for the latest information onsupported configurations
35
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
Supported zoning parametersRefer to the EMC Networked Storage Topology Guide for the mostup-to-date information on supported zoning parameters
At the time these notes were published the following parameterswere supported
20 VSANs 5 Hops 2000 Unique members per physical infrastructure 1000 Zonesets per physical infrastructure 2000 Zones per physical infrastructure 1 FCIP tunnel
Supported IVR parameters IVR zone members 1000 IVR zones 1000 IVR zone sets 32 VSANS 20 IVR enabled switches 64
An RPQ can be submitted for any configurations that exceed thislimit
Managing zone changes in multiswitch fabricsZoning changes may be made through Fabric Manager or CLI Whenaccessing Fabric Manager or CLI the user does so from the point ofview of one switch That is Fabric Manager and CLI are accessed byentering the IP address of one switch in the fabric
When zoning changes are made the applicable VSAN and zone setdata is propagated to the rest of the switches in the fabric via the ISLs
When zoning changes are made to a VSAN the zone set data ispropagated to the rest of the switches in the fabric via the ISLs Bydefault only the active zone set information is relayed to all switchesin the VSAN If the user accesses the Fabric Manager and CLI fromanother switch in the fabric the new VSAN and zone set informationwill not be viewable To view the active and inactive zone set on theother switches in the fabric the user must log in to the CLI and issuea command from the EXEC prompt
36 EMC Connectrix MDS 9000 NX-OS Release Notes
Documentation
Example The following is an example of copying VSAN 1 through 20 zoningdata
CiscoMDS_name zone copy active full vsan 1-20
CiscoMDS_name conf t
Enter configuration commands one per line End with CNTL Z
CiscoMDS_name(config) zoneset distribute full vsan 1-20
CiscoMDS_name(config)
Note This command needs to be issued on all switches in the fabric one timeonly
This is a nondisruptive command After issuing the commands theuser will now see the active and inactive zone sets for the specifiedVSANs on any switch that is chosen from which to manage the fabric
After a zoning change is made save the running configuration to thestartup configuration
DocumentationSend documentation comments to mdsfeedback-doccom
Product DocumentationAs of NX-OS Release 42(1a) software configuration information isavailable in new feature-specific configuration guides for thefollowing information
System management
Interfaces
Fabric
Quality of service
Security
IP services
High availability and redundancy
37
Software media organization and files
EMC Connectrix MDS 9000 NX-OS Release Notes
The information in these new guides previously existed in the CiscoMDS 9000 Family CLI Configuration Guide That configuration guideremains available on Ciscocom and should be used for all softwarereleases prior to NX-OS Release 42(1a) Configuration guidesaddress the features introduced in or available in a particular releaseSelect and view the configuration guide that pertains to the softwareinstalled in your switch
In addition Fabric Manager information has been removed from theMDS NX-OS Release Notes (this document) and placed intostandalone Fabric Manager Release Notes that support both CiscoMDS 9000 Family switches and Cisco Nexus 5000 Series switchesThe Cisco Fabric Manager Release Notes are available onhttpPowerlinkemccom and from the following website
httpwwwciscocomenUSpartnerproductsps10495prod_release_notes_listhtml
Technical supportThese release notes complement a Cisco documentation set EachCisco document refers to where to get help However for any itemssupplied by EMC see ldquoTroubleshooting and getting helprdquo onpage 38
Software media organization and filesFor information on related software environment and systemrequirements refer to the EMC Support Matrix on EMC Powerlink at
httpPowerlinkEMCcom
InstallationFor hardware installation information refer to the Cisco MDS HWInstallation Guides available at Ciscocom
For EMC-specific installation information refer to ldquoEnvironment andsystem requirementsrdquo on page 5 in this document
38 EMC Connectrix MDS 9000 NX-OS Release Notes
Troubleshooting and getting help
Troubleshooting and getting helpEMC support product and licensing information can be obtained asfollows
Product information mdash For documentation release notes softwareupdates or for information about EMC products licensing andservice go to the EMC Powerlink website (registration required) at
httpPowerlinkEMCcom
Technical support mdash For technical support go to EMC CustomerService on Powerlink To open a service request through Powerlinkyou must have a valid support agreement Please contact your EMCsales representative for details about obtaining a valid supportagreement or to answer any questions about your account
Copyright copy 2011 EMC Corporation All rights reserved
EMC believes the information in this publication is accurate as of its publication date The information issubject to change without notice
THE INFORMATION IN THIS PUBLICATION IS PROVIDED ldquoAS ISrdquo EMC CORPORATION MAKES NOREPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION INTHIS PUBLICATION AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OFMERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Use copying and distribution of any EMC software described in this publication requires an applicablesoftware license
For the most up-to-date regulatory document for your product line go to the Technical Documentation andAdvisories section on EMC Powerlink
For the most up-to-date listing of EMC product names see EMC Corporation Trademarks on EMCcom
All other trademarks used herein are the property of their respective owners
30 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Note Upgrading to the 3000 watt power supplies will alleviate thiscondition
iSCSI proxy initiator in Celerra HighRoad environmentsEMC supports the iSCSI proxy initiator feature in Celerrareg
HighRoadreg environments In proxy initiator mode one Fibre Channelinitiator is used for all iSCSI clients who access the switch via thesame iSCSI interface (iscsi33 for example)
The initiators will use the PWWN assigned to the iSCSI interface TheiSCSI interface to which an iSCSI client will logon to is configured inthe client and must be permitted by the virtual target configured forthat initiator
The current session environment supported on the MDS is
300 sessions per port 1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no InitialR2T=yes
Refer to the specific initiator support documentation on how to setthe parameters The implementation will not perform properly ifthese bits are not set
Refer to the MDS documentation for more information regarding theconfiguration of the iSCSI proxy initiator at the following Ciscowebsite
httpwwwciscocomenUSproducts
HPUX N_port IDThe N_port ID port value of 255 (0xFF) has special meaning forHP-UX A N_port ID (FC_ID) can not be returned from a switch thatcontains this value for the N_port ID (FC_ID) port value for a HP-UXinitiator or HP-UX target port Port ID value of 255 (0xFF) cannot be
31
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
configured for HP-UX initiator port and HP-UX target ports whenconfiguring MDS FC_IDs The port_ID value is the third byte of theFC_ID
Interoperability limitationsRefer to the EMC Support Matrix (ESM) and the EMC Networked Storage Topology Guide for modes of operation and caveats
NASBThe NASB feature requires that the backup application load the tapedrive with a compatible tape cartridge prior to configuring NASB inthe backup VSAN
Reserved VSAN Range and Isolated VSAN Range GuidelinesOn an NPV switch with a trunking configuration on any interface or ona regular switch where the feature fport_channel_trunk command hasbeen issued to enable the F PortChannel feature follow theseconfiguration guidelines for reserved VSANs and the isolated VSAN
bull If trunk mode is on for any of the interfaces or NP PortChannelis up the reserved VSANs are 3040 to 4078 and they are notavailable for user configuration
bull The Exchange Virtual Fabric Protocol (EVFP) isolated VSAN is4079 and it is not available for user configuration
bull VSAN 4079 will be impacted by an upgrade to NX-OS Release42(3) depending on whether or not VSAN 4079 was createdprior to the upgrade See theldquoUpgrading Effect on VSAN 4079rdquoon page 17
The following VSAN IDs are assigned in the Fibre Channel Framingand Signaling (FC-FS) interface standard
VF_ID Value Value Description
00h Do not use as a Virtual FabricIdentifier
001h EFFh Available as a Virtual FabricIdentifier
F00h FEEh Reserved
32 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Symmetrix VMax limitationsAt the time of this writing the following features are not supportedfor use with the Symmetrix VMax
FCIP Write Acceleration
The NX-OS IOA functionality is only supported with the Q2 SREnginuity release 5874229182 or higher
For the most up to date status please refer to the current revision ofthese Release Notes on httpPowerlinkemccom and the EMCSupport Matrix available through E-Lab Interoperability Navigator (ELN) athttpelabnavigatorEMCcom
Storage Applications on the MSM-184The MDS 9000 184-Port Multiservice Module (MSM-184) does notsupport multiple concurrent storage applications Only oneapplication can run on the MSM-184 at a time
Downgrading with fport-channel-trunk enabledIf you are running MDS NX-OS Release 42(x) or higher with thefport-channel-trunk feature enabled and you downgrade to anyNX-OS 41(1x) release the installer performs a nondisruptivedowngrade even though the fport-channel-trunk feature is notsupported in NX-OS 41(1x) releases
As a result the switch is in an inconsistent state and the ports maynot function properly
FEFh Control VF-ID (see FibreChannel Link Services (FC-LS)and Fibre Channel SwitchFabric Generation 4 (FC-SW-4)standards)
FF0h FFEh Vendor specific
FFFh Do not use as a Virtual FabricIdentifier
FEFh = 4079
33
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
If you are in this state a workaround is to reboot the switch followingthe upgrade
LDAP AuthenticationThere is currently a limitation in the LDAP server configuration CLIthat prevents the use of an OU with spaces in the name Normallythese OU names could be surrounded by quotation marks howeverquotation marks are not supported by the ldap-server command
MDS-9148 limitationsThe Cisco MDS 9148 Multilayer Fabric Switch does not support thefollowing NX-OS features
Medium and Long range 4GB Agilent
IVR
Remote Span
Translative loop support
FCC - no generation quench reaction only
FC-Redirect
In addition the following features have these limits
VSANS - 31 maximum
SPAN - 1 session maximum
Technical notesThe following sections provide further information on technicalnotes
EMC Email Home for Cisco MDS switchesInstallation and Trouble shooting instructions can be found in thedocumentation located at the EMC Customer Service Internalwebsite
httpwwwcsisusemccomcsweb2esnesnhomehtmConnectrix20MDS20900020Family
34 EMC Connectrix MDS 9000 NX-OS Release Notes
Technical notes
Customers requiring installation of this solution should contact theirEMC Customer Engineer to assist with the installation and providethe documentation
Supported iSCSI sessionsThe current iSCSI session environment supported on the MDS is
300 sessions per port
1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no
InitialR2T=yes
Upgrading Cisco SAN-OSThere are several methods available for upgrading SAN-OS SoftwareEMC personnel are strongly recommended that all upgrades be doneby the Automated One-Step Upgrade using the install all
command EMC personnel should refer to the Connectrix MDS 9000Family Software Image Upgrade Instructions for a complete list ofprerequisites and instructions for performing the upgrade Thisdocument along with tftp software is available on the GlobalServices website at httpwwwcsisusEMCcom under ApplicationDownload Area ESN Product Information Connectrix MDS 9000Family
The Software Upgrade Wizard is an option for upgrades While theinstall all is the preferred method the Software Install Wizard canalso be used
Supported configuration parametersFor the most up-to-date information refer to the EMC Support Matrixavailable through E-Lab Interoperability Navigator athttpelabnavigatoremccom for the latest information onsupported configurations
35
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
Supported zoning parametersRefer to the EMC Networked Storage Topology Guide for the mostup-to-date information on supported zoning parameters
At the time these notes were published the following parameterswere supported
20 VSANs 5 Hops 2000 Unique members per physical infrastructure 1000 Zonesets per physical infrastructure 2000 Zones per physical infrastructure 1 FCIP tunnel
Supported IVR parameters IVR zone members 1000 IVR zones 1000 IVR zone sets 32 VSANS 20 IVR enabled switches 64
An RPQ can be submitted for any configurations that exceed thislimit
Managing zone changes in multiswitch fabricsZoning changes may be made through Fabric Manager or CLI Whenaccessing Fabric Manager or CLI the user does so from the point ofview of one switch That is Fabric Manager and CLI are accessed byentering the IP address of one switch in the fabric
When zoning changes are made the applicable VSAN and zone setdata is propagated to the rest of the switches in the fabric via the ISLs
When zoning changes are made to a VSAN the zone set data ispropagated to the rest of the switches in the fabric via the ISLs Bydefault only the active zone set information is relayed to all switchesin the VSAN If the user accesses the Fabric Manager and CLI fromanother switch in the fabric the new VSAN and zone set informationwill not be viewable To view the active and inactive zone set on theother switches in the fabric the user must log in to the CLI and issuea command from the EXEC prompt
36 EMC Connectrix MDS 9000 NX-OS Release Notes
Documentation
Example The following is an example of copying VSAN 1 through 20 zoningdata
CiscoMDS_name zone copy active full vsan 1-20
CiscoMDS_name conf t
Enter configuration commands one per line End with CNTL Z
CiscoMDS_name(config) zoneset distribute full vsan 1-20
CiscoMDS_name(config)
Note This command needs to be issued on all switches in the fabric one timeonly
This is a nondisruptive command After issuing the commands theuser will now see the active and inactive zone sets for the specifiedVSANs on any switch that is chosen from which to manage the fabric
After a zoning change is made save the running configuration to thestartup configuration
DocumentationSend documentation comments to mdsfeedback-doccom
Product DocumentationAs of NX-OS Release 42(1a) software configuration information isavailable in new feature-specific configuration guides for thefollowing information
System management
Interfaces
Fabric
Quality of service
Security
IP services
High availability and redundancy
37
Software media organization and files
EMC Connectrix MDS 9000 NX-OS Release Notes
The information in these new guides previously existed in the CiscoMDS 9000 Family CLI Configuration Guide That configuration guideremains available on Ciscocom and should be used for all softwarereleases prior to NX-OS Release 42(1a) Configuration guidesaddress the features introduced in or available in a particular releaseSelect and view the configuration guide that pertains to the softwareinstalled in your switch
In addition Fabric Manager information has been removed from theMDS NX-OS Release Notes (this document) and placed intostandalone Fabric Manager Release Notes that support both CiscoMDS 9000 Family switches and Cisco Nexus 5000 Series switchesThe Cisco Fabric Manager Release Notes are available onhttpPowerlinkemccom and from the following website
httpwwwciscocomenUSpartnerproductsps10495prod_release_notes_listhtml
Technical supportThese release notes complement a Cisco documentation set EachCisco document refers to where to get help However for any itemssupplied by EMC see ldquoTroubleshooting and getting helprdquo onpage 38
Software media organization and filesFor information on related software environment and systemrequirements refer to the EMC Support Matrix on EMC Powerlink at
httpPowerlinkEMCcom
InstallationFor hardware installation information refer to the Cisco MDS HWInstallation Guides available at Ciscocom
For EMC-specific installation information refer to ldquoEnvironment andsystem requirementsrdquo on page 5 in this document
38 EMC Connectrix MDS 9000 NX-OS Release Notes
Troubleshooting and getting help
Troubleshooting and getting helpEMC support product and licensing information can be obtained asfollows
Product information mdash For documentation release notes softwareupdates or for information about EMC products licensing andservice go to the EMC Powerlink website (registration required) at
httpPowerlinkEMCcom
Technical support mdash For technical support go to EMC CustomerService on Powerlink To open a service request through Powerlinkyou must have a valid support agreement Please contact your EMCsales representative for details about obtaining a valid supportagreement or to answer any questions about your account
Copyright copy 2011 EMC Corporation All rights reserved
EMC believes the information in this publication is accurate as of its publication date The information issubject to change without notice
THE INFORMATION IN THIS PUBLICATION IS PROVIDED ldquoAS ISrdquo EMC CORPORATION MAKES NOREPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION INTHIS PUBLICATION AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OFMERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Use copying and distribution of any EMC software described in this publication requires an applicablesoftware license
For the most up-to-date regulatory document for your product line go to the Technical Documentation andAdvisories section on EMC Powerlink
For the most up-to-date listing of EMC product names see EMC Corporation Trademarks on EMCcom
All other trademarks used herein are the property of their respective owners
31
Known problems and limitations
EMC Connectrix MDS 9000 NX-OS Release Notes
configured for HP-UX initiator port and HP-UX target ports whenconfiguring MDS FC_IDs The port_ID value is the third byte of theFC_ID
Interoperability limitationsRefer to the EMC Support Matrix (ESM) and the EMC Networked Storage Topology Guide for modes of operation and caveats
NASBThe NASB feature requires that the backup application load the tapedrive with a compatible tape cartridge prior to configuring NASB inthe backup VSAN
Reserved VSAN Range and Isolated VSAN Range GuidelinesOn an NPV switch with a trunking configuration on any interface or ona regular switch where the feature fport_channel_trunk command hasbeen issued to enable the F PortChannel feature follow theseconfiguration guidelines for reserved VSANs and the isolated VSAN
bull If trunk mode is on for any of the interfaces or NP PortChannelis up the reserved VSANs are 3040 to 4078 and they are notavailable for user configuration
bull The Exchange Virtual Fabric Protocol (EVFP) isolated VSAN is4079 and it is not available for user configuration
bull VSAN 4079 will be impacted by an upgrade to NX-OS Release42(3) depending on whether or not VSAN 4079 was createdprior to the upgrade See theldquoUpgrading Effect on VSAN 4079rdquoon page 17
The following VSAN IDs are assigned in the Fibre Channel Framingand Signaling (FC-FS) interface standard
VF_ID Value Value Description
00h Do not use as a Virtual FabricIdentifier
001h EFFh Available as a Virtual FabricIdentifier
F00h FEEh Reserved
32 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Symmetrix VMax limitationsAt the time of this writing the following features are not supportedfor use with the Symmetrix VMax
FCIP Write Acceleration
The NX-OS IOA functionality is only supported with the Q2 SREnginuity release 5874229182 or higher
For the most up to date status please refer to the current revision ofthese Release Notes on httpPowerlinkemccom and the EMCSupport Matrix available through E-Lab Interoperability Navigator (ELN) athttpelabnavigatorEMCcom
Storage Applications on the MSM-184The MDS 9000 184-Port Multiservice Module (MSM-184) does notsupport multiple concurrent storage applications Only oneapplication can run on the MSM-184 at a time
Downgrading with fport-channel-trunk enabledIf you are running MDS NX-OS Release 42(x) or higher with thefport-channel-trunk feature enabled and you downgrade to anyNX-OS 41(1x) release the installer performs a nondisruptivedowngrade even though the fport-channel-trunk feature is notsupported in NX-OS 41(1x) releases
As a result the switch is in an inconsistent state and the ports maynot function properly
FEFh Control VF-ID (see FibreChannel Link Services (FC-LS)and Fibre Channel SwitchFabric Generation 4 (FC-SW-4)standards)
FF0h FFEh Vendor specific
FFFh Do not use as a Virtual FabricIdentifier
FEFh = 4079
33
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
If you are in this state a workaround is to reboot the switch followingthe upgrade
LDAP AuthenticationThere is currently a limitation in the LDAP server configuration CLIthat prevents the use of an OU with spaces in the name Normallythese OU names could be surrounded by quotation marks howeverquotation marks are not supported by the ldap-server command
MDS-9148 limitationsThe Cisco MDS 9148 Multilayer Fabric Switch does not support thefollowing NX-OS features
Medium and Long range 4GB Agilent
IVR
Remote Span
Translative loop support
FCC - no generation quench reaction only
FC-Redirect
In addition the following features have these limits
VSANS - 31 maximum
SPAN - 1 session maximum
Technical notesThe following sections provide further information on technicalnotes
EMC Email Home for Cisco MDS switchesInstallation and Trouble shooting instructions can be found in thedocumentation located at the EMC Customer Service Internalwebsite
httpwwwcsisusemccomcsweb2esnesnhomehtmConnectrix20MDS20900020Family
34 EMC Connectrix MDS 9000 NX-OS Release Notes
Technical notes
Customers requiring installation of this solution should contact theirEMC Customer Engineer to assist with the installation and providethe documentation
Supported iSCSI sessionsThe current iSCSI session environment supported on the MDS is
300 sessions per port
1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no
InitialR2T=yes
Upgrading Cisco SAN-OSThere are several methods available for upgrading SAN-OS SoftwareEMC personnel are strongly recommended that all upgrades be doneby the Automated One-Step Upgrade using the install all
command EMC personnel should refer to the Connectrix MDS 9000Family Software Image Upgrade Instructions for a complete list ofprerequisites and instructions for performing the upgrade Thisdocument along with tftp software is available on the GlobalServices website at httpwwwcsisusEMCcom under ApplicationDownload Area ESN Product Information Connectrix MDS 9000Family
The Software Upgrade Wizard is an option for upgrades While theinstall all is the preferred method the Software Install Wizard canalso be used
Supported configuration parametersFor the most up-to-date information refer to the EMC Support Matrixavailable through E-Lab Interoperability Navigator athttpelabnavigatoremccom for the latest information onsupported configurations
35
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
Supported zoning parametersRefer to the EMC Networked Storage Topology Guide for the mostup-to-date information on supported zoning parameters
At the time these notes were published the following parameterswere supported
20 VSANs 5 Hops 2000 Unique members per physical infrastructure 1000 Zonesets per physical infrastructure 2000 Zones per physical infrastructure 1 FCIP tunnel
Supported IVR parameters IVR zone members 1000 IVR zones 1000 IVR zone sets 32 VSANS 20 IVR enabled switches 64
An RPQ can be submitted for any configurations that exceed thislimit
Managing zone changes in multiswitch fabricsZoning changes may be made through Fabric Manager or CLI Whenaccessing Fabric Manager or CLI the user does so from the point ofview of one switch That is Fabric Manager and CLI are accessed byentering the IP address of one switch in the fabric
When zoning changes are made the applicable VSAN and zone setdata is propagated to the rest of the switches in the fabric via the ISLs
When zoning changes are made to a VSAN the zone set data ispropagated to the rest of the switches in the fabric via the ISLs Bydefault only the active zone set information is relayed to all switchesin the VSAN If the user accesses the Fabric Manager and CLI fromanother switch in the fabric the new VSAN and zone set informationwill not be viewable To view the active and inactive zone set on theother switches in the fabric the user must log in to the CLI and issuea command from the EXEC prompt
36 EMC Connectrix MDS 9000 NX-OS Release Notes
Documentation
Example The following is an example of copying VSAN 1 through 20 zoningdata
CiscoMDS_name zone copy active full vsan 1-20
CiscoMDS_name conf t
Enter configuration commands one per line End with CNTL Z
CiscoMDS_name(config) zoneset distribute full vsan 1-20
CiscoMDS_name(config)
Note This command needs to be issued on all switches in the fabric one timeonly
This is a nondisruptive command After issuing the commands theuser will now see the active and inactive zone sets for the specifiedVSANs on any switch that is chosen from which to manage the fabric
After a zoning change is made save the running configuration to thestartup configuration
DocumentationSend documentation comments to mdsfeedback-doccom
Product DocumentationAs of NX-OS Release 42(1a) software configuration information isavailable in new feature-specific configuration guides for thefollowing information
System management
Interfaces
Fabric
Quality of service
Security
IP services
High availability and redundancy
37
Software media organization and files
EMC Connectrix MDS 9000 NX-OS Release Notes
The information in these new guides previously existed in the CiscoMDS 9000 Family CLI Configuration Guide That configuration guideremains available on Ciscocom and should be used for all softwarereleases prior to NX-OS Release 42(1a) Configuration guidesaddress the features introduced in or available in a particular releaseSelect and view the configuration guide that pertains to the softwareinstalled in your switch
In addition Fabric Manager information has been removed from theMDS NX-OS Release Notes (this document) and placed intostandalone Fabric Manager Release Notes that support both CiscoMDS 9000 Family switches and Cisco Nexus 5000 Series switchesThe Cisco Fabric Manager Release Notes are available onhttpPowerlinkemccom and from the following website
httpwwwciscocomenUSpartnerproductsps10495prod_release_notes_listhtml
Technical supportThese release notes complement a Cisco documentation set EachCisco document refers to where to get help However for any itemssupplied by EMC see ldquoTroubleshooting and getting helprdquo onpage 38
Software media organization and filesFor information on related software environment and systemrequirements refer to the EMC Support Matrix on EMC Powerlink at
httpPowerlinkEMCcom
InstallationFor hardware installation information refer to the Cisco MDS HWInstallation Guides available at Ciscocom
For EMC-specific installation information refer to ldquoEnvironment andsystem requirementsrdquo on page 5 in this document
38 EMC Connectrix MDS 9000 NX-OS Release Notes
Troubleshooting and getting help
Troubleshooting and getting helpEMC support product and licensing information can be obtained asfollows
Product information mdash For documentation release notes softwareupdates or for information about EMC products licensing andservice go to the EMC Powerlink website (registration required) at
httpPowerlinkEMCcom
Technical support mdash For technical support go to EMC CustomerService on Powerlink To open a service request through Powerlinkyou must have a valid support agreement Please contact your EMCsales representative for details about obtaining a valid supportagreement or to answer any questions about your account
Copyright copy 2011 EMC Corporation All rights reserved
EMC believes the information in this publication is accurate as of its publication date The information issubject to change without notice
THE INFORMATION IN THIS PUBLICATION IS PROVIDED ldquoAS ISrdquo EMC CORPORATION MAKES NOREPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION INTHIS PUBLICATION AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OFMERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Use copying and distribution of any EMC software described in this publication requires an applicablesoftware license
For the most up-to-date regulatory document for your product line go to the Technical Documentation andAdvisories section on EMC Powerlink
For the most up-to-date listing of EMC product names see EMC Corporation Trademarks on EMCcom
All other trademarks used herein are the property of their respective owners
32 EMC Connectrix MDS 9000 NX-OS Release Notes
Known problems and limitations
Symmetrix VMax limitationsAt the time of this writing the following features are not supportedfor use with the Symmetrix VMax
FCIP Write Acceleration
The NX-OS IOA functionality is only supported with the Q2 SREnginuity release 5874229182 or higher
For the most up to date status please refer to the current revision ofthese Release Notes on httpPowerlinkemccom and the EMCSupport Matrix available through E-Lab Interoperability Navigator (ELN) athttpelabnavigatorEMCcom
Storage Applications on the MSM-184The MDS 9000 184-Port Multiservice Module (MSM-184) does notsupport multiple concurrent storage applications Only oneapplication can run on the MSM-184 at a time
Downgrading with fport-channel-trunk enabledIf you are running MDS NX-OS Release 42(x) or higher with thefport-channel-trunk feature enabled and you downgrade to anyNX-OS 41(1x) release the installer performs a nondisruptivedowngrade even though the fport-channel-trunk feature is notsupported in NX-OS 41(1x) releases
As a result the switch is in an inconsistent state and the ports maynot function properly
FEFh Control VF-ID (see FibreChannel Link Services (FC-LS)and Fibre Channel SwitchFabric Generation 4 (FC-SW-4)standards)
FF0h FFEh Vendor specific
FFFh Do not use as a Virtual FabricIdentifier
FEFh = 4079
33
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
If you are in this state a workaround is to reboot the switch followingthe upgrade
LDAP AuthenticationThere is currently a limitation in the LDAP server configuration CLIthat prevents the use of an OU with spaces in the name Normallythese OU names could be surrounded by quotation marks howeverquotation marks are not supported by the ldap-server command
MDS-9148 limitationsThe Cisco MDS 9148 Multilayer Fabric Switch does not support thefollowing NX-OS features
Medium and Long range 4GB Agilent
IVR
Remote Span
Translative loop support
FCC - no generation quench reaction only
FC-Redirect
In addition the following features have these limits
VSANS - 31 maximum
SPAN - 1 session maximum
Technical notesThe following sections provide further information on technicalnotes
EMC Email Home for Cisco MDS switchesInstallation and Trouble shooting instructions can be found in thedocumentation located at the EMC Customer Service Internalwebsite
httpwwwcsisusemccomcsweb2esnesnhomehtmConnectrix20MDS20900020Family
34 EMC Connectrix MDS 9000 NX-OS Release Notes
Technical notes
Customers requiring installation of this solution should contact theirEMC Customer Engineer to assist with the installation and providethe documentation
Supported iSCSI sessionsThe current iSCSI session environment supported on the MDS is
300 sessions per port
1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no
InitialR2T=yes
Upgrading Cisco SAN-OSThere are several methods available for upgrading SAN-OS SoftwareEMC personnel are strongly recommended that all upgrades be doneby the Automated One-Step Upgrade using the install all
command EMC personnel should refer to the Connectrix MDS 9000Family Software Image Upgrade Instructions for a complete list ofprerequisites and instructions for performing the upgrade Thisdocument along with tftp software is available on the GlobalServices website at httpwwwcsisusEMCcom under ApplicationDownload Area ESN Product Information Connectrix MDS 9000Family
The Software Upgrade Wizard is an option for upgrades While theinstall all is the preferred method the Software Install Wizard canalso be used
Supported configuration parametersFor the most up-to-date information refer to the EMC Support Matrixavailable through E-Lab Interoperability Navigator athttpelabnavigatoremccom for the latest information onsupported configurations
35
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
Supported zoning parametersRefer to the EMC Networked Storage Topology Guide for the mostup-to-date information on supported zoning parameters
At the time these notes were published the following parameterswere supported
20 VSANs 5 Hops 2000 Unique members per physical infrastructure 1000 Zonesets per physical infrastructure 2000 Zones per physical infrastructure 1 FCIP tunnel
Supported IVR parameters IVR zone members 1000 IVR zones 1000 IVR zone sets 32 VSANS 20 IVR enabled switches 64
An RPQ can be submitted for any configurations that exceed thislimit
Managing zone changes in multiswitch fabricsZoning changes may be made through Fabric Manager or CLI Whenaccessing Fabric Manager or CLI the user does so from the point ofview of one switch That is Fabric Manager and CLI are accessed byentering the IP address of one switch in the fabric
When zoning changes are made the applicable VSAN and zone setdata is propagated to the rest of the switches in the fabric via the ISLs
When zoning changes are made to a VSAN the zone set data ispropagated to the rest of the switches in the fabric via the ISLs Bydefault only the active zone set information is relayed to all switchesin the VSAN If the user accesses the Fabric Manager and CLI fromanother switch in the fabric the new VSAN and zone set informationwill not be viewable To view the active and inactive zone set on theother switches in the fabric the user must log in to the CLI and issuea command from the EXEC prompt
36 EMC Connectrix MDS 9000 NX-OS Release Notes
Documentation
Example The following is an example of copying VSAN 1 through 20 zoningdata
CiscoMDS_name zone copy active full vsan 1-20
CiscoMDS_name conf t
Enter configuration commands one per line End with CNTL Z
CiscoMDS_name(config) zoneset distribute full vsan 1-20
CiscoMDS_name(config)
Note This command needs to be issued on all switches in the fabric one timeonly
This is a nondisruptive command After issuing the commands theuser will now see the active and inactive zone sets for the specifiedVSANs on any switch that is chosen from which to manage the fabric
After a zoning change is made save the running configuration to thestartup configuration
DocumentationSend documentation comments to mdsfeedback-doccom
Product DocumentationAs of NX-OS Release 42(1a) software configuration information isavailable in new feature-specific configuration guides for thefollowing information
System management
Interfaces
Fabric
Quality of service
Security
IP services
High availability and redundancy
37
Software media organization and files
EMC Connectrix MDS 9000 NX-OS Release Notes
The information in these new guides previously existed in the CiscoMDS 9000 Family CLI Configuration Guide That configuration guideremains available on Ciscocom and should be used for all softwarereleases prior to NX-OS Release 42(1a) Configuration guidesaddress the features introduced in or available in a particular releaseSelect and view the configuration guide that pertains to the softwareinstalled in your switch
In addition Fabric Manager information has been removed from theMDS NX-OS Release Notes (this document) and placed intostandalone Fabric Manager Release Notes that support both CiscoMDS 9000 Family switches and Cisco Nexus 5000 Series switchesThe Cisco Fabric Manager Release Notes are available onhttpPowerlinkemccom and from the following website
httpwwwciscocomenUSpartnerproductsps10495prod_release_notes_listhtml
Technical supportThese release notes complement a Cisco documentation set EachCisco document refers to where to get help However for any itemssupplied by EMC see ldquoTroubleshooting and getting helprdquo onpage 38
Software media organization and filesFor information on related software environment and systemrequirements refer to the EMC Support Matrix on EMC Powerlink at
httpPowerlinkEMCcom
InstallationFor hardware installation information refer to the Cisco MDS HWInstallation Guides available at Ciscocom
For EMC-specific installation information refer to ldquoEnvironment andsystem requirementsrdquo on page 5 in this document
38 EMC Connectrix MDS 9000 NX-OS Release Notes
Troubleshooting and getting help
Troubleshooting and getting helpEMC support product and licensing information can be obtained asfollows
Product information mdash For documentation release notes softwareupdates or for information about EMC products licensing andservice go to the EMC Powerlink website (registration required) at
httpPowerlinkEMCcom
Technical support mdash For technical support go to EMC CustomerService on Powerlink To open a service request through Powerlinkyou must have a valid support agreement Please contact your EMCsales representative for details about obtaining a valid supportagreement or to answer any questions about your account
Copyright copy 2011 EMC Corporation All rights reserved
EMC believes the information in this publication is accurate as of its publication date The information issubject to change without notice
THE INFORMATION IN THIS PUBLICATION IS PROVIDED ldquoAS ISrdquo EMC CORPORATION MAKES NOREPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION INTHIS PUBLICATION AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OFMERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Use copying and distribution of any EMC software described in this publication requires an applicablesoftware license
For the most up-to-date regulatory document for your product line go to the Technical Documentation andAdvisories section on EMC Powerlink
For the most up-to-date listing of EMC product names see EMC Corporation Trademarks on EMCcom
All other trademarks used herein are the property of their respective owners
33
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
If you are in this state a workaround is to reboot the switch followingthe upgrade
LDAP AuthenticationThere is currently a limitation in the LDAP server configuration CLIthat prevents the use of an OU with spaces in the name Normallythese OU names could be surrounded by quotation marks howeverquotation marks are not supported by the ldap-server command
MDS-9148 limitationsThe Cisco MDS 9148 Multilayer Fabric Switch does not support thefollowing NX-OS features
Medium and Long range 4GB Agilent
IVR
Remote Span
Translative loop support
FCC - no generation quench reaction only
FC-Redirect
In addition the following features have these limits
VSANS - 31 maximum
SPAN - 1 session maximum
Technical notesThe following sections provide further information on technicalnotes
EMC Email Home for Cisco MDS switchesInstallation and Trouble shooting instructions can be found in thedocumentation located at the EMC Customer Service Internalwebsite
httpwwwcsisusemccomcsweb2esnesnhomehtmConnectrix20MDS20900020Family
34 EMC Connectrix MDS 9000 NX-OS Release Notes
Technical notes
Customers requiring installation of this solution should contact theirEMC Customer Engineer to assist with the installation and providethe documentation
Supported iSCSI sessionsThe current iSCSI session environment supported on the MDS is
300 sessions per port
1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no
InitialR2T=yes
Upgrading Cisco SAN-OSThere are several methods available for upgrading SAN-OS SoftwareEMC personnel are strongly recommended that all upgrades be doneby the Automated One-Step Upgrade using the install all
command EMC personnel should refer to the Connectrix MDS 9000Family Software Image Upgrade Instructions for a complete list ofprerequisites and instructions for performing the upgrade Thisdocument along with tftp software is available on the GlobalServices website at httpwwwcsisusEMCcom under ApplicationDownload Area ESN Product Information Connectrix MDS 9000Family
The Software Upgrade Wizard is an option for upgrades While theinstall all is the preferred method the Software Install Wizard canalso be used
Supported configuration parametersFor the most up-to-date information refer to the EMC Support Matrixavailable through E-Lab Interoperability Navigator athttpelabnavigatoremccom for the latest information onsupported configurations
35
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
Supported zoning parametersRefer to the EMC Networked Storage Topology Guide for the mostup-to-date information on supported zoning parameters
At the time these notes were published the following parameterswere supported
20 VSANs 5 Hops 2000 Unique members per physical infrastructure 1000 Zonesets per physical infrastructure 2000 Zones per physical infrastructure 1 FCIP tunnel
Supported IVR parameters IVR zone members 1000 IVR zones 1000 IVR zone sets 32 VSANS 20 IVR enabled switches 64
An RPQ can be submitted for any configurations that exceed thislimit
Managing zone changes in multiswitch fabricsZoning changes may be made through Fabric Manager or CLI Whenaccessing Fabric Manager or CLI the user does so from the point ofview of one switch That is Fabric Manager and CLI are accessed byentering the IP address of one switch in the fabric
When zoning changes are made the applicable VSAN and zone setdata is propagated to the rest of the switches in the fabric via the ISLs
When zoning changes are made to a VSAN the zone set data ispropagated to the rest of the switches in the fabric via the ISLs Bydefault only the active zone set information is relayed to all switchesin the VSAN If the user accesses the Fabric Manager and CLI fromanother switch in the fabric the new VSAN and zone set informationwill not be viewable To view the active and inactive zone set on theother switches in the fabric the user must log in to the CLI and issuea command from the EXEC prompt
36 EMC Connectrix MDS 9000 NX-OS Release Notes
Documentation
Example The following is an example of copying VSAN 1 through 20 zoningdata
CiscoMDS_name zone copy active full vsan 1-20
CiscoMDS_name conf t
Enter configuration commands one per line End with CNTL Z
CiscoMDS_name(config) zoneset distribute full vsan 1-20
CiscoMDS_name(config)
Note This command needs to be issued on all switches in the fabric one timeonly
This is a nondisruptive command After issuing the commands theuser will now see the active and inactive zone sets for the specifiedVSANs on any switch that is chosen from which to manage the fabric
After a zoning change is made save the running configuration to thestartup configuration
DocumentationSend documentation comments to mdsfeedback-doccom
Product DocumentationAs of NX-OS Release 42(1a) software configuration information isavailable in new feature-specific configuration guides for thefollowing information
System management
Interfaces
Fabric
Quality of service
Security
IP services
High availability and redundancy
37
Software media organization and files
EMC Connectrix MDS 9000 NX-OS Release Notes
The information in these new guides previously existed in the CiscoMDS 9000 Family CLI Configuration Guide That configuration guideremains available on Ciscocom and should be used for all softwarereleases prior to NX-OS Release 42(1a) Configuration guidesaddress the features introduced in or available in a particular releaseSelect and view the configuration guide that pertains to the softwareinstalled in your switch
In addition Fabric Manager information has been removed from theMDS NX-OS Release Notes (this document) and placed intostandalone Fabric Manager Release Notes that support both CiscoMDS 9000 Family switches and Cisco Nexus 5000 Series switchesThe Cisco Fabric Manager Release Notes are available onhttpPowerlinkemccom and from the following website
httpwwwciscocomenUSpartnerproductsps10495prod_release_notes_listhtml
Technical supportThese release notes complement a Cisco documentation set EachCisco document refers to where to get help However for any itemssupplied by EMC see ldquoTroubleshooting and getting helprdquo onpage 38
Software media organization and filesFor information on related software environment and systemrequirements refer to the EMC Support Matrix on EMC Powerlink at
httpPowerlinkEMCcom
InstallationFor hardware installation information refer to the Cisco MDS HWInstallation Guides available at Ciscocom
For EMC-specific installation information refer to ldquoEnvironment andsystem requirementsrdquo on page 5 in this document
38 EMC Connectrix MDS 9000 NX-OS Release Notes
Troubleshooting and getting help
Troubleshooting and getting helpEMC support product and licensing information can be obtained asfollows
Product information mdash For documentation release notes softwareupdates or for information about EMC products licensing andservice go to the EMC Powerlink website (registration required) at
httpPowerlinkEMCcom
Technical support mdash For technical support go to EMC CustomerService on Powerlink To open a service request through Powerlinkyou must have a valid support agreement Please contact your EMCsales representative for details about obtaining a valid supportagreement or to answer any questions about your account
Copyright copy 2011 EMC Corporation All rights reserved
EMC believes the information in this publication is accurate as of its publication date The information issubject to change without notice
THE INFORMATION IN THIS PUBLICATION IS PROVIDED ldquoAS ISrdquo EMC CORPORATION MAKES NOREPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION INTHIS PUBLICATION AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OFMERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Use copying and distribution of any EMC software described in this publication requires an applicablesoftware license
For the most up-to-date regulatory document for your product line go to the Technical Documentation andAdvisories section on EMC Powerlink
For the most up-to-date listing of EMC product names see EMC Corporation Trademarks on EMCcom
All other trademarks used herein are the property of their respective owners
34 EMC Connectrix MDS 9000 NX-OS Release Notes
Technical notes
Customers requiring installation of this solution should contact theirEMC Customer Engineer to assist with the installation and providethe documentation
Supported iSCSI sessionsThe current iSCSI session environment supported on the MDS is
300 sessions per port
1800 sessions total overall
The following iSCSI parameters must be set on all iSCSI initiatorsconnecting to the MDS (both pass through and proxy initiator mode)
ImmediateData=no
InitialR2T=yes
Upgrading Cisco SAN-OSThere are several methods available for upgrading SAN-OS SoftwareEMC personnel are strongly recommended that all upgrades be doneby the Automated One-Step Upgrade using the install all
command EMC personnel should refer to the Connectrix MDS 9000Family Software Image Upgrade Instructions for a complete list ofprerequisites and instructions for performing the upgrade Thisdocument along with tftp software is available on the GlobalServices website at httpwwwcsisusEMCcom under ApplicationDownload Area ESN Product Information Connectrix MDS 9000Family
The Software Upgrade Wizard is an option for upgrades While theinstall all is the preferred method the Software Install Wizard canalso be used
Supported configuration parametersFor the most up-to-date information refer to the EMC Support Matrixavailable through E-Lab Interoperability Navigator athttpelabnavigatoremccom for the latest information onsupported configurations
35
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
Supported zoning parametersRefer to the EMC Networked Storage Topology Guide for the mostup-to-date information on supported zoning parameters
At the time these notes were published the following parameterswere supported
20 VSANs 5 Hops 2000 Unique members per physical infrastructure 1000 Zonesets per physical infrastructure 2000 Zones per physical infrastructure 1 FCIP tunnel
Supported IVR parameters IVR zone members 1000 IVR zones 1000 IVR zone sets 32 VSANS 20 IVR enabled switches 64
An RPQ can be submitted for any configurations that exceed thislimit
Managing zone changes in multiswitch fabricsZoning changes may be made through Fabric Manager or CLI Whenaccessing Fabric Manager or CLI the user does so from the point ofview of one switch That is Fabric Manager and CLI are accessed byentering the IP address of one switch in the fabric
When zoning changes are made the applicable VSAN and zone setdata is propagated to the rest of the switches in the fabric via the ISLs
When zoning changes are made to a VSAN the zone set data ispropagated to the rest of the switches in the fabric via the ISLs Bydefault only the active zone set information is relayed to all switchesin the VSAN If the user accesses the Fabric Manager and CLI fromanother switch in the fabric the new VSAN and zone set informationwill not be viewable To view the active and inactive zone set on theother switches in the fabric the user must log in to the CLI and issuea command from the EXEC prompt
36 EMC Connectrix MDS 9000 NX-OS Release Notes
Documentation
Example The following is an example of copying VSAN 1 through 20 zoningdata
CiscoMDS_name zone copy active full vsan 1-20
CiscoMDS_name conf t
Enter configuration commands one per line End with CNTL Z
CiscoMDS_name(config) zoneset distribute full vsan 1-20
CiscoMDS_name(config)
Note This command needs to be issued on all switches in the fabric one timeonly
This is a nondisruptive command After issuing the commands theuser will now see the active and inactive zone sets for the specifiedVSANs on any switch that is chosen from which to manage the fabric
After a zoning change is made save the running configuration to thestartup configuration
DocumentationSend documentation comments to mdsfeedback-doccom
Product DocumentationAs of NX-OS Release 42(1a) software configuration information isavailable in new feature-specific configuration guides for thefollowing information
System management
Interfaces
Fabric
Quality of service
Security
IP services
High availability and redundancy
37
Software media organization and files
EMC Connectrix MDS 9000 NX-OS Release Notes
The information in these new guides previously existed in the CiscoMDS 9000 Family CLI Configuration Guide That configuration guideremains available on Ciscocom and should be used for all softwarereleases prior to NX-OS Release 42(1a) Configuration guidesaddress the features introduced in or available in a particular releaseSelect and view the configuration guide that pertains to the softwareinstalled in your switch
In addition Fabric Manager information has been removed from theMDS NX-OS Release Notes (this document) and placed intostandalone Fabric Manager Release Notes that support both CiscoMDS 9000 Family switches and Cisco Nexus 5000 Series switchesThe Cisco Fabric Manager Release Notes are available onhttpPowerlinkemccom and from the following website
httpwwwciscocomenUSpartnerproductsps10495prod_release_notes_listhtml
Technical supportThese release notes complement a Cisco documentation set EachCisco document refers to where to get help However for any itemssupplied by EMC see ldquoTroubleshooting and getting helprdquo onpage 38
Software media organization and filesFor information on related software environment and systemrequirements refer to the EMC Support Matrix on EMC Powerlink at
httpPowerlinkEMCcom
InstallationFor hardware installation information refer to the Cisco MDS HWInstallation Guides available at Ciscocom
For EMC-specific installation information refer to ldquoEnvironment andsystem requirementsrdquo on page 5 in this document
38 EMC Connectrix MDS 9000 NX-OS Release Notes
Troubleshooting and getting help
Troubleshooting and getting helpEMC support product and licensing information can be obtained asfollows
Product information mdash For documentation release notes softwareupdates or for information about EMC products licensing andservice go to the EMC Powerlink website (registration required) at
httpPowerlinkEMCcom
Technical support mdash For technical support go to EMC CustomerService on Powerlink To open a service request through Powerlinkyou must have a valid support agreement Please contact your EMCsales representative for details about obtaining a valid supportagreement or to answer any questions about your account
Copyright copy 2011 EMC Corporation All rights reserved
EMC believes the information in this publication is accurate as of its publication date The information issubject to change without notice
THE INFORMATION IN THIS PUBLICATION IS PROVIDED ldquoAS ISrdquo EMC CORPORATION MAKES NOREPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION INTHIS PUBLICATION AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OFMERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Use copying and distribution of any EMC software described in this publication requires an applicablesoftware license
For the most up-to-date regulatory document for your product line go to the Technical Documentation andAdvisories section on EMC Powerlink
For the most up-to-date listing of EMC product names see EMC Corporation Trademarks on EMCcom
All other trademarks used herein are the property of their respective owners
35
Technical notes
EMC Connectrix MDS 9000 NX-OS Release Notes
Supported zoning parametersRefer to the EMC Networked Storage Topology Guide for the mostup-to-date information on supported zoning parameters
At the time these notes were published the following parameterswere supported
20 VSANs 5 Hops 2000 Unique members per physical infrastructure 1000 Zonesets per physical infrastructure 2000 Zones per physical infrastructure 1 FCIP tunnel
Supported IVR parameters IVR zone members 1000 IVR zones 1000 IVR zone sets 32 VSANS 20 IVR enabled switches 64
An RPQ can be submitted for any configurations that exceed thislimit
Managing zone changes in multiswitch fabricsZoning changes may be made through Fabric Manager or CLI Whenaccessing Fabric Manager or CLI the user does so from the point ofview of one switch That is Fabric Manager and CLI are accessed byentering the IP address of one switch in the fabric
When zoning changes are made the applicable VSAN and zone setdata is propagated to the rest of the switches in the fabric via the ISLs
When zoning changes are made to a VSAN the zone set data ispropagated to the rest of the switches in the fabric via the ISLs Bydefault only the active zone set information is relayed to all switchesin the VSAN If the user accesses the Fabric Manager and CLI fromanother switch in the fabric the new VSAN and zone set informationwill not be viewable To view the active and inactive zone set on theother switches in the fabric the user must log in to the CLI and issuea command from the EXEC prompt
36 EMC Connectrix MDS 9000 NX-OS Release Notes
Documentation
Example The following is an example of copying VSAN 1 through 20 zoningdata
CiscoMDS_name zone copy active full vsan 1-20
CiscoMDS_name conf t
Enter configuration commands one per line End with CNTL Z
CiscoMDS_name(config) zoneset distribute full vsan 1-20
CiscoMDS_name(config)
Note This command needs to be issued on all switches in the fabric one timeonly
This is a nondisruptive command After issuing the commands theuser will now see the active and inactive zone sets for the specifiedVSANs on any switch that is chosen from which to manage the fabric
After a zoning change is made save the running configuration to thestartup configuration
DocumentationSend documentation comments to mdsfeedback-doccom
Product DocumentationAs of NX-OS Release 42(1a) software configuration information isavailable in new feature-specific configuration guides for thefollowing information
System management
Interfaces
Fabric
Quality of service
Security
IP services
High availability and redundancy
37
Software media organization and files
EMC Connectrix MDS 9000 NX-OS Release Notes
The information in these new guides previously existed in the CiscoMDS 9000 Family CLI Configuration Guide That configuration guideremains available on Ciscocom and should be used for all softwarereleases prior to NX-OS Release 42(1a) Configuration guidesaddress the features introduced in or available in a particular releaseSelect and view the configuration guide that pertains to the softwareinstalled in your switch
In addition Fabric Manager information has been removed from theMDS NX-OS Release Notes (this document) and placed intostandalone Fabric Manager Release Notes that support both CiscoMDS 9000 Family switches and Cisco Nexus 5000 Series switchesThe Cisco Fabric Manager Release Notes are available onhttpPowerlinkemccom and from the following website
httpwwwciscocomenUSpartnerproductsps10495prod_release_notes_listhtml
Technical supportThese release notes complement a Cisco documentation set EachCisco document refers to where to get help However for any itemssupplied by EMC see ldquoTroubleshooting and getting helprdquo onpage 38
Software media organization and filesFor information on related software environment and systemrequirements refer to the EMC Support Matrix on EMC Powerlink at
httpPowerlinkEMCcom
InstallationFor hardware installation information refer to the Cisco MDS HWInstallation Guides available at Ciscocom
For EMC-specific installation information refer to ldquoEnvironment andsystem requirementsrdquo on page 5 in this document
38 EMC Connectrix MDS 9000 NX-OS Release Notes
Troubleshooting and getting help
Troubleshooting and getting helpEMC support product and licensing information can be obtained asfollows
Product information mdash For documentation release notes softwareupdates or for information about EMC products licensing andservice go to the EMC Powerlink website (registration required) at
httpPowerlinkEMCcom
Technical support mdash For technical support go to EMC CustomerService on Powerlink To open a service request through Powerlinkyou must have a valid support agreement Please contact your EMCsales representative for details about obtaining a valid supportagreement or to answer any questions about your account
Copyright copy 2011 EMC Corporation All rights reserved
EMC believes the information in this publication is accurate as of its publication date The information issubject to change without notice
THE INFORMATION IN THIS PUBLICATION IS PROVIDED ldquoAS ISrdquo EMC CORPORATION MAKES NOREPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION INTHIS PUBLICATION AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OFMERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Use copying and distribution of any EMC software described in this publication requires an applicablesoftware license
For the most up-to-date regulatory document for your product line go to the Technical Documentation andAdvisories section on EMC Powerlink
For the most up-to-date listing of EMC product names see EMC Corporation Trademarks on EMCcom
All other trademarks used herein are the property of their respective owners
36 EMC Connectrix MDS 9000 NX-OS Release Notes
Documentation
Example The following is an example of copying VSAN 1 through 20 zoningdata
CiscoMDS_name zone copy active full vsan 1-20
CiscoMDS_name conf t
Enter configuration commands one per line End with CNTL Z
CiscoMDS_name(config) zoneset distribute full vsan 1-20
CiscoMDS_name(config)
Note This command needs to be issued on all switches in the fabric one timeonly
This is a nondisruptive command After issuing the commands theuser will now see the active and inactive zone sets for the specifiedVSANs on any switch that is chosen from which to manage the fabric
After a zoning change is made save the running configuration to thestartup configuration
DocumentationSend documentation comments to mdsfeedback-doccom
Product DocumentationAs of NX-OS Release 42(1a) software configuration information isavailable in new feature-specific configuration guides for thefollowing information
System management
Interfaces
Fabric
Quality of service
Security
IP services
High availability and redundancy
37
Software media organization and files
EMC Connectrix MDS 9000 NX-OS Release Notes
The information in these new guides previously existed in the CiscoMDS 9000 Family CLI Configuration Guide That configuration guideremains available on Ciscocom and should be used for all softwarereleases prior to NX-OS Release 42(1a) Configuration guidesaddress the features introduced in or available in a particular releaseSelect and view the configuration guide that pertains to the softwareinstalled in your switch
In addition Fabric Manager information has been removed from theMDS NX-OS Release Notes (this document) and placed intostandalone Fabric Manager Release Notes that support both CiscoMDS 9000 Family switches and Cisco Nexus 5000 Series switchesThe Cisco Fabric Manager Release Notes are available onhttpPowerlinkemccom and from the following website
httpwwwciscocomenUSpartnerproductsps10495prod_release_notes_listhtml
Technical supportThese release notes complement a Cisco documentation set EachCisco document refers to where to get help However for any itemssupplied by EMC see ldquoTroubleshooting and getting helprdquo onpage 38
Software media organization and filesFor information on related software environment and systemrequirements refer to the EMC Support Matrix on EMC Powerlink at
httpPowerlinkEMCcom
InstallationFor hardware installation information refer to the Cisco MDS HWInstallation Guides available at Ciscocom
For EMC-specific installation information refer to ldquoEnvironment andsystem requirementsrdquo on page 5 in this document
38 EMC Connectrix MDS 9000 NX-OS Release Notes
Troubleshooting and getting help
Troubleshooting and getting helpEMC support product and licensing information can be obtained asfollows
Product information mdash For documentation release notes softwareupdates or for information about EMC products licensing andservice go to the EMC Powerlink website (registration required) at
httpPowerlinkEMCcom
Technical support mdash For technical support go to EMC CustomerService on Powerlink To open a service request through Powerlinkyou must have a valid support agreement Please contact your EMCsales representative for details about obtaining a valid supportagreement or to answer any questions about your account
Copyright copy 2011 EMC Corporation All rights reserved
EMC believes the information in this publication is accurate as of its publication date The information issubject to change without notice
THE INFORMATION IN THIS PUBLICATION IS PROVIDED ldquoAS ISrdquo EMC CORPORATION MAKES NOREPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION INTHIS PUBLICATION AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OFMERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Use copying and distribution of any EMC software described in this publication requires an applicablesoftware license
For the most up-to-date regulatory document for your product line go to the Technical Documentation andAdvisories section on EMC Powerlink
For the most up-to-date listing of EMC product names see EMC Corporation Trademarks on EMCcom
All other trademarks used herein are the property of their respective owners
37
Software media organization and files
EMC Connectrix MDS 9000 NX-OS Release Notes
The information in these new guides previously existed in the CiscoMDS 9000 Family CLI Configuration Guide That configuration guideremains available on Ciscocom and should be used for all softwarereleases prior to NX-OS Release 42(1a) Configuration guidesaddress the features introduced in or available in a particular releaseSelect and view the configuration guide that pertains to the softwareinstalled in your switch
In addition Fabric Manager information has been removed from theMDS NX-OS Release Notes (this document) and placed intostandalone Fabric Manager Release Notes that support both CiscoMDS 9000 Family switches and Cisco Nexus 5000 Series switchesThe Cisco Fabric Manager Release Notes are available onhttpPowerlinkemccom and from the following website
httpwwwciscocomenUSpartnerproductsps10495prod_release_notes_listhtml
Technical supportThese release notes complement a Cisco documentation set EachCisco document refers to where to get help However for any itemssupplied by EMC see ldquoTroubleshooting and getting helprdquo onpage 38
Software media organization and filesFor information on related software environment and systemrequirements refer to the EMC Support Matrix on EMC Powerlink at
httpPowerlinkEMCcom
InstallationFor hardware installation information refer to the Cisco MDS HWInstallation Guides available at Ciscocom
For EMC-specific installation information refer to ldquoEnvironment andsystem requirementsrdquo on page 5 in this document
38 EMC Connectrix MDS 9000 NX-OS Release Notes
Troubleshooting and getting help
Troubleshooting and getting helpEMC support product and licensing information can be obtained asfollows
Product information mdash For documentation release notes softwareupdates or for information about EMC products licensing andservice go to the EMC Powerlink website (registration required) at
httpPowerlinkEMCcom
Technical support mdash For technical support go to EMC CustomerService on Powerlink To open a service request through Powerlinkyou must have a valid support agreement Please contact your EMCsales representative for details about obtaining a valid supportagreement or to answer any questions about your account
Copyright copy 2011 EMC Corporation All rights reserved
EMC believes the information in this publication is accurate as of its publication date The information issubject to change without notice
THE INFORMATION IN THIS PUBLICATION IS PROVIDED ldquoAS ISrdquo EMC CORPORATION MAKES NOREPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION INTHIS PUBLICATION AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OFMERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Use copying and distribution of any EMC software described in this publication requires an applicablesoftware license
For the most up-to-date regulatory document for your product line go to the Technical Documentation andAdvisories section on EMC Powerlink
For the most up-to-date listing of EMC product names see EMC Corporation Trademarks on EMCcom
All other trademarks used herein are the property of their respective owners
38 EMC Connectrix MDS 9000 NX-OS Release Notes
Troubleshooting and getting help
Troubleshooting and getting helpEMC support product and licensing information can be obtained asfollows
Product information mdash For documentation release notes softwareupdates or for information about EMC products licensing andservice go to the EMC Powerlink website (registration required) at
httpPowerlinkEMCcom
Technical support mdash For technical support go to EMC CustomerService on Powerlink To open a service request through Powerlinkyou must have a valid support agreement Please contact your EMCsales representative for details about obtaining a valid supportagreement or to answer any questions about your account
Copyright copy 2011 EMC Corporation All rights reserved
EMC believes the information in this publication is accurate as of its publication date The information issubject to change without notice
THE INFORMATION IN THIS PUBLICATION IS PROVIDED ldquoAS ISrdquo EMC CORPORATION MAKES NOREPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION INTHIS PUBLICATION AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OFMERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Use copying and distribution of any EMC software described in this publication requires an applicablesoftware license
For the most up-to-date regulatory document for your product line go to the Technical Documentation andAdvisories section on EMC Powerlink
For the most up-to-date listing of EMC product names see EMC Corporation Trademarks on EMCcom
All other trademarks used herein are the property of their respective owners
