No traffic to Pool Members , predictive (member).

A few observations:

1. A hash persistence profile, like the universal persistence profile, is generally reliant on an iRule to manage the payload content used for persistence. Without an iRule there's nothing really to persist on. I couldn't say for certain, but the presence of this profile without an iRule may be causing the uneven loading. If this VIP is used with standard browser clients, your best bet and arguably the most reliable option is to use cookie insert persistence.

    

2. If all members in a pool have the same priority group activation value, then priority group adds no value.

    

3. The predictive load balancing algorithm, while very powerful, will consume additional system resources which is usually unwarranted for most applications that will work splendidly with the least connections method.