F5 HTTP Load Balancing practices

F5 HTTP Load Balancing practices

1, network topology

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/83/F7/wKioL1eCJPmTAvRRAAA9eiuybHM857.png "title=" 1.png " alt= "Wkiol1ecjpmtavrraaa9eiuybhm857.png"/>

2, configure the address pool node first.

650) this.width=650; "Src=" Http://s3.51cto.com/wyfs02/M01/83/F9/wKiom1eCJQjwiROaAAB08FydnT4174.png-wh_500x0-wm_3 -wmp_4-s_815417488.png "title=" 2.png "alt=" Wkiom1ecjqjwiroaaab08fydnt4174.png-wh_50 "/>

3. Configure the node pool.

650) this.width=650; "Src=" Http://s2.51cto.com/wyfs02/M02/83/F7/wKioL1eCJRPD9lr4AADQWA-0jyU470.png-wh_500x0-wm_3 -wmp_4-s_3247689843.png "title=" 3.png "alt=" Wkiol1ecjrpd9lr4aadqwa-0jyu470.png-wh_50 "/>

3, add virtual service policy

650) this.width=650; "src=" Http://s2.51cto.com/wyfs02/M02/83/F9/wKiom1eCJSriyZLGAADQWA-0jyU136.png "style=" float: none; "title=" 3.png "alt=" Wkiom1ecjsriyzlgaadqwa-0jyu136.png "/>

650) this.width=650; "src=" Http://s1.51cto.com/wyfs02/M00/83/F9/wKiom1eCJSuhxuJXAABg52dUgDE111.png "style=" float: none; "title=" 4.png "alt=" Wkiom1ecjsuhxujxaabg52dugde111.png "/>

650) this.width=650; "src=" Http://s1.51cto.com/wyfs02/M00/83/F7/wKioL1eCJSugAb1PAADf3v1XS6E748.png "style=" float: none; "title=" 5.png "alt=" Wkiol1ecjsugab1paadf3v1xs6e748.png "/>

4, the client uses LoadRunner to hit the stream test, in the F5 view Real-time connection number, the connection number is about

650) this.width=650; "Src=" Http://s4.51cto.com/wyfs02/M00/83/F9/wKiom1eCJTqDsC22AABfKR6l5YI395.png-wh_500x0-wm_3 -wmp_4-s_4167787041.png "title=" 7.png "alt=" Wkiom1ecjtqdsc22aabfkr6l5yi395.png-wh_50 "/>

Summary: This is the simplesthttpload configuration. Note that according to the experimental topology, we have to do the sourceNatstrategy, why? The client is on the same network segment as the server and is only connected via a switch, and the client accessesVip, the purposeIpto be10.23.22.205, the sourceIpto be10.23.22.1. AfterF5after the load, if you do notNataddress translation, sourceIpstill for10.23.22.1, the purposeIpto be10.23.58.4. After the server receives the message to reply, namely the reverse message sourceIpto be10.23.58.4, the purposeIpto be10.23.22.1, so that the reverse message is sent directly through the switch to the client, that is, the reverse message does not go throughF5The load device can cause access to the system, and the client is the first to access the10.23.22.205, the last reverse message becomes the source is10.23.58.4, the client is definitely not recognized.

This article is from the "Ding classmate 1990" blog, please be sure to keep this source http://dingtongxue1990.blog.51cto.com/4959501/1817094

F5 HTTP Load Balancing practices