The below specifications apply to the examples shown in this section using NSX Advanced Load Balancer UI.

  • The customer has multiple data centers.

  • Each application will require health monitors to be configured.

  • view.sales.avi.local will run in US-West and rely on US-Central as a disaster recovery site.

  • pay.sales.avi.local will run at US-West as well as US-East to achieve both high availability and optimal user experience.

This operation can only be performed by an authorized user logged into the GSLB leader Controller.

The Templates > Profiles > Global Health Monitor tab shows the five pre-existing system-standard monitors.

For a system-standard monitor, the better practice is to define a brand new monitor by clicking Create. The defaults that apply will be populated into the editor window, and can then be modified as desired. Refer to the New GSLB Health Monitor editor window below.

Successful Checks

The number of consecutive successful health checks before a virtual service is marked UP.

Failed Checks

The number of consecutive failed health checks before a virtual service is marked DOWN.

Send Interval

The number of seconds between health checks to a given virtual service.

Receive Timeout

A valid response from the server is expected within this number of seconds. It must be less than the send interval. If server status is regularly flapping between UP and DOWN, consider increasing this value.

Is Federated?

This option helps define the object’s replication scope. If enabled, the object is replicated across the federation. Else, it is visible within the Controller cluster and its associated SEs.

Is_federated is set to True only when GSLB is turned on. A federated health monitor is used for GSLB purposes while it is not applicable for a regular health monitor. This implies that a GSLB service cannot be associated with a regular health monitor, because the GSLB service is a federated object, while the health monitor is not. Conversely, A pool cannot be associated with a federated health monitor because the pool is not a federated object.

Health Monitor Port

Regardless of what port the associated virtual services use, this monitor will direct its health checks to port 80. A monitor port is mandatory for HTTP(S), TCP, UDP, and external health monitors.

Clicking Save in the new GSLB Health Monitor editor completes the custom-monitor creation.
Note:

In NSX Advanced Load Balancer, health monitoring is supported for DNS NSX Advanced Load Balancer configured in the active/standby mode.