VTY "ghost sessions"

Unanswered Question
Feb 13th, 2007

I've been trying to clear the following lines but no way, we've two "ghost sessions" on the router.

Router#sh use

Line User Host(s) Idle Location

2 vty 0 idle never

3 vty 1 idle never

Any idea about wha't going on?

thx in advance

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
lgijssel Tue, 02/13/2007 - 04:59

Try issueing the command: sh user

This will display which ip is on the other side. This information could be quite helpfull when you don't know what is going on.

Could be anything, my best guess is a mgmt app.

Regards,

Leo

lgijssel Tue, 02/13/2007 - 05:04

Ok, sorry. You just did that.

Could you also post the output from the clear line command which you say does not work?

enriquebs Tue, 02/13/2007 - 05:09

OK ;)

The output when I try to clean the session don't say anything, I type "clear line 2" and the behaviour looks good, but after typing again the "sh use" command the sessions are taking up again...

enriquebs Tue, 02/13/2007 - 05:07

Here is the "show user" command output at present:

Router#show users

Line User Host(s) Idle Location

2 vty 0 idle never

3 vty 1 idle never

* 4 vty 2 XEBS0002 idle 00:00:00 172.26.26.99

5 vty 3 XFLO0001 idle 00:01:29 172.26.27.105

6 vty 4 XAGB0009 10.9.145.118 00:01:27 172.26.27.102

Interface User Mode Idle Peer Address

Router#

We get information about five sessions. We can handle and clear the last three, but no way to clean the two first sessions.

lgijssel Tue, 02/13/2007 - 05:30

Does the router perhaps have a special (different) line configuration for these lines?

satharcodacal Tue, 02/13/2007 - 05:31

hi,

the vty configuration chnaged, please check the configuration and vty password

regards,

sathar

enriquebs Tue, 02/13/2007 - 06:57

Here is the config. By the way, the ACL is permitting telnet and ssh from NOC's computers.

line vty 0 4

access-class 10 in

exec-timeout 30 0

password 7 password

logging synchronous

login authentication Tacacs

transport input telnet ssh

Anyway next saturday we've to reboot the router due maintenance, maybe this issue will be solved then...

Actions

This Discussion