Forum Discussion
Akhil_128431
Nimbostratus
NimbostratusInactivity-timeout for tmsh connection
I had set the inactivity-timeout as 30 mins on my LTM (set months before). The tmsh list sys sshd inactivity-timeout returns me the following result.
ssh sshd {
inactivity-timeout 1800
}
...
Naresh_173597Nimbostratus
NimbostratusShaggy,
Thanks for the reply, but in boxes of tmos version 10.x we don't find idle-timeout util.
Here are some queries.
1)Also is it mandatory to set these options to kick off idle sessions. Ain't those taken care by f5 itself without any manual configuration.
2) If am setting the time-out today will it kill the older sessions as well.
3) Is it advisable to clean the idle sessions with external scripts which looks some thing like this,
netstat -anp | grep | awk '{print $7}' | cut -d \/ -f1 | grep -oE "[[:digit:]]{1,}" | xargs kill
shaggyNimbostratus
Nimbostratus1) If you want session timeout, you should set these values. As far as I know, F5 doesn't have a default CLI/SSH/TMSH/bigpipe timeout.
2) I'm not sure if it will kill the older sessions as I expect the timeout applies to new sessions only. If they remain after making the change, you can use "ps | grep sshd | grep (user-name)" and "kill (pid)" to clear the old sessions
3) This isn't necessary if the timeouts are set and function as expected
3a) If this is an automated process/device logging into the F5, can it be configured to send the appropriate quit/exit commands to properly terminate the session when completed?
