Troubleshooting Fcip Link Flaps; Troubleshooting Fcip Isl Link Failures - Cisco 9134 - MDS Multilayer Fabric Switch Troubleshooting Manual

FCIP Issues
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
Jan 14 15:14:31
Jan 14 15:14:31
Jan 14 15:14:31
Jan 14 15:14:31
Jan 14 15:14:31
Jan 14 15:14:31
does not match LEP's peer fabric WWN (0x20010005300059df)
Jan 14 15:14:31
Jan 14 15:14:31
Jan 14 15:14:31
0xd8072c00
Jan 14 15:14:31
Jan 14 15:14:37
10.10.10.2:64046
Jan 14 15:14:37
Jan 14 15:14:37
Jan 14 15:14:37
Jan 14 15:14:37
Jan 14 15:14:37
Jan 14 15:14:37
Jan 14 15:14:37
does not match LEP's peer fabric WWN (0x20010005300059df)
Jan 14 15:14:37
Jan 14 15:14:37
Jan 14 15:14:37
0xd8071000
Jan 14 15:14:37
Jan 14 15:14:37
10.10.10.2:64044
Jan 14 15:14:37
Jan 14 15:14:37
Jan 14 15:14:37
Jan 14 15:14:37
Jan 14 15:14:37
Jan 14 15:14:37
Jan 14 15:14:37
does not match LEP's peer fabric WWN (0x20010005300059df)
Jan 14 15:14:37
Jan 14 15:14:37
Jan 14 15:14:37
0xd8071400
Jan 14 15:14:37

Troubleshooting FCIP Link Flaps

If you have an FCIP link that flaps, adjust the TCP keepalive and max retransmission values. In Fabric
Manager, choose ISLs > FCIP, select the Profiles tab and set the Keepalive field. In the CLI, use the tcp
keepalive-timeout and tcp max-retransmissions commands in FCIP profile submode.

Troubleshooting FCIP ISL Link Failures

If you have an FCIP ISL link that experiences unexplained failures, the FCIP profile in use may not be
configured to match the underlying physical link characteristics and the shared traffic constraints.
For example, if you have a 200 Mbps physical link and you have configured two FCIP tunnels across
that link, each with 155 Mbps traffic, link failures will occur because the physical connection cannot
handle the traffic.
Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x
20-34
port1: 855328:FCIP21: Bind the DE 0xd802d200 [1] to tunnel LEP 0x80111570
port1: 855329:FCIP21: Bind DE 1 to TCP-hdl 0xd8072c00
port1: 855330:FCIP21: Setup for Special Frame handling: I'm Responder
port1: 855331:FCIP21: Setup timer to wait for SF
port1: 855332:FCIP21: processing SF frame, I'm Responder
port1: 855333:FCIP21: Source FC fabric name in SF (0x20000005300059de)
port1: 855334:FCIP21: Delete the DE [1]0xd802d200
port1: 855335:FCIP21: Set lep operation state to DOWN
port1: 855336:FCIP21: DE [-670903808] 0x00000001 terminate tcp connection
port1: 855337:FCIP21: Delete the DE object [1] 0xd802d200
port1: 855338:FCIP21: Received new TCP connection from peer:
port1: 855339:FCIP21: Create a DE 0xd802d5c0 for this tunnel
port1: 855340:FCIP21: Bind the DE 0xd802d5c0 [1] to tunnel LEP 0x80111570
port1: 855341:FCIP21: Bind DE 1 to TCP-hdl 0xd8071000
port1: 855342:FCIP21: Setup for Special Frame handling: I'm Responder
port1: 855343:FCIP21: Setup timer to wait for SF
port1: 855344:FCIP21: processing SF frame, I'm Responder
port1: 855345:FCIP21: Source FC fabric name in SF (0x20000005300059de)
port1: 855346:FCIP21: Delete the DE [1]0xd802d5c0
port1: 855347:FCIP21: Set lep operation state to DOWN
port1: 855348:FCIP21: DE [-670902848] 0x00000001 terminate tcp connection
port1: 855349:FCIP21: Delete the DE object [1] 0xd802d5c0
port1: 855350:FCIP21: Received new TCP connection from peer:
port1: 855351:FCIP21: Create a DE 0xd802cac0 for this tunnel
port1: 855352:FCIP21: Bind the DE 0xd802cac0 [1] to tunnel LEP 0x80111570
port1: 855353:FCIP21: Bind DE 1 to TCP-hdl 0xd8071400
port1: 855354:FCIP21: Setup for Special Frame handling: I'm Responder
port1: 855355:FCIP21: Setup timer to wait for SF
port1: 855356:FCIP21: processing SF frame, I'm Responder
port1: 855357:FCIP21: Source FC fabric name in SF (0x20000005300059de)
port1: 855358:FCIP21: Delete the DE [1]0xd802cac0
port1: 855359:FCIP21: Set lep operation state to DOWN
port1: 855360:FCIP21: DE [-670905664] 0x00000001 terminate tcp connection
port1: 855361:FCIP21: Delete the DE object [1] 0xd802cac0
Chapter 20 Troubleshooting IP Storage Services
OL-9285-05