Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c @ c i s c o . c o m Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.2(3) Release Date: December 18, 2007 Part Number: OL-14116-04 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 on page 35.
Introduction Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c @ c i s c o . c o m Introduction The Cisco MDS 9000 Family of Multilayer Directors and Fabric Switches provides industry-leading availability, scalability, security, and management, allowing you to deploy high performance storage-area networks with lowest total cost of ownership.
Components Supported Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c @ c i s c o . c o m Table 1 Cisco MDS 9000 Family Supported Software and Hardware Components (continued) Component Part Number Description Applicable Product License 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.
Components Supported Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c @ c i s c o . c o m Table 1 Cisco MDS 9000 Family Supported Software and Hardware Components (continued) Component Part Number Description Applicable Product Chassis DS-C9513 MDS 9513 director (13-slot modular chassis with 11 slots MDS 9513 Switch only for switching modules, and 2 slots reserved for Supervisor 2 modules only—SFPs1 sold separately).
Components Supported Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c @ c i s c o . c o m Table 1 Cisco MDS 9000 Family Supported Software and Hardware Components (continued) Component Part Number Description Applicable Product External crossbar module DS-13SLT-FAB1 MDS 9513 crossbar fabric module. MDS 9513 Switch only Supervisor modules DS-X9530-SF2-K9 MDS 9500 Supervisor-2, module. MDS 9500 Series only DS-X9530-SF1-K9 MDS 9500 Supervisor/Fabric-I module.
Components Supported Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c @ c i s c o . c o m Table 1 Cisco MDS 9000 Family Supported Software and Hardware Components (continued) Component Part Number Description Applicable Product 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.
Software Download Process Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c @ c i s c o . c o m Software Download Process Use the software download procedure to upgrade to a later version, or downgrade to an earlier version, of an operating system.
Software Download Process Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c @ c i s c o . c o m Note Refer to the “Determining Software Compatibility” section of the Cisco MDS 9000 Family CLI Configuration Guide for more details. Note If you would like to request a copy of the source code under the terms of either GPL or LGPL, please send an e-mail to mds-software-disclosure@cisco.com.
Software Download Process Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c @ c i s c o . c o m switch# show module Mod Ports Module-Type --- ----- -------------------------------... ... 5 0 Supervisor/Fabric-1 6 0 Supervisor/Fabric-1 Model Status ------------------ ------------ DS-X9530-SF1-K9 DS-X9530-SF1-K9 active* ha-standby For a Supervisor-2 module, the output might look like this: switch# show module Mod Ports Module-Type --- ----- -------------------------------.
Upgrading Your Cisco MDS SAN-OS Software Image Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c @ c i s c o . c o m Upgrading Your Cisco MDS SAN-OS Software Image This section lists the guidelines recommended for upgrading your Cisco MDS SAN-OS software image and contains the following sections: • Upgrading Your Version of Cisco Fabric Manager, page 10 • Upgrading with IVR Enabled, page 15 • Reconfiguring SSM Ports Before Upgrading to SAN-OS Release 3.
Upgrading Your Cisco MDS SAN-OS Software Image Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c @ c i s c o . c o m 2. • Cisco ACS 3.1 and 4.0 • PIX Firewall • IP Tables • SSH v2 • Global Enforce SNMP Privacy Encryption • HTTPS Ensure data migration when upgrading Cisco Fabric Manager from Cisco SAN-OS Releases 3.1(2b) and later. If you are upgrading Cisco Fabric Manager in Cisco SAN-OS Releases 3.
Upgrading Your Cisco MDS SAN-OS Software Image Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c @ c i s c o . c o m Step 3 Copy the Fabric Manager jar file m9000-fm-3.2.3.jar from the CD-ROM to a folder on the Solaris workstation. Step 4 Launch the installer using the following command: Step 5 Follow the onscreen instructions provided in the Fabric Manager management software setup wizard. java -Xms512m -Xmx512m -jar m9000-fm-3.2.3.
Upgrading Your Cisco MDS SAN-OS Software Image Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c @ c i s c o . c o m – Fibre Channel Ports: Traffic on Fibre Channel ports can be nondisruptively upgraded. See Table 5 for the nondisruptive upgrade path for all SAN-OS releases. – SSM: Intelligent services traffic on the SSM, such as SANTap, NASB, and FC write acceleration, is disrupted during an upgrade. SSM Fibre Channel traffic is not.
Upgrading Your Cisco MDS SAN-OS Software Image Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c @ c i s c o . c o m Table 5 Nondisruptive Upgrade Path to SAN-OS Release 3.2(3) (continued) Current Nondisruptive Upgrade Path SAN-OS 2.1(2) Upgrade to SAN-OS Release 2.1(2b) and then upgrade to Release 3.2(3). or Upgrade to SAN-OS Release 2.1(2d) and then upgrade to Release 3.2(3). or Upgrade to SAN-OS Release 2.1(2e) and then upgrade to Release 3.2(3).
Upgrading Your Cisco MDS SAN-OS Software Image Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c @ c i s c o . c o m Table 6 FICON Nondisruptive Upgrade Path to SAN-OS 3.2(3) Current Release with FICON Enabled Upgrade Path SAN-OS 2.0(2b) Use the interface shutdown command to administratively shut any Fibre Channel ports on Generation 1 modules that are in an operationally down state before nondisruptively upgrading from SAN-OS Release 2.0(2b) to SAN-OS Release 3.
Upgrading Your Cisco MDS SAN-OS Software Image Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c @ c i s c o . c o m Note Step 3 Complete Step 2 for all IVR enabled switches before moving to Step 3. Check the syslogs for any ISL that was isolated.
Upgrading Your Cisco MDS SAN-OS Software Image Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c @ c i s c o . c o m Reconfiguring SSM Ports Before Upgrading to SAN-OS Release 3.2(3) Starting with Cisco MDS SAN-OS Release 3.0(1), the SSM front panel ports can no longer be configured in auto mode, which is the default for releases prior to Release 3.0(1).
Upgrading Your Cisco MDS SAN-OS Software Image Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c @ c i s c o . c o m Step 4 Save the running configuration to the startup configuration before the upgrade procedure to ensure that the changes are preserved during and after the upgrade.
Upgrading Your Cisco MDS SAN-OS Software Image Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c @ c i s c o . c o m To work around an image upgrade failure caused by a lack of space on the bootflash, follow these steps: Step 1 Prior to installing the new image, copy the old (existing) system image file to an external server. You may need to reinstall this file later.
Downgrading Your Cisco MDS SAN-OS Software Image Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c @ c i s c o . c o m If you are performing an upgrade on one of those switches, you should follow the nondisruptive upgrade path shown in Table 5, even though the upgrade is disruptive. Following the nondisruptive upgrade path ensures that the binary startup configuration remains intact.
Downgrading Your Cisco MDS SAN-OS Software Image Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c @ c i s c o . c o m – IVR: With IVR enabled, you must follow additional steps if you are downgrading from Cisco SAN-OS Release 2.1.(1a), 2.1(1b), or 2.1.(2a). See the “Upgrading with IVR Enabled” section on page 15 for these instructions. – FICON: If you have FICON enabled, the downgrade path is different. See Table 8.
Downgrading Your Cisco MDS SAN-OS Software Image Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c @ c i s c o . c o m Table 7 Nondisruptive Downgrade Path from SAN-OS Release 3.2(3) To SAN-OS Release Nondisruptive Downgrade Path SAN-OS 2.0(2b) Downgrade to SAN-OS Release 2.1(2b) and then downgrade to Release 2.0(2b). SAN-OS 2.0(1b) Downgrade to SAN-OS Release 2.1(2b) and then downgrade to Release 2.0(1b). SAN-OS 1.x Downgrade to SAN-OS to Release 2.
New Features in Cisco MDS SAN-OS Release 3.2(3) Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c @ c i s c o . c o m – The EPLD version on the SSM is at 0x07 or higher. Use the show version module slot epld CLI command to determine your EPLD version. Refer to the Cisco MDS 9000 Family Release Notes for Cisco MDS 9000 EPLD Images to upgrade your EPLD image.
Caveats Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c @ c i s c o . c o m Caveats This section lists the open and resolved caveats for this release. Use Table 9 to determine the status of a particular caveat. In the table, “O” indicates an open caveat and “R” indicates a resolved caveat. Table 9 DDTS Number Open Caveats and Resolved Caveats Reference Software Release (Open or Resolved) 3.2(2c) 3.
Caveats Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c @ c i s c o . c o m Table 9 DDTS Number Open Caveats and Resolved Caveats Reference (continued) Software Release (Open or Resolved) 3.2(2c) 3.
Caveats Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c @ c i s c o . c o m Resolved Caveats • CSCsi62114 Symptom: An MDS 9513 switch running SAN-OS Release 3.1(2) my reload due to both Supervisors hitting a kernel within 6 seconds of each other. This does not occur when running SAN-OS Release 3.2(1a) or later. Workaround: This issue is resolved.
Caveats Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c @ c i s c o . c o m • CSCsl02669 Symptom: When an incorrect fabric identifier is assigned to a fabric during initial discovery, Performance Manager displays the wrong number of flows when fabrics are discovered at a later time. Workaround: This issue is resolved. • CSCsl41090 Symptom: During an upgrade from SANOS Release 3.0(x) (or lower) to Release 3.
Caveats Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c @ c i s c o . c o m • CSCsl51357 Symptom: The Device Manager Summary tab does not show multiple pWWNs that are on the NPV interface. Workaround: This issue is resolved. • CSCsl55450 Symptom: The Fabric Manager Server GUI displays "Finished searching the table. The search item not found." This occurrs when you select Inventoryand then Zones to display the Member column, then click the Find icon (binoculars).
Caveats Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c @ c i s c o . c o m • CSCsk49029 Symptom: If there is a request to export a domain while the same domain is being cleaned up, domain entries might not be programmed. As a result, communication between IVR devices might not occur. Workaround: Because the the programming request was lost, the only way to retrigger the programming is to withdraw the domain and refresh IVR. Follow these steps: 1.
Caveats Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c @ c i s c o . c o m • CSCsk54591 Symptom: In rare circumstances, if two or more catastrophic exceptions affecting the MDS arbiter occur in quick succession, it is possible that an MDS 9500 Series switch will completely reset. Workaround: None. • CSCsl39215 Symptom: The CIM server stops. This occurs after creating a subscription using the same filter and handler. Workaround: Reload the switch.
Caveats Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c @ c i s c o . c o m • CSCsg19303 Symptom: Graceful shutdowns of ISLs are not supported for IVR traffic. Workaround: Increase the FSPF cost on the link before it is shut down, so that traffic will flow through an alternate path. • CSCsi66310 Symptom: The management port on MDS switches supports one user-configured IPv6 address, but does not support autoconfiguration of an IPv6 address in Cisco SAN-OS Release 3.2(1).
Caveats Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c @ c i s c o . c o m • CSCsk49309 Symptom: IPv6 duplicate address detection (DAD) may not always works for the management port. Workaround: None. • CSCsk63929 Symptom: If DMM is provisioned on the SSM and you downgrade to a Cisco MDS SAN-OS release that does not support DMM, the configuration persists and the GUI and CLI show DMM as a provisioned application.
Caveats Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c @ c i s c o . c o m • CSCsl12130 Symptom: After a disruptive downgrade or upgrade between SAN-OS Release 3.2(2c) and Release 3.2(1a), issuing a no shutdown command on a Cisco SME interface fails. When issuing the install all command to perform the downgrade process, a warning is issued that indicates that the downgrade will be disruptive if Cisco SME is enabled.
Caveats Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c @ c i s c o . c o m • CSCsl65951 Symptom: Using Fabric Manager Release 3.2(2), an error is displayed in the creation wizard. This occurs when an enclosure spans multiple fabrics and not all fabrics are managed and when the Data Migration Wizard is used to create a job with that enclosure as the existing storage (selecting all ports listed in that enclosure).
Related Documentation Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c @ c i s c o . c o m Related Documentation The documentation set for the Cisco MDS 9000 Family includes the following documents.
Related Documentation Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c @ c i s c o .
Obtaining Documentation, Obtaining Support, and Security Guidelines Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c @ c i s c o .
Obtaining Documentation, Obtaining Support, and Security Guidelines Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c @ c i s c o . c o m Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.
