In Global Server Load Balancing (GSLB), what is the effect of setting triggerMonitor MEPDOWN on a site regarding default service monitoring?

In Global Server Load Balancing (GSLB), what is the effect of setting triggerMonitor MEPDOWN on a site regarding default service monitoring?

• A. The state of the GSLB service will always be controlled by Metric Exchange Protocol (MEP).
• B. The service monitor is invoked only when Metric Exchange Protocol (MEP) has marked the service as DOWN for any reason.
• C. The service monitor will take precedence over Metric Exchange Protocol (MEP).
• D. The service monitor is invoked only when Metric Exchange Protocol (MEP) connectivity has been lost between SiteA and SiteB.

Answer: (D)

Triggering monitor MEPDOWN makes GSLB use the MEP connectivity status as the gate for running the local service monitor. If the MEP link between sites is healthy, the default service monitor isn’t invoked. Only when MEP connectivity has been lost between the sites will the service monitor be run to verify the actual service status. This setup prevents unnecessary service checks during normal cross-site communication and ensures a recheck happens only when the inter-site link fails.

Triggering monitor MEPDOWN makes GSLB use the MEP connectivity status as the gate for running the local service monitor. If the MEP link between sites is healthy, the default service monitor isn’t invoked. Only when MEP connectivity has been lost between the sites will the service monitor be run to verify the actual service status. This setup prevents unnecessary service checks during normal cross-site communication and ensures a recheck happens only when the inter-site link fails.