The portshow -perf and - params options can be applied only to the 7500 switch and FR4-18i blade.
Symptom FCIP tunnel does not come Online.
Probable cause and recommended action
Confirm the following steps.
1. Confirm GE port is online.
portshow ge1
Eth Mac Address: 00.05.1e.37.93.06
Port State: 1 Online
Port Phys: 6 In_Sync
Port Flags: 0x3 PRESENT ACTIVE
Port Speed: 1G
2. Confirm IP configuration is correct on both tunnel endpoints.
portshow ipif ge1
Port: ge1
Interface IP Address NetMask MTU
----------------------------------------------------------
0 11.1.1.1 255.255.255.0 1500
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
Pinging 11.1.1.2 from ip interface 11.1.1.1 on 0/ge1 with 64 bytes of data
Reply from 11.1.1.2: bytes=64 rtt=0ms ttl=64
Reply from 11.1.1.2: bytes=64 rtt=0ms ttl=64
Reply from 11.1.1.2: bytes=64 rtt=0ms ttl=64
Reply from 11.1.1.2: bytes=64 rtt=0ms ttl=64
Ping Statistics for 11.1.1.2:
Packets: Sent = 4, Received = 4, Loss = 0 ( 0 percent loss)
Min RTT = 0ms, Max RTT = 0ms Average = 0ms
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
Traceroute to 11.1.1.2 from IP interface 11.1.1.1 on 0/1, 64 hops max
1 11.1.1.2 0 ms 0 ms 0 ms
Traceroute complete.
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.
