HP Cisco Nexus 5000 Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS R - Page 54

Workaround, Symptom, show system internal, capability, ips measure-rtt, show tech-support sme

Page 54 highlights

Caveats Send documentation comments to [email protected] Workaround: Exit all Fabric Manager clients and rename the map layout files by replacing space characters with an underscore. The map layout files are found on the computer running the Fabric Manager server. Each Fabric Manager user has their own directory of map files. These map files are found in the following directory: C:\Program Files\Cisco Systems\MDS 9000\db\\*.map. • CSCsq66823 Symptom: On an MDS 9222i switch, an upgrade from SAN-OS Release 3.2(x), Release 3.3(1a), or Release 3.3(1c) to SAN-OS Release 3.3(1c) fails when there is an active FC-Redirect configuration (created by SME or DMM applications) on the switch. An active FC-Redirect configuration is defined as: • FC-Redirect configuration for hosts or targets connected locally • FC-Redirect configuration created by the application running on that switch. If an upgrade is attempted when an active configurations is present, the switch will go into a disruptive upgrade. Workaround: Take the targets in FC-Redirect configurations offline. • CSCso49196 Symptom: During an upgrade from SAN-OS Release 3.2(3a) to Release 3.3(1a), when a switchover occurs to the Supervisor running Release 3.3(1a), Cisco SME traffic flows for hosts that are not connected locally to the switch that is getting upgraded, may get flapped for a very short time. This can also occur during a switchover to a Supervisor running Release 3.3(1a). Workaround: None. • CSCso31754 Symptom: IVR does not finish a domain capture which stops the export of IVR devices. Workaround: To avoid the API errors that cause this ACL/IVR issue, enter the show system internal capability command on the standby Supervisor and look at the last entry under each module. (You can ignore the Supervisor.) If the output states online then you can do a switchover or an upgrade. • CSCsi56167 Symptom: The response time shown in the output of a ping ip-address command may not be accurate if there is an MDS MSM-8/4 in the path. Workaround: Use the ips measure-rtt command to measure the round trip time. • CSCsk91974 Symptom: When you issue the show tech-support sme or the show klm internal isapi_scsi command after attaching to a module, you may see this error message: cat: write error: Bad address. This issue does not affect the actual tech-support log. Workaround: None. • CSCsk73654 Symptom: In certain tape libraries, the tape drives are exported as LUNs. If these target ports are already a part of a Cisco SME configuration and new tape drives are added as LUNs, the new tape drives will not be discovered during a Cisco SME tape group or tape device configuration. Workaround: Perform a rescan at the host level or a flap of the target port to allow Cisco SME to rediscover these newly added tape drives. • CSCso50663 Symptom: The following syslog message is displayed: Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.3(2) 54 OL-14116-10

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58

Send documentation comments to [email protected]
54
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.3(2)
OL-14116-10
Caveats
Workaround
: Exit all Fabric Manager clients and rename the map layout files by replacing space
characters with an underscore. The map layout files are found on the computer running the Fabric
Manager server. Each Fabric Manager user has their own directory of map files. These map files are
found in the following directory:
C:\Program Files\Cisco Systems\MDS 9000\db\<user>\*.map
.
CSCsq66823
Symptom: On an MDS 9222i switch, an upgrade from SAN-OS Release 3.2(x), Release 3.3(1a), or
Release 3.3(1c) to SAN-OS Release 3.3(1c) fails when there is an active FC-Redirect configuration
(created by SME or DMM applications) on the switch. An active FC-Redirect configuration is
defined as:
FC-Redirect configuration for hosts or targets connected locally
FC-Redirect configuration created by the application running on that switch.
If an upgrade is attempted when an active configurations is present, the switch will go into a
disruptive upgrade.
Workaround
: Take the targets in FC-Redirect configurations offline.
CSCso49196
Symptom
: During an upgrade from SAN-OS Release 3.2(3a) to Release 3.3(1a), when a switchover
occurs to the Supervisor running Release 3.3(1a), Cisco SME traffic flows for hosts that are not
connected locally to the switch that is getting upgraded, may get flapped for a very short time. This
can also occur during a switchover to a Supervisor running Release 3.3(1a).
Workaround
: None.
CSCso31754
Symptom
: IVR does not finish a domain capture which stops the export of IVR devices.
Workaround
: To avoid the API errors that cause this ACL/IVR issue, enter the
show system internal
capability
command on the standby Supervisor and look at the last entry under each module. (You can
ignore the Supervisor.) If the output states
online
then you can do a switchover or an upgrade.
CSCsi56167
Symptom
: The response time shown in the output of a
ping
ip-address
command may not be accurate
if there is an MDS MSM-8/4 in the path.
Workaround
: Use the
ips measure-rtt
command to measure the round trip time.
CSCsk91974
Symptom
: When you issue the
show tech-support sme
or the
show klm internal isapi_scsi
command
after attaching to a module, you may see this error message:
cat: write error: Bad address
. This
issue does not affect the actual tech-support log.
Workaround
: None.
CSCsk73654
Symptom
: In certain tape libraries, the tape drives are exported as LUNs. If these target ports are already
a part of a Cisco SME configuration and new tape drives are added as LUNs, the new tape drives will not
be discovered during a Cisco SME tape group or tape device configuration.
Workaround
: Perform a rescan at the host level or a flap of the target port to allow Cisco SME to
rediscover these newly added tape drives.
CSCso50663
Symptom
: The following syslog message is displayed: