Forum Discussion
NimbostratusRDP Sessions exceeding limit through F5.
RDP session requires connection persistence unless the RDP servers are clustered and mirror session information to one-another. Depending on the exact setup, BigIP may have initiated 1 connection to each server while just one connection carries meaningful RDP session information to a single server. Can you check connection tables or do a measured test during off-peak hours to see how many pool member counters increase when you initiate a RDP session?
For fix. Give a try with following settings and see if the problem persist. Source IP persistence profile (Virtual Server setting), Least Sessions load-balancing algorithm (Pool setting). Source IP persistence can probably be replaced with something better but for initial test it's good enough. As you apply changes, old connections should be killed to see immediate effect, otherwise they will continue to function with previous configuration until timed out. To kill all connections to a particular Virtual Server, use
tmsh delete /sys connection cs-server-addr VS.IP.AD.DR cs-server-port 3389
NacreousRDP session requires connection persistence unless the RDP servers are clustered and mirror session information to one-another. Depending on the exact setup, BigIP may have initiated 1 connection to each server while just one connection carries meaningful RDP session information to a single server. Can you check connection tables or do a measured test during off-peak hours to see how many pool member counters increase when you initiate a RDP session?
For fix. Give a try with following settings and see if the problem persist. Source IP persistence profile (Virtual Server setting), Least Sessions load-balancing algorithm (Pool setting). Source IP persistence can probably be replaced with something better but for initial test it's good enough. As you apply changes, old connections should be killed to see immediate effect, otherwise they will continue to function with previous configuration until timed out. To kill all connections to a particular Virtual Server, use
tmsh delete /sys connection cs-server-addr VS.IP.AD.DR cs-server-port 3389
NimbostratusHi Rapp first of all Happy new your to you !!!
Thanks for all explanation,Agreed on persistence profile configuration and least session load-balancing method configuration suggestion.
And answer to your first question i already did close monitoring and seen that Round-Robin working good for initial few connections but after connections start increasing rapidly its seems not working as expected and few servers not seems accepting connections.
