Note: Binary Data health checks use HTTP (not HTTPS).

When Binary Data is selected as the health check method, some other fields are available, as described below.

For examples on how to create custom, protocol-specific, binary health checks, refer to the Custom TCP Service Health Checks section.

Data to Send

Specify a hexadecimal string to send to the Real Server. This hexadecimal string must contain an even number of characters. For example:

  • 12d is not valid because it has an odd number of characters
  • 12de is valid and will result in 16bits of data being sent to the Real Server
  • 012d is valid and results in 16 bits of data being sent to the Real Server
  • 00012d is valid and results in 24 bits of information

Reply Pattern

Specify the hexadecimal string that the LoadMaster will attempt to locate in the response data. The response is treated as a sequence of bytes; there is no header or body – there is just a sequence of bytes. This checker could be used to health check an Extended Binary Coded Decimal Interchange Code (EBCDIC) data stream.

If the LoadMaster finds the pattern in the response, the Real Server is considered up. If the string is not found, the Real Server is marked as down.

Note: This hexadecimal string must contain an even number of characters.

Find Match Within

When a response is returned, the LoadMaster will search for the Reply Pattern in the response. The LoadMaster will search up to the number of bytes specified in this field for a match.

Setting this to 0 means that the search is not limited. Data is read from the Real Server until a match is found. The first 8 KB is read from the Real Server.

Setting the value to more than the length of the reply string means that the check will act as if the value has been set to 0, i.e. all packets (up to 8 KB) are searched.