ADC

Enable external health check for UDP and non-HTTP virtual servers

September 6, 2023

Contributed by:

C S

In public clouds, you can use the NetScaler appliance as a second-tier load balancer when the native load balancer is used as the first tier. The native load balancer can be an application load balancer (ALB) or a network load balancer (NLB). Most of the public clouds do not support UDP health probes in their native load balancers. Hence, if these servers are down their actual status might not be updated. As a result, traffic is sent unconditionally to NetScaler, even if the request cannot be serviced. To monitor the health of such applications, NetScaler supports HTTP and TCP health checks.

An HTTP or TCP listener is created for a content switching virtual server when both the probeProtocol and probePort parameters are configured. The listener reflects the status of the virtual server. The ProbeSuccessResponseCode parameter applies only to HTTP and returns the configured string when the probe is successful.

To enable external health check for UDP and non-HTTP TCP virtual servers by using CLI

At the command prompt, type:

add lb vserver <name> <serviceType> <IPAddress> <port> -ProbeProtocol <HTTP/TCP> -ProbePort <port-num> -ProbeSuccessResponseCode<http-code>
<!--NeedCopy-->

Example:

add lb vserver Vserver-UDP-1 HTTP 10.102.29.60 80 -ProbeProtocol TCP -probeport 5000 -probesuccessResponseCode 200ok
<!--NeedCopy-->

To enable external health check for UDP and non-HTTP TCP virtual servers by using GUI

Navigate to Traffic Management > Load Balancing > Virtual Servers, and then create a virtual server.
Click Add to create a virtual server.
In the Basic Settings pane, update the following details:
1. Probe Protocol –Select the protocol (HTTP or TCP) of the probe for external health check of the virtual server.
2. Probe Success Response Code –Enter the response string for a successful probe. This parameter is applicable only for the HTTP protocol.
  - Default Value: 200ok
  - Maximum Length: 63
3. Probe Port –Enter the port number for HTTP or TCP monitoring.
Click OK.

The official version of this content is in English. Some of the Cloud Software Group documentation content is machine translated for your convenience only. Cloud Software Group has no control over machine-translated content, which may contain errors, inaccuracies or unsuitable language. No warranty of any kind, either expressed or implied, is made as to the accuracy, reliability, suitability, or correctness of any translations made from the English original into any other language, or that your Cloud Software Group product or service conforms to any machine translated content, and any warranty provided under the applicable end user license agreement or terms of service, or any other agreement with Cloud Software Group, that the product or service conforms with any documentation shall not apply to the extent that such documentation has been machine translated. Cloud Software Group will not be held responsible for any damage or issues that may arise from using machine-translated content.

Was this helpful

Enable external health check for UDP and non-HTTP virtual servers

September 6, 2023

Contributed by:

C S

September 6, 2023

Contributed by:

C S

Enable external health check for UDP and non-HTTP virtual servers

To enable external health check for UDP and non-HTTP TCP virtual servers by using CLI

To enable external health check for UDP and non-HTTP TCP virtual servers by using GUI

In this article