![]() ![]() Gateway health checking is supported for both Avi SEs. You can enable health checks for each Avi SE’s next-hop gateways. You can also disable health monitoring by an SE for virtual services for which it is standing by. Standby virtual services are shown in light grey.īy default, health checks are sent by both Avi SEs to back-end servers. Virtual services running on a legacy HA SE group are not disrupted during a rolling upgrade.įigure 1: Legacy HA active/standby, showing compacted and distributed load options. Two options, compacted and distributed (figure 1), determine whether all active virtual service placements are concentrated onto one SE in a healthy pair or not.Īvi Vantage supports rolling upgrades by the Avi Controller of SEs in a legacy HA configuration. ![]() As part of the takeover process, the survivor also takes ownership of all floating addresses, such as VIPs, SNAT-IP, and so on. Upon failure of an SE, the surviving SE takes over traffic for all virtual services previously active on the failed SE, while continuing to handle traffic for virtual services already assigned to it. The other SE in the pair is the standby for that VS, carrying no traffic for it while the other SE is healthy. In this mode, one SE carries all the traffic for a virtual service placed on it, and is thus the active SE for that VS. By default, active virtual services are compacted onto one SE, as illustrated in Figure 1. In legacy HA mode, exactly two Avi SEs are configured. Legacy active/standby is useful for migrating from hardware appliance-based solutions.Īvi Vantage also provides elastic HA, including active/active and N+M modes. Legacy active/standby high availability (HA) is available for Avi Service Engine (SE) redundancy. Legacy HA for Avi Service Engines Overview ![]()
0 Comments
Leave a Reply. |