Migrating existing clusters to different management server (R80.30)

[johnnyringo]

Last year I'd brought up a pair of R80.30 clusters with a temporary R80.30 management server.  

I'm now ready to migrate over to a permanent R80.30 management server, which was built by a co-worker.  Currently, this is my plan to migrate to the new management server.

1. Reset SIC on the gateways, create them in SmartConsole as if they were new clusters
2. Re-enter all settings and IP addresses
3. Re-create policy manually, install policy

This seems very manual and error-prone.  Is there a way to easily migrate, such as export/import or snapshot operations?   The policy isn't huge (only 25 rules or so) but I'd like to do anything possible to cut down the chance of an error.  

[Chris_Atkinson]

Is the new Management server fresh or does it have other gateways attached?

Depending on the details you can migrate the database:

https://sc1.checkpoint.com/documents/R80.30/WebAdminGuides/EN/CP_R80.30_Installation_and_Upgrade_Gui...

[johnnyringo]

The new management server already has a couple gateways attached.

[Chris_Atkinson]

If there are already gateways attached the process to merge them will be more manual and though there are some phython scripts that leverage the API that can help to a point. It might be helpful to enlist assistance from a partner or PS who have done this before.

Refer: https://community.checkpoint.com/t5/API-CLI-Discussion/Python-tool-for-exporting-importing-a-policy-...

Note also that support for R80.30 ends in September and you should consider upgrading. 

[johnnyringo]

OK, well given the policy is only 25 lines and can be re-entered within a couple hours, I'll probably just opt for the manual approach.  

And yes, I realize R80.30 is being phased out.  We just completed the migration off R77 less than 18 months ago, so...ummm..yeah....

[Chris_Atkinson]

For awareness if/when resetting SIC:

sk86521: Reset SIC without restarting the firewall process