# BIG-IP VE VMWare Cluster HA triggering configuration

**URL:** <https://community.f5.com/t/big-ip-ve-vmware-cluster-ha-triggering-configuration/70496>\
**Category:** Technical Forums\
**Tags:** cloud, failover, ha, big-ip-ve\
**Created:** [September 9, 2022, 8:16am UTC](https://community.f5.com/t/big-ip-ve-vmware-cluster-ha-triggering-configuration/70496 "2022-09-09T08:16:22Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ASF](https://avatars.discourse-cdn.com/v4/letter/a/c4cdca/32.png) [@ASF](https://community.f5.com/u/ASF)\
**Post date:** [September 9, 2022, 8:16am UTC](https://community.f5.com/t/big-ip-ve-vmware-cluster-ha-triggering-configuration/70496/1 "2022-09-09T08:16:22Z")

</div>

Hi,

this is my first step&nbsp; into BIG-IP VE deployments (always viprion so far).

I have all my test clusters up & running in a VMWare environment: Active/Stanby using dedicated vNIC&VLAN.

4 vNIC per device, 2 cluster members, each one running at different ESXi.

But I would like to ccountercheck which would be the best option to trigger HA. At PHY deployments we deploy HA Group based on trunks. Now this does not work for all cases.

Would a failsafe condition based on VLAN be the best solution? E.g. with failover to the sdby BIG-IP in case no ARP was received from client\_VLAN gateway?

any comment wellcome!

Regards.

---

<div class="post-metadata">

**Author:** ![JoshBecigneul](https://d1p9zq3aats0t8.cloudfront.net/user_avatar/community.f5.com/joshbecigneul/32/19933_2.png) [@JoshBecigneul](https://community.f5.com/u/JoshBecigneul)\
**Post date:** [September 16, 2022, 1:13am UTC](https://community.f5.com/t/big-ip-ve-vmware-cluster-ha-triggering-configuration/70496/2 "2022-09-16T01:13:15Z")

</div>

Hi&nbsp; @ASF &nbsp;,

I think you might need to consider some questions around the failsafe topic, including what your expected failure scenarios might be. For instance, in a virtual environment I’d say the chances of losing the VLAN near to the interface of the VE are low, but something like a missing gateway or an upstream connection might be a greater risk. You should also only configure VLAN failsafe on the vlans that truly matter.

The other option, gateway failsafe, can monitor one or more upstream gateways, depending on the architecture.&nbsp;[https://support.f5.com/csp/article/K75303031](https://support.f5.com/csp/article/K75303031)

HA Group builds on gateway failsafe but can work at the traffic group level, should you have a need for that level of control.&nbsp;[https://support.f5.com/csp/article/K42542000](https://support.f5.com/csp/article/K42542000)

---

<div class="post-metadata">

**Author:** ![ASF](https://avatars.discourse-cdn.com/v4/letter/a/c4cdca/32.png) [@ASF](https://community.f5.com/u/ASF)\
**Post date:** [September 16, 2022, 3:22am UTC](https://community.f5.com/t/big-ip-ve-vmware-cluster-ha-triggering-configuration/70496/3 "2022-09-16T03:22:39Z")

</div>

Thanks&nbsp; @JoshBecigneul &nbsp;, very useful!

Regards
