[j-nsp] Transfer some task from MX to VRR

[Robert Hass]

>I think vMX can forward data.

vMX indeed will be full-featured router. But my questions was related to
move part of control-plane (basically whole BGP part of rpd) to external
server. Maybe OpenFlow somehow helps here ? How openflow take care of eBGP
to customers ? Session should be on router or on OpenFlow controller ? OF
v1.3 just has been implemented in JunOS 14.x releases for MX series.

BTW. Are anyone participating in vMX beta-trial ?

Rob


On Mon, Dec 1, 2014 at 3:06 PM, Mark Tinka <mark.tinka at seacom.mu> wrote:

> On Monday, December 01, 2014 03:09:15 PM Eric Van Tol wrote:
>
> > 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.
>
> I think vMX can forward data. It will come down to how well
> it optimizes the CPU, and how good the CPU actually is.
>
> > 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.
>
> Agree.
>
> Your design can get complicated if you separate routing from
> forwarding for a particular device or downstream-set.
>
> Mark.
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>