Pool load balancing to one node
Hi guys, So we have an HTTP application behind our 11.5.1 BIGIPs, which in turn is behind an ISAPI filter that forwards http traffic to the Bigips. (temporary) What we saw is that 24 hours after putting our BIGIPs inbetween, all users were on one node and this was severely stressing it. We saw this in applications logs aswell as bigip pool statistics. I had to put the node offline to force a rebalance of the visitors due to the cookie persistence. Now 3 days later and we had the same problem. Again, force node offline, tried round robin load balancing & removed the fallback persistence 'source_addr' to be sure. (Am I correct to say fallback persistence shouldn't be used when using HTTP profiles?) So I have the following pool configuration; ltm pool /ITSS/live-hwo-pool { load-balancing-mode least-connections-member members { server1.company.com:commplex-link { address 2.170.0.11 session monitor-enabled state up } server2.company.com:commplex-link { address 2.170.0.12 session monitor-enabled state up } } monitor tcp and /ITSS/fw-prd-mon partition ITSS } And virtual; ltm virtual /ITSS/live-hwo-vs { destination /ITSS/2.170.0.100:https ip-protocol tcp mask 255.255.255.255 partition ITSS persist { cookie { default yes } } policies { /ITSS/asm_auto_l7_policy__live-hwo-vs } pool /ITSS/live-hwo-pool profiles { /ITSS/live-hwo-ssl { context clientside } http { } httpcompression { } no-reject-dos { } oneconnect { } tcp { context clientside } tcp-lan-optimized { context serverside } websecurity { } } rules { maintenance-unavailable-rule secure-cookie-rule /ITSS/url-rewrite /ITSS/show-error-page-rule } security-log-profiles { "Log illegal request and response" } source 0.0.0.0/0 source-address-translation { type automap } vlans { EXT-WIN-11 } vlans-enabled vs-index 507 } It hasn't happened again, but I would love some suggestions or feedback on why this is happening. Thanks!