Table Of Contents
Cisco MDS 9000 Family Release Notes
for Cisco MDS SAN-OS Release 2.1(2)Determining the Software Version
Performing a Disruptive Upgrade on a Single Supervisor MDS Family Switch
New Features in Cisco MDS SAN-OS Release 2.1(2)
Nondisruptive Storage Services Module (SSM) Image Upgrade
Default Initial State for SSMs
Persistent FC IDs and Domains for IVR
SCSI Flow Services Support for Interfaces
Special Characters in TACACS+ Global Secret Keys
Control for SNMP Notifications for linkUp/linkDown Traps
NASB Storage Array Controller Support
Cisco Product Security Overview
Reporting Security Problems in Cisco Products
Obtaining Technical Assistance
Cisco Technical Support & Documentation Website
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Cisco MDS 9000 Family Release Notes
for Cisco MDS SAN-OS Release 2.1(2)
Release Date: July 26, 2005
Text Part Number: OL-7411-03 R0
This document describes the caveats and limitations for switches in the Cisco MDS 9000 Family. Use this document in conjunction with documents listed in the "Related Documentation" section.
Note
Release notes are sometimes updated with new information on restrictions and caveats. Refer to the following website for the most recent version of the Cisco MDS 9000 Family Release Notes: http://www.cisco.com/en/US/products/hw/ps4159/ps4358/prod_release_notes_list.html
Table 1 shows the on-line change history for this document.
Table 1 On-Line History Change
A0
7/25/2005
Created release notes
B0
08/05/2005
Added DDTS CSCeh41099
C0
08/08/2005
Changed the state of DDTS CSCin95832
D0
08/11/2005
Added DDTS CSCeh70232
E0
08/22/2005
Removed DDTS CSCeh61610
F0
08/23/2005
Added DDTS CSCeh61610
G0
11/03/2005
Added DDTS CSCeh69186
H0
12/07/2005
Added DDTS CSCsc31424
I0
12/30/2005
Added DDTS CSCei91968
I1
02/22/2006
Added DDTS CSCsc23435 and CSCsc57865
J0
05/26/2006
Added DDTS CSCeg33121, CSCeg53114, CSCeg82721, CSCeh30951, CSCeh52973, CSCeh65824, CSCei36082, CSCei55208, CSCei79457, CSCei57342, CSCei58652, CSCei67982, CSCei71686, CSCei86399, CSCei91676, CSCsb89732, CSCsc09732, CSCsc23435, CSCsc28722, CSCsc33788, CSCsc48919, CSCsc57865, CSCsc93936, CSCsc97070, CSCsd07246, CSCsd29338, CSCsd30165, CSCsd71701, CSCsd72822, CSCsd76429, CSCsd89872, and CSCsd94718
K0
06/06/2006
Removed DDTS CSCed16845
L0
08/07/2006
Removed DDTS CSCeg33121, CSCeg84871, CSCeh30951, CSCei10774, CSCei55341
Added DDTS CSCse84811,
Revised DDTS CSCsd89872 description
Revised status for DDTS CSCei10774, CSCeg90336, CSCeh93109
M0
09/05/2006
Added DDTS CSCsd78967
N0
09/13/2006
Added DDTS CSCsf21970
O0
11/07/2006
Added DDTS CSCse70275, and CSCsg15392
P0
02/23/2007
Added DDTS CSCse99087, CSCsg03171, and CSCsh27840.
Q0
04/04/2007
Added the section "Performing a Disruptive Upgrade on a Single Supervisor MDS Family Switch".
R0
08/24/2007
Added DDTS CSCsd83775.
Contents
This document includes the following sections:
•
•
•
•
Introduction
The Cisco MDS 9000 Family of multilayer directors and fabric switches offers intelligent fabric-switching services that realize maximum performance while ensuring high reliability levels. These switches combine robust and flexible hardware architecture with multiple layers of network and storage management intelligence. This powerful combination enables highly available, scalable storage networks that provide advanced security and unified management features.
The Cisco MDS 9000 Family provides intelligent networking features such as multiprotocol and multitransport integration, virtual SANs (VSANs), advanced security, sophisticated debug analysis tools, and unified SAN management.
System Requirements
This section describes the system requirements for Cisco MDS SAN-OS Release 2.1(2) and includes the following topics:
•
Components Supported
Table 2 lists the software and hardware components supported by the Cisco MDS 9000 Family.
Note
Table 2 Cisco MDS 9000 Family Supported Software and Hardware Components
Software
M95S1K9-2.1.2
MDS 9500 Supervisor/Fabric-I, SAN-OS software.
MDS 9500 Series only
M92S1K9-2.1.2
MDS 9216 Supervisor/Fabric-I, SAN-OS software.
MDS 9200 Series only
M91S1K9-2.1.2
MDS 9100 Supervisor/Fabric-I, SAN-OS software.
MDS 9100 Series only
License
M9500ENT1K9
Enterprise package.
MDS 9500 Series
M9200ENT1K9
Enterprise package.
MDS 9200 Series
M9100ENT1K9
Enterprise package.
MDS 9100 Series
M9500FIC1K9
Mainframe package.
MDS 9500 Series
M9200FIC1K9
Mainframe package.
MDS 9200 Series
M9100FIC1K9
Mainframe package.
MDS 9100 Series
M9500FMS1K9
Fabric Manager Server package.
MDS 9500 Series
M9200FMS1K9
Fabric Manager Server package.
MDS 9200 Series
M9100FMS1K9
Fabric Manager Server package.
MDS 9100 Series
M9500EXT1K9
SAN Extension over IP package for IPS-8 module.
MDS 9500 Series
M9200EXT1K9
SAN Extension over IP package for IPS-8 module.
MDS 9200 Series
M9500EXT14K9
SAN Extension over IP package for IPS-4 module.
MDS 9500 Series
M9200EXT14K9
SAN Extension over IP package for IPS-4 module.
MDS 9200 Series
M9500EXT12K9
SAN Extension over IP package for MPS 14+2 module.
MDS 9500 Series
M9200EXT12K9
SAN Extension over IP package for MPS 14+2 module.
MDS 9200 Series
M9500SSE1K9
Storage Services Enabler package.
MDS 9500 Series with ASM or SSM
M9200SSE1K9
Storage Services Enabler package.
MDS 9200 Series with ASM or SSM
Chassis
DS-C9509
MDS 9509 director, base configuration (9-slot modular chassis includes 7 slots for switching modules and 2 slots for supervisor modules—SFPs1 sold separately).
MDS 9509 only
DS-C9506
MDS 9506 director (6-slot modular chassis includes 4 slots for switching modules and 2 slots for supervisor modules—SFPs sold separately).
MDS 9506 only
DS-C9216-K9
MDS 9216 16-port semi-modular fabric switch (includes 16 1-Gbps/2-Gbps Fibre Channel ports, power supply, and expansion slot—SFPs sold separately).
MDS 9216 only
DS-C9216A-K9
MDS 9216A 16-port semi-modular fabric switch (includes 16 1-Gbps/2-Gbps Fibre Channel ports, power supply, and expansion slot—SFPs sold separately).
MDS 9216A only
DS-C9216i-K9
MDS 9216i 16-port semi-modular fabric switch (includes 14 1-Gbps/2-Gbps Fibre Channel ports, 2 Gigabit Ethernet ports, power supply, and expansion slot—SFPs sold separately).
MDS 9216i only
DS-C9120-K9
MDS 9120 fixed configuration, non-modular, fabric switch (includes 4 full rate ports and 16 host-optimized ports).
MDS 9120 only
DS-C9140-K9
MDS 9140 fixed configuration (non-modular) fabric switch (includes 8 full rate ports and 32 host-optimized ports).
MDS 9140 only
Supervisor modules
DS-X9530-SF1-K9
MDS 9500 Supervisor/Fabric-I, module.
MDS 9500 Series only
Switching modules
DS-X9016
MDS 9000 16-port 1-Gbps/2-Gbps Fibre Channel module (SFPs sold separately).
MDS 9500 Series and 9200 Series
DS-X9032
MDS 9000 32-port 1-Gbps/2-Gbps Fibre Channel module (SFPs sold separately).
Services modules
DS-X9308-SMIP
8-port Gigabit Ethernet IP Storage Services module.
DS-X9304-SMIP
4-port Gigabit Ethernet IP Storage Services module.
DS-X9032-SMV
32-port Fibre Channel Advanced Services Module (ASM).
DS-X9032-SSM
MDS 9000 32-port 1-Gbps/2-Gbps Fibre Channel Storage Services Module (SSM).
DS-X9560-SMC
Caching Services Module (CSM).
DS-X9302-14K9
14-port Fibre Channel/2-port Gigabit Ethernet Multiprotocol Services (MPS-14/2) module.
LC-type fiber-optic SFP
DS-SFP-FC-2G-SW
2-Gbps/1-Gbps Fibre Channel — short wavelength SFP.
MDS 9000 Family
DS-SFP-FC-2G-LW
2-Gbps/1-Gbps Fibre Channel — long wavelength SFP.
DS-SFP-FCGE-SW
1-Gbps Ethernet and 1-Gbps/2-Gbps Fibre Channel—short wavelength SFP.
DS-SFP-FCGE-LW
1-Gbps Ethernet and 1-Gbps/2-Gbps Fibre Channel — long wavelength SFP.
CWDM2
CWDM-SFP-xxxx-2G
Gigabit Ethernet and 1-Gbps/2-Gbps Fibre Channel SFP LC interface xxxx nm, where xxxx = 1470, 1490, 1510, 1530, 1550, 1570, 1590, or 1610 nm.
MDS 9000 Family
CWDM-MUX-4
Add/drop multiplexer for four CWDM wavelengths.
CWDM-MUX-8
Add/drop multiplexer for eight CWDM wavelengths.
CWDM-CHASSIS-2
Two slot chassis for CWDM add/drop multiplexer(s).
Power supplies
DS-CAC-300W
300-W3 AC power supply.
MDS 9100 Series only
DS-CAC-845W
845-W AC power supply.
MDS 9200 Series only
DS-CAC-2500W
2500-W AC power supply.
MDS 9509 only
DS-CDC-2500W
2500-W DC power supply.
DS-CAC-4000W-US
4000-W AC power supply for US (cable attached).
DS-CAC-4000W-INT
4000-W AC power supply international (cable attached).
DS-CAC-1900W
1900-W AC power supply.
MDS 9506 only
DS-CDC-1900W
1900-W DC power supply.
CompactFlash
MEM-MDS-FLD512M
MDS 9500 supervisor CompactFlash disk, 512MB.
MDS 9500 Series only
Port analyzer adapter
DS-PAA-2
A standalone Fibre Channel-to-Ethernet adapter that allows for simple, transparent analysis of Fibre Channel traffic in a switched fabric.
MDS 9000 Family
CD-ROM
M90FM-CD-212=
MDS 9000 Management Software and Documentation CD-ROM, spare
MDS 9000 Family
1 SFP = small form-factor pluggable
2 CWDM = coarse wavelength division multiplexing
3 W = Watt
Determining the Software Version
Note
To determine the version of the Cisco MDS SAN-OS software currently running on a Cisco MDS 9000 Family switch using the CLI, log into the switch and enter the show version EXEC command.
To determine the version of the Cisco MDS SAN-OS software currently running on a Cisco MDS 9000 Family switch using the Fabric Manager, view the Switches tab in the Information pane, locate the switch using the IP address, logical name, or WWN, and check its version in the Release column.
Image Upgrade
The Cisco MDS SAN-OS software is designed for mission-critical high availability environments. To realize the benefits of nondisruptive upgrades on the Cisco MDS 9500 Directors, we highly recommend that you install dual supervisor modules.
You can nondisruptively upgrade to Cisco MDS SAN-OS Release 2.1(2) from any SAN-OS software release beginning with Release 1.3(x). If you are running an older version of the SAN-OS, upgrade to Release 1.3(x) and then Release 2.1(2).
When downgrading from Cisco MDS SAN-OS Release 2.1(2) to Release 1.3(x), you might need to disable new features in Release 2.1(2) for a nondisruptive downgrade. Issuing the install all command from the CLI, or using Fabric Manager to perform the downgrade enables the compatibility check. The check indicates that the downgrade is disruptive and the reason is "current running-config is not supported by new image."
Compatibility check is done:Module bootable Impact Install-type Reason------ -------- -------------- ------------ ------2 yes disruptive reset Current running-config is not supported by new image3 yes disruptive reset Current running-config is not supported by new image5 yes disruptive reset Current running-config is not supported by new image6 yes disruptive reset Current running-config is not supported by new imageAt a minimum, you need to disable the default device alias distribution feature using the no device-alias distribute command in global configuration mode. The show incompatibility system bootflash:1.3(x)_filename command determines which additional features need to be disabled.
Note
Performing a Disruptive Upgrade on a Single Supervisor MDS Family Switch
Cisco MDS SAN-OS software upgrades are disruptive on the following single supervisor Cisco MDS Family switches:
•
•
•
If you are performing an upgrade on one of those switches, you should follow the nondisruptive upgrade path listed in this section, even though the upgrade is disruptive. Following the nondisruptive upgrade path ensures that the binary startup configuration remains intact.
If you do not follow the upgrade path, the binary startup configuration is deleted because it is not compatible with the new image, and the ASCII startup configuration file is applied when the switch comes up with the new upgraded image. When the ASCII startup configuration file is applied, there may be errors. Because of this, we recommend that you follow the nondisruptive upgrade path.
New Features in Cisco MDS SAN-OS Release 2.1(2)
This section describes the new features introduced in this release. For more information about the features listed, refer to the Cisco MDS 9000 Family Configuration Guide and the Cisco MDS 9000 Family Fabric Manager Configuration Guide.
Note
Nondisruptive Storage Services Module (SSM) Image Upgrade
You can perform a nondisruptive upgrade of Fibre Channel switching for an SSM using the new install ssi command. The SSM must be running EPLD version 2.1(2) to use the install ssi command. To upgrade the EPLD image, the SSM must be installed on a Cisco MDS 9500 Series switch.
Default Initial State for SSMs
Storage Service Modules (SSMs) initially come up in Fibre Channel switching mode by default.
Persistent FC IDs and Domains for IVR
You can configure persistent FC IDs and domains for IVR. This improves IVR management by allowing you to control and assign a specific virtual domain to use for a native VSAN, and by allowing you to control and assign a specific virtual FC ID to use for a device.
Note
SCSI Flow Services Support for Interfaces
You can configure SCSI flow services on groups of four interfaces, as well as on the entire module.
Special Characters in TACACS+ Global Secret Keys
Two special characters are allowed in TACACS+ global secret keys. You can use the dollar sign ($) and the percent sign (%) in TACACS+ global secret keys.
Control for SNMP Notifications for linkUp/linkDown Traps
In Cisco MDS SAN-OS Release 2.1(2), users can configure which linkUp/linkDown trap notifications to enable for interfaces.
NASB Storage Array Controller Support
You can enable Network-Accelerated Serverless Backup (NASB) as storage array controller devices.
NASB Target Rediscovery
You can enable Network-Accelerated Serverless Backup (NASB) to rediscover a target device.
iSCSI Duplicate WWN Check
You can check for potential WWN conflicts in the current configuration.
Fabric Manager Enhancements
The Cisco MDS 9000 Family Fabric Manager supports:
•
–
–
–
–
–
•
•
•
•
•
•
Limitations and Restrictions
This section lists the limitations and restrictions for this release.
SANTap
The maximum number of targets that SANTap supports is 16.
iSCSI
iSCSI pass-thru forwarding mode requires Microsoft iSCSI driver version 2.0 and Cisco iSCSI driver version 4.2.1. There are no restrictions for iSCSI store-and-forward forwarding mode.
VSFN Compatibility
For the latest VSFN compatibility information, refer to the Cisco MDS SAN-OS Release Compatibility Matrix for VERITAS Storage Foundation for Networks Software.
Caveats
This section lists the open and resolved caveats for this release. Use Table 3 to determine the status of a particular caveat. In the table, "O" indicates an open caveat and "R" indicates a resolved caveat.
Resolved Caveats
•
Symptom: In some rare instances in Cisco MDS SAN-OS Release 1.3, 2.0, and 2.1(1), when the IP Storage Services (IPS) module restarted after a failure, VSAN membership information about iSCSI interfaces was lost. However, a configuration saved with the copy running-config startup command was not lost.
Workaround: None.
•
Symptom: VPN 4.0.1 does not work with large SNMP PDU packets.
Workaround: Upgrade to VPN 4.0.5.
•
Symptom: Duplicate fabrics are opened under different SANs when the loadFromDB option is selected.
Workaround: In Fabric Manager, select Admin > Fabrics to remove the fabric, and then reopen it with the loadFromDB box deselected.
•
Symptom: Some hosts may not accept IKE tunnel creation from Cisco MDS 9000 Family switches when an IKE session already exists in the switch. In such cases it may take more than the expected time for the IPsec session to come up. This scenario can happen when the Gigabit Ethernet interface on the switch fails and comes back up or if you issue a VRRP switchover to a different switch.
Workaround: For a faster recovery, disconnect and reinitiate the iSCSI session from the host.
•
Symptom: If an IPS module with operational FCIP PortChannels is reloaded, upgraded, or downgraded, the supervisor module may be reloaded causing the system to reboot.
Workaround: Before reloading, upgrading, or downgrading an IPS module, shut down all FCIP PortChannels on the line card.
•
Symptom: Under certain traffic patterns, the Gigabit Ethernet port can flap when auto compression mode is selected. This problem can also occur rarely even when compression mode 1 is selected.
Workaround: Use mode 2 or mode 3 compression mode if the maximum throughput required is less than 25 Mega bits/sec. There is no workaround if the throughput requirement is > 25 Mbps.
•
Symptom: A user that you create in Fabric Manager or Device Manager cannot log in from the console. Release 2.1(2) fixes this problem. However, if a third-party application creates a user using SNMP, a new MIB is required for Release 3.0.
Workaround: Third-party applications should use SSH to connect to the MDS 9000 switch, and then use CLI commands to create the user account.
•
Symptom: The ICMP Path-MTU discovery might not work with IPsec depending upon the SPD policy that is created and where the ICMP error message is originated.
Workaround: Identify the path MTU and set it as the local interface MTU in the switch.
•
Symptom: iSCSI immediate and unsolicited data is not allowed to be used when the data digest is turned on.
Workaround: None.
•
Symptom: If an MDS switch has more than one module that supports Ethernet ports, the Cisco Discovery Protocol (CDP) learns entries over both the Gigabit Ethernet ports and the mgmt0 port. Subsequently, if there is either a system switchover or a restart of the CDP process, CDP will lose neighbors learned over the Gigabit Ethernet ports. A side effect of this behavior is that the sh cdp neighbors interface <gig intf> command causes the CDP process to crash and results in either a switchover on a dual supervisor or a reload on a single supervisor. This problem does not occur as long as the MDS switch is populated with just one module that supports Ethernet ports. Any combination of two or more modules supporting Ethernet ports will cause the problem. In addition, in the case of the Cisco MDS 9216i a module that supports Ethernet ports along with the supervisor module in slot1 is susceptible to the problem.
Workaround: None. Disable CDP so it does not learn of any entries, thereby preventing a crash or switchover.
•
Symptom: Traffic stops flowing when a member, who is not the first member, of a non-trunking PortChannel in an IVR zone set is flapped.
Workaround: None.
•
Symptom: In Fabric Manager, the switch appears in two VSANs when connected through ISL.
Workaround: None.
•
Symptom: FCIP Write Acceleration does not work with certain storage replication subsystems.
Workaround: None.
•
Symptom: Following an upgrade from Release 1.1 to Release 1.3 or higher, with persistent FC ID enabled, the FC IDs for the storage arrays may get changed after a link flap.
Workaround: None.
•
Symptom: Under certain traffic patterns, the auto compression mode in MPS-14/2 modules can cause a packet buffer leak. This might lead to a drop in FCIP performance. A low free clusters count below 40000 in the output of the show ips stats buffer interface gigabitethernet x/y command indicates that the IPS port may potentially have hit this bug.
Workaround: Reload the MPS-14/2 module. Or use compression mode2 or mode3 to avoid the problem
•
Symptom: When many iSCSI sessions go up or down simultaneously, such as when a line card fails, the amount of syslog messages generated can overwhelm the supervisor and cause a new iSCSI session login to be delayed.
Workaround: None.
•
Symptom: If two IPS ports on an IPS module are configured in the same IP subnet, but put on different LAN segments, external iSNS clients may not be able to connect to the iSNS server on the IPS port.
Workaround: Put the IPS ports in the same IP subnet on the same LAN segment.
•
Symptom: During an upgrade of the firmware on an IBM tape drive, the tape utility program may hang after it resets and performs loop initialization. The tape drive sends OPN, FLOGI, and CLS. The switch sends OPN and ACC, but does not send CLS, which causes the tape utility to hang while it waits for CLS.
Workaround: After the firmware is correctly upgraded on the tape drive, follow these steps:
–
–
•
Symptom: A newly configured FCIP link may fail to come up when running on an MPS-14/2 module. This symptom may occur following an upgrade of Cisco MDS SAN-OS Release 2.0(1b) to Release 2.0(3) and the configuration of a new FCIP link.
In the log on the switch, you may see the following messages:
%PORT-5-IF_DOWN_ELP_FAILURE_ISOLATION: %$VSAN xyz%$ Interface fcipabc is down (Isolation due to ELP failure)
%PORT-5-IF_DOWN_OFFLINE: %$VSAN xyz%$ Interface fcipabc is down (Offline)
%PORT-5-IF_DOWN_NONE: %$VSAN xyz%$ Interface fcipabc is down (None)VSAN xyz is the allowed VSAN number for the FCIP interface and interface fcipabc is the configured FCIP interface number.
Workaround: Reload the MPS-14/2 module using the reload module module-number command, where module-number is a specific module.
•
Symptom: Two MDS 9000 switches configured with an FCIP bridge port (B port) tunnel may have problems with multi-frame sequences. You may notice this problem activating large zone sets when the SFC frame times out.
Workaround: If the connection is between two MDS switches, then the B port configuration is not required and should not be used. If B port is a requirement, then reduce the zone set length by not distributing the full database, or suffusions.
•
Symptom: The output from the fcping and traceroute commands shows an incorrect MDS 9000 switch and password for enclosure fabrics.
Workaround: None.
•
Symptom: When SANTap is unprovisioned without the appliance first deleting objects it had previously created, SANTap may have problems if the session objects are present.
Workaround: The appliance must delete all objects first before SANTap is unprovisioned.
•
Symptom: The line cards shut down after the supervisor module fails.
Workaround: Remove the failed supervisor module and reinsert the line card. Or enter the no poweroff module slot command in Exec mode on the switch, where slot is the slot number of the module that failed.
•
Symptom: If a Fibre Channel target goes offline while an iSCSI login is occurring, the IPS port will terminate the TCP session, but it will not return a login response PDU to the iSCSI initiator. As a result, some iSCSI initiators wait up to 30 seconds before they try to log in again.
Workaround: None.
•
Symptom: If you have configured your switch port for auto speed using the switchport speed auto command and auto mode using the switchport auto mode command, the switch port may fail to establish a link with the device connected through an Emulex HBA LP8000 and remains in a link-failure state after a switch upgrade to Cisco MDS SAN-OS Release 2.0.x. The problem occurs with the following combination of HBA, driver version 5.2.23.6. and 5.2.3790, firmware v3.92a2 and LP8000, and OS configured at 1-Gbps.
Workaround: Configure the switch port speed to 1-Gbps using the switchport speed 1000 command to support the Emulex HBA LP8000.
•
Symptom: An FCIP interface stays in the initializing state if it is part of a PortChannel and it is removed with the no fcip enable command.
Workaround: Remove the PortChannel that the FCIP interface previously belonged to.
•
Symptom: When a default zoning policy is permitted and there is no active zone set, packets may drop on Fx ports if there are a lot of Fx and Nx ports going up and down.
Workaround: Configure and activate a zone set.
•
Symptom: A core dump is generated when a chassis reloads and multiple modules do not reboot in a reasonable amount of time. The system health monitor on a module is restarted by the process manager resulting in the core dump.
Workaround: None.
•
Symptom: WWNs assigned to iSCSI initiators by the system can inadvertently be returned to the system when an upgrade fails or a manual downgrade is performed, such as when an older iSAN software version is booted up without using the install all command. In these scenarios, the system can later assign those WWNs again to other initiators, which causes conflicts. This bug is a duplicate of CSCeg53114.
Workaround: When a scenario like this occurs, Cisco MDS SAN-OS Release 2.1(2) prevents the problem by reserving any configured WWNs that belong to the system. In addition, users can check for potential conflicts in the current configuration using the iscsi duplicate-wwn-check command.
•
Symptom: If the standby supervisor and the line cards are reloaded simultaneously, the line cards do not come online and reach the OK state.
Workaround: Perform a reload at the switch level to recover from this problem.
•
Symptom: An error message in the log file occurs because the platform manager component passes the wrong parameter while responding to an SNMP query. In some cases, this results in the query not being responded to.
Workaround: Perform a refresh on the Device Manager to clear the problem.
•
Symptom: An IVR zoneset activation fails at any IVR enabled switch and remains in "ready to advertise" state. This happens in very rare cases when the force option is not used while activating the IVR zoneset.
Workaround: Deactivate IVR zoneset from an IVR enabled switch where the IVR Zoneset activation status is either "ready to advertise" or "advertising". Note that this step would disrupt IVR traffic. When the deactivation is successful then reactivate the IVR zoneset with the force option.
•
Symptom: During a single CLI session, if a user repeatedly (over 6000+ times) enters a nested submode and exits all submodes using the end command, the system will crash.
Workaround: Log out of the session and log in again before continuing operations.
•
Symptom: In some rare cases, an IVR process may restart if VSANs with IVR devices are continuously suspended and unsuspended while IVR zone set activation is in progress.
Workaround: Avoid suspending and unsuspending VSANs with IVR members while IVR zone set activation is in progress.
•
Symptom: Following the merge of two fabrics, the Fabric Manager Client cannot open.
Workaround: Close all fabrics and reopen the new fabric.
•
Symptom: An installation of the Device Manager following the installation of the Fabric Manager failed the install process was trying to detect the port that will be used by the database server. If the port is taken, the installation displays an error and then quits.By default, the database tries to bind to port 9001. If the port is taken by another application, the database cannot be started.
Workaround: Do not check the database server port during installation. If the port is not available and the database server cannot be started, the database updating dialog box hangs. If that occurs, follow these steps to resolve the problem.
1.
2.
3.
•
Symptom: The CFS merge status as shown by the show cfs merge status name app-name command output may not reflect the correct merge status on certain switches while two fabrics are merging.
CFS merge is a protocol that runs between a designated switch in either fabric. Other switches do not participate in the merge process. While a merge is happening, the switches not merging do not reflect this, only the designated switches have the correct information. Once the merge is done, all switches would show the correct status. Usually, the merge completes in a very short time and this behavior is unlikely to be noticed.
Workaround: None.
•
Symptom: If you issue a dpvm commit command, the DPVM application implicitly activates the existing configuration database. The configuration database is activated only when the dpvm commit command is explicitly issued after the dpvm activate command.
Workaround: None.
•
Symptom: WWNs assigned to iSCSI initiators by the system can inadvertently be returned to the system when an upgrade fails or a manual downgrade is performed, such as when an older iSAN software version is booted up without using the install all command. In these scenarios, the system can later assign those WWNs again to other initiators, which causes conflicts. CSCei17870 is a duplicate of this caveat.
Workaround: When a scenario like this occurs, Cisco MDS SAN-OS Release 2.1(2) prevents the problem by reserving any configured WWNs that belong to the system. In addition, users can check for potential conflicts in the current configuration using the iscsi duplicate-wwn-check command.
•
Symptom: Password recovery might fail if you use the copy <config-url> startup command to save the switch configuration, or if you boot a system image that is older than the image you used to store the configuration and did not use the install all command. The following message might display in syslog or on the console during the process of password recovery.
<<%ASCII-CFG-2-ACFG_CONFIGURATION_APPLY_ERROR>>
Workaround: Issue the write erase command from the switchboot prompt.
Note
•
Symptom: iSNS server functionality may not restore iSCSI initiator node detail properly after a system switchover. Under this circumstance, iSNS server will not respond correctly to DevGetNext request from an iSNS client. This problem does not happen consistently.
Workaround: None
•
Symptom: If two fabrics merge, one with automatic VSAN topology and the other configured VSAN topology, and if the autonomous fabric ID assignment as per the user configured topology is not the same as the autonomous fabric ID assignment in the autonomous fabric ID table then sometimes the IVR zone set activation keeps waiting for the switch with the lowest WWW to modify the AFID table to correct the misconfiguration.
Workaround: Issue the clear ivr session command to clear the IVR session and reactivate the IVR zone set followed by the ivr commit command.
•
Symptom: The Fabric Manager server does not filter VSANs by each client's VSAN scope.
Workaround: None.
•
Symptom: Alias for a down endport is not shown and is referenced by its pwwn in the Edit FullZoneset screen of the Fabric Manager rather than the fcalias name. This does not affect the functionality of adding those members to the zones either in Fabric Manager or in the CLI.
Guest
