I believe your Cisco SE forwarded the same question to me.

Here is the answer I gave him :

with sticky source ip, this output is most probably normal.

Let's say you have 4 clients, A,B,C,D.

They all open 2 connections to the VIP.

You will have on server 1 - AACC and on server 2 BBDD.

Now, let's say B and D decides to close the connections while C stays connected and A decides to open 2 more connections.

Because of stickyness the new connections from A will be sent to server1.

You end up with server1: AAAACC and server2: - no connections.

This is even worst if a server goes down.

Assume only server1 is up.

All clients open a connection. Because server2 is down, all the connection are sent to server1.

Because of stickyness, when server2 comes back up, all connections from A,B,C,D are still forwarded to server1.

I see your servers had a lot of transitions.

So you might have a sticky table that forwards most of the traffic to server1.

You should configure a sticky timeout, so that the sticky table can be refreshed.

Here is the command that you need :

CSS11503-2(config-owner-content[gdufour-WWW])# sticky-inact-timeout ?

Integer value(Range: 0-65535)

CSS11503-2(config-owner-content[gdufour-WWW])# sticky-inact-timeout

And clear the sticky table manually if you want to start fresh immediately.

Gilles.