<< Prev Question Next Question >>
Question 48/52
An application is being load balanced through the LTM device using the configuration displayed below.
The network has been re-engineered to NAT all client connection. As a result, all client connections are hitting the same pool member.
Which changes should the LTM Specialist make in order to restore load balancing functionality wile maintaining session persistence?
The network has been re-engineered to NAT all client connection. As a result, all client connections are hitting the same pool member.
Which changes should the LTM Specialist make in order to restore load balancing functionality wile maintaining session persistence?
Recent Comments (The most recent comments are at the top.)
The attached image configuration displays using the source address as a persistence mode and as per the question - the network has been re-engineered to NAT all client connections. As a result, all the connections are being directed to the same pool member which received the first request from f5 big-ip client side. When the cookie persistence is used then based on the user cookies, the request will be directed to the new pool member based on the configured load balancing algorithm, and has no effect of NAT configuration.