Step 2: Use Interface Addresses
Purpose
You can ping interfaces on remote routers.
Action
To ping and traceroute between R5 and R6, enter the following JUNOS CLI operational mode commands:
user@host>pinginterface-addresscountrequests
user@host>tracerouteinterface-address
Sample Output
user@R6>ping 10.1.15.2 count 3
PING 10.1.15.2 (10.1.15.2): 56 data bytes
64 bytes from 10.1.15.2: icmp_seq=0 ttl=253 time=2.738 ms
64 bytes from 10.1.15.2: icmp_seq=1 ttl=253 time=0.858 ms
64 bytes from 10.1.15.2: icmp_seq=2 ttl=253 time=0.849 ms
--- 10.1.15.2 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.849/1.482/2.738/0.888 ms
user@R6> traceroute 10.1.15.2
traceroute to 10.1.15.2 (10.1.15.2), 30 hops max, 40 byte packets
1 10.1.26.1 (10.1.26.1) 0.617 ms 0.534 ms 0.500 ms
2 10.1.12.1 (10.1.12.1) 3.500 ms 0.543 ms 0.508 ms
3 10.1.15.2 (10.1.15.2) 0.699 ms 0.700 ms 0.672 ms
user@R5> ping 10.1.36.2 count 3
PING 10.1.36.2 (10.1.36.2): 56 data bytes
64 bytes from 10.1.36.2: icmp_seq=0 ttl=253 time=0.890 ms
64 bytes from 10.1.36.2: icmp_seq=1 ttl=253 time=0.857 ms
64 bytes from 10.1.36.2: icmp_seq=2 ttl=253 time=3.264 ms
--- 10.1.36.2 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.857/1.670/3.264/1.127 ms
user@R5> traceroute 10.1.36.2
traceroute to 10.1.36.2 (10.1.36.2), 30 hops max, 40 byte packets
1 10.1.15.1 (10.1.15.1) 0.636 ms 7.979 ms 0.497 ms
2 10.1.12.2 (10.1.12.2) 0.544 ms 0.547 ms 0.512 ms
3 10.1.36.2 (10.1.36.2) 0.729 ms 0.696 ms 0.672 ms
What It Means
The sample output shows a successful ping and traceroute between the interfaces on R6 and R5. The ping is successful because the interface addresses of both routers are advertised to their directly connected neighbors.
The output for the traceroute command shows the path from R6 to R5, which is through R2.
 |
NOTE: A |