Cisco Cisco MDS 9000 NX-OS Software Release 4.1 Notas de publicación
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 o m .
47
Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 4.1(3)
OL-17675-03
Caveats
•
CSCsw95386
Symptom: Certain applications that use SME perform a move medium operation to change tapes
in a library, without first performing a load or unload operation. This causes the check condition
“SCSI check condition of medium may have changed.” SME does not perform the media
identification logic correctly for this check condition, which causes tape labeling to fail.
in a library, without first performing a load or unload operation. This causes the check condition
“SCSI check condition of medium may have changed.” SME does not perform the media
identification logic correctly for this check condition, which causes tape labeling to fail.
Workaround: None.
•
CSCsz59152
Symptom: On an MDS 9513 switch, the crossbar ASIC on a Fabric 1 or Fabric 2 module may fail.
As a result, some ports may get disabled on the modules that use the crossbar links in the bad fabric
module.
As a result, some ports may get disabled on the modules that use the crossbar links in the bad fabric
module.
Workaround: To resolve this issue, follow these steps:
1.
Replace the affected Fabric 1 or Fabric 2 module.
2.
Manually bring up the ports that went down by entering the shut command, followed by the no
shut command.
shut command.
•
CSCsz84411
Symptom: An MDS 9124 switch may randomly reboot with a reset reason of unknown. This is a
rare event and occurs only in systems that have a single power supply with a serial number beginning
with QCS.
rare event and occurs only in systems that have a single power supply with a serial number beginning
with QCS.
Workaround: Install and power up the redundant power supply.
•
CSCtb00005
Symptom: On an MDS 9000 switch running NX-OS Release 4.1(x) software, if three supervisor
switchovers occur within a 20-minute period, an embedded event manager (EEM) policy triggers
the power down of all modules in the chassis. Internal processing associated with the EEM policy
might leave the state of a module out-of-sync with the supervisor module.
switchovers occur within a 20-minute period, an embedded event manager (EEM) policy triggers
the power down of all modules in the chassis. Internal processing associated with the EEM policy
might leave the state of a module out-of-sync with the supervisor module.
Workaround: Remove the module and then reinstall it.
•
CSCtb28442
Symptom: End of sequence is not set for STK drives when the host requests more data than what is
written to the tape.
written to the tape.
Workaround: None.
•
CSCtb77695
Symptom: When a tape reaches its capacity, an IBM TS1120 tape drive send a check condition with
eom=1 and asc_ascq = 0. Because asc_ascq is not set to End of Medium or Partition, SME continues
to send traffic as if the end of the tape has not been reached. As a result, the backup fails when it
spans across multiple tapes. This issue is specific only to IBM TS1120 tape drives.
eom=1 and asc_ascq = 0. Because asc_ascq is not set to End of Medium or Partition, SME continues
to send traffic as if the end of the tape has not been reached. As a result, the backup fails when it
spans across multiple tapes. This issue is specific only to IBM TS1120 tape drives.
Workaround: None.
•
CSCtc20849
Symptom: Following a reboot of an MDS 9513 switch running Cisco SAN-OS Release 3.3(2), both
supervisor modules generated core files. The show cores command and the show system
reset-reason command displayed the following output:
supervisor modules generated core files. The show cores command and the show system
reset-reason command displayed the following output:
switch# show cores
Module-num Process-name PID Core-create-time
---------- ------------ --- ----------------
8 qos 15671 Sep 21 22:16
7 qos 4370 Sep 21 22:17
switch# show system reset-reason