Technical Bulletin #4
Announcement Date:
May 12, 2009
Exclusions:
None
Effective Date:
Immediate
Expiration Date:
None
Products Covered by this bulletin:
Products Covered by this Announcement:
ServerIron 4G Series
ServerIron GT C Series
ServerIron GT E Series
ServerIron 350 & 350-PLUS
ServerIron 350 & 350-PLUS
ServerIron 450 & 450-PLUS
Executive Summary:
Configuring Binary Health checks
Discussion:
ServerIron can perform any Health Checks if you specify data in carray format.
Considerations :
1. You can specify binary health check only under server real statement, not under
healthck command.
2. You can define binary health check only for the ports that are not pre-defined by
ServerIron. Example config is doing rtsp slb. Since l7 rstp health check is already
supported by ServerIron, you needed to change the port number from 554 to 5554 to do
binary health check.
3. Maximam number of letters for carray is 224. This is not enough for typical health
check.
4. Example config will perform health checking by sending "OPTIONS
rtsp://10.176.0.81:5554 RTSP/1.0" for real server and if ServerIron receives "RSTP/1.0
200 OK" data from real server, ServerIron regards real server as ACTIVE. When ASCII
Brocade Communications Systems, Inc.
Page 1
22/4/2009
No statements made by Brocade Communications Systems, Inc. (“Brocade”) in this technical bulletin, or information contained herein, may
be deemed to constitute either an amendment of an existing agreement or an implied new commitment, promise or legal obligation by
foundry to develop or deliver any specific product, feature or functionality.
data "OPTIONS rtsp://10.176.0.81:5554 RTSP/1.0" is translated into CARRAY data,
total num of letter is 222.
5. The number of 224 comes from "content-check" which will send ASCII data for real
servers in ascii. However, when we think of the nature of data difference between ACSII
and CARRAY(Binary), the total number of letters for "content-check-carray" should be
more than 224. I think 1024byte would be fine for most applications.
Example configuration:
server real evo7 10.176.0.81
port 5554
port 5554 content-check-carray m1
port 5554 content-check-carray send
"0x4f,0x50,0x54,0x49,0x4f,0x4e,0x53,0x20,0x72,0x74,0x73,0x70,0x3a,0x2f,0x2f,0x31,0x30,0x2e,0x31,0x37,0x36,0x
2e,0x30,0x2e,0x38,0x31,0x3a,0x35,0x35,0x35,0x34,0x20,0x52,0x54,0x53,0x50,0x2f,0x31,0x2e,0x30,0x0d,0x0a,0x0d,
0x0a"
port 5554 keepalive
server virtual vip1 10.176.0.220
port 5554
bind rtsp evo7 5554
http match-list m1
default down
up simple 0x52,0x54,0x53,0x50,0x2f,0x31,0x2e,0x30,0x20,0x32,0x30,0x30,0x20,0x4f,0x4b,0x0d,0x0a
Recommended Field & Partner Action:
Reference:
binaryHC.pcap
Author:
Kenichi Kono, Layer 4-7 Systems Engineer
Brocade Communications Systems, Inc.
Page 2
22/4/2009
No statements made by Brocade Communications Systems, Inc. (“Brocade”) in this technical bulletin, or information contained herein, may
be deemed to constitute either an amendment of an existing agreement or an implied new commitment, promise or legal obligation by
foundry to develop or deliver any specific product, feature or functionality.