[j-nsp] VMX integrated FPC

[Nikolas Geyer]

vRR is basically just the VCP component of vMX without the vFP, which is why it’s limited to Linux bridged “management” interfaces.

There is nested vMX which runs the VCP as a nested virtual machine within the VFP,  not sure if it reduces requirements and iirc it only works on KVM.

Sent from my iPhone

> On Dec 21, 2020, at 6:43 PM, Mark Tees <marktees at gmail.com> wrote:
> 
> That's it. I actually wanted to see MX specific things get spun on up
> on interfaces from some code being developed.
> 
> Currently I have 2 x VMX's squashed into 4G's of RAM running under
> Vmware Fusion which currently does the job but it's a bit messy. I can
> probably fix the mess by generating the Vmware VM config files.
> 
> I should inspect the VRR image to see what it's doing and if there is
> anything that can be mimicked.
> 
> The other thing is if I am happy with just seeing the changes being
> loaded into control plane successfully I can just use a group but not
> apply it.
> 
>> On Tue, 22 Dec 2020 at 02:52, Saku Ytti <saku at ytti.fi> wrote:
>> 
>>> On Mon, 21 Dec 2020 at 18:27, <adamv0025 at netconsultings.com> wrote:
>>> 
>>> I guess if you don't want any vfp VM and want to run vcp VM only then vRR or
>>> the cRDP are the possible options?
>> 
>> I suspect the requirement is MX feature/configuration validation, so
>> pps would be traded for simplicity of stack, down to 1pps. vRR and
>> cRPD would not be an acceptable answer for this use-case.
>> 
>> 
>> --
>>  ++ytti
> 
> 
> 
> -- 
> Regards,
> 
> Mark Tees
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp