Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[lvs\-users\]\s+The\s+effect\s+of\s+wlc\,\s+lblc\,\s+and\s+persistent\s*$/: 3 ]

Total 3 documents matching your query.

1. Re: [lvs-users] The effect of wlc, lblc, and persistent (score: 1)
Author: "Robinson, Eric" <eric.robinson@xxxxxxxxx>
Date: Wed, 6 Mar 2013 19:18:16 +0000
Thanks, Malcolm. We've been running an LVS load balancer since 2006 and we have approximately 1400 realserver connections behind it, and didn't know this. :-) -- Eric Robinson Disclaimer - March 6,
/html/lvs-users/2013-03/msg00013.html (10,522 bytes)

2. Re: [lvs-users] The effect of wlc, lblc, and persistent (score: 1)
Author: Malcolm Turnbull <malcolm@xxxxxxxxxxxxxxxx>
Date: Sat, 2 Mar 2013 09:22:27 +0000
Eric, LBLC & DH schedulers can only be used in a completely transparent forwarding LVS i.e. firewall mark matches the packets of ALL routed traffic and forwards it to a proxy/squid cache. This is bec
/html/lvs-users/2013-03/msg00002.html (13,766 bytes)

3. [lvs-users] The effect of wlc, lblc, and persistent (score: 1)
Author: "Robinson, Eric" <eric.robinson@xxxxxxxxx>
Date: Fri, 1 Mar 2013 16:34:46 +0000
Need some help understanding the effect of wlc, lblc, and persistent. In our environment, the following realserver configuration in ldirectord results in pretty even load balancing. virtual=192.168.5
/html/lvs-users/2013-03/msg00001.html (10,915 bytes)


This search system is powered by Namazu