 Feedback
|
Table Of Contents
Cisco MDS 9000 Family Release Notes
for Cisco MDS SAN-OS Release 2.1(1b)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(1b)
Cisco Product Security Overview
Reporting Security Problems in Cisco Products
Obtaining Technical Assistance
Cisco Technical Support Website
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Cisco MDS 9000 Family Release Notes
for Cisco MDS SAN-OS Release 2.1(1b)
Release Date: July 25, 2005
Text Part Number: OL-7411-02 S0
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/04/2005
Added DDTS CSCed57251, CSCeh61610, CSCeh64080, CSCec31365, CSCeg20932, CSCeg53114, CSCeh52280, CSCeh56143, CSCeh82490, CSCeh83514, CSCeh87985, CSCeg90336, CSCeh52973, CSCeh87930, CSCeh90270, CSCeh93625, CSCei01431, CSCeh73101, CSCei29086, CSCeh39705, CSCeh49483, CSCeh70727, CSCeh71865, CSCeh73149, CSCeh85768, CSCeh87930, CSCeh90270, CSCeh91293, CSCeh93109, CSCeh95139, CSCei02196, CSCei18837, CSCeh08307, CSCeh79330, CSCeh82166, CSCei08541, CSCei22596, CSCei31020, CSCei32317, and CSCei50995
Added iSCSI information to the Limitations and Restrictions section.
C0
08/05/2005
Added DDTS CSCeh41099
D0
08/11/2005
Added DDTS CSCeh70232
E0
08/22/2005
Removed DDTS CSCeh61610
F0
08/23/2005
Added DDTS CSCeh61610
G0
09/20/2005
Added DDTS CSCei88345
H0
11/03/2005
Added DDTS CSCeh69186
I0
12/07/2005
Added DDTS CSCsc31424
J0
12/30/2005
Added DDTS CSCei91968
J1
02/22/2006
Added DDTS CSCsc23435
K0
05/26/2006
Added DDTS: CSCed16845, CSCeg12383, CSCeg33121, CSCeg37598, CSCeg53114, CSCeg72539, CSCeg82721, CSCeg84871, CSCeh30951, CSCeh65824, CSCeh70232, CSCeh92604, CSCei10774, CSCei19822, CSCei32317, CSCei36082, CSCei79457, CSCei91968, CSCei48889, CSCei57342, CSCei58652, CSCei67982, CSCei86399, CSCei91676, CSCej08751, CSCin92870, CSCin95879, CSCsb89732, CSCsc09732, CSCsc33788, CSCsc48919, CSCsc97070, CSCsd07246, CSCsd29338, CSCsd30165, CSCsd71701, CSCsd72822, CSCsd76429, and CSCsd89872
L0
06/06/2006
Removed DDTS CSCed16845
M0
8/7/2006
Added DDTS CSCse84811
Removed DDTS CSCeg33121, CSCeg84871, CSCeh30951, CSCei36082, CSCec31365, CSCeg12383, CSCeg53114, CSCeg55238, CSCeh34828, CSCei48889, CSCei91676, CSCej08751, CSCin92870, CSCin95879, CSCsd71701.
N0
09/05/2006
Added DDTS CSCsd78967
O0
09/13/2006
Added DDTS CSCsf21970
P0
11/07/2006
Added DDTS CSCsg15392 and CSCin95789
Q0
02/23/2007
Added DDTS CSCse99087, CSCsg03171, and CSCsh27840.
R0
04/04/2007
Added the section "Performing a Disruptive Upgrade on a Single Supervisor MDS Family Switch".
S0
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(1b) 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.1B
MDS 9500 Supervisor/Fabric-I, SAN-OS Software Release 2.1.1b
MDS 9500 Series only
M92S1K9-2.1.1B
MDS 9216 Supervisor/Fabric-I, SAN-OS Software Release 2.1.1b
MDS 9200 Series only
M91S1K9-2.1.1B
MDS 9100 Supervisor/Fabric-I, SAN-OS Software Release 2.1.1b
MDS 9100 Series only
License
M9500ENT1K9
Enterprise package.
MDS 9500 Series
M9200ENT1K9
Enterprise package.
MDS 9200 Series
M9100ENT1K9
Enterprise package.
MDS 9100 Series
M9500FIC1K9
Mainframe package.
MDS 9500 Series
M9200FIC1K9
Mainframe package.
MDS 9200 Series
M9100FIC1K9
Mainframe package.
MDS 9100 Series
M9500FMS1K9
Fabric Manager Server package.
MDS 9500 Series
M9200FMS1K9
Fabric Manager Server package.
MDS 9200 Series
M9100FMS1K9
Fabric Manager Server package.
MDS 9100 Series
M9500EXT1K9
SAN Extension over IP package for IPS-8 module.
MDS 9500 Series
M9200EXT1K9
SAN Extension over IP package for IPS-8 module.
MDS 9200 Series
M9500EXT14K9
SAN Extension over IP package for IPS-4 module.
MDS 9500 Series
M9200EXT14K9
SAN Extension over IP package for IPS-4 module.
MDS 9200 Series
M9500EXT12K9
SAN Extension over IP package for MPS 14+2 module.
MDS 9500 Series
M9200EXT12K9
SAN Extension over IP package for MPS 14+2 module.
MDS 9200 Series
M9500SSE1K9
Storage Services Enabler package.
MDS 9500 Series with ASM or SSM
M9200SSE1K9
Storage Services Enabler package.
MDS 9200 Series with ASM or SSM
Chassis
DS-C9509
MDS 9509 director, base configuration (9-slot modular chassis includes 7 slots for switching modules and 2 slots for supervisor modules—SFPs1 sold separately).
MDS 9509 only
DS-C9506
MDS 9506 director (6-slot modular chassis includes 4 slots for switching modules and 2 slots for supervisor modules—SFPs sold separately).
MDS 9506 only
DS-C9216-K9
MDS 9216 16-port semi-modular fabric switch (includes 16 1-Gbps/2-Gbps Fibre Channel ports, power supply, and expansion slot—SFPs sold separately).
MDS 9216 only
DS-C9216A-K9
MDS 9216A 16-port semi-modular fabric switch (includes 16 1-Gbps/2-Gbps Fibre Channel ports, power supply, and expansion slot—SFPs sold separately).
MDS 9216A only
DS-C9216i-K9
MDS 9216i 16-port semi-modular fabric switch (includes 14 1-Gbps/2-Gbps Fibre Channel ports, 2 Gigabit Ethernet ports, power supply, and expansion slot—SFPs sold separately).
MDS 9216i only
DS-C9120-K9
MDS 9120 fixed configuration, non-modular, fabric switch (includes 4 full rate ports and 16 host-optimized ports).
MDS 9120 only
DS-C9140-K9
MDS 9140 fixed configuration (non-modular) fabric switch (includes 8 full rate ports and 32 host-optimized ports).
MDS 9140 only
Supervisor modules
DS-X9530-SF1-K9
MDS 9500 Supervisor/Fabric-I, module.
MDS 9500 Series only
Switching modules
DS-X9016
MDS 9000 16-port 1-Gbps/2-Gbps Fibre Channel module (SFPs sold separately).
MDS 9500 Series and 9200 Series
DS-X9032
MDS 9000 32-port 1-Gbps/2-Gbps Fibre Channel module (SFPs sold separately).
Services modules
DS-X9308-SMIP
8-port Gigabit Ethernet IP Storage Services module.
DS-X9304-SMIP
4-port Gigabit Ethernet IP Storage Services module.
DS-X9032-SMV
32-port Fibre Channel Advanced Services Module (ASM).
DS-X9032-SSM
MDS 9000 32-port 1-Gbps/2-Gbps Fibre Channel Storage Services Module (SSM).
DS-X9560-SMC
Caching Services Module (CSM).
DS-X9302-14K9
14-port Fibre Channel/2-port Gigabit Ethernet Multiprotocol Services (MPS-14/2) module.
LC-type fiber-optic SFP
DS-SFP-FC-2G-SW
2-Gbps/1-Gbps Fibre Channel — short wavelength SFP.
MDS 9000 Family
DS-SFP-FC-2G-LW
2-Gbps/1-Gbps Fibre Channel — long wavelength SFP.
DS-SFP-FCGE-SW
1-Gbps Ethernet and 1-Gbps/2-Gbps Fibre Channel—short wavelength SFP.
DS-SFP-FCGE-LW
1-Gbps Ethernet and 1-Gbps/2-Gbps Fibre Channel — long wavelength SFP.
CWDM2
CWDM-SFP-xxxx-2G
Gigabit Ethernet and 1-Gbps/2-Gbps Fibre Channel SFP LC interface xxxx nm, where xxxx = 1470, 1490, 1510, 1530, 1550, 1570, 1590, or 1610 nm.
MDS 9000 Family
CWDM-MUX-4
Add/drop multiplexer for four CWDM wavelengths.
CWDM-MUX-8
Add/drop multiplexer for eight CWDM wavelengths.
CWDM-CHASSIS-2
Two slot chassis for CWDM add/drop multiplexer(s).
Power supplies
DS-CAC-300W
300-W3 AC power supply.
MDS 9100 Series only
DS-CAC-845W
845-W AC power supply.
MDS 9200 Series only
DS-CAC-2500W
2500-W AC power supply.
MDS 9509 only
DS-CDC-2500W
2500-W DC power supply.
DS-CAC-4000W-US
4000-W AC power supply for US (cable attached).
DS-CAC-4000W-INT
4000-W AC power supply international (cable attached).
DS-CAC-1900W
1900-W AC power supply.
MDS 9506 only
DS-CDC-1900W
1900-W DC power supply.
CompactFlash
MEM-MDS-FLD512M
MDS 9500 supervisor CompactFlash disk, 512MB.
MDS 9500 Series only
Port analyzer adapter
DS-PAA-2
A standalone Fibre Channel-to-Ethernet adapter that allows for simple, transparent analysis of Fibre Channel traffic in a switched fabric.
MDS 9000 Family
1 SFP = small form-factor pluggable
2 CWDM = coarse wavelength division multiplexing
3 W = Watt
Determining the Software Version
Note
To determine the version of the Cisco MDS SAN-OS software currently running on a Cisco MDS 9000 Family switch using the CLI, log into the switch and enter the show version EXEC command.
To determine the version of the Cisco MDS SAN-OS software currently running on a Cisco MDS 9000 Family switch using the Fabric Manager, view the Switches tab in the Information pane, locate the switch using the IP address, logical name, or WWN, and check its version in the Release column.
Image Upgrade
The Cisco MDS SAN-OS software is designed for mission-critical high availability environments. To realize the benefits of nondisruptive upgrades on the Cisco MDS 9500 Directors, we highly recommend that you install dual supervisor modules.
You can nondisruptively upgrade to Cisco MDS SAN-OS Release 2.1(1b) 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(1b).
When downgrading from Cisco MDS SAN-OS Release 2.1(1b) to Release 1.3(x), you might need to disable new features in Release 2.1(1b) 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(1b)
This section describes the new features introduced in this release. For more information about the features listed, refer to the documentation set listed in the "Related Documentation" section.
Note
Limitations and Restrictions
iSCSI pass-thru forwarding mode requires Microsoft iSCSI driver version 2.0 and Cisco iSCSI driver version 4.2.1. There are no restrictions for iSCSI store-and-forward forwarding mode.
Caveats
This section lists the open and resolved caveats for this release. Use Table 3 to determine the status of a particular caveat. In the table, "O" indicates an open caveat, and "R" indicates a resolved caveat.
Resolved Caveats
•
Symptom: An incorrect device instance on the MDS 9000 modules might get reinitialize from an error recovery mechanism, leaving the module in an unusable state. In some cases, the module may reboot. The system console reports that the module's ports are down due to a system health failure. The console and the switch log (sh logging logfile) will have the following error messages, which indicate that the switch is exhibiting this error:
Note
2005 Jul 12 12:18:29 mds-a1-ut %SYSTEMHEALTH-2-OHMS_MOD_PORT_LB_TEST_FAILED: Module 1 Port 1 has failed loop back tests.2005 Jul 12 12:18:29 mds-a1-ut %MODULE-2-MOD_DIAG_FAIL: Module 1 reported failure on ports 1/1-1/1 (Fibre Channel) due to System Health failure in device 6 (device error 0x40730019)2005 Jul 12 12:18:29 mds-a1-ut %MODULE-2-MOD_SOMEPORTS_FAILED: Module 1 reported failure on ports 1/1-1/1 (Fibre Channel) due to System Health failure in device 6 (error 0x40730019)Workaround: Downgrade to a Cisco MDS SAN OS Release 2.0(x) version supported by your OSM. Or upgrade to Cisco MDS SAN OS Release 2.1.2 or 2.1(1b). Resetting the module will clear the problem, but the problem could reoccur unless you are using a SAN OS version with the bug fix.
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: 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: 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 very rarely even when compression mode 1 is selected. This issue exists in Cisco MDS SAN OS Release 2.x releases after Release 2.0(1).
Workaround: Use mode 2 or mode 3 compression mode if the maximum throughput required is less than 25 Mbps. There is no workaround if the throughput requirement is > 25 Mbps.
•
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 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 IVR-enabled fabric running Cisco MDS SAN-OS Release 2.0 is merged with an IVR-enabled fabric running Cisco MDS SAN-OS Release 2.1 in NAT mode, then the IVR process on the 2.0 fabric may restart.
Workaround: Follow the IVR NAT guideline of not mixing fabrics in IVR NAT and non-NAT modes. For example, upgrade the fabric running Cisco MDS SAN OS Release 2.0 to Cisco MDS SAN OS Release 2.1 and have NAT mode enabled on that fabric before merging with another fabric where the NAT mode is already on.
•
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: 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: 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: 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: 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 use VSANs.
•
Symptom: The output from the fcping and traceroute commands shows an incorrect MDS 9000 switch and password for enclosure fabrics.
Workaround: None.
•
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 to transfer.
Workaround: Do not have the following on the same switch:
a.
b.
c.
However, any two of the above three configurations are supported on the same switch.
Note
•
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 your switch port is configured in auto speed (switchport speed auto) and auto mode (switchport mode auto), the switch port fails to establish a link with the device connected through Emulex HBA LP8000 and remains in link-failure state. The problem occurs with the following combination of HBA, driver, firmware, and OS configured at 1 Gbps.
Workaround: Configure the switch port speed to 1 Gbps (switchport speed 1000) 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: Disabling QoS does not remove the QoS attribute from an IVR zone set, and subsequent activation of the IVR zone set does not succeed.
Workaround: Remove the QoS attribute from the IVR zone set, both active and configured, before disabling QoS.
•
Symptom: If the standby supervisor and the line cards are reloaded simultaneously, the line cards do not come online and reach the OK state.
Workaround: Perform a reload at the switch level to recover from this problem.
•
Symptom: An active IVR zone set on the local switch is not propagated when the commit session contains any other configuration changes.
Workaround: For Cisco SAN-OS Release 2.1(2) and later, perform an implicit commit without any changes. In the case of a merge failure and the IVR zone set is not active on remote switches but is active on a local switch, issue an implicit commit from the local switch to propagate the active zone set to the remote switches.
For releases prior to Release 2.1(2), the workaround is different. Add either a dummy member to an existing zone or add a dummy zone with dummy members to the currently active IVR zone set, and then reactivate the IVR zone set. Then issue the commit command, which will propagate the active zone set to the other switches.
•
Symptom: An error message in the log file occurs because the platform manager component passes the wrong parameter while responding to a 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: 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: An Inter-Switch Link (ISL) flap resulting in fabric segmentation or a merge during or after an upgrade from Cisco MDS SAN-OS Release 2.0(x) to a later image where IVR is running might be disruptive. Some possible scenarios include:
–
–
–
If this problem occurs, syslogs indicate RDI failure and the flapped lSL could remain in a down state because of a domain overlap. This is caused by conflicts between the allowed domains list and the virtual domain requested through RDI.
Workaround: There are four distinct scenarios for which the workarounds are provided.
1.
2.
a.
Issue the fcdomain domain {id} static vsan {vsan id} command to configure the static domains.
Note
b.
Note
c.
Example Syslog Error Messages2005 Aug 31 21:52:04 switch %FCDOMAIN-2-EPORT_ISOLATED: %$VSAN 2005%$ Isolation of interface port-channel 52 (reason: unknown failure)2005 Aug 31 21:52:04 switch %FCDOMAIN-2-EPORT_ISOLATED: %$VSAN 2005%$ Isolation of interface port-channel 51 (reason: domain ID assignment failure)d.
switch(config)# vsan databaseswitch(config-vsan-db)# vsan { vsan ID} suspendswitch(config-vsan-db)# no vsan { vsan ID} suspende.
f.
3.
4.
Note
•
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: 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.
•
Symptom: VPN 4.0.1 does not work with large SNMP PDU packets.
Workaround: Upgrade to VPN 4.0.5.
•
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: 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: 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: 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: In Fabric Manager, a null pointer exception error message might result in a zone merge recovery on an already recovered fabric.
Workaround: Close the dialog box and relaunch it.
•
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 a DevGetNext request from an iSNS client. This problem does not happen consistently.
Workaround: None
•
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: A Windows host running Hummingbird 10 with Connectivity Secure Shell 9 cannot use SSH to connect to an MDS switch running Cisco MDS SAN-OS Releases 2.0(x) with the same host configuration used to connect to an MDS switch running 1.3(x) code.The host will display the error Authentication Failed, no more shared authentication methods.
Workaround: Reconfigure the client to use "keyboard-interactive" instead of "password" for authentication. To do this, go to tunnel profile settings, select Security Settings>Authentication. Ensure the "keyboard interactive" is the method used, "password" might be the currently configured method. Or upgrade to Cisco MDS SAN-OS Release 2.1(1a).
•
Symptom: If two fabrics merge, one with automatic VSAN topology and the other with configured VSAN topology, and if the autonomous fabric ID assignment configured by the user 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: The 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 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: 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: 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 the 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 zone set 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 zone set by issuing the ivr zoneset activate name ivzs-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 the iSCSI VSAN membership feature is disabled.
Workaround: Explicitly put all ISCSI interfaces in VSAN 1 before disabling the iscsi interface vsan-membership command.
•
Symptom: If you have an SSM with Fibre Channel write acceleration enabled, flapping a port during heavy I/Os causes the 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 done, disable the SCSI-flow features and reenable them.
•
Symptom: In the running-configuration output, the zoneset activate name zoneset_name vsan vsan-id command appears after the ivr zoneset activate name ivzs-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 ivzs-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: 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: A corrupted entry is created in the snmpTargetParamsTable when a user creates an entry with NULL string in object snmpTargetParamsName as its index. The SNMP service may stop and restart.
Workaround: None. To avoid similar problems, enter a name in snmpTargetParamsName with at least one character when creating a snmpTargetParamsEntry.
•
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: 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: 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: 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: 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, it is no longer possible to create, modify, or delete the admin role.
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 configuration mode.
•
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: If FC data-in frames for an iSCSI read command are lost between the FC target and an MDS switch with an IPS module but the MDS receives a good SCSI status frame from the target, the MDS switch can send an iSCSI status PDU with the wrong status sequence number (StatSN) to the iSCSI host causing it to reset the TCP connection to the MDS switch.
Workaround: None.
•
Symptom: When a special frame is enabled for FCIP and FCIP is bound to an Ethernet channel, the IPS port may fail. The failure results if FCIP TCP connections need to be migrated to the peer core and then TCP on the new peer core must be initialized properly.
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, the MDS switch 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 the MDS 9000 switch to be the syslog server, follow these steps:
1.
2.
3.
•
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.
Workaround: None.
•
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: 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: 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: 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.
•
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: 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, 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: The clear auto-learned entries command is not distributed over CFS by DPVM/CFS even if CFS distribution is enabled for the modules. Therefore, the command takes effect only at the local switch.
Workaround: None. You must issue the clear auto-learned entries command at every switch to clear all auto-learned entries in the fabric.
•
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: 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: 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 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: 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: The SAN-OS software creates a syslog message after a configuration change through the command-line interface The syslog message looks like this:
switch# 2006 Feb 8 09:00:33 switch %VSHD-5-VSHD_SYSLOG_CONFIG_I: Configuring console from pts/1 (dhcp-peg3-vl30-144-254-7-182.cisco.com)Using the Fabric Manager to make the same configuration change does not result in the same syslog message:
switch# 2006 Feb 8 09:00:56 switch %PORT-5-IF_DOWN_ADMIN_DOWN: %$VSAN 1%$ Interface fc1/5 is down (Administratively down)Workaround: None.
•
Symptom: 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: If you try to configure SSH key for any of the non-local user accounts, in some rare cases you might see a core dump on standby.
Workaround: First delete the non-local user-account and create it again so that it becomes a local user account. Then perform any type of configuration for that user account. User should not perform configuration operations on non- local user accounts. Non-local user accounts can be created due to users getting authenticated using the RADIUS/TACACS+ server.
•
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 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/univercd/home/home.htm
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
Documentation DVD
Cisco documentation and additional literature are available in a Documentation DVD package, which may have shipped with your product. The Documentation DVD is updated regularly and may be more current than printed documentation. The Documentation DVD package is available as a single unit.
Registered Cisco.com users (Cisco direct customers) can order a Cisco 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
You can find instructions for ordering documentation at this URL:
http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm
You can order Cisco documentation in these ways:
•
http://www.cisco.com/en/US/partner/ordering/
•
Documentation Feedback
You can send comments about technical 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:
•
•
Tip
Never use a revoked or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one that has the most recent creation date in this public key server list:
http://pgp.mit.edu:11371/pks/lookup?search=psirt%40cisco.com&op=index&exact=on
In an emergency, you can also reach PSIRT by telephone:
•
•
Obtaining Technical Assistance
For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, Cisco Technical Support provides 24-hour-a-day, award-winning technical assistance. The Cisco Technical Support Website on Cisco.com features extensive online support resources. In addition, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not hold a valid Cisco service contract, contact your reseller.
Cisco Technical Support Website
The Cisco Technical Support 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, 365 days a year, at this URL:
http://www.cisco.com/techsupport
Access to all tools on the Cisco Technical Support 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 TAC 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 TAC 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
•
•
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.
