[j-nsp] VPLS Between 2 Routers
Serge Vautour
sergevautour at yahoo.ca
Fri Mar 2 11:13:25 EST 2012
If you just want 2 end points, an L2VPN would be much simpler to setup. This works for me:
interfaces {
ge-1/0/2 {
mtu 9192;
encapsulation ethernet-ccc;
unit 0;
}
}
routing-instances {
TEST {
instance-type l2vpn;
interface ge-1/0/2.0;
vrf-target target:123:987700;
protocols {
l2vpn {
encapsulation-type ethernet;
no-control-word;
site site1 {
site-identifier 1;
interface ge-1/0/2.0;
}
}
}
}
}
This is completely transparent. Any valid ethernet frame with/without a dot1q tag will go through.
Once you add the interface to your site, your config looks similar. Try adding the "vlan-id all" knob under the RI.
Serge
________________________________
From: David Ball <davidtball at gmail.com>
To: Craig Whitmore <lennon at orcon.net.nz>
Cc: juniper-nsp at puck.nether.net
Sent: Thursday, March 1, 2012 8:55:30 PM
Subject: Re: [j-nsp] VPLS Between 2 Routers
Try adding the interface (ge-0/0/7.0) under the 'site' definition in the
routing instance config.....it's required, as far as I know. The rest
looks pretty familiar.
David
On 1 March 2012 17:06, Craig Whitmore <lennon at orcon.net.nz> wrote:
> Hi there
>
> I am pretty new to MPLS but what I'm trying to do is set up a L2 Tunnel
> between 2 Routers via VPLS. The idea is the customer can plug a TRUNK port
> at both ends and run whatever VLANS they want between them . Maybe there is
> a easier way to do it. There are LOTS of examples in LOTS of different
> places on how VPLS should be set up and all are slightly different. I
> cannot
> get any data thru the VPLS connection..
>
> The set up is 2 Juniper Routers running OSPF between them and then BGP
> between the Loopbacks also running MPLS/LDP etc
>
> The Config is (the same on both ends basically)
>
> ge-0/0/7 {
> description "VPLS";
> per-unit-scheduler;
> encapsulation ethernet-vpls;
> unit 0 {
> family vpls;
> }
> }
>
> VPLS-Customer {
> instance-type vpls;
> interface ge-0/0/7.0;
> route-distinguisher XXXXX:2000; (XXXXXX:1000 on other side).. (XXXX =
> the AS number)
> vrf-target target:XXXXX:100;
> protocols {
> vpls {
> site-range 10;
> no-tunnel-services;
> site router-2000 {
> site-identifier 5; (different on both sides)
> }
> }
> }
> }
>
>
> Debug..
>
> # show vpls connections extensive
>
> Instance: VPLS-Customer
> Local site: router-2000 (5)
> Number of local interfaces: 1
> Number of local interfaces up: 1
> IRB interface present: no
> ge-0/0/7.0
> lsi.1049090 6 Intf - vpls VPLS-Customer local site 5
> remote site 6
> Label-base Offset Size Range Preference
> 262153 1 8 8 100
> connection-site Type St Time last up # Up trans
> 6 rmt Up Mar 2 11:32:17 2012 1
> Remote PE: Y.Y.Y.Y, Negotiated control-word: No (Y.Y.Y.Y = Loopback of
> other router)
> Incoming label: 262158, Outgoing label: 262165
> Local interface: lsi.1049090, Status: Up, Encapsulation: VPLS
> Description: Intf - vpls VPLS-Customer local site 5 remote site 6
> Connection History:
> Mar 2 11:32:17 2012 status update timer
> Mar 2 11:32:17 2012 loc intf up lsi.1049090
> Mar 2 11:32:17 2012 PE route changed
> Mar 2 11:32:17 2012 Out lbl Update 262165
> Mar 2 11:32:17 2012 In lbl Update 262158
> Mar 2 11:32:17 2012 loc intf down
>
>
> #show bgp summary instance VPLS-Customer
>
> Groups: 0 Peers: 0 Down peers: 0
> Table Tot Paths Act Paths Suppressed History Damp State
> Pending
> VPLS.l2vpn.0 1 1 0 0 0
> 0
>
> # show bgp summary.
>
> Peer AS InPkt OutPkt OutQ Flaps Last
> Up/Dwn State|#Active/Received/Accepted/Damped...
> Y.Y.Y.Y 56030 6057 4657 0 0 1d 11:40:03
> Establ (Y.Y.Y.Y = IP Address of other routers loopback)
> inet.0: 2/5156/2/0
> inet.2: 0/0/0/0
> bgp.l2vpn.0: 1/1/1/0
> bgp.l3vpn.0: 0/0/0/0
> VPLS-Customer.l2vpn.0: 1/1/1/0
>
>
>
>
>
>
> _______________________________________________
> 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