A BIG-IP Administrator needs to determine why only one pool member is showing connections from the virtual server, resulting in uneven load…

Uneven load balancing where one member receives all traffic can be caused by two primary factors. First, if health monitors have marked all other pool members as 'down', the BIG-IP system will direct all new connections to the single remaining 'up' member. Second, a persistence profile can cause this behavior. If a single client establishes a persistent session and then generates a high volume of traffic, all of that traffic will be "stuck" to the same pool member, creating an imbalance, even if other members are available.

A. A virtual server marked down would not process any traffic, so no connections would be sent to any pool member.

D. If all pool members are marked down, the virtual server would also be marked down (by default) and no traffic would be forwarded.

1. F5 Networks (2021). BIG-IP Local Traffic Manager: Concepts, K00451023, Chapter 4: Pools, Section: 'Understanding pool, pool member, and node status'.

2. F5 Networks (2021). BIG-IP Local Traffic Manager: Concepts, K00451023, Chapter 6: Persistence, Section: 'Understanding persistence'.

3. F5 Networks (2021). BIG-IP Local Traffic Manager: Monitors, K51452193, Chapter 1: Introducing BIG-IP Monitors, Section: 'About health and performance monitors'.