Routing

last person joined: 4 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.  ipv6 - No route to host

    Posted 01-20-2016 02:43

    Hello forum guys, 

     

    I have following configuration: 

     

    MX-80-1# run show configuration interfaces ae0.0
    family inet {
    address 10.42.131.37/29;
    }
    family inet6 {
    address 2a00:8a00:6000:601b::11/125;
    }

    [edit]

     

    MX-80-1# run show configuration routing-options
    rib inet6.0 {
    static {
    route ::/0 next-hop 2a00:8a00:6000:601b::9;
    }

     

    Ipv6 neighbor show in ipv6 neighbor table: 

     

    MX-80-1# run show ipv6 neighbors
    IPv6 Address Linklayer Address State Exp Rtr Secure Interface
    fe80::8e60:4fff:fe1b:a4c1 8c:60:4f:1b:a4:c1 stale 184 yes no ae0.0

     

    however, when I try to ping global unicast address - it is fail. 

     

    MX-80-1# run ping 2a00:8a00:6000:601b::9

    PING6(56=40+8+8 bytes) 2a00:8a00:6000:601b::11 --> 2a00:8a00:6000:601b::9
    ping: sendmsg: No route to host
    ping6: wrote 2a00:8a00:6000:601b::9 16 chars, ret=-1
    ping: sendmsg: No route to host
    ping6: wrote 2a00:8a00:6000:601b::9 16 chars, ret=-1
    ping: sendmsg: No route to host
    ping6: wrote 2a00:8a00:6000:601b::9 16 chars, ret=-1
    ping: sendmsg: No route to host
    ping6: wrote 2a00:8a00:6000:601b::9 16 chars, ret=-1
    ^C
    --- 2a00:8a00:6000:601b::9 ping6 statistics ---
    4 packets transmitted, 0 packets received, 100% packet loss

    [edit]

     

    what have I missed? is there any option on Juniper which enable ipv6 unicast routing or is it enable by default? 



  • 2.  RE: ipv6 - No route to host

    Posted 01-20-2016 04:04

    interesting fact is that other end -  cisco router - can ping juniper MX: 

     

    cisco# ping6 2a00:8a00:6000:601b::11
    PING6 2a00:8a00:6000:601b::11 (2a00:8a00:6000:601b::11): 56 data bytes
    64 bytes from 2a00:8a00:6000:601b::11: icmp_seq=0 time=6.668 ms
    64 bytes from 2a00:8a00:6000:601b::11: icmp_seq=1 time=8.578 ms
    64 bytes from 2a00:8a00:6000:601b::11: icmp_seq=2 time=1.52 ms
    64 bytes from 2a00:8a00:6000:601b::11: icmp_seq=3 time=8.461 ms
    64 bytes from 2a00:8a00:6000:601b::11: icmp_seq=4 time=1.38 ms

    --- 2a00:8a00:6000:601b::11 ping6 statistics ---
    5 packets transmitted, 5 packets received, 0.00% packet loss
    round-trip min/avg/max = 1.38/5.321/8.578 ms

     

    cisco# sh ipv6 neighbor | i Vlan132
    01:48:11 0881.f487.d2b0 50 icmpv6 Vlan132
    gta-core-950#

     

     

     

     



  • 3.  RE: ipv6 - No route to host

     
    Posted 01-20-2016 04:32

    Can you specify the interface and check the behavior?

     

    MX-80-1# run ping 2a00:8a00:6000:601b::9 interface ae0.0



  • 4.  RE: ipv6 - No route to host

    Posted 01-20-2016 05:44

    same behavior: 

     

    MX-80-1# run ping 2a00:8a00:6000:601b::9 interface ae0.0
    PING6(56=40+8+8 bytes) 2a00:8a00:6000:601b::11 --> 2a00:8a00:6000:601b::9
    ping: sendmsg: No route to host
    ping6: wrote 2a00:8a00:6000:601b::9 16 chars, ret=-1
    ping: sendmsg: No route to host
    ping6: wrote 2a00:8a00:6000:601b::9 16 chars, ret=-1
    ping: sendmsg: No route to host
    ping6: wrote 2a00:8a00:6000:601b::9 16 chars, ret=-1
    ping: sendmsg: No route to host
    ping6: wrote 2a00:8a00:6000:601b::9 16 chars, ret=-1
    ^C
    --- 2a00:8a00:6000:601b::9 ping6 statistics ---
    4 packets transmitted, 0 packets received, 100% packet loss

    [edit]

    additionally, I enabled ospfv3 beetween MX80 ae0.0 interface and vlan 132 on cisco L3 switch - same  situation. Route to appear to not be in the ipv6 routing table: 

     

     

    MX-80-1# run show route table inet6.0 2a00:8a00:6000:601b::9

    [edit]

    ...

     

     



  • 5.  RE: ipv6 - No route to host

    Posted 01-20-2016 05:48

    this is ipv6 details for vlan 132 on cisco: 

     

    cisco# sh ipv6 int vlan 132
    IPv6 Interface Status for VRF "default"(1)
    Vlan132, Interface status: protocol-up/link-up/admin-up, iod: 89
    IPv6 address:
    2a00:8a00:6000:601b::9/125 [VALID]
    IPv6 subnet: 2a00:8a00:6000:601b::8/125
    IPv6 link-local address: fe80::8e60:4fff:fe1b:a4c1 (default) [VALID]
    IPv6 virtual addresses configured: none
    IPv6 multicast routing: disabled
    IPv6 report link local: disabled
    IPv6 Forwarding feature: disabled
    IPv6 multicast groups locally joined:
    ff02::6 ff02::5 ff02::2 ff02::1
    ff02::1:ff00:9 ff02::1:ff1b:a4c1 ff02::1:ff00:8
    IPv6 multicast (S,G) entries joined: none
    IPv6 MTU: 9014 (using link MTU)
    IPv6 unicast reverse path forwarding: none
    IPv6 load sharing: none
    IPv6 interface statistics last reset: never
    IPv6 interface RP-traffic statistics: (forwarded/originated/consumed)
    Unicast packets: 0/24/24
    Unicast bytes: 0/2096/1592
    Multicast packets: 0/603383/124
    Multicast bytes: 0/57078878/9316

     

     

    that ip - 2a00:8a00:6000:601b::9/125 comes from subnet 2a00:8a00:6000:601b::8/125. It is first Ip that is available- however I am not sure - is it that first ipv6 address should be reserve in ipv6 for anycast? 



  • 6.  RE: ipv6 - No route to host
    Best Answer

    Posted 01-20-2016 13:15

    The next-hop address is not in the same subnet as the interface address and I believe that is part of the problem.

     

    2a00:8a00:6000:601b::11/125 is in the range 2a00:8a00:6000:601b:0000:0000:0000:0010-
    2a00:8a00:6000:601b:0000:0000:0000:0017

     

    2a00:8a00:6000:601b::9/125 is in the range 2a00:8a00:6000:601b:0000:0000:0000:0008-
    2a00:8a00:6000:601b:0000:0000:0000:000f

     

    So your static route on the Juniper is literally pointing to a next-hop the router does not know how to get to (which is why no route to host message).

     

    It is interesting the Cisco router can ping the juniper...but my guess is link-local addressing is come into play there. Either way, your next-hop should be reachable (on the same subnet as your gateway interface).

     

     



  • 7.  RE: ipv6 - No route to host

    Posted 01-20-2016 22:59

     

    heh - I can see my mistake now. I assigned 2a00:8a00:6000:601b::11/125 address belive that it is within the range: 2a00:8a00:6000:601b:0000:0000:0000:0008-
    2a00:8a00:6000:601b:0000:0000:0000:000f, becouse - I forgot to convert 11 in decimal to 11 in hex. 11 in hex would be B, not 11 🙂 

     

     



  • 8.  RE: ipv6 - No route to host

    Posted 01-20-2016 23:03

    sucess 🙂 

     

    MX-80-1# set interfaces ae0 unit 0 family inet6 address 2a00:8a00:6000:601b::B/125

    [edit]
    admin@MX-80-1-Feve3-Rack-21# commit
    commit complete

    [edit]
    MX-80-1# run ping 2a00:8a00:6000:601b::9
    PING6(56=40+8+8 bytes) 2a00:8a00:6000:601b::b --> 2a00:8a00:6000:601b::9
    16 bytes from 2a00:8a00:6000:601b::9, icmp_seq=1 hlim=64 time=0.732 ms
    16 bytes from 2a00:8a00:6000:601b::9, icmp_seq=2 hlim=64 time=1.813 ms
    16 bytes from 2a00:8a00:6000:601b::9, icmp_seq=3 hlim=64 time=1.202 ms
    16 bytes from 2a00:8a00:6000:601b::9, icmp_seq=4 hlim=64 time=0.765 ms
    16 bytes from 2a00:8a00:6000:601b::9, icmp_seq=5 hlim=64 time=0.984 ms
    16 bytes from 2a00:8a00:6000:601b::9, icmp_seq=6 hlim=64 time=0.989 ms
    ^C
    --- 2a00:8a00:6000:601b::9 ping6 statistics ---
    7 packets transmitted, 6 packets received, 14% packet loss
    round-trip min/avg/max/std-dev = 0.732/1.081/1.813/0.363 ms

     

    thanks mtighe - you point my head into wright direction !! 

     



  • 9.  RE: ipv6 - No route to host

    Posted 01-20-2016 18:54

    Could you please share  interface vlan configurations and configuration of the physical interface connecting Juniper router (if it is a point to point connection).