[j-nsp] Collapsed MPLS CE/PE/P configuration
Aaron
aaron1 at gvtc.com
Mon Dec 21 12:08:23 EST 2015
Darn, I hate when word-wrap does that ... I'll try again...
this makes L3VPN work for me on a PE...
set interfaces ge-0/0/47 mtu 9192
set interfaces ge-0/0/47 unit 0 family inet address 10.101.14.118/30
set interfaces ge-0/0/47 unit 0 family mpls
set interfaces lo0 unit 0 family inet address 10.101.12.245/32
set interfaces lo0 unit 1 family inet address 1.2.3.4/32
set protocols bgp group ibgp type internal
set protocols bgp group ibgp local-address 10.101.12.245
set protocols bgp group ibgp family inet-vpn unicast
set protocols bgp group ibgp neighbor 10.101.0.254 local-as 64512
set protocols ospf area 0.0.0.1 interface lo0.0
set protocols ospf area 0.0.0.1 interface ge-0/0/47.0
set protocols ldp interface ge-0/0/47.0
set routing-instances one instance-type vrf
set routing-instances one interface lo0.1
set routing-instances one route-distinguisher 10.101.12.245:1
set routing-instances one vrf-target import target:1:1
set routing-instances one vrf-target export target:1:1
set routing-instances one vrf-table-label
--------------------------------------------------------------------
explained as i understand it....
P-facing core interface...
set interfaces ge-0/0/47 mtu 9192
set interfaces ge-0/0/47 unit 0 family inet address 10.101.14.118/30
set interfaces ge-0/0/47 unit 0 family mpls
set interfaces lo0 unit 0 family inet address 10.101.12.245/32
PE-CE test interface...
set interfaces lo0 unit 1 family inet address 1.2.3.4/32
MP-BGP label signalling mechanism for advertising VPNV4 label between pe's...
set protocols bgp group ibgp type internal
set protocols bgp group ibgp local-address 10.101.12.245
set protocols bgp group ibgp family inet-vpn unicast
set protocols bgp group ibgp neighbor 10.101.0.254 local-as 64512
IGP routing ... you need to be able to FIRST learn the remote PE's loopback in order to route to it...
set protocols ospf area 0.0.0.1 interface lo0.0
set protocols ospf area 0.0.0.1 interface ge-0/0/47.0
set protocols ldp interface ge-0/0/47.0
MPLS L3VPN config...
set routing-instances one instance-type vrf
set routing-instances one interface lo0.1
set routing-instances one route-distinguisher 10.101.12.245:1
set routing-instances one vrf-target import target:1:1
set routing-instances one vrf-target export target:1:1
set routing-instances one vrf-table-label
-----Original Message-----
From: juniper-nsp [mailto:juniper-nsp-bounces at 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 mtu 9192
set interfaces ge-0/0/47 unit 0 family inet address 10.101.14.118/30 set interfaces ge-0/0/47 unit 0 family mpls set interfaces lo0 unit 0 family inet address 10.101.12.245/32 set interfaces lo0 unit 1 family inet address 1.2.3.4/32 set protocols bgp group ibgp type internal set protocols bgp group ibgp local-address 10.101.12.245 set protocols bgp group ibgp family inet-vpn unicast set protocols bgp group ibgp neighbor 10.101.0.254 local-as 64512 set protocols ospf area 0.0.0.1 interface lo0.0 set protocols ospf area 0.0.0.1 interface ge-0/0/47.0 set protocols ldp interface ge-0/0/47.0 set routing-instances one instance-type vrf set routing-instances one interface lo0.1 set routing-instances one route-distinguisher 10.101.12.245:1 set routing-instances one vrf-target import target:1:1 set routing-instances one vrf-target export target:1:1 set routing-instances one vrf-table-label
explained as i understand it....
P-facing core interface...
set interfaces ge-0/0/47 mtu 9192
set interfaces ge-0/0/47 unit 0 family inet address 10.101.14.118/30 set interfaces ge-0/0/47 unit 0 family mpls
set interfaces lo0 unit 0 family inet address 10.101.12.245/32
PE-CE test interface...
set interfaces lo0 unit 1 family inet address 1.2.3.4/32
MP-BGP label signalling mechanism for advertising VPNV4 label between pe's...
set protocols bgp group ibgp type internal set protocols bgp group ibgp local-address 10.101.12.245 set protocols bgp group ibgp family inet-vpn unicast set protocols bgp group ibgp neighbor 10.101.0.254 local-as 64512
IGP routing ... you need to be able to FIRST learn the remote PE's loopback in order to route to it...
set protocols ospf area 0.0.0.1 interface lo0.0 set protocols ospf area 0.0.0.1 interface ge-0/0/47.0
set protocols ldp interface ge-0/0/47.0
MPLS L3VPN config...
set routing-instances one instance-type vrf set routing-instances one interface lo0.1 set routing-instances one route-distinguisher 10.101.12.245:1 set routing-instances one vrf-target import target:1:1 set routing-instances one vrf-target export target:1:1 set routing-instances one vrf-table-label
Aaron
-----Original Message-----
From: juniper-nsp [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Matthew Crocker
Sent: Monday, December 21, 2015 9:42 AM
To: jnsp 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 local interfaces and then have the two routing-instances be able to talk to each other over the MPLS network (A-B or A-C-B)
Does anyone have any documentation on how to configure this? I’ve read a bunch of L3VPN JunOS docs but they all have CE, PE, P routers. In my case the routers A & B are acting as CE & PE while router C is acting as P
MX-A has a config:
CROCKER-VOIP {
instance-type vrf;
interface ge-2/0/8.13;
route-distinguisher 10.126.13.1:1;
vrf-export export-direct;
vrf-target target:7849:13;
}
# run show route table CROCKER-VOIP
CROCKER-VOIP.inet.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
10.126.13.0/30 *[Direct/0] 00:38:46
> via ge-2/0/8.13
10.126.13.1/32 *[Local/0] 00:38:46
Local via ge-2/0/8.13
MX-B has a config:
routing-instance
CROCKER-VOIP {
instance-type vrf;
interface ae0.301;
interface ae0.302;
route-distinguisher 10.127.13.1:1;
vrf-export export-direct;
vrf-target target:7849:13;
}
# run show route table CROCKER-VOIP
CROCKER-VOIP.inet.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
10.127.13.0/30 *[Direct/0] 00:47:21
> via ae0.301
10.127.13.1/32 *[Local/0] 00:47:21
Local via ae0.301
10.127.13.4/30 *[Direct/0] 00:47:21
> via ae0.302
10.127.13.5/32 *[Local/0] 00:47:21
Local via e0.302
A ‘show run bgp sum’ bgp.l3vpn.0 with 0 routes
Do I need to build a MPLS connection interface between the two routing-instances?
—
Matthew Crocker
President - Crocker Communications, Inc.
Managing Partner - Crocker Telecommunications, LLC
E: matthew at corp.crocker.com
E: matthew at crocker.com
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
More information about the juniper-nsp
mailing list