This article contains information about configuring reverse monitoring with the primary and secondary services on a NetScaler appliance.
When you bind primary and secondary services to the virtual server (VServer) on a NetScaler appliance, you can configure the appliance such that the status of the secondary service is marked as DOWN until the primary service is not available. You can do so by configuring reverse monitors to probe the primary service and bind the monitors to the secondary service. Additionally, bind the direct monitor to probe the primary service.
Until the primary service sends the correct response to the reverse monitor, the probe is considered as FAILED and the status of the service to which the monitor is bound is marked as DOWN.
To configure reverse monitoring with the primary and secondary services on a NetScaler appliance, run the appropriate set of the following commands, as required:
For an HTTP service, run the following commands:
>add lb monitor <Monitor_Name> HTTP -respCode 200 -httpRequest "HEAD /" -destIP <Primary_Service_IP_Address> -destPort 80 -reverse YES
>bind lb monitor <Monitor_Name> <Secondary_Service_Name>
For an ICMP service, run the following commands:
>add lb monitor <Monitor_Name> PING -destIP <Primary_Service_IP_Address> -reverse YES
>bind lb monitor <Monitor_Name> <Secondary_Service_Name>
The following table describes the conditions of reverse monitoring for an HTTP service:
Condition | Direct | Reverse |
Connection not established | Fail | Fail |
HTTP response code matches one of the configured | Success | Fail |
HTTP response code does not match one of the configured | Fail | Success |
Probe timed out | Fail | Fail |
The following table describes the conditions of reverse monitoring for an ICMP service:
Condition | Direct | Reverse |
ICMP echo reply is received | Success | Fail |
Probe timed out | Fail | Success |