They sell XRv now specifically as a vRR, you can find the deployment guides on their website.
The throughput on it isn't very good and they suggest using the CSR if you really want a software router. The only other thing they have XRv for is testing. Juniper doesn't really have two tracks, its the same RE software, just think of it like using two different line modules in the same router. I just don't think they have quite made it seamless at this point. Phil -----Original Message----- From: "Mark Tinka" <mark.ti...@seacom.mu> Sent: 12/1/2014 11:52 AM To: "juniper-nsp@puck.nether.net" <juniper-nsp@puck.nether.net> Cc: "Phil Bedard" <phil...@gmail.com>; "Robert Hass" <robh...@gmail.com> Subject: Re: [j-nsp] Transfer some task from MX to VRR On Monday, December 01, 2014 05:27:23 PM Phil Bedard wrote: > Juniper as far as I know plans on maintaining two > versions of the vMX at least to start with. The vRR > version is similar to the one used for things like lab > testing and uses 1 VM with both the vRE and vPFE > integrated. The vRR is not meant to be in the > forwarding path just like the vRR offerings from ALU and > Cisco. You would not really want to use it to terminate > eBGP sessions. Don't know about the ALU offering, but Cisco don't have a vRR-type solution. CSR1000v is a full-fledged router. What you can do and how much traffic you can forward through it is all controlled by what license you buy. I find this a better use of vendor resources than maintaining two separate tracks. Mark. _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
