- CheckMates
- :
- Products
- :
- Quantum
- :
- Security Gateways
- :
- Re: Can't Install R82 on VMware 6.7
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Can't Install R82 on VMware 6.7
Hi,
I've just completed the FTW for a build of R82 T777 on my ESXi 6.7 machine, and now the firewall just crashes on boot. Same messages going round and round.
The VM has 8GB and 6 CPU's, with 4 NICs with OS type "Other 4.x 64-bit". The guest was configured to be an ElasticXL cluster member running vsnext.
A build of R82 to be a primary manager worked just fine. Any help appreciated 🙂
Thanks
Jamie
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
According to the R82 Release Notes, ElasticXL is NOT supported on Open Servers. ElasticXL Cluster supports only Check Point appliances that have the dedicated ports called "Mgmt" and "Sync".
According to the R82 Release Notes, VSNext is NOT supported on Open Servers.
Why it is even possible to select these options on VM during FTW, is another question...
Jozko Mrkvicka
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Can you change the nic type as below? I know this is eve-ng, but not sure if same option can be set in vmware.
Andy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Andy,
NICs are already vmxnet3, have attached the settings spec.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I remember once I had similar issue with vmware and had to change controller type. We got rid of vmware, as we found eve-ng is so much better, so dont sadly ability to test this for you, sorry : - (
Andy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Funny enough, I just switched my internal lab to Promox from VMware ESXi 7 🙂
Since I had to do the switch on the same hardware, I converted the VMs to qcow2 and tested them on a different system running KVM.
It's all...a bit different, but at least the underlying Linux is actually usable and a whole lot easier to upgrade than VMware. 🙂
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Totally agree!
Btw, @stallwoodj
See if below video helps. I know its R80.40, but worth checking out the settings.
Andy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You should be specifying RHEL 8.x as the VM type, I believe.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Dameon,
Tried that, still getting the same error on boot.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
According to the R82 Release Notes, ElasticXL is NOT supported on Open Servers. ElasticXL Cluster supports only Check Point appliances that have the dedicated ports called "Mgmt" and "Sync".
According to the R82 Release Notes, VSNext is NOT supported on Open Servers.
Why it is even possible to select these options on VM during FTW, is another question...
Jozko Mrkvicka
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Great point. I totally overlooked the fact it was elasticxl in the description.
Andy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I believe the plan is to support these options in a JHF.
Meanwhile, for lab purposes, you can likely make this work.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hey @stallwoodj
I dug a little further about previous posts made about elastic xl and found below, but not sure it might be useful here, since I made post asking about sync issue with elasticxl in eve-ng, but you can check out what @shais gave as a solution, though if your vm is not even booting up, cant even check it. Let me see if there are any colleagues that can possibly test this somehow on vmware.
Andy
Also, maybe below may help, if there is a setting for promiscuous mode in vmware, you may want to disable it.
https://community.checkpoint.com/t5/Security-Gateways/R82-lab-with-ElasticXL/m-p/219578#M41986
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Maybe it's not supported. But it seems to be working on ESXi 8.0 Update 2. I've used the following configuration:
- CPU: 2vCPUs
- Memory: 16GB
- Hard disk 1: 110GB
- SCSI Controller 0: LSI Logic SAS
- 3x Network adapter: VMXNET 3
First installation failed. The security gateway didn't start. Messages about 'ckp: Loading FW-1 IPv4 Instance 0: failed'. Then I started with the config above.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Im sure these things can be done and workaround applied, but then again, I would never encourage anyone doing it in production, specially if official vendor document states its not supported.
Andy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I agree, I wouldn't run it in production. But it sure helps if these new features can be run in my home lab.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
100%
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @stallwoodj ,
ElasticXL/VSNext is not supported officially for production.
BUT We do encourage using VMs for it on Labs for demos/training/playing....
In most cases installing on VMs should work out of the box.
I guess you have some specific issue related to your ESX. If you did not manage to overcome it you can send me private message and i can try assist.
Regards,
Shai.
