 Feedback
|
Table Of Contents
Cisco MDS 9000 Family Release Notes
for Cisco MDS SAN-OS Release 3.0(2)Determining the Software Version
Upgrading Your Cisco MDS SAN-OS Software Image
Performing a Nondisruptive Software Upgrade on Generation 1 Modules
Selecting the Correct Software Image for an MDS 9500 Series Switch
Reconfiguring SSM Ports Before Upgrading to SAN-OS Release 3.0(2)
Migrating from Supervisor-1 Modules to Supervisor-2 Modules
Configuring Generation 2 Switching Modules
Performing a Disruptive Upgrade on a Single Supervisor MDS Family Switch
New Features in Cisco MDS SAN-OS Release 3.0(2)
FICON Port Prohibiting Default
Downgrading from Cisco MDS SAN-OS Release 3.0(2)
Downgrading from Cisco SAN-OS Release 3.2(1)
Configuring Default Settings for the Default Zone
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.0(2)
Release Date: May 17, 2006
Text Part Number: OL-8795-02 V0
This document describes the caveats and limitations for switches in the Cisco MDS 9000 Family. Use this document in conjunction with documents listed in the "Related Documentation" section.
Note
Release notes are sometimes updated with new information on restrictions and caveats. Refer to the following website for the most recent version of the Cisco MDS 9000 Family Release Notes: http://www.cisco.com/en/US/products/hw/ps4159/ps4358/prod_release_notes_list.html
Table 1 shows the on-line change history for this document.
Table 1 Online History Change
A0
05/17/2006
Created release notes
B0
06/23/2006
Added DDTS CSCsd95862, CSCsd19272, CSCse13769, CSCse36768, CSCse42040.
Updated the New Features in Cisco MDS SAN-OS Release 3.0(2) section.
C0
06/30/2006
Added DDTS CSCse33080 and CSCse56522
D0
07/07/2006
Corrected the CWDM part numbers in Table 2.
E0
08/3/2006
Revised DDTS CSCsd89872 and CSCse84811
F0
08/22/2006
Revised the Downgrading from Cisco MDS SAN-OS Release 3.0(2) section.
Added DDTS CSCse65400
G0
09/05/2006
Added DDTS CSCse88606.
H0
09/7/2006
Added DDTS CSCec28084
I0
09/22/2006
Added the external crossbar module part number.
J0
11/29/2006
Added a note to the Downgrading section on having iSCSI enabled during a downgrade.
Added a Limitation and Restriction about CWDM SFPs.
K0
12/07/2006
Added DDTS CSCin95789, CSCsd15794, CSCsd21187, CSCsd81137, CSCsd99599, CSCse22145, CSCse31881, CSCse41442, CSCse44834, CSCse48977, CSCse52582, CSCse57269, CSCse62012, CSCse70275, CSCse71420, CSCse72182, CSCse79582, CSCse85609, CSCse88880, CSCse98656, CSCsf12069, CSCsf18552, CSCsf18884, CSCsf19419, CSCsf21575, CSCsf96043, CSCsf97117, CSCsf98427, CSCsg01963, CSCsg10555, CSCsg12020, CSCsg13769,
and CSCsg15392.L0
02/01/2007
Added DDTS CSCsg03171.
M0
02/22/2007
Added DDTS CSCsd92433, CSCsd97376, CSCse99087, CSCsf27608, CSCsg05037, CSCsg12096, CSCsg29400, CSCsg35972, CSCsg62359, CSCsg82792, CSCsh27840, and CSCsh31236.
N0
04/04/2007
Added DDTS CSCsh83200.
Added the section "Performing a Disruptive Upgrade on a Single Supervisor MDS Family Switch".
Added the section "Configuring Default Settings for the Default Zone".
O0
06/11/2007
Added DDTS CSCsg41556 and CSCsh24256.
P0
07/18/2007
Removed DDTS CSCei82909.
Q0
07/24/2007
Added DDTS CSCsg18834.
R0
09/28/2007
Added DDTS CSCsi49231.
S0
10/23/2007
Removed DDTS CSCsh31236.
Added information about downgrading from Cisco SAN-OS 3.2(1) to the "Limitations and Restrictions" section.
T0
04/30/2008
Added DDTS CSCso63465.
U0
11/13/2008
Added the "Performing a Nondisruptive Software Upgrade on Generation 1 Modules" section.
V0
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.
System Requirements
This section describes the system requirements for Cisco MDS SAN-OS Release 3.0(2) and includes the following topics:
•
Components Supported
Table 2 lists the software 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.0.2
MDS 9500 Supervisor/Fabric-2, SAN-OS software.
MDS 9500 Series only
M95S1K9-3.0.2
MDS 9500 Supervisor/Fabric-I, SAN-OS software.
MDS 9500 Series only
M92S1K9-3.0.2
MDS 9216 Supervisor/Fabric-I, SAN-OS software.
MDS 9200 Series only
M91S1K9-3.0.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
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 ASM or SSM
M9200SSE1K9
Storage Services Enabler package.
MDS 9200 Series with ASM or SSM
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-C9120-K9
MDS 9120 fixed configuration, non-modular, fabric switch (includes 4 full rate ports and 16 host-optimized ports).
MDS 9120 only
External
crossbar moduleDS-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 wavelength mode.
MDS 9500 Series and 9200 Series, except for the MDS 9216
DS-X2-FC10G-LR
X2/SC optics, 10-Gbps Fibre Channel for long wavelength mode.
LC-type fiber-optic SFP
DS-SFP-FC-2G-SW2
2-Gbps/1-Gbps Fibre Channel—short wavelength SFP.
MDS 9000 Family
DS-SFP-FC-2G-LW2
2-Gbps/1-Gbps Fibre Channel—long wavelength SFP.
DS-SFP-FCGE-SW2
1-Gbps Ethernet and 1-Gbps/2-Gbps Fibre Channel—short wavelength SFP.
DS-SFP-FCGE-LW2
1-Gbps Ethernet and 1-Gbps/2-Gbps Fibre Channel—long wavelength SFP.
DS-SFP-GE-T2
1-Gbps Ethernet SFP.
DS-SFP-FC4G-SW3
4-Gbps/2-Gbps/1-Gbps Fibre Channel—short wavelength SFP for DS-X91xx switching modules.
DS-SFP-FC4G-MR3
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-LW3
4-Gbps/2-Gbps/1-Gbps Fibre Channel—long wavelength SFP for DS-X91xx switching modules only. Supports distances up to 10 km.
CWDM4
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-W5 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 Supported on the DS-X9530-SF1-K9, MDS 9500 Series Supervisor module only
3 Supported on the DS-X9530-SF2-K9, MDS 9500 Series Supervisor-2 module only
4 CWDM = coarse wavelength division multiplexing
5 W = Watt
Determining the Software Version
Note
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.
Downloading Software
To download the latest Cisco MDS SAN-OS software, access the Software Center at this URL: http://www.cisco.com/public/sw-center
Upgrading Your Cisco MDS SAN-OS Software Image
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.
Use the following guidelines to nondisruptively upgrade your Cisco MDS SAN-OS Release 3.0(2):
•
•
•
–
–
–
–
–
•
•
–
–
–
–
–
•
•
Caution
Note
Note
Performing a Nondisruptive Software Upgrade on Generation 1 Modules
Generation 1 modules may reload during a nondisruptive SAN-OS software upgrade because of the CompactFlash being unable to partition for the new code. If that happens, the installer aborts and reloads the module.
This issue affects the following modules:
•
•
•
•
This issue might be seen during an upgrade from Cisco SAN-OS Release 3.0(x), 3.1(x) or 3.2(x). It has been addressed for upgrades from SAN-OS Release 3.3(1) or higher. Therefore, you will not be impacted by this issue if you are running SAN-OS Release 3.3(1) when you upgrade to a higher SAN-OS release.
When this problem occurs, the module will automatically reload and may cause the Install All to stop, which will cause the upgrade to be unsuccessful. Error messages similar to the following may be displayed:
Install has failed. Return code 0x40930020 (Non-disruptive upgrade of a module failed).Please identify the cause of the failure, and try 'install all' again.Module 2: Non-disruptive upgrading.-- FAIL. Return code 0x40690009 (Error in downloading image for image upgrade).To avoid this kind of unplanned disruption, follow the methods for identifying and correcting this issue described in Cisco Field Notice 63099, before proceeding with the SAN-OS upgrade.
This Field notice can be found under the Support, Products page for Cisco MDS9500 Series Multilayer Directors selection.
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 running might be disruptive. Some possible scenarios include:
–
–
–
If this problem occurs, syslogs indicate RDI failure and the flapped lSL could remain in a down state because of a domain overlap. This is caused by conflicts between the allowed domains list and the virtual domain requested through RDI.
This issue was resolved in an earlier release, however upgrades from Cisco SAN-OS Release 2.1(1a), 2.1(1b), or 2.1(2a) to Release 3.0(2) when IVR is enabled requires that you use the following workaround.
For VSANS in interop mode 2 or 3, issue an IVR refresh, and then follow the upgrade guidelines listed in "Upgrading Your Cisco MDS SAN-OS Software Image" section.
To upgrade from Cisco SAN-OS Release 2.1(1a), 2.1(1b), or 2.1(2a) to Release 3.0(2) for all other VSANs with IVR enabled, follow these steps:
Step 1
Note
Step 2
Note
Step 3
Example Syslog Error Messages
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
If you are adding new switches running Cisco MDS SAN-OS Release 3.0(x), upgrade all your existing switches to Release 3.0(2) as described in this procedure. Then add new switches.
Note
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 3.
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-standbyReconfiguring SSM Ports Before Upgrading to SAN-OS Release 3.0(2)
Starting with Cisco MDS SAN-OS Release 3.0(1), the SSM front panel ports can no longer be configured in auto mode. Because auto mode is the default for releases prior to Release 3.0(1), you should modify the configuration of the ports before upgrading a SAN-OS software image prior to Release 3.0(1) to Release 3.0(2) to avoid any traffic disruption.
For more information on upgrading SAN-OS software, see "Upgrading Your Cisco MDS SAN-OS Software Image".
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 might cause a disruption if the port is currently operating in E mode.
To make the configuration change 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
Migrating 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
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 listed in this section, 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.
New Features in Cisco MDS SAN-OS Release 3.0(2)
This section describes the new features introduced in this release. For more 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
Domain Manager Fast Restart
Domain Manager normally initiates a build fabric phase when selecting a new principal link. The fast restart feature shortens the time it takes to select this new principal link. When the fast restart feature is enabled and a back-up link is available, Domain Manager takes only few milliseconds to select a new principal link. Also, the reconfiguration required to select the new principal link only affects the two switches that are directly attached to the failed link, and not the entire VSAN.
FICON Configuration
The following FICON features have been added to Cisco Fabric Manager and Device Manager:
•
•
•
•
FICON Port Prohibiting Default
Allows you to change the default setting for port prohibiting.
Limitations and Restrictions
This section lists the limitations and restrictions for this release.
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.0(1). For instructions about how to modify the configuration of the ports before upgrading to SAN-OS Release 3.0(2), see the "Reconfiguring SSM Ports Before Upgrading to SAN-OS Release 3.0(2)" section.
Downgrading from Cisco MDS SAN-OS Release 3.0(2)
Use the following guidelines to nondisruptively downgrade your Cisco MDS SAN-OS Release 3.0(2):
•
•
•
•
–
–
–
•
•
•
•
–
–
–
•
Use the show install all impact downgrade-image CLI command to determine if your downgrade will be nondisruptive.
Downgrading from Cisco SAN-OS Release 3.2(1)
Following a downgrade from Cisco MDS SAN-OS Release 3.2(1) to an earlier SAN-OS release that does not support the Data Mobility Manager (DMM) feature that is offered from SAN-OS Release 3.2(1) onwards, you might have stale configuration information on the switch, if you had provisioned DMM on the SSM. In this situation, you can remove the stale configuration from the SSM by entering the following commands:
switch(config)# poweroff module slot
switch# purge module slot running-configISNS Server
The iSCSI ISNS server feature is not supported in Cisco MDS SAN-OS Release 3.0(2).
FCIP Tape Acceleration
FCIP tape acceleration is not supported in Cisco MDS SAN-OS Release 3.0(2).
CWDM SFPs
Some 2-Gbps CWDM SFPs do not have have speed capability encoded in EEPROM memory and they could negotiate and obtain synchronization up to 4-Gbps on modules that support 4-Gbps 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 fixed to 1- or 2-Gbps instead of Auto.
10-Gbps Inter-Switch Links
•
•
These restrictions will be addressed in a future Cisco SAN-OS software release.
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.
Caveats
This section lists the open and resolved caveats for this release. Use Table 4 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: On rare occasions, when an active supervisor module is removed from a dual supervisor system, a switchover occurs. After being reinserted, the old active supervisor comes up as the standby supervisor, and the new active supervisor can indicate a kernel panic message.
Workaround: None. This issue has been resolved.
•
Symptom: The iSCSI I/O failed on a Windows host at 1% packet loss in an IP network.
Workaround: None. This issue has been resolved.
•
Symptom: The Fabric Manager Server does not automatically handle a fabric merge and split. As a result, you many see duplicate fabrics in the database and the web client.
Workaround: Close all fabrics from the Fabric Manager Server and then reopen the new fabric.
•
Symptom: On a Cisco MDS 9020 Fabric Switch, Fabric Manager displays a 4-Gbps Inter-Switch Link (ISL) as a 3-Gbps ISL.
Workaround: None. This issue has been resolved.
•
Symptom: In interop mode 4, a zone merge can cause a default-zone policy change. This change occurs if one of the switches involved in the merge has no active zone set and the default-zone policy is permit. This occurrence can cause traffic disruption.
Workaround: None. This issue has been resolved.
•
Symptom: When the default gateway is configured for multiple CPP interfaces, the running configuration retains the default gateway associated with only one of the CPP interfaces.
Workaround: None. This issue has been resolved.
•
Symptom: In Fabric Manager, the Device Alias sort function does not work correctly.
Workaround: None. This issue has been resolved.
•
Symptom: In Fabric Manager, the local zone database is not synchronized.
Workaround: None. This issue has been resolved.
•
Symptom: In a system with autocreate PortChannel configured, if there are multiple link flaps or configuration changes on a PortChannel, the PortChannel Manager process memory might run out causing the PortChannel Manager process to crash.
Workaround: None. This issue has been resolved.
Open Caveats
•
Symptom: In some cases, after a nondisruptive upgrade (or downgrade) of 48-port and 24-port 4-Gbps Fibre Channel switching modules from Cisco SAN-OS Release 3.0(1) (or downgrade form Release 3.0(2)) to Release 3.0(2) (or downgrade from Release 3.0(1)), the next port flap could result in oversubscribed ports coming up in error-disabled state.
Workaround: Reload the 48-port and 24-port 4-Gbps Fibre Channel switching modules or upgrade to Cisco SAN-OS Release 3.0(2a) or newer.
•
Symptom: Under certain circumstances, processing a response to the recovery message might cause a software failure. If the host receives a status from the host-end FCIP tunnel for a tape read or Write IO and is slow in responding with a status confirmation, the recovery message is sent by the FCIP Tape Acceleration feature to the host.
Workaround: None.
•
Symptom: In some cases, when a VSAN is in suspended mode, the switch with the suspended VSAN does not appear in the table on the information pane of the GUI.
Workaround: Using Fabric Manager, go to the All VSANs node to unsuspend that switch or VSAN Using Device Manager, go to the FC > VSANs menu, click the General tab and select unsuspend.
•
Symptom: You cannot bind more than one FCIP interface on Gigabit Ethernet port 2 on an MPS-14/2 module in Cisco SAN-OS Release 3.0(1) and Release 3.0(2).
Workaround: None.
•
Symptom: If a module reloads or reinitializes on its own because of an error, and the port channel has one of its member ports on this module, in rare cases, the peer port of this member port will not forward traffic after the module comes back up.
Workaround: Issue the shutdown/no shutdown command sequence on the port channel. If the problem still persists, issue the shutdown/no shutdown command sequence on the affected ports.
•
Symptom: Certain CIM requests leak memory over time.
Workaround: None.
•
Symptom: This problem is observed in Interop mode 4, if IVR is being used with Mcdata switches. The SW-RSCN generated by McData switches does not contain the port WWN and node WWN as required by the Fibre Channel standard. In Cisco MDS SAN-OS Release 3.0(1) and earlier, IVR expected the port WWN in the SW-RCSN. When a device attached to a McData switch goes down, the IVR process does not understand the SW-RCSN generated by the McData switch. As a result, the IVR process does not propagate this information in other VSANs and the device entry continues to stay in the name server database in other VSANs.
Workaround: Remove the device from the IVR active zone set to get rid of the stale entry.
•
Symptom: Removing all devices belonging to a source domain from active zone set or an unreachable source domain might cause traffic disruption from other existing source domains.
Workaround: Add a new member belonging to a source domain that is not currently configured to communicate with the destination domain, to the IVR zone set and reactivate the IVR zone set.
•
Symptom: A CFS merge might fail if all the switches in a large fabric are reloaded.
Workaround: Issue the ivr commit configuration command to perform a blank commit and bring up CFS from the failed state.
•
Symptom: If you have SANTap enabled on your SSM, it might reload on its own if your host applications issue FCP requests with an FCP_DL setting of greater than 58K bytes.
Workaround: None.
•
Symptom: Multiple RSA implementations might fail to properly handle signatures allowing an attacker to forge RSA signatures.
Workaround: None.
•
Symptom: Under rare conditions, it is possible that a Cisco MDS9216i Switch or an MPS-14/2 module running FCIP might experience port software failures, causing a flap on the Gigabit Ethernet interface. You may see messages like the following:
2006 Sep 7 23:13:20 mdspd1 %ETHPORT-5-IF_DOWN_SOFTWARE_FAILURE: Interface GigabitEthernet1/1 is down (Port software failure)
2006 Sep 7 23:13:20 mdspd1 %KERN-3-SYSTEM_MSG: Sibyte: Error: CoreId 1 out of range
2006 Sep 7 23:13:20 mdspd1 %PORT-5-IF_DOWN_INITIALIZING: %$VSAN 2%$ Interface fcip1 is down (Initializing)
2006 Sep 7 23:13:20 mdspd1 %PORT-5-IF_DOWN_SOFTWARE_FAILURE: %$VSAN 4094%$ Interface iscsi1/1 is down (Port software failure)
2006 Sep 7 23:13:26 mdspd1 %IPS_SB_MGR-SLOT1-2-PORT_SOFTWARE_FAILURE: Port software failure, module 1 port 1
2006 Sep 7 23:13:26 mdspd1 %IPS_SB_MGR-SLOT1-2-PORT_SOFTWARE_FAILURE: Port software failure, module 1 port 1
2006 Sep 7 23:13:37 mdspd1 %PORT-5-IF_DOWN_ADMIN_DOWN: %$VSAN 4094%$ Interface iscsi1/1 is down (Administratively down)
2006 Sep 7 23:13:46 mdspd1 %ETHPORT-5-IF_UP: Interface GigabitEthernet1/1 is up
2006 Sep 7 23:13:49 mdspd1 %PORT-5-IF_UP: %$VSAN 2%$ Interface fcip1 is up in mode TE
2006 Sep 7 23:13:49 mdspd1 %PORT-5-IF_UP: %$VSAN 2%$ Interface fcip1 is up in mode TE
Workaround: To reduce the messages or stop them, remove write acceleration if you have it configured for the FCIP interface.
•
Symptom: While using an FCIP link for remote SPAN, it is possible that the FCIP link may flap.
Workaround: Do not use FCIP links for Remote SPAN.
•
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: Files created using the fcanalyzer local command cannot be copied or viewed. Fibre Channel analyzer runs as root, and it creates files with the owner as root. The correct file creation masks are not set when the file is created, so no user other than root can read or copy the file.
Workaround: None.
•
Symptom: LTO-1 tape drives in certain tape libraries cannot be used with the NASB feature. When multiple initiators (such as backup host and NASB engine) issue SCSI write commands, the tape drives respond with a SCSI CHECK CONDITION with Sense - 0x03 and ASC/ASCQ = 0x3b/0x00. They do not handle the transition from the host initiator to the NASB engine initiator. In general, this is an issue for all NASB solutions with this tape drive and library combination.
Workaround: None.
•
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: The mgmt0 interface responds to ARP requests for the IPS interfaces.
Workaround: Configure the mgmt0 interface in a separate VLAN from the IPS interfaces.
•
Symptom: When suspending or deleting VSANs with no delay between those actions, some Fibre Channel interfaces and member ports in a PortChannel becoming suspended or error-disabled.
Workaround: Make sure that you suspend and unsuspend one VSAN at a time, and that you wait a minimum of 60 seconds after you issue the vsan suspend command before you issue any other configuration command.
•
Symptom: The Forwarding Information Base (FIB) process may fail if an IVR zone set push from the Fabric Manager fails because of an SNMP timeout and various switches send conflicting active IVR zone sets.
Workaround: There are two ways to address the problem:
•
•
•
Symptom: Cisco MDS 9100 Series switches and the 9216i switch do not handle counter roll-over appropriately and might reset after being up for 497 days. MPS-14/2 modules are also susceptible and could be reset by the supervisor.
Workaround: None.
•
Symptom: On the Cisco MDS 9000 4-port 10-Gbps Fibre Channel module, one of the applications would crash during port flaps because of a memory corruption in the application.
Workaround: None.
•
Symptom: During a link flap, the FCIP tape acceleration feature could get into a state where if the tape is slow in responding, the backup or restore operation may fail.
Workaround: None.
•
Symptom: When an administrator configures a serverless backup with QiNetix 5.9, the first time (or each time the disks are reconfigured using Volume Explorer on CommVault) the backup fails with a Reservation Conflict error on the disk.
Workaround: Reset the disk and retry the configured serverless backup.
•
Symptom: If the iSNS Client has registered with the iSNS server, and does not send any protocol
messages to server, the the iSNS Server might not timeout idle sessions from the iSNS client.Workaround: Clear the session explicitly from the iSNS Client side.
•
Symptom: 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.
Workaround: Reset the value of the MTU size (576 to 8000 bytes) and issue the no shutdown command on the interface for normal operation.
•
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: The SAN-OS software creates a syslog message after a configuration change through the command-line interface The syslog message looks like this:
switch# 2006 Feb 8 09:00:33 switch %VSHD-5-VSHD_SYSLOG_CONFIG_I: Configuring console from pts/1 (dhcp-peg3-vl30-144-254-7-182.cisco.com)Using the Fabric Manager to make the same configuration change does not result in the same syslog message:
switch# 2006 Feb 8 09:00:56 switch %PORT-5-IF_DOWN_ADMIN_DOWN: %$VSAN 1%$ Interface fc1/5 is down (Administratively down)Workaround: None.
•
Symptom: 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.
Workaround: Increase the VRRP advertisement interval for these interfaces.
•
Symptom: A serverless backup of a volume spanning multiple tapes does not work with CommVault QiNetix 5.9 because CommVault QiNetix 5.9 is not able to determine the end of Tape.
Workaround: None.
•
Symptom: After using the ip access-group command to configure an access list for the mgmt0 interface and saving the running configuration to the startup configuration, the ip access-group command is not present following a reboot of the running configuration. However, the command is in the startup configuration, and the access list is still in the configuration, but the access list is not applied to the mgmt0 interface.
Workaround: Reconfigure the ip access-group command or issue a copy startup-config running-config command to replace the ip access-group command.
•
Symptom: Duplicate entries within an FC alias might cause an ISL isolation between your MDS 9000 switch and a Brocade switch.
Workaround: Remove duplicate entries from the Brocade switch and the link will come up.
•
Symptom: When using Cisco MDS SAN-OS Release 2.1(2e) or earlier to configure PortChannels, the following message may be displayed:
Last membership update failed: port-channel: required service is not responding (err_id 0x402B No portIf this issue occurs, any attempt to delete the PortChannel will fail and no additional operations can be performed on that specific PortChannel that gave the error.
Workaround: Upgrade from Cisco SAN-OS Release 2.1(2e) or earlier to Release 3.0(2a) to prevent the problem from occurring. If the problem has already occurred, an upgrade to Release 3.0(2a) will not correct the problem. Issue the write erase command and reboot the system to correct this problem.
•
Symptom: In interop mode 3, when a regular or IVR zone set is activated from an MDS switch and the active zone set contains aliases, the aliases in the corresponding zone set in the full configuration database are removed.
Workaround: To maintain the alias information, activate a zone set containing aliases from a Brocade switch.
•
Symptom: When using Fabric Manager and SNMP, a login does not occur when a user ID contains a backslash "\".
Workaround: None.
•
Symptom: In some cases of link flapping (a link down or up due to removal or insertion of cables or transceivers) on 10-Gbps ISLs, an early LR might arrive before the ELP exchange is complete and would trigger a transmit credit update to the port. This causes the switch port transmit credit to program to the default value of one (1) instead of the actual number configured. This might cause an impact to performance.
Workaround: None.
•
Symptom 1: SNMP events are not visible in Fabric Manager because Fabric Manager is unable to register to receive SNMP notifications, even though Device Manager is registered to receive SNMP notifications from the MDS switch.
Symptom 2: Cisco EMC Call Home does not send call home messages. Cisco EMC Call Home is a new feature for Cisco SAN-OS Release 3.0(1). This does not affect the other Cisco Call Home features.
Workaround: Choose Admin > Events > Destinations to configure the SNMP notification address from Device Manager. By default, Fabric Manager receives SNMP notifications on port 2162.
•
Symptom: The ISNS server process terminates when ISNS-SERVER is enabled on a switch that has more than 100 iSCSI initiators.
Workaround: None.
•
Symptom: CFS coordinated distribution events are not logged in the syslogs.
Workaround: Use the show cfs internal session-history name command to see the coordinated distribution events that are logged.
•
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: The Cisco MDS 9100 and 9200 Series switches might see excessive debugging messages sent to the CompactFlash causing a rare condition where the CompactFlash could lock up. If this occurs, you might experience an inability to save a new configuration to the Flash and a reboot of the switch is required to recover from this failure. If a successful administrative function requires a write to CompactFlash or there is an update within the fabric, then unexpected behavior might occur.
Workaround: None.
•
Symptom: Issuing the show zone member fcid command on your Cisco MDS 9000 switch might not display the zones with that member FC ID.
Workaround: Configure zone membership by using either pWWN, pWWN + LUN, FC ID, or FC ID + LUN.
•
Symptom: If you try to create a user with a weak password, it fails. Subsequent attempts to create the same user with a strong password also fail because of an inConsistentValue error. This is because when the creation failed in the first set, the undo is not handled completely.
Workaround: Issue the no snmp-server username command in the CLI before the user creation is attempted a second time.
•
Symptom: Fabric Manager Zone Editor may open slowly when a large number of zones are present (for example, 8000 zones).
Workaround. None.
•
Symptom: In Fabric Manager, a device moved from one VSAN to another, might still show up in the Edit IVR Local Full Zone Database dialog box as in the old VSAN. Clicking the refresh button has no effect.
Workaround: Click the rediscover button to rediscover the fabric and then press the refresh button on the Zone dialog box.
•
Symptom: Issuing the setup command might fail after a supervisor switchover, even though the standby supervisor is already in HA-standby state.
Workaround: None.
•
Symptom: The Qlogic 2460 HBA fails to remote boot when it connects to a VT instantiated by SANTap on the SSM because the Qlogic 2460 BIOS sends a test ready unit with an invalid command reference number (CRN) and task attribute field. This same HBA can boot when SANTap and the SSM are not part of the configuration.
Workaround:Use the Qlogic 2340 HBA.
•
Symptom: If you have multiple switches with IVR, and there is a mismatch of IVR VSAN topology and IVR zones which were corrected later, you might get an error message in the logs %FSPF-3-IPC_PROC_ERR: Error in processing IPC message : Opcode = 68, Error code = 401a0013
Workaround: None.
•
Symptom: In Fabric Manager, the active zone set name might display in bold italics instead of plain italics, indicating a pending zone set when there is no actual change pending.
Workaround: None.
•
Symptom: Setting a value higher than 4 for the maximum number of times a packet is retransmitted before TCP closes the connection might product unexpected results. This would occur during a link FCIP tunnel recovery after a short downtime.
Workaround: Configure the TCP maximum retransmissions to values between 1 and 4 only.
•
Symptom: You might experience a system reboot if you are using custom VSAN role-based access control for SNMP users.
Workaround: None.
•
Symptom: Your system might not recover after some types of chassis clock failure and your Supervisor modules might reboot continuously. If the active supervisor reboots, it might report the following message before reboot:
2006 Aug 2 14:36:35 svs-san-m9513-3 %MODULE-2-MOD_DIAG_FAIL: Module 7
(serial: JAB102100U3) reported failure on ports 7/1-7/1 (Supervisor Inband)
due to Fatal runtime sync error. (DevErr is bitmap of failed modules) in
device 88 (device error 0x40)Workaround: None. This issue is resolved.
•
Symptom: A user called snmp-user can successfully log into an MDS switch through the CLI, but cannot log in through Fabric Manager or Device Manager. The login attempt fails with this error: SNMP: Unknown username
Workaround: None.
•
Symptom: A lock request for device-alias might fail, even though the lock is not acquired in the fabric for device-alias. This issue does not happen in a single switch setup but can happen when there are two or more switches with device alias enabled for CFS.
Workaround: Follow these steps:
1.
2.
3.
•
Symptom: When activating an IVR zone set or changing an IVR configuration, the IVR process might crash. The IVR process restarts and status is restored to a pre-crash state. Neither existing traffic nor the configfuration is affected.
Workaround: None. When the IVR process restarts after the crash, the inconsistent database gets corrected.
•
Symptom: On FICON enabled VSANs, if you perform prohibit or unprohibit operations to change the prohibit matrix on a large number of ports, the Cisco MDS 9513 switch might take more time to respond than the ptov protocol timeout.
Workaround: None.
•
Symptom: Following an upgrade from Cisco SAN-OS 2.1(2b) to Cisco SAN-OS 3.0(2), a VSAN carrying FICON traffic was not trunking and the remote Domain Manager was not responding.
Workaround: None.
•
Symptom: No alerts are issued for FCS errors on the sup-fc0 port even though it might affect Fibre Channel communication.
Workaround: None.
•
Symptom: IVR commit complains that one or more remote switches are running Cisco SAN-OS Release 2.04a and earlier.
Workaround: Clear the IVR session on the that was locked, activate the correct IVR full zone set after confirming that it is the same in all switches, or IVR commit on that switch.
•
Symptom: The dynamic port VSAN membership (DPVM) failed after the number of F ports exceeded 64 and a port flap occurred.
Workaround: Keep the number of F ports in a switch below 64.
•
Symptom: Cisco Fabric Manager shows read-write community strings for other communities when a user is logged in with a read-only community string.
Workaround: None.
•
Symptom: Congestion in a switch might happen after a Supervisor 2 switchover, due to a misconfiguration on the standby Supervisor 2 during a downgrade to Cisco SAN-OS Release 3.0(2) or Release 3.0(2a). If this occurs during an in-service downgrade to Cisco SAN-OS Release 3.0.2, you might experience port flaps resulting in traffic disruption.
Workaround: None.
•
Symptom: If your switch is up for a long period of time, such as more than 100 days, zone set activation in Fabric Manager might not reflect the latest results and active-local differences may still be shown.
Workaround: Close and reopen Fabric Manager with the "Accelerate Discovery" option unchecked. This reflects the latest change, but might need to be done after every change.
•
Symptom: When in-order delivery (IOD) is disabled, an entry in the accounting log is posted showing that it is enabled.
Workaround: None.
•
Symptom: The management port link status LED on the Supervisor-2 module might not display the current status.
Workaround: None.
•
Symptom: If a Generation 1 module has any port that is administratively up, but operationally down when you upgrade from SAN-OS Release 2.x to either Release 3.0(1) or Release 3.0(2x), you might experience traffic disruption on that module.
Workaround: Use the shutdown command to shut all the ports operationally down and administratively up on all the Generation 1 modules before upgrading from SAN-OS Release 2.x to Release SAN-OS 3.0(x) or Release 3.0(2x). After the upgrade is complete, the ports can be brought to an administratively up state using the no shutdown command.
•
Symptom: When an IBM mainframe using FICON issues a 32 command to read port statistics, the MDS switch does not respond correctly. The host never clears allegiance which results in the customer being unable to do FICON management, either through Device Manager or the CLI, on the switch itself. If the host continues to periodically send the 32 command to the Control Unit Port (CUP) device, the ficonstat process can run out of memory and can result in supervisor switchover.
Workaround: Perform a system switchover.
•
Symptom: If you use Device Manager to create a target initiator and then you select Edit, Device Manager allows the entry to be a host address with a /24 mask, but it should only allow a /32 mask for a host address.
Workaround: Use Device Manager to remove the entry.
•
Symptom: Following an upgrade from Cisco SAN-OS 2.0(2b) to Cisco SAN-OS 3.0(2) on a switch where Fabric Binding is enabled, the switch displays this message:
%LICMGR-3-LOG_LIC_NO_LIC: No license(s) present for feature ENTERPRISE_PKG. Application(s) shutdown in xx days.
Fabric Binding incorrectly causes the ENTERPRISE_PKG to start the grace period even if Fabric Binding is being used solely for FICON VSANs under the installed MAINFRAME_PKG license.
Workaround: Although there is no workaround for this issue, you can use the show license usage ENTERPRISE_PKG command to verify that Fabric Binding is usine the ENTERPRISE_PKG license.
•
Symptom: If a user attempts to log in using TACACS+ authentication to an MDS switch or an SSH server configured on the switch, the login might fail if password-authentication is the first login method the user tries.
Workaround: Use the keyboard-interactive method as the first login method for SSH.
•
Symptom: When trying to copy a core file from an MDS switch to a location such as a TFTP server, the system asks for the core filename, but the actual filename is not visible in the CLI.
Workaround: To show the supervisor module on which a process crashed and show the process ID, enter the show cores command. To transfer the core file, enter the full command:
copy core://supervisor mod number/pid tftp:•
Symptom: It is possible for the hardware interface 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: 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: 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: Additional information is needed from the show tech-support command.
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: http://www.cisco.com/en/US/products/ps5989/products_documentation_roadmap09186a00804500c1.html.
For information on IBM TotalStorage SAN Volume Controller Storage Software for the Cisco MDS 9000 Family, refer to the IBM TotalStorage Support website: http://www.ibm.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.
CCVP, the Cisco Logo, and the Cisco Square Bridge logo are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn is a service mark of Cisco Systems, Inc.; and Access Registrar, Aironet, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, Follow Me Browsing, FormShare, GigaDrive, GigaStack, HomeLink, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, LightStream, Linksys, MeetingPlace, MGX, Networking Academy, Network Registrar, Packet, PIX, ProConnect, RateMUX, ScriptShare, SlideCast, SMARTnet, StackWise, The Fastest Way to Increase Your Internet Quotient, and TransPath 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. (0609R)
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.
© 2006 Cisco Systems, Inc. All rights reserved.
