Cisco AP776A - Nexus Converged Network Switch 5020 Catatan Rilis - Halaman 29

Jelajahi secara online atau unduh pdf Catatan Rilis untuk Beralih Cisco AP776A - Nexus Converged Network Switch 5020. Cisco AP776A - Nexus Converged Network Switch 5020 44 halaman. Cisco nexus 5000 series release notes release 4.1(3)n1(1) (ol-16601-01 h0, july 2009)
Juga untuk Cisco AP776A - Nexus Converged Network Switch 5020: Catatan Rilis (48 halaman), Catatan Rilis (26 halaman), Catatan Rilis (22 halaman), Panduan Referensi Cepat (14 halaman), Catatan Rilis (3 halaman), Catatan Rilis (26 halaman)

Cisco AP776A - Nexus Converged Network Switch 5020 Catatan Rilis
S e 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 c k - 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.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(3).
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(3) 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(3), 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.
These default settings are applied when a VSAN is created. However, the settings will not take effect on
VSAN 1, because it exists prior to running the setup script. Therefore, when you need these settings for
VSAN 1, you must explicitly issue the following commands:
OL-14116-11
zone default-zone permit vsan 1
zoneset distribute full vsan 1
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.3(3)
Limitations and Restrictions
29