Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 2.1(2b) (OL-7411-04, September 2005)

Send documentation comments to [e-mail].
14
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 2.1(2b)
OL-7411-04
Caveats
Upon receiving this policy, the protocol and port numbers are ignored and only the IP addresses for
the IPSec policy are used. Thus, although iSCSI traffic is encrypted, non-iSCSI trafffic (such as
ICMP ping) sent by the Microsoft host in clear text will be dropped in the MDS port.
Workaround: None.
• CSCeh75500
Symptom: A device that interfaces with SANTap may request SANTap to create a session for an
ITL that was previously requested, and ITL checking is not robust.
Workaround: Have the device validate the ITL and ensure that it does not send a request for a
duplicate ITL.
• CSCeh88814
Symptom: When SANTap is unprovisioned, the control virtual target (CVT) object is not getting
cleaned up on the supervisor module.
Workaround: To ensure that cleanup occurs, the administrator should first issue the no santap
module slot-number appl-vsan vsan-id command to clean up the CVT, and then unprovision
SANTap.
• CSCei32317
Symptom: When configuring a remote SPAN (RSPAN), the Fibre Channel tunnel will not come up
if it goes through more than one hop.
Workaround: Configure the Fibre Channel tunnel explicit-path option and list every IP hop
between the source and destination.
• CSCei48889
Symptom: LTO-1 tape drives in certain tape libraries can not be used with NASB feature. When
multiple initiators (such as Backup Host and NASB engine) issue SCSI write commands, the tape
drives respond with a SCSI CHECK CONDITION with Sense - 0x03 and ASC/ASCQ = 0x3b/0x00.
They do not handle the transition from the host initiator to the NASB engine initiator. In general,
this is an issue for all NASB solutions with this tape drive and library combination.
Workaround: None.
• CSCei83322
Symptom: VPM does not start after an update to Cisco MDS SAN-OS Release 2.1(2) on the SSM
module. The module remains in a power cycled state.
Workaround: Power down all ASM and SSM modules on the switch and power them back. This
causes the VPM process to start. Issue the show processes | include vpm command to ensure the
process started.
• CSCin92870
Symptom: The Fabric Manager Server does not automatically handle a fabric merge and split. As a
result, you many see duplicate fabrics in the database and the web client.
Workaround: Close all fabrics from the Fabric Manager Server and then reopen the new fabric.
• CSCin95686
Symptom: The RRD graph in the Performance Manager does not refresh on a web client opened in
Mozilla or Netscape.
Workaround: Do not use a proxy server or use the browser’s Refresh button.
• CSCin95789