Radware Alteon Application Manual page 496

Alteon Application Switch Operating System Application Guide
Health Checking
ASCII-Based Health Check
The following is the general format for ASCII-based health-check:
open application_port, protocol-name #(for example: 80, TCP)
send request 1 (ascii string)
expect response 1
send request 2
expect response 2
send request 3
expect response 3
close #(used in TCP-based health checks only)
Binary-Based Health Check
The following is the general format for binary-based health check scripts. Specify the binary content
in hexadecimal format:
open application_port, protocol-name #(for example: 80, TCP)
bsend request 1 (binary pattern in hex format)
nsend request 1-continued
bexpect response 1
nexpect response 1-continued
expect response 3
offset offset count
depth number of packets from offset to count
close #(used in TCP-based health checks only)
A Binary-Based TCP Health Check
The bsend and bexpect commands are used to specify binary content. The offset and depth
commands are used to specify where in the packet to start looking for the binary content. For
example, if your script is configured to look for an HTTP 200 (ok) response, this typically appears
starting from the 7th byte in the packet, so an offset value of 7 can be specified:
open "80,tcp"
bsend " <binary content for request 1> "
nsend " <continuing binary content for request 1> "
bexpect " <binary content for response 1> "
nexpect " <binary content> "
offset " <byte count from the start of the IP header> "
depth "10"
wait "100"
close #(used in TCP-based health checks only)
Notes UDP-Based Health Checks
• UDP-based health check scripts can use either ASCII strings or binary patterns.
• The close command is not required for a health check on UDP protocol.
Notes TCP-based Health Checks for HTTP Protocol
• If you are performing HTTP 1.1 pipelining, you need to individually open and close each
response in the script.
496
Document ID: RDWR-ALOS-V2900_AG1302