Session Broker and F5 Weird stuff

Hi boudjel,

did you configure it according to the deployment guide (including least conn and msrdp based persistence)?

You can run a trace on the F5 to filter the traffic from the client and look after the RDP header values. If the first 8 characters do not vary, it could happen all requests persist to the same pool member depending on the very first selection.

tcpdump -i 0.0:nnnp -s 0 -w /var/tmp/capture_ts001.cap host   

This can be validated as well by monitoring the persistence table.

watch -d tmsh show ltm persist persist-records mode msrdp   

There is a kown issue in case of using routing domains. Please see SOL15695 for details.

Another possible reason could be the direct path between the client and the real servers. As the session broker indicates the real server IP (as far as I understand) the client connects directy.

The virtual server is bypassed and does not increase the concurrent connection. So least conn load balancing method will pick the next best member in pool with least number of current connections (please see the pool statistics).

It would be great to keep us posted on your findings.

Thanks, Stephan

PS: There is another related open thread on this subject here on DC.