Who rated this post

Just to wrap this up, and let "Future Me" and "Future You" know, this "aio" package worked well to do an inline upgrade on an Azure CloudGuard management server:

[Expert@moon:0]# da_cli upgrade package=aio_Check_Point_R82_T777_Gaia_Install_and_Upgrade.tgz reboot_delay=30
{
   "Action ID" : "216",
   "Delay" : "30",
   "Message" : "upgrade command delivered to service.",
   "Package" : "aio_Check_Point_R82_T777_Gaia_Install_and_Upgrade.tgz"
}

[Expert@moon:0]# da_cli_status 216
{
   "Action ID" : "216",
   "Action Type" : "Upgrade",
   "DAService State" : "ready",
   "ExtendedMessage" : "N/A",
   "Message" : "",
   "Package" : "aio_Check_Point_R82_T777_Gaia_Install_and_Upgrade.tgz",
   "Progress" : "100",
   "Status" : "in progress"
}


Broadcast message from admin@moon (Wed Oct  8 09:37:07 2025):

The system is going down for reboot NOW!

[Expert@moon:0]# ./da_cli_status 216

*************************************
Action : Upgrade
Status : success
Package: aio_Check_Point_R82_T777_Gaia_Install_and_Upgrade.tgz
*************************************


[Expert@moon:0]# cpinfo -y FW1

This is Check Point CPinfo Build 914000250 for GAIA
[FW1]
	HOTFIX_WEBCONSOLE_AUTOUPDATE
	HOTFIX_GOT_MGMT_AUTOUPDATE
	HOTFIX_NGM_DOCTOR_AUTOUPDATE
	HOTFIX_INEXT_NANO_EGG_AUTOUPDATE
	HOTFIX_VCE_R81_20_AUTOUPDATE
	HOTFIX_PUBLIC_CLOUD_CA_BUNDLE_AUTOUPDATE
	HOTFIX_GOT_TPCONF_MGMT_AUTOUPDATE

FW1 build number:
This is Check Point Security Management Server R82 - Build 844
This is Check Point's software version R82 - Build 151

(i wrote myself a short script to fetch the da_cli actionID; got tired of typing that long command. 😁)

API status is good:

api st[Expert@moon:0]# api status

API Settings:
---------------------
Accessibility:                      Require all granted
Automatic Start:                    Enabled

Processes:

Name      State     PID       More Information
-------------------------------------------------
API       Started   28353     
CPM       Started   28353     Check Point Security Management Server is running and ready
FWM       Started   27701     
APACHE    Started   12281     

Port Details:
-------------------
JETTY Internal Port:               56264
JETTY Documentation Internal Port: 50714
APACHE Gaia Port:                  443

Profile:
-------------------
Machine profile:                   Large env resources profile with SME or Dedicated Log Server
CPM heap size:                     8192m

                          Apache port retrieved from: dbget http:ssl_port


--------------------------------------------
Overall API Status: Started
--------------------------------------------

API readiness test SUCCESSFUL. The server is up and ready to receive connections

Now gotta throw on the latest JHF and we're set!