Lost SGM

[Bilguunbileg]

Dears,

I have a some problems. new SGM can not connect and below is log. New SGM is lost situation.

[Expert@mn-dc1-r1c1-sec-fw.sg-ch01-01:0]# cphaprob stat

Cluster Mode: HA Over LS

ID Unique Address Assigned Load State Name

1 (local) 192.0.2.1 100% ACTIVE(!) mn-dc1-r1c1-sec-fw.sg-ch01-01
2 none 0% LOST mn-dc1-r1c1-sec-fw.sg-ch01-02

Active PNOTEs: during_upgrade

Last member state change event:
Event Code: CLUS-116505
State change: DOWN -> ACTIVE(!)
Reason for state change: All other machines are dead (timeout), FULLSYNC PNOTE
Event time: Fri Oct 11 01:05:48 2024

[Expert@mn-dc1-r1c1-sec-fw.sg-ch01-01:0]#

But ping and ssh is successfully.

[Expert@mn-dc1-r1c1-sec-fw.sg-ch01-01:0]# ping 192.0.2.2
PING 192.0.2.2 (192.0.2.2) 56(84) bytes of data.
64 bytes from 192.0.2.2: icmp_seq=1 ttl=64 time=0.305 ms
64 bytes from 192.0.2.2: icmp_seq=2 ttl=64 time=0.066 ms
64 bytes from 192.0.2.2: icmp_seq=3 ttl=64 time=0.070 ms

How can i fix that issue? Please check this issue

[AkosBakos]

Hi @Bilguunbileg 

I found this article, but here the SGM remained in DOWN state. Maybe helpful.

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

Symptoms

• A Security Group Member (SGM) in a Security Group is in the "DOWN" state after an upgrade to R81.10.

• When you reboot the applicable SGM, it goes to the "INIT" state and then to the "DOWN" state.

• This error appears during the boot stage:

  during_upgrade already exists in list. First remove.
  Updating of persistant storage failed
  Registered during_upgrade in failure detection mechanism.
  Registration no. 4
  

• Below is the applicable pnote:

  Device Name: during_upgrade
  
  Registration number: 4
  
  Timeout: none
  
  Current state: problem
  
  Time since last report: 4766.2 sec
  

Cause

The upgrade did not complete on the SGM in the "DOWN" state.

Solution

This problem was fixed. The fix is included starting from:

• Check Point R81.20

---

This workaround is available for a Multi-Version Cluster (MVC) upgrade.

Run this command on the SGM in the DOWN state:

# sp_upgrade --cleanup