Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.3(4a) (OL-14116-13, November 2009)

Send documentation comments to [e-mail]
31
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.3(4a)
OL-14116-13
Caveats
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:
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
----- reset reason for Supervisor-module 8 (from Supervisor in slot 8) ---
1) At 517868 usecs after Mon Sep 21 22:12:09 2009
Reason: Reset triggered due to HA policy of Reset
Service: Service "qos"
Version: 3.3(2)
----- reset reason for Supervisor-module 7 (from Supervisor in slot 7) ---
1) At 260648 usecs after Mon Sep 21 22:12:37 2009
Reason: Reset triggered due to HA policy of Reset
Service: Service "qos"
Version: 3.3(2)
Workaround: This issue is resolved.
• CSCtc48338
Symptom: On any of the MDS 9500 Series Director switches that have removable Supervisor 2
modules, a supervisor may reset when any one of the following commands is executed on the switch,
or the same information is collected through Cisco Fabric Manager or Device Manager:
• show hardware internal mgmt0 stats
• show hardware internal eobc stats
• show tech
• show tech details
• show tech-support
• tac-pac
In a dual supervisor switch, entering one of these commands will force a supervisor switchover. In
single supervisor systems, the switch will reload.
This issue does not affect switches with a nonremovable Supervisor 2 module, such as the MDS
9222i or MDS 9124.
Workaround: This issue is resolved.
Open Caveats
• CSCsr85709
Symptom: Under certain conditions, the port manager can take a long time to respond to a port
configuration, which can trigger a set-port-configuration failure. If this occurs, then the FCIP tunnel
will not come up and will stay in a disabled state.
Workaround: Enter a shut command, followed by a no shut command on the FCIP interface at
either end of the FCIP tunnel.