cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1357
Views
0
Helpful
9
Replies

VPN over a TE Tunnel When the TE Tunnel Is from PE1 to PE2 on XR

oteros
Level 1
Level 1

Hi, everyone, i need to implement this over XR. I tryed to do , as this document but it did not work.

http://www.cisco.com/en/US/tech/tk436/tk428/technologies_tech_note09186a0080125b01.shtml#case1

Do anyone, know where is this document for XR ?? or if it´s supported for XR. Thanks very much.

9 Replies 9

Adam Vitkovsky
Level 3
Level 3

See how they check the next-hop of the VPN route (route in the VRF) whether it is reachable via the tunnel-te interface

Do you see that?

PE1# show cef vrf aqua 172.16.13.13

via 10.11.11.11

PE1# show route 10.11.11.11 
* 10.11.11.11, from 10.11.11.11, via Tunnel0

PE1# show mpls forwarding int tunnel-te0
Local Outgoing   Prefix           Bytes tag Outgoing  Next Hop 
tag   tag or VC   or Tunnel Id     switched   interface 
21     Pop tag     10.11.11.11/32   0         Tu0       point2point 

This is accomplished by the command:

int tunnel-te 0
 autoroute announce 

Same has to be true for the opposite PE2

Since the traffic-engineering tunnel is unidirectional you have to manually configure a TE-tunnel in the opposite direction from PE2 to PE1

adam

i see,

PE1# show mpls forwarding int tunnel-te0
Local Outgoing   Prefix           Bytes tag Outgoing  Next Hop 
tag   tag or VC   or Tunnel Id     switched   interface 
21     no label 10.11.11.11/32   0         Tu0       point2point 

i tryed with ip route, and autoroute announce in both sides.
Should i configure anything else?? i only enable mpls over the tunnel

You see the “no label” in the outgoing direction.
That is always a sign that mpls forwarding is not working properly between the two routers
See the P1 should have send you the implicit pop label for the NH prefix (over the LDP session) 
which would translate into “Pop tag“ in the outgoing direction as seen in the output I have posted.
 
The mpls forwarding/LDP has to be enabled on all the interfaces interconnecting 
PE1 and P1 and P2 and PE2

PE1
mpls ldp
 interface GigabitEthernet0/x/x/x -> to P1
 
P1
mpls ldp
 interface GigabitEthernet0/x/x/x -> to PE1
 interface GigabitEthernet0/x/x/y -> to P2
 
you can verify the LDP neighbors with cmd:
sh mpls ldp nei
adam

yes every ldp is up.

I enabled also


PE1
mpls ldp
 interface GigabitEthernet0/x/x/x -> to P1
interface tunnel0 -> to PE2
 
PE2
mpls ldp
interface tunnel0 -> to PE1


I know that should not be necesary, but i want to know if i´m missing somenting else in the configuration.

I’m sorry to confuse things with my previous post

Actually The pop-label should be allocated by PE2 which is not happening for some reason.

Please show me the output from both PE routers:

PE1

sh mpls for prefix 10.11.11.11/32 det

PE2

sh mpls for prefix 10.2.2.2/32 det
I’m interested in: Label Stack (Top -> Bottom):
 

And

PE1& PE2

sh ip rsvp reservation detail

I’m interested in:

Resource:

Labels: Local downstream:

And yes you can remove the “mpls ip” from the tunnel interface on both PE routers as it is not needed

Also you don’t need the static routes as “autoroute announce” will take care of the routing

adam

adam

hI, here you are, i´m seeing that XR is not puting the next-hop in the reservation, this is normal ?

RP/0/0/CPU0:PE2#sh mpls forwarding prefix 11.11.0.1/32 det

Wed Nov  6 22:38:18.605 SGT

Local  Outgoing    Prefix             Outgoing     Next Hop        Bytes      

Label  Label       or ID              Interface                    Switched   

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

16000  Pop         11.11.0.1/32         tt22         11.11.0.1         1586       

     Updated Nov  6 22:24:10.875

     Version: 186, Priority: 1

     MAC/Encaps: 14/18, MTU: 1500

     Label Stack (Top -> Bottom): { 16010 Imp-Null }

     Packets Switched: 30

RP/0/0/CPU0:PE2#sh  rsvp reservation detail

RESV: IPv4-LSP Session addr: 11.11.0.2. TunID: 22. LSPId: 1.

Source addr: 11.11.0.2. ExtID: 11.11.0.1.

