Uninstalling a Hotfix from a Single Chassis

This procedure describes the Full Connectivity uninstall of an Offline CPUSE package from a Single Chassis.

Important Notes

It is not supported to upgrade the CPUSE Agent on SGMs in a Security Group.
This procedure keeps the current connections in a Security Group A logical group of Security Gateway Modules that provides Active/Active cluster functionality. A Security Group can contain one or more Security Gateway Modules. Security Groups work separately and independently from each other. To the production networks, a Security Group appears a single Security Gateway..
This procedure applies to Security Groups in Security Gateway mode and VSX mode.

In VSX mode, you must run all the commands in the context of VS0.

Do not uninstall the hotfix from all the SGMs at the same time.

If you do so with the command below, traffic stops passing through all SGMs until the hotfix is uninstalled:

installer uninstall <Number of CPUSE Package> member_ids all

In this procedure, you divide all SGMs in a specific Security Group into two or more logical groups.

In the procedure below, we use two logical groups denoted below as "A" and "B".

You uninstall the hotfix from one logical group of the SGMs at one time.

The other logical group(s) of the SGMs continues to handle traffic.

Each logical group should contain the same number of SGMs - as close as possible.

Examples:

Environment	Description
Single Chassis	There are 8 SGMs in the Security Group. The Logical Group "A" contains SGMs from 1_1 to 1_4. The Logical Group "B" contains SGMs from 1_5 to 1_8.
Single Chassis	There are 5 SGMs in the Security Group. The Logical Group "A" contains SGMs from 1_1 to 1_3. The Logical Group "B" contains SGMs from 1_4 to 1_5.

Best Practice - Perform this procedure over the serial console.

Procedure

Step 1 - Disable the SMO Image Cloning feature

Note - The SMO See "SMO". Image Cloning feature automatically clones all the required software packages to the SGMs during their boot. When you install or remove software packages gradually on SGMs, it is necessary to disable this feature, so that after a reboot the updated SGMs do not clone the software packages from the existing non-updated SGMs.

Step

Instructions

Connect to the command line on the Security Group.

If your default shell is /bin/bash (Expert mode), then go to Gaia gClish The name of the global command line shell in Check Point Gaia operating system for Security Gateway Modules. Commands you run in this shell apply to all Security Gateway Module in the Security Group.:

gclish

Examine the state of the SMO Image Cloning feature:

show smo image auto-clone state

Disable the SMO Image Cloning feature, if it is enabled:

set smo image auto-clone state off

Examine the state of the SMO Image Cloning feature:

show smo image auto-clone state

Step 2 - Uninstall a Hotfix from SGMs in the Logical Group "A"

Step

Instructions

Connect in one of these ways:

Connect to one of the SGMs in the Logical Group "A" through the console.
Connect to one of the SGMs in the Logical Group "B" over SSH.

Go to the context of one of the SGMs in the Logical Group "A":

member <Member ID>

Example:

member 1_1

Go to the Expert mode.

expert

Set the SGMs in the Logical Group "A" to the state "DOWN":

g_clusterXL_admin –b <SGM IDs in Group "A"> down

Example:

[Expert@HostName-ch0x-0x:0]# g_clusterXL_admin -b 1_1-1_4 down

Go to the Gaia gClish:

gclish

Uninstall the CPUSE package from SGMs in the Logical Group "A":

installer uninstall [Press the Tab key]

installer uninstall <Number of CPUSE Package> member_ids <SGM IDs in Group "A"

Example:

[Global] HostName-ch01-01 > installer uninstall 2 member_ids 1_1-1_4
... ...
Update Service Engine
+------------------------------------------------------------------------------+
|Member ID    |Status                                                          |
+-------------+----------------------------------------------------------------+
|1_01 (local) |Package is ready for uninstallation                             |
|1_02         |Package is ready for uninstallation                             |
|1_03         |Package is ready for uninstallation                             |
|1_04         |Package is ready for uninstallation                             |
+-------------+----------------------------------------------------------------+
The machines (1_02,1_02,1_03,1_04) will automatically reboot after uninstall.
Do you want to continue? ([y]es / [n]o) y

