Forum Discussion
The HA concept is still work in progress as there is no association between the so called HA group feature and traffic groups.
Anyway, we have to deal with the current features and we are limited to legacy methods as are:
- VLAN Fail-Safe
- Gateway Fail-Safe
and the new
- HA Group
Make sure to use HA Group only or VLAN / Gateway Fail-Safe as alternative approach.
VLAN Fail-Safe needs to be activated per VLAN and will not be synchronized.
Make sure to apply it to production VLANs only, be conservative with the timeout (stay at least above 30 seconds) and use the failover action 'failover'. Otherwise it might be required to start the unit in single user mode to get out of a never ending loop ...
Gateway Fail-Safe will require to create two pools (which will be synchronized).
One Pool will assigned per device to be monitored as a failover trigger. This is a unique mapping.
Both with VLAN Fail-Safe and Gateway Fail-Safe you can face a standby/standby if both devices do not have the required resources!
An HA Group may contain pools of servers, aggregated links (trunk) and number of available blades (VIPRION only). Especially the trunk monitoring allows a pretty fast failover by using the bi-directional LACP protocol for link verification.
Using HA Groups requires some more brainwork as you need to calculate a proper balance of assigned wheigts and active bonus.
As mentioned before the HA Groups are fine to run v11 in active/standby because by now only a single HA Group per device can be created.