H3C Technologies H3C S12500 Series Switches - Manual (Page 34)

21
PING 172.16.1.2 (172.16.1.2): 56 data bytes
56 bytes from 172.16.1.2: icmp_seq=0 ttl=254 time=7.000 ms
56 bytes from 172.16.1.2: icmp_seq=1 ttl=254 time=0.000 ms
56 bytes from 172.16.1.2: icmp_seq=2 ttl=254 time=1.000 ms
56 bytes from 172.16.1.2: icmp_seq=3 ttl=254 time=1.000 ms
56 bytes from 172.16.1.2: icmp_seq=4 ttl=254 time=2.000 ms
--- 172.16.1.2 ping statistics ---
5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.000/2.200/7.000/2.482 ms
The output shows that the switch can communicate with the hosts on subnet 172.16.1.0/24.
# Ping a host on subnet 172.16.2.0/24 from the switch to check the connectivity.
ping 172.16.2.2
PING 172.16.2.2 (172.16.2.2): 56 data bytes
56 bytes from 172.16.2.2: icmp_seq=0 ttl=255 time=2.000 ms
56 bytes from 172.16.2.2: icmp_seq=1 ttl=255 time=7.000 ms
56 bytes from 172.16.2.2: icmp_seq=2 ttl=255 time=1.000 ms
56 bytes from 172.16.2.2: icmp_seq=3 ttl=255 time=2.000 ms
56 bytes from 172.16.2.2: icmp_seq=4 ttl=255 time=1.000 ms
--- 172.16.2.2 ping statistics ---
5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss
round-trip min/avg/max/stddev = 1.000/2.600/7.000/2.245 ms
The output shows that the switch can communicate with the hosts on subnet 172.16.2.0/24.
# Ping a host on subnet 172.16.1.0/24 from a host on subnet 172.16.2.0/24 to check the connectivity.
Host B can be successfully pinged from Host A.