 Feedback
|
Table Of Contents
Cisco MDS 9000 Family Release Notes
for Cisco MDS SAN-OS Release 3.0(3)Determining the Software Version
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
Reconfiguring SSM Ports Before Upgrading to SAN-OS Release 3.0(3)
Upgrading the SSI Image on Your SSM
Performing a Disruptive Upgrade on a Single Supervisor MDS Family Switch
Downgrading Your Cisco MDS SAN-OS Software Image
General Downgrading Guidelines
Downgrading your SSI Image on Your SSM
New Features in Cisco MDS SAN-OS Release 3.0(3)
Command Scheduler Remote User Passwords
Virtual Router Redundancy Protocol (VRRP) Interfaces
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(3)
Release Date: October 11, 2006
Text Part Number: OL-8795-04 T0
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
10/11/2006
Created release notes.
B0
10/17/2006
Added DDTS CSCse85609.
C0
10/30/2006
Added DDTS CSCsg22134, CSCsg27527, CSCsg30429, CSCsg37901.
Modified DDTS CSCse98656.
Added a description of a new MIB in the New Features in Cisco MDS SAN-OS Release 3.0(3) section.
D0
11/05/2006
Added DDTS CSCsf96302.
E0
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.
F0
12/07/2006
Added DDTS CSCsd99599.
G0
02/01/2007
Added DDTS CSCsg03171.
H0
02/12/2007
Changed the state of DDTS CSCsg03171 to Resolved.
I0
02/16/2007
AddedCSCsd92433, CSCsd97376, CSCse99087, CSCsf27608, CSCsf30937, CSCsg05037, CSCsg12096, CSCsg17437, CSCsg29400, CSCsg31247, CSCsg31334, CSCsg35972, CSCsg41556, CSCsg52197, CSCsg62359, CSCsg62816, CSCsg80637, CSCsg81220, CSCsg82792, CSCsg90318, CSCsg93198, CSCsg94749, CSCsg95021, CSCsg96497, CSCsg99049, CSCsg99790, CSCsh27840, and CSCsh31236.
J0
02/27/2007
Added DDTS CSCsg72224 and CSCsh40033.
K0
04/04/2007
Added DDTS CSCsh66010 and 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".
L0
06/11/2007
Added DDTS CSCsg15616, CSCsg82777, CSCsh24256, CSCsi14241, CSCsi27133, and CSCsi33540.
M0
07/18/2007
Added DDTS CSCsj04224, CSCsj07363, and CSCsj19105.
Removed DDTS CSCei82909.
N0
08/24/2007
Added DDTS CSCsg18834 and CSCsh95415.
O0
09/28/2007
Added DDTS CSCeh35635, CSCsh05721, CSCsi49231, and CSCsj65565.
P0
10/23/2007
Removed DDTS CSCsh31236.
Added a Note about downgrading from Cisco SAN-OS Release 3.2(1) to the "Downgrading Your Cisco MDS SAN-OS Software Image" section.
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
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.0.3
MDS 9500 Supervisor/Fabric-2, SAN-OS software.
MDS 9500 Series only
M95S1K9-3.0.3
MDS 9500 Supervisor/Fabric-I, SAN-OS software.
MDS 9500 Series only
M92S1K9-3.0.3
MDS 9216 Supervisor/Fabric-I, SAN-OS software.
MDS 9200 Series only
M91S1K9-3.0.3
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 SSM
M9200SSE1K9
Storage Services Enabler package.
MDS 9200 Series with 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 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 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-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
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-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:
•
•
•
•
Note
General Upgrading Guidelines
Use the following guidelines when upgrading to Cisco MDS SAN-OS Release 3.0(3):
•
•
•
–
–
–
–
–
Use Table 4 to determine your nondisruptive upgrade path to Cisco SAN-OS Release 3.0(3). Find the image release number you are currently using in the Current column of the table and use the path recommended.
Note
Table 4 Nondisruptive Upgrade Path to SAN-OS Release 3.0(3)
SAN-OS 3.0(2a)
You can nondisruptively upgrade directly to SAN-OS Release 3.0(3). 1
SAN-OS 3.0(2)
You can nondisruptively upgrade directly to SAN-OS Release 3.0(3). 1
SAN-OS 3.0(1)
You can nondisruptively upgrade directly to SAN-OS Release 3.0(3).
SAN-OS 2.1(3)
You can nondisruptively upgrade directly to SAN-OS Release 3.0(3).
SAN-OS 2.1(2e)
You can nondisruptively upgrade directly to SAN-OS Release 3.0(3).
SAN-OS 2.1(2d)
You can nondisruptively upgrade directly to SAN-OS Release 3.0(3).
SAN-OS 2.1(2b)
You can nondisruptively upgrade directly to SAN-OS Release 3.0(3).
SAN-OS 2.1(2)
Upgrade to SAN-OS Release 2.1(2b) and then upgrade to Release 3.0(3).
or
Upgrade to SAN-OS Release 2.1(2d) and then upgrade to Release 3.0(3).
or.
Upgrade to SAN-OS Release 2.1(2e) and then upgrade to Release 3.0(3).
or
Upgrade to SAN-OS Release 2.1(3) and then upgrade to Release 3.0(3).SAN-OS 2.1(1b)
Upgrade to SAN-OS Release 2.1(2b) and then upgrade to Release 3.0(3).
or
Upgrade to SAN-OS Release 2.1(2d) and then upgrade to Release 3.0(3).
or
Upgrade to SAN-OS Release 2.1(2e) and then upgrade to Release 3.0(3).
or
Upgrade to SAN-OS Release 2.1(3) and then upgrade to Release 3.0(3).SAN-OS 2.1(1a)
Upgrade to SAN-OS Release 2.1(2b) and then upgrade to Release 3.0(3).
or
Upgrade to SAN-OS Release 2.1(2d) and then upgrade to Release 3.0(3).
or
Upgrade to SAN-OS Release 2.1(2e) and then upgrade to Release 3.0(3).
or
Upgrade to SAN-OS Release 2.1(3) and then upgrade to Release 3.0(3).SAN-OS 2.0(x)
Upgrade to SAN-OS Release 2.1(2b) and then upgrade to Release 3.0(3).
or
Upgrade to SAN-OS Release 2.1(2d) and then upgrade to Release 3.0(3).
or
Upgrade to SAN-OS Release 2.1(2e) and then upgrade to Release 3.0(3).
or
Upgrade to SAN-OS Release 2.1(3) and then upgrade to Release 3.0(3).SAN-OS 1.x
Upgrade to SAN-OS Release 1.3(4a), then to Release 2.1(2b), and then upgrade to Release 3.0(3).
1 See CSCse36768 for related information.
Use Table 5 to determine your nondisruptive upgrade path to Cisco SAN-OS Release 3.0(3). 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.
Performing a Nondisruptive Software Upgrade on Generation 1 Modules
Generation 1 modules may reload during a nondisruptive SAN-OS software upgrade because of the CompactFlash being unable to partition for the new code. If that happens, the installer aborts and reloads the module.
This issue affects the following modules:
•
•
•
•
This issue might be seen during an upgrade from Cisco SAN-OS Release 3.0(x), 3.1(x) or 3.2(x). It has been addressed for upgrades from SAN-OS Release 3.3(1) or higher. Therefore, you will not be impacted by this issue if you are running SAN-OS Release 3.3(1) when you upgrade to a higher SAN-OS release.
When this problem occurs, the module will automatically reload and may cause the Install All to stop, which will cause the upgrade to be unsuccessful. Error messages similar to the following may be displayed:
Install has failed. Return code 0x40930020 (Non-disruptive upgrade of a module failed).Please identify the cause of the failure, and try 'install all' again.Module 2: Non-disruptive upgrading.-- FAIL. Return code 0x40690009 (Error in downloading image for image upgrade).To avoid this kind of unplanned disruption, follow the methods for identifying and correcting this issue described in Cisco Field Notice 63099, before proceeding with the SAN-OS upgrade. This Field notice can be found under the Support, Products page for Cisco MDS9500 Series Multilayer Directors selection.
The caveat associated with this issue is CSCsm62295.
Upgrading 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.0(x). A FICON fabric can upgrade from the Cisco SAN-OS Releases 2.0(2b) and 2.0(3) to Release 3.0(x). However, 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 "General Upgrading Guidelines" 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.0(3)
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
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 4, 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.0(3):
•
•
•
•
•
•
–
–
–
–
–
–
–
Use Table 6 to determine your nondisruptive downgrade path from Cisco SAN-OS Release 3.0(3). 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
Table 6 Nondisruptive Downgrade Path from SAN-OS Release 3.0(3)
SAN-OS 3.0(2a)
You can nondisruptively downgrade directly from SAN-OS Release 3.0(3). 1
SAN-OS 3.0(2)
You can nondisruptively downgrade directly from SAN-OS Release 3.0(3). 1
SAN-OS 3.0(1)
You can nondisruptively downgrade directly from SAN-OS Release 3.0(3).
SAN-OS 2.1(3)
You can nondisruptively downgrade directly from SAN-OS Release 3.0(3).
SAN-OS 2.1(2e)
You can nondisruptively downgrade directly from SAN-OS Release 3.0(3).
SAN-OS 2.1(2d)
You can nondisruptively downgrade directly from SAN-OS Release 3.0(3).
SAN-OS 2.1(2b)
You can nondisruptively downgrade directly from SAN-OS Release 3.0(3).
SAN-OS 2.1(2)
Downgrade to SAN-OS Release 2.1(2b) and then downgrade to Release 2.1(2).
SAN-OS 2.1(1b)
Downgrade to SAN-OS Release 2.1(2b) and then downgrade to Release 2.1(1b).
SAN-OS 2.1(1a)
Downgrade to SAN-OS Release 2.1(2b) and then downgrade to Release 2.1(1a).
SAN-OS 2.0(4a)
Downgrade to SAN-OS Release 2.1(2b) and then downgrade to Release 2.0(4a).
SAN-OS 2.0(4)
Downgrade to SAN-OS Release 2.1(2b) and then downgrade to Release 2.0(4).
SAN-OS 2.0(3)
Downgrade to SAN-OS Release 2.1(2b) and then downgrade to Release 2.0(3).
SAN-OS 2.0(2b)
Downgrade to SAN-OS Release 2.1(2b) and then downgrade to Release 2.0(2b).
SAN-OS 2.0(1b)
Downgrade to SAN-OS Release 2.1(2b) and then downgrade to Release 2.0(1b).
SAN-OS 1.x
Downgrade to SAN-OS to Release 2.1(2b), then to Release 1.3(4a), and then downgrade to your SAN-OS 1.x release.
1 See CSCsg10555 for related information.
Use Table 7 to determine your nondisruptive downgrade path from Cisco SAN-OS Release 3.0(3). 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.
Downgrading your 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.0(3)
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
Command Scheduler Remote User Passwords
This feature allows you to specify passwords for remote users to allow them configure command scheduler jobs.
IVR Zones and Zone Members
This feature increases the limits for IVR zones to 8,000 and for IVR zone members to 10,000.
Preferred Path
This feature allows you to specify preferred path route maps for Fibre Channel data traffic. A new MIB, CISCO-PREFERRED-PATH-MIB, configures and monitors this Preferred Path feature.
User Configuration Limit
The maximum number of users that you can create on an MDS switch is 256. Previously, there was no limit.
Fabric Manager Enhancements
The Cisco MDS 9000 Family Fabric Manager supports:
•
•
•
New MIB
Cisco MDS SAN-OS Release 3.0(3) includes the following MIB: CISCO-IP-NW-DISCOVERY-MIB. This new MIB replaces CISCO-ISNS-IP-NW-DISCOVERY-MIB, which is no longer supported.
Limitations and Restrictions
This section lists the limitations and restrictions for this release.
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.
Fabric Manager
Observe the following limitations or restrictions for the Cisco SAN-OS Release 3.0(3) 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.0(1). For instructions about how to modify the configuration of the ports before upgrading to SAN-OS Release 3.0(3), see the "Reconfiguring SSM Ports Before Upgrading to SAN-OS Release 3.0(3)" 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.
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 8 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 mgmt0 interface responds to ARP requests for the IPS interfaces.
Workaround: None. This issue is resolved.
•
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: None. This issue is resolved.
•
Symptom: If you have a Port Channel with multiple FCIP tunnels, and Write Acceleration is enabled on the the FCIP tunnels, the end device might reboot with an error after the PortChannel comes up or if fcping is issued to that device.
Workaround: None. This issue is resolved.
•
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. This issue is resolved.
•
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. This issue is resolved.
•
Symptom: If a module reloads or reinitializes on its own because of an error, and the PortChannel 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: None. This issue is resolved.
•
Symptom: Certain CIM requests leak memory over time.
Workaround: None. This issue is resolved.
•
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: None. This issue is resolved.
•
Symptom: A CFS merge might fail if all the switches in a large fabric is reloaded.
Workaround: None. This issue is resolved.
•
Symptom: Removing all devices belonging to a source domain from active zoneset or an unreachable source domain might cause traffic disruption from other existing source domains.
Workaround: None. This issue is resolved.
•
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. This issue is resolved.
•
Symptom: Multiple RSA implementations might not handle signatures properly, allowing an attacker to forge RSA signatures.
Workaround: None. This issue is resolved.
•
Symptom: iSCSI might be affected if the TCP timestamp option is not enabled and there is a very high drop rate in the network (around 1%), it is possible that the TCP connection could be closed even before the configured number of retransmits occur.
Workaround: None. This issue is resolved.
•
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: None. This issue is resolved.
•
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: None. This issue is resolved.
•
Symptom: Duplicate entries within an Fibre Channel alias might cause an ISL isolation between your Cisco MDS 9000 switch and a Brocade switch.
Workaround: None. This issue is resolved.
•
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: None. This issue is resolved.
•
Symptom: In Fabric Manager, the active zone set displayed may be inconsistent with the local zone set. This occurs with zone members, such as iSCSI, that have multiple end ports or an FC alias name that points to different ports.
Workaround: None. This issue is resolved.
•
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 will be removed.
Workaround: None. This issue is resolved.
•
Symptom: When using Fabric Manager and SNMP, a login does not occur when a user ID contains a backslash "\".
Workaround: None. This issue is resolved.
•
Symptom: CFS coordinated distribution events are not logged in the syslogs.
Workaround: None. This issue is resolved.
•
Symptom: The Cisco MDS 9100 and 9200 series switches running SAN-OS Release 3.0(1) or Release 3.0(2) 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. On Cisco MDS 9500 and 9200 switches running SAN-OS Release 3.0(1) and Release 3.0(2), the CompactFlash lock up might occur on the modules resulting in an inability to successfully perform in-service upgrades to that module and a reload of the module alone is required to recover from this failure.
Workaround: None. This issue is resolved.
•
Symptom: Issuing the show zone member fcid fcid-id command in your Cisco MDS 9000 switch might not display the zones with that member FC ID.
Workaround: None. This issue is resolved.
•
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: None. This issue is resolved.
•
Symptom: Fabric Manager Zone Editor may open slowly when a large number of zones are present (for example, 8000 zones).
Workaround. None. This issue is resolved.
•
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: None. This issue is resolved.
•
Symptom: Issuing the setup command might fail after a supervisor switchover, even though the standby supervisor is already in HA-standby state.
Workaround: None. This issue is resolved.
•
Symptom: RMON alarms do not show up in the running configuration when they are configured through Threshold Manager using 64-bit alarms.
Workaround: None. This issue is resolved.
•
Symptom: If you have multiple switches with IVR enabled, and there is a mismatch of IVR VSAN topology and IVR zones that 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 = 401a0013Workaround: None. This issue is resolved.
•
Symptom: In Fabric Manager, the Active Zoneset Name might display in bold italics instead of plain italic font, indicating a pending zoneset when there is no actual change pending.
Workaround: None. This issue is resolved.
•
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: None. This issue is resolved.
•
Symptom: You might experience a system reboot if you are using custom VSAN role-based access control for SNMP users.
Workaround: None. This issue is resolved.
•
Symptom: An Fibre Channel domain restart disrupts the EMC Invista controller connectivity with the SSM.
Workaround: None. This issue is resolved.
•
Symptom: Your Cisco MDS 9513 switch 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: When activating an IVR zone set or changing an IVR configuration, the IVR process might crash.
Workaround: None. This issue is resolved.
•
Symptom: A lock request for device alias configuration might fail, even though the lock is not acquired in the fabric for device aliases. This issue does not happen in a single switch setup but can happen when there are two or more switches with CFS enabled for device aliases.
Workaround: None. This issue is resolved.
•
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 Director might take more time to respond than the ptov protocol timeout.
Workaround: None. This issue is resolved.
•
Symptom: No alerts are issued for FCS errors on the sup-fc0 port even though it might affect Fibre Channel communication.
Workaround: None. This issue is resolved.
•
Symptom: In a fabric with more than one switch, where a switch that is connected to a host that can generate the RSCN to the switch, you might see the following syslog message on one of the remote switches:
2006 Oct 27 21:23:12 switch-1 %RSCN-2-SWRSCN_REJECT: %$VSAN <vsan-id>%$ SW-RSCN rejected: Sending SW-RJT: Affected domain can not be the local domain: fcid <0xFFFCDD>, Reason code-Logical error, Reason code expl-No additional explanation
The RSCN generated by the host will be distributed by the switch (that is connected to the host) sending the SW-RSCN to all the remote switches.Workaround: None. This issue is resolved.
•
Symptom: IVR commit complains that one or more remote switches are running Cisco SAN-OS Release 2.04a and earlier.
Workaround: None. This issue is resolved
•
Symptom: The dynamic port VSAN membership (DPVM) failed after the number of F ports exceeded 64 and a port flap occurred.
Workaround: None. This issue is resolved.
•
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. This issue is resolved.
•
Symptom: If your switch is up for a long period of time, 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: None. This issue is resolved.
•
Symptom: The management port link status LED on the Supervisor-2 module might not display the current status.
Workaround: None. This issue is resolved.
•
Symptom: If a Generation 1 module has any port 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: None. This issue is resolved.
•
Symptom: If you use Fabric Manager to log on to a Cisco MDS 9000 switch with AAA authentication configured, you might see an error message saying that a maximum of 16 CLI sessions have been reached on the switch.
Workaround: None. This issue is resolved.
Open Caveats
•
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: On the Cisco MDS 9000 Family 12-port, 24-port and 48-port 4-Gbps Fibre Channel modules and the Cisco MDS 9000Family 4-port 10-Gbps Fibre Channel module, the communications component that communicates with the Supervisor modules has an issue where its receiver erroneously indicates an available frame when there is none. As a result, the software might attempt to access a memory location, which could lead to a kernel crash. This situation is extremely rare.
Workaround: None.
•
Symptom: When the server.hostname parameter is set to an IP address in the server.properties file, the Fabric Manager Server restart message repeatedly displays in the Fabric Manager Client open dialog box.
Workaround: None. This issue is resolved in the Cisco MDS 9000 Family Fabric Manager Release 3.0(3a). For more information, refer to the Release Notes for Cisco MDS 9000 Family Fabric Manager Release 3.0(3a).
•
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: Cisco MDS SAN-OS Release 3.0(3) does not support fabric binding in interop mode 4.
Workaround: None.
•
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: Re-install the module.
•
Symptom: If a management application makes multiple SNMP get or get next requests for interface information in bulk, such as interface counters, and these requests are made in a short period of time, the SNMP process may occasionally crash.
Workaround: Do not make frequent multiple requests to get the performance related data.
•
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: 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: 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: 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 the iSNS Client has registered with the iSNS server, and does not send any protocol messages to the server, the iSNS Server might not time out idle sessions from the iSNS client.
Workaround: Clear the session explicitly from the iSNS Client side.
•
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: Occasionally, the Common Information Model (CIM) server may be automatically restarted because of an internal error. In this case, the connected CIM client is disconnected.
Workaround: You must explicitly reconnect the CIM client to the CIM server.
•
Symptom: On rare occasions, the PortChannels with FCIP interface members fail to come up when the switch reboots. This occurrence happens when the startup configuration has a default switch port trunk mode setting that does not match the configured trunk mode for PortChannel members (FCIP interfaces). Also, the startup configuration shows any explicit switch port trunk mode setting for the PortChannel.
Workaround: Reconfigure the switch port trunk mode on the PortChannel.
•
Symptom: The iSNS server might crash when iSCSI is disabled and iSNS is enabled using Fabric Manager.
Workaround: None.
•
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 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: 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: 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: On rare occasions following an upgrade from Cisco MDS SAN-OS 2.1(2b) to Cisco SAN-OS 3.0(2a), module configurations might be removed.
Workaround: Reload the affected modules and then reconfigure or copy the configurations for the affected interfaces to the switch.
•
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: When in-order delivery (IOD) is disabled, an entry in the accounting log is posted showing that it is enabled.
Workaround: None.
•
Symptom: Time zone changes that are executed on an MDS switch do not take effect on the 12-port, 24-port, and 48 port 1-Gbps/2-Gbps/4-Gbps Fibre Channel modules, and on the 4-port 10-Gbps module. This issue occurs in SAN-OS Releases 3.0(1), 3.0(2), 3.0(2a), and 3.0(3).
Time zone changes that are executed on an MDS switch do not take effect on the 16-port or 32-port 1-Gbps/2-Gbps module, on the 4-port or 8-port Gigabit Ethernet IP services module, the MPS 14/2 module, and on the SSM. This issue occurs in SAN-OS Release 3.0(3).
This issue has no effect on functionality. However, debug messages and syslogs from the MDS switching modules will have incorrect timestamps if the time zone is configured on an MDS switch.
Workaround: None.
•
Symptom: Graceful shutdowns of ISLs are not supported for IVR traffic.
Workaround: Increase the fspf cost on the link before it is shut down, so that traffic will flow through an alternate path.
•
Symptom: Following an upgrade of the Fabric Manager to Cisco MDS SAN-OS 3.0(3), some hosts have a status of "not in fabric" in the VSAN local zone. In addition, the hosts do not appear in the VSAN host table or in the IVR device database. As a result, Fabric Manager cannot be used to configure zones or IVR zones for these hosts.
Workaround: None. This issue is resolved in the Cisco MDS 9000 Family Fabric Manager Release 3.0(3a). For more information, refer to the Release Notes for Cisco MDS 9000 Family Fabric Manager Release 3.0(3a).
•
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:If you click the Dump FM Server popup menu item, or use the Fabric Manager Server info command, the Fabric Manager Server displays an error message.
Workaround: None. This issue is resolved in the Cisco MDS 9000 Family Fabric Manager Release 3.0(3a). For more information, refer to the Release Notes for Cisco MDS 9000 Family Fabric Manager Release 3.0(3a).
•
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, you can use the show license usage ENTERPRISE_PKG command to verify that Fabric Binding is using the ENTERPRISE_PKG license.
•
Symptom: After you install an MPS-14/2 module, the power capacity level on the switch might be incorrect.
Workaround: To correct the power capacity level, switch the power capacity from Redundant to Combined and then back to Redundant again.
•
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: On all Cisco MDS Fibre Channel modules, remote spanning does not work if the size of the spanned packet is more than 2112 octets. Remote spanning works normally for packet sizes less than or equal to 2112 octets.
Workaround: None.
•
Symptom: Files placed on the volatile: partition cannot be copied or viewed by a user with the network-admin role.
Workaround: Log in to the MDS switch. with the same user that created the file and view or copy the file from the volatile partition.
•
Symptom: On the Cisco MDS 9000 Family 12-port, 24-port and 48-port 4-Gbps Fibre Channel modules and the Cisco MDS 9000 Family 4-port 10-Gbps Fibre Channel module, it is possible during port flaps to have a credits overrun or underrun situation that might bring down all or some of the ports, or possibly cause the module to reboot in some rare cases.
Workaround: None.
•
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: When you use the run-script command in conjunction with conditional services such as TACACS+ and IVR, the script fails with command parse errors.
Workaround: None.
•
Symptom: The Fabric Manager Configuration Analysis Tool shows mismatches when there are none.
Workaround: None.
•
Symptom: If an MDS switch running Cisco SAN-OS 3.0(x) is configured so that the default gateway is on the FCIP network and there is a static route for the management LAN, then the FCIP tunnel might go down.
Workaround: Configure the default gateway on the management LAN and a static route for the FCIP tunnel.
•
Symptom: Following a reboot of a SAN Volume Controller (SVC) node, all SVC Nx port registers are Fibre Channel 4 in the native VSAN, but some of them are not exported in the IVR VSAN.
Workaround: Issue the shut command followed by the no shut command.
•
Symptom: Following an upgrade to Cisco SAN-OS 3.x in a chassis where Generation 2 modules are present and FC flows are present, if you create and delete FC flows several times, then FC flows might not be able to be created anymore. You might see the following message in Fabric Manager when you click Finish after creating an FC flow:
Snmp: acltcam: Unable to allocate memory
Workaround: To resolve this issue, follow these steps:
6.
7.
8.
•
Symptom: Fabric Manager does not allow you to create more than 2048 flows per switch. The actual limitation is 2048 flows for a Generation 2 module and 1024 flows for a Generation 1 module.
Workaround: None.
•
Symptom: When an SSH session is opened for only a brief period, an MDS switch may send the following kinds of messages, indicating that the local tty is not available:
%DAEMON-3-SYSTEM_MSG: error: ioctl(TIOCSCTTY): Input/output error
%DAEMON-3-SYSTEM_MSG: error: open /dev/tty failed - could not set controlling tty: No such device or address
%DAEMON-3-SYSTEM_MSG: error: /dev/pts/0: No such file or directory
Workaround: Set the logging level of the daemon message to 2 or higher.
•
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: 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: When a device is removed from 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: To remove the state entry from the name server database, follow these steps:
1.
2.
3.
4.
•
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: 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: 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.
Workaround: Set the clock through the CLI.
•
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: 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: 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: If the startup configuration and the running configuration contain the same configuration items, but have differences in terms of format (spaces or empty lines), then the output of the show running-config diff command will not be blank.
Workaround: Carefully examine the output of the show running-config diff command to determine if the startup configuration and running configuration are actually different, or if there are just format differences in the two files.
•
Symptom: When you create a user with the name user, only the snmp-user is created and not the corresponding CLI user. There is no warning message about this.
Workaround: None.
•
Symptom: When Fabric Manager, Device Manager, or the CLI is unable to acquire device allegiance (meaning that the host has exclusive control of the device), an enhanced error message specifies that the configuration must be retried due to contention from the mainframe configuration.
Workaround: Issue the command again.
•
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: Additional information is needed from the show tech-support command.
Workaround: None.
•
Symptom: When httpd port 80 is blocked on the switch, it takes a long time for Fabric Manager and Device Manager to discover the fabric.
Workaround: Set the TCP timeout to 500 ms in the runtime arguments for Fabric Manager Server.
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.
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)
© 2006 Cisco Systems, Inc. All rights reserved.
