Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.1(2a) (OL-12208-03, February 2007)
Send documentation comments to mdsfeedback-doc@cisco.com
20
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.1(2a)
OL-12208-03
New Features in Cisco MDS SAN-OS Release 3.1(2a)
• Downgrade the SSI boot images on the SSMs on the switch to a release version supported by your
Cisco SAN-OS release. Refer to the Cisco MDS SAN-OS Release Compatibility Matrix for Storage
Service Interface Images.
• SSM intelligent services traffic switching on SSM ports is disrupted on upgrades or downgrades.
• Fibre Channel switching traffic on SSM ports is not disrupted under the following conditions:
–
All SSM applications are disabled. Use the show ssm provisioning CLI command to determine
if any applications are provisioned on the SSM. Use the no ssm enable feature configuration
mode CLI command to disable these features.
–
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.
–
Refer to the Cisco MDS Storage Services Module Interoperability Support Matrix and to the
“Managing Modules” chapter in the Cisco MDS 9000 Family CLI Configuration Guide,
Release 3.x for information on downgrading your SSM.
New Features in Cisco MDS SAN-OS Release 3.1(2a)
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 and the Cisco MDS
9000 Family Fabric Manager Configuration Guide.
Note These release notes are specific to this release. For the complete Release 3.x documentation set, see the
“Related Documentation” section on page 25.
There are no new features in Cisco MDS SAN-OS Release 3.1(2a).
Limitations and Restrictions
This section lists the limitations and restrictions for this release.
Using SAN Device Virtualization on Cisco Fabric Switches
There must be at least one SAN device virtualization-enabled switch that is not a Cisco MDS 9124
switch, a Cisco Fabric Switch for HP c-Class BladeSystem, or a Cisco Fabric Switch for IBM
BladeCenter between the server and the target that are being virtualized. In other words, SAN device
virtualization does not work when initiators and primary targets are connected to the same Cisco MDS
9124 Switch or Cisco Fabric Switch for HP c-Class BladeSystem or Cisco Fabric Switch for IBM
BladeCenter.
Interface Names on Cisco Fabric Switches and Interface Based Zoning
The Cisco Fabric Switch for HP c-Class BladeSystem and the Cisco Fabric Switch for IBM BladeCenter
use different Fibre Channel interface names than those used on MDS 9000 Family switches. Interface
names are used in many operations, including domain interface zoning.