Cisco VTY Session Question

[Carlton Patterson]

Community,

Can someone take a look at the following vty line configuration and let me know why I can't open more than one session

line vty 0

exec-timeout 60 0

login authentication vty_access

transport input all

line vty 1

exec-timeout 60 0

login authentication vty_access

no exec

transport preferred none

transport input all

line vty 2 4

exec-timeout 60 0

login authentication vty_access

transport input all

line vty 5 15

exec-timeout 60 0

login authentication vty_access

no exec

transport preferred none

transport input all

!

[Richard Burts · Accepted solution]

I see issues that prevent some of the vty lines from accepting sessions but not enough problems to account for being limited to a single session. on vty 1 and on 5 to 15 you have configured no exec. This prevents any session from being established.

I assume that the session you establish is probably on vty 0. I do not see what would prevent additional sessions on vty 2 through 4. Perhaps there is something in vty_access which is having this impact? We need to have more information to be able to come up with a good explanation. At a minimum we will need to see the aaa parts of the config. Perhaps the output of show line might also be helpful.

HTH

Rick

[Carlton Patterson]

Hi Richard,

Thanks for getting back to me.

The problem was 'no exec'

Cheers

Carlton

[Richard Burts]

Carlton

I am glad that you have resolved the issue and that my suggestion was helpful. Thank you for using the rating system to mark the question as answered.

HTH

Rick

[Marvin Rhoads]

I was going to say the same earlier. By default vty login will use the next avaialble vty line. Since you always had line 1 avaialble but essentially unusable, you could not establish a second vty.

I believe you could have hacked around that by specifying the line number when inititaing a login. e.g. telnet  3003 as specified in this old thread.