Install Check Point Jumbo Hotfix Accumulator with CPUSE

Import, verify and install a Check Point Jumbo Hotfix Accumulator using CPUSE from Gaia Clish.

ⓘ

Validation status

Reviewed against the current Check Point CPUSE Administration Guide and R82 administration documentation on 27 September 2026.

!

Plan the maintenance activity first

Hotfix installation can restart Check Point services and some packages require a reboot. On clusters, scalable platforms and management systems, follow the product-specific installation sequence for the target release and architecture. Confirm backups/snapshots, rollback options, available disk space and cluster health before starting.

Before you start

Use a CPUSE package that is explicitly supported for the installed Check Point release and platform.

Do not manually unpack and force-install the CPUSE Deployment Agent RPM as the normal hotfix workflow. The legacy Tech-Wiki article included an R77.30-era Deployment Agent RPM procedure; current CPUSE documentation uses the Gaia installer commands directly.

Useful checks before installation include:

>_Review installed version and CPUSE packages

show version all
show installer packages all

Import an offline package

Transfer the approved CPUSE offline package to the Gaia system, for example under /var/log/, then enter Gaia Clish.

>_Import a local CPUSE package

installer import local /var/log/Check_Point_Hotfix_Bundle_FULL.tgz

Show imported packages and identify the package ID:

>_List imported packages

show installer packages imported

Verify compatibility

Always run CPUSE verification before installation.

>_Verify the imported package

installer verify <PACKAGE_ID>

Review the complete verification result and resolve any prerequisite or compatibility errors before continuing.

Install

!

Check cluster and reboot requirements

Do not start installation simply because verification succeeds. Confirm the supported member order, expected traffic impact and reboot behaviour for the target platform and package.

>_Install the verified package

installer install <PACKAGE_ID>

Monitor the installation until CPUSE reports completion and then verify the system, Check Point services and cluster state as appropriate.

Post-install checks

Typical checks include:

>_Basic post-install verification

show version all
cpwd_admin list

On ClusterXL systems, also confirm that the intended members return to their expected state before proceeding with another member.

✓

Keep the package ID with the change record

Record the CPUSE package name, package ID, Jumbo Hotfix take, installation time and verification outcome so the installed state can be correlated with the maintenance record.

Official references

• Check Point CPUSE - Installing a Software Package on Gaia
• Check Point CPUSE - Gaia Clish syntax
• Check Point R82 Scalable Platforms Administration Guide

See also

• Check Point
• Tune Check Point ClusterXL policy installation timeout