Policy install crashes primary gateway 0-2000030

[joecool]

I was working on a web application in the mobile access blade, finished some changes and pushed policy, a fail over occurred. The primary gateway had rebooted and came up with the policy "defaultfilter" so we were unable to access it, we got to the console and started troubleshooting but we were unable to determine the problem.  So we rebuilt the now non working gateway. When installing policy on the cluster the same situation occurred, the working member had a failure and rebooted the newly rebuilt firewall became primary and we had basically moved the problem from one to the other.

Further troubleshooting we changed the ip address of the working newly rebuilt gateway in management so it can't get policy and tried a policy install and got the following error. Policy installation failed on gateway. If the problem persists contact Check Point support (Error code: 0-2000030). There is an sk166976 which has a procedure to fix the problem but it didn't work. This is on an r80.30 t_196 open server.

We feel that if we rebuild the non working gateway again the same trouble will happen again so we are stuck unable to install policy and do not have redundancy. At this point we are waiting on checkpoint to find the problem but really want to get this fixed so any help would be greatly appreciated.

Thanks,
Joe

[_Val_]

@joecool Do you have a case with TAC?

[G_W_Albrecht]

Strange - sk166976 must be an internal SK as i can not find it...

[_Val_]

Yes, it is internal, and was exposed before by mistake.

[imados]

Hello,

I am facing the same issue in a CloudGuard IaaS Gateway, Did you find a solution to your problem ?

Thanks,

Imad

[j-bal]

Check out sk171553.  We havent tested this yet but we along with other Azure customers are experiencing similar behavior on a VMSS config.