Firewall cloning for DR

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Firewall cloning for DR

L2 Linker

Hello,

I have a Panorama that manage 2 cluster. Each one have a dedicated Device-Group and Template.

Now the cluster 2 must be recycled as a DR of the cluster 1. 

My idea is to reassign the cluster 2 to the same DG and Templ of the cluster 1. Should works, right?

As far as I know if I move the cluster 2 on the same DG/templ the Panorama "add" the new conf . How I can "force" to replace the entire conf with the Cluster 1conf on cluster 2?

Am I forgetting something?

There is any impact on the cluster 1 (like outage etc)?

 

Note. of course the Cluster 2 data plane interface will be moved in the DR Vlan to avoid the duplicated address

1 accepted solution

Accepted Solutions

Cyber Elite
Cyber Elite

Hi @Charlie80 ,

 

Yes, moving cluster 2 to the new device group and template will work.  The Policies and Objects will be replaced.  The Network and Device configuration may or may not be replaced.  It depends if anything is currently overridden on the NGFWs.  You may have to select Force Template Values.  You will get a warning that you may break connectivity because template have IP addresses, etc.  You should have Automated Commit Recovery enabled.  With any production cutover, you will need to do your due diligence to prevent outages.

 

Cluster 1 will not be impacted if you do not make any changes to the device group or templates.

 

Thanks,

 

Tom

Help the community: Like helpful comments and mark solutions.

View solution in original post

1 REPLY 1

Cyber Elite
Cyber Elite

Hi @Charlie80 ,

 

Yes, moving cluster 2 to the new device group and template will work.  The Policies and Objects will be replaced.  The Network and Device configuration may or may not be replaced.  It depends if anything is currently overridden on the NGFWs.  You may have to select Force Template Values.  You will get a warning that you may break connectivity because template have IP addresses, etc.  You should have Automated Commit Recovery enabled.  With any production cutover, you will need to do your due diligence to prevent outages.

 

Cluster 1 will not be impacted if you do not make any changes to the device group or templates.

 

Thanks,

 

Tom

Help the community: Like helpful comments and mark solutions.
  • 1 accepted solution
  • 1175 Views
  • 1 replies
  • 1 Likes
  • 38 Subscriptions
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!