Technical data

Fabric OS FCIP Administrator’s Guide 89
53-1002474-01
FCIP tunnel issues
4
2. Confirm IP configuration is correct on both tunnel endpoints using the following command.
portshow ipif ge1
3. Enter the portCmd --ping command to the remote tunnel endpoint from both endpoints.
The -s value is the source IP address; the –d value is the destination IP address.
portcmd --ping ge1 -s 11.1.1.1 -d 11.1.1.2
If the command is successful, then you have IP connectivity and your tunnel should come up. If
not continue to the next step.
4. Enter the portCmd
--traceroute command to the remote tunnel endpoint from both endpoints.
portcmd --traceroute ge1 -s 11.1.1.1 -d 11.1.1.2
5. The tunnel or route lookup may fail to come online because of a missing but required IP route.
If there are routed IP connections that provide for the FCIP tunnel, then both ends of the tunnel
must have defined ipRoute entries.
Refer to the “Configuring an IP route” on page 37 to review the setup of the IP route.
6. Confirm FCIP tunnel is configured correctly using the following command:
portshow fciptunnel ge1 all
The Compression, Fastwrite, and Tape Pipelining settings must match the opposite endpoint or
the tunnel may not come up. Remote and local IP and WWN should be opposite each other.
For details on command syntax and example output, refer to the Fabric OS Command
Reference Manual.
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.