The original config also doesn't show any of your BGP config from inet.0,
so it's hard to say what's missing.
IIRC, if you have vrf-target, you don't need vrf-export:
vrf-export export-direct;
vrf-target target:7849:13;
If you want to do explicit export policy via vrf-export, I
Thanks Phil & Hugo,
I figured it out and have a working config now.
CROCKER-VOIP {
instance-type vrf;
interface ae0.301;
interface ae0.302;
route-distinguisher A.B.C.137:13;
vrf-target target:7849L:13;
vrf-table-label;
}
The issue wasn’t the VRF config at all. The
Hello,
I have 3 MX series routers connected via 3 10G circuits A - B - C -A.
OSPD, MPLS, RSVP, LDP are all running
inet-vpn any configured on the BGP groups
I’m trying to build a routing-instance on MX-A & MX -B with some local
interfaces and then have the two routing-instances be able
: juniper-nsp [mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of
Aaron
Sent: Monday, December 21, 2015 11:04 AM
To: 'Matthew Crocker'; 'jnsp list'
Subject: Re: [j-nsp] Collapsed MPLS CE/PE/P configuration
Maybe this will help...
this makes L3VPN work for me on a PE...
set interfaces ge-0/0/47
list
Subject: [j-nsp] Collapsed MPLS CE/PE/P configuration
Hello,
I have 3 MX series routers connected via 3 10G circuits A - B - C -A.
OSPD, MPLS, RSVP, LDP are all running
inet-vpn any configured on the BGP groups
I’m trying to build a routing-instance on MX-A & MX -B with some l
5 matches
Mail list logo
