 Feedback
|
Table Of Contents
Cisco MDS 9000 Family Release Notes
for Cisco MDS SAN-OS Release 3.2(1a)Determining the Software Version
Selecting the Correct Software Image for an MDS 9100 Series Switch
Selecting the Correct Software Image for an MDS 9200 Series Switch
Selecting the Correct Software Image for an MDS 9500 Series Switch
Migrating from Supervisor-1 Modules to Supervisor-2 Modules
Configuring Generation 2 Switching Modules
Upgrading Your Cisco MDS SAN-OS Software Image
Performing a Nondisruptive Software Upgrade on Generation 1 Modules
Upgrading Your Version of Cisco Fabric Manager
FICON Supported Releases and Upgrade Paths
Upgrading an MDS 9216 Switch with iSCSI Enabled
Reconfiguring SSM Ports Before Upgrading to SAN-OS Release 3.2(1a)
Upgrading the SSI Image on Your SSM
Upgrading a Switch with Insufficient Space for Two Images on the Bootflash
Upgrading a Cisco MDS 9124 Switch
Performing a Disruptive Upgrade on a Single Supervisor MDS Family Switch
Downgrading Your Cisco MDS SAN-OS Software Image
General Downgrading Guidelines
Downgrading the SSI Image on Your SSM
New Features in Cisco MDS SAN-OS Release 3.2(1a)
Cisco MDS 9134 Multilayer Fabric Switch
Cisco MDS 92221 Multiservice Switch
Cisco MDS 9000 18/4-Port Multiservice Module (MSM-18/4)
Cisco MDS 9000 18/4-Port Multiservice Module FIPS (MSFM-18/4)
Digital Diagnostic Enhancements
Intelligent Fabric Application Enhancements
TACACS+ Password Expiry Notification
Server LUN Map Discovery Commands
In-service Software Upgrades for the Cisco MDS 9222i Switch
New CLI Command to Recover the Modflash Partition
Cisco Fabric Manager Enhancements
Threshold Configuration Flexibility
SAN Device Virtualization Scalability
Upgrading to Recover Loss of Performance Manager Data
Compatibility of Fabric Manager and Data Mobility Manager
Cisco MDS 9134 Multilayer Fabric Switch
Using NPIV on Cisco Fabric Switches
Cisco MDS 9222i Multiservice Modular Switch and Cisco MDS 9000 18/4-Port Multiservice Module
Using SAN Device Virtualization on Cisco Fabric Switches
Virtual Router Redundancy Protocol (VRRP) Interfaces
QoS on an MDS 48-port Fibre Channel Module
Maximum Number of Zones Supported in Interop Mode 4
Configuring Default Settings for the Default Zone
PPRC Not Supported with FCIP Write Acceleration
Using IVR In a Fabric With Mixed Code Versions
Regulatory Compliance and Safety Information
Installation and Configuration Note
Obtaining Documentation, Obtaining Support, and Security Guidelines
Cisco MDS 9000 Family Release Notes
for Cisco MDS SAN-OS Release 3.2(1a)
Release Date: October 6, 2007
Part Number: OL-14116-02 O0
This document describes the caveats and limitations for switches in the Cisco MDS 9000 Family. Use this document in conjunction with documents listed in the "Related Documentation" section.
Note
Release notes are sometimes updated with new information on restrictions and caveats. Refer to the following website for the most recent version of the Cisco MDS 9000 Family Release Notes: http://www.cisco.com/en/US/products/hw/ps4159/ps4358/prod_release_notes_list.html
Table 1 shows the on-line change history for this document.
Table 1 Online History Change
A0
10/06/2007
Created release notes.
B0
10/18/2007
Added DDTS CSCsj72662.
C0
10/22/2007
Changed the status of DDTS CSCsh31236 to Resolved.
D0
10/23/2007
Added DDTS CSCsk93834.
Removed DDTS CSCsh31236.
Added a description of a new CLI Command to recover the modflash partition to the "New Features in Cisco MDS SAN-OS Release 3.2(1a)" section.
E0
04/23/2008
Added DDTS CSCsk48149.
F0
04/30/2008
Added DDTS CSCso63465.
G0
07/09/2008
Added Upgrading to Recover Loss of Performance Manager Data.
Added NPV and NPIV Requirements.
H0
11/13/2008
Added the "Performing a Nondisruptive Software Upgrade on Generation 1 Modules" section.
I0
11/18/2008
Added DDTS CSCso72230.
J0
01/15/2009
Removed iSNS from the "Changes in Existing Features" section.
K0
04/14/2009
Updated DDTS CSCsk49634.
L0
04/29/2009
Added the "FICON Supported Releases and Upgrade Paths" section.
Revised "FICON Downgrade Paths" section.
Added the"Compatibility of Fabric Manager and Data Mobility Manager" limitation.
M0
08/28/2009
Removed the DS-SFP-GE-T from Table 1 because it is supported on switches running SAN-OS Release 3.3(1) or later.
N0
07/29/2010
Added the "PPRC Not Supported with FCIP Write Acceleration" limitation.
Added the "Using IVR In a Fabric With Mixed Code Versions" limitation.
O0
11/03/2010
Added the Supervisor-2A module to Table 2.
Contents
This document includes the following sections:
•
•
•
•
Introduction
The Cisco MDS 9000 Family of Multilayer Directors and Fabric Switches provides industry-leading availability, scalability, security, and management, allowing you to deploy high performance storage-area networks with lowest total cost of ownership. Layering a rich set of intelligent features onto a high performance, protocol agnostic switch fabric, the Cisco MDS 9000 Family addresses the stringent requirements of large data center storage environments: uncompromising high availability, security, scalability, ease of management, and seamless integration of new technologies.
The Cisco MDS 9000 Family SAN-OS is the underlying system software that powers the Cisco MDS 9500 Series, 9200 Series, and 9100 Series multilayer switches. The Cisco SAN-OS provides intelligent networking features, such as multiprotocol and multitransport integration, virtual SANs (VSANs), advanced security, sophisticated debug analysis tools, and unified SAN management.
Components Supported
Table 2 lists the SAN-OS software part number and hardware components supported by the Cisco MDS 9000 Family.
Note
Table 2 Cisco MDS 9000 Family Supported Software and Hardware Components
Software
M95S2K9-3.2.1A
MDS 9500 Supervisor/Fabric-2, SAN-OS software.
MDS 9500 Series only
M95S1K9-3.2.1A
MDS 9500 Supervisor/Fabric-I, SAN-OS software.
MDS 9500 Series only
M92S2K9-3.2.1A
MDS 9222 Supervisor/Fabric-2, SAN-OS software.
MDS 9200 Series only
M92S1K9-3.2.1A
MDS 9216 Supervisor/Fabric-I, SAN-OS software.
MDS 9200 Series only
M91S2K9-3.2.1A
MDS 9100 Supervisor/Fabric-2, SAN-OS software.
MDS 9100 Series only
M91S1K9-3.2.1A
MDS 9100 Supervisor/Fabric-I, SAN-OS software
MDS 9100 Series only
License
M9500ENT1K9
Enterprise package.
MDS 9500 Series
M9200ENT1K9
Enterprise package.
MDS 9200 Series
M9100ENT1K9
Enterprise package.
MDS 9100 Series
M9500FIC1K9
Mainframe package.
MDS 9500 Series
M9200FIC1K9
Mainframe package.
MDS 9200 Series
M9100FIC1K9
Mainframe package.
MDS 9100 Series
M9100FIC1EK9
FICON license.
MDS 9100 Series
M9500FMS1K9
Fabric Manager Server package.
MDS 9500 Series
M9200FMS1K9
Fabric Manager Server package.
MDS 9200 Series
M9100FMS1K9
Fabric Manager Server package.
MDS 9100 Series
M9500EXT1K9
SAN Extension over IP package for IPS-8 module.
MDS 9500 Series
M9200EXT1K9
SAN Extension over IP package for IPS-8 module.
MDS 9200 Series
M9500EXT14K9
SAN Extension over IP package for IPS-4 module.
MDS 9500 Series
M9200EXT14K9
SAN Extension over IP package for IPS-4 module.
MDS 9200 Series
M9500EXT12K9
SAN Extension over IP package for MPS-14/2 module.
MDS 9500 Series
M9200EXT12K9
SAN Extension over IP package for MPS-14/2 module.
MDS 9200 Series
M9500EXT1AK9
SAN Extension over IP package for MSM-18/4 module or MSFM-18/4 FIPS module.
MDS 9500 Series
M9200EXT1AK9
SAN Extension over IP package for MSM-18/4 module or MSFM-18/4 FIPS module.
MDS 9200 Series
M9500SSE1K9
Storage Services Enabler package.
MDS 9500 Series with SSM
M9200SSE1K9
Storage Services Enabler package.
MDS 9200 Series with SSM
M95DMMS1K9
Data Mobility Manager (DMM)
MDS 9500 Series with SSM
M92DMMS1K9
Data Mobility Manager (DMM)
MDS 9200 Series with SSM
M95DMMTS1K9
Data Mobility Manager (DMM) for 180 days
MDS 9500 Series with SSM
M92DMMTS1K9
Data Mobility Manager (DMM) for 180 days
MDS 9200 Series with SSM
M9124PL8-4G
On-Demand Ports Activation License
MDS 9124 Switch
M9134PL8-4G
On-Demand Ports Activation License
MDS 9134 Switch
M9134PL2-10G
On-Demand Ports Activation License
MDS 9134 Switch
HP-PL12-4G
On-Demand Ports Activation License
Cisco Fabric Switch for HP c-Class BladeSystem only
IBM-PL10-4G
On-Demand Ports Activation License
Cisco Fabric Switch for IBM BladeCenter only
Chassis
DS-C9513
MDS 9513 director (13-slot modular chassis with 11 slots for switching modules, and 2 slots reserved for Supervisor 2 modules only—SFPs1 sold separately).
MDS 9513 only
DS-C9509
MDS 9509 director, base configuration (9-slot modular chassis includes 7 slots for switching modules and 2 slots for supervisor modules—SFPs sold separately).
MDS 9509 only
DS-C9506
MDS 9506 director (6-slot modular chassis includes 4 slots for switching modules and 2 slots for supervisor modules—SFPs sold separately).
MDS 9506 only
DS-C9222i-K9
MDS 9222i Multiservice Modular Switch (includes 18 4-Gbps Fibre Channel ports and 4 Gigabit Ethernet IP storage services ports, and a modular expansion slot for Cisco MDS 9000 Family Switching and Service modules.)
MDS 9222i only
DS-C9216-K9
MDS 9216 16-port semi-modular fabric switch (includes 16 1-Gbps/2-Gbps Fibre Channel ports, power supply, and expansion slot—SFPs sold separately).
MDS 9216 only
DS-C9216A-K9
MDS 9216A 16-port semi-modular fabric switch (includes 16 1-Gbps/2-Gbps Fibre Channel ports, power supply, and expansion slot—SFPs sold separately).
MDS 9216A only
DS-C9216i-K9
MDS 9216i 16-port semi-modular fabric switch (includes 14 1-Gbps/2-Gbps Fibre Channel ports, 2 Gigabit Ethernet ports, power supply, and expansion slot—SFPs sold separately).
MDS 9216i only
DS-C9140-K9
MDS 9140 fixed configuration (non-modular) fabric switch (includes 8 full rate ports and 32 host-optimized ports).
MDS 9140 only
DS-C9124-K9
MDS 9124 fixed configuration (non-modular) multilayer fabric switch (includes 8 enabled ports; an on-demand ports activation license can enable 8 additional ports, up to 24 ports).
MDS 9124 only
DS-C9134-K9
MDS 9134 fixed configuration (non-modular) multilayer fabric switch (includes 24 enabled 4-Gbps ports; an on-demand ports activation license can enable 8 additional ports, up to 32 4-Gbps ports. An additional port activation license can enable 2 10-Gbps ports.).
MDS 9134 only
DS-C9120-K9
MDS 9120 fixed configuration, non-modular, fabric switch (includes4 full rate ports and 16 host-optimized ports).
MDS 9120 only
DS-HP-FC-K9
Cisco Fabric Switch for HP c-Class BladeSystem (includes sixteen internal and eight external active ports and four 4-Gb SFPs installed, or eight internal and four external active ports and two 4-Gb SFPs installed).
Cisco Fabric Switch for HP c-Class BladeSystem only
DS-IBM-FC-K9
Cisco Fabric Switch for IBM BladeCenter (includes fourteen internal and six external ports)
Cisco Fabric Switch for IBM BladeCenter only
External crossbar module
DS-13SLT-FAB1
MDS 9513 crossbar fabric module.
MDS 9513 only
Supervisor modules
DS-X9530-SF2-K9
MDS 9500 Supervisor-2 module.
MDS 9500 Series only
DS-X9530-SF2A-K9
MDS 9500Supervisor-2A module.
DS-X9530-SF1-K9
MDS 9500 Supervisor/Fabric-I module.
Switching modules
DS-X9016
MDS 9000 16-port 1-Gbps/2-Gbps Fibre Channel module (SFPs sold separately).
MDS 9500 Series and 9200 Series
DS-X9032
MDS 9000 32-port 1-Gbps/2-Gbps Fibre Channel module (SFPs sold separately).
DS-X9112
MDS 9000 12-port 4-Gbps Fibre Channel module (SFPs sold separately).
MDS 9500 Series and 9200 Series, except for the MDS 9216
DS-X9124
MDS 9000 24-port 4-Gbps Fibre Channel module (SFPs sold separately).
MDS 9500 Series and 9200 Series, except for the MDS 9216
DS-X9148
MDS 9000 48-port 4-Gbps Fibre Channel module (SFPs sold separately).
MDS 9500 Series and 9200 Series, except for the MDS 9216
DS-X9704
MDS 9000 4-port 10-Gbps Fibre Channel module (SFPs sold separately)
MDS 9500 Series and 9200 Series, except for the MDS 9216
Services modules
DS-X9308-SMIP
8-port Gigabit Ethernet IP Storage services module.
MDS 9500 Series and 9200 Series
DS-X9304-SMIP
4-port Gigabit Ethernet IP Storage services module.
DS-X9032-SSM
MDS 9000 32-port 1-Gbps/2-Gbps Fibre Channel Storage Services Module (SSM).
DS-X9302-14K9
14-port Fibre Channel/2-port Gigabit Ethernet Multiprotocol Services (MPS-14/2) module.
DS-X9304-18K9
18-port Fibre Channel/4-port Gigabit Ethernet Multiservice (MSM-18/4) module.
DS-X9304-18FK9
18-port Fibre Channel/4-port Gigabit Ethernet Multiservice FIPS (MSFM-18/4) module.
Optics
DS-X2-FC10G-SR
X2/SC optics, 10-Gbps Fibre Channel for Short Reach.
MDS 9500 Series and 9200 Series, except for the MDS 9216
DS-X2-FC10G-LR
X2/SC optics, 10-Gbps Fibre Channel for Long Reach.
DS-X2-FC10G-ER
X2/SC optics, 10-Gbps Fibre Channel for Extended Reach (40 km).
DS-X2-E10G-SR
X2/SC optics, 10-Gbps Ethernet for Short Reach
DS-X2-FC10G_CX4
X2/CX-4 optics, 10-Gbps Fibre Channel, copper
LC-type fiber-optic SFP
DS-SFP-FC-2G-SW
2-Gbps/1-Gbps Fibre Channel—short wavelength SFP.
MDS 9000 Family
DS-SFP-FC-2G-LW
2-Gbps/1-Gbps Fibre Channel—long wavelength SFP.
DS-SFP-FCGE-SW
1-Gbps Ethernet and 1-Gbps/2-Gbps Fibre Channel—short wavelength SFP.
DS-SFP-FCGE-LW
1-Gbps Ethernet and 1-Gbps/2-Gbps Fibre Channel—long wavelength SFP.
DS-SFP-FC4G-SW
4-Gbps/2-Gbps/1-Gbps Fibre Channel—short wavelength SFP for DS-X91xx switching modules.
MDS 9500 Series and 9200 Series, except for the MDS 9216
DS-SFP-FC4G-MR
4-Gbps/2-Gbps/1-Gbps Fibre Channel—long wavelength SFP for DS-X91xx switching modules only. Supports distances up to 4 km.
DS-SFP-FC4G-LW
4-Gbps/2-Gbps/1-Gbps Fibre Channel—long wavelength SFP for DS-X91xx switching modules only. Supports distances up to 10 km.
CWDM2
DS-CWDM-xxxx
Gigabit Ethernet and 1-Gbps/2-Gbps/4-Gbps Fibre Channel SFP LC interface xxxx nm, where xxxx = 1470, 1490, 1510, 1530, 1550, 1570, 1590, or 1610 nm.
MDS 9000 Family
DS-CWDM-MUX-4
Add/drop multiplexer for four CWDM wavelengths.
DS-CWDM-MUX-8
Add/drop multiplexer for eight CWDM wavelengths.
DS-CWDMCHASSIS
Two slot chassis for CWDM add/drop multiplexers.
Power supplies
DS-CAC-6000W
6000-W AC power supply.
MDS 9513 only
DS-CAC-2500W
2500-W AC power supply.
MDS 9509 only
DS-CDC-2500W
2500-W DC power supply.
DS-CAC-3000W
3000-W AC power supply.
DS-CAC-4000W-US
4000-W AC power supply for US (cable attached).
DS-CAC-4000W-INT
4000-W AC power supply international (cable attached).
DS-CAC-1900W
1900-W AC power supply.
MDS 9506 only
DS-CDC-1900W
1900-W DC power supply.
DS-CAC-845W
845-W AC power supply.
MDS 9200 Series only
DS-CAC-300W
300-W3 AC power supply.
MDS 9100 Series only
CompactFlash
MEM-MDS-FLD51M
MDS 9500 supervisor CompactFlash disk, 512 MB.
MDS 9500 Series only
Port analyzer adapter
DS-PAA-2, DS-PAA
A standalone Fibre Channel-to-Ethernet adapter that allows for simple, transparent analysis of Fibre Channel traffic in a switched fabric.
MDS 9000 Family
CD-ROM
M90FM-CD-321=
MDS 9000 Management Software and Documentation CD-ROM, spare.
MDS 9000 Family
1 SFP = small form-factor pluggable
2 CWDM = coarse wavelength division multiplexing
3 W = Watt
Software Download Process
Use the software download procedure to upgrade to a later version, or downgrade to an earlier version, of an operating system. This section describes the software download process for the Cisco MDS SAN-OS and includes the following topics:
•
•
•
•
Determining the Software Version
To determine the version of Cisco MDS SAN-OS software currently running on a Cisco MDS 9000 Family switch using the CLI, log in to the switch and enter the show version EXEC command.
To determine the version of Cisco MDS SAN-OS software currently running on a Cisco MDS 9000 Family switch using the Fabric Manager, view the Switches tab in the Information pane, locate the switch using the IP address, logical name, or WWN, and check its version in the Release column.
Note
Downloading Software
The Cisco MDS SAN-OS software is designed for mission-critical high availability environments. To realize the benefits of nondisruptive upgrades on the Cisco MDS 9500 Directors, we highly recommend that you install dual supervisor modules.
To download the latest Cisco MDS SAN-OS software, access the Software Center at this URL:
http://www.cisco.com/public/sw-center
See the following sections in this release note for details on how you can nondisruptively upgrade your Cisco MDS 9000 switch. Issuing the install all command from the CLI, or using Fabric Manager to perform the downgrade, enables the compatibility check. The check indicates if the upgrade can happen nondisruptively or disruptively depending on the current configuration of your switch and the reason.
Compatibility check is done:Module 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 resetAt a minimum, you need to disable the default device alias distribution feature using the no device-alias distribute command in global configuration mode. The show incompatibility system bootflash:1.3(x)_filename command determines which additional features need to be disabled.
Note
Note
Selecting the Correct Software Image for an MDS 9100 Series Switch
The system and kickstart image that you use for an MDS 9100 series switch depends on which switch you use, as shown in Table 3.
Selecting the Correct Software Image for an MDS 9200 Series Switch
The system and kickstart image that you use for an MDS 9200 series switch depends on which switch you use, as shown in Table 4.
Table 4 Software Images for MDS 9200 Series Switches
MDS 9222i
Filename begins with m9200-s2ek9
MDS 9216A or MDS 9216i
Filename begins with m9200-s1ek9
Selecting the Correct Software Image for an MDS 9500 Series Switch
The system and kickstart image that you use for an MDS 9500 Series switch depends on whether the switch is based on a Supervisor-1 module or a Supervisor-2 module, as shown in Table 5.
Use the show module command to display the type of supervisor module in the switch.
For a Supervisor-1 module, the output might look like this:
switch# show moduleMod Ports Module-Type Model Status--- ----- -------------------------------- ------------------ ------------......5 0 Supervisor/Fabric-1 DS-X9530-SF1-K9 active*6 0 Supervisor/Fabric-1 DS-X9530-SF1-K9 ha-standbyFor a Supervisor-2 module, the output might look like this:
switch# show moduleMod Ports Module-Type Model Status--- ----- -------------------------------- ------------------ ------------......7 0 Supervisor/Fabric-2 DS-X9530-SF2-K9 active *8 0 Supervisor/Fabric-2 DS-X9530-SF2-K9 ha-standbyMigrating from Supervisor-1 Modules to Supervisor-2 Modules
As of Cisco MDS SAN-OS Release 3.0(1), the Cisco MDS 9509 and 9506 Directors support both Supervisor-1 and Supervisor-2 modules. Supervisor-1 and Supervisor-2 modules cannot be installed in the same switch, except during migration. Both the active and standby supervisor modules must be of the same type, either Supervisor-1 or Supervisor-2 modules. For Cisco MDS 9513 Directors, both supervisor modules must be Supervisor-2 modules.
Caution
Note
To migrate from a Supervisor-1 module to a Supervisor-2 module, refer to the step-by-step instructions in the Cisco MDS 9000 Family CLI Configuration Guide.
Configuring Generation 2 Switching Modules
The Cisco MDS 9500 Multilayer Directors are designed to operate with any combination of Cisco MDS 9000 Generation 1 and Generation 2 modules. However, there are limitations to consider when combining the various modules and supervisors in the Cisco MDS 9500 Series platform chassis. The references listed in this section provide specific information about configurations that combine different modules and supervisors.
For information on configuring Generation 2 switching modules, refer to:
http://www.cisco.com/en/US/products/ps5989/products_configuration_guide_chapter09186a0080664c6b.html
For information on port index availability, refer to:
http://www.cisco.com/en/US/products/ps5990/products_installation_guide_chapter09186a0080419599.html
For information on Cisco MDS 9000 hardware and software compatibility, refer to:
http://www.cisco.com/en/US/products/ps5989/products_device_support_table09186a00805037ee.html
Upgrading Your Cisco MDS SAN-OS Software Image
This section lists the guidelines recommended for upgrading your Cisco MDS SAN-OS software image and contains the following sections:
•
•
•
•
•
•
•
•
Performing a Nondisruptive Software Upgrade on Generation 1 Modules
Generation 1 modules may reload during a nondisruptive SAN-OS software upgrade because of the CompactFlash being unable to partition for the new code. If that happens, the installer aborts and reloads the module.
This issue affects the following modules:
•
•
•
•
This issue might be seen during an upgrade from Cisco SAN-OS Release 3.0(x), 3.1(x) or 3.2(x). It has been addressed for upgrades from SAN-OS Release 3.3(1) or higher. Therefore, you will not be impacted by this issue if you are running SAN-OS Release 3.3(1) when you upgrade to a higher SAN-OS release.
When this problem occurs, the module will automatically reload and may cause the Install All to stop, which will cause the upgrade to be unsuccessful. Error messages similar to the following may be displayed:
Install has failed. Return code 0x40930020 (Non-disruptive upgrade of a module failed).Please identify the cause of the failure, and try 'install all' again.Module 2: Non-disruptive upgrading.-- FAIL. Return code 0x40690009 (Error in downloading image for image upgrade).To avoid this kind of unplanned disruption, follow the methods for identifying and correcting this issue described in Cisco Field Notice 63099, before proceeding with the SAN-OS upgrade. This Field notice can be found under the Support, Products page for Cisco MDS9500 Series Multilayer Directors selection.
The caveat associated with this issue is CSCsm62295.
Upgrading Your Version of Cisco Fabric Manager
As of Cisco SAN-OS Release 3.2(1), Cisco Fabric Manager is no longer packaged with a Cisco MDS 9000
Family switch. It is included on the CD-ROM that ships with the switch. You can install Fabric Manager from the CD-ROM or from files that you download. For a complete description of the changes in Fabric Manager, see the "Cisco Fabric Manager Enhancements" section.
Installing Cisco Fabric Manager is a multi-step process that involves installing a database, as well as Fabric Manager. The complete installation instructions are provided in the "Installation of Cisco MDS SAN-OS and Fabric Manager" section in the Cisco MDS 9000 Family Fabric Manager Configuration Guide, and are available on-screen once you launch the Fabric Manager installer from the CD-ROM.
The following section presents the flow of the installation process at a high level. Review these guidelines before you begin the installation process.
1.
•
•
•
•
–
–
•
•
•
•
Note
•
•
•
•
•
•
•
•
•
2.
If you are upgrading Cisco Fabric Manager in Cisco SAN-OS Releases 3.1(2b) and later, be aware that data is migrated from the Hypersonic HSQL database to either the PostgreSQL database or Oracle Database 10g Express during the installation. Data is also migrated from Oracle Database 10g Express to Oracle Database 10g Express. If you migrate the database from Oracle to Oracle, the schema is updated.3.
If you are upgrading Fabric Manager in a Cisco SAN-OS Release prior to 3.1(2b), be aware that data is migrated from the Hypersonic HSQL database to either the PostgreSQL database or the Oracle Database 10g Express during the installation. The Fabric Manager Installer installs the PostgreSQL database on Windows. If you want to install the PostgreSQL database on Solaris or Linux, or if you want to install the Oracle Database 10g Express database, follow the instructions in the "Installation of Cisco MDS SAN-OS and Fabric Manager" section in the Cisco MDS 9000 Family Fabric Manager Configuration Guide.
Note
4.
If you want to use the Oracle Database 10g Express, you must install the database and create a user name and password before continuing with the Fabric Manager installation. We recommend the Oracle Database 10g Express option for all users who are running Performance Manager on large fabrics (1000 or more end devices).
If you want to install the PostgreSQL database, you must disable any security software you are running as PostgreSQL may not install certain folders or users. You must also log in as a Superuser before you start the installation.
5.
http://cisco.com/cgi-bin/tablebuild.pl/mds-fm
To install Fabric Manager on Solaris, follow these steps:
Step 1
Step 2
Step 3
Step 4
java -Xmx256m -jar m9000-fm-3.2.1a.jar
Step 5
To install Fabric Manager on Windows, follow these steps:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
To install Device Manager on your workstation, follow these steps:
Step 1
Step 2
Step 3
Step 4
Note
General Upgrading Guidelines
Use the following guidelines when upgrading to Cisco MDS SAN-OS Release 3.2(1a):
•
•
•
•
•
–
–
–
–
–
Use Table 6 to determine your nondisruptive upgrade path to Cisco SAN-OS Release 3.2(1a). Find the image release number you are currently using in the Current column of the table and use the path recommended.
Note
FICON Supported Releases and Upgrade Paths
Cisco MDS SAN-OS Release 3.2(1a) does not support FICON.
Table 7 lists the SAN-OS and NX-OS releases that support FICON. Refer to the specific release notes for FICON upgrade path information.
Table 7 FICON Supported Releases
NX-OS
Release 4.1(1c)
SAN-OS
Release 3.3(1c)
Release 3.2(2c)
Release 3.0(3b)
Release 3.0(3)
Release 3.0(2)
Release 2.0(2b)
Upgrading an MDS 9216 Switch with iSCSI Enabled
Following a software upgrade to Cisco SAN-OS Release 3.2(1a) on a Cisco MDS 9216, 9216A, or 9216i Switch, you need to enable iSCSI on all modules where iSCSI interfaces were present before the upgrade. Use the iscsi enable module slot-number command to enable iSCSI, then issue the copy running-config startup-config command to have the configuration take effect.
Upgrading with IVR Enabled
An Inter-Switch Link (ISL) flap resulting in fabric segmentation or a merge during or after an upgrade from Cisco MDS SAN-OS Release 2.0(x) to a later image where IVR is enabled might be disruptive. Some possible scenarios include the following:
•
•
•
If this problem occurs, syslogs indicate a failure and the flapped ISL could remain in a down state because of a domain overlap.
This issue was resolved in Cisco SAN-OS Release 2.1(2b); therefore, you must upgrade to Release 2.1(2b) before upgrading to Release 3.2(1a). An upgrade from Cisco SAN-OS Releases 2.1(1a), 2.1(1b), or 2.1(2a) to Release 2.1(2b) when IVR is enabled requires that you follow the procedure below, and then follow the upgrade guidelines listed in the "Upgrading Your Version of Cisco Fabric Manager" section. If you have VSANs in interop mode 2 or 3, you must issue an IVR refresh for those VSANs.
To upgrade from Cisco SAN-OS Releases 2.1(1a), 2.1(1b), or 2.1(2a) to Release 2.1(2b) for all other VSANs with IVR enabled, follow these steps:
Step 1
Note
Step 2
Note
Step 3
2005 Aug 31 21:52:04 switch %FCDOMAIN-2-EPORT_ISOLATED:%$VSAN 2005%$ Isolation of interfaceport-channel 52 (reason: unknown failure)2005 Aug 31 21:52:04 switch %FCDOMAIN-2-EPORT_ISOLATED: %$VSAN 2005%$Isolation of interface port-channel 51(reason: domain ID assignment failure)Step 4
switch(config)# vsan databaseswitch(config-vsan-db)# vsan vsan-id suspendswitch(config-vsan-db)# no vsan vsan-id suspendStep 5
Step 6
Step 7
Note
Reconfiguring SSM Ports Before Upgrading to SAN-OS Release 3.2(1a)
Starting with Cisco MDS SAN-OS Release 3.0(1), the SSM front panel ports can no longer be configured in auto mode, which is the default for releases prior to Release 3.0(1).
Note
For more information on upgrading SAN-OS software, see the "Upgrading Your Cisco MDS SAN-OS Software Image" section.
If the configuration is not updated before the upgrade, the installation process for the new image will automatically convert all ports configured in auto mode to Fx mode. This change in mode might cause a disruption if the port is currently operating in E mode.
To upgrade the image on your SSM without any traffic disruption, follow these steps:
Step 1
switch# show interface fc 2/1 - 32fc2/1 is upHardware is Fibre Channel, SFP is short wave laser w/o OFC (SN)Port WWN is 20:4b:00:0d:ec:09:3c:00Admin port mode is auto <-------- shows port is configured in auto modesnmp traps are enabledPort mode is F, FCID is 0xef0300 <-------- shows current port operational mode is FPort vsan is 1Speed is 2 GbpsTransmit B2B Credit is 3Step 2
a.
switch# config tswitch(config)# interface fc 2/1switch(config-if)# switchport mode fxb.
switch# config tswitch(config)# interface fc 2/5switch(config-if)# switchport mode eStep 3
a.
switch# config tswitch(config)# interface fc 2/2switch(config-if)# switchport mode fxb.
switch# config tswitch(config)# interface fc 2/2switch(config-if)# shutdownswitch# copy running-config startup-config
Upgrading the SSI Image on Your SSM
Use the following guidelines to nondisruptively upgrade the SSI image on your SSM:
•
•
–
–
–
–
–
Caution
Upgrading a Switch with Insufficient Space for Two Images on the Bootflash
To upgrade the SAN-OS image on a Cisco MDS 9000 Family switch requires enough space on the internal CompactFlash (also referred to as bootflash) to accommodate both the old software image and the new software image.
As of Cisco MDS SAN-OS Release 3.1(1), on MDS switches with a 256-MB CompactFlash, it is possible in some scenarios that a user might be unable to fit two images on the bootflash. This lack of space on the bootflash might cause the upgrade process to fail because new images are always copied onto the bootflash during an upgrade.
The following MDS switches are affected by this issue:
•
•
•
To work around an image upgrade failure caused by a lack of space on the bootflash, follow these steps:
Step 1
Step 2
switch# delete bootflash:m9200-ek9-mz.3.0.3.bin
Note
switch# delete bootflash://sup-standby/m9500-sf1ek9-mz.3.0.3.binStep 3
Step 4
Step 5
Upgrading a Cisco MDS 9124 Switch
If you are upgrading from Cisco MDS SAN-OS Release 3.1(1) to Cisco SAN-OS Release 3.2(1a) on a Cisco MDS 9124 Switch, follow these guidelines:
•
•
•
•
•
•
Performing a Disruptive Upgrade on a Single Supervisor MDS Family Switch
Cisco MDS SAN-OS software upgrades are disruptive on the following single supervisor Cisco MDS Family switches:
•
•
•
If you are performing an upgrade on one of those switches, you should follow the nondisruptive upgrade path shown in Table 6, even though the upgrade is disruptive. Following the nondisruptive upgrade path ensures that the binary startup configuration remains intact.
If you do not follow the upgrade path, (for example, you upgrade directly from SAN-OS Release 2.1(2b) to SAN-OS Release 3.2(1a)), the binary startup configuration is deleted because it is not compatible with the new image, and the ASCII startup configuration file is applied when the switch comes up with the new upgraded image. When the ASCII startup configuration file is applied, there may be errors. Because of this, we recommend that you follow the nondisruptive upgrade path.
Downgrading Your Cisco MDS SAN-OS Software Image
This section lists the guidelines recommended for downgrading your Cisco MDS SAN-OS software image and contains the following sections:
•
•
General Downgrading Guidelines
Use the following guidelines to nondisruptively downgrade your Cisco MDS SAN-OS Release 3.2(1a):
•
•
•
•
•
•
–
–
–
–
–
–
–
Use Table 8 to determine your nondisruptive downgrade path from Cisco SAN-OS Release 3.2(1a). Find the SAN-OS image you want to downgrade to in the To SAN-OS Release column of the table and use the path recommended.
Note
FICON Downgrade Paths
Cisco MDS SAN-OS Release 3.2(1a) does not support FICON.
Refer to Table 7 for a list SAN-OS and NX-OS releases that support FICON. Refer to the specific release notes for FICON downgrade path information.
Downgrading the SSI Image on Your SSM
Use the following guidelines when downgrading your SSI image on your SSM.
•
•
•
•
–
–
–
New Features in Cisco MDS SAN-OS Release 3.2(1a)
Cisco MDS SAN-OS Release 3.2(1a) does not include any new features, but it provides all the new features of Cisco MDS SAN-OS Release 3.2(1). This section briefly describes those features. For detailed information about the features listed, refer to the Cisco MDS 9000 Family CLI Configuration Guide and the Cisco MDS 9000 Family Fabric Manager Configuration Guide. For information about new CLI commands associated with these features, refer to the Cisco MDS 9000 Family Command Reference. The "New and Changed Information" section in each of these books provides a detailed list of all new features and includes links to the feature description or new command.
Cisco MDS 9134 Multilayer Fabric Switch
The Cisco MDS 9134 Multilayer Fabric Switch is a 32-port 1-, 2-, and 4-Gbps autosensing Fibre
Channel and 2-port 10-Gbps switch. It features On-Demand Port Activation Licensing. By default, the first 24 ports are licensed. An additional license is required for the remaining 8 ports. The 210-Gbps ports are not licensed by default, but require a separate license.
Cisco MDS 92221 Multiservice Switch
The Cisco MDS 9222i Multiservice Modular Switch offers eighteen 4-Gbps Fibre Channel ports and four Gigabit Ethernet IP storage services ports, and a modular expansion slot to host Cisco MDS 9000 Family Switching and Services Modules.
The MDS 9222i switch provides the cryptographic engine used by Cisco Storage Media Encryption. The Cisco MDS 9222i also supports non-disruptive, in services software upgrades (ISSU).
Cisco MDS 9000 18/4-Port Multiservice Module (MSM-18/4)
The Cisco MDS 900018/4-Port Multiservice Module (MSM-18/4) offer eighteen 1-, 2-, and 4-Gbps Fibre Channel ports and four Gigabit Ethernet IP storage services ports. Its multiprotocol capabilities integrate in a single-form-factor Fibre Channel, Fibre Channel over IP (FCIP), Small Computer System Interface over IP (iSCSI), IBM Fiber Connectivity (FICON), FICON Control Unit Port (CUP) management, and switch cascading.
The Cisco MDS-18/4 Module can be used with the Cisco MDS 9200 Series of Multilayer Fabric Switches and the Cisco MDS 9500 Series of Multilayer Directors.
Note
Cisco MDS 9000 18/4-Port Multiservice Module FIPS (MSFM-18/4)
The Cisco MDS 9000 Family 18/4-Port Multiservice Federal Information Processing Standards (FIPS) Module is a FIPS 140-2 Level 3-compliant version of the Cisco MSM-18/4 Module. It provides added security to meet regulatory and industry requirements. FIPS Level 3 certification requires enhanced physical security, including a hard, opaque potting material to deter unauthorized access and tampering.
Cisco Data Mobility Manager
Cisco MDS Data Mobility Manager (DMM) for the Cisco MDS 9000 family of switches provides capabilities and features that simplify data migration and minimize service disruptions. Data migration is the process of copying data from an existing storage device to a new storage device.
Data migration is done frequently for storage array upgrades and consolidation or replacement of existing Storage. Cisco MDS 9000 Data Mobility Manger (DMM) offers a new data migration approach using a SAN switch based intelligent fabric application. Cisco DMM runs on the Cisco MDS 9000 Storage Services Module (SSM).
The primary purpose of this feature is moving data from existing storage array to a new storage array. Cisco DMM features include:
•
•
•
•
•
•
•
The Cisco DMM can be introduced without having to reconfigure or rewire the existing SAN infrastructure, and migration can enabled/disabled via software control from the Cisco Fabric Manager. Cisco DMM can be used in SANs which have only Cisco MDS 9000 switches as well as those containing a heterogeneous mixture of Cisco and other vendor switches.
N-Port Virtualization
The N-Port virtualization (NPV) feature reduces the number of Fibre Channel domain IDs in core-edge SANs. Switches operating in the NPV mode do not join a fabric, they just pass traffic between core switch links and end-devices, which eliminates the domain IDs for these edge switches. This feature is available only for Cisco MDS 9000 blade switches, the Cisco MDS 9124 Multilayer Fabric Switch, and the Cisco MDS 9134 Multilayer Fabric Switch.
The NPV mode applies to an entire switch. All end devices connected to a switch in the NPV mode must log in as N-port to use this feature. Loop attached devices are not supported. All links from the edge switches in NPV mode to the core switches are established as N-ports, not E-ports as used for a typical inter-switch links. Instead, N-Port Identifier Virtualization (NPIV) is used by the switches in NPV mode to log in multiple end-devices that share a link to the core switch.
NPV and NPIV Requirements
Table 9 shows the minimum SAN-OS release that supports NPV.
Table 10 shows the minimum SAN-OS releases that support NPIV.
Table 10 NPIV Core SAN-OS Requirements
MDS 9124, MDS 9134
Release 3.2(2c)
MDS 9200, MDS 9500
Release 3.2(1)
NPIV is not supported on the MDS 9020 switch and the MDS 9040 switch.
Note
Note
Digital Diagnostic Enhancements
The digital diagnostics capabilities for small form-factor pluggable (SFP) and 10 Gbps X2 form factor optics have been enhanced in Cisco SAN-OS release 3.2(1a):
•
•
•
Universal Serial Bus Support
The two Universal Serial Bus (USB) 2.0 compatible ports on the Cisco MDS 9500 Series Supervisor-2 modules are available for use with Cisco SAN-OS release 3.2(1a). USB flash drives connected to these ports may be used for the same functions as media in the external compact flash slot.
Intelligent Fabric Application Enhancements
Several intelligent fabric application enhancements are included in Cisco SAN-OS 3.2(1a):
•
–
–
–
•
•
FIPS Support
Federal Information Processing Standards (FIPS) l40-2 level 2 qualification has been completed for the Cisco MDS 9000 family. Customers choosing to implement FIPS level 2 security in the SAN select the FIPS mode for switch security.
The FIPS mode has been enhanced to support the Cisco MDS 9000 14/2-Port Multiprotocol Services Module.
TACACS+ Password Expiry Notification
When an end-user authenticates to a Cisco MDS 9000 switch via a TACACS+ account, this feature lets them know when a password has expired or is about to expire. If the password has expired, the end-user is prompted to change the password.
SMI-S Enhancements
Indications supported has been expanded to allow meaningful monitoring of Cisco MDS 9000 family switches. The following indications have been added:
•
•
•
•
Common Criteria
Validation of Common Criteria (CC) evaluation assurance level 3 (EAL 3) for the Cisco MDS 9000 Family members running Cisco SAN-OS 3.0(2a) shall be achieved by the release 3.2(1a) time frame.
Common Criteria is an international standard (ISO/IEC 15408) for computer security that provides assurance that the process of specifying, developing, and evaluating security features have been conducted in a rigorous manner, enabling evaluators to determine if a product meets its security requirements.
Server LUN Map Discovery Commands
Server LUN map discovery commands have been added to the CLI to discover all LUNs in a disk array that are masked for access by a particular host. You can specify a VSAN, a specific host interface, and the targets to query. The commands allow you to find LUNs that are zoned, and also LUNs that are not zoned if the disk array allows this. A Cisco MDS 9000 Storage Services Module (SSM) is required to use this feature.
New MIBS
The following new MIB is included in Cisco MDS 9000 SAN-OS release 3.2(1a):
•
In-service Software Upgrades for the Cisco MDS 9222i Switch
Cisco SAN-OS 3.2(1a) includes non-disruptive, in service software upgrades (ISSU) for the Cisco MDS 9222i switch. This feature does not apply to the Cisco MDS 9216 and 9216i fabric switches.
New CLI Command to Recover the Modflash Partition
The infrastructure of the Storage Services Module (SSM) includes a non-volatile modflash partition to store partner specific images and configuration files. Any detectable partitioning and file system errors are automatically repaired during the module initialization procedures. However, certain types of file system errors cannot be auto-detected or auto-repaired. Manual procedures might be required to recover from these types of errors. This recovery procedure is destructive, since it reformats and recreates the modflash partition. All data in the modflash partition is deleted. SSM initial provisioning procedures need to be followed for completing the recovery procedure. For these situations, a new CLI command is included in Cisco MDS SAN-OS Release 3.2(1a). The following example shows the debug mkfs modflash command.
switch# attach module slot
Attaching to module x ...
To exit type 'exit', to abort type '$.'
module-slot# debug mkfs modflashCisco Fabric Manager Enhancements
New Installation Process
Starting in release 3.2(1a), the installation process for Cisco Fabric Manager is changing to accommodate three significant enhancements:
•
•
•
–
–
Cisco Fabric Manager can now be installed from a CD-ROM or from files downloaded from the Cisco web site. To install Fabric Manager Server, you can get the software from the CD-ROM or from a Jar file, and install the PostgresSQL database and the Fabric Manager Server. To install a Fabric Manager Client, you can install the software from the Fabric Manager Server and install the Fabric Manager Client (without a database) and Cisco Device Manger.
The installation process has been broken down into a few large steps for added flexibility. A manual workflow is provided on the CD-ROM to guide the end user through installing a Java Virtual Machine (JVM) if one in not present, installing PostgresSQL database or connecting to an existing Oracle instance, and installing the Cisco Fabric Manager framework and application.
For general guidelines about the Fabric Manager installation process, see "Upgrading Your Version of Cisco Fabric Manager" section. For complete Fabric Manager installation instructions, refer to the "Installation of Cisco MDS SAN-OS and Fabric Manager" section in the Cisco MDS 9000 Family Fabric Manager Configuration Guide, or use the on-screen instructions provided with the CD-ROM.
Custom Report Enhancements
Several enhancements to the Cisco Fabric Manager custom reports are included in release 3.2(1a). These licensed Cisco FMS features include:
•
•
•
•
Analysis Reports
Cisco Fabric Manager Server release 3.2(1a) analysis reports present an additional level of information, by compiling results from running specific test programs and more complex analysis of Cisco Fabric Manager Server (FMS) database statistics.
The analysis reports in Cisco FMS release 3.2(1a) are licensed features. They include:
•
•
•
•
•
Threshold Configuration Flexibility
Cisco Fabric Manager Server allows two performance thresholds to be configured for throughput values for connections to end devices and inter-switch links (ISLs). Prior to Cisco Fabric Manager release 3.2(1a) the user interface forced users to select either a fixed percentage or auto-baseline setting for both. Now end-users can set one threshold for a link based on a fixed percentage and the other using the auto-baseline setting.
Changes in Existing Features
iSCSI
As of Cisco SAN-OS Release 3.2(1a), iSCSI should be enabled at the module level.
SAN Device Virtualization Scalability
Cisco SAN-OS Release 3.2(1a) supports 800 SAN device virtualization (SDV) virtual devices, with 4 secondary real devices mapped to each SDV virtual device in a VSAN.
Limitations and Restrictions
This section lists the limitations and restrictions for this release. This section includes the following topics:
•
•
•
•
•
•
•
•
•
•
•
•
Upgrading to Recover Loss of Performance Manager Data
Caution
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Java Web Start
When using Java Web Start, it is recommended that you do not use an HTML cache or proxy server. You can use the Java Web Start Preferences panel to view or edit the proxy configuration. To do this, launch the Application Manager, either by clicking the desktop icon (Microsoft Windows), or type ./javaws in the Java Web Start installation directory (Solaris Operating Environment and Linux), and then select Edit>Preferences.
If you fail to change these settings, you may encounter installation issues regarding a version mismatch. If this occurs, you should clear your Java cache and retry.
Data Mobility Manager
Use the following guidelines when running Cisco Data Mobility Manager:
•
•
•
•
•
Compatibility of Fabric Manager and Data Mobility Manager
Cisco Fabric Manager in any MDS NX-OS 4.1(x) release does not support Data Mobility Manager (DMM) in any SAN-OS 3.3(x) release or in any 3.2(x) release. To use the Cisco Fabric Manager GUI for DMM, both Fabric Manager and DMM must be running NX-OS or SAN-OS software from the same release series.
Cisco MDS 9134 Multilayer Fabric Switch
The Cisco MDS 9134 Multilayer Fabric Switch does not support the following Cisco MDS SAN-OS features:
•
•
•
•
In addition, the following features have these limits:
•
•
Using NPIV on Cisco Fabric Switches
In Cisco SAN-OS Release 3.2(1a), the Cisco MDS 9134 Switch, the Cisco MDS 9124 Switch, the Cisco Fabric Switch for HP c-Class BladeSystem, and the Cisco Fabric Switch for IBM BladeCenter do not support hardware-enforced zoning for devices attached to an F port that is participating in NPIV. This capability will be supported in a future release.
If NPIV is enabled on a Cisco MDS 9134 Switch, the Cisco MDS 9124 Switch, the Cisco Fabric Switch for HP c-Class BladeSystem, and the Cisco Fabric Switch for IBM BladeCenter and one of the devices connected through an F port that is participating in NPIV goes down, all devices connected through the same F port will lose connectivity. This situation can be corrected by issuing the shutdown command, followed by the no shutdown command. This issue will be resolved in a future release.
Cisco MDS 9222i Multiservice Modular Switch and Cisco MDS 9000 18/4-Port Multiservice Module
The Cisco MDS 9222i Multiservice Modular Switch and the Cisco MDS 9000 18/4-Port Multiservice Module (MSM-18/4) support one iSCSI forwarding mode that is equivalent to store-forward on the MPS-14/2 module.
The Cisco MDS 9222i and the MSM-18/4 support header-digest, but not data-digest in Cisco SAN-OS 3.2(1a).
The Cisco MDS 9222i and the MSM-18/4 do not support Ether channel.
The Cisco MDS 9222i supports only the following modules in slot 2:
•
•
•
•
•
The MSM-18/4 and MDS 9222i Switch do not support the following features:
•
•
•
•
•
•
Using SAN Device Virtualization on Cisco Fabric Switches
There must be at least one SAN device virtualization-enabled switch that is not a Cisco MDS 9124 switch, a Cisco Fabric Switch for HP c-Class BladeSystem, or a Cisco Fabric Switch for IBM BladeCenter between the server and the target that are being virtualized. In other words, SAN device virtualization does not work when initiators and primary targets are connected to the same Cisco MDS 9124 Switch or or Cisco MDS 9134 Switch or Cisco Fabric Switch for HP c-Class BladeSystem or Cisco Fabric Switch for IBM BladeCenter.
CWDM SFPs
The 2-Gbps CWDM SFPs do not have have a maximum speed set in memory and they negotiate to 4-Gbps on modules that support the higher speed. As a result, the link comes up and appears to work, but then becomes disabled and connectivity problems occur. To correct this problem, both sides of the connection must have their speed hard coded to 2-Gbps.
Fabric Manager
Observe the following limitations or restrictions for the Cisco SAN-OS Release 3.2(1a) for Fabric Manager:
•
•
•
MTU Size Limitation
The Cisco MDS 9216i switch and MPS-14/2 module do not support an MTU size greater than 8000 bytes. An attempt to set the MTU size greater than 8000 bytes will result in an error. As a workaround, reset the value of the MTU size (576 to 8000 bytes) and issue the no shutdown command on the interface for normal operation.
Reconfiguring SSM Ports
Starting with Cisco MDS SAN-OS Release 3.0(1), the SSM front panel ports can no longer be configured in auto mode, which is the default for releases prior to Release 3.1(1). For instructions about how to modify the configuration of the ports before upgrading to SAN-OS Release 3.1(3a), see the "Reconfiguring SSM Ports Before Upgrading to SAN-OS Release 3.2(1a)" section.
Virtual Router Redundancy Protocol (VRRP) Interfaces
When a switchover occurs on a switch that is the master for Virtual Router Redundancy Protocol (VRRP) interfaces, the switchover may cause a minor delay. As a result, the VRRP backup (occurring elsewhere) may assume the role of the VRRP master. As a workaround, increase the VRRP advertisement interval for these interfaces.
QoS on an MDS 48-port Fibre Channel Module
Due to possible differences in parts per million between the MAC ASICs on both sides of an ISL link, there is a potential throughput issue when running QoS over an ISL on an MDS 48-port Fibre Channel module. Specifically, the user may not see traffic throughput that follows the programmed QoS ratios. The throughput ratio on the high and/or medium priority class of service (COS) relative to the low priority COS, may not be as high as the actual programmed ratio.
If this situation occurs, you can move the ISL to a port on a different port group on one and/or both sides of the link, or move the ISL to a port on a lower-density card if you require accurate QoS ratios.
Maximum Number of Zones Supported in Interop Mode 4
In interop mode 4, the maximum number of zones that is supported in an active zone set is 2047, due to limitations in the connected vendor switch.
When IVR is used in interop mode 4, the maximum number of zones supported, including IVR zones, in the active zone set is 2047.
Configuring Default Settings for the Default Zone
Following an upgrade from any Cisco SAN-OS 2.x release to any Cisco SAN-OS 3.x release, the configuration defined by the zone default-zone permit vsan vsan-id command is applied only to the active VSAN. The configuration does not apply to unconfigured VSANs. In SAN-OS 3.x, you can apply the configuration to unconfigured VSANs by issuing the system default zone default-zone permit command.
Similarly, the zoneset distribute full vsan vsan-id command applies only to the active VSAN following an upgrade from any Cisco SAN-OS 2.x release to any Cisco SAN-OS 3.x release.
Although you can configure the default-zone settings in the setup script, these settings do not take effect for VSAN 1, because VSAN 1 already exits prior to running the setup script. To configure the default settings for the default-zone in VSAN 1, you must explicitly enter the zone default-zone permit command.
PPRC Not Supported with FCIP Write Acceleration
IBM Peer to Peer Remote Copy (PPRC) is not supported with FCIP Write Acceleration.
Using IVR In a Fabric With Mixed Code Versions
If you are using IVR and you are running SAN-OS 3.x software on your MDS switches, make sure that all IVR switches run the same code version. Otherwise, if you have a fabric with mixed code versions, the switches running the higher version may not be able to see all IVR devices. The mixed fabric can cause an inconsistent database among IVR switches, which might affect IVR behavior. For this reason, it is important that all IVR switches run the same SAN-OS version, preferably SAN-OS Release 3.3(4a), which has device update (DU) support, or later.
Caveats
This section lists the open and resolved caveats for this release. Use Table 11 to determine the status of a particular caveat. In the table, "O" indicates an open caveat and "R" indicates a resolved caveat.
Resolved Caveats
•
Symptom: During an in-service software upgrade (ISSU) to Cisco MDS SAN-OS Release 3.2(1a) on a module in an MDS 9500 series switch, the access control list (ACL) process on the module might fail. As a result, the ISSU operation fails, which causes a disruptive reload of the module.
Workaround: This issue is resolved.
•
Symptom: The CIM Server process goes into an unresponsive state after approximately two hours of scheduled probes that associate Fibre Channel ports to each switch.
Workaround: This issue is resolved.
•
Symptom: 100% CPU utilization was seen on an MDS switch. It was caused by repeated fabric logins (FLOGIs) on a particular port. This situation can occur if a host cannot log in because the allocation of the FC ID fails, and keeps re-trying using a specific pattern of Source FC IDs (S_IDs) for the FLOGI frame.
Workaround: This issue has been resolved. The interface will now be error-disabled for too many FLOGI failures.
To troubleshoot the configuration and find the reason for the FC ID allocation failure, examine the messages in the syslog. Refer to the Cisco MDS 9000 Family CLI Configuration Guide for detailed information about FLOGI, FC IDs, and FC ID allocation for HBAs.
•
Symptom: Under some circumstances, disabling the CIM Server does not terminate the CIM Server process, which causes further enabling or disabling of the CIM Server to be ineffective.
Workaround: This issue is resolved.
•
Symptom: In rare situations, data virtual target (DVT) configurations might disappear following a reload of the SSM or an upgrade to the SSI 3.1(2m) image.
Workaround: This issue is resolved.
•
Symptom: Spectra Logic tape drives require a unique area ID.
Workaround: This issue is resolved.
•
Symptom: Following an upgrade to any Cisco SAN-OS 3.0 release or to any Cisco SAN-OS 3.1 release up to 3.1(4), one or more 4-port blocks on the MDS 9000 16-port Fibre Channel switching module might become disabled. Similarly, one or more 8-port blocks might become disabled on the MDS 9000 32-port Fibre Channel switching module.
You might see output similar to the following from a show logging log command:
%IMAGE_DNLD-SLOT4-2-IMG_DNLD_STARTED: Module image download process. Please wait until completion...
%IMAGE_DNLD-SLOT4-2-IMG_DNLD_COMPLETE: Module image download process. Download successful.
%MODULE-2-MOD_DIAG_FAIL: Module 4 (serial: XYZ) reported failure on ports 4/13-4/16 (Fibre Channel) due to Q-Engine instance shutdown in device 7 (device error 0xc0703572)
%MODULE-2-MOD_SOMEPORTS_FAILED: Module 4 (serial: XYZ) reported failure on ports 4/13-4/16 (Fibre Channel) due to Q-Engine instance shutdown in device 7 (error 0xc0703572)
%PORT-5-IF_DOWN_HW_FAILURE: %$VSAN 4094%$ Interface fc4/16 is down (Hardware Failure)
%PORT-5-IF_DOWN_HW_FAILURE: %$VSAN 4094%$ Interface fc4/15 is down (Hardware Failure)
%PORT-5-IF_DOWN_HW_FAILURE: %$VSAN 1003%$ Interface fc4/14 is down (Hardware Failure)You might see output similar to the following from a show module internal exceptionlog command:
==================== EXCEPTION LOG ====================
*** Log# 0 ***
Device Id : 7
Device Name : aladdin
Device Error Code : c0703572(H)
Sys Error : Q-Engine instance shutdown
Errtype : NON-CATASTROPHIC
PhyPortLayer : Fibre Channel
Port(s) Affected : 13-16
Error Description : aladdin instance #3 shutdown: 0xc0703572 DSAP : 0 UUID : 0 Time : Mon Jul 9 22:33:18 2007
(954381 usecs 823(H) jiffies)Workaround: This issue is resolved.
•
Symptom: On an MDS switch with dual supervisor modules, the bootflash on the standby supervisor is replaced with a new bootflash. Then there is a system switchover. Then the bootflash on the new standby supervisor (which was previously the active supervisor) is replaced. The copy running-config startup-config command is used to save the configuration, but the console speed does not get saved. Instead, the console speed is reset to 9600.
Workaround: This issue is resolved.
•
Symptom: An association call from a VSAN to its logical switch returns a particular WWN, but an association call from the physical system to the virtual system does not return the same WWN, which indicates that the logical switch is not associated to the physical switch.
Workaround: This issue is resolved.
•
Symptom: Under rare circumstances, a customer running the Cisco MDS SAN-OS SANTap feature with EMC RecoverPoint might find that following a reload of the SSM module, the SSM CVT is stuck in UNKNOWN status in the RecoverPoint appliance.
Workaround: This issue is resolved.
•
Symptom: Memory leaks in the CIM Server could eventually result in the process terminating or becoming unresponsive.
Workaround: This issue is resolved.
All known resource leaks in the CIM Server have been fixed. However, some growth in the process size can still be observed when repeatedly executing queries that retrieve large amounts of data.
•
Symptom: When using the Fcanalyzer on an MDS 9513 Switch or an MDS 9124 Switch to capture packets remotely, no packets were captured.
Workaround: This issue is resolved.
•
Symptom: Following a fabric reconfiguration, if you use Fabric Manager Server to discover the fabric and you check the Accelerate Discovery check box on the Discover New Fabric dialog box, some VSANs are segmented by Fabric Manager Server. VSANs may be segmented because they are isolated or down.
Workaround: This issue is resolved.
•
Symptom: When creating a new VSAN through Fabric Manager or through a script that can create a VSAN on each switch at the same time, the same domain ID is created for each switch. This causes the newly-created VSAN to be segmented on all links.
Workaround: This issue is resolved.
•
Symptom: A fibre channel port on an MDS switching module remained out-of-service after the port was put back in service. As a result, it was not possible to configure the port.
Workaround: This issue is resolved.
•
Symptom: Following a Cisco SAN-OS software upgrade or downgrade, certain ports get stuck in link failure or in a not-connected state, even though the same SFP, cable, host, or storage device works in other ports on the same module.
Workaround: This issue is resolved.
•
Symptom: When an fcalias is added as a zone member or a zone is added to a zone set via SNMP, there is an SNMPD memory leak.
Workaround: This issue is resolved.
•
Symptom: A data path processor (DPP) might fail on an MDS switch running Cisco SAN-OS Release 3.1(2b) with an SSM running SSI Release 3.1(2m) and with the SANTap feature provisioned. The failure occurs while the DPP is processing an unexpected transfer ready message.
Workaround: This issue is resolved.
•
Symptom: IVR zone set activation in Interop mode 4 results in a failure without an appropriate status message. This issue is seen if a successful IVR zone set activation results in more than 2047 zones in Interop mode 4. In Interop mode 4, the combined number of regular and IVR zones supported is 2047. If an IVR activation attempts to activate more than 2047 zones, the activation is rejected by the zone server module. An appropriate status message is not conveyed back to IVR.
Workaround: This issue is resolved.
•
Symptom: In some cases, when Fabric Manager Server is installed on hosts with multiple network interfaces, the trap destination IP interface might be incorrectly registered, which results in traps not reaching the Fabric Manager Server.
Workaround: This issue is resolved.
•
Symptom: After switching over from the active to the standby supervisor, an EMC call home message displays that says the mgmt0 interface has failed on slot 1.
Workaround: This issue is resolved.
•
Symptom: The Java Help search engine in Cisco Fabric Manager and Device Manager does not work correctly in Cisco SAN-OS 3.1(2).
Workaround: This issue is resolved.
•
Symptom: For passwords authenticated by an AAA server, the MDS switch should inform the user when their password is about to expire.
Workaround: This is an enhancement. It is available only for CLI logins. Fabric Manager and Device currently do not support this feature.
•
Symptom: If the port license count on an MDS switch is greater than the one supported by the installed platform, ports do not automatically acquire a license. The license must be acquired manually.
Workaround: This issue is resolved.
•
Symptom: A URL for EMC is needed so that Fabric Manager can be downloaded from EMC.
Workaround: This issue is resolved.
Open Caveats
•
Symptom: If you bring up more than one link at a time between two VSANs that have overlapping domains and at least one of the switches is SDV enabled, one link will become isolated. The other links will come up, even though the domains are overlapping. In addition, the SDV virtual domains will change, causing traffic disruption on all devices associated with their old value.
Workaround: Bring up multiple links between two switches one at a time. Verify that the first link came up correctly before attempting to bring up the next link. If the first link fails to come up because of a domain ID overlap, resolve the domain conflict and then try again to bring up the links.
•
Symptom: FCIP links may fail on an MDS 9216i switch that has compression set to auto when the other end of the FCIP link is terminated by an IPS-8 module. You may see the following message in the logs:
%IPS_SB_MGR-SLOT1-3-CRYPTO_FAILURE: Heartbeat failure in encryption engine (error 0x1)
%ETHPORT-5-IF_DOWN_SOFTWARE_FAILURE: Interface GigabitEthernet1/1 is down (Port software failure)
%PORT-5-IF_DOWN_SOFTWARE_FAILURE: %$VSAN 1%$ Interface fcip99 is down (Port software failure)Workaround: If both ends of an FCIP link are not on an MPS-14/2 module, do not use mode 1 and auto.
•
Symptom: A data path processor (DPP) might fail on an MDS switch running SSI Release 3.2(1a) on the SSM. The failure occurs after several days of running traffic when a misbehaving target sends unexpected frames well after the response has already been received from the same target.
Workaround: None.
•
Symptom: If there is a request to export a domain while the same domain is being cleaned up, domain entries might not be programmed. As a result, communication between IVR devices might not occur.
Workaround: Because the the programming request was lost, the only way to retrigger the programming is to withdraw the domain and refresh IVR. Follow these steps:
1.
switch# show ivr internal dep
Internal information for DEP FSM
--------------------------------
vsan domain nh status sync_status req i/f
101 0x61(97) 1001 ALL_DONE OXID|FCID_RW 0 [ fc3/2 ]
102 0x62(98) 1002 ALL_DONE OXID|FCID_RW 0 [ fc3/5 ]
1001 0x9e(158) 101 NONE OXID|FCID_RW 0 [ fc2/16 ]
1002 0x98(152) 102 ALL_DONE OXID|FCID_RW 0 [ fc9/10]Number of DEP entries : 4
After waiting for a few minutes for IVR to stabilize, if the status column for the {vsan, domain} combination is NONE, then this problem has occurred the switch.
2.
3.
•
Symptom: In rare cases, an FCIP link might flap on a network with high latency and a consistently high loss rate (above 100ms RTT and 0.5% loss).
Workaround: None.
•
Symptom: When IVR exports a new virtual domain and multiple border switches export that virtual domain, some of the entries in the Fibre Channel name server (FCNS) database that correspond to this virtual domain may have partial entries where the port type contains a dash (-). This can then lead to a lack of IVR communication between these devices and other IVR devices.
Workaround: Use the show ivr internal vdri vsan vsan-id domain domain command to determine which border switch is exporting the virtual domain. Then on any of the border switches that is exporting the virtual domain, enter the following command for each device that has a partial FCNS entry:
switch(config)# ivr device pwwn pwwn fcns register vsan vsan-id
In this example, pWWN is the port pWWN of the device and vsan-id is the VSAN that contains the incomplete FCNS entries.
•
Symptom: Following an upgrade to Cisco MDS SAN-OS Release 3.2(1a) on a Cisco MDS 9124 switch, an interface is shown as up, but there is no FLOGI information for the port in the FLOGI database.
Workaround: Set the port mode to F.
•
Symptom: In rare instances, the following Generation 2 modules might reload:
–
–
–
–
The output of the show logging log command will have events like those shown below. In the following output, module 7 is the supervisor and module 12 is the module that reloaded.
2008 Jul 15 19:39:30 fcd95c41 %MODULE-4-MOD_WARNING: Module 7 (serial: JAE1134UR88) reported warnings on ports 7/1-7/3 (Unknown) due to BE2 Arbiter experienced an error in device 65 (device error 0xc410d613)2008 Jul 15 19:39:30 fcd95c41 %MODULE-4-MOD_WARNING: Module 8 (serial: JAE1134UOTD) reported warnings on ports 8/1-8/3 (Unknown) due to BE2 Arbiter experienced an error in device 65 (device error 0xc410d613)2008 Jul 15 19:39:35 fcd95c41 %XBAR-5-XBAR_STATUS_REPORT: Module 12 reported status for component 88 code 0x40240015.2008 Jul 15 19:39:35 fcd95c41 %MODULE-2-MOD_DIAG_FAIL: Module 12 (serial: JAE1136VU6L) reported failure on ports 12/1-12/24 (Fibre Channel) due to Fatal runtime Arb error. (DevErr is bitmap of failed modules) in device 88 (device error 0x800)"show logging onboard" will show log similar to the one below for the reloaded module:Logging time: Tue Jul 15 19:39:28 2008machine check: process swapper (0), jiffies 0x744af3a4Free pages in zone[0]:0x4a70,zone[1]:0x0,zone[2]:0x0Stack: c000dd58 c001eefc c000b2c4 c000ae98 d2060e10 c003d7a4 c00f869c c0045cdcd196c584 d196d100 c000c31c c000c3e4 c000ae90 c000c910 c000c924 c0008948 c01ca610 c0000394.....................................Workaround: None. The chance of a module reload occurring again on the same module is very rare. Therefore, continued use of the module is acceptable.
A software workaround for this issue exists in SAN-OS Release 3.3.(2) and NX-OS Release 4.(1b). Upgrading to one of those releases will help decrease instances of modules reloads.
•
Symptom: When you configure Cisco Traffic Analyzer to capture traffic on one or more interfaces on a Windows platform, the configuration web page might not show that the interface has been selected for traffic capture even though traffic capture on that interface is enabled.
Workaround: Check the logs to clarify that the correct interface has been selected.
•
Symptom: If an iSNS client tries to register a portal separately after registering the network entity and storage node object with the Cisco MDS iSNS server, the portal registration might fail.
Workaround: Register the portal at the same time as the network entity and storage node object registration.
•
Symptom: If there are IP over Fibre Channel (IPFC) interfaces configured on an SSM, you might experience issues if you downgrade from SAN-OS Release 3.x to Release 2.x.
Workaround: Before downgrading, remove the IPFC interface on the module and then recreate the IPFC interface after the downgrade is complete.
•
Symptom: If IP ACLs are applied to any IP Storage Gigabit Ethernet port, implicit deny does not take effect.
Workaround: Configure explicit deny on the port.
•
Symptom: Time zone changes that are executed on an MDS switch do not take effect on the 12-port, 24-port, and 48 port 1-Gbps/2-Gbps/4-Gbps Fibre Channel modules, and on the 4-port 10-Gbps module. This issue occurs in SAN-OS Releases 3.0(1), 3.0(2), 3.0(2a), and 3.0(3).
Time zone changes that are executed on an MDS switch do not take effect on the 16-port or 32-port 1-Gbps/2-Gbps module, on the 4-port or 8-port Gigabit Ethernet IP services module, the MPS 14/2 module, and on the SSM. This issue occurs in SAN-OS Release 3.0(3).
This issue has no effect on functionality. However, debug messages and syslogs from the MDS switching modules have incorrect timestamps if the time zone is configured on an MDS switch.
Workaround: None.
•
Symptom: Graceful shutdowns of ISLs are not supported for IVR traffic.
Workaround: Increase the fspf cost on the link before it is shut down, so that traffic will flow through an alternate path.
•
Symptom: The management port on MDS switches supports one user-configured IPv6 address, but does not support autoconfiguration of an IPv6 address in Cisco SAN-OS Release 3.2(1a).
Workaround: None.
•
Symptom: On a Gigabit Ethernet interface on the MDS MSM-18/4, shut the interface before removing its IP address so that configuration changes on the interface can take effect. This applies only to the Gigabit Ethernet ports in slot 1 of the MDS 9222i Switch and the MDS 9216i Switch.
Workaround: Always shut the interface using the shutdown command before removing the IP address and making configuration changes.
•
Symptom: HP Blade Servers that are connected through an HP Virtual Connect (VC) FC module to a Cisco Fabric Switch for HP c-Class BladeSystem using NPIV lose access to LUNs when load balancing on the VC module is switched from 16:1 to 8:1. When the load balancing ratio is 16:1, all servers connect through interface ext1. When the ratio is 8:1, servers 1 and 3 connect through ext1, servers 2 and 4 connect through ext2, and so on. Servers on ext2 are not affected by the switchover. In addition, packets might get dropped when the switchover occurs.
Workaround: None.
•
Symptom: If a supervisor switchover occurs while Fabric Manager is creating a DMM job, the job creation process times out.
Workaround: Cancel the DMM job and then recreate it.
•
Symptom: Removing a fabric and then adding the same fabric in Fabric Manager causes a session fabric ID mismatch. As a result, hosts to not appear in the Step 1 window of the the Fabric Manager DMM job creation wizard.
Workaround: Restart the Fabric Manager Server.
•
Symptom: Fabric Manager takes 2 to 3 minutes to bring up the DMM job creation wizard in a setup with 25 switches, 400 enclosures, and 2400 entries in the name server.
Workaround: None.
•
Symptom: In a configuration with a PortChannel with FCIP members and Write Acceleration in use, if IVR NAT is enabled on one end of the PortChannel and not enabled on the other end, then traffic over the FCIP tunnel might fail.
Workaround: Enable IVR NAT on both ends of the PortChannel or disable it on both ends.
•
Symptom: Although the FCIP compression ratio is set to Auto, it does not display correctly in Fabric Manager Server.
Workaround: None.
•
Symptom: IPv6 duplicate address detection (DAD) may not always works for the management port.
Workaround: None.
•
Symptom: If DMM is provisioned on the SSM and you downgrade to a Cisco MDS SAN-OS release that does not support DMM, the configuration persists and the GUI and CLI show DMM as a provisioned application.
Workaround: Manually remove the DMM configuration from the switch before downgrading to a Cisco MDS SAN-OS release that does not support DMM, such as downgrading from SAN-OS Release 3.2(1a) to SAN-OS Release 3.1(3). If you forget to remove the configuration before the downgrade, power off the module and purge the configuration on the SSM module by entering the following commands:
switch(config)# poweroff module slot
switch# purge module slot running-config•
Symptom: In rare situations during a storage-based online data migration job, the user might not be able to destroy the job if the following sequence of events occurs:
1.
2.
3.
4.
Workaround: Reload the SSM.
•
Symptom: FCP-CMD (for example, Inquiry) frames targeted to LUN 0x45F0 or LUN 0x50F0 are dropped by an MDS switch when traffic flows (egresses) thru Generation 2 modules. LUN 0x45F0 corresponds to HPUX's Volume Set Address <VBUS ID: 0xB, Target ID: 0xE, LUN: 0x0>.
Workaround: Do not use LUN 0x45F0 and LUN 0x50F0 when Generation 2 modules are present in the fabric.
•
Symptom: The response time shown in the output of a ping ip-address command may not be accurate if there is an MDS MSM -8/4 in the path.
Workaround: Use the ips measure-rtt command to measure the round trip time.
•
Symptom: The following Fabric Manager client components that use SSH and Telnet do not work well with NAT:
•
•
•
Workaround: None.
Related Documentation
The documentation set for the Cisco MDS 9000 Family includes the following documents.
Release Notes
•
•
•
Compatibility Information
•
•
•
•
Regulatory Compliance and Safety Information
•
Hardware Installation
•
•
•
•
Cisco Fabric Manager
•
•
•
•
Command-Line Interface
•
•
•
•
•
Troubleshooting and Reference
•
•
•
•
Installation and Configuration Note
•
•
•
•
•
Obtaining Documentation, Obtaining Support, and Security Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2007 Cisco Systems, Inc. All rights reserved.
