topic Re: HA failover if Running Config is not synced in General Topics

HA failover if Running Config is not synced

MP18 — Thu, 15 Nov 2018 23:15:24 GMT

If on Active Passive PA both shows running config not sync

Say failover happens for somereason or we trigger the manual failover bgy suspending the active PA will then

Passive PA becomes active and start passing the traffic even though running config is not syc between two?

Re: HA failover if Running Config is not synced

BPry — Fri, 16 Nov 2018 22:16:04 GMT

The passive PA will still become active, and will still pass traffic, it simply will not be utilizing the same configuration file. This can cause issues for example if you've since added/removed additional security policies that are not present on the peer HA unit; a function that is expected to be working could possibly stop functioning simply because the configuration was not in sync with your peer unit.

Re: HA failover if Running Config is not synced

MP18 — Sat, 17 Nov 2018 01:44:17 GMT

Best Regards

Mike

Re: HA failover if Running Config is not synced

Pras — Mon, 11 Jul 2022 00:25:35 GMT

@BPry
I m having similar issue and I am interested to know how to safely make the configurations same on both the HA pairs?

Thanks

Re: HA failover if Running Config is not synced

BPry — Tue, 12 Jul 2022 20:12:14 GMT

@Pras,

What error are you seeing recorded in the logs for a configuration sync failure? What happens if you attempt to sync the configuration from the active to the passive manually? You ultimately need to figure out why the configuration isn't syncing automatically. That could be something as simple as a user holding a configuration lock on the passive unit, or a larger issue.

Re: HA failover if Running Config is not synced

Pras — Fri, 15 Jul 2022 04:13:22 GMT

@BPry There are no specific/interesting log errors but when I compared the config files. I noticed the configs are not exact and some configs are within different folders within the .xml file . It's strange. I m wondering how can I safely copy the config from primary to secondary. I saw another KB saying need to edit manually: management address and HA IPs and peer IPs, and hostname. Are these the only parameters that need to be edited?
Thanks