Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.3(4) (OL-14116-12, July 2009)

Send documentation comments to [e-mail]
28
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.3(4)
OL-14116-12
Limitations and Restrictions
Deleting Cisco SME Interfaces
A Cisco SME interface can be deleted from the cluster only after the interface is administratively
shut-down and all related tasks associated with the interface shut-down are complete.
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.2(x) to Release 3.3(1c) is not supported
if there is a Cisco SME or Cisco DMM configuration in the fabric for hosts and targets attached to the
MDS 9222i module.
SANTap
The SANTap feature allows third party data storage applications, such as long distance replication and
continuous backup, to be integrated into the SAN. SANTap is not supported in Release 3.3(4).
Deleting SANTap Configurations Is Required Before Downgrade
If you are running Cisco MDS NX-OS Release 4.1(1b) in combination with the SSI 4.1(1b) image and
you wish to downgrade to Cisco SAN-OS Release 3.3(4) and an SSI 3.2(3*) image, you must delete all
SANTap configurations prior to the downgrade. Downgrading without completely deleting the SANTap
configurations is not supported.
FCIP Interoperability
FCIP interoperability fails between two MDS switches, one running MDS NX-OS Release 4.1(1c) and
the other running MDS SAN-OS Release 3.3(4), if the IP ACL configuration for an IPSec crypto map
specifies TCP as the protocol, as in the following example:
switch(config)# ip access-list acl-name permit tcp local-gige-ip-address local-mask
remote-gige-ipaddress remote-mask
FCIP interoperability does not fail if the IP ACL uses IP as the protocol, as in the following example:
switch(config)# ip access-list acl-name permit ip local-gige-ip-address local-mask
remote-gige-ipaddress remote-mask
Applying Zone Configurations to VSAN 1
In the setup script, you can configure system default values for the default-zone to be permit or deny,
and you can configure default values for the zone distribution method and for the zone mode.