- CheckMates
- :
- Products
- :
- CloudMates Products
- :
- Cloud Network Security
- :
- Discussion
- :
- Resize Checkpoint VM 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
Resize Checkpoint VM in Azure
We are running a R77.30 Cluster in Azure on two D2v2 virtual machines (2 core, 7GB ram). The VPN traffic volume has naturally increased as we have moved applications to Azure and we are getting to a point where we may need to increase the VM size to cope with the additional VPN load. Firstly, will more cores and RAM help provide more VPN throughput by spreading the load across more cores?
If so, I know you can re-size Windows virtual machines in Azure easily. Is it supported to re-size a Checkpoint VM in Azure? So from a D2v2 (2 core, 7GB ram) to a D3v2 (4 core, 14GB ram). I have available vsec licenses for the additional cores so licensing is not an issue. If it is supported is it literally re-size the VM in Azure portal and reboot or is there any other Checkpoint considerations? for example CoreXL?
thanks
Alex
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If you are running blades other than Firewall, VPN, and Identity Awareness, no.
This is because the combination of the various Software Blades + VPN results in all VPN traffic being on Core 0.
Adding more cores to a R77.30 gateway doesn't solve this, but upgrading to R80.10 will as this release removes that limitation.
Other than that, shutting down, changing instance type, and restarting is supported/will work (if you have licenses of course).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks Dameon. I'm running FW, VPN, APP, URL blades which by your response suggests a resize on the current R77.30 version won't make a difference. Might have to look at upgrading to R80.10 once I've seen someone do this successfully with a cluster in Azure as this is a prod environment.
![](/skins/images/A53DAF99EDBAFE11A1FC6E62F510C235/responsive_peak/images/icon_anonymous_message.png)