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.
•
Guest
