ADC

TCP-based application monitoring

May 2, 2023

Contributed by:

S C

The NetScaler appliance has two built-in monitors that monitor TCP-based applications: tcp-default and ping-default. When you create a service, the appropriate default monitor is bound to it automatically, so that the service can be used immediately if it is UP. The tcp-default monitor is bound to all TCP services. The ping-default monitor is bound to all non-TCP services.

You can’t delete or modify default monitors. When you bind any other monitor to a TCP service, the default monitor is unbound from the service. The following table lists the monitor types, and the parameters and monitoring processes associated with each type.

Monitor type	Specific parameters	Process
tcp	Not applicable	The NetScaler appliance establishes a 3-way handshake with the monitor destination, and then closes the connection. If the appliance observes TCP traffic to the destination, it does not send TCP monitoring requests. This occurs if LRTM is disabled. By default, LRTM is disabled on this monitor.
http	httprequest [“HEAD /”] - HTTP request that is sent to the service. respcode [200] - A set of HTTP response codes are expected from the service.	The NetScaler appliance establishes a 3-way handshake with the monitor destination. After the connection is established, the appliance sends HTTP requests, and then compares the response code with the configured set of response codes.
tcp-ecv	send [””] - is the data that is sent to the service. The maximum permissible length of the string is 512 bytes. recv [””] - expected response from the service. The maximum permissible length of the string is 128 bytes. The last character is NULL termination.	The NetScaler appliance establishes a 3-way handshake with the monitor destination. When the connection is established, the appliance uses the send parameter to send specific data to the service and expects a specific response through the receive parameter. Different servers send different sizes of segments. However, the pattern must be within 16 TCP segments.
http-ecv	send [””] - HTTP data that is sent to the service; recv [””] - the expected HTTP response data from the service	The NetScaler appliance establishes a 3-way handshake with the monitor destination. When the connection is established, the appliance uses the send parameter to send the HTTP data to the service and expects the HTTP response that the receive parameter specifies. (HTTP body part without including HTTP headers). Empty response data matches any response. Expected data might be anywhere in the first 24 K bytes of the HTTP body of the response.
ping	Not Applicable	The NetScaler appliance sends an ICMP echo request to the destination of the monitor and expects an ICMP echo response.

To configure built-in monitors for TCP-based applications, see Configuring Monitors in a Load Balancing Setup.

To configure TCP-based monitors by using CLI

Type the following command:

add lb monitor <monitorName> <type> -respCode <int[-int]> -httpRequest <string> -resptimeout <integer> [<units>] -retries <integer> -downTime <integer> [<units>] -action <action>
<!--NeedCopy-->

Example for TCP monitor type:

add lb monitor Exch2010-RPC-AddressBook TCP -LRTM ENABLED -interval 10 -resptimeout 5 -destPort 59601
<!--NeedCopy-->

Example for HTTP monitor type:

add lb monitor Mon_S4B_FE_2 HTTP -respCode 200 -httpRequest "GET /Autodiscover/XFrame/XFrame.html" -LRTM ENABLED -retries 10 -secure YES
<!--NeedCopy-->

Example for HTTP-ECV monitor type:

add lb monitor STM_EXC2016_SSLBridge_MON HTTP-ECV -send "GET /owa/healthcheck.htm" -recv "200 OK" -LRTM ENABLED -destPort 443 -secure YES
<!--NeedCopy-->

Example for PING monitor type:

add lb monitor lbmon-localhost-ping PING -LRTM DISABLED -destIP 127.0.0.1
<!--NeedCopy-->

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

TCP-based application monitoring

May 2, 2023

Contributed by:

S C

May 2, 2023

Contributed by:

S C

TCP-based application monitoring

To configure TCP-based monitors by using CLI

In this article