Junos OS

 View Only
last person joined: yesterday 

Ask questions and share experiences about Junos OS.

"traceroute monitor" command

  • 1.  "traceroute monitor" command

    Posted 09-29-2023 13:16

    Hi, 

    I'm start learning Junos in the recent days.

    I understood that the "traceroute monitor" is like a traceroute alway running and updating the result has the topology change over the time.

    I had setup the network diagram in a lab session 

    static route are used in this setup to reach Lo0.0 of each router from each other.  The most direct route has precedence of 1 and I have also setup qualified next to to each other as well

    example from vMX3 perspective :

    jcluser@vMX3# show | display set    
    set routing-options static route 0.0.0.0/0 next-hop 100.123.0.1
    set routing-options static route 10.1.1.1/32 next-hop 10.0.2.1
    set routing-options static route 10.1.1.1/32 qualified-next-hop 10.0.4.2 preference 2
    set routing-options static route 10.1.1.1/32 qualified-next-hop 10.0.6.4 preference 2
    set routing-options static route 10.1.1.1/32 preference 1
    set routing-options static route 10.2.2.2/32 next-hop 10.0.4.2
    set routing-options static route 10.2.2.2/32 qualified-next-hop 10.0.6.4 preference 2
    set routing-options static route 10.2.2.2/32 qualified-next-hop 10.0.2.1 preference 2
    set routing-options static route 10.2.2.2/32 preference 1
    set routing-options static route 10.4.4.4/32 next-hop 10.0.6.4
    set routing-options static route 10.4.4.4/32 qualified-next-hop 10.0.4.2 preference 2
    set routing-options static route 10.4.4.4/32 qualified-next-hop 10.0.2.1 preference 2
    set routing-options static route 10.4.4.4/32 preference 1

    the setup work fine when I disable ge-0/0/2 on vMX3 the route to 10.1.1.1 is removed and subsequent route through vMX2 become the new next hop.

    on the beginning of my test all interfaces are enable

    on vMX3 I run "ping 10.1.1.1 source 10.3.3.3"

    so the trafic is as expected to 10.0.2.1

    I diabled interface ge-0/0/2 

    so traffic this case is going to vMX2 according to the routing table 

    jcluser@vMX3# run show route table inet.0 10.1.1.1  

    inet.0: 12 destinations, 14 routes (12 active, 0 holddown, 0 hidden)
    + = Active Route, - = Last Active, * = Both

    10.1.1.1/32        *[Static/2] 01:47:39
                           to 10.0.6.4 via ge-0/0/0.0
                        >  to 10.0.4.2 via ge-0/0/1.0

    [edit routing-options static]

    my ping requestis still pinging successfully 

    but the traffic is now going from vMX3 to vMX2 to finally reach vMX1 lo0.0 interface.

    But to see the new traffic path on the "traceroute monitor" I have to interrupt it and restart it to see the traffic is croossing vMX2 to reach vMX1.

    The reverse behavior is also the same, after I restart the "traceroute monitor" command I see it crossing vMX2 to reach vMX1.  So I reenable path between vMX3 and vMX1  so the direct path between the 2 routers should be effective but according to the monitor traceroute traffic is still going through vMX2.  I restart the "traceroute monitor" and then the direct path is now shown...

    what I why I should restart the "traceroute monitor" command to see the updated path ?  


      



    ------------------------------
    Christian Phoenix
    ------------------------------