I would recommend clearing the serverfarm statistics (clear serverfarm ) and then monitor (show serverfarm detail) the distribution of connections.You should be looking at "total
connections" column and not the "Current conns" column.
Round robin algorithm doesn't care about the current number of connections, it only takes into account the total number of connections sent. Current connections can be more on 1 server vs other just because of HTTP1.1 persistence (where multiple GETS are sent on a single TCP connection).
If you want to loadbalance on "current connection" basis then change the predictor to
On a lightly loaded ACE you may see this. The ACE has two network processors which work independently. Both implement the RR algorithm on the same servers in the serverfarm. Hence you may see what looks like an error in the distribution.
Over the long term, in the absence of stickiness then the load balance algorithms will even out. The key in my previous reply was that the NPs act independently. There is no way of forcing an exact 1-1 distribution. Whether you see 1-1 or 2-2 is a matter of chance - depending on how the NPs see the serverfarms and make their decisions.
Introduction This article will help you understand the steps on how to
download the UCS licenses from the Cisco Systems website and then
installing it on the UCS. The redacted (blue lines) just covers up
certain numbers for privacy please do not take them...
Introduction This article will help you understand and educate the
customer on how to clear their "expired licenses"
(license-graceperiod-expired) from their UCS-M. If a customer just
purchased a license and needs a step by step guide on how to download
Introduction Prepositioning is a powerful tools on the WAAS platform but
it is not always easy to figure out why your jobs are failing when
trying to retrieve the files.Here is a method that should help you to
figure out the reason why they are not succes...