Thanks a lot Aaron , much appreciated So , VPLS (Cisco term) is operable with Juniper Now , the l2circuit configuration I posted is functional ? Because I want to propose my customers all options :)
BR, Mohammad On Mon, Apr 18, 2016 at 10:27 PM, Aaron <aar...@gvtc.com> wrote: > you didn't tell me whether you wanted rfc4761 or rfc4762, so i'm giving > you both of my scenario notes...make sure you prove this out before going > live with it. These were my notes from when I tested this in my lab last > year… hopefully I didn’t leave to much out and you can make sense of this… > > > > - Aaron > > > > ******************************************************************** > > RFC4761 VPLS - BGP AD w/BGP Sig > > > > ***** MX104--- > > > > set interfaces ge-1/3/2 encapsulation ethernet-vpls > > > > set interfaces ge-1/3/2 unit 0 family vpls > > > > set protocols mpls interface ge-1/3/0.0 > > > > set protocols ldp interface ge-1/3/0.0 > > > > set protocols ldp interface lo0.0 > > > > set protocols bgp group ibgp type internal > > > > set protocols bgp group ibgp local-address 10.101.12.248 > > > > set protocols bgp group ibgp family inet-vpn unicast > > > > set protocols bgp group ibgp family l2vpn signaling > > > > set protocols bgp group ibgp neighbor 10.101.0.254 local-as 64512 > > > > set routing-instance vlan100 instance-type vpls > > > > set routing-instance vlan100 interface ge-1/3/2.0 > > > > set routing-instance vlan100 route-distinguisher 10.101.12.248:32768 > > > > set routing-instance vlan100 vrf-target target:65535:10100 > > > > set routing-instance vlan100 protocols vpls > > > > set routing-instance vlan100 protocols vpls site-range 8 > > > > set routing-instance vlan100 protocols vpls no-tunnel-service > > > > set routing-instance vlan100 protocols vpls site my_site site-identifier 2 > > > > set routing-instance vlan100 protocols vpls site my_site interface > ge-1/3/2.0 > > > > > > ****** ASR9k--- > > > > (i don't show port config with efp and into bridge domain) > > > > (also shown are inet and inet6 af's (what cisco calls vpnv4 and vpnv6, i > don't think those were really needed for this vpls lab...) > > > > router bgp 64512 > > > > neighbor-group rr-clients-l2vpn_4761-vpnv4-and-6 > > > > remote-as 64512 > > > > update-source Loopback0 > > > > address-family vpnv4 unicast > > > > address-family vpnv6 unicast > > > > address-family l2vpn vpls-vpws > > > > Signalling ldp disable > > > > neighbor 10.101.12.248 > > > > use neighbor-group rr-clients-l2vpn_4761-vpnv4-and-6 > > l2vpn > > > > autodiscovery bgp > > > > signaling-protocol bgp > > > > mtu mismatch ignore > > > > bridge group v100 > > > > bridge-domain v100 > > > > vfi v100 > > > > vpn-id 10100 > > > > autodiscovery bgp > > > > rd auto > > > > route-target import 65535:10100 > > > > route-target export 65535:10100 > > > > signaling-protocol bgp > > > > ve-id 5 > > > > ve-range 11 > > > > > > ************************************************************ > > RFC4762 VPLS - BGP AD w/LDP Sig > > > > ***** MX104--- > > > > set interfaces ge-1/3/2 encapsulation ethernet-vpls > > > > set interfaces ge-1/3/2 unit 0 family vpls > > > > set protocols mpls interface ge-1/3/0.0 > > > > set protocols ldp interface ge-1/3/0.0 > > > > set protocols ldp interface lo0.0 > > > > set protocols bgp group ibgp type internal > > > > set protocols bgp group ibgp local-address 10.101.12.248 > > > > set protocols bgp group ibgp family inet-vpn unicast > > > > set protocols bgp group ibgp family l2vpn auto-discovery-only > > > > set protocols bgp group ibgp neighbor 10.101.0.254 local-as 64512 > > > > set routing-instances vlan100 instance-type vpls > > > > set routing-instances vlan100 interface ge-1/3/2.0 > > > > set routing-instances vlan100 route-distinguisher 10.101.12.248:32768 > > > > set routing-instances vlan100 l2vpn-id l2vpn-id:65535:10100 > > > > set routing-instances vlan100 vrf-target target:65535:10100 > > > > set routing-instances vlan100 protocols vpls no-tunnel-services > > > > ****** ASR9k--- > > > > (i don't show port config with efp and into bridge domain) > > > > (also shown are inet and inet6 af's (what cisco calls vpnv4 and vpnv6, i > don't think those were really needed for this vpls lab...) > > > > router bgp 64512 > > > > neighbor-group rr-clients-l2vpn_4762-vpnv4-and-6 > > > > remote-as 64512 > > > > update-source Loopback0 > > > > address-family vpnv4 unicast > > > > address-family vpnv6 unicast > > > > address-family l2vpn vpls-vpws > > > > neighbor 10.101.12.248 > > > > use neighbor-group rr-clients-l2vpn_4762-vpnv4-and-6 > > > > l2vpn > > > > bridge group v100 > > > > bridge-domain v100 > > > > vfi v100 > > > > vpn-id 10100 > > > > autodiscovery bgp > > > > rd auto > > > > route-target import 65535:10100 > > > > route-target export 65535:10100 > > > > signaling-protocol ldp > > > > vpls-id 65535:10100 > > > > > > > > _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp