Re: MP-EBGP problem with PPPOE interfaces

From: Marko Milivojevic (markom@markom.info)
Date: Sun Jul 27 2008 - 09:20:06 ART


I was never able to make this work properly. I even believe someone
posted an IOS bug ID on the mailing list here few months back.

I could have bad memory...

--
Marko
CCIE #18427

On Sun, Jul 27, 2008 at 11:15, ahmed mahmoud <ahmadforever@gmail.com> wrote: > Good day Everyone. > > I faced a problem while solving one of the CCIE senarios, Where I had an > Inter-AS case using the MP-EBGP neighborship between the ASBRs , while the > connection between the ASBRs was PPPOE... the problem is the following. > > The accepting side of the PPPOE connection (The virtual template ) is > perfect as the BGP updates are coming with the labels and the labels are > injected into the LFIB as below > > ====================================================================== > Rack1R6#sh ip b v a 10.1.7.0 > BGP routing table entry for 1000:1:10.1.7.0/24, version 23 > Paths: (1 available, best #1, no table) > Advertised to non peer-group peers: > 24.1.3.3 > 200 > 24.1.56.5 from 24.1.56.5 (24.1.5.5) > Origin incomplete, localpref 100, valid, external, best > Extended Community: RT:200:2 OSPF DOMAIN ID:0x0005:0x000000010200 OSPF > RT:0.0.0.0:2:0 OSPF ROUTER ID:10.1.47.4:512, > mpls labels in/out *27/30* > > Rack1R6#sh mpls forwarding-table > *27 30* 1000:1:10.1.7.0/24 \ > > ===================================================================================== > > > while on the dialing side of the PPPOE (Dialer Interface) the BGP updates > are coming with the labels but the LFIB is not populated and the > forwarding fails as below > > ======================================================================== > Rack1R5#sh ip b v a 10.1.8.0 > BGP routing table entry for 1000:1:10.1.8.0/24, version 33 > Paths: (1 available, best #1, no table) > Flag: 0x820 > Advertised to update-groups: > 2 > 100 > 24.1.56.6 from 24.1.56.6 (24.1.6.6) > Origin incomplete, localpref 100, valid, external, best > Extended Community: RT:100:1 OSPF DOMAIN ID:0x0005:0x000000010200 > OSPF RT:0.0.0.0:2:0 OSPF ROUTER ID:10.1.28.2:512, > mpls labels in/out *34/25* > Rack1R5#sh mpls for > Rack1R5#sh mpls forwarding-table > Local Outgoing Prefix Bytes tag Outgoing Next Hop > tag tag or VC or Tunnel Id switched interface > 16 Pop tag 24.1.4.4/32 0 Fa0/0 24.1.45.4 > 17 20 24.1.1.1/32 0 Fa0/0 24.1.45.4 > 18 18 24.1.9.9/32 0 Fa0/0 24.1.45.4 > 19 Pop tag 24.1.14.0/29 0 Fa0/0 24.1.45.4 > 20 17 24.1.19.0/24 0 Fa0/0 24.1.45.4 > 21 Untagged 24.1.56.6/32 0 Vi1 point2point > 29 23 1000:1:192.10.1.0/24 \ > 0 Fa0/0 24.1.45.4 > 30 16 1000:1:10.1.7.0/24 \ > 18526 Fa0/0 24.1.45.4 > 31 21 1000:1:10.1.47.0/24 \ > 0 Fa0/0 24.1.45.4 > 32 22 1000:1:51.51.51.51/32 \ > 0 Fa0/0 24.1.45.4 > 33 20 1000:1:10.1.18.0/24 \ > 0 Fa0/0 24.1.45.4 > Rack1R5# > ==================================================================== > > > Please advise !!!



This archive was generated by hypermail 2.1.4 : Mon Aug 04 2008 - 06:11:57 ART