xconnect with MPLS TE FRR

Unanswered Question
Mar 2nd, 2010

Hi guys !!!

I've prepared test desk for L2VPN with TE FRR (see Attach)

Briefly, I've two identical routers linked by two ethernet trunked-ports with one vlan correspondingly.

Routers has a connectivity in the normal state. I've seen xconnect UP and Tunnel 1 UP with  FRR: Ready.

I've losing connectivity if I shuotdown VLAN on the primary ethernet-interface. but when I type

show mpls traffic-eng tunnels protection

I see   R_vrn_7609_t1 LSP Head, Tunnel1, Admin: up, Oper: down

          Path Protection: Backup lsp in use.

          LSP Tunnel R2_6506_t2 is signalled, connection is up

Thus I heve Tunnel Backup OK, but I haven't connectivity between xconnet interfaces :-(

PS: I want to do xconnect through VLAN because I have leased ethernet links without mpls.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
jcozzupoli Tue, 03/02/2010 - 16:16

hi,

Having a look at the output you pasted, Operation state of the TE tunnel is down:

R_vrn_7609_t1 LSP Head, Tunnel1, Admin: up, Oper: down

          Path Protection: Backup lsp in use.

          LSP Tunnel R2_6506_t2 is signalled, connection is up

Can you please show us the output of:

show mpls l2transport vc detail when you do the same test? Check for the "next hop" value in that, if its "MOI" then there is your problem.

Also, here is a template of implementing TE-FRR:

interface Tunnel100
description :MPLS-TE Tunnel Primary
ip unnumbered Loopback0
tunnel destination 10.100.100.2
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng autoroute announce
tunnel mpls traffic-eng path-option 1 explicit name TE_DC_PRIMARY
tunnel mpls traffic-eng priority 1 1
tunnel mpls traffic-eng bandwidth 5000
tunnel mpls traffic-eng fast-reroute

!

interface Tunnel200
description :MPLS-TE Tunnel Secondary
ip unnumbered Loopback0
tunnel destination 10.100.100.2
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng path-option 1 explicit name TE_DC_SECONDARY
tunnel mpls traffic-eng priority 1 1
tunnel mpls traffic-eng bandwidth 5000

!

interface x/y

description PRIMARY

mpls traffic-eng backup-path Tunnel200

HTH

Joe.

Oleg Gnedykh Tue, 03/02/2010 - 22:49

Hi!

Thank you for your answer.

R1#show mpls l2transport vc detail   
Local interface: Gi1/2 up, line protocol up, Ethernet up
  Destination address: 10.100.100.2, VC ID: 100, VC status: down
    Output interface: none, imposed label stack {}
    Preferred path: Tunnel1,  no route
    Default path: disabled
    No adjacency
  Create time: 00:51:00, last status change time: 00:09:18
  Signaling protocol: LDP, peer 10.100.100.2:0 up
    Targeted Hello: 10.100.100.1(LDP Id) -> 10.100.100.2
    MPLS VC labels: local 19, remote 311
    Group ID: local 0, remote 0
    MTU: local 1500, remote 1500
    Remote interface description:
  Sequencing: receive disabled, send disabled
  VC statistics:
    packet totals: receive 412, send 48
    byte totals:   receive 29673, send 8920
    packet drops:  receive 0, send 0

Thet is all right (IMHO)

But I didn't uderstand what is it "Tunnel R2_t1 is signalled, connection is up"  (see later)

R1#sh mpls traffic-eng tunn protection
R1_t1
  LSP Head, Tunnel1, Admin: up, Oper: down
  Src 10.100.100.1, Dest 10.100.100.2, Instance 0
  Fast Reroute Protection: None
  Path Protection: Backup lsp in use.
R1_t2
  LSP Head, Tunnel2, Admin: up, Oper: up
  Src 10.100.100.1, Dest 10.100.100.2, Instance 17
  Fast Reroute Protection: None
  Path Protection: None

LSP Tunnel R2_t1 is signalled, connection is up
  InLabel  : Vlan63, implicit-null
  OutLabel :  -
  RSVP Signalling Info:
       Src 10.100.100.2, Dst 10.100.100.1, Tun_Id 1, Tun_Instance 454
    RSVP Path Info:
      My Address: 10.100.100.1  
      Explicit Route:  NONE
      Record   Route:   NONE
      Tspec: ave rate=1000 kbits, burst=1000 bytes, peak rate=1000 kbits
    RSVP Resv Info:
      Record   Route:   NONE
      Fspec: ave rate=1000 kbits, burst=1000 bytes, peak rate=1000 kbits

LSP Tunnel R2_t2 is signalled, connection is up
  InLabel  : Vlan64, implicit-null
  OutLabel :  -
  RSVP Signalling Info:
       Src 10.100.100.2, Dst 10.100.100.1, Tun_Id 2, Tun_Instance 1050
    RSVP Path Info:
      My Address: 10.100.100.1  
      Explicit Route:  NONE
      Record   Route:   NONE
      Tspec: ave rate=1000 kbits, burst=1000 bytes, peak rate=1000 kbits
    RSVP Resv Info:
      Record   Route:   NONE
      Fspec: ave rate=1000 kbits, burst=1000 bytes, peak rate=1000 kbits

jcozzupoli Wed, 03/03/2010 - 14:41

Hi,

Yes Laurent poses a very good, and important question, that many overlook in troubelshooting these types of issues. Since pseudowires are, as they say in the enterprise world, an extended vlan, you'd need to have the same dot1q vlan on both ends.

Regards,

Joe.

Oleg Gnedykh Thu, 03/04/2010 - 03:10

Hi Joe!

I don't understand a problem. Of course I have same vlan on corresponded physical interfaces (VID63,64)

Oleg Gnedykh Thu, 03/04/2010 - 03:01

Hi Laurent!

No. I shutdown only one side. I think this is a more reality situation, when the link down anywhere.

PS: Can the TE with FRR propagate through VLAN?

Laurent Aubert Thu, 03/04/2010 - 06:40

You have TE tunnel on both direction and FRR triggers only when the interface is down so you need to shutdown VLAN on both side so FRR will kick-in on both direction. Otherwise the tunnel on side where the VLAN is still UP will stay down as you are using explicit path.

HTH

Laurent.

Oleg Gnedykh Thu, 03/04/2010 - 07:32

Hi Laurent!

I thought about it, and today I've moved channels from VLANs to physical interfaces. The FRR has worked wonderfully.

But in real life it's unreal because I've leased line :-(

Can you suggest some workaround?

Actions

This Discussion

Related Content