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.

Getting Started with BIG-IP Next: Configuring Instance High Availability

With BIG-IP classic, there are a lot of design choices to make and steps on both systems to arrive at an HA pair. With BIG-IP Next, this is simplified quite a bit. Once configured, the highly availab...
Updated Mar 11, 2024
Version 2.0
application delivery
big-ip next
central manager
JRahm's avatar
Icon for Admin rankAdmin
Christ Follower, Husband, Father, Technologist. I love community and I especially love THIS community. My background is networking, but I've dabbled in all the F5 iStuff, I'm a recovering Perl guy, and am very much a python enthusiast. Learning alongside all of you in this accelerating industry toward modern apps and architectures.
View Profile
jreaves's avatar
jreaves
Icon for Nimbostratus rankNimbostratus
Jun 10, 2024

i have both n1/n2 nodes in central manager and both show healthy. I follow these steps and when cm is trying to create the ha I get an error that says "unable to connect to the https server on peer node ip x.x.x.x" pairup failed.  I checked our firewall logs and see no communications from the central manager to this ip. Also the ctrl plane ha, data plane ha, dataplane-ext and dataplane-int vlans are all on the same router with no acls so nothing should be blocking their access.  Any idea's on what would cause this issue?

Scot_JC's avatar
Scot_JC
Icon for Employee rankEmployee
Aug 09, 2024

Hi, I experienced the same difficulty - "unable to connect to the https server on peer node ip x.x.x.x" - once and I think I got over this with ensuring the active instance is licensed.