Forum Discussion
MR_RJ
Cirrus
CirrusIssue with SSH and RDP connections times out
Hi,
When we first installed our BIG-IP LTM we had issues that RDP sessions going through the LTM was disconnected, same thing with SSH session to the LTM CLI.
To solve this I cre...
MR_RJCirrus
Cirrushttp://devcentral.f5.com/Default.aspx?tabid=63&articleType=ArticleView&articleId=285
Suggests:
Idle Timeout
The explanation of the idle timeout is fairly intuitive. This setting controls the number of seconds the connection remains idle before the LTM closes it. For most applications, the default 300 seconds is more than enough, but for applications with long-lived connections like remote desktop protocol, the user may want to leave the desk and get a cup of coffee without getting dumped but the administrators don't want to enable keepalives. The option can be configured with a numeric setting in seconds, or can be set to indefinite, in which case the abandoned connections will sit idle until a reaper reclaims them or services are restarted. I try to isolate applications onto their own virtual servers so I can maximize the profile settings, but in the case where a wildcard virtual is utilized, the idle timeout can be set in an iRule with the IP::idle_timeout command:
when CLIENT_ACCEPTED {
switch [TCP::local_port] {
"22" {
IP::idle_timeout 600
}
"23" {
IP::idle_timeout 600
}
"3389" {
IP::idle_timeout 3600
}
default {
IP::idle_timeout 120
}
}
....Maybe this is _the_ way to go. Dunno if during the 3600 seconds if the RDP keep-alive willl keep this session active so it wont disconnect after 60min. We'll see!
Any other ideas?
//Robert
