topic Re: R82.10 ElasticXL & VSNext supported in VMware? in Firewall and Security Management

Lab: R82.10 ElasticXL & VSNext problems in VMware

bluecross — Fri, 15 May 2026 08:55:11 GMT

Hello,

I'm trying to setup a R82 lab with ElasticXL and VSNext in VMware.
Having read these posts: https://community.checkpoint.com/t5/Firewall-and-Security-Management/R82-ElasticXL-amp-VSNext-Issues/m-p/251796 and https://community.checkpoint.com/t5/Firewall-and-Security-Management/Building-VSNext-in-R82-walk-through-with-videos/td-p/232604 I supposed that VSNext is possible in virtualization, but I'm still failing.
Setting up ElasticXL-Cluster didn't throw up any problems, but when setting it up as VSNext, there's no communication possible between SMS and gateway.
Can anybody confirm, that it is possible to run VSNext under virtualization? Both posts mention proxmox for the lab, also VMware (vSphere/ESXi) should be possible too.
When I configure the gateway for VSNext in the FTW, I can't connect to the management IP of the system after reboot. vNIC is in the same vlan (portgroup). I assume that the creation of the "wrp0" interface is the cause of the problem, as it uses a new virtual mac which is mapped to the (correct) mgmt/eth0 interface. Promiscuous mode is enabled for the portgroups of the dSwitch too...

Thanks for your help!

Re: R82.10 ElasticXL & VSNext supported in VMware?

Lesley — Fri, 15 May 2026 08:47:03 GMT

Support has changed from R82 to R82.10 check it out here:

https://sc1.checkpoint.com/documents/R82.10/WebAdminGuides/EN/CP_R82.10_RN/Content/Topics-RN/Supported-Environments.htm?tocpath=Supported%20Environments%20in%20R82.10%7C_____0#Supported_Environments_in_R82.10

Re: R82.10 ElasticXL & VSNext supported in VMware?

emmap — Fri, 15 May 2026 08:51:26 GMT

It's supported and should work, I've done it in VMWare workstation without issue. Can you ping out from VS0?

Re: R82.10 ElasticXL & VSNext supported in VMware?

bluecross — Fri, 15 May 2026 10:47:31 GMT

@emmap wrote:
Can you ping out from VS0?

No, seems like an isolated host. Can not ping second gateway in same network (and it's the same dSwitch on the same esxi host), nor the SMS or a client in this network.
Same is true for the sync-network, both VMs use 192.0.2.1, not resulting in conflict.

I can see the mac addresses for the SMS an client VM on both nodes via wrp0 but not the other gateway (incomplete).

Situation on the sync-network is a little bit different: Moving the client vm to the sync-network with an ip from this network I can reach 192.0.2.1 (tested with both gateways)