Routing

last person joined: yesterday 

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.  Help with 6PE data plane

    Posted 09-22-2014 10:51

    Hi,

     

    I'm having trouble forwarding packets between two IPv6 islands in a simple setup. The control plane seems to be working fine as i'm learning the routes in each of the CEs but can't ping the remote CE from the local CE and vice versa.

     

    Here's my topology:

     

    C3---R5---R7---R8---P1

     

    C3 lo0.3 - fd18:cccc:dddd:2:f::1/128

    P1 lo0.36 - fd01:aaaa:bbbb:0:f::1/128

     

    root@C3# run show bgp summary                    
    Groups: 1 Peers: 1 Down peers: 0
    Table          Tot Paths  Act Paths Suppressed    History Damp State    Pending
    inet6.0               16         16          0          0          0          0
    Peer                     AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn State|#Active/Received/Accepted/Damped...
    8000::2               54591        252        250       0       0     1:51:00 Establ
      inet6.0: 16/16/16/0
    
    [edit]
    root@C3# run show route fd01:aaaa:bbbb:0:f::1    
    
    inet6.0: 38 destinations, 38 routes (38 active, 0 holddown, 0 hidden)
    + = Active Route, - = Last Active, * = Both
    
    fd01:aaaa:bbbb:0:f::/80
                       *[BGP/170] 00:31:22, localpref 100
                          AS path: 54591 110047427 I
                        > to 8000::2 via ge-0/0/5.303
    root@R5# run show route fd18:cccc:dddd:2:f::1 extensive 
    
    inet6.0: 38 destinations, 38 routes (38 active, 0 holddown, 0 hidden)
    fd18:cccc:dddd:2:f::/80 (1 entry, 1 announced)
    TSI:
    KRT in-kernel fd18:cccc:dddd:2:f::/80 -> {8000::1}
    Page 0 idx 1 Type 1 val 9381b74
        Flags: Nexthop Change
        Nexthop: Self
        Localpref: 100
        AS path: [54591] 64514 I
        Communities:
    Path fd18:cccc:dddd:2:f:: from 8000::1 Vector len 4.  Val: 1
            *BGP    Preference: 170/-101
                    Next hop type: Router, Next hop index: 571
                    Address: 0x934c880
                    Next-hop reference count: 48
                    Source: 8000::1
                    Next hop: 8000::1 via ge-0/0/5.303, selected
                    State: <Active Ext>
                    Local AS: 54591 Peer AS: 64514
                    Age: 1:55:31 
                    Task: BGP_64514.8000::1+179
                    Announcement bits (3): 0-KRT 3-BGP_RT_Background 4-Resolve tree 4 
                    AS path: 64514 I
                    Accepted
                    Localpref: 100
                    Router ID: 172.31.47.1
    
    [edit]
    root@R5# run show route fd01:aaaa:bbbb:0:f::1 extensive 
    
    inet6.0: 38 destinations, 38 routes (38 active, 0 holddown, 0 hidden)
    fd01:aaaa:bbbb:0:f::/80 (1 entry, 1 announced)
    TSI:
    KRT in-kernel fd01:aaaa:bbbb:0:f::/80 -> {indirect(262142)}
    Page 0 idx 0 Type 1 val 9381768
        Nexthop: Self
        AS path: [54591] 110047427 I
        Communities:
    Path fd01:aaaa:bbbb:0:f:: from 172.30.5.8 Vector len 4.  Val: 0
            *BGP    Preference: 170/-101
                    Next hop type: Indirect
                    Address: 0x934d060
                    Next-hop reference count: 48
                    Source: 172.30.5.8
                    Next hop type: Router, Next hop index: 527
                    Next hop: 172.30.0.42 via ge-0/0/4.157 weight 0x1, selected
                    Label-switched-path R5-to-R8
                    Label operation: Push 2, Push 299840(top)
                    Label TTL action: prop-ttl, prop-ttl(top)
                    Protocol next hop: ::ffff:172.30.5.8
                    Push 2
                    Indirect next hop: 95bc000 262142
                    State: <Active Int Ext>
                    Local AS: 54591 Peer AS: 54591
                    Age: 2:18:57    Metric2: 20 
                    Task: BGP_54591.172.30.5.8+179
                    Announcement bits (3): 0-KRT 3-BGP_RT_Background 4-Resolve tree 4 
                    AS path: 110047427 I
                    Accepted
                    Route Label: 2
                    Localpref: 100
                    Router ID: 172.30.5.8
                    Indirect next hops: 1
                            Protocol next hop: ::ffff:172.30.5.8 Metric: 20
                            Push 2
                            Indirect next hop: 95bc000 262142
                            Indirect path forwarding next hops: 1
                                    Next hop type: Router
                                    Next hop: 172.30.0.42 via ge-0/0/4.157 weight 0x1
                            ::ffff:172.30.5.8/128 Originating RIB: inet6.3
                              Metric: 20                      Node path count: 1
                              Forwarding nexthops: 1
                                    Nexthop: 172.30.0.42 via ge-0/0/4.157

     

    root@R8# run show route fd18:cccc:dddd:2:f::1 extensive 
    
    inet6.0: 36 destinations, 36 routes (36 active, 0 holddown, 0 hidden)
    fd18:cccc:dddd:2:f::/80 (1 entry, 1 announced)
    TSI:
    KRT in-kernel fd18:cccc:dddd:2:f::/80 -> {indirect(262142)}
    Page 0 idx 0 Type 1 val 93817bc
        Nexthop: Self
        AS path: [54591] 64514 I
        Communities:
    Path fd18:cccc:dddd:2:f:: from 172.30.5.5 Vector len 4.  Val: 0
            *BGP    Preference: 170/-101
                    Next hop type: Indirect
                    Address: 0x934cd00
                    Next-hop reference count: 48
                    Source: 172.30.5.5
                    Next hop type: Router, Next hop index: 528
                    Next hop: 172.30.0.45 via ge-0/0/4.178 weight 0x1, selected
                    Label-switched-path R8-to-R5
                    Label operation: Push 2, Push 299856(top)
                    Label TTL action: prop-ttl, prop-ttl(top)
                    Protocol next hop: ::ffff:172.30.5.5
                    Push 2
                    Indirect next hop: 95bc000 262142
                    State: <Active Int Ext>
                    Local AS: 54591 Peer AS: 54591
                    Age: 1:57:01    Metric2: 20 
                    Task: BGP_54591.172.30.5.5+63047
                    Announcement bits (3): 0-KRT 3-BGP_RT_Background 4-Resolve tree 4 
                    AS path: 64514 I
                    Accepted
                    Route Label: 2
                    Localpref: 100
                    Router ID: 172.30.5.5
                    Indirect next hops: 1
                            Protocol next hop: ::ffff:172.30.5.5 Metric: 20
                            Push 2
                            Indirect next hop: 95bc000 262142
                            Indirect path forwarding next hops: 1
                                    Next hop type: Router
                                    Next hop: 172.30.0.45 via ge-0/0/4.178 weight 0x1
                            ::ffff:172.30.5.5/128 Originating RIB: inet6.3
                              Metric: 20                      Node path count: 1
                              Forwarding nexthops: 1
                                    Nexthop: 172.30.0.45 via ge-0/0/4.178
    
    [edit]
    root@R8# run show route fd01:aaaa:bbbb:0:f::1 extensive 
    
    inet6.0: 36 destinations, 36 routes (36 active, 0 holddown, 0 hidden)
    fd01:aaaa:bbbb:0:f::/80 (1 entry, 1 announced)
    TSI:
    KRT in-kernel fd01:aaaa:bbbb:0:f::/80 -> {fe80::20c:2901:36f1:dae0}
    Page 0 idx 1 Type 1 val 93814ac
        Flags: Nexthop Change
        Nexthop: Self
        Localpref: 100
        AS path: [54591] 110047427 I
        Communities:
    Path fd01:aaaa:bbbb:0:f:: from fe80::20c:2901:36f1:dae0 Vector len 4.  Val: 1
            *BGP    Preference: 170/-101
                    Next hop type: Router, Next hop index: 554
                    Address: 0x934c760
                    Next-hop reference count: 48
                    Source: fe80::20c:2901:36f1:dae0
                    Next hop: fe80::20c:2901:36f1:dae0 via ge-0/0/5.310, selected
                    State: <Active Ext>
                    Local AS: 54591 Peer AS: 110047427
                    Age: 2:20:09 
                    Task: BGP_110047427.fe80::20c:2901:36f1:dae0+179
                    Announcement bits (3): 0-KRT 3-BGP_RT_Background 4-Resolve tree 4 
                    AS path: 110047427 I
                    Accepted
                    Localpref: 100
                    Router ID: 172.17.15.1

     

    root@P1# run show bgp summary                    
    Groups: 1 Peers: 1 Down peers: 0
    Table          Tot Paths  Act Paths Suppressed    History Damp State    Pending
    inet6.0               16         16          0          0          0          0
    Peer                     AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn State|#Active/Received/Accepted/Damped...
    fe80::20c:2901:3655:d726       54591        322        312       0       1     2:20:29 Establ
      inet6.0: 16/16/16/0
    
    [edit]
    root@P1# run show route fd18:cccc:dddd:2:f::1    
    
    inet6.0: 36 destinations, 36 routes (36 active, 0 holddown, 0 hidden)
    + = Active Route, - = Last Active, * = Both
    
    fd18:cccc:dddd:2:f::/80
                       *[BGP/170] 00:37:48, localpref 100
                          AS path: 54591 64514 I
                        > to fe80::20c:2901:3655:d726 via ge-0/0/5.310

     As you can see, i'm learning the routes via BGP in each of the CEs but ping from one loopback to another is not working.

     

    root@C3# run ping fd01:aaaa:bbbb:0:f::1 source fd18:cccc:dddd:2:f::1 
    PING6(56=40+8+8 bytes) fd18:cccc:dddd:2:f::1 --> fd01:aaaa:bbbb:0:f::1
    ^C
    --- fd01:aaaa:bbbb:0:f::1 ping6 statistics ---
    10 packets transmitted, 0 packets received, 100% packet loss

     

    Any help would be greatly appreciated. Thanks!



  • 2.  RE: Help with 6PE data plane

    Posted 09-22-2014 12:08

    Hi,

     

     

    Did you enable family mpls on your edge routers on the core facing interfaces?

    More specifically family mpls must be added:

    • on R5 : on the link R5-R7
    • on R8 : on the link R8-R7

     

     

    --
    If this post solves your problem, please mark this post as "Accepted Solution".
    Kudos are appreciated



  • 3.  RE: Help with 6PE data plane

    Posted 09-22-2014 12:17

    Yes, I have MPLS configured in the core interfaces of R5 and R8. The LSPs are up as well.

     

    root@R5# show protocols mpls 
    ipv6-tunneling;
    label-switched-path R5-to-R8 {
        to 172.30.5.8;
    }
    interface ge-0/0/4.158;
    interface ge-0/0/4.157;
    
    [edit]
    root@R5# run show mpls lsp 
    Ingress LSP: 1 sessions
    To              From            State Rt P     ActivePath       LSPname
    172.30.5.8      172.30.5.5      Up     0 *                      R5-to-R8
    Total 1 displayed, Up 1, Down 0
    
    Egress LSP: 1 sessions
    To              From            State   Rt Style Labelin Labelout LSPname 
    172.30.5.5      172.30.5.8      Up       0  1 FF       3        - R8-to-R5
    Total 1 displayed, Up 1, Down 0
    
    Transit LSP: 0 sessions
    Total 0 displayed, Up 0, Down 0

     

    root@R8# show protocols mpls 
    ipv6-tunneling;
    label-switched-path R8-to-R5 {
        to 172.30.5.5;
    }
    interface ge-0/0/4.158;
    interface ge-0/0/4.178;
    
    [edit]
    root@R8# run show mpls lsp 
    Ingress LSP: 1 sessions
    To              From            State Rt P     ActivePath       LSPname
    172.30.5.5      172.30.5.8      Up     0 *                      R8-to-R5
    Total 1 displayed, Up 1, Down 0
    
    Egress LSP: 1 sessions
    To              From            State   Rt Style Labelin Labelout LSPname 
    172.30.5.8      172.30.5.5      Up       0  1 FF       3        - R5-to-R8
    Total 1 displayed, Up 1, Down 0
    
    Transit LSP: 0 sessions
    Total 0 displayed, Up 0, Down 0

     

     

     



  • 4.  RE: Help with 6PE data plane
    Best Answer

    Posted 09-22-2014 12:23

    Hi again,

     

    My first post was not correct. I meant to write the following:

     

    Did you enable family inet6 on your edge routers on the core facing interfaces?

    More specifically family inet6 must be added:

    • on R5 : on the link R5-R7
    • on R8 : on the link R8-R7

     

     

    --
    If this post solves your problem, please mark this post as "Accepted Solution".
    Kudos are appreciated

     

     

     

     



  • 5.  RE: Help with 6PE data plane

    Posted 09-22-2014 13:56
    Perfect! I was indeed missing the "family inet6" statement on the core facing interfaces.

    It is a bit counter intuitive since the IPv6 traffic is getting tunneled through the LSP in the core and technically the core facing interfaces are only pushing on labels. But now that I look back at the documentations it has "family inet6" defined on all the core facing interfaces.

    Thanks again for all your help!!!

    Sent from my iPhone