MPLS TE With ISIS lab verification issue

I am working on the above lab, however my traceroute from r1 to xr2 still goes thru r4:

R1#traceroute 20.20.20.20

Type escape sequence to abort.
Tracing the route to 20.20.20.20

  1 10.1.2.2 0 msec 0 msec 0 msec
  2 20.2.4.4 [MPLS: Labels 26/16000 Exp 0] 4 msec 0 msec 4 msec
  3 20.4.5.5 [MPLS: Labels 27/16000 Exp 0] 0 msec 0 msec 4 msec
  4 20.5.19.19 0 msec 4 msec 4 msec
  5 10.19.20.20 4 msec *  0 msec

 

even though TE data indicates otherwise:

R2#sh mpls traffic-eng topology path destination 19.19.19.19
Query Parameters:
  Destination: 19.19.19.19
    Bandwidth: 0
   Priorities: 0 (setup), 0 (hold)
     Affinity: 0x0 (value), 0xFFFFFFFF (mask)
Query Results:
  Min Bandwidth Along Path: 0 (kbps)
  Max Bandwidth Along Path: 75000 (kbps)
  Hop  0: 20.2.3.2            : affinity 00000000, bandwidth 75000 (kbps)
  Hop  1: 20.2.3.3            : affinity 00000000, bandwidth 75000 (kbps)
  Hop  2: 20.3.4.3            : affinity 00000000, bandwidth 75000 (kbps)
  Hop  3: 20.3.4.4            : affinity 00000000, bandwidth 75000 (kbps)
  Hop  4: 20.4.6.4            : affinity 00000000, bandwidth 75000 (kbps)
  Hop  5: 20.4.6.6            : affinity 00000000, bandwidth 75000 (kbps)
  Hop  6: 20.6.19.6           : affinity 00000000, bandwidth 75000 (kbps)
  Hop  7: 20.6.19.19          : affinity 00000000, bandwidth 0 (kbps)
  Hop  8: 19.19.19.19

 

AM I MISSING SOMETHING?

Comments

  • Cab you show us the Show ip route 19.19.19.19... to check weather 19.19.19.19 is taking tunnel or normal IGP path..

  • R2#sh ip ro 19.19.19.19
    Routing entry for 19.19.19.19/32
      Known via "static", distance 1, metric 0 (connected)
      Routing Descriptor Blocks:
      * directly connected, via Tunnel21
          Route metric is 0, traffic share count is 1

    -----------------------

    I fixed it, but not sure if that's a hack or not. Because the solution provided by INE is diff.

    I enabled mpls on the tunnel interface...

  • Actualy I think this is a bug, as it is not required to enable mpls on the tunnel interface, it is very enough to do the mpls traffic-engineering mode on

     

    Can you provide us with the full configuration of the tunnel, explicit policy and the static route if defined?

  • Can you provide us with the full configuration of the tunnel, explicit policy and the static route if defined?

  • You are 100% sure that you are using tunnel 21 interface for the mpls tunnel and not another id?

  • scroll up....

  • Sorry but what I see is that you configured a static route on an interface tunnel 21, from your output I don't see that you have a working the tunnel the with I'd 21...

    scroll up....

     

  • Take a look at the topology output.
    It implies a working tunnel...

    Sent from my iPhone

    On Mar 3, 2013, at 5:55 PM, vspaziani <[email protected]> wrote:

    Sorry but what I see is that you configured a static route on an intended tunnel 21, from your output I don't see that you have a working the tunnel the with I'd 21...

    image franqe:

    scroll up....

     




    INE - The Industry Leader in CCIE Preparation

    http://www.INE.com



    Subscription information may be found at:

    http://www.ieoc.com/forums/ForumSubscriptions.aspx
  • MPlS IP is not required under traffic-eng tunnel , Rsvp is taking care here for Label distribution .. there might anyother issue..simply enabling mpls ip under tunnel it means ur making new LDP neighbour ship so RSVP has no Role anymore here...

     

    Paste your XR and IOS route Config ...

     

     

  • did you add "tunn mpls traffic-eng autoroute destination" and not "autoroute announce"?   assuming you're doing inter-area / inter-level TE.   haven't seen your config's.



    Jason



    On Thu, Feb 28, 2013 at 8:16 AM, franqe <[email protected]> wrote:

    I am working on the above lab, however my traceroute from r1 to xr2 still goes thru r4:

    R1#traceroute 20.20.20.20

    Type escape sequence to abort.
    Tracing the route to 20.20.20.20

      1 10.1.2.2 0 msec 0 msec 0 msec
      2 20.2.4.4 [MPLS: Labels 26/16000 Exp 0] 4 msec 0 msec 4 msec
      3 20.4.5.5 [MPLS: Labels 27/16000 Exp 0] 0 msec 0 msec 4 msec

      4 20.5.19.19 0 msec 4 msec 4 msec
      5 10.19.20.20 4 msec *  0 msec

     

    even though TE data indicates otherwise:

    R2#sh mpls traffic-eng topology path destination 19.19.19.19
    Query Parameters:
      Destination: 19.19.19.19
        Bandwidth: 0
       Priorities: 0 (setup), 0 (hold)
         Affinity: 0x0 (value), 0xFFFFFFFF (mask)

    Query Results:
      Min Bandwidth Along Path: 0 (kbps)
      Max Bandwidth Along Path: 75000 (kbps)
      Hop  0: 20.2.3.2            : affinity 00000000, bandwidth 75000 (kbps)
      Hop  1: 20.2.3.3            : affinity 00000000, bandwidth 75000 (kbps)

      Hop  2: 20.3.4.3            : affinity 00000000, bandwidth 75000 (kbps)
      Hop  3: 20.3.4.4            : affinity 00000000, bandwidth 75000 (kbps)
      Hop  4: 20.4.6.4            : affinity 00000000, bandwidth 75000 (kbps)

      Hop  5: 20.4.6.6            : affinity 00000000, bandwidth 75000 (kbps)
      Hop  6: 20.6.19.6           : affinity 00000000, bandwidth 75000 (kbps)
      Hop  7: 20.6.19.19          : affinity 00000000, bandwidth 0 (kbps)

      Hop  8: 19.19.19.19

     

    AM I MISSING SOMETHING?




    INE - The Industry Leader in CCIE Preparation

    http://www.INE.com



    Subscription information may be found at:

    http://www.ieoc.com/forums/ForumSubscriptions.aspx

Sign In or Register to comment.