Go to the Expert mode.

expert

Monitor the SGMs in the Logical Group "A" until they boot:

asg monitor

Step 3- Uninstall a Hotfix from SGMs in the Logical Group "B"

Step

Instructions

Connect in one of these ways:

Connect to one of the SGMs in the Logical Group "B" through the console.
Connect to one of the SGMs in the Logical Group "A" over SSH.

Go to the context of one of the SGMs in the Logical Group "B":

member <Member ID>

Example:

member 1_5

Go to the Expert mode.

expert

Set the SGMs in the Logical Group "B" to the state "DOWN":

g_clusterXL_admin –b <SGM IDs in Group "B"> down

Example:

[Expert@HostName-ch0x-0x:0]# g_clusterXL_admin -b 1_5-1_8 down

Go to the Gaia gClish:

gclish

Uninstall the CPUSE package from SGMs in the Logical Group "B":

installer uninstall [Press the Tab key]

installer uninstall <Number of CPUSE Package> member_ids <SGM IDs in Group "B"

Example:

[Global] HostName-ch01-01 > installer uninstall 2 member_ids 1_5-1_8
... ...
Update Service Engine
+------------------------------------------------------------------------------+
|Member ID    |Status                                                          |
+-------------+----------------------------------------------------------------+
|1_05 (local) |Package is ready for uninstallation                             |
|1_06         |Package is ready for uninstallation                             |
|1_07         |Package is ready for uninstallation                             |
|1_08         |Package is ready for uninstallation                             |
+-------------+----------------------------------------------------------------+
The machines (1_05,1_06,1_07,1_08) will automatically reboot after uninstall.
Do you want to continue? ([y]es / [n]o) y

Go to the Expert mode.

expert

Monitor the SGMs in the Logical Group "B" until they boot:

asg monitor

Step 4 - Make sure the Hotfix is uninstalled

Step

Instructions

Connect to the command line on the Security Group.

Go to the Expert mode.

expert

Run:

asg diag verify

Step 5 - (Optional) Delete the uninstalled Hotfix package from the Chassis

In this optional step, you delete the uninstalled Hotfix package from the chassis to free the disk space.

Step

Instructions

Go to the Gaia gClish:

gclish

Delete the uninstalled Hotfix package from the CPUSE repository on the chassis:

installer delete [Press the Tab key]

installer delete <Number of CPUSE Package>

Example:

[Global] HostName-ch01-01 > installer delete 2
... ...
Update Service Engine
+------------------------------------------------------------------------------+
|Member ID    |Status                                                          |
+-------------+----------------------------------------------------------------+
|1_01 (local) |Package is ready for delete                                     |
|1_02         |Package is ready for delete                                     |
|1_03         |Package is ready for delete                                     |
|1_04         |Package is ready for delete                                     |
|1_05         |Package is ready for delete                                     |
|1_06         |Package is ready for delete                                     |
|1_07         |Package is ready for delete                                     |
|1_08         |Package is ready for delete                                     |
+-------------+----------------------------------------------------------------+
You are about to perform
Package delete (Check_Point_R81.20_Hotfix_Bundle_FULL.tar) on blades:
1_01,1_02,1_03,1_04,1_05,1_06,1_07,1_08
*** In case the package is installed, you might not be able to uninstall and Import the package ever again ! ***

Are you sure? (Y - yes, any other key - no) y
Update Service Engine
+------------------------------------------------------------------------------+
|Member ID    |Status                                                          |
+-------------+----------------------------------------------------------------+
|1_01 (local) |The package was successfully removed from the machine.          |
|1_02         |The package was successfully removed from the machine.          |
|1_03         |The package was successfully removed from the machine.          |
|1_04         |The package was successfully removed from the machine.          |
|1_05         |The package was successfully removed from the machine.          |
|1_06         |The package was successfully removed from the machine.          |
|1_07         |The package was successfully removed from the machine.          |
|1_08         |The package was successfully removed from the machine.          |
+-------------+----------------------------------------------------------------+
[Global] HostName-ch01-01 >