Forum Discussion
James_125728
Nimbostratus
NimbostratusRDS Farm not Balancing
Here's my setup:
- 1 server hosting RDS Gateway & Web Access roles
- 1 connection broker
- 2 RDS Sessions hosts in a farm
- (All are Windows Server 2008 R2)
I have the Session Hosts load balanced via my LTM as described in the RDS Deployment Guide. The Gateway/Web Access server and the Connection Broker are just single servers and are not setup in the F5 at all.
I have a RemoteApp published to the Web Access server, and it works just fine... However, the load is not being distributed. Right now I have 20 sessions on Session Host 2, and only two on Session Host 1. Of those, 11 are disconnected but still logged in, and 9 are actually active (all on Node 2)
If I login to the F5 and look at the statistics for the Virtual Server, it says there is currently only 1 connection. I suspect this is part of the problem, since the pool is set to load balance via "Least Connections (member)"
Not exactly related, but it also appears to not be creating persistence records, (The virtual server is set to use MSRDP persistence, but none show up on the Statistics report.)
Any ideas?
- This may be a bug. Can you run this command from tmsh and then see if you get persistence records:
modify ltm persistence msrdp RDP-SessionHost-persist has-session-dir yes 
James_125728Still don't see persistence records being created. I've even tried using the default "msrdp" persistence profile instead of my RDP-SessionHost-persist profile.
I tried setting source_addr as my fallback persistence, and I do see that it falls through and creates a source address persistence record.- I recommend opening a case with F5 support on this one. Puzzled as to why we're not creating a record for the token.