Brocade Fabric OS FCIP Administrator's Guide v7.1.0 (53-1002748-01, March 2013)

74 Fabric OS FCIP Administrator’s Guide
53-1002748-01
FCIP links
3
7. Get a GE Ethernet sniffer trace.
Rule out all possible blocking factors. Routers and firewalls that are in the data path must be
configured to pass FCIP traffic (TCP port 3225) and IPsec traffic, if IPsec is used (UDP port
500). If possible blocking factors have been rule out, simulate a connection attempt using the
portCmd
--ping command, from source to destination, and then take an Ethernet trace
between the two endpoints. The Ethernet trace can be examined to further troubleshoot the
FCIP connectivity.
Symptom FCIP tunnel goes online and offline.
Probable cause and recommended action
A bouncing tunnel is one of the most common problems. This issue is usually because of an over
commitment of available bandwidth resulting in the following behaviors.
• Too much data tries to go over the link.
• Management data gets lost, queued too long, and timeouts expire.
• Data exceeds timeouts multiple times.
Take the following steps gather information.
1. Verify what link bandwidth is available.
2. Confirm the IP path is being used exclusively for FCIP traffic.
3. Confirm that traffic shaping is configured to limit the bandwidth to available using the following
command:
portShow fciptunnel all -perf --tcp -c
Examine data from both routers. This data shows retransmissions indicating input and output
rates on the tunnels.
Gather this information for both data and management TCP connections.
4. Run Tperf to gather WAN performance data.
FCIP links
The following list contains information for troubleshooting FCIP links:
• When deleting FCIP links, you must delete them in the exact reverse order they were created.
That is, first delete the tunnels, then the IP interfaces, and finally the port configuration.
Statically defined IP routes are not removed automatically and must be removed before
manually before deleting IP addresses.
• IP addresses and FCIP configurations are retained by slot in the system.
• The portCmd --ping command only verifies physical connectivity. This command does not
verify that you have configured the ports correctly for FCIP tunnels.
• Ports at both ends of the tunnel must be configured correctly for an FCIP tunnel to work
correctly. These ports can be either VE_Ports or VEX_Ports. A VEX_Port must be connected to a
VE_Port.
• When configuring routing over an FCIP link for a fabric, the edge fabric will use VE_Ports and
the backbone fabric will use VEX_Ports for a single tunnel.