 Feedback
|
Table Of Contents
Cisco MDS 9000 Family Release Notes
for Cisco MDS SAN-OS Release 2.1(2)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(2)
Nondisruptive Storage Services Module (SSM) Image Upgrade
Default Initial State for SSMs
Persistent FC IDs and Domains for IVR
SCSI Flow Services Support for Interfaces
Special Characters in TACACS+ Global Secret Keys
Control for SNMP Notifications for linkUp/linkDown Traps
NASB Storage Array Controller Support
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(2)
Release Date: July 26, 2005
Text Part Number: OL-7411-03 R0
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
7/25/2005
Created release notes
B0
08/05/2005
Added DDTS CSCeh41099
C0
08/08/2005
Changed the state of DDTS CSCin95832
D0
08/11/2005
Added DDTS CSCeh70232
E0
08/22/2005
Removed DDTS CSCeh61610
F0
08/23/2005
Added DDTS CSCeh61610
G0
11/03/2005
Added DDTS CSCeh69186
H0
12/07/2005
Added DDTS CSCsc31424
I0
12/30/2005
Added DDTS CSCei91968
I1
02/22/2006
Added DDTS CSCsc23435 and CSCsc57865
J0
05/26/2006
Added DDTS CSCeg33121, CSCeg53114, CSCeg82721, CSCeh30951, CSCeh52973, CSCeh65824, CSCei36082, CSCei55208, CSCei79457, CSCei57342, CSCei58652, CSCei67982, CSCei71686, CSCei86399, CSCei91676, CSCsb89732, CSCsc09732, CSCsc23435, CSCsc28722, CSCsc33788, CSCsc48919, CSCsc57865, CSCsc93936, CSCsc97070, CSCsd07246, CSCsd29338, CSCsd30165, CSCsd71701, CSCsd72822, CSCsd76429, CSCsd89872, and CSCsd94718
K0
06/06/2006
Removed DDTS CSCed16845
L0
08/07/2006
Removed DDTS CSCeg33121, CSCeg84871, CSCeh30951, CSCei10774, CSCei55341
Added DDTS CSCse84811,
Revised DDTS CSCsd89872 description
Revised status for DDTS CSCei10774, CSCeg90336, CSCeh93109
M0
09/05/2006
Added DDTS CSCsd78967
N0
09/13/2006
Added DDTS CSCsf21970
O0
11/07/2006
Added DDTS CSCse70275, and CSCsg15392
P0
02/23/2007
Added DDTS CSCse99087, CSCsg03171, and CSCsh27840.
Q0
04/04/2007
Added the section "Performing a Disruptive Upgrade on a Single Supervisor MDS Family Switch".
R0
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(2) and includes the following topics:
•
Components Supported
Table 2 lists the software and hardware components supported by the Cisco MDS 9000 Family.
Note
Table 2 Cisco MDS 9000 Family Supported Software and Hardware Components
Software
M95S1K9-2.1.2
MDS 9500 Supervisor/Fabric-I, SAN-OS software.
MDS 9500 Series only
M92S1K9-2.1.2
MDS 9216 Supervisor/Fabric-I, SAN-OS software.
MDS 9200 Series only
M91S1K9-2.1.2
MDS 9100 Supervisor/Fabric-I, SAN-OS software.
MDS 9100 Series only
License
M9500ENT1K9
Enterprise package.
MDS 9500 Series
M9200ENT1K9
Enterprise package.
MDS 9200 Series
M9100ENT1K9
Enterprise package.
MDS 9100 Series
M9500FIC1K9
Mainframe package.
MDS 9500 Series
M9200FIC1K9
Mainframe package.
MDS 9200 Series
M9100FIC1K9
Mainframe package.
MDS 9100 Series
M9500FMS1K9
Fabric Manager Server package.
MDS 9500 Series
M9200FMS1K9
Fabric Manager Server package.
MDS 9200 Series
M9100FMS1K9
Fabric Manager Server package.
MDS 9100 Series
M9500EXT1K9
SAN Extension over IP package for IPS-8 module.
MDS 9500 Series
M9200EXT1K9
SAN Extension over IP package for IPS-8 module.
MDS 9200 Series
M9500EXT14K9
SAN Extension over IP package for IPS-4 module.
MDS 9500 Series
M9200EXT14K9
SAN Extension over IP package for IPS-4 module.
MDS 9200 Series
M9500EXT12K9
SAN Extension over IP package for MPS 14+2 module.
MDS 9500 Series
M9200EXT12K9
SAN Extension over IP package for MPS 14+2 module.
MDS 9200 Series
M9500SSE1K9
Storage Services Enabler package.
MDS 9500 Series with ASM or SSM
M9200SSE1K9
Storage Services Enabler package.
MDS 9200 Series with ASM or SSM
Chassis
DS-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
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.
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(2) 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(2).
When downgrading from Cisco MDS SAN-OS Release 2.1(2) to Release 1.3(x), you might need to disable new features in Release 2.1(2) 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(2)
This section describes the new features introduced in this release. For more information about the features listed, refer to the Cisco MDS 9000 Family Configuration Guide and the Cisco MDS 9000 Family Fabric Manager Configuration Guide.
Note
Nondisruptive Storage Services Module (SSM) Image Upgrade
You can perform a nondisruptive upgrade of Fibre Channel switching for an SSM using the new install ssi command. The SSM must be running EPLD version 2.1(2) to use the install ssi command. To upgrade the EPLD image, the SSM must be installed on a Cisco MDS 9500 Series switch.
Default Initial State for SSMs
Storage Service Modules (SSMs) initially come up in Fibre Channel switching mode by default.
Persistent FC IDs and Domains for IVR
You can configure persistent FC IDs and domains for IVR. This improves IVR management by allowing you to control and assign a specific virtual domain to use for a native VSAN, and by allowing you to control and assign a specific virtual FC ID to use for a device.
Note
SCSI Flow Services Support for Interfaces
You can configure SCSI flow services on groups of four interfaces, as well as on the entire module.
Special Characters in TACACS+ Global Secret Keys
Two special characters are allowed in TACACS+ global secret keys. You can use the dollar sign ($) and the percent sign (%) in TACACS+ global secret keys.
Control for SNMP Notifications for linkUp/linkDown Traps
In Cisco MDS SAN-OS Release 2.1(2), users can configure which linkUp/linkDown trap notifications to enable for interfaces.
NASB Storage Array Controller Support
You can enable Network-Accelerated Serverless Backup (NASB) as storage array controller devices.
NASB Target Rediscovery
You can enable Network-Accelerated Serverless Backup (NASB) to rediscover a target device.
iSCSI Duplicate WWN Check
You can check for potential WWN conflicts in the current configuration.
Fabric Manager Enhancements
The Cisco MDS 9000 Family Fabric Manager supports:
•
–
–
–
–
–
•
•
•
•
•
•
Limitations and Restrictions
This section lists the limitations and restrictions for this release.
SANTap
The maximum number of targets that SANTap supports is 16.
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.
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.
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: In some rare instances in Cisco MDS SAN-OS Release 1.3, 2.0, and 2.1(1), when the IP Storage Services (IPS) module restarted after a failure, VSAN membership information about iSCSI interfaces was lost. However, a configuration saved with the copy running-config startup command was not lost.
Workaround: None.
•
Symptom: VPN 4.0.1 does not work with large SNMP PDU packets.
Workaround: Upgrade to VPN 4.0.5.
•
Symptom: Duplicate fabrics are opened under different SANs when the loadFromDB option is selected.
Workaround: In Fabric Manager, select Admin > Fabrics to remove the fabric, and then reopen it with the loadFromDB box deselected.
•
Symptom: Some hosts may not accept IKE tunnel creation from Cisco MDS 9000 Family switches when an IKE session already exists in the switch. In such cases 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.
•
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: 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: A user that you create in Fabric Manager or Device Manager cannot log in from the console. Release 2.1(2) fixes this problem. However, if a third-party application creates a user using SNMP, a new MIB is required for Release 3.0.
Workaround: Third-party applications should use SSH to connect to the MDS 9000 switch, and then use CLI commands to create the user account.
•
Symptom: The ICMP Path-MTU discovery might not work with IPsec depending upon the SPD policy that is created and where the ICMP error message is originated.
Workaround: Identify the path MTU and set it as the local interface MTU in the switch.
•
Symptom: iSCSI immediate and unsolicited data is not allowed to be used when the data digest is turned on.
Workaround: None.
•
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: Traffic stops flowing when a member, who is not the first member, of a non-trunking PortChannel in an IVR zone set is flapped.
Workaround: None.
•
Symptom: In Fabric Manager, the switch appears in two VSANs when connected through ISL.
Workaround: None.
•
Symptom: FCIP Write Acceleration does not work with certain storage replication subsystems.
Workaround: None.
•
Symptom: Following an upgrade from Release 1.1 to Release 1.3 or higher, with persistent FC ID enabled, the FC IDs for the storage arrays may get changed after a link flap.
Workaround: None.
•
Symptom: Under certain traffic patterns, the auto compression mode in MPS-14/2 modules can cause a packet buffer leak. This might lead to a drop in FCIP performance. A low free clusters count below 40000 in the output of the show ips stats buffer interface gigabitethernet x/y command indicates that the IPS port may potentially have hit this bug.
Workaround: Reload the MPS-14/2 module. Or use compression mode2 or mode3 to avoid the problem
•
Symptom: When many iSCSI sessions go up or down simultaneously, such as when a line card fails, the amount of syslog messages generated can overwhelm the supervisor and cause a new iSCSI session login to be delayed.
Workaround: None.
•
Symptom: If two IPS ports on an IPS module are configured in the same IP subnet, but put on different LAN segments, external iSNS clients may not be able to connect to the iSNS server on the IPS port.
Workaround: Put the IPS ports in the same IP subnet on the same LAN segment.
•
Symptom: During an upgrade of the firmware on an IBM tape drive, the tape utility program may hang after it resets and performs loop initialization. The tape drive sends OPN, FLOGI, and CLS. The switch sends OPN and ACC, but does not send CLS, which causes the tape utility to hang while it waits for CLS.
Workaround: After the firmware is correctly upgraded on the tape drive, follow these steps:
–
–
•
Symptom: A newly configured FCIP link may fail to come up when running on an MPS-14/2 module. This symptom may occur following an upgrade of Cisco MDS SAN-OS Release 2.0(1b) to Release 2.0(3) and the configuration of a new FCIP link.
In the log on the switch, you may see the following messages:
%PORT-5-IF_DOWN_ELP_FAILURE_ISOLATION: %$VSAN xyz%$ Interface fcipabc is down (Isolation due to ELP failure)
%PORT-5-IF_DOWN_OFFLINE: %$VSAN xyz%$ Interface fcipabc is down (Offline)
%PORT-5-IF_DOWN_NONE: %$VSAN xyz%$ Interface fcipabc is down (None)VSAN xyz is the allowed VSAN number for the FCIP interface and interface fcipabc is the configured FCIP interface number.
Workaround: Reload the MPS-14/2 module using the reload module module-number command, where module-number is a specific module.
•
Symptom: Two MDS 9000 switches configured with an FCIP bridge port (B port) tunnel may have problems with multi-frame sequences. You may notice this problem activating large zone sets when the SFC frame times out.
Workaround: If the connection is between two MDS switches, then the B port configuration is not required and should not be used. If B port is a requirement, then reduce the zone set length by not distributing the full database, or suffusions.
•
Symptom: The output from the fcping and traceroute commands shows an incorrect MDS 9000 switch and password for enclosure fabrics.
Workaround: None.
•
Symptom: When SANTap is unprovisioned without the appliance first deleting objects it had previously created, SANTap may have problems if the session objects are present.
Workaround: The appliance must delete all objects first before SANTap is unprovisioned.
•
Symptom: The line cards shut down after the supervisor module fails.
Workaround: Remove the failed supervisor module and reinsert the line card. Or enter the no poweroff module slot command in Exec mode on the switch, where slot is the slot number of the module that failed.
•
Symptom: If a Fibre Channel target goes offline while an iSCSI login is occurring, the IPS port will terminate the TCP session, but it will not return a login response PDU to the iSCSI initiator. As a result, some iSCSI initiators wait up to 30 seconds before they try to log in again.
Workaround: None.
•
Symptom: If you have configured your switch port for auto speed using the switchport speed auto command and auto mode using the switchport auto mode command, the switch port may fail to establish a link with the device connected through an Emulex HBA LP8000 and remains in a link-failure state after a switch upgrade to Cisco MDS SAN-OS Release 2.0.x. The problem occurs with the following combination of HBA, driver version 5.2.23.6. and 5.2.3790, firmware v3.92a2 and LP8000, and OS configured at 1-Gbps.
Workaround: Configure the switch port speed to 1-Gbps using the switchport speed 1000 command to support the Emulex HBA LP8000.
•
Symptom: An FCIP interface stays in the initializing state if it is part of a PortChannel and it is removed with the no fcip enable command.
Workaround: Remove the PortChannel that the FCIP interface previously belonged to.
•
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: A core dump is generated when a chassis reloads and multiple modules do not reboot in a reasonable amount of time. The system health monitor on a module is restarted by the process manager resulting in the core dump.
Workaround: None.
•
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. This bug is a duplicate of CSCeg53114.
Workaround: When a scenario like this occurs, Cisco MDS SAN-OS Release 2.1(2) prevents the problem by reserving any configured WWNs that belong to the system. In addition, users can check for potential conflicts in the current configuration using the iscsi duplicate-wwn-check command.
•
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 error message in the log file occurs because the platform manager component passes the wrong parameter while responding to an SNMP query. In some cases, this results in the query not being responded to.
Workaround: Perform a refresh on the Device Manager to clear the problem.
•
Symptom: An IVR zoneset activation fails at any IVR enabled switch and remains in "ready to advertise" state. This happens in very rare cases when the force option is not used while activating the IVR zoneset.
Workaround: Deactivate IVR zoneset from an IVR enabled switch where the IVR Zoneset activation status is either "ready to advertise" or "advertising". Note that this step would disrupt IVR traffic. When the deactivation is successful then reactivate the IVR zoneset with the force option.
•
Symptom: During a single CLI session, if a user repeatedly (over 6000+ times) enters a nested submode and exits all submodes using the end command, the system will crash.
Workaround: Log out of the session and log in again before continuing operations.
•
Symptom: In some rare cases, an IVR process may restart if VSANs with IVR devices are continuously suspended and unsuspended while IVR zone set activation is in progress.
Workaround: Avoid suspending and unsuspending VSANs with IVR members while IVR zone set activation is in progress.
•
Symptom: Following the merge of two fabrics, the Fabric Manager Client cannot open.
Workaround: Close all fabrics and reopen the new fabric.
•
Symptom: An installation of the Device Manager following the installation of the Fabric Manager failed the install process was trying to detect the port that will be used by the database server. If the port is taken, the installation displays an error and then quits.By default, the database tries to bind to port 9001. If the port is taken by another application, the database cannot be started.
Workaround: Do not check the database server port during installation. If the port is not available and the database server cannot be started, the database updating dialog box hangs. If that occurs, follow these steps to resolve the problem.
1.
2.
3.
•
Symptom: The CFS merge status as shown by the show cfs merge status name app-name command output may not reflect the correct merge status on certain switches while two fabrics are merging.
CFS merge is a protocol that runs between a designated switch in either fabric. Other switches do not participate in the merge process. While a merge is happening, the switches not merging do not reflect this, only the designated switches have the correct information. Once the merge is done, all switches would show the correct status. Usually, the merge completes in a very short time and this behavior is unlikely to be noticed.
Workaround: None.
•
Symptom: If you issue a dpvm commit command, the DPVM application implicitly activates the existing configuration database. The configuration database is activated only when the dpvm commit command is explicitly issued after the dpvm activate command.
Workaround: None.
•
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: When a scenario like this occurs, Cisco MDS SAN-OS Release 2.1(2) prevents the problem by reserving any configured WWNs that belong to the system. In addition, users can check for potential conflicts in the current configuration using the iscsi duplicate-wwn-check command.
•
Symptom: Password recovery might fail if you use the copy <config-url> startup command to save the switch configuration, or if you boot a system image that is older than the image you used to store the configuration and did not use the install all command. The following message might display in syslog or on the console during the process of password recovery.
<<%ASCII-CFG-2-ACFG_CONFIGURATION_APPLY_ERROR>>
Workaround: Issue the write erase command from the switchboot prompt.
Note
•
Symptom: iSNS server functionality may not restore iSCSI initiator node detail properly after a system switchover. Under this circumstance, iSNS server will not respond correctly to DevGetNext request from an iSNS client. This problem does not happen consistently.
Workaround: None
•
Symptom: If two fabrics merge, one with automatic VSAN topology and the other configured VSAN topology, and if the autonomous fabric ID assignment as per the user configured topology is not the same as the autonomous fabric ID assignment in the autonomous fabric ID table then sometimes the IVR zone set activation keeps waiting for the switch with the lowest WWW to modify the AFID table to correct the misconfiguration.
Workaround: Issue the clear ivr session command to clear the IVR session and reactivate the IVR zone set followed by the ivr commit command.
•
Symptom: The Fabric Manager server does not filter VSANs by each client's VSAN scope.
Workaround: None.
•
Symptom: Alias for a down endport is not shown and is referenced by its pwwn in the Edit FullZoneset screen of the Fabric Manager rather than the fcalias name. This does not affect the functionality of adding those members to the zones either in Fabric Manager or in the CLI.
Workaround: None
•
Symptom: The boot command accepts modflash://slot-0/, even though an image should not be stored on modflash://slot-0/. If it is, the image disappears upon SSM reload.
Workaround: Store an SSI image on the SSM flash on modflash://slot-1/ (where slot is the slot number where SSM is installed) and have the SSI boot variable point to modflash://slot-1/.
•
Symptom: The RMON_ALERT e-mail does not send the variable or any information about what alarm is triggered.
Workaround: None.
•
Symptom: The show version image command does not support the use of modflash:.
Workaround: Copy the image back to the supervisor to execute the show version image command.
•
Symptom: The RMON_ALERT e-mail does not send the variable or any information about what alarm is triggered.
Workaround: None.
•
Symptom: iSCSI initiators do not advertise their iqn names on Interop VSAN Fibre Channel name server (FCNS). Fabric Manager will not display them.
Workaround: None.
•
Symptom: After a process restart or merging with several fabrics simultaneously, the IVR zoneset activation process might hang in the "ready to advertise" state.
Workaround: Clear the IVR session by issuing the clear ivr session command and then reactivate the IVR zoneset by issuing the ivr zoneset activate name < name> force" followed by the ivr commit command.
•
Symptom: iSNS server continues giving a list of iSCSI targets that are in the VSAN of an iSCSI interface even after iSCSI VSAN membership feature is disabled.
Workaround: Explicitly put all iscsi interfaces in VSAN 1 before disabling iscsi interface vsan-membership.
•
Symptom: If you have an SSM with Fibre Channel write acceleration enabled, flapping a port during heavy I/Os causes the data plane processor (DPP) software to drain all the pending I/Os. If the draining process takes too long, it can result in timeouts for reconfiguration of the affected SCSI flows.
Workaround: After port flapping is finished, disable the SCSI flow features and reenable them.
•
Symptom: In the running-configuration output, the zoneset activate name zoneset_name vsan vsan command appears after the ivr zoneset activate name zoneset_name command. Hence, if a saved running-configuration is applied, then IVR zone set activation without the force option would fail if there is no active regular zone set when the ivr zoneset activate command is issued from the running configuration.
Workaround: Issue the ivr zoneset activate name <name> force command one more time followed by ivr commit.
•
Symptom: If IVR NAT mode is enabled, avoid IVR zone members within transit VSANs. In rare cases, IVR devices might not be able to communicate with each other when the IVR zone set has members in transit VSANs and when there are multiple parallel transit VSANs.
Workaround: None.
•
Symptom: If an IVR-enabled fabric (fabric A) running Cisco MDS SAN-OS Release 2.0(x) merges with an IVR-enabled fabric (fabric B) running Cisco MDS SAN-OS Release 2.1(x), then the IVR process on fabric A may restart if fabric B contains only an active IVR zone set but no configured zone sets.
Workaround: Make sure that fabric B has at least one IVR zone set configured.
•
Symptom: Following SSA1 losing sync, the switch resets SSA0 rather than SSA1, prior to sending a sync loss message to the supervisor. The crossbar manager reports a sync loss and a successful resync on either fabric 0 link1 or fabric 1 link1, but traffic does not flow to or from the line card.
Workaround: Reload the line card. Because this problem only occurs when sync loss has occurred, the loss of sync could indicate a hardware problem with the line card, the chassis, or the fabric.
•
Symptom: A corrupted license file installs on an MDS 9000 switch without errors.
Workaround: None.
•
Symptom: A Fabric Manager zone migration wizard causes a Telnet session to hang when a non-MDS switch is present.
Workaround: None.
•
Symptom: An Infotrend storage loop device does not perform fabric login (FLOGI) after failover testing.
Workaround: Issue the shutdown/no shutdown command sequence on the FC interface to force the Infotrend device to re-login. Contact Infotrend for a firmware release that prevents this problem.
•
Symptom: When you perform a nondisruptive upgrade from Release 1.3(x) to 2.0(x), and then issue the show running-config command, the switch displays the wrong user. The user shown will be inconsistent with the user shown when you issue the show user-account command.
Workaround: Recreate the user.
•
Symptom: Exception logs occur on a syslog verification. These are caused by repacking the fm.jar and fmserver.jar files. The Device Manager now requires the fmserver.jar file for a syslog RMI registry inquiry.
Workaround: None.
•
Symptom: In Fabric Manager, Cisco MDS switches in SAN islands appear under several logical domain SANs.
Workaround: None.
•
Symptom: An MDS 9000 switch running SAN-OS 2.0(1b) can potentially send excessive Call Home messages due to a malfunctioning line card that acts as if it were being inserted and removed repeatedly.
Workaround: None.
•
Symptom: After upgrading to Release 2.0, the switch incorrectly allows creation of a user role named admin, a system reserved name. If this role is subsequently deleted, the user account admin can no longer be modified (e.g. password change) and the CLI will incorrectly report that the user account admin does not exist.
Workaround: Before upgrading to Release 2.0, create the admin role.
•
Symptom: When no role is associated with a user, SNMP fails when the no role name admin command is issued to delete the admin role. The SNMP user (admin) has no roles assigned, which causes the failure when there is an attempt to delete a specific role.
Workaround: Associate at least one role (group) to the user by executing the snmp-server user username [group-name] command in config mode.
•
Symptom: When an iSCSI host sends a read command to a target and some Fibre Channel data-in frames are not received by an IPS line card but the MDS switch receives a good SCSI status frame from the target, the IPS port can send an iSCSI status PDU with a wrong Status Sequence Number (StatSN) to the iSCSI host, causing it to reset the TCP connection. This scenario has been observed in some rare instances of Fibre Channel cable cut testing.
Workaround: None.
•
Symptom: If there are two FCIP members in the PortChannel, while the traffic is running (at a 1-Gbps rate or any other large rate) bring up the second FCIP link (previously just one FCIP member is up), and you will see the total PortChannel throughput drop to about 10% of the previous number, and this low rate will last for about 25 seconds. This may cause array replication software to timeout on commands and lose sync.
Workaround: None.
•
Symptom: FLOGI service may fail after a switchover due to high availability inconsistency caused when a VSAN, enabled with FICON, is deleted and recreated. The VSAN configuration events should occur before the switchover. The process of bringing up the F port after the switchover triggers the FLOGI service termination. This scenario is very rare and is caused by some race conditions within the FLOGI service.
Workaround: None.
•
Symptom: Fabric Manager does not display FCIP tunnels properly.
Workaround: None.
•
Symptom: When a special frame is enabled for FCIP and FCIP is bound to an Ethernet channel, the IPS port may fail.
Workaround: Disable the special frame in FCIP.
•
Symptom: Following the installation of a third-party syslog server to a PC running Fabric Manager and Device Manager, the third-party syslog server takes ownership of the PC's IP address as the syslog server. As a result, FM/DM is no longer able to act as the syslog server.
You can see the error message "java.lang.NullPointerException" if you verify syslog on the MDS switch through Device Manager by choosing Logs > Syslog > Verify.
If you uninstall the third-party software and verify syslog again with Logs > Syslog > Verify, you see the error message "Can't connect to FM server."
Workaround: To allow FM/DM to be the syslog server, follow these steps:
1.
2.
3.
•
Symptom: If more than one path is configured for an explicit path, the running configuration shows one path, even when there are other paths. If the explicit path is not used for any FC-tunnel interface, then there is no problem.
Workaround: Copy the running configuration to a network file or onto bootflash. Manually add the paths that are present in the running configuration to the files.
•
Symptom: Ports are shown incorrectly in the MIB. In the CISCO-FCIP-MGMT-MIB, connUnitNumPorts should show only FC ports in the system. In the CISCO-FC-FE-MIB, fcFeModuleFxPortCapacity should show only the number of FC ports. For the MPS-14/2 module, Ethernet ports are also shown incorrectly. This caveat supersedes CSCeh74379.
Workaround: None.
•
Symptom: An HP blade server is recognized as a storage device by Fabric Manager.
Workaround: Manually set the HP blade server to a host device.
•
Symptom: Cisco MDS SAN-OS Release 2.1(1a) does not support in-order delivery (IOD) for QoS attribute changes in IVR traffic. However, QoS for IVR traffic is supported, along with IOD for IVR traffic in all other cases.
Workaround: None.
•
Symptom: The Performance Manager web client displays incorrect average and peak values. In such cases, values are higher than what is shown in the web client display.
Workaround: None.
•
Symptom: During a switch upgrade, a SAN Volume Controller (SVC) node may not save its entire state under rare circumstances. This results in that node not being part of the cluster after the switch upgrade. Verify this symptom by issuing the show nodes local command at the svc-config prompt—the command output displays the following information:
–
–
Workaround: Manually remove the SVC node from the cluster and then add the node back into the cluster. Refer to the Cisco MDS 9000 Family SAN Volume Controller Configuration Guide for procedural details.
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: If you install an SSM and boot it with either the VSFN or SSI image, the Enterprise License grace period starts.
Workaround: None.
•
Symptom: The VSAN suspend/resume operation facilitates network level reconfiguration and is not often used. In MDS SAN-OS Release 2.1(2), the command should not be used on 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: Removing zones from an active zone set may generate a system message that the zone activation has failed due to 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: A Brocade 3850 switch running 4.4.0c code in interop mode or a Bladecenter with a Brocade module running 4.4.1a code will fail upon receiving a SW-RSCN frame from an MDS 9000 Family switch that was generated as a result of a FC-4 registration from an HBA to a name server on the MDS switch.
When an FC-4 registration from an HBA to a name server on an MDS 9000 Family switch occurs, the switch generates a SW-RSCN with the switch event as NO_INFO(0x00), which is compliant with Fibre Channel standards. However, the Brocade switch expects a SW-RSCN with the switch event as ONLINE(0x01) upon FC-4 registration.
Workaround: Brocade is fixing this problem in their next release.
In the interim, you can use a new hidden command that when configured, allows the SW-RSCN frame that is sent during name server registration to carry the event ONLINE(0x01), instead of NO_INFO(0x00). You can configure this command only in interop mode 1.
To enable this feature, enter the following command:
switch(config)# rscn restrict swrscn-event vsan 1To disable this feature, enter the following command:
switch(config)# no rscn restrict swrscn-event vsan 1•
Symptom: If port 9001 is in use by another process, the database update for the previous release tables and data may hang.
Workaround: Edit the server.properties file in the bin directory and use another port. Alternatively, remove the process that opened port 9001.
•
Symptom: iSCSI hosts are unable to log in to the target storage arrays because of name server issues on the IPS blade.
Workaround: None.
•
Symptom: An iSCSI host cannot log in to one IPS port after many supervisor module switchovers.
Workaround: None.
•
Symptom: During a long testing cycle involving various tests, the port manager process failed due to a NULL pointer access causing a system switchover.
Workaround: None
•
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: 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: When IVR is enabled, the Fabric-Device Management Interface information is not transferred across VSANs for IVR devices.
Workaround: None.
•
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: On rare occasions, the PortChannels with FCIP interface members fail to come up when the switch reboots. This happens when the startup configuration has a default switchport trunk mode setting that does not match the configured trunk mode for PortChannel members (FCIP interfaces). Also, the startup configuration shows any explicit switchport trunk mode setting for the PortChannel.
Workaround: Reconfigure the switchport trunk mode on the PortChannel.
•
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: 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: Files created using the fcanalyzer local command cannot be copied or viewed. FC analyzer runs as root and the files that it creates are created with the owner as root. The correct file creation masks are not set when the file is created and so no user other than root can read or copy the file.
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 a FCIP tunnel in a PortChannel.
•
Symptom: If there are active IVR zones with the QoS attribute, then QoS should not be disabled (for example, with the no qos enable command or through Fabric Manager).
Workaround: Before disabling QoS, QoS attributes from the active IVR zones should be removed and then the resultant IVR zone set should be reactivated.
•
Symptom: Protocol and port numbers, if specified in a IP ACL assigned to a IPSec profile (crypto map), will be ignored.
The 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 the above 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: If you install an SSM and boot it with either the VSFN or SSI image, the Enterprise License grace period starts.
Workaround: None.
•
Symptom: Fabric Manager might display a duplicate SAN.
Workaround: Uninstall the current Cisco SAN-OS release, and then install Cisco SAN-OS Release 2.1(2b) to remove the invalid data completely. Or upgrade to Cisco SAN-OS Release 2.1(2b), and then open a fabric without reloading from the database.
•
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: LTO tape drives in the IBM-3584 library are not supported. When multiple initiators (such as Backup Host and NASB engine) issue SCSI write commands to this tape drive, it responds with a SCSI CHECK CONDITION with Sense - 0x03 and ASC/ASCQ = 0x3b/0x00. It does not handle the transition from the host initiator to the NASB engine initiator. In general, this is an issue for all NASB solutions with this tape drive and library combination. This behavior pertains only to the LTO drives on the IBM 3584 library. LTO-2 drives on the same library function correctly.
Workaround: None.
•
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 and then enable the link.
•
Symptom: When a reconfigure fabric (RCF) frame occurs on a VSAN, the ports may be left in a state where the fabric binding is incorrect.
Workaround: None. This issue has been resolved.
•
Symptom: During an upgrade of an MDS switch with two or more MPS-14/2 modules, FCIP tunnels on multiple MPS-14/2 modules can be down at the same time. If a PortChannel of two FCIP tunnels on different MPS-14/2 modules is used for redundancy, the redundancy can be lost. If IVR is running over these FCIP tunnels, IVR can lose remote devices as a result of loss of access over the FCIP based PortChannel.
Workaround: Place other modules on which you can perform a hitless upgrade between the MPS-14/2 modules to allow for more time between module upgrade and to give the FCIP tunnels more time to stabilize. To recover access over the FCIP based PortChannel, reactivate the IVR zone set by adding a dummy zone with two dummy members.
•
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: If iSCSI virtual targets are configured with more than 50 LUN maps, then erroneous overlapping LUN map system messages appear when the iSCSI initiator is not allowed to log in to these iSCSI virtual targets.
Workaround: None.
•
Symptom: In a fabric with more than one switch, there is a possibility of CFS or syslog crashing because of a PSS-FULL condition. This happens because of leakage in the PSS records stored by the CFS module.
CFS internal distributions cause a PSS leakage during one of the following:
–
–
Application and Regular CFS distributions in a stable fabric do not result in PSS leakages.
Workaround: None. A switchover will help in cleaning up these records but the usage of the partition remains same (dev/shm partition). However, CFS will reuse the freed space for further PSS storage.
•
Symptom: A Linux host with an iSCSI driver can see only the first eight Logical Units (LUs) of a configured iSCSI virtual target with more than eight LUN maps configured.
Workaround: None.
•
Symptom: The Fabric Manager server does not automatically handle a fabric merge and split. As a result, you many see duplicate fabrics in the database and the web client.
Workaround: Close all fabrics from the Fabric Manager Server and then reopen the new fabric.
•
Symptom: 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: 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: 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: If you upgrade from a SAN-OS Release 1.3(x) image to a 2.0(x) or 2.1(x) image, ongoing traffic may be disrupted because spurious Registered State Change Notifications (RSCNs) are generated during the upgrade. Hosts that are registered to receive RSCNs using State Change Registration (SCR) get these spurious RSCNs and are disrupted. If you upgrade from a Release 2.0(x) image to a 2.1(x) image, there is no traffic disruption.
Workaround: Use the rscn suppress interface fcx/y hidden command to suppress the RSCNs on a per interface basis during the upgrade.
Note
To use the hidden configuration command to suppress the RSCNs, follow these steps:
1.
2.
3.
4.
5.
6.
•
Symptom: Issuing the no shutdown command on a port produces this error:
fc1/1: (error) port channel config in progress - config not allowedYou can reproduce the problem by removing a port from a port channel and then perform a system switchover. However, the problem does not always occur with these steps.
Workaround: Use the channel-group X command where port channel X, to configure a new port channel and add the port to it. Then use the no interface port-channel X command to remove the newly created port channel. The no shutdown command will now be accepted on the port.
•
Symptom: In rare circumstances, after you issue the install all command to upgrade an MDS switch, the upgrade may fail because the installer process fails. When this failure occurs, you may see a message like the following:
%CALLHOME-2-EVENT: SW_CRASH alert for service: installerThe installer failed to respond for 10 times. Exiting ...Unable to send exit to installer. Return code -1If you upgrade from 1.3(x) to 2.1 or from 2.0(x) to 2.1 and the upgrade fails, and if after the upgrade failure the supervisor modules are running the new software version, but some modules are running the older software version, then the next attempt to execute the install all command will trigger this problem.
You should not encounter this problem if you upgrade from 2.1 to a higher version.
Workaround: There are two ways to address this issue:
•
•
•
Symptom: When a data path on a Storage Service Module (SSM) is congested, diagnostic frames that are delivered as best effort may be dropped. The Online Health Management System (OHMS) may bring down a Fibre Channel port on an SSM when congestion occurs and declare the port as failed.
Workaround: To work around this issue, enter the following command:
switch(config)# no system health module ssm-module-number loopback failure-action•
Symptom: A device alias cannot be renamed using Fabric Manager. Fabric Manager is polling the description of the device and not the name or alias for the device.
Workaround: Use the CLI to rename the device alias.
•
Symptom: When you attempt to copy a running configuration or startup configuration to a tftp server in a single step, the operation fails.
Workaround: Copy the configuration in two steps:
switch# copy running-config volatile:switch# copy volatile: tftp:•
Symptom: In Cisco SAN-OS Release 2.1, if more than 250 iSCSI sessions are present on an IPS services module port with proxy initiator mode configured, a port software failure may occur.
Workaround: Limit the maximum number of sessions on an IPS services module port with proxy initiator mode to 250.
In SAN-OS Release 3.0(1), the session limit has increased to 500 sessions per IPS services module port in both transparent and proxy initiator mode.
•
Symptom: Following a successful login by a host, the show interface command lists an interface as "isolated due to port loopback." In Fabric Manager, the Device Manager shows the same information about the interface.
Workaround: None.
•
Symptom: On an MDS 9500 Series switch running Cisco SAN-OS Release 2.1(1b), the output of the show version command shows the wrong value for the last reset, but this does not cause any operational problems on the switch. The output may look like the following:
kernel uptime is 137 days 3 hours 49 minute(s) 32 second(s)Last reset at -447213060 usecs after Sun Mar 18 05:59:15 2018Reason: Not definedSystem version: Service: §"HWorkaround: None.
•
Symptom: This issue is a duplicate of CSCsd45429.
Workaround. None. This issue has been resolved.
•
Symptom: If a switch has multiple SSMs with the SCSI flow feature enabled, an SSM may fail to come up when you perform an upgrade or reload.
Workaround: Before attempting to upgrade or reload an SSM, remove SCSI flow provisioning. Once the SSM comes back up, enable SCSI flow provisioning again.
Follow these steps:
1.
switch(config)# no ssm enable feature scsi-flow force module module-number2.
switch# install all system bootflash:m9500-sf1ek9-mz.2.1.2d.bin kickstart bootflash:m9500-sf1ek9-kickstart-mz.2.1.2d.bin ssi bootflash:m9000-ek9-ssi-mz.2.1.2j.bin3.
switch(config)# ssm enable feature scsi-flow module module-number4.
switch# show module5.
switch# reload module module-number6.
Note
•
Symptom: FCIP tape acceleration causes a flap in the FCIP link when it receives duplicate CHECK CONDITION status frames from a tape device.
Workaround: Because there is no workaround when the tape drive is functioning in this manner, we recommend that you turn off FCIP tape acceleration.
•
Symptom: A Fibre Channel Inter-Switch Link (ISL) does not come up and it displays a fabric binding database mismatch error when fabric binding is activated. Thi s problem may be seen when a supervisor switchover occurs or is performed and this ISL comes up. The fabric binding merge activity detects an incompatible database and fails to bring up the link because an incorrect domain ID is being used by the fabric binding module. The fabric binding module on the switch where the switchover occurs would have cleared its local domain ID and be using a domain ID of zero.
Workaround: Issue the fcdomain restart vsan vsan-id command in the VSANs of interest.
•
Symptom: When using Cisco MDS SAN-OS Release 2.1(2e) or earlier to configure PortChannels, the following message may be displayed:
Last membership update failed: port-channel: required service is not responding (err_id 0x402B No portIf this issue occurs, any attempt to delete the PortChannel will fail and no additional operations can be performed on that specific PortChannel that gave the error.
Workaround: Upgrade from Cisco SAN-OS Release 2.1(2e) or earlier to Release 3.0(2a) to prevent the problem from occurring. If the problem has already occurred, an upgrade to Release 3.0(2a) will not correct the problem. Issue the write erase command and reboot the system to correct this problem.
•
Symptom: In Fabric Manager, the local zone database is not synchronized.
Workaround: None.
•
Symptom: The Qlogic 2460 HBA fails to remote boot when it connects to a VT instantiated by SANTap on the SSM because the Qlogic 2460 BIOS sends a test ready unit with an invalid command reference number (CRN) and task attribute field. This same HBA can boot when SANTap and the SSM are not part of the configuration.
Workaround:Use the Qlogic 2340 HBA.
•
Symptom: In a system with autocreate PortChannel configured, if there are multiple link flaps or configuration changes on a PortChannel, the PortChannel Manager process memory might run out causing the PortChannel Manager process to crash.
Workaround: Issue the write erase command and reload the switch.
•
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: If you issue immediate, back-to-back commands to delete and then create FCIP interfaces, the internal port service might crash.
Workaround: Wait 5 seconds between the delete and the following create command for a given FCIP interface.
•
Symptom: The dynamic port VSAN membership (DPVM) failed after the number of F ports exceeded 64 and a port flap occurred.
Workaround: Keep the number of F ports in a switch below 64.
•
Symptom: If a Generation 1 module has any port that is administratively up, but operationally down when you upgrade from SAN-OS Release 2.x to either Release 3.0(1) or Release 3.0(2x), you might experience traffic disruption on that module.
Workaround: Use the shutdown command to shut all the ports operationally down and administratively up on all the Generation 1 modules before upgrading from SAN-OS Release 2.x to Release SAN-OS 3.0(x) or Release 3.0(2x). After the upgrade is complete, the ports can be brought to an administratively up state using the no shutdown command.
Related Documentation
The documentation set for the Cisco MDS 9000 Family includes the following documents:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
For information on VERITAS Storage Foundation™ for Networks for the Cisco MDS 9000 Family, refer to the VERITAS website: http://support.veritas.com/
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/
Obtaining Documentation
Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.
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
Cisco documentation and additional literature are available in the Product Documentation DVD package, which may have shipped with your product. The Product Documentation DVD is updated regularly and may be more current than printed documentation.
The Product Documentation DVD is a comprehensive library of technical product documentation on portable media. The DVD enables you to access multiple versions of hardware and software installation, configuration, and command guides for Cisco products and to view technical documentation in HTML. With the DVD, you have access to the same documentation that is found on the Cisco website without being connected to the Internet. Certain products also have .pdf versions of the documentation available.
The Product Documentation DVD is available as a single unit or as a subscription. Registered Cisco.com users (Cisco direct customers) can order a Product Documentation DVD (product number DOC-DOCDVD=) from the Ordering tool or Cisco Marketplace.
Cisco Ordering tool:
http://www.cisco.com/en/US/partner/ordering/
Cisco Marketplace:
http://www.cisco.com/go/marketplace/
Ordering Documentation
Beginning June 30, 2005, registered Cisco.com users may order Cisco documentation at the Product Documentation Store in the Cisco Marketplace at this URL:
http://www.cisco.com/go/marketplace/
Cisco will continue to support documentation orders using the Ordering tool:
•
http://www.cisco.com/en/US/partner/ordering/
•
http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm
•
Documentation Feedback
You can rate and provide feedback about Cisco technical documents by completing the online feedback form that appears with the technical documents on Cisco.com.
You can send comments about Cisco documentation to bug-doc@cisco.com.
You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:
Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883We appreciate your comments.
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 can perform these tasks:
•
•
•
A current list of security advisories and notices for Cisco products is available at this URL:
If you prefer to see advisories and notices as they are updated in real time, you can access a Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed from 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 might 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 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.htm
The link on this page has the current PGP key ID in use.
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
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)—Your 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 operation 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 your network is impaired, but 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/go/marketplace/
•
•
•
http://www.cisco.com/go/iqmagazine
or view the digital edition at this URL:
http://ciscoiq.texterity.com/ciscoiq/sample/
•
•
http://www.cisco.com/en/US/products/index.html
•
http://www.cisco.com/discuss/networking
•
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.
CCSP, CCVP, the Cisco Square Bridge logo, Follow Me Browsing, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.; and Access Registrar, Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, FormShare, GigaDrive, GigaStack, HomeLink, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, Linksys, MeetingPlace, MGX, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, ProConnect, RateMUX, ScriptShare, SlideCast, SMARTnet, StrataView Plus, TeleRouter, 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. (0502R)
Copyright © 2004 - 2005 Cisco Systems, Inc. All rights reserved.
