active/passive HA setup with existing production firewall

Reply
L2 Linker

active/passive HA setup with existing production firewall

I have a second PA-500 I need to add to an existing production PA-500 for active/passive HA. I have read the admin guide for HA setup, but it appears to be for two pre-production firewalls. Are there any special precautions I need to take into account so that the post production firewall syncs it's config to the new firewall? The admin guide dosen't seem to say.

 

Thanks,


Accepted Solutions
L7 Applicator

i'd first enable HA on the production firewall without connecting the new one just yet

 

once the config is committed it will show as an active member and the cluster is broken (because the secondary member is 'down')

 

next, configure the second member's basics: HA config, management config (leave everything else default) and make sure it's device priority in HA is higher than the active member (higher number = lower priority) and cluster ID is identical

once that configuration is committed, suspend the secondary's HA functionality

> request high-availability state suspend 

next, hook up the HA cables and wait until member 1 reports the cluster is connected

 

once HA is up (there will be error messages as the config is out of sync) perform a sync-to-peer on the primary unit:

 

 > request high-availability sync-to-remote running-config

this will send the active configuration to the new device and commit it

Tom Piens - PANgurus.com
Like my answer? check out my book! amazon.com/dp/1789956374

View solution in original post


All Replies
L6 Presenter

Hi,

 

l haven't done much of HA set-ups but make sure you do have a local backup copy of your configuration (somewhere on your MGMT station).

Then just follow the guide, make a priority to be higher (lower number) on the current running box with preemption is enabled. Can also disable config sync while doing configuration, after all tested enable it back. 

 

Cheers,

Myky

L7 Applicator

i'd first enable HA on the production firewall without connecting the new one just yet

 

once the config is committed it will show as an active member and the cluster is broken (because the secondary member is 'down')

 

next, configure the second member's basics: HA config, management config (leave everything else default) and make sure it's device priority in HA is higher than the active member (higher number = lower priority) and cluster ID is identical

once that configuration is committed, suspend the secondary's HA functionality

> request high-availability state suspend 

next, hook up the HA cables and wait until member 1 reports the cluster is connected

 

once HA is up (there will be error messages as the config is out of sync) perform a sync-to-peer on the primary unit:

 

 > request high-availability sync-to-remote running-config

this will send the active configuration to the new device and commit it

Tom Piens - PANgurus.com
Like my answer? check out my book! amazon.com/dp/1789956374

View solution in original post

L2 Linker

Thanks for the Info. This helped.

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!