Virtual OVA deployed 81.20 cannot login

[tkerbe]

Hello,

I work for a very large enterprise and we are in the process of deploying (2) virtual gateways for a PoC in our environment. Our build team has deployed the OVAs on ESXi using what our CheckPoint SE gave us (ivory_main-631-991001385-GW.ova)

Please keep in mind I am very new to CheckPoint appliances and CheckPoint products. This OVA was deployed and I am able to access the CLI via vSphere web console for both VMs. I was prompted with a simple screen that has a banner displaying;"This system is for authorized use only". I utilized admin / admin and it displays; "Login incorrect", on both VMs.

• I have confirmed with my build team that they deployed the OVA as is and did not change any credentials in the process. Our SE has had us try a couple of different combos, with no luck.
• Our SE is now deploying their own VM with the exact OVA to see if the same issue happens. 
• These VMs are both configured with 192.168.1.1 so I cannot access the Gaia web UI.

Am I missing something crucial here? Seems like this should be a very simple step in the deployment. 

[Bob_Zimmerman · Accepted solution]

Were they built through a vCenter or directly on an ESXi host? The OVAs need you to set the password via the initial config on a vCenter, but that doesn't work directly on an ESXi host and you won't be able to log in.

You can always just download the ISO image, upload it to the ESXi host, and use it in a virtual optical drive to install the OS.

[tkerbe]

This is exactly what happened. Our SE sent us the correct OVA that I put in one of my replies on this. Unfortunately since we have a separate build team I didn't get to deploy any of this myself or even see these parameters and the build team always leaves everything blank. 

Thank you for this reply though! I appreciate all of your help. 

[the_rock]

So the screenshot you attached shows grub password, which is not even set initially. Is it possible someone may had entered different password when going through initial install?

Best,

Andy

[Bob_Zimmerman]

I think you read that backwards. The message is complaining that the GRUB password hasn't been changed. R81.20 makes you set that in config_system or the first-time wizard, so those definitely haven't been completed. I don't recall if deploying the OVA through a vCenter gives you the option to change the GRUB password at the cloud-init level.

[the_rock]

I know thats what it said, but that does not appear to be related to the issue they have. I dont ever recall having to set grub password in R81.20, even in new install.

Andy

[_Val_]

Did you consider reaching out to the person provided you with the OVA?

[tkerbe · Accepted solution]

Thank you to everyone who replied. Our SE told us that they had initially sent us the incorrect OVA. Correct OVA was ivory_main-631-991001385_unsecured.ova

This had to do with the original OVA requiring a bunch of parameters to be configured when importing the OVA. If those aren't set initially there is no opportunity to set them later. So our internal build team just left all of this blank and that resulted in a VM that couldn't be configured.

I attached the screenshot of what should have been configured when importing the OVA into ESXi.