 Feedback
|
Table Of Contents
Cisco MDS 9000 Family Release Notes
for Cisco MDS SAN-OS Release 3.1(2)Determining the Software Version
Selecting the Correct Software Image for an MDS 9100 Series Switch
Selecting the Correct Software Image for an MDS 9500 Series Switch
Migrating from Supervisor-1 Modules to Supervisor-2 Modules
Configuring Generation 2 Switching Modules
Upgrading Your Cisco MDS SAN-OS Software Image
Performing a Nondisruptive Software Upgrade on Generation 1 Modules
Upgrading Your Version of Cisco Fabric Manager
Reconfiguring SSM Ports Before Upgrading to SAN-OS Release 3.1(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.1(2)
Support for Cisco Fabric Switch for HP c-Class BladeSystem
Support for Cisco Fabric Switch for IBM BladeCenter
FCS Discovery of Virtual Devices
Compact Flash Report in Cisco Fabric Manager
Fabric Manager New Login Procedure
Virtual Router Redundancy Protocol (VRRP) Interfaces
QoS on an MDS 48-port Fibre Channel Module
Maximum Number of Zones Supported in Interop Mode 4
Configuring Default Settings for the Default Zone
PPRC Not Supported with FCIP Write Acceleration
Using IVR In a Fabric With Mixed Code Versions
Regulatory Compliance and Safety Information
Installation and Configuration Note
Cisco Product Security Overview
Reporting Security Problems in Cisco Products
Product Alerts and Field Notices
Obtaining Technical Assistance
Cisco Technical Support & Documentation Website
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Cisco MDS 9000 Family Release Notes
for Cisco MDS SAN-OS Release 3.1(2)
Release Date: February 05, 2007
Text Part Number: OL-12208-02 U0
This document describes the caveats and limitations for switches in the Cisco MDS 9000 Family. Use this document in conjunction with documents listed in the "Related Documentation" section.
Note
Release notes are sometimes updated with new information on restrictions and caveats. Refer to the following website for the most recent version of the Cisco MDS 9000 Family Release Notes: http://www.cisco.com/en/US/products/hw/ps4159/ps4358/prod_release_notes_list.html
Table 1 shows the online change history for this document.
Table 1 Online History Change
A0
02/05/2007
Created release notes.
B0
02/07/2007
Added a "Maximum Number of Zones Supported in Interop Mode 4".
Revised the description of the Upgrade Path in Table 6 and the description of the Downgrade Path in Table 7.
Added the Limitation "Using SDV on a Cisco MDS 9124 Switch, on a Cisco Fabric Switch for HP c-Class BladeSystem, or on a Cisco Fabric Switch for IBM BladeCenter".
C0
02/14/2007
Added CSCsh69086 and CSCsh71985.
D0
02/27/2007
Added CSCsh66920.
Removed CSCsg19148.
E0
03/30/2007
Added DDTS CSCsg29630, CSCsh02602, CSCsh21262, CSCsh24256, CSCsh62126, CSCsh66010, CSCsh66920, CSCsh82676, CSCsh83200, CSCsh85505, CSCsh86629, CSCsh93540, CSCsh94906, and CSCsi24128.
Added the section "Performing a Disruptive Upgrade on a Single Supervisor MDS Family Switch".
Added the section "Configuring Default Settings for the Default Zone".
F0
04/05/2007
Revised the section "Upgrading a Cisco MDS 9124 Switch".
Added the section "Fabric Manager New Login Procedure".
G0
05/03/2007
Added DDTS CSCsg52197.
H0
05/15/2007
Removed the Interop Mode 4 Support Limitation.
I0
05/31/2007
Added DDTS CSCsh75149, CSCsi27133, CSCsi31860, CSCsi33540, CSCsi41668, and CSCsi52049.
J0
07/18/2007
Added DDTS CSCsj04224, CSCsj07363, and CSCsj19105.
Removed DDTS CSCei82909.
K0
08/24/2007
Added DDTS CSCsh95415.
L0
09/24/2007
Added DDTS CSCsi72048.
M0
09/27/2007
Added DDTS CSCeh35635, CSCsg49151, CSCsg62704, CSCsh05721, CSCsh63658, CSCsi49231, CSCsi56949, CSCsj13175, CSCsj29134, CSCsj52389, CSCsj64048, CSCsj65565, and CSCsj95379.
N0
10/24/2007
Changed the status of DDTS CSCsh31236 to Resolved.
Added a Note about Downgrading from Cisco SAN-OS 3.2(1) to the "Downgrading Your Cisco MDS SAN-OS Software Image" section.
P0
04/23/2008
Added DDTS CSCsk48149.
Q0
04/30/2008
Added DDTS CSCso63465.
R0
11/13/2008
Added the "Performing a Nondisruptive Software Upgrade on Generation 1 Modules" section.
S0
11/18/2008
Added DDTS CSCso72230.
T0
07/30/2010
Added the "PPRC Not Supported with FCIP Write Acceleration" limitation.
Added the "Using IVR In a Fabric With Mixed Code Versions" limitation.
U0
11/04/2010
Added the Supervisor-2A module to Table 2.
Contents
This document includes the following sections:
•
•
•
•
•
•
Introduction
The Cisco MDS 9000 Family of Multilayer Directors and Fabric Switches provides industry-leading availability, scalability, security, and management, allowing you to deploy high performance storage-area networks with lowest total cost of ownership. Layering a rich set of intelligent features onto a high performance, protocol agnostic switch fabric, the Cisco MDS 9000 Family addresses the stringent requirements of large data center storage environments: uncompromising high availability, security, scalability, ease of management, and seamless integration of new technologies.
The Cisco MDS 9000 Family SAN-OS is the underlying system software that powers the Cisco MDS 9500 Series, 9200 Series, and 9100 Series multilayer switches. The Cisco SAN-OS provides intelligent networking features, such as multiprotocol and multitransport integration, virtual SANs (VSANs), advanced security, sophisticated debug analysis tools, and unified SAN management.
Components Supported
Table 2 lists the SAN-OS software part number and hardware components supported by the Cisco MDS 9000 Family.
Note
Table 2 Cisco MDS 9000 Family Supported Software and Hardware Components
Software
M95S2K9-3.1.2
MDS 9500 Supervisor/Fabric-2, SAN-OS software.
MDS 9500 Series only
M95S1K9-3.1.2
MDS 9500 Supervisor/Fabric-I, SAN-OS software.
MDS 9500 Series only
M92S1K9-3.1.2
MDS 9216 Supervisor/Fabric-I, SAN-OS software.
MDS 9200 Series only
M91S2K9-3.1.2
MDS 9100 Supervisor/Fabric-2, SAN-OS software.
MDS 9100 Series only
M91S1K9-3.1.2
NDS 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
M9500FMS1K9
Fabric Manager Server package.
MDS 9500 Series
M9200FMS1K9
Fabric Manager Server package.
MDS 9200 Series
M9100FMS1K9
Fabric Manager Server package.
MDS 9100 Series
M9500EXT1K9
SAN Extension over IP package for IPS-8 module.
MDS 9500 Series
M9200EXT1K9
SAN Extension over IP package for IPS-8 module.
MDS 9200 Series
M9500EXT14K9
SAN Extension over IP package for IPS-4 module.
MDS 9500 Series
M9200EXT14K9
SAN Extension over IP package for IPS-4 module.
MDS 9200 Series
M9500EXT12K9
SAN Extension over IP package for MPS 14+2 module.
MDS 9500 Series
M9200EXT12K9
SAN Extension over IP package for MPS 14+2 module.
MDS 9200 Series
M9500SSE1K9
Storage Services Enabler package.
MDS 9500 Series with SSM
M9200SSE1K9
Storage Services Enabler package.
MDS 9200 Series with SSM
M9124PL8-4G
On-Demand Ports Activation License
MDS 9124 Switch
HP-PL12-4G
On-Demand Ports Activation License
Cisco Fabric Switch for HP c-Class BladeSystem only
IBM-PL10-4G
On-Demand Ports Activation License
Cisco Fabric Switch for IBM BladeCenter only
Chassis
DS-C9513
MDS 9513 director (13-slot modular chassis with 11 slots for switching modules, and 2 slots reserved for Supervisor 2 modules only—SFPs1 sold separately).
MDS 9513 only
DS-C9509
MDS 9509 director, base configuration (9-slot modular chassis includes 7 slots for switching modules and 2 slots for supervisor modules—SFPs sold separately).
MDS 9509 only
DS-C9506
MDS 9506 director (6-slot modular chassis includes 4 slots for switching modules and 2 slots for supervisor modules—SFPs sold separately).
MDS 9506 only
DS-C9216-K9
MDS 9216 16-port semi-modular fabric switch (includes 16 1-Gbps/2-Gbps Fibre Channel ports, power supply, and expansion slot—SFPs sold separately).
MDS 9216 only
DS-C9216A-K9
MDS 9216A 16-port semi-modular fabric switch (includes 16 1-Gbps/2-Gbps Fibre Channel ports, power supply, and expansion slot—SFPs sold separately).
MDS 9216A only
DS-C9216i-K9
MDS 9216i 16-port semi-modular fabric switch (includes 14 1-Gbps/2-Gbps Fibre Channel ports, 2 Gigabit Ethernet ports, power supply, and expansion slot—SFPs sold separately).
MDS 9216i only
DS-C9140-K9
MDS 9140 fixed configuration (non-modular) fabric switch (includes 8 full rate ports and 32 host-optimized ports).
MDS 9140 only
DS-C9124-K9
MDS 9124 fixed configuration (non-modular) multilayer fabric switch (includes 8 enabled ports; an on-demand ports activation license can enable 8 additional ports, up to 24 ports).
MDS 9124 only
DS-C9120-K9
MDS 9120 fixed configuration, non-modular, fabric switch (includes 4 full rate ports and 16 host-optimized ports).
MDS 9120 only
DS-HP-FC-K9
Cisco Fabric Switch for HP c-Class BladeSystem (includes sixteen internal and eight external active ports and four 4-Gb SFPs installed, or eight internal and four external active ports and two 4-Gb SFPs installed).
Cisco Fabric Switch for HP c-Class BladeSystem only
DS-IBM-FC-K9
Cisco Fabric Switch for IBM BladeCenter (includes fourteen internal and six external ports)
Cisco Fabric Switch for IBM BladeCenter only
External crossbar module
DS-13SLT-FAB1
MDS 9513 crossbar fabric module.
MDS 9513 only
Supervisor modules
DS-X9530-SF2-K9
MDS 9500 Supervisor-2 module.
MDS 9500 Series only
DS-X9530-SF2A-K9
MDS 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
DS-X9124
MDS 9000 24-port 4-Gbps Fibre Channel module (SFPs sold separately).
MDS 9500 Series and 9200 Series, except for the MDS 9216
DS-X9148
MDS 9000 48-port 4-Gbps Fibre Channel module (SFPs sold separately).
MDS 9500 Series and 9200 Series, except for the MDS 9216
DS-X9704
MDS 9000 4-port 10-Gbps Fibre Channel module (SFPs sold separately)
MDS 9500 Series and 9200 Series, except for the MDS 9216
Services modules
DS-X9308-SMIP
8-port Gigabit Ethernet IP Storage services module.
MDS 9500 Series and 9200 Series
DS-X9304-SMIP
4-port Gigabit Ethernet IP Storage services module.
DS-X9032-SSM
MDS 9000 32-port 1-Gbps/2-Gbps Fibre Channel Storage Services Module (SSM).
DS-X9302-14K9
14-port Fibre Channel/2-port Gigabit Ethernet Multiprotocol Services (MPS-14/2) module.
Optics
DS-X2-FC10G-SR
X2/SC optics, 10-Gbps Fibre Channel for Short Reach.
MDS 9500 Series and 9200 Series, except for the MDS 9216
DS-X2-FC10G-LR
X2/SC optics, 10-Gbps Fibre Channel for Long Reach.
DS-X2-FC10G-ER
X2/SC optics, 10-Gbps Fibre Channel for Extended Reach (40 km).
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
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 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-FLD512M
MDS 9500 supervisor CompactFlash disk, 512 MB.
MDS 9500 Series only
Port analyzer adapter
DS-PAA-2, DS-PAA
A standalone Fibre Channel-to-Ethernet adapter that allows for simple, transparent analysis of Fibre Channel traffic in a switched fabric.
MDS 9000 Family
CD-ROM
M90FM-CD-212=
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 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 4.
Use the show module command to display the type of supervisor module in the switch.
For a Supervisor-1 module, the output might look like this:
switch# show moduleMod Ports Module-Type Model Status--- ----- -------------------------------- ------------------ ------------......5 0 Supervisor/Fabric-1 DS-X9530-SF1-K9 active*6 0 Supervisor/Fabric-1 DS-X9530-SF1-K9 ha-standbyFor a Supervisor-2 module, the output might look like this:
switch# show moduleMod Ports Module-Type Model Status--- ----- -------------------------------- ------------------ ------------......7 0 Supervisor/Fabric-2 DS-X9530-SF2-K9 active *8 0 Supervisor/Fabric-2 DS-X9530-SF2-K9 ha-standbyMigrating from Supervisor-1 Modules to Supervisor-2 Modules
As of Cisco MDS SAN-OS Release 3.0(1), the Cisco MDS 9509 and 9506 Directors support both Supervisor-1 and Supervisor-2 modules. Supervisor-1 and Supervisor-2 modules cannot be installed in the same switch, except during migration. Both the active and standby supervisor modules must be of the same type, either Supervisor-1 or Supervisor-2 modules. For Cisco MDS 9513 Directors, both supervisor modules must be Supervisor-2 modules.
Caution
Note
To migrate from a Supervisor-1 module to a Supervisor-2 module, refer to the step-by-step instructions in the Cisco MDS 9000 Family CLI Configuration Guide.
Configuring Generation 2 Switching Modules
The Cisco MDS 9500 Multilayer Directors are designed to operate with any combination of Cisco MDS 9000 Generation 1 and Generation 2 modules. However, there are limitations to consider when combining the various modules and supervisors in the Cisco MDS 9500 Series platform chassis. The references listed in this section provide specific information about configurations that combine different modules and supervisors.
For information on configuring Generation 2 switching modules, refer to:
http://www.cisco.com/en/US/products/ps5989/products_configuration_guide_chapter09186a0080664c6b.html
For information on port index availability, refer to:
http://www.cisco.com/en/US/products/ps5990/products_installation_guide_chapter09186a0080419599.html
For information on Cisco MDS 9000 hardware and software compatibility, refer to:
http://www.cisco.com/en/US/products/ps5989/products_device_support_table09186a00805037ee.html
Upgrading Your Cisco MDS SAN-OS Software Image
This section lists the guidelines recommended for upgrading your Cisco MDS SAN-OS software image and contains the following sections:
•
•
•
•
•
•
•
Caution
For instructions on how to scan your switch fabric and display the status of Compact Flash using CLI commands, refer to the Cisco MDS 9000 Family CLI Configuration Guide.
Performing a Nondisruptive Software Upgrade on Generation 1 Modules
Generation 1 modules may reload during a nondisruptive SAN-OS software upgrade because of the Compact Flash being unable to partition for the new code. If that happens, the installer aborts and reloads the module.
This issue affects the following modules:
•
•
•
•
This issue might be seen during an upgrade from Cisco SAN-OS Release 3.0(x), 3.1(x) or 3.2(x). It has been addressed for upgrades from SAN-OS Release 3.3(1) or higher. Therefore, you will not be impacted by this issue if you are running SAN-OS Release 3.3(1) when you upgrade to a higher SAN-OS release.
When this problem occurs, the module will automatically reload and may cause the Install All to stop, which will cause the upgrade to be unsuccessful. Error messages similar to the following may be displayed:
Install has failed. Return code 0x40930020 (Non-disruptive upgrade of a module failed).Please identify the cause of the failure, and try 'install all' again.Module 2: Non-disruptive upgrading.-- FAIL. Return code 0x40690009 (Error in downloading image for image upgrade).To avoid this kind of unplanned disruption, follow the methods for identifying and correcting this issue described in Cisco Field Notice 63099, before proceeding with the SAN-OS upgrade. This Field notice can be found under the Support, Products page for Cisco MDS9500 Series Multilayer Directors selection.
The caveat associated with this issue is CSCsm62295.
Upgrading Your Version of Cisco Fabric Manager
To upgrade your version of Cisco Fabric Manager, or install Cisco Fabric Manager for the first time, follow these steps:
Step 1
Note
Step 2
a.
b.
c.
Step 3
Note
Step 4
Note
Step 5
General Upgrading Guidelines
Use the following guidelines when upgrading to Cisco MDS SAN-OS Release 3.1(2):
•
•
•
•
•
–
–
–
–
–
Use Table 5 to determine your nondisruptive upgrade path to Cisco SAN-OS Release 3.1(2). Find the image release number you are currently using in the Current column of the table and use the path recommended.
Note
Use Table 6 to determine your nondisruptive upgrade path to Cisco MDS SAN-OS Release 3.1(2). Find the image release number you are currently using in the Current Release with FICON Enabled column of the table and use the path recommended.
Note
Upgrading with IVR Enabled
An Inter-Switch Link (ISL) flap resulting in fabric segmentation or a merge during or after an upgrade from Cisco MDS SAN-OS Release 2.0(x) to a later image where IVR is enabled might be disruptive. Some possible scenarios include the following:
•
•
•
If this problem occurs, syslogs indicate a failure and the flapped ISL could remain in a down state because of a domain overlap.
This issue was resolved in Cisco SAN-OS Release 2.1(2b); therefore, you must upgrade to Release 2.1(2b) before upgrading to Release 3.1(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.1(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)# shutdownswitch# copy running-config startup-config
Upgrading the SSI Image on Your SSM
Use the following guidelines to nondisruptively upgrade the SSI image on your SSM:
•
•
–
–
–
–
–
Caution
Upgrading a Switch with Insufficient Space for Two Images on the Bootflash
To upgrade the SAN-OS image on a Cisco MDS 9000 Family switch requires enough space on the internal CompactFlash (also referred to as bootflash) to accommodate both the old software image and the new software image.
As of Cisco MDS SAN-OS Release 3.1(1), on MDS switches with a 256-MB CompactFlash, it is possible in some scenarios that a user might be unable to fit two images on the bootflash. This lack of space on the bootflash might cause the upgrade process to fail because new images are always copied onto the bootflash during an upgrade.
The following MDS switches are affected by this issue:
•
•
•
To work around an image upgrade failure caused by a lack of space on the bootflash, follow these steps:
Step 1
Step 2
switch# delete bootflash:m9200-ek9-mz.3.0.3.bin
Note
switch# delete bootflash://sup-standby/m9500-sf1ek9-mz.3.0.3.binStep 3
Step 4
Step 5
Upgrading a Cisco MDS 9124 Switch
If you are upgrading from Cisco MDS SAN-OS Release 3.1(1) to Cisco SAN-OS Release 3.1(2) on a Cisco MDS 9124 Switch, follow these guidelines:
•
•
•
•
•
•
Note
Note
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 5, even though the upgrade is disruptive. Following the nondisruptive upgrade path ensures that the binary startup configuration remains intact.
If you do not follow the upgrade path, (for example, you upgrade directly from SAN-OS Release 2.1(2b) to SAN-OS Release 3.1(2b)), 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.1(2):
•
•
•
•
•
•
–
–
–
–
–
–
–
Use Table 7 to determine your nondisruptive downgrade path from Cisco SAN-OS Release 3.1(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
Use Table 8 to determine your nondisruptive downgrade path from Cisco SAN-OS Release 3.1(2). Find the image release number you are currently using in the Current Release with FICON Enabled column of the table and use the path recommended.
Note
Downgrading the SSI Image on Your SSM
Use the following guidelines when downgrading your SSI image on your SSM.
•
•
•
•
–
–
–
Note
switch(config)# poweroff module slot
switch# purge module slot running-config
New Features in Cisco MDS SAN-OS Release 3.1(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 and the Cisco MDS 9000 Family Fabric Manager Configuration Guide.
Note
Support for Cisco Fabric Switch for HP c-Class BladeSystem
Cisco MDS SAN-OS 3.1(2) supports the new Cisco Fabric Switch for HP c-Class BladeSystem.Through the on-demand port activation license, this switch can be configured with sixteen internal and eight external active ports and four 4-Gb SFPs installed, or with eight internal and four external active ports and two 4-Gb SFPs installed. The Cisco Fabric Switch for HP c-Class BladeSystem also features nondisruptive software upgrades.
The Cisco Fabric Switch for HP c-Class BladeSystem does not support the following Cisco MDS SAN-OS features:
•
•
•
•
In addition, the following features are limited on the Cisco Fabric Switch for HP c-Class BladeSystem:
•
•
Note
Support for Cisco Fabric Switch for IBM BladeCenter
Cisco MDS SAN-OS 3.1(2) supports the new Cisco Fabric Switch for IBM BladeCenter. This switch includes fourteen internal and six external ports, and it features an on-demand port activation license and nondisruptive software upgrades.
The Cisco Fabric Switch for IBM BladeCenter does not support the following Cisco MDS SAN-OS features:
•
•
•
•
In addition, the following features are limited on the Cisco Fabric Switch for IBM BladeCenter:
•
•
Note
SAN Device Virtualization
Cisco SAN device virtualization allows you to create virtual devices that represent physical end-devices when configuring switches with Cisco SAN-OS Release 3.1(2) and later. Virtualization of SAN devices accelerates swap-out or failover to a replacement disk.
SAN device virtualization enables you to:
•
•
Cisco SAN-OS Release 3.1(2) supports only virtual targets in the SAN Device Virtualization feature. In addition, LUN zoning is not available for SDV devices in Cisco SAN-OS Release 3.1(2).
Enable/Disable Link Traps
A new command-line interface command has been added to Cisco SAN-OS 3.1(2) that allows you to control whether SNMP link state traps are enabled or disabled. By default, the link state traps are enabled, so that whenever a link toggles its state up or down, a trap is generated. Issuing the no link-state-trap command on the interface disables the traps. The state of the link trap, either enabled or disabled, is added to the running configuration for the switch.
Daylight Saving Time Change
Starting in 2007, daylight saving time (DST) in the U.S. begins on the second Sunday in March and ends on the first Sunday in November.
Cisco SAN-OS does not automatically adjust for daylight saving time. You must change the switch configuration to make the daylight saving time adjustment.
To change the clock on multiple MDS switches in a fabric, use the new Run CLI Commands feature in Cisco Fabric Manager. Follow these steps:
Step 1
Step 2
Step 3
Step 4
config t
clock summer-time PDT 2 Sunday March 02:00 1 Sunday November 02:00 60
exit
Note
Step 5
Step 6
For additional information about the new Run CLI Commands feature in Cisco Fabric Manager, refer to the Cisco MDS 9000 Family Fabric Manager Configuration Guide.
To manually change the time on an MDS switch through the CLI, use the clock summer-time command:
switch# config t
switch(config)# clock summer-time daylight_timezone_name 2 Sunday March 02:00 1 Sunday November 02:00 60For additional information about this procedure, refer to the Cisco MDS 9000 Family CLI Configuration Guide.
FCS Discovery of Virtual Devices
As of Cisco SAN-OS Release 3.1(2), Cisco Fabric Configuration Services (FCS) supports the discovery of virtual devices. The fcs virtual-device-add command, issued in FCS configuration submode, allows you to discover virtual devices in a particular VSAN or in all VSANs. For the devices that are zoned for IVR to be discovered with this command, they must have request domain_ID (RDI) enabled.
OHMS for the MDS 9124 Switch
The Online Health Management System (OHMS) system health feature is available on the Cisco MDS 9124 Switch. This online diagnostic feature can be used for hardware fault detection and recovery.
Compact Flash Report in Cisco Fabric Manager
Cisco MDS Fabric Manager Release 3.1(2) includes a reporting feature that automatically scans your switch fabric and reports the status of Compact Flash on certain modules.
The Compact Flash report can be used on switches running Cisco MDS 9000 SAN-OS Release 2.x and higher. Creating the report requires that you complete the following tasks:
•
•
•
To download the Compact Flash Check Utility (m9000-lc1-gplug-mz.1.0.2.bin), follow these steps:
Step 1
Step 2
To run the Compact Flash report using Fabric Manager, follow these steps:
Step 1
You see the Compact Flash Report dialog box with all switches selected.
Step 2
Step 3
Step 4
Step 5
You see the Compact Flash Report dialog box showing the status of each switch.
Note
Step 6
Step 7
Step 8
Step 9
Step 10
Fabric Manager New Login Procedure
As of Cisco SAN-OS Release 3.1(1), logging into Fabric Manger is a two-part process that involves entering your username and password twice, in two different dialog boxes. To successfully complete the login process, you must:
•
•
To log in to Fabric Manger Server, follow these steps:
Step 1
Step 2
Step 3
Step 4
To discover new fabrics, follow these steps:
Step 1
Step 2
Step 3
Step 4
The Open Fabric dialog box displays.
Step 5
Step 6
For additional information about logging in to Fabric Manager and setting the seed switch, refer to "Setting the Seed Switch in Cisco SAN-OS Release 3.1(1) and Later" in the Cisco MDS 9000 Family Fabric Manager Configuration Guide.
Limitations and Restrictions
This section lists the limitations and restrictions for this release. This section includes the following topics:
•
•
•
•
•
•
•
CWDM SFPs
The 2-Gbps CWDM SFPs do not have have a maximum speed set in memory and they negotiate to 4-Gbps on modules that support the higher speed. As a result, the link comes up and appears to work, but then becomes disabled and connectivity problems occur. To correct this problem, both sides of the connection must have their speed hard coded to 2-Gbps.
Fabric Manager
Observe the following limitations or restrictions for the Cisco SAN-OS Release 3.1(2) for Fabric Manager:
•
•
iSNS
Observe the following behaviors regarding the iSNS server and client:
•
•
•
•
•
MTU Size Limitation
The Cisco MDS 9216i switch and MPS-14/2 module do not support an MTU size greater than 8000 bytes. An attempt to set the MTU size greater than 8000 bytes will result in an error. As a workaround, reset the value of the MTU size (576 to 8000 bytes) and issue the no shutdown command on the interface for normal operation.
Reconfiguring SSM Ports
Starting with Cisco MDS SAN-OS Release 3.0(1), the SSM front panel ports can no longer be configured in auto mode, which is the default for releases prior to Release 3.1(1). For instructions about how to modify the configuration of the ports before upgrading to SAN-OS Release 3.1(2), see the "Reconfiguring SSM Ports Before Upgrading to SAN-OS Release 3.1(2)" section.
Virtual Router Redundancy Protocol (VRRP) Interfaces
When a switchover occurs on a switch that is the master for Virtual Router Redundancy Protocol (VRRP) interfaces, the switchover may cause a minor delay. As a result, the VRRP backup (occurring elsewhere) may assume the role of the VRRP master. As a workaround, increase the VRRP advertisement interval for these interfaces.
QoS on an MDS 48-port Fibre Channel Module
Due to possible differences in parts per million between the MAC ASICs on both sides of an ISL link, there is a potential throughput issue when running QoS over an ISL on an MDS 48-port Fibre Channel module. Specifically, the user may not see traffic throughput that follows the programmed QoS ratios. The throughput ratio on the high and/or medium priority class of service (COS) relative to the low priority COS, may not be as high as the actual programmed ratio.
If this situation occurs, you can move the ISL to a port on a different port group on one and/or both sides of the link, or move the ISL to a port on a lower-density card if you require accurate QoS ratios.
Maximum Number of Zones Supported in Interop Mode 4
In interop mode 4, the maximum number of zones that is supported in an active zone set is 2047, due to limitations in the connected vendor switch.
When IVR is used in interop mode 4, the maximum number of zones supported, including IVR zones, in the active zone set is 2047.
Using SDV on a Cisco MDS 9124 Switch, on a Cisco Fabric Switch for HP c-Class BladeSystem, or on a Cisco Fabric Switch for IBM BladeCenter
There must be at least one SAN device virtualization-enabled switch that is not a Cisco MDS 9124 switch, a Cisco Fabric Switch for HP c-Class BladeSystem, or a Cisco Fabric Switch for IBM BladeCenter between the server and the target that are being virtualized. In other words, SAN device virtualization does not work when initiators and primary targets are connected to the same Cisco MDS 9124 Switch or Cisco Fabric Switch for HP c-Class BladeSystem or Cisco Fabric Switch for IBM BladeCenter.
Configuring Default Settings for the Default Zone
Following an upgrade from any Cisco SAN-OS 2.x release to any Cisco SAN-OS 3.x release, the configuration defined by the zone default-zone permit vsan vsan-id command is applied only to the active VSAN. The configuration does not apply to unconfigured VSANs. In SAN-OS 3.x, you can apply the configuration to unconfigured VSANs by issuing the system default zone default-zone permit command.
Similarly, the zoneset distribute full vsan vsan-id command applies only to the active VSAN following an upgrade from any Cisco SAN-OS 2.x release to any Cisco SAN-OS 3.x release.
Although you can configure the default-zone settings in the setup script, these settings do not take effect for VSAN 1, because VSAN 1 already exits prior to running the setup script. To configure the default settings for the default-zone in VSAN 1, you must explicitly enter the zone default-zone permit command.
PPRC Not Supported with FCIP Write Acceleration
IBM Peer to Peer Remote Copy (PPRC) is not supported with FCIP Write Acceleration.
Using IVR In a Fabric With Mixed Code Versions
If you are using IVR and you are running SAN-OS 3.x software on your MDS switches, make sure that all IVR switches run the same code version. Otherwise, if you have a fabric with mixed code versions, the switches running the higher version may not be able to see all IVR devices. The mixed fabric can cause an inconsistent database among IVR switches, which might affect IVR behavior. For this reason, it is important that all IVR switches run the same SAN-OS version, preferably SAN-OS Release 3.3(4a), which has device update (DU) support, or later.
Caveats
This section lists the open and resolved caveats for this release. Use Table 9 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: The fabric login (FLOGI) process fails while new hosts are initializing. The show flogi internal event error command shows that a module is not present.
Workaround: This issue is resolved
•
Symptom: If you create a PortChannel with a number higher than 128, IP over Fibre Channel (IPFC) ping does not work.
Workaround: This issue is resolved.
•
Symptom: On a Cisco MDS 9513 Switch, when there are more than 512 ports on a single chassis, some ports with indexes between 0x200 and 0x20f may not come up. In addition, some ports with indexes between 0x0 and 0xf may show unexpected behavior when the ports with indexes between 0x200 and 0x20f are brought up. To display the port indexes, issue the show system internal fcfwd idxmap port-to-interface command. The port indexes appear in the column with the heading "glob idx."
Workaround: This issue is resolved.
•
Symptom: Cisco Fabric Manager Server does not allow monitoring of unlicensed fabrics without a client connected. EMC Call Home needs to run continuously on multiple unlicensed fabrics, even if no client is connected.
Workaround: This issue is resolved.
•
Symptom: After you install an MPS-14/2 module, the power capacity level on the switch might be incorrect.
Workaround: This issue is resolved.
•
Symptom: An MDS switch does not respond to a query of the Fabric Configuration Server (FCS) for devices zoned through IVR.
Workaround: This issue is resolved. For additional information, see "FCS Discovery of Virtual Devices" section.
•
Symptom: On the Cisco MDS 9124 Switch, traffic may not flow to and from an FL port, if an F port and an FL port are part of the same port group. In addition, hard zoning may not be strictly enforced in that port group. This problem may not happen if the FL port has only one disk or device behind it.
Workaround: This issue is resolved.
•
Symptom: The Fabric Manager Web Server report for port group performance does not show the correct port groups for the MDS 9000 48-port 4-Gbps Fibre Channel module.
Workaround: This issue is resolved.
•
Symptom: Dynamic port VSAN membership (DPVM) entries are configured and activated in the DPVM database, but the output of the show dpvm ports vsan command is null. This occurs only with ports that are assigned a dynamic VSAN based on a device alias configuration in the DPVM, as opposed to ports that have a dynamic VSAN assigned based on nWWN or pWWN configuration.
Workaround: This issue is resolved.
•
Symptom: The Fabric Manager DPVM table does not support device types.
Workaround: This issue is resolved.
•
Symptom: The WWN Name value in the DPVM active database displays incorrectly in Fabric Manager.
Workaround: This issue is resolved.
•
Symptom: During a downgrade to a Cisco MDS SAN-OS software image, any activity that requires hardware programming results in a standby supervisor being reset and the downgrade being terminated.
Workaround: This issue is resolved.
•
Symptom: Occasionally, following an IVR zone set activation, IVR fails to export some devices to other VSANs. (For scalability reasons, IVR maintains a run-time cache of all devices in IVR zones that have been successfully activated. If activation fails in a VSAN and later succeeds, then devices that are member of that VSAN are not added to the cache.)
Workaround: This issue is resolved.
•
Symptom: When a device is removed from a remote switch, the device might still appear in the name server database, and the fcns refresh command might fail to remove the stale entry.
Workaround: This issue is resolved.
•
Symptom: Volatile memory might get full because captured IVR PLOGI records are not deleted after the PLOGIs are released. This situation occurs when one or more hosts send unexpectedly large number of PLOGIs in a short time, such as when a VMware host sends PLOGIs to disks with no LUNs exposed to the host SAN volume controller (SVC) environment.
Workaround: This issue is resolved.
•
Symptom: During a Cisco MDS SAN-OS software upgrade, the acltcam process may restart if an unexpected value is read from an unused hardware TCAM location. As a result, the upgrade of this module and subsequent modules may be terminated.
Workaround: This issue is resolved.
•
Symptom: During an upgrade to Cisco MDS SAN-OS Release 3.1(1), when IVR is configured in non-NAT mode, an access control list (ACL) process might occasionally exit if it encounters a specific error condition. This could cause the module to reload.
Workaround: This issue is resolved.
•
Symptom: In a manually configured IVR VSAN topology, IVR zone set activation might fail in interop mode 4 VSANs. If this happens, the following messages are logged:
2007 Jan 28 08:09:12 MDS1 %ZONE-2-ZS_CHANGE_ACA_FAILED: %$VSAN 1%$ ACA failed : domain 0x02 returns NO_REASON_CODE
2007 Jan 28 08:09:12 MDS1 %ZONE-2-ZS_CHANGE_ACTIVATION_FAILED:
Workaround: This issue is resolved.
•
Symptom: After setting the clock from Fabric Manager (using SNMP), I/O timeouts were observed. The network time protocol (NTP) was not sending the notification that the clock had changed.
Workaound: This issue is resolved.
Open Caveats
•
Symptom: If you bring up more than one link at a time between two VSANs that have overlapping domains and at least one of the switches is SDV enabled, one link will become isolated. The other links will come up, even though the domains are overlapping. In addition, the SDV virtual domains will change, causing traffic disruption on all devices associated with their old value.
Workaround: Bring up multiple links between two switches one at a time. Verify that the first link came up correctly before attempting to bring up the next link. If the first link fails to come up because of a domain ID overlap, resolve the domain conflict and then try again to bring up the links.
•
Symptom: On large fabrics with many PortChannels, the Fabric Manager Server may consume 99-100% of the CPU for extended periods of time.
Workaround: Restart the Fabric Manager Server.
•
Symptom: If you are using a Cisco MDS 16-port or 32-port 2-Gbps Fibre Channel switching module, a 4-port or 8-port Gigabit Ethernet IP Storage services module, the Storage Services Module (SSM), or the 14/2-port Multiprotocol Services (MPS-14/2) module and you perform a nondisruptive upgrade to Cisco SAN-OS 3.1(1), 3.1(2), or 3.1(2a), the modules do not correctly route traffic to any new modules that you insert following the upgrade.
Workaround: To workaround this issue, do one of the following:
–
–
–
–
•
Symptom: If there is an interruption to the upgrade process on a given module during an upgrade to Cisco MDS SAN-OS Release 3.1(2), the install all command will fail. This may result in a condition where some modules and supervisors are running SAN-OS 3.1(2) and the remainder of modules in the chassis are running an older version of SAN-OS. You may not be able to execute the install all command again to upgrade the remaining modules to SAN-OS 3.1(2).
If you issue the show install all status command, you may see the following types of messages in the install logs:
Module X: Upgrading Bios/loader/bootrom.
Warning: please do not remove or power off the module at this time.
-- FAIL. Return code 0x40710001 (BIOS versions are identical).
CAUTION: The BIOS/loader/bootrom of above module may be in corrupted state. Please try programming it again and DO NOT reboot without programming it successfully, otherwise you have to manually take out the flash from the card and program it in a BIOS programming station.Install has failed. Return code 0x40930015 (Pre-upgrade of a module failed).Please identify the cause of the failure, and try 'install all' again.
Workaround: Issue the install module module-number image forced hidden command to upgrade the modules that are running the lower version of SAN-OS following the failure of the install all command.
•
Symptom: On a 4-Gbps Fibre Channel module, PLOGI accepts were discarded because the port was initially an F port, but had been changed to an E port.
Workaround: To resolve this issue, follow these steps:
1.
2.
3.
4.
5.
6.
•
Symptom: 100% CPU utilization was seen on an MDS switch. It was caused by repeated fabric logins (FLOGIs) on a particular port. This situation can occur if a host cannot log in because the allocation of the FC ID fails, and keeps re-trying using a specific pattern of Source FC IDs (S_IDs) for the FLOGI frame.
Workaround: The interface will now be error-disabled for too many FLOGI failures.
To troubleshoot the configuration and find the reason for the FC ID allocation failure, examine the messages in the syslog. Refer to the Cisco MDS 9000 Family CLI Configuration Guide for detailed information about FLOGI, FC IDs, and FC ID allocation for HBAs.
•
Symptom: 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: If you install a feature license on any module, then the storage services module (SSM) with the SCSI flow feature will be reprovisioned and write acceleration on the flows will be affected.
Workaround: To work around this issue, please contact Cisco TAC. They can help you recover from this problem by guiding you through the following steps:
1.
2.
3.
4.
5.
•
Symptom: A crash might occur in the intelligent line card (ILC) helper process when provisioning or deprovisioning a storage application on the SSM card.
Workaround: If the ILC helper dumps core memory three times, reboot the switch for it to function normally. Use the show cores command to determing if the ILC helper has dumped core memory.
•
Symptom: In rare situations, data virtual target (DVT) configurations might disappear following a reload of the SSM or an upgrade to the SSI 3.1(2m) image.
Workaround: Statically define the DVTs using the santap module command, as in the following example:
switch(config)# santap module slot-number dvt target-pwwn target-pwnn target-vsan target-vsan-id dvt-name dvt-name dvt-vsan dvt-vsan-id lun-size-handling 1
•
Symptom: Spectra Logic tape drives require a unique area ID.
Workaround: Add the company OUI ID to the swtich database so that the switch can assign unique area IDs to the Spectra Logic tape drives.
•
Symptom: In rare instances, the following Generation 2 modules might reload:
–
–
–
–
The output of the show logging log command will have events like those shown below. In the following output, module 7 is the supervisor and module 12 is the module that reloaded.
2008 Jul 15 19:39:30 fcd95c41 %MODULE-4-MOD_WARNING: Module 7 (serial: JAE1134UR88) reported warnings on ports 7/1-7/3 (Unknown) due to BE2 Arbiter experienced an error in device 65 (device error 0xc410d613)2008 Jul 15 19:39:30 fcd95c41 %MODULE-4-MOD_WARNING: Module 8 (serial: JAE1134UOTD) reported warnings on ports 8/1-8/3 (Unknown) due to BE2 Arbiter experienced an error in device 65 (device error 0xc410d613)2008 Jul 15 19:39:35 fcd95c41 %XBAR-5-XBAR_STATUS_REPORT: Module 12 reported status for component 88 code 0x40240015.2008 Jul 15 19:39:35 fcd95c41 %MODULE-2-MOD_DIAG_FAIL: Module 12 (serial: JAE1136VU6L) reported failure on ports 12/1-12/24 (Fibre Channel) due to Fatal runtime Arb error. (DevErr is bitmap of failed modules) in device 88 (device error 0x800)"show logging onboard" will show log similar to the one below for the reloaded module:Logging time: Tue Jul 15 19:39:28 2008machine check: process swapper (0), jiffies 0x744af3a4Free pages in zone[0]:0x4a70,zone[1]:0x0,zone[2]:0x0Stack: c000dd58 c001eefc c000b2c4 c000ae98 d2060e10 c003d7a4 c00f869c c0045cdcd196c584 d196d100 c000c31c c000c3e4 c000ae90 c000c910 c000c924 c0008948 c01ca610 c0000394.....................................Workaround: None. The chance of a module reload occurring again on the same module is very rare. Therefore, continued use of the module is acceptable.
A software workaround for this issue exists in SAN-OS Release 3.3.(2) and NX-OS Release 4.(1b). Upgrading to one of those releases will help decrease instances of modules reloads.
•
Symptom: When you configure Cisco Traffic Analyzer to capture traffic on one or more interfaces on a Windows platform, the configuration web page might not show that the interface has been selected for traffic capture even though traffic capture on that interface is enabled.
Workaround: Check the logs to clarify that the correct interface has been selected.
•
Symptom: If an iSNS client tries to register a portal separately after registering the network entity and storage node object with the Cisco MDS iSNS server, the portal registration might fail.
Workaround: Register the portal at the same time as the network entity and storage node object registration.
•
Symptom: If there are 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: 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: On an MDS switch with dual supervisor modules, the bootflash on the standby supervisor is replaced with a new bootflash. Then there is a system switchover. Then the bootflash on the new standby supervisor (which was previously the active supervisor) is replaced. The copy running-config startup-config command is used to save the configuration, but the console speed does not get saved. Instead, the console speed is reset to 9600.
Workaround: After you replace the bootflash and the standby supervisor boots up, issue the copy running-config startup-config command to synchronize the configuration from the active supervisor to the standby supervisor.
•
Symptom: An association call from a VSAN to its logical switch returns a particular WWN, but an association call from the physical system to the virtual system does not return the same WWN, which indicates that the logical switch is not associated to the physical switch.
Workaround: None.
•
Symptom: Changing fabric credentials from a local SNMP user to a TACACS+ user in Cisco Fabric Manager using server > admin results in a Fabric Manager Server error.
Workaround: Close the fabric and then reopen it using the new TACACS+ user credentials, with Accelerate Discover unchecked.
•
Symptom: It is possible for the hardware interface that is used to access SFPs and temperature sensors on modules to lock up. This inhibits the detection of a subsequent removal or insertion of an SFP and results in the failure to read a module's temperature sensors.
Workaround: Reload the module to recover the sensor.
•
Symptom: When compression is enabled on an FCIP link, the throughput on the GigabitEthernet interface may be reduced, as compared to uncompressed throughput. Depending on the data pattern, this may or may not impact application throughput.
Workaround: If application throughput is reduced, disable compression on the FCIP link.
•
Symptom: Under rare circumstances, a customer running the Cisco MDS SAN-OS SANTap feature with EMC RecoverPoint might find that following a reload of the SSM module, the SSM CVT is stuck in UNKNOWN status in the RecoverPoint appliance.
Workaround: None.
•
Symptom: If the limit of 5000 iSCSI sessions is reached and new initiators try create sessions, a memory leak may occur.
Workaround: Do not exceed the 5000 session limit.
•
Symptom: In Cisco Fabric Manager Release 3.1(1), some tables in the database are cleared after a fabric is persisted to the database. This causes Fabric Manager Client to show empty ISLs or end ports in the Inventory page, as well as zero ISLs, zero end ports, or zero flows in the Performance page.
Workaround: None.
•
Symptom: Zone member configuration based on interface domain does not work correctly in Cisco MDS SAN-OS 3.1(1) and3.1(2) when you use CLI commands to configure interface-domain zones.
Workaround: Use Cisco Fabric Manager to configure interface-domain zones.
•
Symptom: The Performance Manager in Cisco Fabric Manager does not collect and report the correct Fibre Channel flow statistics.
Workaround: Download Cisco SAN-OS 3.1(2a), if you want to use the Performance Manager to manage the fabric.
•
Symptom: In rare situations, an upgrade to Cisco MDS SAN-OS 3.0(3) or higher may cause an MDS 9000 16-port Fibre Channel switching module to reload during the upgrade process. After the upgrade image is loaded on the module, a memory manager process reads the hardware to restore itself to its pre-upgrade state. While doing so, it finds an invalid entry in memory and then crashes while trying to process that entry. As a result, the module reloads, which clears the invalid entry and the module then comes up fully operational. However, the module reload may abort the upgrade process and the remaining modules may require manual upgrades.
You may see syslog messages similar to the following:
2007 Apr 2 11:15:35 MDS1 %IMAGE_DNLD-SLOT1-2-IMG_DNLD_STARTED: Module image
download process. Please wait until completion...
2007 Apr 2 11:15:49 MDS1 %IMAGE_DNLD-SLOT1-2-IMG_DNLD_COMPLETE: Module image
download process. Download successful.
2007 Apr 2 11:16:59 MDS1 %ACL-2-ACL_LINECARD_STATUS: Status from
linecard: 0, for module: acltcam(ID: 0), status : 0, error_id: 0x40320002,
catastrophic: FALSE, restart count: 0.
2007 Apr 2 11:17:48 MDS1 %ACL-2-ACL_LINECARD_STATUS: Status from
linecard: 0, for module: acltcam(ID: 0), status : 0, error_id: 0x40320002,
catastrophic: TRUE, restart count: 2.
2007 Apr 2 11:17:48 MDS1 %MODULE-5-MOD_REINIT: Re-initializing module 1(serial: xyz)
2007 Apr 2 11:18:07 MDS1 %PLATFORM-5-MOD_DETECT: Module 1 detected (Serial number xyz)
2007 Apr 2 11:18:07 MDS1 %PLATFORM-5-MOD_PWRUP: Module 1 powered up (Serial number xyz) ..
2007 Apr 2 11:18:53 MDS1 %MODULE-5-MOD_OK: Module 1 is online (serial: xyz)Workaround: Upgrade to Cisco MDS SAN-OS Release 3.1(3). Alternatively, check for invalid hardware entries before attempting an upgrade. If no such entries are found, then the upgrade process will not encounter this issue. The following example shows the commands you can use to check for invalid entries on a module:
switch# attach module <module number>
module-<n># show process acltcam luxor 0 input dump | exclude e00000000000000000 | include ": e"
module-<n># show process acltcam luxor 0 input dump | exclude e00000000000000000 | include ": f"module-<n># show process acltcam luxor 0 output dump | exclude e00000000000000000 | include ": e"
module-<n># show process acltcam luxor 0 output dump | exclude e00000000000000000 | include ": f"
module-<n># show process acltcam luxor 1 input dump | exclude e00000000000000000 | include ": e"
module-<n># show process acltcam luxor 1 input dump | exclude e00000000000000000 | include ": f"
module-<n># show process acltcam luxor 1 output dump | exclude e00000000000000000 | include ": e"
module-<n># show process acltcam luxor 1 output dump | exclude e00000000000000000 | include ": f"
•
Symptom: Cisco Fabric Manager may display a licensed fabric as unlicensed in the Open Fabric dialog box.
Workaround: Click the Refresh button to update the license information.
•
Symptom: If you remove a fan tray module from an MDS 9500 series switch that is running Cisco MDS SAN-OS Release 3.0(1), 3.0(2), 3.0(2a) 3.0(2b), 3.0(3), 3.1(1), 3.1(2) or 3.1(2a), the switch shuts down if you do not replace the fan tray module within 170 seconds. (In all other SAN-OS releases, you have 250 seconds to replace it.)
Workaround: None.
•
Symptom: The SNMP Getbulk request in Cisco SAN-OS 3.1(1) does not work correctly when the non-repeaters argument is set to a number other than zero. This results in an erroneous error.
Workaround: Set the non-repeaters argument to zero when issuing SNMP Getbulk requests.
•
Symptom: If the Fabric Manager client loses connectivity to the Fabric Manager server, the client displays the error "no such object in table." The user is then unable to manage the fabric.
Workaround: Close the Fabric Manager client and restart it.
•
Symptom: The export utility in Performance Manager does not work correctly in Cisco SAN-OS 3.1(2a).
Workaround: None.
•
Symptom: If an interface index map is not programmed correctly, the Port Manager continues to bring up the port, which results in an ACL programming failure and the following error message:
%ZONE-2-ZS_TCAM_PROGRAMMING_FAILED: %$VSAN xxx%$ TCAM operation failed : Unknown, Reason: idxmap ioctl failure
Because of the programming failure, the port is effectively useless, even though it is up.
Workaround: None.
•
Symptom: If there are IVR-NAT rewrite rules for FCIP interfaces on an MDS 9000 MPS-14/2 module in an IVR border switch, updates or modifications of the rewrite rules may fail after the MPS-14/2 module is upgraded to SAN-OS 3.1(2x) or lower. Stale IVR-NAT rules are left on the FCIP interfaces rather than the required IVR-NAT rules, and this impacts IVR traffic over the FCIP link.
There is no impact on traffic unless and until IVR rewrite rules need to be modified after an upgrade. However, if the IVR rewrite information changes (such as when a virtual domain ID changes) because of other events taking place in the fabric, then the stale IVR rewrite rules continue to re-write the frames entering the FCIP interface with the old rewrite information. This may result in frames with an invalid rewritten destination ID getting dropped or incorrectly forwarded in the network. Frames with a source ID that is incorrectly rewritten will eventually be rejected or incorrectly interpreted by the destination device.
Workaround: Upgrade to Cisco MDS SAN-OS Release 3.1(3). Otherwise, use one of the following workarounds:
•
•
•
Symptom: When creating a new VSAN through Fabric Manager or through a script that can create a VSAN on each switch at the same time, the same domain ID is created for each switch. This causes the newly-created VSAN to be segmented on all links.
Workaround: Either create the VSAN using static domain IDs, or use the CLI to create new VSANs at different times.
•
Symptom: An SNMP Get-Next Request for the MIB object ip.ipAddrTable.ipAddrEntry.ipAdEntIfIndex on an MDS 9000 switch resolves by asking ifIndex for a loopback address. Because there is no hardware (ifIndex) for a loopback address, the ifIndex reply for this interface is skipped and the next possible instance of the object, which is IP-MIB::ipAdEntNetMask, is returned.
Workaround: There are two ways you can work around this issue. Do one of the following:
–
–
•
Symptom: A fibre channel port on an MDS switching module remained out-of-service after the port was put back in service. As a result, it was not possible to configure the port.
Workaround: To put the module back in service, enter the commands shown in this example:
switch(config)# poweroff module slot-number
switch# purge module slot-number running-config
switch(config)# no poweroff module slot-numberConfigure the module again because the previous configuration will be lost.
•
Symptom: Following a Cisco SAN-OS software upgrade or downgrade, certain ports get stuck in link failure or in a not-connected state, even though the same SFP, cable, host, or storage device works in other ports on the same module.
Workaround: Reload the module, or contact Cisco TAC for a less disruptive workaround.
•
Symptom: When an fcalias is added as a zone member or a zone is added to a zone set via SNMP, there is an SNMPD memory leak.
Workaround: None.
•
Symptom: A data path processor (DPP) might fail on an MDS switch running Cisco SAN-OS Release 3.1(2b) with an SSM running SSI Release 3.1(2m) and with the SANTap feature provisioned. The failure occurs while the DPP is processing an unexpected transfer ready message.
Workaround: None.
•
Symptom: IVR zone set activation in Interop mode 4 results in a failure without an appropriate status message. This issue is seen if a successful IVR zone set activation results in more than 2047 zones in Interop mode 4. In Interop mode 4, the combined number of regular and IVR zones supported is 2047. If an IVR activation attempts to activate more than 2047 zones, the activation is rejected by the zone server module. An appropriate status message is not conveyed back to IVR.
Workaround: None.
•
Symptom: FCP-CMD (for example, Inquiry) frames targeted to LUN 0x45F0 or LUN 0x50F0 are dropped by an MDS switch when traffic flows (egresses) thru Generation 2 modules. LUN 0x45F0 corresponds to HPUX's Volume Set Address <VBUS ID: 0xB, Target ID: 0xE, LUN: 0x0>.
Workaround: Do not use LUN 0x45F0 and LUN 0x50F0 when Generation 2 modules are present in the fabric.
•
Symptom: The RMON 64-bit alarms table can show large values as negative numbers.
Workaround: None.
•
Symptom: When enhanced zoning is enabled, an empty pop-up window displays in Fabric Manager after a zone set activation completes.
Workaround: None.
•
Symptom: For passwords authenticated by an AAA server, the MDS switch should inform the user when their password is about to expire.
Workaround: This is an enhancement. It is available only for CLI logins. Fabric Manager and Device currently do not support this feature.
•
Symptom: During a Fabric Manager upgrade, the following files were not preserved: AAA.properties and emccallhome.properties.
Workaround: None.
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 this URL: http://www.cisco.com/en/US/customer/products/ps5989/products_documentation_roadmap09186a00804500c1.html
For information on IBM TotalStorage SAN Volume Controller Storage Software for the Cisco MDS 9000 Family, refer to the IBM TotalStorage Support website: http://www.ibm.com/storage/support/2062-2300/Release Notes
•
•
•
•
Compatibility Information
•
•
•
•
•
Regulatory Compliance and Safety Information
•
Hardware Installation
•
•
•
•
•
Cisco Fabric Manager
•
•
•
•
•
Command-Line Interface
•
•
•
•
•
•
•
•
Troubleshooting and Reference
•
•
•
•
•
•
Installation and Configuration Note
•
•
•
Obtaining Documentation
Cisco documentation and additional literature are available on Cisco.com. This section explains the product documentation resources that Cisco offers.
Cisco.com
You can access the most current Cisco documentation at this URL:
http://www.cisco.com/techsupport
You can access the Cisco website at this URL:
You can access international Cisco websites at this URL:
http://www.cisco.com/public/countries_languages.shtml
Product Documentation DVD
The Product Documentation DVD is a library of technical product documentation on a portable medium. The DVD enables you to access installation, configuration, and command guides for Cisco hardware and software products. With the DVD, you have access to the HTML documentation and some of the PDF files found on the Cisco website at this URL:
http://www.cisco.com/univercd/home/home.htm
The Product Documentation DVD is created and released regularly. DVDs are available singly or by subscription. Registered Cisco.com users can order a Product Documentation DVD (product number DOC-DOCDVD= or DOC-DOCDVD=SUB) from Cisco Marketplace at the Product Documentation Store at this URL:
http://www.cisco.com/go/marketplace/docstore
Ordering Documentation
You must be a registered Cisco.com user to access Cisco Marketplace. Registered users may order Cisco documentation at the Product Documentation Store at this URL:
http://www.cisco.com/go/marketplace/docstore
If you do not have a user ID or password, you can register at this URL:
http://tools.cisco.com/RPF/register/register.do
Documentation Feedback
You can provide feedback about Cisco technical documentation on the Cisco Technical Support & Documentation site area by entering your comments in the feedback form available in every online document.
Cisco Product Security Overview
Cisco provides a free online Security Vulnerability Policy portal at this URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
From this site, you will find information about how to do the following:
•
•
•
A current list of security advisories, security notices, and security responses for Cisco products is available at this URL:
To see security advisories, security notices, and security responses as they are updated in real time, you can subscribe to the Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed. Information about how to subscribe to the PSIRT RSS feed is found at this URL:
http://www.cisco.com/en/US/products/products_psirt_rss_feed.html
Reporting Security Problems in Cisco Products
Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you have identified a vulnerability in a Cisco product, contact PSIRT:
•
An emergency is either a condition in which a system is under active attack or a condition for which a severe and urgent security vulnerability should be reported. All other conditions are considered nonemergencies.
•
In an emergency, you can also reach PSIRT by telephone:
•
•
Tip
Never use a revoked encryption key or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one linked in the Contact Summary section of the Security Vulnerability Policy page at this URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
The link on this page has the current PGP key ID in use.
If you do not have or use PGP, contact PSIRT to find other means of encrypting the data before sending any sensitive material.
Product Alerts and Field Notices
Modifications to or updates about Cisco products are announced in Cisco Product Alerts and Cisco Field Notices. You can receive Cisco Product Alerts and Cisco Field Notices by using the Product Alert Tool on Cisco.com. This tool enables you to create a profile and choose those products for which you want to receive information.
To access the Product Alert Tool, you must be a registered Cisco.com user. (To register as a Cisco.com user, go to this URL: http://tools.cisco.com/RPF/register/register.do) Registered users can access the tool at this URL: http://tools.cisco.com/Support/PAT/do/ViewMyProfiles.do?local=en
Obtaining Technical Assistance
Cisco Technical Support provides 24-hour-a-day award-winning technical assistance. The Cisco Technical Support & Documentation website on Cisco.com features extensive online support resources. In addition, if you have a valid Cisco service contract, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not have a valid Cisco service contract, contact your reseller.
Cisco Technical Support & Documentation Website
The Cisco Technical Support & Documentation website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day at this URL:
http://www.cisco.com/techsupport
Access to all tools on the Cisco Technical Support & Documentation website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:
http://tools.cisco.com/RPF/register/register.do
Note
Tip
If you suspect that the browser is not refreshing a web page, force the browser to update the web page by holding down the Ctrl key while pressing F5.
To find technical information, narrow your search to look in technical documentation, not the entire Cisco.com website. On the Cisco.com home page, click the Advanced Search link under the Search box and then click the Technical Support & Documentation radio button.
To provide feedback about the Cisco.com website or a particular technical document, click Contacts & Feedback at the top of any Cisco.com web page.
Submitting a Service Request
Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool provides recommended solutions. If your issue is not resolved using the recommended resources, your service request is assigned to a Cisco engineer. The TAC Service Request Tool is located at this URL:
http://www.cisco.com/techsupport/servicerequest
For S1 or S2 service requests, or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.
To open a service request by telephone, use one of the following numbers:
Asia-Pacific: +61 2 8446 7411
Australia: 1 800 805 227
EMEA: +32 2 704 55 55
USA: 1 800 553 2447For a complete list of Cisco TAC contacts, go to this URL:
http://www.cisco.com/techsupport/contacts
Definitions of Service Request Severity
To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.
Severity 1 (S1)—An existing network is "down" or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.
Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operations are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.
Severity 3 (S3)—Operational performance of the network is impaired while most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.
Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.
Obtaining Additional Publications and Information
Information about Cisco products, technologies, and network solutions is available from various online and printed sources.
•
http://www.cisco.com/offer/subscribe
•
•
http://www.cisco.com/go/marketplace/
•
•
•
http://www.cisco.com/en/US/products/index.html
•
http://www.cisco.com/discuss/networking
•
http://www.cisco.com/univercd/cc/td/doc/abtunicd/136957.htm
•
http://www.cisco.com/en/US/learning/index.html
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)
© 2007 Cisco Systems, Inc. All rights reserved.
