Create a Post
cancel
Showing results for 
Search instead for 
Did you mean: 
JayM1
Participant
Jump to solution

Removing member from ClusterXL

Hi All,

I have a pair of 3920 gateway appliances in a clusterXL setup and want to remove one of them to use elsewhere.  

Whats the best way to remove without causing an outage, issues with policy pushes and sync issues ?   

 

0 Kudos
1 Solution

Accepted Solutions
MarcusJ
Participant
Participant

@JayM1 wrote:

Will I need to login to active member and disable cluster membership there as well and reboot?    


It depends on the situation.

If the gateway will operate as a standalone, disable cluster membership in cpconfig and reboot it.

Otherwise these issues might appear:

  • Policy installation may fail with errors about cluster membership.
  • Features like Static NAT may not work correctly.
  • The gateway may not function properly as a standalone device.


    Disabling cluster membership modifies how the gateway's kernel modules and Check Point services operate.
    ClusterXL and related high-availability modules are loaded at boot time. Disabling cluster membership removes these modules from the boot process. A reboot ensures that all cluster-related processes and kernel modules are fully unloaded and that the gateway starts in standalone mode.

If the gateway will be added shortly to another cluster you can keep cluster membership active in cpconfig.

 

View solution in original post

0 Kudos
3 Replies
Lesley
MVP Platinum
MVP Platinum

Please follow this SK:

https://support.checkpoint.com/results/sk/sk36441

Or as a reference the admin guide, SK sounds better to me tbh. Any cases would recommend window

https://sc1.checkpoint.com/documents/R82/WebAdminGuides/EN/CP_R82_ClusterXL_AdminGuide/Content/Topic...

 

-------
Please press "Accept as Solution" if my post solved it 🙂
0 Kudos
JayM1
Participant

Will I need to login to active member and disable cluster membership there as well and reboot?    

0 Kudos
MarcusJ
Participant
Participant

@JayM1 wrote:

Will I need to login to active member and disable cluster membership there as well and reboot?    


It depends on the situation.

If the gateway will operate as a standalone, disable cluster membership in cpconfig and reboot it.

Otherwise these issues might appear:

  • Policy installation may fail with errors about cluster membership.
  • Features like Static NAT may not work correctly.
  • The gateway may not function properly as a standalone device.


    Disabling cluster membership modifies how the gateway's kernel modules and Check Point services operate.
    ClusterXL and related high-availability modules are loaded at boot time. Disabling cluster membership removes these modules from the boot process. A reboot ensures that all cluster-related processes and kernel modules are fully unloaded and that the gateway starts in standalone mode.

If the gateway will be added shortly to another cluster you can keep cluster membership active in cpconfig.

 

0 Kudos

Leaderboard

Epsum factorial non deposit quid pro quo hic escorol.

Upcoming Events

    CheckMates Events