I contact my router in 2 steps (first to another and then to my 837)
I lost my connection to the 1st router so I lost my connection to 837, but it is still active.
How can I kill the unused session?
Alex.
Alex.
clear session [session id]Quote:> I contact my router in 2 steps (first to another and then to my 837)
> I lost my connection to the 1st router so I lost my connection to 837,
> but it is still active.
> How can I kill the unused session?
> Alex.
router#who
Line User Host(s) Idle Location
* 1 vty 0 idle 00:00:00 10.43.1.39
2 vty 1 idle 00:00:03 10.10.51.91
Interface User Mode Idle Peer
Address
Find the line you want to kill (let's assume VTY 1) and enter:
router#cle line vty 1
or
router#cle line 2
If you don't have it setup already, you should consider adding an
exec-timeout to your VTY lines to clear idle sessions after x minutes.
To enable a 5 minute exec-timeout:
router(config-line)#exec-time 5 0
Adding a keepalive to should also clear up any hung sessions (with
varying degrees of success):
router(config)#service tcp-keepalives-in
Cheers,
Spencer Teran
1. PIX 6.3(5) kill ssh session?
Is there any possiblity to show/kill administrative sessions via ssh?
For telnet sessions, that isn't a problem:
----------
pixfirewall# who
0: 10.0.0.1
pixfirewall#
----------
Unfortunately, "who" does not show any users logged in via ssh, so I'm
not able to kill these sessions.
Martin
6. DKB MegaChip and A2K MB revs
7. SSH session
9. How to kill a RConsole session
10. Ascend killing TCP sessions
11. SSH sessions to W2K (was: Windows as a VT-xxx serial terminal server?)
12. Help: What's killing my telnet sessions?
13. Help! Ascend VPN kills telnet sessions