Three devices clustered but only 2 is going active when using "force to standby"

Question

HI All,&nbsp;
I have 3 devices in cluster.&nbsp;
bigip1
bigip2
bigip3&nbsp;
bigip1 is my current active.when the bigip1 was forced to standby, bigip2 becames active. When we force bigip2 to standby, the active state only goes back to bigip1. Is this a correct behaviour? The bigip3 only get active when we change the ha-order in traffic-group.&nbsp;
Thanks!
Ferdz&nbsp;

henrik_gyllkran · Answer

Yes, that is indeed how it's supposed to work. The default failover method for a traffic group is "Load Aware" so unless you have multiple traffic groups and bigip1 is already active for those I suspect that since there is a tie between bigip1 and bigip3 when you force bigip2 to standby bigip1 will win simply by being the first BIG-IP in the list. Read more about the Load Aware calculation here:&nbsp;
https://support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/tmos-implementations-11-6-0/6.html?sr=49108538&nbsp;

Forum Discussion

Three devices clustered but only 2 is going active when using "force to standby"

1 Reply

Recent Discussions

Rundeck ansible F5 errors

What is the meaning is 52% block in WAF

rewrite Azure AD response for portal access via web portal

AS3 Monitoring multiple ports selectively

Open Redirection Mitigation

Related Content

F5 BIG-IP per application Red Hat OpenShift cluster migrations

F5 BIG-IP deployment with OpenShift - multi-cluster architectures

Integrating with your IPv6 Kubernetes Cluster

Multiple Kubernetes Clusters and Path-Based Routing with F5 Distributed Cloud

Multi-Cluster, Multi-Cloud Networking for K8S with F5 Distributed Cloud – Architecture Pattern