Table Of Contents
Cisco MDS 9000 Family Release Notes
for Cisco MDS SAN-OS Release 2.1(2d)Determining the Software Version
Upgrading Your Cisco MDS SAN-OS Software Image
Performing a Disruptive Upgrade on a Single Supervisor MDS Family Switch
New Features in Cisco MDS SAN-OS Release 2.1(2d)
Regulatory Compliance and Safety Information
Installation and Configuration Note
Cisco Product Security Overview
Reporting Security Problems in Cisco Products
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 2.1(2d)
Release Date: December 19, 2005
Text Part Number: OL-7411-05 Q0
This document describes the caveats and limitations for switches in the Cisco MDS 9000 Family. Use this document in conjunction with documents listed in the "Related Documentation" section.
Note
Release notes are sometimes updated with new information on restrictions and caveats. Refer to the following website for the most recent version of the Cisco MDS 9000 Family Release Notes: http://www.cisco.com/en/US/products/hw/ps4159/ps4358/prod_release_notes_list.html
Table 1 shows the on-line change history for this document.
Table 1 Online History Table
A0
12/19/2005
Release note created
B0
12/23/2005
Added software part numbers and upgrade information
C0
12/30/2005
Added DDTS CSCei91968
D0
02/17/2006
Added DDTSs CSCsb90192, Workaround: None., CSCsc23435, CSCsc24966, CSCsc31424, CSCsc57865, CSCsc68084, CSCsc98796, CSCsc97070, CSCsd02008, and CSCsd21093
Added limitation for iSCSI proxy initiators
E0
05/31/2006
Added CSCeg33121, CSCsd29338, CSCeg12962, CSCeg84871, CSCeh04183, CSCeh30951, CSCeh70232, CSCei02126, CSCei10774, CSCei36082, CSCei55208, CSCei79457, CSCsc75056, CSCsc95884, CSCsd47064, CSCsd79954, CSCeg53114, CSCei57342, CSCei58652, CSCei71686, CSCei86399, CSCei91676, CSCej08751, CSCsb89732, CSCsc09732, CSCsc20106, CSCsc33788, CSCsc40012, CSCsc48919, CSCsc60283, CSCsc93936, CSCsd07246, CSCsd12831, CSCsd22920, CSCsd25790, CSCsd30165, CSCsd34882, CSCsd53429, CSCsd58774, CSCsd60578, CSCsd70927, CSCsd71701, CSCsd72822, CSCsd73494, CSCsd76429, CSCsd81725, CSCsd82449, and CSCsd94718
F0
06/06/2006
Removed DDTS CSCed16845
G0
07/10/2006
Corrected the CWDM part numbers in Table 2.
Removed CSCeg33121, CSCeg12962, CSCeg84871, CSCeg90336, CSCeh04183, CSCeh30951, CSCeh52973, CSCeh70232, CSCeh93109, CSCei10774, CSCei36082, CSCei55208, CSCei55341, CSCec31365, CSCeg12383, CSCeg53114, CSCeg55238, CSCeh34828, CSCei48889, CSCei83322, CSCei91676, CSCej08751, CSCin92870, CSCin95789, CSCsd71701.
H0
08/7/2006
Added DDTS CSCse84811
I0
08/18/2006
Added DDTS CSCse89151
J0
08/22/2006
Added DDTS CSCse65400.
K0
09/5/2006
Added DDTS CSCsd78967 and CSCse88606.
L0
09/13/2006
Added DDTS CSCsf21970
M0
11/13/2006
Added DDTS CSCin95789, CSCsd81137, CSCse22145, CSCse70275, CSCse71420, CSCsf96043, CSCsg12020, and CSCsg15392.
N0
02/23/2007
Added DDTS CSCse99087, CSCsg03171, CSCsg62359, and CSCsh27840.
O0
03/26/2007
Added DDTS CSCsd41578.
P0
04/04/2007
Added the section "Performing a Disruptive Upgrade on a Single Supervisor MDS Family Switch".
Q0
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 provide industry-leading availability, scalability, security, and management, allowing you to deploy high performance storage-area networks with lowest total cost of ownership. Layering a rich set of intelligent features onto a high performance, protocol agnostic switch fabric, the Cisco MDS 9000 Family addresses the stringent requirements of large data center storage environments: uncompromising high availability, security, scalability, ease of management, and seamless integration of new technologies.
The Cisco MDS 9000 Family SAN-OS is the underlying system software that powers the Cisco MDS 9500 series, 9200 series, and 9100 series multilayer switches. The Cisco SAN-OS provides intelligent networking features such as multiprotocol and multitransport integration, virtual SANs (VSANs), advanced security, sophisticated debug analysis tools, and unified SAN management.
System Requirements
This section describes the system requirements for Cisco MDS SAN-OS Release 2.1(2d) 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.2D
MDS 9500 Supervisor/Fabric-I, SAN-OS software.
MDS 9500 Series only
M92S1K9-2.1.2D
MDS 9216 Supervisor/Fabric-I, SAN-OS software.
MDS 9200 Series only
M91S1K9-2.1.2D
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-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
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.
DS-SFP-GE-T
1-Gbps Ethernet SFP
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 multiplexer(s).
Power supplies
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.
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, 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
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
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.
Upgrading Your Cisco MDS SAN-OS Software Image
The Cisco MDS SAN-OS software is designed for mission-critical high availability environments. To realize the benefits of nondisruptive upgrades on the Cisco MDS 9500 Directors, we highly recommend that you install dual supervisor modules.
You can nondisruptively upgrade to Cisco MDS SAN-OS Release 2.1(2d) from any SAN-OS software release beginning with Release 1.3(x). If you are running an older version of the SAN-OS, first upgrade to Release 1.3(x), and then upgrade to Release 2.1(2d).
When downgrading from Cisco MDS SAN-OS Release 2.1(2d) to Release 1.3(x), you might need to disable new features in Release 2.1(2d) 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 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.
If you are upgrading from Cisco MDS SAN-OS Release 2.1(1x) to any image later than Release 2.1(2) and have IVR enabled, review CSCei88345 in the Cisco MDS 9000 Family Release notes for Cisco MDS SAN-OS Release 2.1(2b) for upgrade instructions.
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(2d)
There are no new features available for this release.
Limitations and Restrictions
This section lists the limitations and restrictions for this release.
VSFN Compatibility
For the latest VSFN compatibility information, refer to the Cisco MDS SAN-OS Release Compatibility Matrix for VERITAS Storage Foundation for Networks Software.
iSCSI Proxy Initiators
No more than 250 iSCSI proxy initiator sessions can be active on an IPS port.
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
•
Symptom: When making zone changes, even in basic mode, the zone server might complain that other sessions are active. Issuing a force commit or uncommit command fails because the command is not supported in this mode. This occurs when the zone mode changes are applied to multiple VSANs at the same time.
Workaround: If a VSAN is stuck in this state, the only option is to disruptively suspend and not suspend the VSAN. When making mode changes, make the changes one VSAN at a time. Issue the show zone status vsan X command to verify the mode status of VSAN x before proceeding with the next VSAN. Another possible workaround is to look for another VSAN that has an open session and then end that session with the no zone commit vsan xxx command. Use the command show zone internal vsan xxx to check for an open session. You should then be able to issue a no zone commit vsan yyy to close the session opened for the original VSAN you were working with.
•
Symptom: CFS distribution may become inconsistent when a link flaps. One switch in the CFS distribution list may detect that a CFS peer has dropped from the fabric while the other CFS peers do not detect this. Subsequent CFS distributions result in incorrect updates to CFS peers.
Workaround: Use a switch where all other switches are reachable through CFS for IVR applications and follow these steps:
a.
b.
Note
c.
d.
After Step d, all the IVR enabled switches should have active user-configured topology with the same entries.
Using the switch where the problem exists with the auto topology output, follow these remaining steps:
e.
f.
g.
•
Symptom: When a switchover occurs, CFS distributions initiated from other switches in the fabric might timeout and go into retry mode. This might result in the application distributions failure and consequent loss of application dependent functionality.
Workaround: There is no workaround at the CFS level, however, applications like IVR may retry and recover.
•
Symptoms: FC ID rewrite entries may not be programmed on interfaces that are part of a PortChannel and the module containing those interfaces that are down (powered down or removed).
This typically happens if the PortChannel is up and the module containing some of its members is down. For example, if IVR devices are communicating over a port channel. Power down a module containing a PortChannel member. Reboot the switch (without issuing the copy running-configuration startup-configuration command. After the reboot, the devices may not be able to communicate because FC ID rewrite entries are not programmed.
Workaround: Issue the copy running-configuration startup-configuration command before you reboot when a module is powered down. Or, issue the purge module slot running-config command to purge any data related to the module that is powered down.
Note
•
Symptom: When multiple IVR-enabled switches are exporting a virtual domain into a VSAN, a duplicate LSR for the same virtual domain may be generated. As a result, the route to the virtual domain flaps periodically because of the contents of the two LSRs.
This condition is more likely to happen when there is a larger number of switches exporting the same virtual domain into a VSAN.Before a steady state can be met, you must terminate the virtual domain exportation. This issue is seen only when the NAT mode is enabled.
Workaround: Issue the show fspf database command a few times and observe the outputs to identify the domain where the route is flapping.
•
Symptom: In Cisco SAN-OS Release 2.1(2b), the power supplies on some Cisco MDS 9120 and Cisco MDS 9140 switches are flagged as unsupported. This generates a syslog message, a Call Home message, and a SNMP trap. Only certain power supplies with newer SEEPROM formats will trigger this problem.
Workaround: None. The power supplies continue to function normally and the unsupported message can be ignored. Or, upgrade to Cisco SAN-OS Release 2.1(2d).
•
Symptom: A module might be taken offline mistakenly by a module reset, a module in a powered-down state, or a module in an unknown state. This is caused by a timing relationship issue between the supervisor and modules in the on-line health-check error handling mechanism. This occurs the following exist:
a.
b.
Workaround: If the module is offline, remove and reinsert the module. Or, upgrade to Cisco MDS SAN-OS Release 2.1(2d).
Open Caveats
•
Symptom: The port manager might crash and a switchover might occur when FICON is configured and the MDS switch is interoperating with a CNT device. This occurs when a port is UP, a link failure happens, and the remote node ID (RNID) retry timer is activated.
Workaround: None
•
Symptom: The VSAN suspend/resume operation facilitates network level reconfiguration and is not often used. In Cisco MDS SAN-OS Release 2.1(2), the command should not be used on a SANTap related VSAN.
Workaround: If VSAN suspend/resume must be used, first unprovision SANTap prior to using VSAN suspend/resume.
•
Symptom: Enabling IVR-NAT on the same switch where write acceleration is enabled over a PortChannel of multiple FCIP links might result in frames from the source to the destination not transferring.
Workaround: Do not have all of the following on the same switch:
–
–
–
However, any two of the above three configurations are supported on the same switch.
Note
•
Symptom: If snmpTargetAddrName and snmpTargetParamsName are set to NULL in the SNMP host/target creation, then the SNMP process crashes and may cause a switchover to the standby supervisor module.
Workaround: When using third party tools or any other SNMP tool, set snmpTargetAddrName and snmpTargetParamsName to non-NULL values.
•
Symptom: Removing zones from an active zone set may generate a system message that the zone activation has failed because of an Accept Change Authorization (ACA) failure.
Workaround: None required. The IVR retries the activation and eventually the zone set activation succeeds.
•
Symptom: An active IVR zone set on the local switch is not propagated when the commit session contains any other configuration changes.
Workaround: For Release 2.1(2), 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 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 other switches.
•
Symptom: An iSCSI host cannot log in to one IPS port after many supervisor module switchovers.
Workaround: None.
•
Symptom: The following syslog message is displayed:
Transmit Flow Control is seen for too longfollowed by link flap of the affected port. This applies only in E port mode and TE port mode of operation on Storage Services Modules (SSM) (DS-X9032-SSM) interfaces and occurs only when class-F packets are dropped due to a timeout condition. Typically, the packet timeout happens when there is serious congestion in the network, forcing the packets to stay in the switch for more than the timeout period.
Workaround: Avoid configuring in E port mode or TE port mode on the Fibre Channel interfaces.
•
Symptom: Installing an invalid license file may cause an MDS switch to reload.
Workaround: Recover the switch from the console port. Then request another license file from Cisco. Install the unaltered license file.
Note
•
Symptom: The install all command may fail on an SSM when you downgrade from Cisco SAN-OS Release 3.0(1) to any SAN-OS 2.x release earlier than SAN-OS Release 2.1(2d) on a system with at least one SSM.
Workaround: Power down the SSM before you downgrade the SAN-OS software. After the downgrade, power up the SSM with the new boot variable set to the appropriate Release 2.x SSI image.
•
Symptom: When a port continuously flaps, the Fibre Channel process may crash and cause a supervisor switchover.
Workaround: Use a different port or check the host bus adapter (HBA) port.
•
Symptom: The Forwarding Information Base (FIB) process may fail if an IVR zone set push from the Fabric Manager fails because of an SNMP timeout and various switches send conflicting active IVR zone sets.
Workaround: There are two ways to address the problem:
•
•
•
Symptom: If a VSAN that is connected to a McDATA switch with Interop mode 1 participates in IVR, and the VSAN has devices that are zoned for IVR with a device in a VSAN with domain IDs not within the range 97 to 127, then there may be a loss of connectivity between the hosts and storage devices that are zoned for IVR and the devices in a normal zone.
Workaround: Enable IVR NAT, which may be nondisruptive, or change the domain IDs of all the VSANs that need to participate with the VSAN in Interop mode 1 to the range 97 to 127.
•
Symptom: If you remove a port from a port channel or shutdown a member port of a port-channel, the ConnUnitPortStatus/State trap is not sent.
Workaround: None.
•
Symptom: If a module reloads or reinitializes on its own because of an error, and the port channel has one of its member ports on this module, in rare cases, the peer port of this member port will not forward traffic after the module comes back up.
Workaround: Issue the shutdown/no shutdown command sequence on the port channel. If the problem still persists, issue the shutdown/no shutdown command sequence on the affected ports.
•
Symptom: If you have more than 800 zones in an active zoneset for a single VSAN, your MDS 9000 switch might reload if you move from basic zoning to enhanced zoning and then read the active zoneset information.
Workaround: Lower the number of zones in an active zoneset for a single VSAN to less than 800.
•
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: If an iSCSI initiator is configured differently on multiple switches, iSNS might report more targets to the initiator than the initiator can access. An iSCSI initiator would get a target error if it attempts to establish a connection.
Workaround: None.
•
Symptom: Creating a role that has VSAN policy as "deny" requires an Enterprise License on the switch. If such a role is created on a switch that does not have the license, the switch exhibits different behavior when distribution is turned on versus when distribution is turned off.
–
–
Workaround: None.
•
Symptom: The iSNS server might crash when iSCSI is disabled and iSNS is enabled using Fabric Manager.
Workaround: None.
•
Symptom: Tape devices can only be accessed over an FCIP tunnel in a PortChannel with write acceleration enabled if SID/DID based load-balancing is used in the VSANs.
Workaround: Disable write acceleration or enable SID/DID based load-balancing in the VSANs if you have tape device traffic going over an FCIP tunnel in a PortChannel.
•
Symptom: Protocol and port numbers, if specified in an IP ACL assigned to an IPsec profile (crypto map), will be ignored. In an interop between Microsoft's iSCSI initiator with IPsec encryption with Cisco MDS 9000 Series switches, if IPsec is configured in the Microsoft iSCSI initiator (also the IPsec/IKE initiator), the host IPsec implementation sends the following IPsec policy:
source IP - Host IP, dest IP - MDS IP,source port - any, dest port - 3260 (iSCSI), protocol - 6 (TCP).Upon receiving this policy, the protocol and port numbers are ignored and only the IP addresses for the IPSec policy are used. Thus, although iSCSI traffic is encrypted, non-iSCSI traffic (such as ICMP ping) sent by the Microsoft host in clear text will be dropped in the MDS port.
Workaround: None.
•
Symptom: SNMP service might stop and restart because of a corrupted snmpTargetParamsEntry in the snmpTargetParamsTable. This corrupted entry is created when there is a null string in object snmpTargetParamsName as its index.
Workaround: Enter a name in the snmpTargetParamsName with at least one character when creating an snmpTargetParamsEntry.
•
Symptom: A device that interfaces with SANTap may request SANTap to create a session for an ITL that was previously requested, and ITL checking is not robust.
Workaround: Have the device validate the ITL and ensure that it does not send a request for a duplicate ITL.
•
Symptom: When SANTap is unprovisioned, the control virtual target (CVT) object is not getting cleaned up on the supervisor module.
Workaround: To ensure that cleanup occurs, the administrator should first issue the no santap module slot-number appl-vsan vsan-id command to clean up the CVT, and then unprovision SANTap.
•
Symptom: When configuring a remote SPAN (RSPAN), the Fibre Channel tunnel will not come up if it goes through more than one hop.
Workaround: Configure the Fibre Channel tunnel explicit-path option and list every IP hop between the source and destination.
•
Symptom: If a link is isolated because of a fabric-binding database mismatch, a reactivation of the corrected fabric-binding database may not initialize the ports.
Workaround: Use the shut command followed by the no shut command to manually disable then enable the link.
•
Symptom: When a reconfigure fabric (RCF) frames occurs on a VSAN, the ports may be left in a state where the fabric binding is incorrect.
Workaround: None.
•
Symptom: If iSCSI is enabled before FCIP, then the qos command that is configurable under a FCIP interface is not available as an option. The reverse is true as well. If FCIP is enabled first, then the qos command is not an option for iSCSI interfaces.
Workaround: None.
•
Symptom: A TACACS+ key that includes the less than (<) and greater than (>) characters fails when copied to an ftp server, and then copied back to the MDS switch.
Workaround: None.
•
Symptom: In a fabric with more than one switch, CFS or syslog can crash because of a PSS-FULL condition. This happens because of memory leakage in the persistent storage service (PSS) records stored by the CFS module.
CFS internal distributions cause a PSS leakage during one of the following events:
–
–
In a stable fabric, application and regular CFS distributions do not result in PSS memory leakages.
Workaround: None. A switchover will help in cleaning up these records but the usage of the partition remains the same (dev/shm partition). However, CFS will reuse the freed space for further PSS storage.
•
Symptom: The RRD graph in the Performance Manager does not refresh on a web client opened in Mozilla or Netscape.
Workaround: Do not use a proxy server or use the browser's Refresh button.
•
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: After an upgrade from SAN-OS Release 1.3(2a) to any release lower than SAN-OS Release 3.0(1), you may see errors like the following in the syslog file:
2005 Sep 15 17:36:55 coral %SYSMGR-3-CFGWRITE_SRVFAILED: Service "fcc" failed to store its configuration (error-id 0xFFFFFFFF).2005 Sep 15 17:36:56 coral %SYSMGR-2-CFGWRITE_ABORTED: Configuration copy aborted.2005 Sep 15 17:36:59 coral %SYSMGR-3-CFGWRITE_FAILED: Configuration copy failed (error-id 0x401E0000).2005 Sep 15 17:37:43 coral %SYSMGR-3-CFGWRITE_SRVFAILED: Service "fcc" failed to store its configuration (error-id 0xFFFFFFFF).2005 Sep 15 17:37:44 coral %SYSMGR-2-CFGWRITE_ABORTED: Configuration copy aborted.2005 Sep 15 17:37:47 coral %SYSMGR-3-CFGWRITE_FAILED: Configuration copy failed (error-id 0x401E0000).2005 Sep 15 17:38:31 coral %SYSMGR-3-CFGWRITE_SRVFAILED: Service "fcc" failed to store its configuration (error-id 0xFFFFFFFF).2005 Sep 15 17:38:32 coral %SYSMGR-2-CFGWRITE_ABORTED: Configuration copy aborted.2005 Sep 15 17:38:35 coral %SYSMGR-3-CFGWRITE_FAILED: Configuration copy failed (error-id 0x401E0000).Workaround: After the upgrade, issue the copy running-config startup-config command before issuing the show startup-config command.
If you have already encountered this issue, perform a stateful switchover, then issue the copy running-config startup-config command.
•
Symptom: The CFS process crashes while processing a discovery response containing null data.
Workaround: None.
•
Symptom: If there is a port software failure at the same time as a configuration change for an FCIP interface, the configuration change can fail and subsequent configuration and show commands will fail for that FCIP interface.
Workaround: None.
•
Symptom: On a Cisco MDS 9020 Fabric Switch, Fabric Manager displays a 4-Gbps Inter-Switch Link (ISL) as a 3-Gbps ISL.
Workaround: None.
•
Symptom: System logs an error due to a xbar-ASIC interface device 6 (overflow). The error results in packet loss and, potentially, the card going into a failure state.
The down-xbar interface ASIC (D-chip) has a mapping of hardware queues to software destination indexes (DIs).This table is initialized by hardware to map all queues to DI 0. The D-chip statically allocates packet buffers for each hardware queue during initialization. These buffers correspond to credits given to the central arbiter for the corresponding DI.
On line cards with FCIP interfaces, the binding of DIs is performed dynamically after initialization. This means that any hardware queues that have not yet been bound to a DI will actually be giving credits to the arbiter for DI 0.
In rare cases, the D-chip may fill up with packets causing an overflow condition and cause packets to be dropped and an error is be logged. If the condition persists for 1 second, the card goes into failure state.
The following hardware components are affected by this error:
•
•
•
•
Workaround: None.
•
Symptom: The following commands can sometimes hang the terminal during execution:
•
•
Workaround: If you are connected through an SSH or Telnet session, shut down the session and restart a new one.
•
Symptom: Upgrading from a Cisco SAN-OS Release 1.3(x) image to a Release 2.x image can disrupt ongoing traffic because spurious RSCNs are generated during the upgrade. Hosts that have registered for the RSCN, using SCR, will receive these spurious RSCNs and hence the disruption. However, upgrading from Release 2.0(x) to Release 2.1(x) will not disrupt any traffic.
Workaround: Suppress the RSCNs on a per interface basis during the upgrade using the rscn suppress interface fc slot/port hidden command.
Note
Note
Follow these steps:
1.
2.
3.
4.
5.
6.
7.
8.
•
Symptom: Issuing a no shutdown command on an interface causes the following message to display:
fc1/1: (error) port channel config in progress - config not allowedThe following steps may reproduce the problem:
1.
switch# config tswitch(config)# interface fc slot/portswitch(config-if)# no channel-group group-number2.
switch(config-if)# endswitch# system switchover
Note
Workaround:
1.
switch# config tswitch(config)# interface fc slot/portswitch(config-if)# channel-group group-numberWhere the PortChannel group-number does not exist.
2.
switch(config-if)# exitswitch(config)# no interface port-channel group-number3.
switch(config)# interface fc slot/portswitch(config-if)# no shutdown
Guest
