 Feedback
|
Table Of Contents
Cisco MDS 9000 Family Release Notes
for Cisco MDS SAN-OS Release 3.3(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
Upgrading Your Version of Cisco Fabric Manager
Upgrading from Release 3.1(2c) with the PostgreSQL Patch
The Fabric Manager Installation Process Overview
FICON Supported Releases and Upgrade Paths
Reconfiguring SSM Ports Before Upgrading to SAN-OS Release 3.3(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.3(1a)
Media Servers with Drives in Two Fabrics
Cisco Fabric Manager Enhancements
Upgrading to Recover Loss of Performance Manager Data
Maximum Number of Zones Supported in Interop Mode 4
Storage Media Encryption Not Supported
Cisco MDS 9222i Module Upgrade
Applying Zone Configurations to VSAN 1
Running Storage Applications on the MSM-18/4
Compatibility of Fabric Manager and Data Mobility Manager
PPRC Not Supported with FCIP Write Acceleration
Using IVR In a Fabric With Mixed Code Versions
Regulatory Compliance and Safety Information
Intelligent Storage Networking Services
Installation and Configuration Note
Obtaining Documentation and Submitting a Service Request
Cisco MDS 9000 Family Release Notes
for Cisco MDS SAN-OS Release 3.3(1a)
Release Date: April 24, 2008
Part Number: OL-14116-06 V0
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
04/24/2008
Created release notes.
B0
04/30/2008
Added DDTS CSCso63465.
C0
05/29/2008
Revised FCIP Interop description.
D0
06/02/2008
Changed DDTS CSCsm17768 to resolved.
E0
06/19/2008
Added SNMP Version 3 Authentication limitation.
Updated Installing Fabric Manager on Windows.
Added DDTS CSCsl04532.
F0
07/09/2008
Added Upgrading to Recover Loss of Performance Manager Data.
G0
09/16/2008
Updated FlexAttach.
H0
09/17/2008
Added DDTS CSCsl12611.
I0
10/22/2008
Added DDTS CSCso05448.
J0
11/12/2008
Added DDTS CSCso36760.
Added a Note to the "General Downgrading Guidelines" section about downgrading when Data Mobility Manager or Storage Media Encryptionare configured in the fabric.
K0
11/18/2008
Added DDTS CSCso72230.
Removed DDTS CSCsk90998.
L0
02/23/2009
Added DDTS CSCsl90865.
M0
03/04/2009
Added DDTS CSCso01396.
N0
03/20/2009
Added DDTS CSCsm80790.
Added "Applying Zone Configurations to VSAN 1" and "Running Storage Applications on the MSM-18/4" to the "Limitations and Restrictions" section.
O0
04/14/2009
Updated DDTS CSCsk49634.
P0
04/28/2009
Added the "FICON Supported Releases and Upgrade Paths" section.
Added the "FICON Downgrade Paths" section.
Added the "Compatibility of Fabric Manager and Data Mobility Manager" limitation.
Added the "Storage Media Encryption Not Supported" limitation.
Q0
06/23/2009
Added a statement not to use Java 1.6 Update 13 to the "The Fabric Manager Installation Process Overview" section.
R0
07/22/2009
Added DDTS CSCsr85709.
S0
08/28/2009
Added DDTS CSCso19341.
Added a Note to the "Installing Fabric Manager on Windows" section about the effect of a Group Policy Object (GPO) in Windows on Fabric Manager Server when used with the PostgreSQL database.
T0
07/27/2010
Added DDTS CSCsq74312.
U0
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.
V0
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.3.1a
MDS 9500 Supervisor/Fabric-2, SAN-OS software.
MDS 9500 Series only
M95S1K9-3.3.1a
MDS 9500 Supervisor/Fabric-I, SAN-OS software.
MDS 9500 Series only
M92S2K9-3.3.1a
MDS 9222 Supervisor/Fabric-2, SAN-OS software.
MDS 9200 Series only
M92S1K9-3.3.1a
MDS 9216 Supervisor/Fabric-I, SAN-OS software.
MDS 9200 Series only
M91S2K9-3.3.1a
MDS 9100 Supervisor/Fabric-2, SAN-OS software.
MDS 9100 Series only
M91S1K9-3.3.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
License
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
M9500SME1MK9
Cisco Storage Media Encryption package for MSM-18/4 module
MDS 9500 Series with MSM
M9200SME1MK9
Cisco Storage Media Encryption package for MSM-18/4 module
MDS 9200 Series with MSM
M9200SME1FK9
Cisco Storage Media Encryption package for fixed slot
MDS 9222i Switch only
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 Switch 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 Switch 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 Switch 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 Switch 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 Switch 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 Switch 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 Switch only
DS-C9140-K9
MDS 9140 fixed configuration (non-modular) fabric switch (includes 8 full rate ports and 32 host-optimized ports).
MDS 9140 Switch 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 Switch 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 Switch only
DS-C9120-K9
MDS 9120 fixed configuration, non-modular, fabric switch (includes4 full rate ports and 16 host-optimized ports).
MDS 9120 Switch 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 Switch only
Supervisor modules
DS-X9530-SF2-K9
MDS 9500 Supervisor-2 module.
MDS 9500 Series only
DS-X9530-SF2A-K9
MDS 9500 Supervisor-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 Switch
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 Switch
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 Switch
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 Switch
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 Switch
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-GE-T
1-Gbps Ethernet 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 Switch
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
M90FMK9-CD322=
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-ek9
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 the Configuring Generation 2 Switching Modules chapter in the the Cisco MDS 9000 Family CLI Configuration Guide.
For information on port index availability, refer to the "Port Index Availability" section in the Product Overview chapter of the Cisco MDS 9500 Series Hardware Installation Guide.
For information on Cisco MDS 9000 hardware and software compatibility, refer to the Cisco MDS 9000 SAN-OS Hardware and Software Compatibility Information.
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:
•
•
•
•
•
•
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.
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.
Note
Note
Upgrading from Release 3.1(2c) with the PostgreSQL Patch
To upgrade Fabric Manager to Release 3.3(1a) from the UBS special version of 3.1.2c with the PostgreSQL patch, do the following:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
The Fabric Manager Installation Process Overview
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
•
•
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. Refer to Table 6 for information on the supported upgrade path.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. Refer to Table 6 for information on the supported upgrade path.4.
5.
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.
6.
http://cisco.com/cgi-bin/tablebuild.pl/mds-fm
Installing Fabric Manager on Solaris
This section describes how to install Fabric Manager on Solaris.
To install Fabric Manager on Solaris, follow these steps:
Step 1
Step 2
Step 3
Step 4
java -Xms512m -Xmx512m -jar m9000-fm-3.3.1a.jar
Step 5
Note
Installing Fabric Manager on Windows
This section describes how to install Fabric Manager on Windows.
Note
Note
On a Windows system, the Microsoft Active Directory applies a Group Policy Object (GPO) to the Fabric Manager Server. The GPO does not recognize the local user PostgreSQL because it is not in the GPO allow list. As a result, the GPO removes it, and the PostgreSQL database stops working.
To avoid this situation, you should move the Fabric Manager Server to its own OU and apply the same feature settings as the original OU, but remove the local user account to log in as a service.If your server is running Terminal Services in Application mode, or if you are running Citrix Metaframe or any variation thereof, you need to issue the following command on the DOS prompt before installing Fabric Manager Server.
1.
2.
Note
The following is an example of the output of this command:
C:\Documents and Settings\user.domain>CHANGE USER /INSTALLUser session is ready to install applications.3.
4.
The following is an example of the output of this command:
C:\Documents and Settings\user.domain>CHANGE USER /executeUser session is ready to execute applications.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
General Upgrading Guidelines
Use the following guidelines when upgrading to Cisco MDS SAN-OS Release 3.3(1a):
•
•
•
•
•
–
–
–
–
–
Use Table 7 to determine your nondisruptive upgrade path to Cisco SAN-OS Release 3.3(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.3(1a) does not support FICON.
Table 8 lists the SAN-OS and NX-OS releases that support FICON. Refer to the specific release notes for FICON upgrade path information.
Table 8 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 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); you must upgrade to Release 2.1(2b) before upgrading to Release 3.3(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.3(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.3(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 7, 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(2) or earlier version to SAN-OS Release 3.3(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.3(1a):
•
•
•
•
•
•
–
–
–
–
–
–
Note
1.
2.
If these conditions exist, remove the application configuration for these targets and hosts before proceeding with the downgrade.
Use Table 9 to determine the nondisruptive downgrade path from Cisco SAN-OS Release 3.3(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.3(1a) does not support FICON.
Refer to Table 8 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.3(1a)
This section briefly describes the new features introduced in this release. For detailed information about the features listed, refer to the Cisco MDS 9000 Family CLI Configuration Guide, Release 3.x, the Cisco MDS 9000 Family Fabric Manager Configuration Guide, and the Cisco MDS 9000 Family Storage Media Encryption 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.
Note
Cisco SME Enhancements
Cisco Storage Media Encryption (SME) includes enhanced tape encryption functionality in Release 3.3(1a). The new capabilities include additional features, expanded interoperability (more devices and environments), and greater performance and scalability. The Cisco SME enhancements include the following:
•
Rekey Operations
It is necessary to change media encryption keys periodically to ensure that only a limited number of tape cartridges have the same key, when using the key per volume group option. Rekey operations can be performed on a regular basis, using the new Volume Group Key Rekey feature.
Cisco SME has the ability to create new smart cards if they are lost. Release 3.3(1a) includes the option to rekey the cluster with a new master key when replacing smart cards by using the new Master Key Rekey feature.
Off-line Data Restore Tool
The Off-line Data Restore Tool enables end-users to recover data on tape media from a tape device attached to a Linux server. This feature addresses the need to recover data without using Cisco MDS 9000 Family hardware.
Media Servers with Drives in Two Fabrics
SAN-OS Release 3.3(1a) allows end-users to use Cisco SME in an environment where a single media server may have access to different tape drives on in different fabrics that reside in a common tape library.
Expanded Interoperability
The following enhancements in Release 3.3(1a) expand Cisco SME interoperability:
•
•
•
•
Note
Enhanced Performance
SAN-OS Release 3.3(1a) includes performance optimizations for Cisco SME. This includes exceeding the typical throughput requirements for Linear Tape Open (LTO) 3 tape drives. This enhancement increases the maximum throughput for individual tape drives, but it does not change the total aggregate throughput for each Cisco SME interface (module). In addition, Release 3.3(1a) optimizes load balancing. which eliminates unnecessary use of Inter-Switch Links (ISLs). Cisco SME can also rebalance the assignments to improve utilization of the encryption resources
Fx-port Zoning Support
Cisco SME release 3.2(2c) only supports pWWN N-port zoning (defines zone members based on the host or storage port). Though this is the most commonly used zoning method, support now includes other zoning types such as Fx-port zoning (defines zone members based on the switch port). This expands the range of environments Cisco SME can be deployed in without SAN reconfiguration.
NPV Traffic Management
Prior to Release 3.3(1a), assignment of hosts to ports connecting a Cisco MDS 9000 Family switch in the N-Port Virtualization (NPV) mode to a core switch was automatic. You can now select the ports that servers use to connect to the core switches. For information on NPV, refer to the Configuring N Port Virtualization chapter in the Cisco MDS 9000 Family Configuration Guides.
Starting in Cisco MDS SAN-OS Release 3.3(1a), NPV will be supported on the Cisco Fabric Switch for IBM BladeCenter.
Secure Erase
The secure erase feature erases existing data on a given target in such a way that reconstructing that data is virtually impossible. SAN-based secure erase has numerous advantages over traditional data erase mechanisms such as higher speed, lower cost, ease-of-execution, and platform independence.
FlexAttach
FlexAttach is supported on the Cisco Fabric Switch for HP c-Class BladeSystem switch, the Cisco Fabric Switch for IBM BladeCenter switch, the Cisco MDS 9124 switch, and the Cisco MDS 9134 switch, when NPV mode is enabled. The FlexAttach feature reduces the time and coordination effort required by SAN and server administrators when installing and replacing servers. To alleviate interaction between SAN administrators and server administrators, it is important that changes are not made to the SAN configuration when a new server is installed or when an existing server needs replacement. FlexAttach is a new feature included in SAN-OS Release 3.3(1a) that addresses this issue. For information on FlexAttach, refer to the Configuring FlexAttach Virtual pWWN chapter in the Cisco MDS 9000 Family Configuration Guides.
Administrators can benefit from FlexAttach in the following scenarios:
•
•
•
•
•
SMI-S
Cisco SAN-OS Release 3.3(1a) includes the following SMI-S enhancements:
•
•
•
•
FCIP Interop
In Release 3.3(1a), support is included for FCIP interop between the MSM-18/4 module or MDS 9222i switch and the MPS-14/2 module, the MDS 9216i switch, or the IPS-8 module. FCIP is supported on the MPS-14/2 module, MDS 9216i switch, IPS-8 module, IPS-4 module, MDS 9222i switch, and the MSM-18/4 module. Table 10 shows the FCIP interoperability.
Copper SFP
Beginning with Release 3.3(1a), copper SFPs are supported on the Ethernet ports of the MSM-18/4 module and the MDS 9222i switch.
Cisco Fabric Manager Enhancements
This sections describes Cisco Fabric Manager enhancements found in Release 3.3(1a).
New Configuration Wizards
Two new configuration wizards are included in the Cisco Fabric Manager Java user interface: the port-security wizard, and the N-Port Virtualizer (NPV) wizard. The port-security wizard streamlines provisioning by simplifying configuration tasks.
The NPV wizard enables Cisco MDS 9000 switches to quickly change to the NPV mode. The NPV wizard allows administrators to configure the most important options across many switches (up to 100 switches) in a single pass, thus providing considerable time savings.
Scalability Improvement
Increasing Cisco Fabric Manager scalability is essential to keep up with the growing Cisco MDS 9000 Family fabrics. Cisco Fabric Manager now includes the capability to discover and manage up to 10,000 end-devices on a single server when performance monitoring is enable.
Metro-Optical Link Display
Cisco Fabric Manager now discovers links using DWDM optics and displays them with a distinctive line pattern. This feature provides an easy-to-read display showing that the link is used for SAN extensions (relatively long distance links).
Java Runtime 1.6 Support
In addition to Java Runtime Environment (JRE) 1.5, Cisco Fabric Manager now supports JRE 1.6.
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
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.
SNMP Version 3 Authentication
Multiple Cisco products contain either of two authentication vulnerabilities in the Simple Network Management Protocol Version 3 (SNMPv3) feature. These vulnerabilities can be exploited when processing a malformed SNMPv3 message. These vulnerabilities could allow the disclosure of network information or may enable an attacker to perform configuration changes to vulnerable devices. The SNMP server is an optional service that is disabled by default. Only SNMPv3 is impacted by these vulnerabilities.
Note
The United States Computer Emergency Response Team (US-CERT) has assigned Vulnerability Note VU#878044 to these vulnerabilities. Common Vulnerabilities and Exposures (CVE) identifier CVE-2008-0960 has been assigned to these vulnerabilities.
This advisory is posted at http://www.cisco.com/en/US/products/products_security_advisory09186a00809ac83b.shtml.
Workarounds are available for mitigating the impact of the vulnerabilities described in this document.
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.
Storage Media Encryption Not Supported
MDS SAN-OS Release 3.3(1a) does not support the Storage Media Encryption application because of the open caveat CSCsw95386. A fix for this issue is available in SAN-OS Release 3.3(3) and in NX-OS 4.1(3a). Customers who do not plan to upgrade to SAN-OS Release 3.3(3) or NX-OS Release 4.1(3a), but who need an immediate fix for CSCsw95386 should obtain MDS SAN-OS Release 3.3(2E2), which is a special engineering release for customers who are running SAN-OS Release 3.3(2) and using SME.
Cisco MDS 9222i Module Upgrade
On the MDS 9222i module, an upgrade from SAN-OS Release 3.2(x) to Release 3.3(1a) is not supported if there is a Cisco SME or Cisco DMM configuration in the fabric for hosts and targets attached to the MDS 9222i module.
SANTap
The SANTap feature allows third party data storage applications, such as long distance replication and continuous backup, to be integrated into the SAN. SANTap is not supported in Release 3.3(1a).
Applying Zone Configurations to VSAN 1
In the setup script, you can configure system default values for the default-zone to be permit or deny, and you can configure default values for the zone distribution method and for the zone mode.
These default settings are applied when a new VSAN is created. However, the settings will not take effect on VSAN 1, because it exists prior to running the setup script. Therefore, when you need those settings for VSAN 1, you must explicitly issue the following commands:
•
•
•
Running Storage Applications on the MSM-18/4
The Cisco MDS 9000 18/4-Port Multiservice Module (MSM-18/4) does not support multiple, concurrent storage applications. Only one application, such as SME or DMM, can run on the MSM-18/4 at a time.
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.
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: Traffic entering thru a Generation 1 module may be disrupted when upgrading from Release 3.1(3) and earlier to any image later that Release 3.1(3) but earlier than Relese 3.3(1a), if we have active egress SPAN sessions configured with the source as ports that are administratively up but operationally down.
Workaround: This issue is resolved.
•
Symptom: In some instances, the host is not able to see the SAN Device Virtualization (SDV) virtual targets that it is zoned with. The host performs FLOGI, PLOGI and PRLI successfully, followed by SCSI inquiry. The hosts stop at REPORT LUNS.
Workaround: This issue is resolved.
•
Symptom: During In-Service Software Upgrade (ISSU), Inter-VSAN Routing (IVR) gets initialized later than Fibre Channel Name Service(FCNS). FCNS checks with IVR for entries which it has in its persistent storage and that belong to IVR (for virtual domains). Since IVR is not initialized yet, it does not respond to FCNS. As a result, an end device may not be advertised to a transient VSAN or it may not be visible to the IVR end device in a target VSAN.
Workaround: This issue is resolved.
•
Symptom: After upgrading to SAN-OS Release 3.2(3a) or later, the module stays in the "failure" state or rests.
Workaround: This issue is resolved.
•
Symptom: Following and upgrade to SAN-OS Release 3.3(1a), if there is a VSAN mismatch on the external link between the NPV switch and the core switch, the link will not come up after a link flap or link re-initialization.
Workaround: This issue is resolved.
•
Symptom: In a VSAN in which a large number of FICON devices exist and FICON tape acceleration is enabled, FICON tape acceleration performance degradation occurs. The FICON devices do not have to be tapes or virtual tapes; for example, they can be disks.
Workaround: This issue is resolved.
•
Symptom: Under rare conditions, the standby Supervisor module and the active Supervisor module will not have the module capability synchronized. This can be seen by issuing the show system internal capability module <module-no> command on every standby module that is online. Review the output and locate the last entry: CAP_TYPE_MODULE_INFO. The output should display a status of ModuleOnline as shown in the example below.
switch#show system internal capability module <module-no>
113) Service:platform, Capability:CAP_TYPE_MODULE_INFO
Registered by node:0x102 at 1 usecs after Thu Jun 29 13:47:00 1978
Description:Sets Module online status
proc type Linecard
status Module Online
sw card id 2
switch#
Workaround: This issue is resolved.
•
Symptom: During In-Service Software Upgrade (ISSU), SAN Device Virtualization (SDV) gets initialized later than Fibre Channel Name Service(FCNS). FCNS checks with SDV for entries which it has in its PSS and that belong to SDV (for virtual domains). Since SDV is not initialized yet, it will not respond to FCNS. As a result, the SDV entries in the virtual domain will be missing.
Workaround: This issue is resolved.
•
Symptom: The accounting log does not record status updates for zone attribute changes in basic mode.
Workaround. This issue is resolved.
•
Symptom: In a fabric with a very large number of Fibre Channel Name Server (FCNS) devices, if you add one more switch to the fabric, the name server on the newly added switch will receive a query from all other switches in the fabric. It will also receive responses to the queries it sent to other switches in the fabric. When all queries and responses are sent and received in a short period of time, the Fibre Channel 2 stack may drop some of them and the FCNS database may be out of sync.
Workaround. This issue is resolved.
•
Symptom: When the active IVR zoneset contains enhanced device alias-based members, traffic to and from these devices could be disrupted during a stateful restart or a switchover to a Supervisor module. This issue occurs under the following conditions:
–
–
–
a) The system is running a SAN-OS release earlier than Release 3.3(1a) and either a stateful restart of the IVR process or a switchover to another Supervisor running the same SAN-OS release occurs.
b) The system is downgraded to a SAN-OS release earlier than Release 3.3(1a).
Workaround: This issue is resolved.
•
Symptom: A SAN Device Virtualization (SDV) configuration is terminated after an ACL failure due to a Ternary Content Addressable Memory (TCAM) Full condition. This occurs in situations where there are large SDV configurations (for example, 1,000 devices) and when the TCAM becomes full due to excessive entries on a single interface.
Workaround. This issue is resolved.
•
Symptom: Inter-Switch Link (ISL) isolation is seen due to a zone merge failure in interop mode 1. This can occur when a Cisco MDS switch with a large active zoneset tries to merge with non-MDS switches. Since the merge request size is sent out incorrectly in MRRA, some non-MDS switches may reject the subsequent merge request frame leading to an ISL isolation.
Workaround. This issue is resolved.
•
Symptom: A zone commit operation fails. The following message is displayed: No pending info found. This issue occurs when the device-alias is in basic mode and an enhanced zoning session exists. When those conditions exist, if a device-alias is renamed, the lock acquired in enhanced zoning is lost. This causes the zone commit operation to fail.
Workaround. This issue is resolved.
•
Symptom: On an MDS 9513 switch, if a hardware failure on one of the two redundant crossbar modules occurs, it is possible to experience traffic disruptions. Certain FC interfaces may go down and they may not come up again. The output of the show interface command for these interfaces may be similar to the following example.
fc1/2 is down (Link failure: Link Reset failed, non-empty recv queue)
Port description is vader
Hardware is Fibre Channel, SFP is short wave laser w/o OFC (SN)
Port WWN is 20:02:00:0d:ec:3b:09:00
Admin port mode is FX
snmp link state traps are enabled
Port vsan is 200
Receive data field Size is 2112
Beacon is turned off
5 minutes input rate 0 bits/sec, 0 bytes/sec, 0 frames/sec
5 minutes output rate 0 bits/sec, 0 bytes/sec, 0 frames/sec
2933212200 frames input, 4823200761788 bytes
0 discards, 0 errors
0 CRC, 0 unknown class
0 too long, 0 too short
9812020429 frames output, 9487579066196 bytes
0 discards, 0 errors
2 input OLS, 2 LRR, 0 NOS, 6 loop inits
3 output OLS, 2 LRR, 3 NOS, 5 loop inits
This happens only in conditions when a crossbar module on an MDS 9513 switch fails. The output of the show hardware command will indicate that the status of the crossbar module is not "ok".
Workaround: This issue is resolved.
•
Symptom: When IVR is configured, the active Supervisor may fail when issuing any of the following CLI commands:
show tech
show tech detail
show system interface fcfwd idxmap ...
This issue may also occur when using the show tech-support option in Fabric Manager.
Workaround: This issue is resolved.
•
Symptom: Whena SAN-OS upgrade is performed on a Supervisor 1 module, in rare cases, SNMP might fail and the upgrade may fail causing the upgrade to be disruptive.
Workaround: This issue is resolved.
•
Symptom: Polling does not work with multiple fabrics.
Workaround: This issue is resolved.
•
Symptom: The accounting log does not record all commands that are run on the system.
Workaround. This issue is resolved.
•
Symptom: In Cisco SME, tape device names can not include special characters (such as hyphens or underscores). This will cause future tape device creations for a tape group to fail.
Workaround: This issue is resolved.
•
Symptom: When a QoS classmap is created from Fabric Manager with a space between the two words comprising a classmap (for example: "classmap sample map" instead of "classmap samplemap"), the switch accepts the configuration. However, the switch rejects the configuration during start up if the same information is stored in the start-up configuration because the CLI does not allow spaces.
Workaround. This issue is resolved.
•
Symptom: When you run Encrypter.(sh | bat), you see the following exception:
----------------------------------------------------------------------------------Exception in thread "main" java.lang.AbstractMethodError: org.apache.crimson.tree.XmlDocument.getXmlStandalone()Zat com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.setDocumentInfo(Unknown Source)at com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.parse(Unknown Source)at com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.parse(Unknown Source)at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transformIdentity (Unknown Source)at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(Unknown Source)at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(Unknown Source)at com.cisco.dcbu.lib.util.jboss_4_2.JBoss_4_2XMLFileParser.writeXMLFile(JBoss_4_2XMLFile Parser.java:149)at com.cisco.dcbu.lib.util.jboss_4_2.JBoss_4_2XMLFileParser.updateXMLFile(JBoss_4_2XMLFil eParser.java:176)at com.cisco.dcbu.install.UserUtil.updateJBossLoginConfig(UserUtil.java:412)at com.cisco.dcbu.install.UserUtil.dbPwdEncrypt(UserUtil.java:220)at com.cisco.dcbu.install.UserUtil.scriptEncrypt(UserUtil.java:170)at com.cisco.dcbu.install.UserUtil.main(UserUtil.java:330)-----------------------------------------------------------------------------------In addition, the size of the login-config.xml file in the MDS 9000/jboss/server/default/conf directory becomes 0. This occurs when using JRE 1.6 or above.
Workaround: This issue is resolved.
Workaround: (for 3.2.1 to 3.3.1) For Linux or Solaris, go to the MDS 9000/bin directyory. Edit the Encrypter.sh file and remove the text $LIB/crimson.jar: in the file . Note the colon at the end of the text needs to be removed also.
For Windows, go to MDS 9000\bin directory. Edit the Encrypter.bat file and remove the text %INSTALLDIR%\lib\crimson.jar; . Note the semicolon at the end of the text need to be removed also.
After completing the steps above, replace the login-config.xml with the attached file. Find this string: <module-option name="username">DBUSER</module-option> and replace the DBUSER with your db username. Run the script again with the correct db password.
•
Symptom: When you issue the show running-config command, the iSCSI initiators are not shown. This may occur even though the iSCSI session and the show startup-config command shows the iSCSI initiators correctly. Even after issuing the copy run-start command, the show running-diff command shows iSCSI information as the difference.
Workaround: This issue is resolved.
•
Symptom: SAN Device Virtualization (SDV) virtual FCIDs are inconsistent across different switches. This issue can occur when SDV is enabled and if the SDV internal port-table is out of sync with the Fibre Channel Name Service (FCNS).
Workaround. This issue is resolved.
•
Symptom: To send the SNMPv3 Inform packet, the SNMP remote user (the SNMPv3 user with an engineID other than the local engineID) credentials need to be configured on the switch. If the remote user name is configured as "admin", the remote user can not be deleted from the switch.
Workaround. This issue is resolved.
•
Symptom: For an RMON alarm that uses event 0, the first rising alarm will trigger, but subsequent alarms will not. If the event identifier is changed to a configured event identifier, the alarm will work.
Workaround: This issue is resolved.
•
Symptom: If there are uncommitted changes in Dynamic Port VSAN Membership (DPVM), while committing the changes for a device alias then the Messaging and Transanction Service (MTS) buffer may start to fill up and may eventually run out of space. When this occurs, the following error is displayed: mts_acquire_q_space failed for opcode.
Workaround. This issue is resolved.
•
Symptom: On a Generation 2 Supervisor module, a PLOGI ACC frame generated by private loop devices (with the TL port attached) is forwarded with a swapped domain-IDand area-ID in the source FCID. The incorrect format is shown as AADDPP instead of DDAAPP (correct format). This prevents the PLOGI between the host and storage to complete successfully
Workaround. This issue is resolved.
•
Symptom: The show running CLI command output displays the scheduler configuration with an incorrect schedule time value. However, this appears correctly when you issue the show scheduler config CLI command. As a result, if you issue the copy running-start command and the startup configuration is replayed, there will be a syntax error in the scheduler schedule CLI command.
Workaround. This issue is resolved.
•
Symptom: Only the first 100 RMON hcalarms (64 bit) show up in the running-configuration and the startup-configuration. The configuration is kept in the system and will survive across reboots, but it cannot be moved to another Supervisor (for example, in the case of a total Supervisor replacement). This problem does not affect 32-bit alarms. This occurs when the RMON alarm limit has been raised from the default value of 100. This issue does not affect 32-bit alarms.
Workaround. This issue is resolved.
•
Symptom: The number of maximum RMON alarms is not visible in the CLI.
Workaround: This issue is resolved.
•
Symptom: Using a third-party SNMP tool for a full SNMP walk on an MDS 9222i Switch may trigger a kernel failure. Using Fabric Manager or Device Manager will not cause a failure.
Prior to the failure, you might see a message similar to the following. This message indicates that full SNMP walks are occurring:
%KERN-2-SYSTEM_MSG: mts: received a giant packet from AIPC. Giving up. snode=0x202, ssap=924, dnode=0x101, dsap=16, opcode=1089, msg_id=0x1998a, msg_size=44, skb_size=28Workaround:This issue is resolved.
•
Symptom: Due to CSCsl96144, after a Supervisor switchover, the platform manager API failed when the ACL called it. Due to that failure, the ACL didn't handle the IVR request to program or delete the PLOGI capture properly. As a result, IVR could not finish the domain capture which stopped the IVR device export.
Workaround: This issue is resolved.
•
Symptom: Symptom: Using Fabric Manager Server, tape drives and tape groups are not listed in the tape group configuration. This occurs when a Cisco SME VSAN is isolated in the fabric or when the tape drives are in VSANs that are segmented in a fabric.
Workaround: This issue is resolved.
•
Symptom: In Fabric Manager, when using the Alias -> Enclosure button at the End Device Table, alias names are not converted. For example, "Alias-Port1" does not convert to "Alias"(by taking out the hyphen). In releases prior to Release 3.3(a), the convertion occurred correctly.
Workaround: This issue is resolved.
•
Symptom: When a bootflash failure occurs, Call Home destination profiles, for example, XML, with only the Cisco TAC alert group, do not get the notification.
Workaround: This issue is resolved.
•
Symptom: A login to Fabric Manager Server is not successful using a disconnected client.
Workaround: This issue is resolved.
•
Symptom: When 2 Fabric Manager clients simultaneously change the device alias for the same port using the End Device Table, an apply error is displayed on the second Fabric Manager client; and, after a refresh, the old value does not exist.
Workaround: This issue is resolved.
•
Symptom: A 64-bit alarm may log a startup alarm after a system reboot.
Workaround: This issue is resolved.
•
Symptom: RMON cseSysMemoryUtilization memory utilzation alarm may not trigger.
Workaround: This issue is resolved.
•
Symptom: When you configure a 32-bit RMON alarm as a delta alarm, the switch sends rising and falling traps with alarmsampletype as absolute alarms not as delta alarms.
Workaround: This issue is resolved.
•
Symptom: There is a observable performance drop for backup and restore when Cisco SME is introduced between a host and tape due to the increased latency.
Workaround: This issue is resolved.
Open Caveats
•
Symptom: In rare circumstances, after upgrading the SAN-OS, a Generation 1 module may be rebooted as it stops responding to the keep alive messages from the Supervisor module.
Workaround: None.
•
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(1) 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 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: Following an upgrade to Cisco MDS SAN-OS Release 3.2(1) 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: Certain drivers cache the PRLI service parameters negotiated across the PLOGI/PRLI session establishment. If a library controller that does not support RETRY FCP-2 error recovery procedures is included in a SME configuration, SME may negotiate RETRY in PRLI with the host. Subsequently, if the library controller is removed from SME, the host driver may cache the PRLI parameter and attempt to perform SRR, which gets rejected by the target.
Workaround: When configuring an SME cluster through the web client, exclude the library controller target ports in the target port selection window. For those tape libraries, where the library controller and tape drives are exported as LUNs behind the target port, this is not an issue.
•
Symptom: The CIM server stops. This occurs after creating a subscription using the same filter and handler.
Workaround: Reload the switch.
•
Symptom: Using Fabric Manager Release 3.2(2), if you have an enclosure with multiple ports and you then use the Data Migration Wizard to create a job with that enclosure as the existing storage but don't select all the storage ports in the enclosure, an error is displayed in the creation wizard.
Workaround: Put the ports you plan to use as the existing storage in the migration into a separate enclosure, and use that enclosure in the wizard selection.
•
Symptom: In some instances, when requests to the control virtual target (CVT) are made, Fabric Manager times out. Regardless of the timeout, the CVT is created in the specified VSAN.
Workaround: To verify this, do either of the following:
–
–
•
Symptom: An FCIP link was going down because a data path processor (DPP) process had failed because of traffic on an internal chip.
Workaround: None.
•
Symptom: Under very rare circumstances, the ports on an MDS 9000 24-port 4-Gbps Fibre Channel module and on an MDS 9000 48-port 4-Gbps Fibre Channel module might fail and the state of the ports might change to hwFailure, or the module might reload when all the ports on the module fail.
If this occurs, the output of the show logging log command will be similar to the following:
2008 Mar 12 09:36:47 sw-DC3-Core-9509-1 %PORT-5-IF_DOWN_LINK_FAILURE: %$VSAN 2420%$ Interface fc3/2 is down (Link failure)2008 Mar 12 09:36:48 sw-DC3-Core-9509-1 %MODULE-2-MOD_DIAG_FAIL: Module 3 (serial: JAB0938014X) reported failure on ports 3/1-3/6 (Fibre Channel) due to Stratosphere common module experienced an error in device 63 (device error 0xc3f00276)2008 Mar 12 09:36:48 sw-DC3-Core-9509-1 CSCsu31909 %MODULE-2-MOD_SOMEPORTS_FAILED: Module 3 (serial: JAB0938014X) reported failure on ports 3/1-3/6 (Fibre Channel) due to Stratosphere common module experienced an error in device 63 (error 0xc3f00276)Or, the output of the show logging log command will be similar to the following:
%MODULE-2-MOD_DIAG_FAIL: Module 1 (serial: JABxxxxxxxx) reported failure on ports 1/1-1/24 (Fibre Channel) due to Q-Engine experienced an internal hardware error in device 55 (device error 0xc3700637)%MODULE-2-MOD_SOMEPORTS_FAILED: Module 1 (serial: JABxxxxxxxx) reported failure on ports 1/1-1/24 (Fibre Channel) due to Q-Engine experienced an internal hardware error in device 55 (error 0xc3700637)The output of the show module internal exceptionlog command will be similar to the following:
********* Exception info for module 1 ********exception information --- exception instance 1 ----Module Slot Number: 1Device Id : 55Device Name : Tuscany-queDevice Errorcode : 0xc3700637Device ID : 55 (0x37)Device Instance : 00 (0x00)Dev Type (HW/SW) : 06 (0x06)ErrNum (devInfo) : 55 (0x37)System Errorcode : 0x40420032 Q-Engine experienced an internal hardware errorError Type : Minor errorWorkaround: None.
•
Symptom: On the MDS 9222i module, an upgrade from SAN-OS Release 3.2(x) to Release 3.3(1a) fails when there is an active FC-Redirect configuration (created by Cisco SME or Cisco DMM applications) on the switch. An active FC-Redirect configuration is defined as:
–
–
If an upgrade is attempted when such active configuration is present, the switch will go into a disruptive upgrade.
Workaround: None. On the MDS 9222i module, an upgrade from SAN-OS Release 3.2(x) to Release 3.3(1a) is not supported if there is a Cisco SME or Cisco DMM configuration in the fabric for hosts and targets attached to the MDS 9222i module.
•
Symptom: In Fabric Manager Release 3.3(x), zone set cloning returns an autoZoneEditing error. The option to clone a zone is missing.
Workaround: You can upgrade to Fabric Manager Release 3.4(1a), or, if you are using Fabric Manager Release 3.3(x), you can resolve the issue by following these steps:
1.
2.
3.
4.
To resolve this issue from the CLI, enter the zoneset clone Zoneset1v1 clone # vsan vsan-id command.
•
Symptom: If FCIP is enabled and the SAN-OS is upgraded, the SNMP service will run into exception and the following syslog message is displayed: SNMP Operation(165) failed (62) setting error index.
Workaround: Disable FCIP during the SAN-OS upgrade.
•
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 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(1).
Workaround: None.
•
Symptom: On a Gigabit Ethernet interface on an MDS MSM-18/4 module, 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: In certain conditions, an MDS switch may not be able to determine the FC4-type of certain targets. This causes the targets to be listed in the hosts section during a Cisco SME tape group or tape device configuration.
Workaround: Issue the discover scsi-target vsan vsan-id fcid fcid command to re-discover the FC4-type of the targets. A Cisco SME tape group or tape device configuration will now list the targets correctly.
•
Symptom: In rare situations, on an MDS 9513 director switch, an upgrade fails when a standby supervisor does not come up to a state that the installer recognizes. As a result, the standby supervisor is reloaded to recover and the system runs the older configuration version.
Workaround: Perform the upgrade again.
•
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: 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(1) 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: If an NASB configuration in a VSAN is destroyed while a target discovery is pending, the NASB process fails. Issue the show nasb vsan x command on the SSM to view the target discovery in the Pending state.
Workaround: Reload the SSM.
•
Symptom: When NASB is enabled in a VSAN, all targets that are visible in that VSAN are discovered by NASB. If a new target is added to the VSAN, NASB does not automatically discover the new target.
Workaround: To discover the new target, reload the SSM or disable and re-enable NASB in the VSAN.
•
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: If you use JDK instead of JRE on Solaris, you might encounter a problem trying to install Device Manager from a web browser. This can happen because the installer heap limit of 256 MB is not sufficient.
Workaround: If you have this problem, save the jnlp link as file, increase the heap limit to 512 MB, and run javaws element-manager.jnlp at the shell prompt.
•
Symptom: After a disruptive downgrade or upgrade between SAN-OS Release 3.2(2c) and Release 3.2(1a), issuing a no shutdown command on a Cisco SME interface fails. When issuing the install all command to perform the downgrade process, a warning is issued that indicates that the downgrade will be disruptive if Cisco SME is enabled.
Workaround: Disable Cisco SME before proceeding with the downgrade process. If you perform a disruptive downgrade, then issue the purge module slot running-config command for the MSM-18/4 modules where Cisco SME is configured after the downgrade is complete.
•
Symptom: On the MDS 12-port, 24-port, and 48-port 4-Gbps Fibre Channel switching modules, and on the 4-port 10-Gbps Fibre Channel switching module for downgrades from 3.2(2c) to lower versions, if fcdomain persistency is disabled, F ports may not come up after a shutdown or no shutdown or a link flap.
Workaround: Shut the F port, enable and disable fcdomain persistency for that VSAN, and then bring up the F port.
•
Symptom: During an MDS 9222i switch reload, the connection from the management port (mgmt0) to the Gigabit Ethernet interface goes down. When the connection comes back up, the Gigabit Ethernet interface doesn't go into forwarding mode until 30 seconds later. The Fabric Manager server is not able to communicate to the MDS 9222i switch through SNMP during this 30 second window.
Workaround: If the switch is in the Cisco Ethernet switch family, configure port-fast to resolve the issue. On Ethernet switches from other vendors, apply a similar configuration mode.
•
Symptom: Devices attached on a remote McData switch do not show a correct physical connection on the correct port in Fabric Manager. This occurs because the registered devices in the McData nameserver are shifted by 4 from its actual physical port and Fabric Manager looks at this port address from the nameserver to locate the physical port.
Workaround: None.
•
Symptom: In DMM, if a server I/O to a LUN fails during data migration, that session is marked as failed. The DMM migration job is then moved to a Failed state when the remaining sessions are complete. Such a failed migration job can be scheduled for a restart. If such a failed migration job is scheduled to start in less than 5 minutes from the time of scheduling, and another server I/O to a session LUN fails in that 5 minute window, the migration job will move from a Scheduled state to a Failed state. An administrator has the option to start the job immediately or schedule it again. This problem does not happen if an administrator schedules the migration job to start more than 5 minutes from the time of scheduling.
Workaround: Schedule the data migration job to start more than 5 minutes from the time of scheduling.
•
Symptom: Dual-fabric DMM migration jobs can not have one fabric running Release 3.2(1a) and a peer fabric running Release 3.2(2c) due to a signal message change. This may cause unexpected results during a DMM migration job validation, creation, start, and so on.
Workaround: Run both fabrics with the same software image.
•
Symptom: SNMP timeouts occur when a AAA user ages out.
By design, a AAA user is aged out every hour on a switch for security reasons. If a large fabric is discovered using a AAA user and a Performance Monitoring (PM) collection is added for such a fabric, a number of SNMP requests (related to the discovery or PM statistics collection) could time out. When a user views the PM statistics charts (in the Performance tab in the web client), the charts are not seen as continuous.
Workaround: There are two workarounds for this issue. One or both of these workarounds can be used to mitigate this issue.
•
•
•
Symptom: Using Fabric Manager Release 3.2(2), an error is displayed in the creation wizard. This occurs when an enclosure spans multiple fabrics and not all fabrics are managed and when the Data Migration Wizard is used to create a job with that enclosure as the existing storage (selecting all ports listed in that enclosure).
Workaround: Put the ports you plan to use as the existing storage in the migration into a separate enclosure, and use that enclosure in the wizard selection.
•
Symptom: When an IVR-enabled MDS switch with an empty device alias database, attempts to join a fabric which has approximately 7000 device aliases, the device alias merge fails. In this situation, the following occurs:
–
–
–
–
–
Workaround: Enable device alias CFS distribution before enabling IVR.
•
Symptom: DMM jobs move to the Reset state and the following reason is displayed: Peer connection failure. In a Cisco DMM dual-fabric topology, the Storage Service Module (SSMs) in the two fabrics communicate with each other over IP by establishing a TCP connection. This connection is routed IP over FC to the local Supervisor and from the Supervisor it is switched over the IP mgmt interface. As a result, if there is a Supervisor switchover, the TCP connection may or may not survive the switchover. In the event that the TCP connection cannot be re-established in time, the DMM jobs in that SMM will move to the Reset state.
Workaround: None.
•
Symptom: Data Virtual Targets (DVTs) are lost after a downgrade from Release 3.3(1) to earlier releases
Workaround: None.
•
Symptom: In SAN-OS Release 3.2(3a) or earlier, Cisco DMM did not include Method1 and Method2 DMM jobs. In those releases, stored configurations were treated implicitly as Method1 DMM jobs. Configurations now stored by SAN-OS Release 3.3(1a) but read by Release 3.2(3a) or earlier, are assumed to be Method1 jobs.
Workaround: None.
•
Symptom: For a storage-based DMM job that is in the Scheduled state, if the server HBA port goes offline, then the scheduled DMM job will not start. Scheduled DMM jobs start only when all server HBA ports and storage ports are up.
Workaround: For scheduled DMM jobs, make sure all server HBA ports and storage ports (both existing and new storage) are up.
•
Symptom: When a PortChannel is created between 2 switches using the PortChannel wizard in Fabric Manager, the map might not immediately update and may not show the ISLs as part of the PortChannel. After a few discovery cycles, if the map is not updated, then the ISLs may be displayed along with the PortChannel in the map.
Workaround: Using Fabric Manager, remove the fabric and then re-discover the fabric.
•
Symptom: FCIP links might fail to come up after a module reload following a hardware failure on the module.
Workaround: Upgrade to NX-OS 4.1(1b) and reload the module where the failure occurred by entering the reload module command.
•
Symptom: In Cisco DMM, if a Data Migration Job is configured for an Active-Passive array, only the paths on the active controller of the storage are included as part of the job. (Refer to the Cisco MDS 9000 Family Data Mobility Manager Configuration Guide). As a result, if a LUN Trespass has occurred due to a controller fail-over, the host I/Os on the new path to the storage are not captured by DMM and they are not applied to the new storage.
Workaround: If a LUN trespass or controller-failover occurs during migration, destroy the job and recreate it to perform the migration again. This will ensure that the old and new storage are synchonized.
•
Symptom: In Microsoft Windows 2000, 2003, 2003 R2, and 2008, when installing Fabric Manager, Fabric Manager Server, and Device Manager, a service may not restart and/or may not properly execute the PostreSQL installer. This may lead to an incorrect conversion of the PostreSQL database and/or the service may not start. This occurs when running Microsoft Windows 2000, 2003, 2003 R2, or 2008 with Terminal Server running in Application mode.
Note
Workaround: Before you install Fabric Manager, Fabric Manager Server, and Device Manager when using Microsoft Terminal Server in Application mode, you must install the application for global use. This is required when a Service is installed and invoked, and when creating a local dbadmin user. To activate this setting, do the following:
1.
2.
Note
3.
4.
•
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: Under certain conditions, the port manager can take a long time to respond to a port configuration, which can trigger a set-port-configuration failure. If this occurs, then the FCIP tunnel will not come up and will stay in a disabled state.
Workaround: Enter a shut command, followed by a no shut command on the FCIP interface at either end of the FCIP tunnel.
•
Symptom: During an upgrade from SAN-OS Release 3.2(3a) to Release 3.3(1a), when a switchover occurs to the Supervisor running Release 3.3(1a), Cisco SME traffic flows for hosts that are not connected locally to the switch that is getting upgraded, may get flapped for a very short time. This can also occur during a switchover to a Supervisor running Release 3.3(1a).
Workaround: None.
•
Symptom: IVR does not finish a domain capture which stops the export of IVR devices.
Workaround: To avoid the API errors that cause this ACL/IVR issue, enter the show system internal capability command on the standby Supervisor and look at the last entry under each module. (You can ignore the Supervisor.) If the output states online then you can do a switchover or an upgrade.
•
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: When you issue the show tech-support sme or the show klm internal isapi_scsi command after attaching to a module, you may see this error message: cat: write error: Bad address. This issue does not affect the actual tech-support log.
Workaround: None.
•
Symptom: In certain tape libraries, the tape drives are exported as LUNs. If these target ports are already a part of a Cisco SME configuration and new tape drives are added as LUNs, the new tape drives will not be discovered during a Cisco SME tape group or tape device configuration.
Workaround: Perform a rescan at the host level or a flap of the target port to allow Cisco SME to rediscover these newly added tape drives.
•
Symptom: The following syslog message is displayed: %SME_CPP-SLOT13-3-LOG_ERR_SME_ITL_CPP_ERR: Module:13 Host-Target IT Nexus I:0xc1f3202015180006 T:0xc5a0202000010006 vsan:3000 oid:0x117 LunID:0x0000. This message is for debugging purposes and is also displayed during the upgrade of an MSM-18/4 module. An upgrade of the MSM-18/4 module where Cisco SME is enabled, is disruptive; however, this syslog message does not indicate an issue.
Workaround: None.
•
Symptom: The following Fabric Manager client components that use SSH and Telnet do not work well with NAT:
•
•
•
Workaround: None.
•
Symptom: In rare cases, if a READ command issued by Cisco SME for media identification is dropped or lost, the tape is marked as a clear-text tape. Subsequently, a CHECK_CONDITION with ILI is returned when a READ is issued by the host. This can cause a backup application to mark the tape as read-only.
Workaround: Unmount and remount the tape from the backup application to resolve this issue.
•
Symptom: In rare cases, when Cisco SME attempts to perform a tape device discovery of the backend tapes, a SCSI command can stall. This may cause Cisco SME to remain in the device discovery phase.
Workaround: Reload the module.
•
Symptom: In certain cases with the Tape Recycle policy enabled in Cisco SME, a new key is generated when a tape is recycled and the old key is not purged.
Workaround: Manually purge the older version of the key.
•
Symptom: After a 24-port 4-Gbps Fibre Channel module was replaced by a 12-port 4-Gbps Fibre Channel module on a switch with a Supervisor 2 module, the running configuration and the startup configuration were different.
Workaround: Purge the entries by inserting a new module with an equal number or more ports than are present on the module being replaced.
Related Documentation
The documentation set for the Cisco MDS 9000 Family includes the following documents. To find a document online, use the Cisco MDS SAN-OS Documentation Locator at: http://www.cisco.com/en/US/products/ps5989/products_documentation_roadmap09186a00804500c1.html.
For information on IBM TotalStorage SAN Volume Controller Storage Software for the Cisco MDS 9000 Family, refer to the IBM TotalStorage Support website: http://www.ibm.comRelease Notes
•
•
•
Compatibility Information
•
•
•
•
Regulatory Compliance and Safety Information
•
Hardware Installation
•
•
•
•
•
•
Cisco Fabric Manager
•
•
•
•
Command-Line Interface
•
•
•
•
•
•
•
Intelligent Storage Networking Services
•
•
•
Troubleshooting and Reference
•
•
•
•
•
•
Installation and Configuration Note
•
•
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.
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.
© 2008 Cisco Systems, Inc. All rights reserved.
