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.3(2) Release Date: November 11, 2008 Part Number: OL-14116-10 C0 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 56.
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 • Downgrading Your Cisco MDS SAN-OS Software Image, page 23 • New Features in Cisco MDS SAN-OS Release 3.
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 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.
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 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 2 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 2 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 2 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 11 • Upgrading with IVR Enabled, page 18 • 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 Upgrading from Release 3.1(2c) with the PostgreSQL Patch To upgrade Fabric Manager to Release 3.3(2) from the UBS special version of 3.1.2c with the PostgreSQL patch, do the following: Step 1 Upgrade Fabric Manager to Release 3.2(1b), pointing to the same PostgreSQL database which was used by Release 3.1.2c.
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. 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.1(2b) and later, be aware that data is migrated from the Hypersonic HSQL database to either the PostgreSQL database or Oracle Database 10g Express during the installation.
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 Installing Fabric Manager on Windows This section describes how to install Fabric Manager on Windows. Note Fabric Manager Server can not be installed on an Active Directory Server when using PostgreSQL, Fabric Manager servers are domain controllers and can not create local PostgreSQL user accounts.
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 Note Follow the onscreen instructions to complete the installation of Device Manager. If you use a Java JDK instead of a JRE on Solaris, you might encounter a problem trying to install the Device Manager from a web browser. This can happen because the installer heap limit of 256 MB is not sufficient.
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 • FC-Redirect configuration for hosts or target connected locally • FC-Redirect configuration created by application running on that switch. If an upgrade is attempted when an active configurations is present, the switch will go into a disruptive upgrade. Note The software upgrade information in Table 7 applies only to Fibre Channel switching traffic.
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 7 Nondisruptive Upgrade Path to SAN-OS Release 3.3(2) (continued) Current Nondisruptive Upgrade Path SAN-OS 2.1(1b) Upgrade to SAN-OS Release 2.1(2b) and then upgrade to Release 3.3(2). or Upgrade to SAN-OS Release 2.1(2d) and then upgrade to Release 3.3(2). or Upgrade to SAN-OS Release 2.1(2e) and then upgrade to Release 3.3(2).
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 8 FICON Nondisruptive Upgrade Path to SAN-OS 3.3(2) 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.3(2) 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 .
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 – Gigabit Ethernet Ports: Traffic on Gigabit Ethernet ports is disrupted during a 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.
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 9 Nondisruptive Downgrade Path from SAN-OS Release 3.3(2) To SAN-OS Release Nondisruptive Downgrade Path SAN-OS 2.1(2d) You can nondisruptively downgrade directly from SAN-OS Release 3.3(2). SAN-OS 2.1(2b) You can nondisruptively downgrade directly from SAN-OS Release 3.3(2). SAN-OS 2.1(2) Downgrade to SAN-OS Release 2.
New Features in Cisco MDS SAN-OS Release 3.3(2) 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 Downgrading the SSI Image on Your SSM Use the following guidelines when downgrading your SSI image on your SSM. • On a system with at least one SSM installed, the install all command might fail on an SSM when you downgrade from Cisco SAN-OS Release 3.3(2) to any SAN-OS 2.x release earlier than SAN-OS Release 2.1(2e).
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. Upgrading to Recover Loss of Performance Manager Data Warning You must upgrade to Fabric Manager Release 3.1(x) and then upgrade to a later release of Fabric Manager to avoid losing Performance Manager data. If data has been lost, follow the steps below to recover the data.
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 Java Web Start When using Java Web Start, it is recommended that you do not use an HTML cache or proxy server. You can use the Java Web Start Preferences panel to view or edit the proxy configuration. To do this, launch the Application Manager, either by clicking the desktop icon (Microsoft Windows), or type .
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 Emulex Driver Version In some instances, the Emulex driver version 8.1.10.9 may set the task attribute to HEAD_OF_QUEUE instead of SIMPLE_QUEUE. Certain tape drives do not accept this attribute and may reject these commands. The Emulex driver version 8.1.10.12 does not have this issue. Cisco MDS 9222i Module Upgrade On the MDS 9222i module, an upgrade from SAN-OS 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 Table 12 Open Caveats and Resolved Caveats Reference (continued) Software Release (Open or Resolved) Software Release (Open or Resolved) 3.3(1c) 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 12 Open Caveats and Resolved Caveats Reference (continued) Software Release (Open or Resolved) Software Release (Open or Resolved) 3.3(1c) 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 12 Open Caveats and Resolved Caveats Reference (continued) Software Release (Open or Resolved) Software Release (Open or Resolved) 3.3(1c) 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 12 Open Caveats and Resolved Caveats Reference (continued) Software Release (Open or Resolved) Software Release (Open or Resolved) 3.3(1c) 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 switch# show system reset-reason --- reset reason for Supervisor-module 1 (from Supervisor in slot 1) --1) No time Reason: Unknown Service: Version: 3.1(2) or switch# show system reset-reason ----- reset reason for Supervisor-module 1 (from Supervisor in slot 1) --1) At 203437 usecs after Fri Jul 4 18:32:02 2008 Reason: Watchdog Timeout Service: Version: 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 • CSCsq25023 Symptom: In rare instances, when the host-side exchange and the target-side exchange map to the same internal hash index, a port software failure due to a watchdog timeout may occur. This issue occurs with a lot of traffic flows through the same SME engine. 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. • CSCsm39302 Symptom: There is a decrease in the FCIP tunnel throughput when IPSec is configured. Workaround: This issue is resolved. • CSCsm90294 Symptom: Certain XSS and XSRF vulnerabilities were found in the Fabric Manager web client. Workaround: This issue is resolved. • CSCso65297 Symptom: Though the INTEGER is defined as (-2147483648..
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 2) At 347955 usecs after Tue May Reason: Watchdog Timeout Service: Version: 3.2(2c) 3) At 110808 usecs after Tue May Reason: Watchdog Timeout Service: Version: 3.2(2c) 4) At 756666 usecs after Tue May Reason: Watchdog Timeout Service: Version: 3.2(2c) 6 01:18:48 2008 6 01:16:13 2008 6 01:13:39 2008 Workaround: This issue is resolved. • CSCsq17989 Symptom: During an upgrade for 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 Workaround: This issue is resolved. • CSCsq27248 Symptom: If some database processes are shut down uncleanly (for example, the host crashes or a process is killed) the following message may be seen: com.cisco.dcbu.lib.rrd.core.RrdException: Bad sample timestamp 1210312407.
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 port-wwn (vendor) :50:01:10:a0:00:16:d0:f6 [HOSBILLYGIRL] node-wwn :50:01:10:a0:00:16:d0:f7 class :3 node-ip-addr :0.0.0.0 ipa :ff ff ff ff ff ff ff ff fc4-types:fc4_features :scsi-fcp:init symbolic-port-name : symbolic-node-name :HPAE311A FW:v4.00.23 DVR:v9.1.3.16 port-type :N port-ip-addr :0.0.0.
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 • CSCsu56780 Symptom: A Solaris iSCSI host generates this error: iscsi: [ID 498442 kern.warning] WARNING: iscsi session(5) protocol error - received unknown itt:0x0 - protocol error. Workaround:This issue is resolved • CSCsu90793 Symptom: Software failures occurred on a Gigabit Ethernet port when FCIP compression mode auto was used. 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 • CSCsr49954 Symptom: The Recoverpoint Appliance with a QLogic HBA sends an 8 byte RFT_ID instead of the standard 32bytes, which causes FC4 features to be incorrectly registered with all features. 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. • CSCsq69543 Symptom: Fabric Manager does not update Port Channel changes. 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. • CSCsr59106 Symptom: For two FCIP links on different modules but sharing a common DS3 pipe, the MDS switch could not saturate the DS3 pipe. In another setup with no latency and min/max-bw configured to 15mbps, the MDS FCIP shaper does not obey bandwidth rules and sends at a rate greater than 15mbps, which caused unnecessary drops in the network.
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 • CSCsu48426 Symptom: For a data stream that has a lot of variance in the compression ratio across individual tape blocks on the tape, SME restore performance for the HP LTO drives is substantially affected. However, backup performance is not affected. Workaround: This issue is resolved. • CSCsu68490 Symptom: A downgrade from NX-OS 4.1(1b) to SAN-OS 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 Workaround: Bring up multiple links between two switches one at a time. Verify that the first link came up correctly before attempting to bring up the next link. If the first link fails to come up because of a domain ID overlap, resolve the domain conflict and then try again to bring up the links.
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 • CSCsk51193 Symptom: Following an upgrade to Cisco MDS SAN-OS Release 3.2(1) on a Cisco MDS 9124 switch, an interface is shown as up, but there is no FLOGI information for the port in the FLOGI database. Workaround: Set the port mode to F. • CSCsl32492 Symptom: Certain drivers cache the PRLI service parameters negotiated across the PLOGI/PRLI session establishment.
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 • 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. Workaround: Disable FCIP during the SAN-OS upgrade. • CSCsq29607 Symptom: After logging back into Fabric Manager Client, clicking on the Summary tab causes a disconnect.
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 • CSCse47687 Symptom: If IP ACLs are applied to any IP Storage Gigabit Ethernet port, implicit deny does not take effect. Workaround: Configure explicit deny on the port. • CSCsg19148 Symptom: Time zone changes that are executed on an MDS switch do not take effect on the 12-port, 24-port, and 48 port 1-Gbps/2-Gbps/4-Gbps Fibre Channel modules, and on the 4-port 10-Gbps module.
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: None. • CSCsk35951 Symptom: In a configuration with a PortChannel with FCIP members and write acceleration in use, if IVR NAT is enabled on one end of the PortChannel and not enabled on the other end, then traffic over the FCIP tunnel might fail. Workaround: Enable IVR NAT on both ends of the PortChannel or disable it on both ends.
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 • CSCsk95241 Symptom: If you use JDK instead of JRE on Solaris, you might encounter a problem trying to install Device Manager from a web browser. This can happen because the installer heap limit of 256 MB is not sufficient. Workaround: If you have this problem, save the jnlp link as file, increase the heap limit to 512 MB, and run javaws element-manager.jnlp at the shell prompt.
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 • CSCsl42571 Symptom: SNMP timeouts occur when a AAA user ages out. By design, a AAA user is aged out every hour on a switch for security reasons. If a large fabric is discovered using a AAA user and a Performance Monitoring (PM) collection is added for such a fabric, a number of SNMP requests (related to the discovery or PM statistics collection) could time out.
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 • CSCsm54071 Symptom: Data Virtual Targets (DVTs) are lost after a downgrade from Release 3.3(1x) to earlier releases. Workaround: None. • CSCsm63010 Symptom: In SAN-OS Release 3.2(3a) or earlier, Cisco DMM did not include Method1 and Method2 DMM jobs. In those releases, stored configurations were treated implicitly as Method1 DMM jobs. Configurations now stored by SAN-OS 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 Note This applies only to Terminal Server running in Application Mode. This issue does not affect users running a Terminal Server or Remote Desktop session in Remote Administration mode. Workaround: Before you install Fabric Manager, Fabric Manager Server, and Device Manager when using Microsoft Terminal Server in Application mode, you must install the application for global use.
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: Exit all Fabric Manager clients and rename the map layout files by replacing space characters with an underscore. The map layout files are found on the computer running the Fabric Manager server. Each Fabric Manager user has their own directory of map files. These map files are found in the following directory: C:\Program Files\Cisco Systems\MDS 9000\db\\*.map.
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 %SME_CPP-SLOT13-3-LOG_ERR_SME_ITL_CPP_ERR: Module:13 Host-Target IT Nexus I:0xc1f3202015180006 T:0xc5a0202000010006 vsan:3000 oid:0x117 LunID:0x0000. This message is for debugging purposes and is also displayed during the upgrade of an MSM-18/4 module. An upgrade of the MSM-18/4 module where Cisco SME is enabled, is disruptive; however, this syslog message does not indicate an issue.
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 Cisco.com You can access the most current Cisco documentation at this URL: http://www.cisco.com/techsupport You can access the Cisco website at this URL: http://www.cisco.com You can access MDS SAN-OS documentation at this URL: http://www.cisco.com/en/US/products/ps5989/tsd_products_support_series_home.
