Check the contents of the relevant file to determine the installed image version of the deployed vSEC Gateway:
| CloudGuard Gateway |
How to check? |
| CloudGuard for AWS |
[Expert@HostName:0]# cat /etc/in-aws |
| CloudGuard for Azure |
[Expert@HostName:0]# cat /etc/in-azure |
| CloudGuard for Google Cloud Platform |
[Expert@HostName:0]# cat /etc/in-google |
Explanation:
The image version is displayed as <VERSION>-<TAKE>-<BUILD>.vhd where <VERSION> can be:
- gey_hvm = R77.30
- hero3 = R80
- hugo = R80.10
- ogu_GAR1 = R80.10
- gogo13 = R80.20
- gogo_heat = R80.30
- harrry= R80.40
- ice= R81
- ignis= R81.10
Example from CloudGuard for Azure (running R77.30, Take 41, Build 161):
[Expert@HostName:0]# cat /etc/in-azure
gey_hvm-41-161.vhd
[Expert@HostName:0]# cat /etc/cloud-version
release: R80.30
take: 273
build: 525
platform: azure
license: byol
deployment_method: GW
template_name: single
template_version: 20190731
Note: R77.30 builds that are older than 56 will not have the version information in the file /etc/in-*. The file will be empty.
Later versions:
sk125252 - CloudGuard for AWS Latest Updates
sk132192 - CloudGuard for Azure Latest Updates
sk147032 - CloudGuard for GCP (Google Cloud Platform) Latest Updates
|
This solution has been verified for the specific scenario, described by the combination of Product, Version and Symptoms. It may not work in other scenarios.
|
