BIG-IP does not see string

Hi Klaus,

 

 

SOL3451 describes a limit of 5120 bytes that BIG-IP will parse to find the receive string. I don't think this is configurable. The simplest fix might be to rework the page you're monitoring to ensure the string is in the first 5120 bytes. If that's not possible, you can use an EAV to get around the issue.

 

 

Aaron

 

 

Click here

 

 

 

An HTTP health monitor reads up to 5,120 bytes into HTTP data. If the monitor cannot find a match to the configured search string within the first 5,120 bytes, the BIG-IP LTM marks the node as DOWN.

 

 

Important: The standard HTTP health monitor does not send a well-formed HTTP GET statement that includes HTTP headers. Therefore, some servers may refuse to respond or not return response information as expected in the response HTTP headers. For information, refer to SOL3224: HTTP health checks may fail even though the node is responding correctly.

 

 

If you require a health monitor that searches for a string deeper than 5,120 bytes into an HTTP response, you must create an External Application Verification (EAV) health monitor. The amount of data an EAV health monitor can read is determined by the program that the EAV uses (such as cURL) to read the data.

 

 

For specific instructions about configuring an EAV health monitor, refer to the BIG-IP Reference Guide.