Table Of Contents
Cisco MDS 9000 Family Release Notes
for Cisco MDS SAN-OS Release 2.1(1a)Determining the Software Version
Performing a Disruptive Upgrade on a Single Supervisor MDS Family Switch
New Features in Cisco MDS SAN-OS Release 2.1(1a)
Distributed Configuration Copy
Enhance IP Compression Auto Mode
Limit of iSCSI Connections Increased
Network-Accelerated Serverless Backup
Cisco Product Security Overview
Reporting Security Problems in Cisco Products
Obtaining Technical Assistance
Cisco Technical Support Website
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Cisco MDS 9000 Family Release Notes
for Cisco MDS SAN-OS Release 2.1(1a)
Release Date: April 6, 2005
Text Part Number: OL-7411-01 C2
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 On-Line History Change
A0
4/6/2005
Created release notes
B0
4/12/2005
Added DDTS CSCeh04183
C0
4/13/2005
Added DDTS CSCeg81089
D0
4/26/2005
Added iSNS information to the Limitations and Restrictions section
E0
5/3/2005
Added DDTS CSCeg82721 and CSCeh65824
F0
5/9/2005
Added the Adding IVR Virtual Domains information
G0
5/18/2005
Added DDTS CSCeh92604 and CSCeh42252
H0
5/24/2005
Added DDTS CSCeg66225
I0
5/31/2005
Added DDTS CSCeh96928
J0
06/01/2005
Added DDTS CSCeg24199 and CSCeh92843
K0
06/06/2005
Changed the state of DDTS CSCeh92843
L0
06/23/2005
Added DDTS CSCei25319
M0
08/04/2005
Added DDTS CSCed57251, CSCeh61610, CSCeh64080, CSCec31365, CSCeg20932, CSCeg53114, CSCeh19639, CSCeh52280, CSCeh56143, CSCeh82490, CSCeh83514, CSCeh87985, CSCeg90336, CSCeh52973, CSCeh87930, CSCeh90270, CSCeh93625, CSCei01431, CSCeh73101, CSCei29086, CSCeh39705, CSCeh49483, CSCeh70727, CSCeh71865, CSCeh73149, CSCeh85768, CSCeh87930, CSCeh90270, CSCeh91293, CSCeh93109, CSCeh95139, CSCei02196, CSCei18837, CSCeh08307, CSCeh79330, CSCeh82166, CSCei08541, CSCei22596, CSCei31020, and CSCin81851
Added iSCSI information to the Limitations and Restrictions section.
N0
08/05/2005
Added DDTS CSCeh41099
O0
08/11/2005
Added DDTS CSCeh70232
P0
08/22/2005
Removed DDTS CSCeh61610
Q0
08/23/2005
Added DDTS CSCeh61610
R0
09/20/2005
Added DDTS CSCei88345
S0
11/03/2005
Added DDTS CSCeh69186
T0
12/07/2005
Added DDTS CSCsc31424
U0
12/30/2005
Added DDTS CSCei91968
V0
02/22/2006
Added DDTS CSCsc23435
WO
05/26/2006
Removed DDTS CSCeh52973
Added DDTS CSCeg33121, CSCsd29338, CSCeg12962, CSCeg84871, CSCeh04183, CSCeh30951, CSCeh70232, CSCei10774, CSCei19822, CSCei36082, CSCei79457, CSCei48889, CSCei57342, CSCei58652, CSCei67982, CSCei86399, CSCei91676, CSCej08751, CSCin92870, CSCin95789, CSCsc09732,CSCsc33788, CSCsc48919, CSCsc97070, CSCsd34882, CSCsd71701, and CSCsd76429
X0
06/06/2006
Removed DDTS CSCed16845
Y0
09/05/2006
Added DDTS CSCsd78967
Z0
09/13/2006
Added DDTS CSCsf21970
A1
11/07/2006
Added DDTS CSCsg15392
B1
02/23/2007
Added DDTS CSCse99087, CSCsg03171, and CSCsh27840.
C1
04/04/2007
Added the section "Performing a Disruptive Upgrade on a Single Supervisor MDS Family Switch".
C2
08/24/2007
Added DDTS CSCsd83775.
Contents
This document includes the following sections:
•
•
•
•
Introduction
The Cisco MDS 9000 Family of multilayer directors and fabric switches offers intelligent fabric-switching services that realize maximum performance while ensuring high reliability levels. These switches combine robust and flexible hardware architecture with multiple layers of network and storage management intelligence. This powerful combination enables highly available, scalable storage networks that provide advanced security and unified management features.
The Cisco MDS 9000 Family 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 2.1(1a) 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
M95S1K9-2.1.1
MDS 9500 Supervisor/Fabric-I, SAN-OS software.
MDS 9500 Series only
M92S1K9-2.1.1
MDS 9216 Supervisor/Fabric-I, SAN-OS software.
MDS 9200 Series only
M91S1K9-2.1.1
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-C9509
MDS 9509 director, base configuration (9-slot modular chassis includes 7 slots for switching modules and 2 slots for supervisor modules—SFPs1 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-C9120-K9
MDS 9120 fixed configuration, non-modular, fabric switch (includes 4 full rate ports and 16 host-optimized ports).
MDS 9120 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
Supervisor modules
DS-X9530-SF1-K9
MDS 9500 Supervisor/Fabric-I, module.
MDS 9500 Series only
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).
Services modules
DS-X9308-SMIP
8-port Gigabit Ethernet IP Storage Services module.
DS-X9304-SMIP
4-port Gigabit Ethernet IP Storage Services module.
DS-X9032-SMV
32-port Fibre Channel Advanced Services Module (ASM).
DS-X9032-SSM
MDS 9000 32-port 1-Gbps/2-Gbps Fibre Channel Storage Services Module (SSM).
DS-X9560-SMC
Caching Services Module (CSM).
DS-X9302-14K9
14-port Fibre Channel/2-port Gigabit Ethernet Multiprotocol Services (MPS-14/2) module.
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.
CWDM2
CWDM-SFP-xxxx-2G
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
CWDM-MUX-4
Add/drop multiplexer for four CWDM wavelengths.
CWDM-MUX-8
Add/drop multiplexer for eight CWDM wavelengths.
CWDM-CHASSIS-2
Two slot chassis for CWDM add/drop multiplexer(s).
Power supplies
DS-CAC-300W
300-W3 AC power supply.
MDS 9100 Series only
DS-CAC-845W
845-W AC power supply.
MDS 9200 Series only
DS-CAC-2500W
2500-W AC power supply.
MDS 9509 only
DS-CDC-2500W
2500-W DC 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.
CompactFlash
MEM-MDS-FLD512M
MDS 9500 supervisor CompactFlash disk, 512MB.
MDS 9500 Series only
Port analyzer adapter
DS-PAA-2
A standalone Fibre Channel-to-Ethernet adapter that allows for simple, transparent analysis of Fibre Channel traffic in a switched fabric.
MDS 9000 Family
1 SFP = small form-factor pluggable
2 CWDM = coarse wavelength division multiplexing
3 W = Watt
Determining the Software Version
Note
To determine the version of the Cisco MDS SAN-OS software currently running on a Cisco MDS 9000 Family switch using the CLI, log into the switch and enter the show version EXEC command.
To determine the version of the 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.
Image Upgrade
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.
You can nondisruptively upgrade to Cisco MDS SAN-OS Release 2.1(1a) from any SAN-OS software release beginning with Release 1.3(x). If you are running an older version of the SAN-OS, upgrade to Release 1.3(x) and then Release 2.1(1a).
When downgrading from Cisco MDS SAN-OS Release 2.1(1a) to Release 1.3(x), you might need to disable new features in Release 2.1(1a) for a nondisruptive downgrade. Issuing the install all command from the CLI, or using Fabric Manager to perform the downgrade enables the compatibility check. The check indicates that the downgrade is disruptive and the reason is "current running-config is not supported by new image."
Compatibility check is done:Module bootable Impact Install-type Reason------ -------- -------------- ------------ ------2 yes disruptive reset Current running-config is not supported by new image3 yes disruptive reset Current running-config is not supported by new image5 yes disruptive reset Current running-config is not supported by new image6 yes disruptive reset Current running-config is not supported by new imageAt 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
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, 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 2.1(1a)
This section describes the new features introduced in this release. For more information about the features listed, refer to the documentation set listed in the "Related Documentation" section.
Note
CFS Enhancements
By default Cisco Fabric Services (CFS) is in the distribute mode. In the distribute mode, fabric-wide distribution is enabled. Applications can distribute data and configuration to all the CFS-capable switches in the fabric where the application exists.
In the no cfs distribute mode, fabric-wide distribution is disabled. CFS and the applications using CFS on that switch are isolated from the rest of the fabric even though there might be physical connectivity. All CFS operations are restricted to the particular switch. All the CFS commands continue to work much like a physically isolated switch.
The show cfs status command is an executive level command that shows whether CFS fabric distribution mode is enabled or disabled.
Distributed Configuration Copy
As of Cisco MDS SAN-OS Release 2.1(1a), you can use CFS to instruct the other switches in the fabric to save their configurations to their local NVRAM using the copy running-config startup-config fabric command.
Enhance IP Compression Auto Mode
The IP compression feature behavior differs between the IPS module(s) and the MPS-14/2 module—while mode2 and mode3 perform software compression in both modules, mode1 performs hardware-based compression in MPS-14/2 modules, and software compression in IPS-4 and IPS-8 modules.
As of Cisco MDS SAN-OS Release 2.1(1a), the auto mode option uses a combination of compression modes to effectively utilize the WAN bandwidth. The compression modes change dynamically to maximize the WAN bandwidth utilization.
Note
iSCSI Immediate Data
Cisco MDS SAN-OS Release 2.1(1a) supports iSCSI immediate data and unsolicited data feature if the initiator requests it during the login negotiation phase. immediate data is iSCSI write data that is contained in the data segment of an iSCSI command PDU, such as the write command and write data together in one PDU. Unsolicited data is iSCSI write data that an initiator sends to the iSCSI target (MDS in our case) in an iSCSI data-out PDU without having to receive an explicit R2T (Ready to transfer) PDU from the target.
These two features help reduce I/O time for small write commands because it removes one round-trip between the initiator and the target for R2T PDU. The iSCSI target of the MDS switch allows up to
64 KB of unsolicited data per command. This is controlled by the FirstBurstLength parameter during iSCSI login negotiation phase.Limit of iSCSI Connections Increased
In Cisco MDS SAN-OS Release 2.0, a limit of 200 iSCSI connections on each IPS/MPS 14/2 port was imposed. As of Cisco MDS SAN-OS Release 2.1(1a), the number of iSCSI connections on each IPS and MPS 14/2 por tis now up to 500 connections per port.
IVR Enhancements
This section describes the new IVR features for this release.
Adding IVR Virtual Domains
Cisco MDS SAN-OS Release 2.1(1) enables the addition of IVR virtual domains to the assigned domains list in remote VSANs by default. When adding IVR domains, all IVR virtual domains that are currently present in the fabric (and any virtual domain that is created in the future) will appear in the assigned domain list for that VSAN.
IVR NAT
IVR NAT allows you to set up IVR in a fabric without the need for a unique domain ID on every switch in the IVR path. When IVR NAT is enabled, the virtualized end device that appears in the native VSAN uses a virtual domain ID that is unique to the native VSAN.
Note
IVR LUN Zoning
As of Cisco MDS SAN-OS Release 2.1(1a), IVR directly supports LUN zoning.
IVR VSAN Topology
IVR uses a configured IVR VSAN topology to determine how to route traffic between the initiator and the target across the fabric. You can configure this IVR VSAN topology manually on an IVR-enabled switch and distribute the configuration using CFS, or starting in Cisco MDS SAN-OS Release 2.1(1a), you can configure IVR topology in auto mode. This mode automatically builds the IVR VSAN topology and maintains the topology database when fabric reconfigurations occur. Auto mode distributes the IVR VSAN topology to IVR-enabled switches using CFS. Auto mode uses any user-configured IVR VSAN topology as a starting point for the VSAN topology database.
Using auto mode, you no longer need to manually update the IVR VSAN topology when reconfigurations occur in your fabric.
Note
Note
IVR Zoning QoS
IVR zoning QoS can be configured separate from other zone attributes.
Service Groups
Cisco MDS SAN-OS Release 2.1(1a) introduces service groups as a way to limit the control traffic associated with distributing the IVR VSAN topology learned in auto mode. A services group lists fabric IDs and VSANs associated with that fabric ID. When the IVR configuration is distributed, CFS uses the service group to limit the number of switches to which it sends the new IVR VSAN topology database.
Note
Autonomous Fabric ID
The autonomous fabric ID distinguishes segmented VSANS (that is, two VSANs that are logically and physically separate but have the same VSAN number). Cisco MDS SAN-OS Release 2.1(1a) introduces support for fabric IDs from 1 through 64. Fabric IDs are used in conjunction with auto mode to allow segmented VSANS in the IVR VSAN topology database. You can configure up to 64 fabric IDs.
The autonomous fabric ID can be configured individually for each switch and list of VSANs, or the default autonomous fabric ID can be configured for each switch.
Note
Inter-VSAN Zones (IVZ)
As of Cisco MDS SAN-OS Release 2.1(1a), you can configure up to 2000 IVZs and 10,000 IVZ members on the switches in the network.
Multiple Filter Commands
Cisco MDS SAN-OS Release 2.1(1a) supports using multiple filters in the same show command output. This means you can use a combination of the available filters to format the output of any show command.
Note
Cisco MDS SAN-OS Release 2.1(1a) also supports both filters and redirection in the same command. You can apply the required filters to the output of any command and save the output using the file redirection.
Network-Accelerated Serverless Backup
As of Cisco MDS SAN-OS Release 2.1(1a), the SSMs support Network-Accelerated Serverless Backup (NASB). Data movement in the fabric uses considerable processor cycles, which can cause client applications to slow down noticeably. Offloading data movement operations to a media server allows the client applications to run normally even during a backup operation. Media servers can further offload the data movement operation to NASB devices, which allows the media server to focus on the coordination functions needed to complete the backup.
SANTap
The SANTap feature allows third-party data storage applications, such as long distance replication and continuous backup, to be integrated into the SAN. The protocol-based interface offered by SANTap allows easy and rapid integration of the data storage service application because it delivers a loose coupling between the application and an ASM or SSM, thereby reducing the effort needed to integrate applications with the core services being offered by the ASM or SSM.
VSFN Support on SSM
VSFN can be configured on SSM.
Fabric Manager Enhancements
The Cisco MDS 9000 Family Fabric Manager supports:
•
•
•
•
•
•
•
•
•
Device Manager Enhancements
The Cisco MDS 9000 Family Device Manager supports autonomous fabric ID.
Limitations and Restrictions
This section lists the limitations and restrictions for this release.
iSNS
The Internet storage name services (iSNS) server functionality supports only IP network topologies where all IP Storage Services (IPS) modules in the SAN are connected to the same IP network. The iSNS server assumes that if an iSNS client can reach one IPS port, it can also reach every other IPS port in the SAN.
iSCSI
iSCSI pass-thru forwarding mode requires Microsoft iSCSI driver version 2.0 and Cisco iSCSI driver version 4.2.1. There are no restrictions for iSCSI store-and-forward forwarding mode.
Caveats
This section lists the open and resolved caveats for this release. Use Table 3 to determine the status of a particular caveat. In the table, "O" indicates an open caveat and "R" indicates a resolved caveat.
Resolved Caveats
•
A document that describes how the Internet Control Message Protocol (ICMP) could be used to perform a number of Denial of Service (DoS) attacks against the Transmission Control Protocol (TCP) has been made publicly available. This document has been published through the Internet Engineering Task Force (IETF) Internet Draft process, and is entitled "ICMP Attacks Against TCP" (draft-gont-tcpm-icmp-attacks-03.txt). These attacks, which only affect sessions terminating or originating on a device itself, can be of three types:
–
–
–
Multiple Cisco products are affected by the attacks described in this Internet draft. Cisco has made free software available to address these vulnerabilities. In some cases there are workarounds available to mitigate the effects of the vulnerability. This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20050412-icmp.shtml
The disclosure of these vulnerabilities is being coordinated by the National Infrastructure Security Coordination Centre (NISCC), based in the United Kingdom. NISCC is working with multiple vendors whose products are potentially affected. Its posting can be found at: http://www.niscc.gov.uk/niscc/docs/re-20050412-00303.pdf?lang=en
•
Symptom: The iSCSI/IPsec session may go down and come back up after a few hours if using Microsoft's implementation of IPsec in the iSCSI initiator software.
Workaround: None.
•
Symptom: Duplicate fabrics are opened under different SANs when the loadFromDB option is selected.
Workaround: Select Admin > Fabrics to remove the fabric, and then reopen it with the loadFromDB box deselected.
•
Symptom: When a default zoning policy is permitted and there is no active zone set, packets may drop on Fx ports if there are a lot of Fx and Nx ports going up and down.
Workaround: Configure and activate a zone set.
•
Symptom: Disabling QoS does not remove the QoS attribute from an IVR zone set, and subsequent activation of the IVR zone set does not succeed.
Workaround: Remove the QoS attribute from the IVR zone set, both active and configured, before disabling QoS.
•
Symptom: If the standby supervisor and the line cards are reloaded simultaneously, the line cards do not come online and reach the OK state.
Workaround: Perform a reload at the switch level to recover from this problem.
•
Symptom: An active IVR zone set on the local switch is not propagated when the commit session contains any other configuration changes.
Workaround: For Cisco SAN-OS Release 2.1(2) and later, perform an implicit commit without any changes. In the case of a merge failure and the IVR zone set is not active on remote switches but is active on a local switch, issue an implicit commit from the local switch to propagate the active zone set to the remote switches.
For releases prior to Release 2.1(2), the workaround is different. Add either a dummy member to an existing zone or add a dummy zone with dummy members to the currently active IVR zone set, and then reactivate the IVR zone set. Then issue the commit command, which will propagate the active zone set to the other switches.
•
Symptom: Some hosts may not accept IKE tunnel creation from a Cisco MDS 9000 Family switch when an IKE session already exists in the switch. When this occurs, it may take more than the expected time for the IPsec session to come up. This scenario can happen when the Gigabit Ethernet interface on the switch fails and comes back up, or if you issue a VRRP switchover to a different switch.
Workaround: For a faster recovery, disconnect and reinitiate the iSCSI session from the host.
In Cisco SAN-OS Release 3.0(1), you can avoid this problem by configuring a TCP port number (in addition to an IP address mask) in the IP access list used by the IPsec crypto map.
•
Symptom: If an IPS module with operational FCIP PortChannels is reloaded, upgraded, or downgraded, the supervisor module may be reloaded causing the system to reboot.
Workaround: Before reloading, upgrading, or downgrading an IPS module, shut down all FCIP PortChannels on the line card.
•
Symptom: WWNs assigned to iSCSI initiators by the system can inadvertently be returned to the system when an upgrade fails or a manual downgrade is performed, such as when an older iSAN software version is booted up without using the install all command. In these scenarios, the system can later assign those WWNs again to other initiators, which causes conflicts. CSCei17870 is a duplicate of this caveat.
Workaround: None.
•
Symptom: If one of the following two events were to occur on a TL port, the TL port would in effect be not functional.
–
–
Workaround: Issue a shut noshut command on the TL port to fix the problem.
•
Symptom: Under certain traffic patterns, the Gigabit Ethernet port can flap when auto compression mode is selected. This problem can also occur rarely even when compression mode 1 is selected.
Workaround: Use mode 2 or mode 3 compression mode if the maximum throughput required is less than 25 Mega bits/sec. There is no workaround if the throughput requirement is > 25 Mbps.
•
Symptom: If an MDS switch has more than one module that supports Ethernet ports, the Cisco Discovery Protocol (CDP) learns entries over both the Gigabit Ethernet ports and the mgmt0 port. Subsequently, if there is either a system switchover or a restart of the CDP process, CDP will lose neighbors learned over the Gigabit Ethernet ports. A side effect of this behavior is that the sh cdp neighbors interface <gig intf> command causes the CDP process to crash and results in either a switchover on a dual supervisor or a reload on a single supervisor. This problem does not occur as long as the MDS switch is populated with just one module that supports Ethernet ports. Any combination of two or more modules supporting Ethernet ports will cause the problem. In addition, in the case of the Cisco MDS 9216i a module that supports Ethernet ports along with the supervisor module in slot1 is susceptible to the problem.
Workaround: None. Disable CDP so it does not learn of any entries, thereby preventing a crash or switchover.
•
Symptom: The IPS port erroneously reports a check-condition SCSI response to the iSCSI host for a proprietary SCSI command 0xEF when the actual amount of data transfer does not match the transfer size requested in the SCSI command.
Workaround: None.
•
Symptom: In an arbitrated loop configuration, the loop reinitialization without bringing down the link may result in I/O failure (including FLOGI) from the loop devices connected to that port. This problem was observed with Uniwide/Xiotech storage systems configured in Active/Standby mode, where a set of devices were moved from an active arbitrated loop to standby arbitrated loop. The movement of devices was triggered by a hardware failure in the Uniwide storage system.
Workaround: Issue the shutdown/no shutdown command sequence to clear the problem.
•
Symptom: The application might report that the loop port is not up, however, the port is online and operational.
Workaround: Issue the shutdown/no shutdown command sequence to clear the problem.
•
Symptom: On rare occasions, the install license command may fail due to the saved state of the switch configuration. This may occur after saving a remote configuration to the switch using the copy remote-url start-up command.
Workaround: Issue the copy ru st command. The install license command should work properly after that.
•
Symptom: After a successful database merge, the show cfs merge status name application_name command output may not reflect the correct merge status. However, the merge operation remains successful.
Workaround: None. The correct status is displayed when you perform additional CFS operations.
•
Symptom: Your connection to the server might terminate during an upgrade/downgrade process if the client is detecting the server's status upon receiving events. If the client does not receive any events from the server for a certain amount of time, it assumes that the server is down and closes the connection. Fabric Manager timeouts have also been seen that do not coincide with upgrade/downgrade events.
Workaround: Remove the fabric and then reopen it.
•
Symptom: If you delete a fabric and then enable the LoadFromDB option while the fabric rediscovers it, there might be a delay in seeing the fabric in the Fabric Manager client.
Workaround: Do not enable the LoadFromDB option in the Fabric Open dialog box when rediscovering the fabric again.
•
Symptom: The Fabric Manager end-to-end connectivity tab does not display properly. The screen turns gray and a java.lang.nullPointerException can be found in the log.
Workaround: Close the dialog box and relaunch it.
•
Symptom: On Device Manager, select the port by right-clicking the port, selecting monitor, and choosing any category such as traffic, protocol, or link errors. The counters displayed for some of the fields such as "Rx Bytes" in traffic category, "Toolongs" in Frame error category etc. are not accurate. Some of the individual counters are not presented correctly. The problem is seen intermittently.
Workaround: The statistics shown by the show interface command reflects the correct value.
•
Symptom: Configuring the CIM server with an invalid certificate will crash the CIM Server.
1.
Guest
