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 i s c o . c o m
33
Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.2(1)
OL-25090-01
Caveats
•
CSCth80324
Symptom
: FCIP links flap due to maximum TCP retransmissions (“TCP conn. closed - retransmit
failure”), or to extended pings to a peer FCIP switch that shows packet loss. This issue is due to a
buffer leak that is caused when ICMP unreachables are generated in response to frames with an
unreachable source address, such as 0.0.0.0.
This issue can be seen on all Ethernet ports on the MSM-18/4 module and the MDS 9222i switch,
when either is running Cisco NX-OS Release 4.2(1) or later, or Cisco NX-OS Release 5.0(1) or later.
Workaround
: This issue is resolved.
•
CSCti73204
Symptom
: The
show interface ethernet flowcontrol
command entered on an MDS 9000 Family
switch returned the message: “Internal error.”
Workaround
: This issue is resolved.
•
CSCtj92295
Symptom
: An MDS 9000 Family switch fails in the wwnmanager process. Use the s
how logging
log
command and the
show cores
command to confirm the issue:
switch# 2010 Nov 8 06:38:28 sw-dc3-br1-51 %SYSMGR-2-SERVICE_CRASHED: Service
"wwn" (PID 2897) hasn't caught signal 6 (core will be saved).
switch#
sh core
Module Instance Process-name PID Date(Year-Month-Day Time)
------ -------- --------------- -------- -------------------------
8 1 wwn 2897 2010-11-08 06:38:33
Workaround
: This issue is resolved.
•
CSCtk47039
Symptom
: An MDS 9000 Family switch does not respond to an FDISC from an NPV attached
switch if the MDS 9000 switch is already processing an FDISC for the same PWWN. This issue
occurs when the downstream device is running in NPV mode and the FDISC for the same PWWN
must be in progress and no ABTS is sent to cancel the in-progress FDISC.
Workaround
: This issue is resolved.
•
CSCtl86272
Symptom
: Following a software upgrade on a MDS 9222i switch, traffic failures occurred between
a newly configured flow, such as a regular zone flow, an FC-redirect flow, and an IVR flow. The
ACL TCAM entry for the affected flow has no adjacency pointer and therefore no forwarding
information for the flow, as can be seen by entering the following commands:
switch#
attach mod x
switch#
show process acltcam fwd-engine 0 input interface fcy/z
...
Loc cl vsan s_id d_id si up sof ipda dport prot sy fi fr en | pri mod ctl adj
up vld cw stats ce
-----------------------------------------------------------------------------------
--------------------
...
6ef6 2 64 7d0109 7d0101 1 0 0 0 0 0 0 0 0 0 | 0 0 0 0
0 1 0 0 0
...
