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 NX-OS Release 4.1(1b) Release Date: October 12, 2008 Part Number: OL-17675-02 I0 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 64.
Contents 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 Online History Change (continued) Revision Date Description D0 10/24/2008 Removed CSCsk49029, CSCsl31087, and CSCsl34922, which were resolved in SAN-OS 3.3(1c). Updated the “SANTap Enhancements” section. Updated the Software Component descriptions in Table 2. E0 10/27/2008 Added the “MDS 9000 Chassis and Module Support in Cisco MDS NX-OS 4.x”section.
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 .
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 .
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 .
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 .
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 2 Cisco MDS 9000 Family Supported Software and Hardware Components (continued) Component Part Number Description Applicable Product Dense WavelengthDivision Multiplexing (DWDM) DWDM-X2-xx.xx MDS 9500 Series DWDM X2 SC optics for 10-Gbps Fibre Channel connectivity to an existing Ethernet DWDM infrastructure, MDS 9200 Series with 15xx.xx nm wavelength, where xx.xx = 60.
Support for the New Generation 3 Modules 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 Support for the New Generation 3 Modules Cisco MDS NX-OS 4.1(1b) supports the following new Generation 3 8-Gbps modules: • MDS 9000 4/44-port 8-Gbps Host-Optimized Fibre Channel module (DS-X9248-48K9) • MDS 9000 24-port 8-Gbps Fibre Channel module (DS-X9224-96K9) • MDS 9000 48-port 8-Gbps Fibre Channel module (DS-X9248-96K9) In addition, Cisco MDS NX-OS 4.
MDS 9000 Chassis and Module Support in Cisco MDS NX-OS 4.x 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 Configuring Generation 3 and Generation 2 Switching Modules The Cisco MDS 9500 Multilayer Directors are designed to operate with any combination of Cisco MDS 9000 Generation 1, Generation 2, and Generation 3 modules.
MDS 9000 Chassis and Module Support in Cisco MDS NX-OS 4.x 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 Module Support Matrix for Cisco MDS NX-OS 4.
Migrating from Supervisor-1 Modules to Supervisor-2 Modules 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 Module Support Matrix for Cisco MDS SAN-OS 3.
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.
Upgrading Your Cisco MDS NX-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 Use the show module command to display the type of supervisor module in the switch. The following is sample output from the show module command on a Supervisor 2 module: switch# show module Mod Ports Module-Type --- ----- -------------------------------... ...
Upgrading Your Cisco MDS NX-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 When upgrading Fabric Manager, refer to the supported upgrade path shown in Table 10. For example, when upgrading from SAN-OS Release 3.1(x) to NX-OS Release 4.1, you will need to upgrade from Release 3.1(x) to Release 3.2(x) and then upgrade to NX-OS Release 4.1(1b) Table 10 Note Supported Fabric Manager Upgrade Paths Current Upgrade Path 3.0.x 3.
Upgrading Your Cisco MDS NX-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 NX-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-4.1.1b.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-4.1.1b.
Upgrading Your Cisco MDS NX-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 6 Caution Follow the onscreen instructions provided in the Fabric Manager Installer 3.3(1c). Windows 2000 is incompatible with Fabric Manager Release 4.1(1b). If you install Fabric Manager in a Windows 2000 environment, you are at risk of having an unstable Fabric Manager.
Upgrading Your Cisco MDS NX-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 – Gigabit Ethernet Ports: Traffic on Gigabit Ethernet ports is disrupted during an upgrade or downgrade. This includes IPS modules and the Gigabit Ethernet ports on the MPS-14/2 module, the MSM-18/4 module, and the MDS 9222i switch. Those nodes that are members of VSANs traversing an FCIP ISL are impacted, and a fabric reconfiguration occurs.
Upgrading Your Cisco MDS NX-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 11 Current Nondisruptive Upgrade Path to Cisco MDS NX-OS Release 4.1(1b) Nondisruptive Upgrade Path SAN-OS 3.3(1c) You can nondisruptively upgrade directly to NX-OS Release 4.1(1b) SAN-OS 3.3(1a) You can nondisruptively upgrade directly to NX-OS Release 4.1(1b) SAN-OS 3.2(3a) Upgrade to SAN-OS Release 3.3(1x) and then upgrade to NX-OS Release 4.
Upgrading Your Cisco MDS NX-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 11 Current Nondisruptive Upgrade Path to Cisco MDS NX-OS Release 4.1(1b) (continued) Nondisruptive Upgrade Path SAN-OS 2.1(1b) Upgrade to SAN-OS Release 2.1(2b), then upgrade to Release 3.3(1x). and then upgrade to NX-OS Release 4.1(1b) or Upgrade to SAN-OS Release 2.1(2d) then upgrade to Release 3.3(1x). and then to NX-OS Release 4.
Upgrading Your Cisco MDS NX-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 Use Table 12 to determine your FICON nondisruptive upgrade path to Cisco MDS NX-OS Release 4.1(1b) Find the image release number you are currently using in the Current Release with FICON Enabled column of the table and use the path recommended. Table 12 FICON Nondisruptive Upgrade Path to NX-OS Release 4.
Upgrading Your Cisco MDS NX-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 This issue was resolved in Cisco SAN-OS Release 2.1(2b); you must upgrade to Release 2.1(2b) before upgrading to Release 3.3(1c). An upgrade from Cisco SAN-OS Releases 2.1(1a), 2.1(1b), or 2.1(2a) to Release 2.
Upgrading Your Cisco MDS NX-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 NX-OS Release 4.1(1b) 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 NX-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 NX-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 .
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 – SSM: Intelligent services traffic on the SSM, such as SANTap, NASB, and FC write acceleration, is disrupted during a downgrade. SSM Fibre Channel traffic is not. – Gigabit Ethernet Ports: Traffic on Gigabit Ethernet ports is disrupted during a downgrade.
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 13 Nondisruptive Downgrade Path from NX-OS Release 4.1(1b) (continued) To SAN-OS Release Nondisruptive Downgrade Path SAN-OS 3.1(3a) Downgrade to SAN-OS Release 3.3(1a) or 3.3(1c) first and then downgrade to Release 3.1(3a). SAN-OS 3.1(2b) Downgrade to SAN-OS Release 3.3(1a) or 3.3(1c) first and then downgrade to Release 3.1(2b). SAN-OS 3.
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 13 Nondisruptive Downgrade Path from NX-OS Release 4.1(1b) (continued) To SAN-OS Release Nondisruptive Downgrade Path SAN-OS 2.0(1b) Downgrade to SAN-OS Release 3.3(1a) or 3.3(1c) first, then to Release 2.1(2x), then downgrade to Release 2.0(1b). SAN-OS 1.x Downgrade to SAN-OS Release 3.3(1a) or 3.
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 2. Enter the system health check bootflash command. The following example shows this command and its output: switch# system health check bootflash NOTE: This command can take over 30 minutes. Bootflash will be offline during th is time. Do you want to continue? (yes/no) [n] y Unmount successful. Checking bootflash ...
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 Although the switch indicates that the bootflash check takes 30 minutes, it typically completes in just a few seconds. Once the bootflash check is complete on both the active and the standby supervisors, proceed with the downgrade process. Note The system health check bootflash command is available starting in NX-OS 4.1(1b).
New Features in Cisco MDS NX-OS Release 4.1(1b) 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 New Features in Cisco MDS NX-OS Release 4.1(1b) This section briefly describes the new features introduced in this release. For detailed information about the features listed, refer to the Cisco MDS 9000 Family CLI Configuration Guide, Release 3.
New Features in Cisco MDS NX-OS Release 4.1(1b) 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 24-port 8-Gbps Fibre Channel Switching Module The 24-Port 8-Gbps Fibre Channel switching module offers 24 autosensing 4- and 8-Gbps Fibre Channel ports and can be used in the Cisco MDS 9500 Series Switches. The 24-port switching module can be configured in one of two operational modes: shared bandwidth mode (default) and dedicated bandwidth mode.
New Features in Cisco MDS NX-OS Release 4.1(1b) 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 SANTap protocol allows appliances to get an I/O copy for data replication, continuous data protection, and data migration without affecting the integrity, availability, and performance of the primary I/O between servers and storage.
New Features in Cisco MDS NX-OS Release 4.1(1b) 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 Data Mobility Manager Enhancements Cisco Data Mobility Manger (DMM) is a SAN-based, intelligent fabric application offering data migration between heterogeneous disk arrays. Cisco DMM offers rate-adjusted online migration to enable applications to continue uninterrupted while data migration is in progress. Beginning with NX-0S Release 4.
New Features in Cisco MDS NX-OS Release 4.1(1b) 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 Fabric Manager Release 4.1(1b) New Features Cisco Fabric Manager Release 4.1(1b) includes the following new features and enhancements: • Server Admin Tool, page 38 • Flow Management Simplification, page 38 • Web Client Enhancements, page 38 • Supported Platforms for Fabric Manager, page 39 Server Admin Tool In Cisco NX-OS Release 4.
New Features in Cisco MDS NX-OS Release 4.1(1b) 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 message when a user attempts to open the Performance tab if Performance Manager is running and all switches are not licensed for FMS. A link is provided to a report listing the licensing state of the switches, to make it easy to determine which switches are not compliant with the licensing policy.
Licensed Cisco NX-OS Software Packages 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 Licensed Cisco NX-OS Software Packages Most Cisco MDS 9000 family software features are included in the base configuration of the switch: the standard package.
Licensed Cisco NX-OS Software Packages 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 Storage Services Enabler Package The Cisco MDS 9000 SSE package allows network-based storage applications and services to run on the Cisco MDS 9000 family SSMs, Cisco MSM-18/4 Port Multiservice Module, and Cisco MDS 9222i.
Limitations and Restrictions 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 Limitations and Restrictions This section lists the limitations and restrictions for this release.
Limitations and Restrictions 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 Red Hat Enterprise Linux The Linux kernel core dump is not supported in NX-OS Release 4.1(1b) and later versions and therefore the CLI command has been removed. A syntax error message will be displayed if you import configurations from SAN-OS Release 3.3(x) and earlier to NX-OS Release 4.1(1b) and later.
Limitations and Restrictions 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 6 Restart Fabric Manager Server. Maximum Number of Zones Supported in Interop Mode 4 In interop mode 4, the maximum number of zones that is supported in an active zone set is 2047, due to limitations in the connected vendor switch. When IVR is used in interop mode 4, the maximum number of zones supported, including IVR zones, in the active zone set is 2047.
Limitations and Restrictions 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 SME Configuration Limits Table 15 lists the Cisco SME configuration limits for this release.
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 16 to determine the status of a particular caveat. In the table, “O” indicates an open caveat and “R” indicates a resolved caveat. Table 16 DDTS Number Open Caveats and Resolved Caveats Reference SAN-OS Software Release (Open NX-OS Software Release (Open or Resolved) or Resolved) 3.3(1c) 4.
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 16 DDTS Number Open Caveats and Resolved Caveats Reference (continued) SAN-OS Software Release (Open NX-OS Software Release (Open or Resolved) or Resolved) 3.3(1c) 4.
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 16 DDTS Number Open Caveats and Resolved Caveats Reference (continued) SAN-OS Software Release (Open NX-OS Software Release (Open or Resolved) or Resolved) 3.3(1c) 4.
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 • CSCsu80534 Symptom: An MDS 9124 switch, MDS 9134 switch, MDS 9222i switch, Cisco Fabric Switch for IBM BladeCenter, or Cisco Fabric Switch for HP c-Class BladeSystem, may reboot with reason Unknown or Watchdog Timeout when the switch has been up for 497 days.
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 • CSCso36760 Symptom: In Fabric Manager Release 3.3(x), zone set cloning returns an autoZoneEditing error. The option to clone a zone is missing. Workaround: This issue is resolved. • CSCso41087 Symptom: If FCIP is enabled and the SAN-OS is upgraded, the SNMP service will run into exception and the following syslog message is displayed: SNMP Operation(165) failed (62) setting error index.
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 • CSCsr59106 Symptom: Performance decreases on low-bandwidth interfaces. This issue affects only the MDS 18/4 module and the MDS 9222i switch. Workaround: This issue is resolved. • CSCsr62565 Symptom: When performing a query on ni/ei cisco_zonemembersettingdata, the Common Information Model (CIM) server crashes 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 • CSCse31881 Symptom: If there are IP over Fibre Channel (IPFC) interfaces configured on an SSM, you might experience issues if you downgrade from SAN-OS Release 3.x to Release 2.x. Workaround: This issue is resolved. • CSCsg19303 Symptom: Graceful shutdowns of ISLs are not supported for IVR traffic. 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 • 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). 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 • CSCso63465 Symptom: FCP-CMD (for example, Inquiry) frames targeted to LUN 0x45F0 or LUN 0x50F0 are dropped by an MDS switch when traffic flows (egresses) through Generation 2 modules. LUN 0x45F0 corresponds to HPUX's Volume Set Address . Workaround: This issue is resolved. • CSCso66705 Symptom: The FCNS process may fail and dump a core.
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 • CSCsq66823 Symptom: On an MDS 9222i switch, an upgrade from SAN-OS Release 3.2(x), Release 3.3(1), or Release 3.3(1a) to SAN-OS Release 3.3(1c) fails when there is an active FC-Redirect configuration (created by SME or DMM applications) on the switch. An active FC-Redirect configuration is defined as: • FC-Redirect configuration for hosts or targets connected locally.
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 • CSCsr28197 Symptom: The error messages for Device-Alias Merge do not provide information to be able to identify offending Device-Aliases or PWWNs associated with the merge failures. Workaround: This issue is resolved. • CSCsr28302 Symptom: DPVM merge failure messages to not indicate why the merge failed. 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 • CSCsr59290 Symptom: Splitter errors occur on a first Control Virtual Target (CVT), when a second CVT is created on the same SSM module. This occurs when a second CVT is created on the same Data Path Processor (DPP) as that of the first one. This also occurs when the DVT and the RP appliance target ports use the same front panel ports as the DPP. 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 Workaround: This issue is resolved. • CSCsi56167 Symptom: The response time shown in the output of a ping ip-address command may not be accurate if there is an MDS MSM-18/4 in the path. 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 • CSCsr42622 Symptom: When performing an IBM Tivoli Storage Manager (TSM) or Veritas NetBackup database backup (for example, a TSM/NetBackup catalog backup), which requires a separate tape cartridge from the scratch pool (other than regular backup tapes), the backup fails with excessive I/O errors. When using SAN-OS Release 3.3(1a), and SSI Release 3.3(1a), and IBM Tivoli Storage Manager 5.
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 Open Caveats • CSCsk11207 Symptom: Using Fabric Manager Web Client, you download Fabric Manager Client and when prompted to create a desktop shortcut, you select Yes. The default shortcut named “Cisco Fabric Manager” is created on the desktop.
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 • CSCsk35725 Symptom: Fabric Manager takes 2 to 3 minutes to bring up the DMM job creation wizard in a setup with 25 switches, 400 enclosures, and 2400 entries in the name server. Workaround: None. • CSCsk49309 Symptom: IPv6 duplicate address detection (DAD) may not always works for the management port. Workaround: None.
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 • CSCsu53299 Symptom: When reloading a switch, a timing condition may cause CFS to enter the handshake before the Routing Information Base (RIB) does. In this instance, CFS will not see any peers, and as a result, CFS-based applications will not communicate with the rest of the fabric. Workaround: Re-initialize CFS by issuing the following commands.
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 • CSCsu88059 Symptom: After first installing Fabric Manager Server (FMS) (with default flag displayFCoE = false), and then stopping and restarting the FMS with displayFCoE = true, the FCoE interface tables are not showing when the old disconnected client re-connects.
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. To find a document online, use the Cisco MDS SAN-OS Documentation Locator at: http://www.cisco.com/en/US/products/ps5989/products_documentation_roadmap09186a00804500c1.html.
Obtaining Documentation and Submitting a Service Request 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 and Submitting a Service Request 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 Subscribe to the What’s New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0. Cisco.com You can access the most current Cisco documentation at this URL: http://www.
