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

68 Fabric OS FCIP Administrator’s Guide

53-1002748-01

WAN performance analysis tools

Using ping to test a connection

The portCmd --ping command tests the connection between the IP address of a local Ethernet port

and a destination IP address. If you want to use this command to test a VLAN connection when you

do not have an active FCIP tunnel, you must manually add entries to the VLAN tag table on both the

local and remote sides of the route, using portCfg vlantag command.

General syntax of the portcmd --ping command are as follows:

portCmd

--ping slot/ge n|xge n -s source_ip -d destination_ip -n num_requests -q diffserv -t ttl -w

wait_time -z size -v vlan_id -c L2_Cos

When using VLANS, VLAN tagging ensures that test traffic traverses the same path as real FCIP

traffic. A VLAN tag entry for both the local and remote sides of the route must exist prior to issuing

the portCmd --ping or portCmd --traceroute commands. Refer to “Managing the VLAN tag table” on

page 28 for details.

For details of command syntax and output examples, refer to the Fabric OS Command Reference

Manual.

Using traceroute

The portCmd traceroute command traces routes from a local Ethernet port to a destination IP

address. If you want to use this command to trace a route across a VLAN when you do not have an

active FCIP tunnel, you must manually add entries to the VLAN tag table on both the local and

remote sides of the route using portCfg vlantag command.

General syntax of the portcmd --traceroute command are as follows.

portCmd

--traceroute slot/ge n|xge n -s source_ip -d destination_ip -h max_hops -f first_ttl -q

diffserv -w wait time -z size -v vlan_id -c L2_Cos

The following example traces the route between IP addresses 192.168.10.1 and 192.168.20.1

over VLAN 10.

portcmd --traceroute 8/ge0 -s 192.168.10.1 -d 192.168.20.1 -v 10