Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.2(3) (OL14116-04, December 2007)

Send documentation comments to [e-mail]
32
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.2(3)
OL-14116-04
Caveats
• CSCsk49309
Symptom: IPv6 duplicate address detection (DAD) may not always works for the management port.
Workaround: None.
• CSCsk63929
Symptom: If DMM is provisioned on the SSM and you downgrade to a Cisco MDS SAN-OS release
that does not support DMM, the configuration persists and the GUI and CLI show DMM as a
provisioned application.
Workaround: Manually remove the DMM configuration from the switch before downgrading to a
Cisco MDS SAN-OS release that does not support DMM, such as downgrading from SAN-OS
Release 3.2(1) to SAN-OS Release 3.1(3). If you forget to remove the configuration before the
downgrade, power off the module and purge the configuration on the SSM module by entering the
following commands:
switch(config)# poweroff module slot
switch# purge module slot running-config
• CSCsk87502
Symptom: If an NASB configuration in a VSAN is destroyed while a target discovery is pending,
the NASB process fails. Issue the show nasb vsan x command on the SSM to view the target
discovery in the Pending state.
Workaround: Reload the SSM.
• CSCsk87614
Symptom: When NASB is enabled in a VSAN, all targets that are visible in that VSAN are
discovered by NASB. If a new target is added to the VSAN, NASB does not automatically discover
the new target.
Workaround: To discover the new target, reload the SSM or disable and re-enable NASB in the
VSAN.
• CSCsk93834
Symptom: In rare situations during a storage-based online data migration job, the user might not be
able to destroy the job if the following sequence of events occurs:
1. A storage-based data migration job is executing.
2. A port flap occurs on the server and the server HBA port goes down.
3. The storage-based data migration job continues executing until it completes.
4. The user issues the dmm module module-id job job-id destroy command to delete the
storage-based data migration job, but the delete fails.
Workaround: Reload the SSM.
• 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.