Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Local Director Weighted Balancing


I have LD with sticky cookie-passive and weighted load balancing over 3 servers.

It seems the weights of the 3 server are not respected.

Here are some displays :

LD_Prod# sh sticky

Virtual Machine(s) Sticky

virtualprod:80:0:tcp 240 cookie-passive tolsessionid

LD_Prod# sh weight

Real Machine(s) Weight Timeout

bfpctol3:80:0:tcp 4 never

bfpctol1:80:0:tcp 2 never

bfpctol2:80:0:tcp 2 never

LD_Prod# sh statistics

Real Machine(s) Bytes Packets Connections

bfpctol3:80:0:tcp 530221148 1673183 46326

bfpctol1:80:0:tcp 651629640 2068285 57703

bfpctol2:80:0:tcp 283775703 918391 26235

Note that bfpctol3 has a weight of 4 (doubles the other two server weights), but the number of connections does not shows this situation.

The three servers had been always up since last clear counters command.

Any idea ?

Thanks in advance.


Re: Local Director Weighted Balancing

Since there has been no response to your post, it appears to be either too complex or too rare an issue for other forum members to assist you. If you don't get a suitable response to your post, you may wish to review our resources at the online Technical Assistance Center ( or speak with a TAC engineer. You can open a TAC case online at

If anyone else in the forum has some advice, please reply to this thread.

Thank you for posting.

New Member

Re: Local Director Weighted Balancing

Keep in mind the weighted predictor makes its decision on current, instantaneous incoming traffic. The more traffic you send it the, better the results. Also, I would use the show real command to see the predictor at work. The show real displays the instantaneous connections to each server. The show statistics is the over all number of connections each has been given.

You might also want to consider using the "loaded" predictor. The loaded predictor assigns a weighted portion of connections to a server before moving to the next.

Link to predictor definition:

I hope this helps!