topic Re: HA config sync only manually possible: Commit not synchronized in General Topics

HA config sync only manually possible: Commit not synchronized

Retired Member — Wed, 08 Jul 2020 14:49:00 GMT

Hey.

I enabled HA active-passive on a new 3220-pair. HA1a & b, HA 2 & HA backup are green and working fine so far. I can also do a manual sync, which works fine. In HA config i enabled config sync. The failover works fine too, as i tested it.

But it seems, there is no HA auto running-config sync to HA-peer. In dashboard (High Availability) i am in red "not syncronized" status and need to sync manually.

In monitoring, i can see the following warning:

any idea??

thanks guys.
Christian

Re: HA config sync only manually possible: Commit not synchronized

BPry — Wed, 08 Jul 2020 19:46:04 GMT

@Retired Member,

This generally happens if the peer unit has any changes made to it. I'd verify that the peer unit doesn't have some changes that haven't been committed or simply log into the peer unit and load the running-config and perform the manual sync again and see if that doesn't fix the issue.

Re: HA config sync only manually possible: Commit not synchronized

Retired Member — Wed, 08 Jul 2020 20:34:48 GMT

It seems always in this state, after manual commits (on all devices inkl. commit & push from panorama). aswell after manual sync (which works fine) its getting back to the "not syncronized" state, althought the sync was successfull

Re: HA config sync only manually possible: Commit not synchronized

BPry — Thu, 09 Jul 2020 04:22:07 GMT

Okay so it's not an easy one. You'll need to look at the devices ha_agent log and see what the logs are recording.

less mp-log ha_agent.log

Re: HA config sync only manually possible: Commit not synchronized

Retired Member — Tue, 28 Jul 2020 09:53:23 GMT

Thanks for help.

Finally got it now. I just deleted all of the HA config, exported Config on Device A, imported on Device B, changed IP-Settings and Hostname and tried again - now everything is fine, sync is working.

Don't know what really was the issue, but its solved 🙂