一种F5中不向所有成员分发流量的最小连接负载均衡方法

Question

我是负载均衡器上的负载分布故障排除新手，需要您的帮助来解决一个问题。池中有11个成员，但我看到请求一次只有2-3个。当这些服务器由于负载而耗尽时，我看到它们的监视器关闭，请求开始发送到其他2-3个成员。我检查了持久性没有打开，其他成员也是健康的。有人能指导我下一步要检查什么来解决这个问题吗？

下面是池的负载均衡器的一些设置。

allow-nat yes
allow-snat yes
app-service none
autoscale-group-id none
description "Flux Pool for p6_pool"
gateway-failsafe-device none
ignore-persisted-weight disabled
ip-tos-to-client pass-through
ip-tos-to-server pass-through
link-qos-to-client pass-through
link-qos-to-server pass-through
load-balancing-mode least-connections-member
metadata none
min-active-members 0
min-up-members 0
min-up-members-action failover
min-up-members-checking disabled
monitor tcp
partition Common
profiles none
queue-depth-limit 0
queue-on-connection-limit disabled
queue-time-limit 0
reselect-tries 0
service-down-action none
slow-ramp-time 10

清理来自池和虚拟配置的输出

uname@(ab-f5-2)(cfg-sync In Sync)(Active)(/Common)(tmos)# list ltm virtual vs_virtual_name_int_https
ltm virtual vs_virtual_name_int_https {
    destination 172.ip_address:443
    ip-protocol tcp
    mask 255.255.255.255
    pool p_poolName_8443
    profiles {
        http { }
        serverssl-insecure-compatible {
            context serverside
        }
        star.mc-int.vals19 {
            context clientside
        }
        tcp-lan-optimized {
            context serverside
        }
        ab-tcp-wan-optimized {
            context clientside
        }
    }
    rules {
        CIP
    }
    source 0.0.0.0/0
    source-address-translation {
        pool Int-SNAT
        type snat
    }
    translate-address enabled
    translate-port enabled
    vs-index 1999
}

列出ltm池pool_name输出

ltm pool p_poolName_port {
    description "Flux Pool for p_poolName_port"
    load-balancing-mode least-connections-member
    members {
        172.ip.11:port {
            address 172.ip.11
            session monitor-enabled
            state up
        }
        172.ip.2:port {
            address 172.ip.2
            session monitor-enabled
            state up
        }
        172.ip.1:port {
            address 172.ip.1
            session monitor-enabled
            state up
        }
        172.ip.64:port {
            address 172.ip.64
            session monitor-enabled
            state up
        }
        172.ip.68:port {
            address 172.ip.68
            session monitor-enabled
            state up
        }
        172.ip.74:port {
            address 172.ip.74
            session monitor-enabled
            state up
        }
        172.ip.180:port {
            address 172.ip.180
            session monitor-enabled
            state up
        }
        172.ip.188:port {
            address 172.ip.188
            session monitor-enabled
            state up
   }
        172.ip.5:port {
            address 172.ip.5
            session monitor-enabled
            state up
        }
        172.ip.6:port {
            address 172.ip.6
            session monitor-enabled
            state up
        }
        172.ip.7:port {
            address 172.ip.7
            session monitor-enabled
            state up
        }
    }
    monitor tcp
}

ltm规则CIP输出

ltm rule CIP {
    when HTTP_REQUEST {

HTTP::header insert CIP [IP::client_addr]
HTTP::header insert x-CIP [IP::client_addr]

}
}

Answer 1

后来发现，OneConnect配置文件是打开的，并且大多数时间相同的连接都在重复使用。