380 Configuring and monitoring FCIP tunneling
Verifying IP connectivity
After you add the IP addresses of the routes, enter the
portCmd ping
command to ping a destination IP
address from one of the source IP interfaces on the GbE port and verify the Ethernet IP to IP connectivity.
This verification also ensures that data packets can be sent to the remote interface. You can ping a
connection only if both ports have IP interfaces set.
Use the
portCmd --ping
command to ping a destination IP address from one of the source IP interfaces
on the GbE port. Following is the syntax for the command:
portcmd --ping
[
slot-number
/]
port-number
-s
<source -ip>
-d
<dest-ip>
[
-n
<num-requests>][
-q
<
type-of-service
>][
-t
<
ttl
>][
-w<wait-time
]<
-z<size
>]
where:
-s <source_ip>
Specifies the source IP interface that originates the ping request.
-d <destination_ip>
Specifies the destination IP address to which to target the ping request.
-n
<num-requests>
(Optional) Generates specified number of ping requests. The default is 4.
-q
<
type-of-service
>
(Optional) Sets the “tos” in the ping requests to the type of service. The default is 0
(zero). The value must be an integer in the range from 0 through 255.
-t
<
ttl
>
(Optional) Specifies the time to live. The default value is 100.
-w
<
wait-time
>
(Optional) Specifies the time to wait for the response of each ping request. This
parameter is specified in milliseconds and the default value is 5000 milliseconds (5
sec). The maximum allowed wait time for ping is 9000 milliseconds (9 sec).
-z
<
size
>
(Optional) Specifies the size in bytes of the ping packet to use. The default size is 64
bytes. The total size including ICMP/IP headers (28 bytes without IP options) cannot
be greater than IP MTU configured on the interface.
Following is an example of pinging an address from a particular IP interface:
See the
Fabric OS Command Reference Manual
for details about using the
portCmd ping
command.
Testing end-to-end IP path performance
After installing the IP configuration on the FCIP port (e.g. IP address, route entries), you can test the
end-to-end path performance characteristics of the IP interface using WAN analysis tools. For more
information, see ”
WAN performance analysis tools
” on page 387. These tools enable you to monitor
bandwidth, loss, round trip time, and other statistics for a traffic stream between a pair of Brocade port
endpoints.
switch:admin06> portcmd --ping ge0 -s 192.175.5.100 -d 192.175.5.200
Pinging 192.175.5.200 from ip interface 192.175.5.100 on 0/ge0 with 64 bytes of data
Reply from 192.175.5.200: bytes=64 rtt=1ms ttl=64
Reply from 192.175.5.200: bytes=64 rtt=0ms ttl=64
Reply from 192.175.5.200: bytes=64 rtt=0ms ttl=64
Reply from 192.175.5.200: bytes=64 rtt=1ms ttl=64
Ping Statistics for 192.175.5.200:
Packets: Sent = 4, Received = 4, Loss = 0 (0 percent loss)
Min RTT = 0ms, Max RTT = 1ms Average = 0ms
Summary of Contents for AE370A - Brocade 4Gb SAN Switch 4/12
Page 18: ...18 ...
Page 82: ...82 Managing user accounts ...
Page 102: ...102 Configuring standard security features ...
Page 126: ...126 Maintaining configurations ...
Page 198: ...198 Routing traffic ...
Page 238: ...238 Using the FC FC routing service ...
Page 260: ...260 Administering FICON fabrics ...
Page 280: ...280 Working with diagnostic features ...
Page 332: ...332 Administering Extended Fabrics ...
Page 414: ...398 Configuring the PID format ...
Page 420: ...404 Configuring interoperability mode ...
Page 426: ...410 Understanding legacy password behaviour ...
Page 442: ...426 ...
Page 444: ......
Page 447: ......