H3C Technologies H3C SecPath F1000-E - Manual (Page 22)

11
NOTE:
Configure the debugging, terminal debugging and terminal monitor commands before you can display
detailed debugging information on the terminal. For more information about the terminal debugging and
terminal monitor commands, see
Network Management and Monitoring Command Reference.
System maintenance and debugging examples
Ping example
Network requirements
As shown in Figure 8 , verify whether SecPath and Device B can reach each other. If they can reach each
other, get detailed information about routes from SecPath to Device B.
Figure 8 Network diagram
Test procedure
# Use the ping command to display whether SecPath and Device B can reach each other.
<SecPath> ping 1.1.2.2
PING 1.1.2.2: 56 data bytes, press CTRL_C to break
Reply from 1.1.2.2: bytes=56 Sequence=1 ttl=254 time=205 ms
Reply from 1.1.2.2: bytes=56 Sequence=2 ttl=254 time=1 ms
Reply from 1.1.2.2: bytes=56 Sequence=3 ttl=254 time=1 ms
Reply from 1.1.2.2: bytes=56 Sequence=4 ttl=254 time=1 ms
Reply from 1.1.2.2: bytes=56 Sequence=5 ttl=254 time=1 ms
--- 1.1.2.2 ping statistics ---
5 packet(s) transmitted
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 1/41/205 ms
# Get detailed information about routes from SecPath to Device B.
<SecPath> ping -r 1.1.2.2
PING 1.1.2.2: 56 data bytes, press CTRL_C to break
Reply from 1.1.2.2: bytes=56 Sequence=1 ttl=254 time=53 ms
Record Route: