Routing

last person joined: 3 days ago 

Ask questions and share experiences about ACX Series, CTP Series, MX Series, PTX Series, SSR Series, JRR Series, and all things routing, including portfolios and protocols.
  • 1.  Why the ping command is not complicated?

    Posted 08-03-2016 11:02

    Hi

    Why the ping command is not complicated? I have to use the below command to ping.Otherwise it cannot work. The destination and source are connected directly. Anyone can give some suggestion? Thank you

    ping 6.1.1.1.1 bypass-routing interface ge-1/1/3



  • 2.  RE: Why the ping command is not complicated?

     
    Posted 08-03-2016 11:38

    Hi,

     

    Its possible to source the ping from different interfaces. From that command you are sourcing the ping from ge-1/1/3 and bypassing the routing table for this destination.

    Can you check for the route of this address:

    show route x.x.x.x

    Also, the IP address 6.1.1.1.1 does not sound right.

    Cheers,

    Ashvin



  • 3.  RE: Why the ping command is not complicated?

    Posted 08-04-2016 18:31

     Sorry. it should be 6.1.1.1.

    show route x.x.x.x will show some production info, so, ...
    i wonder why ping 6.1.1.1 cannot work, instead this can work: ping 6.1.1.1 bypass-routing interface ge-1/1/3. it is two rotuer connected directly 



  • 4.  RE: Why the ping command is not complicated?
    Best Answer

     
    Posted 08-05-2016 02:59

    Hi,

     

    When you run "ping 6.1.1.1", the ping is being initiated from the default instance [inet.0].

    If there is a route for 6.1.1.1 in inet.0, the ping should be able to use the egress interface of that route.

    In this case, there should be a direct route for 6.1.1.1 in the routing-table where the interface is configured.

     

    Possible reasons why the ping does not work is when the interface is in a routing-instance.

    Example:

    root@PE01# run show route table inet.0 192.168.102.2    
    
    [edit]
    root@PE01# run ping 192.168.102.2 
    PING 192.168.102.2 (192.168.102.2): 56 data bytes
    ping: sendto: No route to host
    ping: sendto: No route to host
    ^C
    --- 192.168.102.2 ping statistics ---
    2 packets transmitted, 0 packets received, 100% packet loss
    
    root@PE01# run ping bypass-routing interface ge-0/0/1 192.168.102.2    
    PING 192.168.102.2 (192.168.102.2): 56 data bytes
    64 bytes from 192.168.102.2: icmp_seq=0 ttl=64 time=3.483 ms
    64 bytes from 192.168.102.2: icmp_seq=1 ttl=64 time=2.255 ms
    ^C
    --- 192.168.102.2 ping statistics ---
    2 packets transmitted, 2 packets received, 0% packet loss
    round-trip min/avg/max/stddev = 2.255/2.869/3.483/0.614 ms

    The interface was in a routing-instance TEST-VRF:

    root@PE01# run show interfaces terse routing-instance TEST-VRF 
    Interface               Admin Link Proto    Local                 Remote
    ge-0/0/1.0              up    up   inet     192.168.102.1/30

    Specifying the routing-instance for the ping:

    root@PE01# run ping routing-instance TEST-VRF 192.168.102.2 
    PING 192.168.102.2 (192.168.102.2): 56 data bytes
    64 bytes from 192.168.102.2: icmp_seq=0 ttl=64 time=2.159 ms
    64 bytes from 192.168.102.2: icmp_seq=1 ttl=64 time=1.366 ms
    ^C
    --- 192.168.102.2 ping statistics ---
    2 packets transmitted, 2 packets received, 0% packet loss
    round-trip min/avg/max/stddev = 1.366/1.762/2.159/0.396 ms
    
    root@PE01# run show route 192.168.102.2

    TEST-VRF.inet.0: 5 destinations, 8 routes (5 active, 0 holddown, 0 hidden)
    + = Active Route, - = Last Active, * = Both

    192.168.102.0/30 *[Direct/0] 00:14:34
    > via ge-0/0/1.0

    Do you have a route for 6.1.1.1 in inet.0?

     

    Hope this helps.

    Cheers,

    Ashvin



  • 5.  RE: Why the ping command is not complicated?

    Posted 08-05-2016 10:16

    Thank you so much for your reply. it is vrf issue