>I'm pretty sure the VRR is mostly for solving the problem of iBGP session scaling.
I asked, as solving problems of iBGP is obvious. Terminating customers sessions on VRR using ebgp-multihop is also possible but it's needs reconfiguration at customer side. It's time consuming and too many questions and it's a small complication. I already saw some EFT code coming from other well-known network vendor where BGP traffic coming to router control-plane was tunneled to VRR like Virtual-Machine and processed there. All BGP related commands was also redirected to VRR but router receives FIB from VRR instead of RIB. Rob On Mon, Dec 1, 2014 at 2:09 PM, Eric Van Tol <[email protected]> wrote: > >-----Original Message----- > >From: juniper-nsp [mailto:[email protected]] On Behalf > Of Robert Hass > >Sent: Monday, December 01, 2014 7:30 AM > >To: [email protected] > >Subject: [j-nsp] Transfer some task from MX to VRR > > > >Hi > >Just readed release notes for 14.2 and I found that starting this release > I > >can transfer some task to external VRR. > > > >So my idea is to move all BGP from MX80 to VRR. But how it can be > performed > >for external BGP sessions where I have just /30 or /31 subnets to > customers > >? (of course without ebgp multihop). > > I'm pretty sure the VRR is mostly for solving the problem of iBGP session > scaling. If that's not the case, I'm sure someone will correct me. > > You don't have much choice with eBGP if you don't want to use multihop, > unless you want to backhaul every customer circuit via L2 to your VRR, in > which case the VRR is basically the gateway for the customer's circuit. > > -evt > > _______________________________________________ > juniper-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp > _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
