Step 4: Evaluate the Solution

Purpose

If the problem is solved, you are finished. If the problem remains or a new problem is identified, start the process over again.

You can address possible causes in any order. In relation to the network in Figure 6, we chose to work from the local router toward the remote router, but you might start at a different point, particularly if you have reason to believe that the problem is related to a known issue, such as a recent change in configuration.

Action

To evaluate the solution, enter the following JUNOS CLI commands:

user@host> show route (ip-address | host-name) 

user@host> ping (ip-address | host-name)

user@host> traceroute (ip-address | host-name)

Sample Output

user@R6> show route 10.0.0.5 

inet.0: 20 destinations, 20 routes (20 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both

10.0.0.5/32        *[BGP/170] 00:01:35, MED 5, localpref 100, from 10.0.0.2

                      AS path: 65001 I

                    > to 10.1.26.1 via so-0/0/2.0

user@R6> ping 10.0.0.5 

PING 10.0.0.5 (10.0.0.5): 56 data bytes

64 bytes from 10.0.0.5: icmp_seq=0 ttl=253 time=0.866 ms

64 bytes from 10.0.0.5: icmp_seq=1 ttl=253 time=0.837 ms

64 bytes from 10.0.0.5: icmp_seq=2 ttl=253 time=0.796 ms

^C

--- 10.0.0.5 ping statistics ---

3 packets transmitted, 3 packets received, 0% packet loss

round-trip min/avg/max/stddev = 0.796/0.833/0.866/0.029 ms

user@R6> traceroute 10.0.0.5 

traceroute to 10.0.0.5 (10.0.0.5), 30 hops max, 40 byte packets

 1  10.1.26.1 (10.1.26.1)  0.629 ms  0.538 ms  0.497 ms

 2  10.1.12.1 (10.1.12.1)  0.534 ms  0.538 ms  0.510 ms

 3  10.0.0.5 (10.0.0.5)  0.776 ms  0.705 ms  0.672 ms

What It Means

The sample output shows that there is now a connection between R6 and R5. The show route command shows that the BGP route to R5 is preferred, as indicated by the asterisk (*). The ping command is successful and the traceroute command shows that the path from R6 to R5 is through R2 (10.1.26.1), and then through R1 (10.1.12.1).