- CheckMates
- :
- Products
- :
- CloudMates Products
- :
- Cloud Network Security
- :
- Discussion
- :
- Upgrading to R81.20 in Azure
- 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
Upgrading to R81.20 in Azure
Hi All,
I need to upgrade our R80.40 cluster in Azure to R81.20. In-place upgrades have failed and according to support and sk180769 we need to upgrade by deploying another cluster into the same subnets. I have been following this document below.
The R81.20 cluster deployment fails at the backend-lb.
My existing R80.40 cluster eth1 (inside) network is 10.28.1.32/27. The existing backend-lb is using 10.28.1.36 as the lb IP. The template is trying to assign the same IP to the new backend-lb it is trying to deploy and failing.
Has anyone tried this recently? I followed the same procedure when we went from R80.30 to R80.40 and didn't have this issue.
Thanks
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @russell_perera,
We have encountered some issues with Azure's function (Microsoft side) that assigns the first available IP of the subnet in our deployment.
As a workaround, you can use the custom template deployment option and specify a start IP address of your choice (Subnet1Start Address/Subnet2Start Address).
GitHub Link: https://github.com/CheckPointSW/CloudGuardIaaS/tree/master/azure/templates
Direct link for HA custom deployment: https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FCh...
Thanks,
Natanel
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @russell_perera,
We have encountered some issues with Azure's function (Microsoft side) that assigns the first available IP of the subnet in our deployment.
As a workaround, you can use the custom template deployment option and specify a start IP address of your choice (Subnet1Start Address/Subnet2Start Address).
GitHub Link: https://github.com/CheckPointSW/CloudGuardIaaS/tree/master/azure/templates
Direct link for HA custom deployment: https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FCh...
Thanks,
Natanel
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks @natanelm that worked. I was able to deploy via a custom template.
![](/skins/images/4BAE0211AB62E3B2F85E95CA468FEED0/responsive_peak/images/icon_anonymous_message.png)