Gateway Monitoring for Legacy HA
Avi Vantage supports health monitoring of the first-hop gateways connected to Avi Service Engines (SEs). As of release 17.2.3 it can also monitor routers which are not directly connected. ICMP echo packets are used to perform the health monitoring.
Gateway health monitoring is performed from both active and standby Avi SEs.
- The current release supports gateway health monitoring only for Avi SEs configured for legacy high availability (HA).
- Another article of interest: Avi SE Behavior on Gateway Monitor Failure
Enabling Gateway Health Monitoring
Gateway health monitoring is part of the cloud configuration. If and when an IP address to monitor is furnished, then all legacy HA SE groups within the particular cloud perform gateway health monitoring.
- Navigate to Infrastructure > Clouds.
- Click the edit icon next to the name of the cloud to modify (for example, Default-Cloud).
- Click Gateway Monitor.
- Click Create.
- Enter the gateway information, including IP address, and click Save.
Use the following commands to configure monitoring for a gateway:
:> configure vrfcontext global
vrfcontext> gateway_mon 192.168.1.10
Make sure to use the IP address of the gateway where this example shows “192.168.1.10.”
Enhancements in Avi Vantage release 16.2.3
Beginning with the 16.2.3 release, it is possible to configure multiple gateway monitors. This is typically useful in two-armed deployment where the first-hop gateway used for front-end and back-end connections are different.
Switchover of the virtual service is triggered if failure is detected in at least one gateway.
Monitoring of Routers Not Directly Connected
Starting with Avi Vantage 17.2.3, gateway monitoring can be extended to routers which are not directly connected. The administrator must take these steps:
Ensure there is an appropriate route in Avi Vantage to provide reachability to the indirectly connected router via Infrastructure > Routing > Static Route.
Configure the new
subnetfield for that gateway monitor to point to the interface network through which the router is reachable. Use these CLI commands:
configure vrfcontext global gateway_mon index 1 subnet 10.10.71.0/24 save save
- In the
1is the index to the router if it is already configured via the Avi UI.
- In the
10.10.71.0/24is the interface network on the SE through which the router being monitored is reachable.