after deployment through terraform backend lb shows none in udr about cloudguardiaas

[chkp-arielto]

Hi @rajeev-cloud, can you please clarify the reason for this issue?

[rajeev-cloud]

I did this cloudguard deployment through terraform script and went successful, so far no issues. for testing purpose, i deployed a machine to test internet access and configured user defined route. well, here is a point under user defined routes "backend lb" ip was showing "next hop as none" instead of virtual appliance. i do not know its a microsoft azure issue or script.

to find the problem, again i did cloudguard installation direct on azure without script and it worked perfect. i was able to see virtual appliance uder user defined routes.

Important - NSG is missing for existing vnet, which will allow "inbound" access, by default with this template it only deploy's VMs.

[chkp-arielto]

Hi @rajeev-cloud,

I want to ensure the operations you made:

1. You deployed a VMSS using Terraform
2. You clicked on the backend route table created as part of the deployment
3. The next-hop of the default route was None
4. When trying to edit this route, the "virtual appliance" option wasn't displayed

Can you confirm that the above is what you performed?

Thanks,
Ariel

[rajeev-cloud]

1. I used "high-availability-existing-vnet" for deployment.
2. Deployment was sucessful.
3. When i used backend lb ip in udr then it shows me next hop as none instead of virtual appliance.

[chkp-arielto]

You are right, the route tables are not created as part of the deployment. Thanks for notifying us, we will fix it soon and keep you updated.

[chkp-arielto]

Hi @rajeev-cloud
We have added the frontend IP configuration in the backend lb (and many other features!).
The changes are delivered here.
Thanks for notifying us!
Ariel