For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

sync issue

3 Topics

Can't change sync type or failover after tenant upgrade.
I made a mistake that I didn't think in the end would matter, but here's what I did. I had previously upgraded this tenant pair to 17.1.3. Everything was fine, and I intended to install on another pair but I installed on the other boot location of one that I had already installed. I didn't think this was an issue as I would just not activate that boot location. However, I couldn't force the Active member to Standby. It was greyed out. I thought that maybe I should boot to that new location because maybe there was something that needed to complete to allow me to fail over between the members. That made it worse because I couldn't change the sync type back to Automatic with incremental sync. So naturally, I booted to the previous partition because it seemed to be at least better, but now I seem to be digging a hole I can't get out of. Where it stands now: The pair is set to sync type "Manual with Incremental Sync" Member1 is standby and says "Not All Devices Synced" Member2 is active and says "Changes Pending" On the Standby Member1, I can change the sync type, but I haven't. On the Active Member2, I can't change the sync type or force it to standby. I have a ticket open but as this is a live system, I pursuing all avenues.
Solved
Shadow
Nov 10, 2025 Place Technical Forum
88Views
0likes
7Comments
Sync-issue when configured FQDN Node to pool with autopopulate enabled
In relation to this article https://my.f5.com/manage/s/article/K02805156, we resolved the issue by manually configuring the FQDN nodes to pool on the paired device prior to syncing.
Troy
Aug 27, 2024 Place Technical Forum
78Views
0likes
1Comment
Can't Sync Cluster : 010717e1:3: Client SSL profile cannot contain more than one set of same certificate/key type..
Hi, I can't sync my cluster do to the following error : 010717e1:3: Client SSL profile cannot contain more than one set of same certificate/key type.. It looks like I'm in a case related here : K16218 I've removed all the difference between my client SSL profile and even deleted the one I've modified. How can I force the sync of the cluster to bypass this SSL profile problem ? Thanks
ldesfosses
Jun 02, 2023 Place Technical Forum
318Views
0likes
1Comment