That's what I understood the PW Labels generated by BGP. Hmmm though now that I read Scott's post again he actually wanted to avoid using routing instances -which unfortunately is exactly what I have recommended with the VPLS setup, but I think that's the only way how to get BGP to allocate/advertise PW Labels and I'd be glad to learn otherwise.
Though the RFC3107 could certainly be used to address the "no OSPF" requirement. And don't you worry you gonna love RFC3107, it's a perfect cure for all routing problems! As David Wheeler once said: "All problems in computer science can be solved by another level of indirection, except for the problem of too many layers of indirection." adam > -----Original Message----- > From: juniper-nsp [mailto:juniper-nsp-boun...@puck.nether.net] On Behalf > Of Mark Tinka > Sent: 19 February 2015 11:54 > To: juniper-nsp@puck.nether.net > Subject: Re: [j-nsp] L2Circuit with BGP/LDP > > > > On 19/Feb/15 11:51, Adam Vitkovsky wrote: > > Hi Scott, > > > > There are two ways how you can setup the E-lines using BGP. > > BGP Auto Discovery with LDP signalling. > > BGP Auto Discovery with BGP signalling. > > > > I think the second one is what you want to accomplish. > > I might have misunderstood the OP's question, but wasn't he asking about > how he can provision Martini EoMPLS circuits where FEC's are generated > from iBGP routes? > > Mark. > _______________________________________________ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp --------------------------------------------------------------------------------------- This email has been scanned for email related threats and delivered safely by Mimecast. For more information please visit http://www.mimecast.com --------------------------------------------------------------------------------------- _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
