AnsweredAssumed Answered

Transfer Policies between R77.30 and R80.10

Question asked by Ruan Kotze on Jul 12, 2018
Latest reply on Jul 31, 2018 by ccse89f54c70-508c-400f-9477-dd8648799b1e

Hi Everyone,

 

I have a scenario where we have an existing R77.30 cluster and a couple of standalone branch Gateways (r77.20) being managed by an R77.30 SMS.  We've purchased an additional two gateways, but due to regulatory requirements we need these to be managed by a separate SMS.  Obviously we'll go R80.10 for the new cluster and GW.

 

This is all simple enough, but we want to copy our existing policies and objects from the R77.30 SMS to the new R80.10 one.  My plan is as follows:

1.  Do advanced upgrade with DB migration to pull everything accross to the R80.10 SMS

2.  Start up the R80.10 SMS in a isolated network (no access to any of the existing Gateways) and delete the existing R77.30 gateways and all references to them from the policies, VPN Communities etc.

3.  Save all changes

4.  Hook R80.10 back up to production network and build a new cluster with my R80.10 gateways

5.  Push policy

 

My main priority is obviously not to impact or disrupt anything on the existing R77.30 SMS and gateways.

 

Appreciate any and all feedback!

Outcomes