Load Balancing to Only One Pool Member

Nikhil here are the answers to your questions. Cleared all cookies & cache on the browser by any chance? Yes. used a different browser? Yes. What model is the Big-ip? CMP enabled? (this can have an affect on LB's decisions) This is a virtual edition running 11.4.1HF7. CMP is enabled on this virtual disable or force offline pool member 5 and what happens? I have not been given the OK to do this yet.

"show ltm persistence persist-records" - consistently shows 5 in the table? Tried using a different persistence profile? (hash?) Any connection limits at the node or pool member level? what LB algo are you using? (least sessions works best with persistence)

"show ltm persistence persist-records" - consistently shows 5 in the table? Yes. Tried using a different persistence profile? (hash?) TBD Any connection limits at the node or pool member level? Not that I am aware of. None configured in any profiles. what LB algo are you using? (least sessions works best with persistence) Least Connections (member). There are few, if any, connections left as the activity has all but ceased for the day. I will attempt using cookie hash persistence tomorrow as well as changing the lb algo.

Keep us posted.

Using cookie hash persistence and least sessions did not result in any change. We were also able to create a duplicate vip/pool combo to do some additional side-by-side testing since this is not production. This is set with source-address persistence and least-connections (member) LBing. Here are the persistence records: source-address 10.12.2.1 10.10.1.2:80 10.1.1.4:80 (tmm: 0) source-address 10.12.2.3 10.10.1.2:80 10.1.1.4:80 (tmm: 0)

I have forcefully removed the persistence table records for this virtual. When they are recreated they are exactly the same. Does this indicate something is not working or do I have something configured incorrectly?

Since this is not production, can you remove node 10.1.1.4 and test again?

I actually was able to get source address persistence working. First I had to set it to no persistence, manually clear the persistence table, and then enable source persistence. Now source address persistence works. This is not a desired state. We want to use cookie persistence, but as a test at least I was able to validate that one form of persistence will work correctly.

OK thats a good start. re-enable with just cookie persistence and let us know.

I changed the persistence on this duplicate virtual back to cookie and it appears to be working. I will attempt this on the other virtual and report back.