-- Exhibit -

-- Exhibit -Refer to the exhibit. Users report that a web application works incorrectly. Sometimes contextual data displayed on
the web pages is accurate; other times it is inaccurate.
The LTM administrator looks at the connection table with a filter on one of the client IP addresses currently connected using the command "tmsh show sys connection cs-client-addr 10.0.20.1"
with the following results:
10.0.20.1:60048 10.0.20.88:80 10.0.20.1:60048 172.16.20.1:80 tcp 3 (tmm: 0) 10.0.20.1:60050 10.0.20.88:80 10.0.20.1:60050 172.16.20.3:80 tcp 3 (tmm: 0) 10.0.20.1:60047 10.0.20.88:80 10.0.20.1:60047 172.16.20.2:80 tcp 3 (tmm: 0) 10.0.20.1:60049 10.0.20.88:80 10.0.20.1:60049 172.16.20.1:80 tcp 3 (tmm: 0)
What is the solution to the problem?
Recent Comments (The most recent comments are at the top.)
The issue is inconsistent application behavior — sometimes contextual data is correct, sometimes not. The tmsh show sys connection output shows that one client IP (10.0.20.1) has connections to multiple backend servers (172.16.20.1, .2, .3).
This indicates that the client's session is being load-balanced to different backend servers, likely because there is no session persistence configured.
Thus, the option D is the correct one.