Fcip Links - Brocade Communications Systems A7533A - Brocade 4Gb SAN Switch Base Troubleshooting Manual

Brocade troubleshooting and diagnostics guide v6.1.0 (53-1000853-01, june 2008)
Hide thumbs Also See for A7533A - Brocade 4Gb SAN Switch Base:
Table of Contents

Advertisement

1. If committing a rate, generally recommend setting a little below available to allow for bursting
2. Type the portShow fciptunnel <GB Port Number> all -perf –params command.
3. Run the following commands on both sides of the tunnel:
4. Confirm the throughput using the portCmd
5. Repeat each step in the opposite direction to get throughput

FCIP links

The following list contains information for troubleshooting FCIP links:
Fabric OS Troubleshooting and Diagnostics Guide
53-1000853-01
To much data tries to be sent over the link.
Management data gets lost, queued too long, and timeouts expire.
Data exceeds timeouts multiple times.
Verify what link bandwidth is available.
Confirm the IP path is being used exclusively for FCIP traffic.
Confirm that traffic shaping is configured to limit the bandwidth to available (portshow
fciptunnel).
Examine data from both routers. This data is not in the supportshow output and shows
retransmissions indicating, input and output rates on the tunnels.
Gather this information for both data and management TCP connections.
portCmd
ipperf <slot/GBPort> -s <local IP> -d <remote IP> -R
--
portCmd
ipperf <slot/GBPort> -s <local IP> -d <remote IP> -S
--
This command must be run on both sides of the tunnel, simultaneously.
On local side:
portcmd --ipperf <slot/GBPort> -s <local IP> -d <remote IP> -R
On Remote side:
portcmd --ipperf <slot/GBPort> -s <local IP> -d <remote IP> -S
When deleting FCIP links, you must delete them in the exact reverse order they were created.
That is, delete first the tunnels, then the IP interfaces, and finally the port configuration. The IP
route information is removed automatically at this point.
IP addresses 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.
One port can be included in multiple tunnels, but each tunnel must have at least one port that
is unique to that tunnel.
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.
ipperf command.
--
9
FCIP links
71

Advertisement

Table of Contents
loading

Table of Contents