NimbostratusLTM load balancing least connections - definitively how does this work ?
Guys Looking for a definitive answer on a least connections load balancing node / member
Least connections member.
Would I be correcting in saying least connections member would look only at connections from the LTM to the pool member(s) only in that pool i.e. that should the node also be a member in a different pool running a second application that these additional connections would be load balanced in isolation of the first app.? i.e. that traffic to servers running multiple applications on multiple ports would have traffic directed to them on a per application basis and not necessarily on a per connections to the server basis.
Least connections node.
Would I be correct to say this method would load balance based on total TCP-IP (or layer 2) sessions / connections held to the node from the LTM? i.e. that traffic is absolutely load balanced on LTM-server connections and not necessarily per application?
Yes.
Least Connections Node evaluates that IP Address, across all pools that use it on that route-domain.
Least Connections Member evaluates that IP + Port combination defined in the Pool only, and is independent on other connections to that node in other pools.
