Hi,

yes the command is there (otherwise the route are not sent to the external peer).

We are doing option B and the route are received form external peer and propagated to internal peer (the PE see and install the route).

The ASBR doesn't install in MPLS forwarding the label for the external route.

s.

Hi,

Probably you might check the below thing. The interconnect interface between providers been enabled with Label switching:

IP labeling not enabled

LSP Tunnel labeling not enabled

BGP tagging enabled

MPLS operational

Optimum Switching Vectors:

IP to MPLS Feature Vector

MPLS Feature Vector

Fast Switching Vectors:

IP to MPLS Fast Feature Switching Vector

MPLS Feature Vector

MTU = 4470

HTH....

Hi,

another bit can be usefull, the flow from the other ASBR reach the internal PE so the MPLS part of the configuration is right.

Traffic coming from externalAS with label 16 and 18 are forwarded the the internal PE after the correct label swap (22/18 an 21/16) the traffic from internal to external is not forwaded from the ASBR.

from another point of view if enabling the vrf on the ASBR makes MPLS forwarding functional i think that MPLS is correctly configured.

s.

I think you need to look at your eBGP configuration. You have a /32 host route for the BGP next-hop 172.16.0.4, but the BGP next-hop for the problematic route is 172.26.107.94. Verify the reason why the next-hops are different, as I assume you are pairing with loopbacks across two interfaces (G0/0 and G0/1).

Outputs from your PE would also be helpful, for us to see the VPN label, BGP next-hop sent to the PE.

Also labels 22 get swapped to 18 and not the other way.

the lab setup is quite simple:

AS1 PE --ibgp-- AS1 ASBR (172.26.107.94) ----ebgp---- AS2 ASBR (172.26.107.93) --ibgp-- AS2 PE (lo0 172.16.0.4)

From the AS2 ASBR the next hop for the internal route is the lo0 of the AS2 PE and the next hop for the AS1 route is the ip address of the btb interface (the ebgp peer is built on the directed connected interface). So no problem on the ebgp next hop.

The label swap from 22 to 18 is unidirectional and is used for the traffic coming from AS1 PE directed to the AS2 PE for destination network annouced by AS2PE.

From the AS2PE point of view there is no problem on the traffic forwarding (label 20 is imposed to the packet and this is the right behaviour) but AS2ASBR doesn't swap it with label 100192 because it is not in the mpls forwarding table. so i think that the problem is not on the PE but in the behaviour of the ASBR.

s.

Hmm,

Can you give the output of the show mpls forwarding on AS2 PE. I will like to know the label stack it uses for sending traffic to AS1 via AS2 ASBR. Kind of confirming that it is using label 20, and not that ASBR is not swapping.

Use show mpls forwarding vrf details command.