 Feedback
|
Table Of Contents
Cisco MDS 9000 Family Release Notes
for Cisco MDS SAN-OS Release 3.3(2)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(2)
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(2)
Upgrading to Recover Loss of Performance Manager Data
Maximum Number of Zones Supported in Interop Mode 4
Upgrading the SAN-OS Software on the MDS 9222i Switch
Storage Media Encryption Not Supported
Cisco MDS 9222i Module Upgrade
Deleting SANTap Configurations Is Required Before Downgrade
Compatibility of Fabric Manager and Data Mobility Manager
PPRC Not Supported with FCIP Write Acceleration
Using IVR In a Fabric With Mixed Code Versions
HTTP Transport Method Not Supported in Call Home
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(2)
Release Date: November 11, 2008
Part Number: OL-14116-10 Y0
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/ps5989/prod_release_notes_list.html
Table 1 shows the online change history for this document.
Table 1 Online History Change
A0
11/11/2008
Created release notes.
B0
11/12/2008
Added DDTS CSCsr89410 and CSCsr92585.
C0
11/14/2008
Added DDTS CSCso72230.
Corrected the DDTS number of CSCsm32705.
D0
11/18/2008
Removed DDTS CSCsk90998.
E0
11/24/2008
Added DDTS CSCso69978.
F0
11/25/2008
Added DDTS CSCso66705.
G0
02/04/2009
Added "Deleting SANTap Configurations Is Required Before Downgrade" to the Limitations and Restrictions section.
H0
02/24/2009
Added DDTS CSCsq47769.
I0
03/17/2009
Changed the state of DDTS CSCsc17059 to Resolved.
J0
03/25/2009
Added DDTS CSCsw95386.
Added the "Storage Media Encryption Not Supported" limitation.
K0
04/10/2009
Removed descriptions of limitations associated with SME because it is not supported in this release.
L0
04/16/2009
Added "FICON Supported Releases and Upgrade Paths".
Revised "FICON Downgrade Paths".
M0
04/24/2009
Added DDTS CSCsz01738.
Added the"Compatibility of Fabric Manager and Data Mobility Manager" limitation.
N0
06/23/2009
Added a statement not to use Java 1.6 Update 13 to the "The Fabric Manager Installation Process Overview" section.
O0
07/08/2009
Updated the "SANTap Support" limitation.
P0
07/22/2009
Added DDTS CSCsr85709.
Q0
08/14/2009
Removed DDTS CSCsm17768 because it was Resolved in SAN-OS Release 3.3(1a).
R0
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.
S0
10/09/2009
Added DDTS CSCsv66455.
T0
11/17/2009
Added DDTS CSCsu38485, CSCtb28442, CSCtb77695, and CSCtc20849.
U0
01/26/2010
Added DDTS CSCsy37212.
V0
07/27/2010
Added DDTS CSCsq74312.
W0
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.
X0
11/03/2010
Added the Supervisor-2A module to Table 2.
Y0
11/29/2011
•
•
•
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.2
MDS 9500 Supervisor/Fabric-2, SAN-OS software.
MDS 9500 Series only
M95S1K9-3.3.2
MDS 9500 Supervisor/Fabric-I, SAN-OS software.
MDS 9500 Series only
M92S2K9-3.3.2
MDS 9222 Supervisor/Fabric-2, SAN-OS software.
MDS 9200 Series only
M92S1K9-3.3.2
MDS 9216 Supervisor/Fabric-I, SAN-OS software.
MDS 9200 Series only
M91S2K9-3.3.2
MDS 9100 Supervisor/Fabric-2, SAN-OS software.
MDS 9100 Series only
M91S1K9-3.3.2
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 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(2) 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.1c.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>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>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(2):
•
•
•
•
•
–
–
–
–
–
Use Table 7 to determine your nondisruptive upgrade path to Cisco SAN-OS Release 3.3(2). Find the image release number you are currently using in the Current column of the table and use the path recommended.
Note
•
•
If an upgrade is attempted when an active configurations is present, the switch will go into a disruptive upgrade.
Note
FICON Supported Releases and Upgrade Paths
Cisco MDS SAN-OS Release 3.3(2) 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(2). 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(2)
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)# shutdownStep 4
switch# 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(2) 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(2)), 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(2):
•
•
•
•
•
•
–
–
–
–
–
–
Use Table 9 to determine the nondisruptive downgrade path from Cisco SAN-OS Release 3.3(2). 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(2) 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(2)
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
There are no new features in Cisco MDS SAN-OS Release 3.3(2).
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.
Upgrading the SAN-OS Software on the MDS 9222i Switch
On an MDS 9222i switch, an upgrade from SAN-OS Release 3.2(x), Release 3.3(1a), or Release 3.3(1c) to SAN-OS Release 3.3(2) 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:
FC-Redirect configuration for hosts or target connected locally
FC-Redirect configuration created by application running on that switch.
If an upgrade is attempted when an active configurations is present, the switch will go into a disruptive upgrade.
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(2) 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.
You can nondisruptively upgrade from SAN-OS Release 3.3(2) to SAN-OS Release 3.3(2E2). Likewise, you can nondisruptively downgrade from SAN-OS Release 3.3(2E2) to SAN-OS Release 3.3(2).
Cisco MDS 9222i Module Upgrade
On the MDS 9222i module, an upgrade from SAN-OS Release 3.2(x) to Release s 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 Support
The SANTap feature allows third-party data storage applications, such as long distance replication and continuous backup, to be integrated into the SAN. Cisco SAN-OS Release 3.3(2) supports SANTap; however, SSI Release 3.3(2) does not support SANTap.
Deleting SANTap Configurations Is Required Before Downgrade
If you are running Cisco MDS NX-OS Release 4.1(1b) in combination with the SSI 4.1(1b) image and you wish to downgrade to Cisco SAN-OS Release 3.3(2) and an SSI 3.2(3*) image, you must delete all SANTap configurations prior to the downgrade. Downgrading without completely deleting the SANTap configurations is not supported.
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.
HTTP Transport Method Not Supported in Call Home
Cisco SAN-OS Release 3.x does not support the HTTP transport method in the Call Home feature.
Caveats
This section lists the open and resolved caveats for this release. Use Table 10 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: An MDS 9124 switch, MDS 9134 switch, MDS 9222i switch, Cisco Fabric Switch for IBM BladeCenter, or Cisco Fabric Switch for HP c-Class BladeSystem, may reboot with reason Unknown or Watchdog Timeout when the switch has been up for 497 days. The following messages may be displayed:
switch#show system reset-reason
--- reset reason for Supervisor-module 1 (from Supervisor in slot 1) ---
1) No time
Reason: Unknown
Service:
Version: 3.1(2)
or
switch# show system reset-reason
----- reset reason for Supervisor-module 1 (from Supervisor in slot 1) ---
1) At 203437 usecs after Fri Jul 4 18:32:02 2008
Reason: Watchdog Timeout
Service:
Version: 3.1(2)
Entering the show logging onboard command will contain a card uptime record with an uptime of 497 days.Thu Sep 25 19:09:33 2008: Card Uptime Record
----------------------------------------------
Uptime: 42946218, 497 days 1 hour(s) 30 minute(s) 18 second(s)
Reset Reason: Unknown (0)
Card Mode..........................: RuntimeWorkaround: This issue is resolved.
•
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: This issue is resolved.
•
Symptom: Under certain rare circumstances, where there are excessive packet drops in the fabric for a given I/O, port software failure (or in other words, SME engine reset) may be seen due to a race condition between the host side and target side error handling of the exchange. This issue has been observed in stress test scenarios where there are packet drops in the host side and lot of target check conditions for the same I/O.
Workaround: This issue is resolved.
•
Symptom: Following an upgrade from SAN-OS Release 3.2(1) to any higher SAN-OS or NX-OS release on a switch that is deployed in a fabric that is operating in IVR1 (non-NAT) mode, the Fibre Channel name service (FCNS) database may contain partial entries. In particular, the port type is displayed as a dash (-) in the FCNS database.
Workaround: This issue is resolved.
•
Symptom: CPP SME may crash when the port software failure coincides with the forwarding of a SCSI error response from the target.
Workaround: This issue is resolved.
•
Symptom: If you have more than 7 SME modules in a switch, Fabric Manager Web Client hangs when the cluster summary page is selected.
Workaround: This issue is resolved.
•
Symptom: The snmp-server enable trap CLI command does not support enabling or disabling of traps from the CISCO-IPSEC-PROVISIONING-MIB.
Workaround: This issue is resolved.
•
Symptom: The snmp-server enable trap CLI command does not support enabling or disabling of traps from the CISCO-IMAGE-UPGRADE-MIB.
Workaround: This issue is resolved.
•
Symptom: In rare instances, when the host-side exchange and the target-side exchange map to the same internal hash index, a port software failure due to a watchdog timeout may occur. This issue occurs with a lot of traffic flows through the same SME engine.
Workaround: This issue is resolved.
•
Symptom: On an MDS 9000 Family switch, after configuring and enabling the Virtual Routing Redundancy Protocol (VRRP) on a Gigabit Ethernet interface, IPS module fails and errors similar to the following are logged:
%ETHPORT-5-IF_DOWN_SOFTWARE_FAILURE: Interface GigabitEthernet1/1 is down (Port software failure)This issue affects only the MDS 9222i switch and the DS-X9304-18K9 MSM-18/4 module. It occurs only if the IP default gateway is configured in the same subnet as the VRRP IP address. In most configurations, the IP default gateway is in the mgmt0 subnet. When the IP default gateway is in the mgmt0 submit, this issue does not occur.
Workaround: This issue is resolved.
•
Symptom: Under rare circumstances, the internal CompactFlash on the supervisor module can become unresponsive. When this occurs, it is possible for the Online Health Management System (OHMS) process that is monitoring the CompactFlash to hang. The system manager process will detect heart beat failures in the OHMS and will stop and restart it. A core file is created during the restart process.
A file system driver will detect that the CompactFlash has become unresponsive and will mount the root file system as read only. In addition, the show system health internal plog command might fail while trying to access persistent log files from the unresponsive CompactFlash. These files will be shown as vsh process cores in the output of the show cores command, which is part of the show tech-support command.
The show logging logfile command will display the following output:
2009 Jan 21 18:08:20 mds1 %SYSMGR-3-HEARTBEAT_FAILURE: Service "SystemHealth" sent SIGABRT for not setting heartbeat for last 3 periods.2009 Jan 21 18:08:29 mds1 %KERN-3-SYSTEM_MSG: Aborting journal on device ide1(22,3).2009 Jan 21 18:08:29 mds1 %KERN-2-SYSTEM_MSG: ext3_abort called.2009 Jan 21 18:08:29 mds1 %KERN-2-SYSTEM_MSG: EXT3-fs abort (device ide1(22,3)): ext3_journal_start: Detected aborted journal2009 Jan 21 18:08:29 mds1 %KERN-2-SYSTEM_MSG: Remounting filesystem read-only2009 Jan 21 18:08:29 mds1 %SYSMGR-3-SERVICE_CRASHED: Service "SystemHealth" (PID 1433) hasn't caught signal 6 (core saved).2009 Jan 21 18:08:29 mds1 %SYSTEMHEALTH-4-OHMS_LC_DAEMON_RESTARTED: System Health process running on module 5 restarted.The show cores command will display the following output:
Module-num Process-name PID Core-create-time---------- ------------ --- ----------------5 SystemHealth 1433 Jan 21 18:085 vsh 27794 Jan 26 12:115 vsh 27797 Jan 26 12:11This issue is limited to Generation 1 supervisors modules running SAN-OS releases prior to SAN-OS Release 3.3(2), and affects supervisor modules on the following MDS components:
–
–
–
–
–
–
Workaround: This is issue is resolved in SAN-OS Release 3.3(2) and NX-OS Release 4.1(1b).
•
Symptom: Tape device cannot be deleted because an SME process is stuck in wait for discovery.
Workaround: This issue is resolved.
•
Symptom: The SSH key information is not consistent between the CLI and the SNMP agent. Starting with Release 3.4.1, Fabric Manager and Device Manager will only manage MDS switches running Release 3.4.1 or later for the SSH feature. SSH1(rsa1) support is removed from the CLI, Fabric Manager, and Device Manager starting with Release 3.4.1 to conform with security practices.
Workaround: This issue is resolved.
•
Symptom: When a tape drive has been created in SME, adding additional paths to the tape drive from newly added hosts does not work from the Fabric Manager Web Client. This indicates that the tape device discovery wizard cannot be used to add these new paths.
Workaround: This issue is resolved.
•
Symptom: When trying to see if a Watchdog Timeout has occurred on a DS-X9032-SSM module, you may see the following error which indicates the 3rd partition has not been created on the Modflash: file system.
MDS-Switch# attach mod 1Attaching to module 1 ...To exit type 'exit', to abort type '$.'module-1# show system internal watchdog-timeoutUnable to seek /dev/hdc3, error 22Or
module-2# show system internal watchdog-timeoutUnable to read /dev/hdc3, error 61This is known to occur on SAN-OS Release 3.0(2a) with the SSI Release 3.0(2) and on the SAN-OS Release 3.1(3a) and SSI Release 3.1(3).
Workaround: This issue is resolved.
•
Symptom: There is a decrease in the FCIP tunnel throughput when IPSec is configured.
Workaround: This issue is resolved.
•
Symptom: Certain XSS and XSRF vulnerabilities were found in the Fabric Manager web client.
Workaround: This issue is resolved.
•
Symptom: Though the INTEGER is defined as (-2147483648..2147483647) in SNMPv2-SMI, the range is restricted to a 16Bit value 231 -1 = 2147483647 in the msgId field of the SNMP PDU (as seen in RFC3412).
In the SAN-OS SNMP stack implementation, the agent can potentially return the entire range of INTEGER as the value of msgId before it starts rolling over. This applies to all SNMP notifications generated from MDS switches. This is seen in SAN-OS Release 2.x and 3.x releases.
Workaround: This issue is resolved.
•
Symptom: The FCNS process may fail and dump a core. The process is then gracefully restarted by the system. Because this condition takes a relatively long time to develop, it is unlikely that the FCNS process will fail frequently enough to cause the active supervisor to reboot.
Workaround: This issue is resolved.
•
Symptom: After the first 200 RMON alarms, the SNMP process will start leaking small amounts of memory for each alarm. This eventually causes the SNMP process on the Supervisor module to reach its maximum memory allocation and fail. The Supervisor module will automatically be restarted by SAN-OS. In rare cases, part or all of the SNMP or RMON configuration may be lost. If the SNMP process fails quickly in succession, the active Supervisor module may also reset. If there is a redundant Supervisor module, this will result in a Supervisor switchover.
This occurs only when many RMON alarms are being generated. the SNMPD process may take seconds to hours to fail, depending on the rate of RMON alarms.
This is seen after a SAN-OS upgrade or after RMON alarms have been configured.
Workaround: This issue is resolved.
•
Symptom: A scheduled web report fails to generate when the fabric is deleted from Fabric Manager. The log records Fabric not found fabricID=xxx.
Workaround: This issue is resolved.
•
Symptom: The output of the show role session status command might not have the correct time for the last roles in the CFS session.
Workaround: This issue is resolved.
•
Symptom: A Supervisor 2 module running on an MDS 9500 switch will reload with Watchdog Timeout reason listed as:
`show system reset-reason`----- reset reason for Supervisor-module 7 (from Supervisor in slot 7)---1) At 363570 usecs after Tue May 6 01:21:22 2008Reason: Watchdog TimeoutService:Version: 3.2(2c)2) At 347955 usecs after Tue May 6 01:18:48 2008Reason: Watchdog TimeoutService:Version: 3.2(2c)3) At 110808 usecs after Tue May 6 01:16:13 2008Reason: Watchdog TimeoutService:Version: 3.2(2c)4) At 756666 usecs after Tue May 6 01:13:39 2008Reason: Watchdog TimeoutService:Version: 3.2(2c)Workaround: This issue is resolved.
•
Symptom: During an upgrade for Release 3.1(3a) to Release 3.2(3a), the standby Supervisor modules is reset due to a global synchronization failure. The following message will be displayed:
2008 Apr 30 23:21:39 EX0-ECA-01A %SYSMGR-2-GSYNC_ABORT: Global sync aborted by signal.2008 Apr 30 23:21:40 EX0-ECA-01A %PLATFORM-5-MOD_REMOVE: Module 5 removed (Serial number JAB091802TC)If you issue the show system reset reason command, an incorrect reason for the reset is shown.
Workaround: This issue is resolved.
•
Symptom: A DS-X9124 module (module 1 in this case) experienced a D-cache parity error and reloaded by itself. Examples of the log messages are seen below:
2008 May 6 09:28:09 SWITCH %MODULE-4-MOD_WARNING: Module 8 (serial: JABxxxxxxxx) reported warnings on ports 8/1-8/3 (Unknown) due to BE2 Arbiter experienced an error in device 65 (device error 0xc4102613)2008 May 6 09:28:09 SWITCH %MODULE-4-MOD_WARNING: Module 7 (serial: JABxxxxxxxx) reported warnings on ports 7/1-7/3 (Unknown) due to BE2 Arbiter experienced an error in device 65 (device error 0xc4102613)2008 May 6 09:28:14 SWITCH %XBAR-5-XBAR_STATUS_REPORT: Module 1 reported status for component 88 code 0x40240015.2008 May 6 09:28:14 SWITCH %MODULE-2-MOD_DIAG_FAIL: Module 1 (serial: JABxxxxxxxx) reported failure on ports 1/1-1/24 (Fibre Channel) due to Fatal runtime Arb error. (DevErr is bitmap of failed modules) in device 88 (device error 0x1)This caused several other DS-X9124 modules (slots 2-6 in this case) to reset. Examples of log messages are seen below:
2008 May 6 09:28:31 SWITCH %MODULE-5-MOD_REINIT: Re-initializing module 5 (serial:JABxxxxxxxx)2008 May 6 09:28:31 SWITCH %MODULE-5-MOD_REINIT: Re-initializing module 6 (serial:JABxxxxxxxx)2008 May 6 09:28:31 SWITCH %MODULE-5-MOD_REINIT: Re-initializing module 4 (serial:JABxxxxxxxx)2008 May 6 09:28:31 SWITCH %MODULE-5-MOD_REINIT: Re-initializing module 3 (serial:JABxxxxxxxx)2008 May 6 09:28:31 SWITCH %MODULE-5-MOD_REINIT: Re-initializing module 2 (serial:JABxxxxxxxx)This issue will change an arbiter timeout value from 5 seconds to 1.5 seconds in order to prevent other modules from resetting when one resets.
Workaround: This issue is resolved.
•
Symptom: If some database processes are shut down uncleanly (for example, the host crashes or a process is killed) the following message may be seen:
com.cisco.dcbu.lib.rrd.core.RrdException: Bad sample timestamp 1210312407. Last update time was 9221120237041090560, at least one second step is requiredThis means that an RRD file has been corrupted.
Workaround: This issue is resolved.
•
Symptom: The Control Virtual Target (CVT) creation fails.
Workaround: This issue is resolved.
•
Symptom: The Fabric Manager web client shows Fabric Events with the next description:
VSAN ... zone activation success, local switch is 00:00:00:00:00:00:00:00
This issue might occur if the enhanced zone mode is configured for a VSAN.
Workaround: This issue is resolved.
•
Symptom: If the KMC response comes back with a failure after 10 seconds, it might get stuck in a locked state.
Workaround: This issue is resolved.
•
Symptom: Typing the Nexus 5000 switch IP address in the browser address bar shows a download page which says Cisco Device Manager for MDS 9000 Series
Workaround: This issue is resolved.
•
Symptom: When running Fabric Manager 3.2(3) and SAN-OS 3.2(3), go to Fabric Manager > Physical Devices Panel > End Devices > Hosts. The panel that displays in the top right showing the Nx ports does not display all fields for 4GB Qlogic modules. It does not show Model, Firmware or Driver for 4GB Qlogic cards. 2GB Qlogic modules for same switch and FM, show Model, Firmware and Driver.
If you look in Device Manager > FC > Name Server > Advanced tab. In the SymbolicNodeName column you can see HPAE311A FW:v4.00.23 DVR:v9.1.3.16 for the card that does not display correctly in Fabric Manager.
On the switch, if you enter show fcns data detail command you can see the symblic-node-name for the missing HBA. ------------------------ VSAN:10 FCID:0x0a0011 ------------------------ port-wwn (vendor) :50:01:10:a0:00:16:d0:f6 [HOSBILLYGIRL] node-wwn :50:01:10:a0:00:16:d0:f7 class :3 node-ip-addr :0.0.0.0 ipa :ff ff ff ff ff ff ff ff fc4-types:fc4_features :scsi-fcp:init symbolic-port-name : symbolic-node-name :HPAE311A FW:v4.00.23 DVR:v9.1.3.16 port-type :N port-ip-addr :0.0.0.0 fabric-port-wwn :23:03:00:0d:ec:3b:ad:40 hard-addr :0x000000 permanent-port-wwn (vendor) :50:01:10:a0:00:16:d0:f6The SymbolicNodeName in Device Manager does not get populated into Fabric Manager for Model,
Firmware, and Driver.Workaround: This issue is resolved.
•
Symptom: License records are not removed if a fabric is purged from the database. License information might be incorrect if the same fabric is added back in to Fabric Manager at a later time.
Workaround: This issue is resolved.
•
Symptom: The error messages for Device-Alias Merge failures need to be more be enhanced to allow customers to pinpoint offending Device Aliases or pWWNs associated with the merge failure.
Workaround: This issue is resolved.
•
Symptom: DPVM Merge failure messages need to be enhanced to help customers determine why the merge failed.
Workaround: This issue is resolved.
•
Symptom: Errors on the management port (mgmt0 or eth1) may be seen in the output of the show logging log command.
%KERN-3-SYSTEM_MSG: eth1: error in ethGetNextRxBuf %KERN-3-SYSTEM_MSG: eth1: stop internals failed %KERN-3-SYSTEM_MSG: eth1: error in rx %KERN-3-SYSTEM_MSG: eth1: error in rx %KERN-3-SYSTEM_MSG: eth1: error in rx %KERN-3-SYSTEM_MSG: eth1: error in rx %KERN-3-SYSTEM_MSG: eth1: error in rxIn rare cases this may result in a kernel panic which causes a supervisor switchover.
Workaround: This issue is resolved.
•
Symptom: The syslog dialog box in Device Manager does not display all logs.
Workaround: This issue is resolved.
•
Symptom: When an FCIP tunnel is configured with IPsec between an MDS 9222i switch and an MDS 9216i switch, it fails to come up if an ACL with TCP permit is configured. This causes a mismatch and causes the security association (SA) policy creation to fail in IPsec on the supervisor.
Workaround: This issue is resolved.
•
Symptom: A Solaris iSCSI host generates this error: iscsi: [ID 498442 kern.warning] WARNING: iscsi session(5) protocol error - received unknown itt:0x0 - protocol error.
Workaround: This issue is resolved
•
Symptom: Software failures occurred on a Gigabit Ethernet port when FCIP compression mode auto was used.
Workaround: This issue is resolved.
•
Symptom: If you have host to storage connectivity issues, check the following counters to see if you have increasing packet drops throughout the path that these devices traverse. Use the show hardware internal packet-flow dropped command and the show hardware internal errors all command to check the counters.
Workaround: This issue is resolved.
•
Symptom:
Workaround: This issue is resolved.
•
Symptom: Under rare situations, the MDS 9124 switch might reboot. If you enter the show system exception-info command, the log might show information similar to the following:
Time of exception: Fri Oct 24 07:06:30 2008(second=1224803190)CPU register dump:1224803190:00958261 machine check: process feature_mgr (1343), jiffies 0x3d7a6760Free pages in zone[0]:0x6ce1,zone[1]:0x0,zone[2]:0x0Call Trace: [<c0007298>] [<c0018e44>] [<c000464c>] [<c00041f8>] [<c0055998>] [<c000b474>] [<c0003f48>] [<10005504>] [<100059fc>] [<0fda00e8>] [<00000000>].......................Workaround: This issue is resolved.
•
Symptom: You cannot see information about the default access list for the management interface (mgmt0)which is applied by the system to the management interface (mgmt0)in the absence of any user access list.
Workaround: This issue is resolved.
•
Symptom: An RDL process crashed because of too many fcpings in a loop. This issue might occur on a switch when fcping is running in a script.
Workaround: This issue is resolved.
•
Symptom: A network management application may occasionally detect 100% CPU utilization when monitoring an MDS switch via SNMP. The show process cpu command does not show a high load. An MDS switch periodically adjusts the hardware clock which can cause the CPU load to reach 100% for less than 1 second. An agent, such as nms, rmon alarm or CLI user, examining the CPU load at this instant will see false CPU load alarms.
Workaround: This issue is resolved.
•
Symptom: The Recoverpoint Appliance with a QLogic HBA sends an 8 byte RFT_ID instead of the standard 32bytes, which causes FC4 features to be incorrectly registered with all features.
Workaround: This issue is resolved.
•
Symptom: In IVR NAT environment, after active mode PortChannel flaps, some member of the PortChannel may not get programmed in the IVR table, so that related IVR traffic will get lost.
Workaround: This issue is resolved.
•
Symptom: A Fiber Channel over IP (FCIP) trunk can go down if the maximum transmission unit (MTU in the path is less than the MTU of the MDS Gigabit Ethernet interface.
Workaround: This issue is resolved.
•
Symptom: If a sync-loss is received for a nonexisting fabric, the xbar-manager transitions to a state from which it does not exit.
Workaround: This issue is resolved.
•
Symptom: An Octeon core occurred.
Workaround: This problem is resolved.
•
Symptom: A slow memory leak has been found as a part of the view of the interface table MIB with the SME interfaces. This eventually results in the SNMPD process resetting due to lack of memory.
Workaround: This issue is resolved.
•
Symptom: After issuing the show boot command, there are duplicate image names listed in the switch output as shown below:
switch# show bootsup-1kickstart variable not setsystem variable = bootflash:/m9500-sf1ek9-mzg.3.4.1.bin;bootflash:/m9500-sf1ek9-mzg.3.4.1.binsup-2kickstart variable not setsystem variable = bootflash:/m9500-sf1ek9-mzg.3.4.1.bin;bootflash:/m9500-sf1ek9-mzg.3.4.1.binNo module boot variable setswitch#This occurs if you issue the boot system command twice with the same image name as shown below:
switch(config)# boot system bootflash:m9500-sf1ek9-mzg.3.4.1.binswitch(config)# boot system bootflash:m9500-sf1ek9-mzg.3.4.1.binWorkaround: This issue is resolved.
•
Symptom: All device aliases in Fabric Manager disappear when adding new device aliases.
Workaround: This issue is resolved.
•
Symptom: Fabric Manager does not update Port Channel changes.
Workaround: This issue is resolved.
•
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: This issue is resolved.
The software workaround for this issue helps reduce instances of module reloads, but does not completely eliminate the problem. Consequently, module reloads might still occur.
•
Symptom: Selecting disks as a part of the tape device configuration causes a CPP SME process failure.
Workaround: This issue is resolved.
•
Symptom: When fctimer CFS distribution is enabled, no commit can be successful, and no change can be made. The error message is as following:
dctl-m9509-190-NAC-B1(config)# fctimer E_D_TOV 1050 vsan 1 Warning:The vsan will be temporarily suspended when updating the timer value This configuration would impact whole fabric. Do you want to continue? (y/n) y 2008 Jul 1 11:34:39 dctl-m9509-190-NAC-B1 %CFS-2-MTS_REJECT: Verification failed reject MTS message SAP 15:RR-token 0x64f82Workaround: This issue is resolved.
•
Symptom: For two FCIP links on different modules but sharing a common DS3 pipe, the MDS switch could not saturate the DS3 pipe. In another setup with no latency and min/max-bw configured to 15mbps, the MDS FCIP shaper does not obey bandwidth rules and sends at a rate greater than 15mbps, which caused unnecessary drops in the network. This issue affects the MSM-18/4 module and the MDS 9222i switch.
Workaround: This issue is resolved.
•
Symptom: With the Cimserver enabled, a zone is created and a device-alias member is added to the zone. Device-alias is in enhanced mode. While querying for ni/ei cisco_zonemembersettingdata, the Cimserver fails.
Workaround: This issue is resolved.
•
Symptom: An FCIP link with an underlying Ethernet interface set to a large MTU (9000 bytes) flaps whenever data frames are sent. Control traffic (such as tape status check commands) are successful and do not cause flaps. This issue only occurs on an MSM-18/4 modules.
Workaround: This issue is resolved.
•
Symptom: A CFS de-register message is not sent when IVR is disabled.
Workaround: This issue is resolved.
•
Symptom: The entries for all configurations are not removed from pss when a VSAN is deleted.
Workaround: This issue is resolved.
•
Symptom: A module gets stuck in the upgrading state if the LCM gets an error.
Workaround: This issue is resolved.
•
Symptom: A failure in the internal software on the MSM-18/4 module causes an FCIP link in the PortChannel to drop.
Workaround: This issue is resolved.
•
Symptom: A downgrade from NX-OS 4.1(1b) to SAN-OS 3.3(1c) is not supported on switches when FC-Redirect based applications like DMM and SME are configured in the fabric, if either of the following conditions are satisfied:
–
–
In such cases, remove the application configuration for such targets and hosts before proceeding with the downgrade.
Workaround: This issue is resolved.
•
Symptom: For a data stream that has a lot of variance in the compression ratio across individual tape blocks on the tape, SME restore performance for the HP LTO drives is substantially affected. However, backup performance is not affected.
Workaround: This issue is resolved.
•
Symptom: A downgrade from NX-OS 4.1(1b) to SAN-OS 3.1(1) is not supported If there are FC-Redirect configurations and any of the following conditions are true:
–
–
Downgrading in such cases might lead to traffic disruption and/or data corruption.
Workaround: This issue is resolved.
•
Symptom: In a dual FCIP link configuration with one of the ports is shutdown, the performance of the other still enabled active FCIP link degrades significantly (from ~12 Mb/sec to 1Mb/sec).
Workaround: This issue is resolved.
•
Symptom: Disabling Fabric Manager e-mails for Call Home on a port flap event through the server properties is not allowed.
Workaround: This issue is resolved.
•
Symptom: RMON can not be used to monitor objects for a group of ports of the same type.
Workaround: This issue is resolved.
•
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.
•
Symptom: The TSM catalog backup fails due to a limitation in SME where all tape blocks are expected to be 16-byte aligned. This issue has also been observed as part of the TSM Export Node process due to the same reason.
Workaround: None.
•
Symptom: PostgreSQL does not shutdown unless it can close all the connections it has. Usually it does not shutdown because it has a connection with Fabric Manager Server.
Workaround: This issue is resolved.
Open Caveats
•
Symptom: The management port hangs and does not transmit packets. The following syslog message displays: eth1: tx timeout.
Workaround: Flap the management port or perform a supervisor switchover.
•
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 : 4After 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.
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: 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: 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: After logging back into Fabric Manager Client, clicking on the Summary tab causes a disconnect.
Workaround: Exit from Fabric Manager Client then restart Fabric Manager Client and log in again.
•
Symptom: When the startup rising alarm is triggered, the sample value is smaller than the rising threshold. This should not trigger an alarm.
Workaround: None.
•
Symptom: Flow statistics on a Generation 2 module may not be accurate if any of the flows that participate in flow statistics on the module have multiple FSPF paths.
Workaround: For all flows that have flow statistics configured on that module, make sure there is only one available FSPF path. Use port-channel instead of multiple links to achieve more bandwidth.
•
Symptom: On Solaris 8, 9, and 10 and RedHat Linux AS4 (kernel version 2.6) the Fabric Manager Release 3.4(1) installer displays a warning message indicating that it is an unsupported platform. This occurs even though these platforms are supported.
Workaround: Ignore the warning message and click Continue.
•
Symptom: An FCIP link may flap due to a watchdog timeout condition when FCIP Tape Acceleration is running in SAN-OS Release 3.3(1c).
Workaround: Disable FCIP Tape Acceleration.
•
Symptom: An FCIP link running with Tape Acceleration may flap when the host is attempting SRR/REC tape error handling.
Workaround: None. If link stability is needed, disable FCIP Tape Acceleration.
•
Symptom: When you enter the install ssi command, bootvar fails to synchronize between the active and standby supervisor.
Workaround: After the install ssi command executes, verify that the SSI bootvar on the standby supervisor is set to the new SSI image. Enter the show boot command to display the bootvar configuration. If the SSI bootvar is not set to the proper SSI image, then use the boot ssi <uri> command to configure the SSI bootvar on the active supervisor again and verify.
•
Symptom: Certain applications that use SME perform a move medium operation to change tapes in a library, without first performing a load or unload operation. This causes the check condition "SCSI check condition of medium may have changed." SME does not perform the media identification logic correctly for this check condition, which causes tape labeling to fail.
Workaround: None.
•
Symptom: End of sequence is not set for STK drives when the host requests more data than what is written to the tape.
Workaround: None.
•
Symptom: When a tape reaches its capacity, an IBM TS1120 tape drive send a check condition with eom=1 and asc_ascq = 0. Because asc_ascq is not set to End of Medium or Partition, SME continues to send traffic as if the end of the tape has not been reached. As a result, the backup fails when it spans across multiple tapes. This issue is specific only to IBM TS1120 tape drives.
Workaround: None.
•
Symptom: Following a reboot of an MDS 9513 switch running Cisco SAN-OS Release 3.3(2), both supervisor modules generated core files. The show cores command and the show system reset-reason command displayed the following output:
switch# show coresModule-num Process-name PID Core-create-time---------- ------------ --- ----------------8 qos 15671 Sep 21 22:167 qos 4370 Sep 21 22:17switch# show system reset-reason----- reset reason for Supervisor-module 8 (from Supervisor in slot 8) ---1) At 517868 usecs after Mon Sep 21 22:12:09 2009Reason: Reset triggered due to HA policy of ResetService: Service "qos"Version: 3.3(2)----- reset reason for Supervisor-module 7 (from Supervisor in slot 7) ---1) At 260648 usecs after Mon Sep 21 22:12:37 2009Reason: Reset triggered due to HA policy of ResetService: Service "qos"Version: 3.3(2)Workaround: To mitigate the risk of a QoS failure, configure static persistent FC IDs so that the local logins do not share the same domain or area. There should be no more than 50 logins with the same area.
In addition, you can enter the show qos internal mem-stats detail | inc fcid command and then check the current allocation value of the QOS_MEM_qos_fcid in the output. If this value is close to 70000, then there is a high chance of a QoS failure, followed by a system reboot.
•
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: 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(1x) 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: 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 synchronized.
•
Symptom: FCIP links might fail to come up after a module reload following a hardware failure on the module.
Workaround: Upgrade to Cisco NX-OS Release 4.1(1b) and reload the module where the failure occurred by entering the reload module command.
•
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 PostgreSQL installer. This may lead to an incorrect conversion of the PostgreSQL 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) through Generation 2 modules. LUN 0x45F0 corresponds to HPUX 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: After creating SANTap Control Virtual Targets (CVTs) or SANTap Data Virtual Targets (DVTs), the running-configuration and the startup-configuration are not synchronized. Output from the show startup-config command will be different from the output of the show running-config and the startup configuration will not display SANTap configuration information.
Workaround: Issue the copy running-startup command whenever you create SANTap Control Virtual Targets (CVTs) or SANTap Data Virtual Targets (DVTs) so that the running configuration and the startup configuration are synchronized.
•
Symptom: On a DS-X9032 module where the SRAM parity error was seen, the SRAM parity error exceptions were logged continuously.
Workaround: None.
•
Symptom: After upgrading from Fabric Manager Release 3.0(2a) to Fabric Manager Release 3.2(3a), the Fabric Manager client fails to reuse the map layout files produced by Release 3.0(2a). Renaming the map layout files will make them compatible with Fabric Manager Release 3.2(3a).
Workaround: Exit all Fabric Manager clients and rename the map layout files by replacing space characters with an underscore. The map layout files are found on the computer running the Fabric Manager server. Each Fabric Manager user has their own directory of map files. These map files are found in the following directory: C:\Program Files\Cisco Systems\MDS 9000\db\<user>\*.map.
•
Symptom: On an MDS 9222i switch, an upgrade from SAN-OS Release 3.2(x), Release 3.3(1a), or Release 3.3(1c) to SAN-OS Release 3.3(1c) fails when there is an active FC-Redirect configuration (created by SME or DMM applications) on the switch. An active FC-Redirect configuration is defined as:
•
•
If an upgrade is attempted when an active configurations is present, the switch will go into a disruptive upgrade.
Workaround: Take the targets in FC-Redirect configurations offline.
•
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: Under rare conditions, a port may drop data after the port flaps in the presence of congestion. The output of the show hardware internal packet-flow dropped command shows the dropped data as RX (receive) frame drops on a module. In such instances, the following type 1, type 2, and possibly type 3 errors may be seen:
–
–
–
For this issue to occur, the port must have frames held in the port buffer at the time that the port is brought down and up. A port normally has time to empty its buffers when it is shut down. However, in unusual cases, such as if there is congestion on the port at the time of the shutdown, or in rare cases, frames can still be held in the buffers while the port is reinitialized.
Workaround: None. If you experience this issue, check the fabric for congestion and then remove the congestion. Reload the module to recover ports that are in a hardware failure state.
•
Symptom: A host that is behind a NPIV F port cannot see the zoned LUNs if the addition of the F port to the zone and the zone set activation occur after an In Service Software Upgrade (ISSU). This issue applies only to an NPIV F port on MDS 9124 and MDS 9134 fabric switches.
Workaround: Following the ISSU, enter the shut command followed by the no shut command on the NPIV F port, and then activate the zone set.
•
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
onlinethen 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.
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_roadmaps_list.htm
For information on IBM TotalStorage SAN Volume Controller Storage Software for the Cisco MDS 9000 Family, refer to the IBM TotalStorage Support website.
Release 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.
CCDE, CCENT, Cisco Eos, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, Cisco TelePresence, the Cisco logo, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website 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. (0807R)
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.