Input adjusted interface: No. Input physical interface: No.

Next hop: 0.0.0.0 (lih: 0x0).

Style: Shared-Explicit. Service: Controlled-Load.

Rate: 5000000 bits/sec. Burst: 1K bytes. Peak: 5M bits/sec.

MTU min: 0, max: 1500 bytes.

Flags: Local Receiver.

State expires in 0.000 sec.

Policy:  Accepted. Policy source(s): Default.

Header info: RSVP TTL=255. IP TTL=255. Flags: 0x0. TOS=0xff.

Resource:

  Labels: Local downstream: 3.

RP/0/0/CPU0:PE2#SH RUN INT TUNNel-TE22

Wed Nov  6 22:50:58.087 SGT

interface tunnel-te22

ipv4 unnumbered Loopback0

autoroute announce

destination 11.11.0.1

path-option 1 explicit name R2_R1

!

RP/0/0/CPU0:PE2#SHOW ROUTE 11.11.0.1

Wed Nov  6 22:53:13.105 SGT

Routing entry for 11.11.0.1/32

  Known via "isis abc", distance 115, metric 40, type level-1

  Installed Nov  6 22:24:10.865 for 00:29:02

  Routing Descriptor Blocks

    11.11.0.1, from 11.11.0.1, via tunnel-te22

      Route metric is 40

  No advertising protos.

PE1 #sh mpls forwarding-table 11.11.0.2 det
Local      Outgoing   Prefix           Bytes Label   Outgoing   Next Hop   
Label      Label      or Tunnel Id     Switched      interface             
24         No Label   11.11.0.2/32       0             Tu22       point2point
        MAC/Encaps=14/18, MRU=1500, Label Stack{16012}, via Et0/1
        0281EDC511EFAABBCC006C108847 03E8C000
        No output feature configured

PE1#sh ip rsvp reservation det
Reservation:
  Tun Dest:   11.11.0.2  Tun ID: 22  Ext Tun ID: 11.11.0.1
  Tun Sender: 11.11.0.1  LSP ID: 1
  Next Hop: 9.9.48.4 on Ethernet0/1
  Label: 16012 (outgoing)
  Reservation Style is Shared-Explicit, QoS Service is Controlled-Load
  Resv ID handle: 0500040E.
  Created: 15:12:43 EST Sun Nov 3 2013
  Average Bitrate is 5M bits/sec, Maximum Burst is 1K bytes
  Min Policed Unit: 0 bytes, Max Pkt Size: 1500 bytes
  Status:
  Policy: Accepted. Policy source(s): MPLS/TE

PE1#sh run int tunnel 22

Building configuration...

Current configuration : 290 bytes

!

interface Tunnel22

ip unnumbered Loopback0

tunnel mode mpls traffic-eng

tunnel destination 11.11.0.2

tunnel mpls traffic-eng autoroute announce

tunnel mpls traffic-eng path-option 1 explicit name R1_R2

PE1#SH IP ROUTE 11.11.0.2

Routing entry for 11.11.0.2/32

  Known via "isis", distance 115, metric 30, type level-1

  Redistributing via isis

  Last update from 9.9.0.2 on Tunnel82, 00:24:03 ago

  Routing Descriptor Blocks:

  * 11.11.0.2, from 11.11.0.2, 00:24:03 ago, via Tunnel22

      Route metric is 30, traffic share count is 1

Hi,

In the PE1#SH IP ROUTE 11.11.0.2 output

Why the route is known via 9.9.0.2 on Tunnel82 <- what is tunnel82 please?

I believe it should be more like:

Last update from 11.11.0.2 on Tunnel22

Also regarding the “sh ip rsvp reservation det” outputs have you selected and copied only information related to PE’s local tunnel?

Because normally the outputs should list the opposite side tunnel (tunnel form the remote PE) as well.

adam

adam

Sorry , someone change the config. Now it´s ok

PE1#SH IP ROUTE 11.11.0.2

Routing entry for 11.11.0.2/32

  Known via "isis", distance 115, metric 30, type level-1

  Redistributing via isis

  Last update from 11.11.0.2 on Tunnel22, 00:14:07 ago

  Routing Descriptor Blocks:

  * 11.11.0.2, from 11.11.0.2, 00:14:07 ago, via Tunnel22

      Route metric is 30, traffic share count is 1

im going to collect

“sh ip rsvp reservation det” again.

Finally i found the problem.

I was doing the test, with a simultator. when i tryed the same over real boxes, the feature run ok.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: