> > I wouldn't consider cRPD for production. vRR (or vMX, if it's still a > thing) seems to make more sense. >
For any use cases that you want protocol interaction, but not substantive traffic forwarding capabilities , cRPD is by far the better option. It can handle around 1M total RIB/FIB using around 2G RAM, right in Docker or k8. The last version of vMX I played with required at least 5G RAM / 4 cores to even start the vRE and vPFEs up, plus you have to do a bunch of KVM tweaking and customization, along with NIC driver fun. All of that has to work right just to START the thing, even if you have no intent to use it for forwarding. You could have cRPD up in 20 minutes on even a crappy Linux host. vMX has a lot more overhead. On Thu, Feb 8, 2024 at 3:13 AM Mark Tinka via juniper-nsp < juniper-nsp@puck.nether.net> wrote: > > > On 2/8/24 09:50, Roger Wiklund via juniper-nsp wrote: > > > Hi > > > > I'm curious, when moving from vRR to cRPD, how do you plan to > manage/setup > > the infrastructure that cRPD runs on? > > I run cRPD on my laptop for nothing really useful apart from testing > configuration commands, e.t.c. > > I wouldn't consider cRPD for production. vRR (or vMX, if it's still a > thing) seems to make more sense. > > Mark. > _______________________________________________ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp > _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
