Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.3(4) (OL-14116-12, July 2009)
Table Of Contents
- Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.3(4)
- Contents
- Introduction
- Components Supported
- Software Download Process
- Determining the Software Version
- Downloading Software
- Selecting the Correct Software Image for an MDS 9100 Series Switch
- Selecting the Correct Software Image for an MDS 9200 Series Switch
- Selecting the Correct Software Image for an MDS 9500 Series Switch
- Migrating from Supervisor-1 Modules to Supervisor-2 Modules
- Configuring Generation 2 Switching Modules
- Upgrading Your Cisco MDS SAN-OS Software Image
- Upgrading Your Version of Cisco Fabric Manager
- General Upgrading Guidelines
- FICON Supported Releases and Upgrade Paths
- Upgrading with IVR Enabled
- Reconfiguring SSM Ports Before Upgrading to SAN-OS Release 3.3(4)
- Upgrading the SSI Image on Your SSM
- Upgrading a Switch with Insufficient Space for Two Images on the Bootflash
- Upgrading a Cisco MDS 9124 Switch
- Performing a Disruptive Upgrade on a Single Supervisor MDS Family Switch
- Upgrading an MDS 9222i Switch
- Downgrading Your Cisco MDS SAN-OS Software Image
- New Features in Cisco MDS SAN-OS Release 3.3(4)
- Limitations and Restrictions
- Upgrading to Recover Loss of Performance Manager Data
- Maximum Number of Zones Supported in Interop Mode 4
- Upgrading the SAN-OS Software on the MDS 9222i Switch
- Java Web Start
- Cisco Storage Media Encryption
- Cisco MDS 9222i Module Upgrade
- SANTap
- Deleting SANTap Configurations Is Required Before Downgrade
- FCIP Interoperability
- Applying Zone Configurations to VSAN 1
- Running Storage Applications on the MSM-18/4
- Compatibility of Fabric Manager and Data Mobility Manager
- A Supervisor-2 Module Might Reset in Switches Running SAN-OS Release 3.2(x)
- Limited ISSU Support on the MDS 9222i Switch
- Caveats
- Related Documentation
- Obtaining Documentation and Submitting a Service Request
Send documentation comments to mdsfeedback-doc@cisco.com
35
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.3(4)
OL-14116-12
Caveats
• CSCso83333
Symptom: System utilization might be incorrectly displayed after the active supervisor is up for
about 497 days. This is a cosmetic issue and there is no functional impact because of this.
Workaround: This issue is resolved.
• CSCsw87910
Symptom: When running Cisco MDS Release SAN-OS 3.3(2) with DPVM enabled, if a link flaps
for a end device with DPVM enabled, you might see the following message in the output of the show
logging log command:
%DPVM-3-PSS_ERR: Failed to update Login info NPV contextpwwn:
50:00:00:00:aa:99:ee:44, syserr = no such pss key
Workaround: This issue is resolved.
• CSCta32005
Symptom: Upon receiving an OLS when a link went down, the OLS counter was not incremented.
Workaround: This issue is resolved.
• CSCsz22811
Symptom: Compression throughput on the MSM-18/4 module has been improved.
Workaround: This issue is resolved.
Open Caveats
• CSCsr85709
Symptom: Under certain conditions, the port manager can take a long time to respond to a port
configuration, which can trigger a set-port-configuration failure. If this occurs, then the FCIP tunnel
will not come up and will stay in a disabled state.
Workaround: Enter a shut command, followed by a no shut command on the FCIP interface at
either end of the FCIP tunnel.
• 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.
• CSCso49196
Symptom: During an upgrade from SAN-OS Release 3.2(3a) to Release 3.3(1a), when a switchover
occurs to the Supervisor running Release 3.3(1a), Cisco SME traffic flows for hosts that are not
connected locally to the switch that is getting upgraded, may get flapped for a very short time. This
can also occur during a switchover to a Supervisor running Release 3.3(1a).
Workaround: None.
• CSCsq20408
Symptom: After creating SANTap Control Virtual Targets (CVTs) or SANTap Data Virtual Targets
(DVTs), the running-configuration and the startup-configuration are not synchronized. Output from
the show startup-config command will be different from the output of the show running-config
and the startup configuration will not display SANTap configuration information.