in

IEOC - Internetwork Expert's Online Community

Welcome to Internetwork Expert's Online Community - IEOC - a place for CCIE and CCENT candidates to connect, share, and learn. Our Online Community features CCIE forums and discussions for all tracks including Routing & Switching, Voice, Security, Service Provider, and Storage. Through these online communities you can discuss your questions with thousands of your peers, hundreds of CCIE's and Internetwork Expert's own team of world renowned CCIE instructors and authors, Brian Dennis - Quintuple CCIE #2210, Scott Morris - Quad CCIE #4713, Brian McGahan – Triple CCIE #8593, Petr Lapukhov - Quad CCIE #16379, Anthony Sequeira - CCIE #15626, Keith Barker - Dual CCIE #6783, and Marvin Greenlee - Triple CCIE #12237.
Latest post 04-08-2009 1:15 PM by cableman. 3 replies.
Page 1 of 1 (4 items)
Sort Posts: Previous Next
  • 12-06-2008 1:12 AM

    4.2 MPLS Tunneling

    Hi there,

    I have the exact config as per solution but upon bring down the R9 to R1 link, it's seems to be that the mpls te link produce this kind of error:

     

    Rack1R1#
    00:37:07: %MPLS_TE-3-CONSISTENCY: Path lookup returned path that didn't pass verification: Tunnel14 
    -Traceback= 6076D55C 61333B20 61333E50 61335FA8 6133AAD0 61346BC4 6134708C 61347370 6133F428 6133F764
    Rack1R1#
    00:37:09: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.9.9 on ATM4/0.19 from FULL to DOWN, Neighbor Down: Dead timer expired
    Rack1R1#
    00:37:18: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.9.9 on ATM4/0.19 from LOADING to FULL, Loading Done
    Rack1R1#sh run
    00:37:20: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel14, changed state to up

    Once, I bring up the R9 to R1 link, tunnel14 seems to be up.

    Here is my configuration on tunel:

     

    Rack1R1#sh run int tun14
    Building configuration...

    Current configuration : 372 bytes
    !
    interface Tunnel14
     ip unnumbered Loopback0
     tunnel destination 192.168.4.4
     tunnel mode mpls traffic-eng
     tunnel mpls traffic-eng autoroute announce
     tunnel mpls traffic-eng priority 7 7
     tunnel mpls traffic-eng bandwidth  1000
     tunnel mpls traffic-eng path-option 1 explicit name R1-R9-R2-R3-R4
     tunnel mpls traffic-eng path-option 2 dynamic
     no clns route-cache
    end

    Since the question dictates if R9 is down, it should be routed as necessary .. I was thinking the route should take path-option 2 dynamically, but it seems to travel on normal OSPF route.

     

    Rack1R1#traceroute 192.168.4.4

    Type escape sequence to abort.
    Tracing the route to 192.168.4.4

      1 129.1.123.3 8 msec 12 msec 20 msec
      2 129.1.34.4 32 msec *  28 msec

    Any ideas ?

    Thank you.

    • Post Points: 20
  • 12-06-2008 2:29 AM In reply to

    Re: 4.2 MPLS Tunneling

    when the link between R1 and R9 goes down it should go through R2 - but it seems it cannot - "Path lookup returned path that didn't pass verification"

    problem could be configuration missing on R2 (RSVP or other...)

    you should check that and if you cannot locate the problem post here your full "running-configuration" for R1 + R2 + R9 and we will take a look ...

    off-course i could be wrong ....

    m2600:

    Hi there,

    I have the exact config as per solution but upon bring down the R9 to R1 link, it's seems to be that the mpls te link produce this kind of error:

     

    Rack1R1#
    00:37:07: %MPLS_TE-3-CONSISTENCY: Path lookup returned path that didn't pass verification: Tunnel14 
    -Traceback= 6076D55C 61333B20 61333E50 61335FA8 6133AAD0 61346BC4 6134708C 61347370 6133F428 6133F764
    Rack1R1#
    00:37:09: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.9.9 on ATM4/0.19 from FULL to DOWN, Neighbor Down: Dead timer expired
    Rack1R1#
    00:37:18: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.9.9 on ATM4/0.19 from LOADING to FULL, Loading Done
    Rack1R1#sh run
    00:37:20: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel14, changed state to up

    Once, I bring up the R9 to R1 link, tunnel14 seems to be up.

    Here is my configuration on tunel:

     

    Rack1R1#sh run int tun14
    Building configuration...

    Current configuration : 372 bytes
    !
    interface Tunnel14
     ip unnumbered Loopback0
     tunnel destination 192.168.4.4
     tunnel mode mpls traffic-eng
     tunnel mpls traffic-eng autoroute announce
     tunnel mpls traffic-eng priority 7 7
     tunnel mpls traffic-eng bandwidth  1000
     tunnel mpls traffic-eng path-option 1 explicit name R1-R9-R2-R3-R4
     tunnel mpls traffic-eng path-option 2 dynamic
     no clns route-cache
    end

    Since the question dictates if R9 is down, it should be routed as necessary .. I was thinking the route should take path-option 2 dynamically, but it seems to travel on normal OSPF route.

     

    Rack1R1#traceroute 192.168.4.4

    Type escape sequence to abort.
    Tracing the route to 192.168.4.4

      1 129.1.123.3 8 msec 12 msec 20 msec
      2 129.1.34.4 32 msec *  28 msec

    Any ideas ?

    Thank you.

    • Post Points: 20
  • 12-07-2008 4:05 AM In reply to

    Re: 4.2 MPLS Tunneling

    Hi,

    Thanks giving me hints. Managed to solve, on R3 need to do remove ip rsvp bandwidth and add it again. The links went up. Funny on dynamips :)

     

    Thanks again.

    • Post Points: 20
  • 04-08-2009 1:15 PM In reply to

    Re: 4.2 MPLS Tunneling

    According to the archived forums, the problem is Cisco doesn't support p2mp LSP. So all you need to do is to use "ip ospf network broadcast" for R1, R2 and R3, the tunnel would re-route if the explicit route didn't work.

     

    • Post Points: 5
Page 1 of 1 (4 items)
IEOC CCIE Forums Internetwork Expert CCIE Training
About IEOC | Terms of Use | RSS | Privacy Policy
© 2010 Internetwork Expert, Inc. All Rights Reserved