cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1382
Views
0
Helpful
0
Replies
Highlighted

6PE MPLS-TE recursive lookup problem

Hi all

I've run into a problem and hope something can point me in the right direction. The topology is below:

Screen Shot 2013-01-15 at 11.00.24 AM.png

The scenario is this. The core is running OSPF and MPLS-TE (tunnel0 between PE1 and PE2). I'm trying to get 6PE working between the two "islands".

CE1 (AS300) is running eBGP with PE1 (AS100) and CE2 (AS400) is running eBGP with PE2 (AS100).

PE1 and PE2 are running iBGP between their respective loopback interfaces (IPv4) for address-family ipv6 unicast.

I've verified MPLS-TE:

PE1#sh mpls traffic-eng tunnels tunnel 0

Name: PE1_t0                              (Tunnel0) Destination: 2.2.2.2

  Status:

    Admin: up         Oper: up     Path: valid       Signalling: connected

    path option 5, type dynamic (Basis for Setup, path weight 2)

  Config Parameters:

    Bandwidth: 128      kbps (Global)  Priority: 7  7   Affinity: 0x0/0xFFFF

    Metric Type: TE (default)

    AutoRoute:  enabled   LockDown: disabled  Loadshare: 128      bw-based

    auto-bw: disabled

  InLabel  :  -

  OutLabel : FastEthernet1/0, 17

  RSVP Signalling Info:

       Src 1.1.1.1, Dst 2.2.2.2, Tun_Id 0, Tun_Instance 17

    RSVP Path Info:

      My Address: 10.1.5.1  

      Explicit Route: 10.1.5.5 10.2.5.5 10.2.5.2 2.2.2.2

      Record Route:  NONE

      Tspec: ave rate=128 kbits, burst=1000 bytes, peak rate=128 kbits

    RSVP Resv Info:

      Record Route:  NONE

      Fspec: ave rate=128 kbits, burst=1000 bytes, peak rate=128 kbits

  Shortest Unconstrained Path Info:

    Path Weight: 2 (TE)

    Explicit Route: 10.1.5.1 10.1.5.5 10.2.5.5 10.2.5.2

                    2.2.2.2

  History:

    Tunnel:

      Time since created: 1 hours, 17 minutes

      Time since path change: 9 minutes, 43 seconds

    Current LSP:

      Uptime: 9 minutes, 43 seconds

      Selection: reoptimation

    Prior LSP:

      ID: path option 5 [14]

      Removal Trigger: label reservation removed

PE1#sh ip cef 2.2.2.2

2.2.2.2/32, version 15, epoch 0, attached

0 packets, 0 bytes

  tag information set

    local tag: tunnel-head

    fast tag rewrite with Tu0, point2point, tags imposed: {17}

  via Tunnel0, 0 dependencies

    valid adjacency

    tag rewrite with Tu0, point2point, tags imposed: {17}

PE1#trace 2.2.2.2 so lo0

Type escape sequence to abort.

Tracing the route to 2.2.2.2

  1 10.1.5.5 [MPLS: Label 17 Exp 0] 40 msec 28 msec 24 msec

  2 10.2.5.2 28 msec *  100 msec

I'm receiving the IPv6 prefixes with the correct next hop:

PE1#sh bgp ipv6 uni | b Network

   Network          Next Hop            Metric LocPrf Weight Path

*> 2001:1::1/128    ::                       0         32768 ?

*>i2001:2::2/128    ::FFFF:2.2.2.2           0    100      0 ?

*> 2001:3::/64      2001:13::3               0             0 300 ?

*>i2001:4::/64      ::FFFF:2.2.2.2           0    100      0 400 ?

*> 2001:13::/64     ::                       0         32768 ?

*>i2001:24::/64     ::FFFF:2.2.2.2           0    100      0 ?

and the labels:

PE1#sh bgp ipv6 uni labels

   Network          Next Hop      In label/Out label

   2001:1::1/128    ::              18/nolabel

   2001:2::2/128    ::FFFF:2.2.2.2  nolabel/19

   2001:3::/64      2001:13::3      19/nolabel

   2001:4::/64      ::FFFF:2.2.2.2  nolabel/20

   2001:13::/64     ::              17/nolabel

   2001:24::/64     ::FFFF:2.2.2.2  nolabel/18

The problem seem to be though that the recursive routing is not "working":

PE1#sh ipv6 cef 2001:2::2/128

2001:2::2/128

     nexthop ::FFFF:2.2.2.2

The debug (debug mpls lfib struct) gives me the following output:

*Jan 15 11:12:09.563: TFIB RES: resolve 2001:2::2/128 -> 2.2.2.2 parent tag has no label binding

*Jan 15 11:12:09.571: TFIB RES: resolve 2001:4::/64 -> 2.2.2.2 parent tag has no label binding

*Jan 15 11:12:09.575: TFIB RES: resolve 2001:24::/64 -> 2.2.2.2 parent tag has no label binding

*Jan 15 11:12:09.579: 6PE: CEF entry added 2001:2::2/128 intag=16777221

*Jan 15 11:12:09.579: 6PE: CEF entry added 2001:3::/64 intag=201326611

*Jan 15 11:12:09.583: LFIB: create tag rewrite: inc 19,outg Exp_null

*Jan 15 11:12:09.583: 6PE: create tag_rew: tag 19 outidb Fa1/1

*Jan 15 11:12:09.583: LFIB: delete tag rew, incoming tag 19

*Jan 15 11:12:09.583: LFIB: delete tag rew, incoming tag 19

*Jan 15 11:12:09.587: 6PE: CEF entry added 2001:4::/64 intag=16777221

*Jan 15 11:12:09.591: 6PE: CEF entry added 2001:24::/64 intag=16777221

It the first three lines that raised my eyebrowes.

I've attached the configs

Anyone got a clue? :-)

Cheers,

Hannes

0 REPLIES 0