Table Of Contents
Cisco MDS 9000 Family Release Notes for Storage Services Interface Image Release 4.1(1i)
Release Date: April 30, 2009
Text Part Number: OL-17791-04 B0
This document describes the caveats and limitations for the Storage Service Interface (SSI) software for the various Cisco MDS Services Module (SSM, MSM-18/4, and MDS 9222i module). Use this document in conjunction with the 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/ps5989/prod_release_notes_list.html
Table 1 shows the on-line change history for this document.
Table 1 Online History Change
Revision Date Description
Created release notes.
Added DDTS CSCsz19597.
This document includes the following sections:
The SSI interface provides the following features:
•Network-based volume management (EMC Invista, Incipient iNSP)
•Network-assisted storage applications using SANTap
•Fibre Channel Write Acceleration (FC-WA) and SCSI flow statistics
•Network-Accelerated Serverless Backup (NASB)
•Data Mobility Manager (DMM)
•Secure Data Erase
Note As of NX-OS Release 4.1(1b), SAN-OS has been changed to NX-OS. References to SAN-OS releases before 4.1(1b) still apply.
This section describes the system requirements for Cisco MDS NX-OS Release 4.1(1b) and includes the following topics:
Table 2 lists the software and hardware components supported by the Cisco MDS 9000 Family.
Determining the Software Version
Note Use the latest available software release supported by your vendor for all Cisco MDS 9000 Family products.
To determine the version of the Cisco NX-OS software currently running on a Cisco MDS 9000 Family switch using the CLI, log into the switch and enter the show version command.
To determine the version of the Cisco NX-OS software currently running on a Cisco MDS 9000 Family switch using the Fabric Manager, from the Switches tab in the information pane, locate the switch using the IP address, logical name, or WWN, and then check its version in the Release column.
To download the latest Cisco software, access the Software Center at this URL:
Note If you would like to request code to be provided under the terms of either GNU General Public License (GPL) or the GNU Lesser General Public License (LGPL), contact firstname.lastname@example.org.
If SSMs are present in a Cisco MDS 9000 Family switch, these upgrades may be performed as required:
•Upgrading a previously provided package
•Upgrading the SAN-OS image
•Reformatting the SSM add-on image
If you need additional information about installing or upgrading the SSM, refer to the Cisco MDS 9000 Family Storage Services Module Software Installation and Upgrade Guide.
This section describes the new features introduced in this release. For more information about the features listed, see the documentation set listed in the"Related Documentation" section.
The SSI release 4.1(1i) image is compatible with the Cisco MDS NX-OS Release 4.1(1b) image.
New Command Available in This Release
SSI Release 4.1(1i) includes the new system isapi set-critical-error-timeout 200 command, which is provided as a part of the workaround for the caveat CSCsy83457.
SANTap treats a data path processor (DPP) failure in an MSM-18/4 or MDS 9222i supervisor module as a core system failure. This type of failure results in an immediate critical iSAPI layer error that causes the module to reload. When this occurs, core files are uploaded to the supervisor in the case of the MSM-18/4, or to a TFTP server if one is configured. The core files will include DPP cores and SANTap process core.
The modules can be configured to upload partial DDP cores (3 core files) or full cores (32 core files) using the ips core dump command. If a full DPP core upload has been configured, then an additional command is required to ensure that all core files upload before the module resets.
To delay the module reload by a specified value, use the system isapi set-critical-error-timeout 200 command. This command is a module command that you must enter at the module prompt, after you enter the attach module slot-number command.
Entering the system isapi set-critical-error-timeout 200 command will delay the module reset for all critical errors. The timeout value should be specified as 200, which is enough time to upload all the core files. This command is not saved in the running-config or startup-config, and must be issued every time the module comes up.
This issue of a possible module reload occurring before all core files have uploaded will be resolved in SSI Release 4.1(3i), and then the system isapi set-critical-error-timeout 200 command will no longer be supported.
This sections lists limitations or restrictions associated with this release.
Configuring SSM Ports in Auto Mode
Starting with Cisco MDS SAN-OS Release 3.0(1), the SSM front panel ports can no longer be configured in auto mode. Because auto mode is the default for releases prior to Release 3.0(1), you should modify the configuration of the ports before upgrading the SAN-OS software image to NX-OS Release 4.1(1b) to avoid any traffic disruption.
For information on how to reconfigure the SSM ports, refer to the "Reconfiguring SSM Ports Before Upgrading to NX-OS Release 4.1(1b)" section of the Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 4.1(1b).
Before upgrading your SSI image, refer to the Cisco MDS NX-OS Release Compatibility Matrix for Storage Service Interface Images, and to Table 11 in the MDS 9000 Family Release Notes for NX-OS Release 4.1(1b). Use Table 11 to determine your nondisruptive upgrade path to Cisco MDS NX-OS Release 4.1(1b).
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.
Table 3 Open and Resolved Caveats for Cisco MDS SSI Release 4.1(1i)
DDTS Number Status
Symptom: A loss of IP connectivity between the DPC and both the SPs for more than 10 seconds causes the SSM to reboot. This is considered a symmetric failure and is considered disruptive for customers. On the other hand, an IP connectivity loss between the DPC and one of the SPs for more than 10 seconds causes the affected SP to reboot. This is considered an asymmetric failure and even though it involves an SP reboot, it is not considered disruptive.
Workaround: This issue is resolved.
Symptom: A DPP failure and an iSAPI failure are now treated as critical failures that cause SANTap to generate a core and reload the module.
Workaround: This issue is resolved.
Symptom: The show santap dpp all command shows the incorrect order for ports after the SSM module is set to l2 and then set to l3 and the data virtual target (DVT) is created using the dvt-port option.
Workaround: This issue is resolved.
Symptom: The show santap tech support command does not work when you make SANTap configuration changes.
Workaround: This issue is resolved.
Symptom: iSAPI unquiesce calls are not protected by a lock in the data path processor code in the MSM-18/4. Under a rare race condition, a list might become corrupted, which will cause the data path processor to fail. As a consequence, the module will reload.
The documentation set for the Cisco MDS 9000 Family includes the following documents. To find a document online, use the Cisco MDS NX-OS Documentation Locator at: http://www.cisco.com/en/US/docs/storage/san_switches/mds9000/roadmaps/doclocater.htm
•Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Releases
•Cisco MDS 9000 Family Release Notes for Storage Services Interface Images
•Cisco MDS 9000 Family Release Notes for Cisco MDS SVC Releases
•Cisco MDS 9000 Family Release Notes for Cisco MDS 9000 EPLD Images
•Cisco MDS 9000 NX-OS Hardware and Software Compatibility Information
•Cisco MDS 9000 Family Interoperability Support Matrix
•Cisco MDS Storage Services Module Interoperability Support Matrix
•Cisco MDS NX-OS Release Compatibility Matrix for IBM SAN Volume Controller Software for Cisco MDS 9000
•Cisco MDS NX-OS Release Compatibility Matrix for Storage Service Interface Images
Regulatory Compliance and Safety Information
•Regulatory Compliance and Safety Information for the Cisco MDS 9000 Family
•Cisco MDS 9124 Multilayer Fabric Switch Quick Start Guide
•Cisco MDS 9500 Series Hardware Installation Guide
•Cisco MDS 9200 Series Hardware Installation Guide
•Cisco MDS 9100 Series Hardware Installation Guide
•Cisco MDS 9020 Fabric Switch Hardware Installation Guide
Cisco Fabric Manager
•Cisco MDS 9000 Family Fabric Manager Quick Configuration Guide
•Cisco MDS 9000 Family Fabric Manager Configuration Guide
•Cisco MDS 9000 Fabric Manager Online Help
•Cisco MDS 9000 Fabric Manager Web Services Online Help
•Cisco MDS 9000 Family Fabric Manager Database Schema
•Cisco MDS 9000 Family Software Upgrade and Downgrade Guide
•Cisco MDS 9000 Family Storage Services Module Software Installation and Upgrade Guide
•Cisco MDS 9000 Family CLI Quick Configuration Guide
•Cisco MDS 9000 Family CLI Configuration Guide
•Cisco MDS 9000 Family Command Reference
•Cisco MDS 9000 Family Quick Command Reference
•Cisco MDS 9020 Fabric Switch Configuration Guide and Command Reference
•Cisco MDS 9000 Family SAN Volume Controller Configuration Guide
Intelligent Storage Networking Services Configuration Guides
•Cisco MDS 9000 Family Data Mobility Manager Configuration Guide
•Cisco MDS 9000 Family Storage Media Encryption Configuration Guide
•Cisco MDS 9000 Family Secure Erase Configuration Guide - For Cisco MDS 9500 and 9200 Series
Troubleshooting and Reference
•Cisco MDS 9000 Family Troubleshooting Guide
•Cisco MDS 9000 Family MIB Quick Reference
•Cisco MDS 9020 Fabric Switch MIB Quick Reference
•Cisco MDS 9000 Family SMI-S Programming Reference
•Cisco MDS 9000 Family System Messages Reference
•Cisco MDS 9020 Fabric Switch System Messages Reference
Installation and Configuration Note
•Cisco MDS 9000 Family SSM Configuration Note
•Cisco MDS 9000 Family Port Analyzer Adapter Installation and Configuration Note
•Cisco 10-Gigabit Fibre Channel X2 Transceiver Module Installation Note
Obtaining Documentation, Obtaining Support, and Security Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
CCDE, CCSI, CCENT, Cisco Eos, Cisco HealthPresence, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco Nurse Connect, Cisco Stackpower, Cisco StadiumVision, Cisco TelePresence, Cisco WebEx, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo 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. (0903R)
Copyright © 2009 Cisco Systems, Inc. All rights reserved.