Is it necessary to put the expectet content coming back from the web server in reply to a content based HTTP health check done by the ServerIron into the first packet? Or is it OK to have the expectet content in one of the following data packets?

It does not really matter. The expected content might be in the first reply packet but it is as well OK if it is part of one of the following data packets. I would suggest to put the content as close to the beginning of the reply as possible and I would suggest as well to keep the replies as small as possible to reduce the amount of data the ServerIron needs to parse to find the expected content. Less health check traffic and less work to parse the health chek replies implies less MP CPU utilisation which is good.

There is not any maximum size - keep in mind that it is good to reduce the HC traffic to a minimum. It is as well required that the real server is able to deliver the content needed to the ServerIron during the configured health check interval. The ServerIron is going to start a new health check as soon as the next interval starts. A health check which is running at this time (still sending data from the real server to the ServerIron) is getting declared as not successful.

Join the Community

Please note: Certain product lines referenced on this website have been acquired by third party buyers and may no longer be supported, offered or sold by Brocade. These product lines include, but are not limited to, the Virtual Router (vRouter), Virtual Application Delivery Controller (vADC), the Virtual Evolved Packet Core (vEPC) and the Software Defined Networking (SDN) Controller. Any mention of these product lines, including associated services and support on this site, as it relates to Brocade should now be considered historical reference only. Ongoing use of such products may be subject to terms and conditions of the buyer.

Some, but not all the content on this site is provided, reviewed, approved or endorsed by Brocade but in any case, is provided solely as a convenience of our customers. All postings and use of the content on this site are subject to the BROCADE WEBSITE USE TERMS AND CONDITIONS. BROCADE ASSUMES NO LIABILITY WHATSOEVER, MAKES NO REPRESENTATION AND DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO THE CONTENT PROVIDED HEREIN, INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, CORRECTNESS, APPROPRIATENESS OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED. THIRD PARTIES USE THIS CONTENT AT THEIR OWN RISK. Content on this site may contain or be subject to specific guidelines or limitation on use. Third parties using this content agree to abide by any limitation or guidelines and to comply with the BROCADE WEBSITE USE TERMS AND CONDITIONS. Brocade may make changes to this content, to specifications, or product design or descriptions at any time, or may remove content at its sole discretion without notice.