[j-nsp] Problem with BGP

[Alan Gravett]

Hi Johan,

What you seem to be describing sounds like the application for route
"origin" filtering between the 2 PE  devices that are multi homed to a VPN
site?

What's not clear is the relationship between as65534 and as64560?

Can you send a diagram and configurations?
On 27 Apr 2016 7:59 PM, "Johan Borch" <johan.borch at gmail.com> wrote:

Hi

I have a problem that perhaps the experts on this list can help me shed
some light on :)

The problem involves two PE routers one Cisco IOS and one Juniper MX. MPLS
& co between them. Each PE have a VRF, same route-target. Each of these
PE-routers have a BGP session inside the VRF that connects to a customer
site via supplier and a leased line. These leased lines should be redundant
for each other.

Both BGP sessions use local as AS65534 and supplier on other side is
AS65535. Sessions are up and I'm receiving routes from supplier in each PE.

Now to my problem.

If I cut the leased line on the Cisco PE it will populate the vrf routing
table on the Cisco PE with routes from the Juniper PE learned over MPLS, no
problem.
If I cut the leased line on the Juniper PE then Juniper PE should learn the
routes from the Cisco PE, but all routes are hidden and Juniper thinks that
AS65534 is looped.

If I check a route on Juniper PE it says:

AS path: $MY_MPLS_NET_AS 65534 65535 $SUPPLIER_AS $SUPPLIER_AS I (Looped:
65534) (sorry for the obfuscation)

State: <Secondary Hidden Int Ext ProtectionCand>

Hidden reason: reason not available

VRF on Juniper side is configured with:
autonomous-system 64560 independent-domain

What am I missing? Can I tell JunOS do not think it is a loop somehow?
Would it be easier to peer with different ASN from each PE?

Johan
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp