Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.3(2) (OL-14116-10 C0, November 2008)

Send documentation comments to mdsfeedback-doc@cisco.com

Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.3(2)

OL-14116-10

Caveats

%SME_CPP-SLOT13-3-LOG_ERR_SME_ITL_CPP_ERR: Module:13 Host-Target IT Nexus

I:0xc1f3202015180006 T:0xc5a0202000010006 vsan:3000 oid:0x117 LunID:0x0000

This message is for debugging purposes and is also displayed during the upgrade of an MSM-18/4

module. An upgrade of the MSM-18/4 module where Cisco SME is enabled, is disruptive; however,

this syslog message does not indicate an issue.

Workaround: None.

• CSCsk43927

Symptom: The following Fabric Manager client components that use SSH and Telnet do not work

well with NAT:

• DMM storage job creation

• Cisco SAN-OS software upgrade

• Zone activation

Workaround: None.

• CSCsk90998

Symptom: The signal loss counters in the output of the show interface fcx/y command are not

incremented.

Workaround: None.

• CSCsm13002

Symptom: In rare cases, if a READ command issued by Cisco SME for media identification is

dropped or lost, the tape is marked as a clear-text tape. Subsequently, a CHECK_CONDITION with

ILI is returned when a READ is issued by the host. This can cause a backup application to mark the

tape as read-only.

Workaround: Unmount and remount the tape from the backup application to resolve this issue.

• CSCsm15874

Symptom: In rare cases, when Cisco SME attempts to perform a tape device discovery of the

backend tapes, a SCSI command can stall. This may cause Cisco SME to remain in the device

discovery phase.

Workaround: Reload the module.

• CSCsm17768

Symptom: There is a observable performance drop for backup and restore when Cisco SME is

introduced between a host and tape due to the increased latency.

Workaround: None.

• CSCsm18303

Symptom: In certain cases with the Tape Recycle policy enabled in Cisco SME, a new key is

generated when a tape is recycled and the old key is not purged.

Workaround: Manually purge the older version of the key.