Technical data

90 Fabric OS FCIP Administrator’s Guide
53-1002474-01
FCIP links
4
3. Confirm that traffic shaping is configured to limit the bandwidth to available using one of the
following commands:
- portShow fciptunnel all -perf –params (FR4-18i blade)
- portShow fciptunnel all -perf --tcp -c (7800 switch and FX8-24 blade)
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 for 7800 switches and FX8-24 blades, or ipperf for FR4-18i blades 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. If FR4-18i blades are
moved to different slots without first deleting configurations, errors can be seen when trying to
reuse these IP addresses.
• 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.
• If an FCIP tunnel fails with the “Disabled (Fabric ID Oversubscribed)” message, the solution is
to reconfigure the VEX_Port to the same Fabric ID as all of the other ports connecting to the
edge fabric.
• Because of an IPsec RASLog limitation, you may not be able to determine an incorrect
configuration that causes an IPsec tunnel to not become active. This misconfiguration can
occur on either end of the tunnel. As a result, you must correctly match the encryption method,
authentication algorithm, and other configurations on each end of the tunnel.
Gathering additional information
The following commands should be executed and their data collected before the supportsave
command is run. A supportsave can take ten minutes or more to run, and some of the information
is time critical.
NOTE
The portshow -perf and - params options can be applied only to the FR4-18i blade.
• traceDump -n