Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.2(2c) (OL14116-03, November 2007)

Send documentation comments to [e-mail]
32
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.2(2c)
OL-14116-03
Caveats
• CSCsk78735
Symptom: The fabric binding database has duplicate local entries.
Workaround: This issue is resolved.
• CSCsk86748
Symptom: In rare circumstances, a Cisco MDS 9000 Supervisor may unexpectedly reload. This can
trigger a Supervisor switchover, or a complete switch reload in the case of non-HA platforms. After
this event, the output of the show system-reset reason command will show output similar to
following:
switch#show system reset-reason
----- reset reason for module 6 from local-supervisor -----
1) At 911546 usecs after Tue Oct 9 11:35:28 2007
Reason: Reset triggered due to bad backplane communication channel
Service: Failure Rx map 0x1f
Version: 3.0(2a)
This issue occurs only in conditions of excessive Fibre Channel control path traffic. This is rare, but
it can happen if, for example, multiple devices that are connected to the switch are reloaded at the
same time.
Workaround: This issue is resolved.
• CSCsl04943
Symptom: The syslogs log file cannot be displayed because the /tmp directory is full. This occurs
when the Control - C command is used to abort the show logging logfile dialog. When the /tmp
directory is full, it can impact SAN-OS operations.
Workaround: This issue is resolved.
• CSCsl16409
Symptom: A CFS incompatibility exists between switches running SAN-OS Release 3.0.x and
Release 3.1.x and switches running Release 3.2.1. In fabrics that include a mix of these SAN-OS
versions, CFS on the switches running Release 3.0.x or Release 3.1.x may not see a switch running
Release 3.2.1 as a CFS peer. SAN-OS Release 3.2.1 is not CFS-compatible with Release 3.0.x and
Release 3.1.x. All other version combinations are compatible.
This could manifest in the following ways:
– CFS applications on switches running Release 3.0.x or Release 3.1.x may not merge with their
peers on a switch running Release 3.2.1.
– Distributions initiated from switches running Release 3.0.x or Release 3.1.x will not make it to
a switch running Release 3.2.1.
This incompatibility does not always occur; however, it occurs when:
– Switches running Release 3.2.1 host virtual domains.
– The domain ID of the real domain on a switch running Release 3.2.1 is less than that of the
virtual domain it hosts.
To identify if this issue occurs, issue the show cfs merge status name <app-id> command on
switches running Release 3.2.1 to show the switches running Release 3.2.1 and the switches running
Release 3.0.x and Release 3.1.x. Issue the show cfs merge status name <app-id> command on
switches running Release 3.0x and Release 3.1.x to show only switches running Release 3.0.x and
Release 3.1.x.
Workaround: This issue is resolved.