cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2175
Views
0
Helpful
6
Replies

Cisco Terminal server 2901 issue

PdhineshK
Level 1
Level 1

Hi Team,

           Recently in our environment we installed and configured the new cisco terminal server 2901.As of now we connected four switches connected in the terminal server.I am able to login the switches from the command prompt thru telnet x.x.x.x(Terminal server ip ) 2011(port).Sometimes its i amn't able to login the switch via outside telnet and locally in the terminal server.I got the below error.

Thru Telnet:

C:\Users\admin>telnet 10.10.1.1 2011
Connecting To 10.10.1.1...Could not open connection to the host, on port 201
1: Connect failed

 

Thru Cisco Terminal server:

CTS#Sw01
Trying Sw01 (192.168.0.1, 2011)...
% Connection refused by remote host

I tried to check the session i am getting "No connection open".Below output i am getting for show line command.I can't able to understand the output.Sometimes its working after restart the server but not continuously again getting the error.

Please provide the inputs to resolve this issue.

 

CTS#sh line
   Tty Line Typ     Tx/Rx    A Modem  Roty AccO AccI  Uses  Noise Overruns  In
      0    0 CTY              -    -      -    -    -     0      0    0/0
      1    1 AUX   9600/9600  -    -      -    -    -     0      0    0/0
      2    2 TTY   9600/9600  -    -      -    -    -     0      0    0/0
  0/0/0    3 TTY   9600/9600  -    -      -    -    -     0      0    0/0
  0/0/1    4 TTY   9600/9600  -    -      -    -    -     0      0    0/0
  0/0/2    5 TTY   9600/9600  -    -      -    -    -     0      0    0/0
  0/0/3    6 TTY   9600/9600  -    -      -    -    -     0      0    0/0
  0/0/4    7 TTY   9600/9600  -    -      -    -    -     0      0    0/0
  0/0/5    8 TTY   9600/9600  -    -      -    -    -     0      0    0/0
  0/0/6    9 TTY   9600/9600  -    -      -    -    -     0      0    0/0
  0/0/7   10 TTY   9600/9600  -    -      -    -    -     0      0    0/0
* 0/0/8   11 TTY   9600/9600  -    -      -    -    -     0      1 7525888/0
  -
* 0/0/9   12 TTY   9600/9600  -    -      -    -    -     0      1 7299968/0
  -
*0/0/10   13 TTY   9600/9600  -    -      -    -    -     0      1 7002001/0
  -
*0/0/11   14 TTY   9600/9600  -    -      -    -    -     0      1 7433019/0
  -
*0/0/12   15 TTY   9600/9600  -    -      -    -    -     0      2 3764335/0
  -
*0/0/13   16 TTY   9600/9600  -    -      -    -    -     0      0 3374894/0

 

 

 

    

6 Replies 6

PdhineshK
Level 1
Level 1

Can anyone please provide inputs to resolve this issue.

Hello,

Can you please post the complete configuration of the 2901 console server? It will help to narrow down the possible cause.

Best regards,
Peter

Hi Peter, Thanks for the response.Please find the attached config. I am able to login all the devices in first time.After i close the window if i am try to login again but no luck getting failed error.When i put command show line its shows asterik symbol in the port whcih i am trying.Seems to connections are not properly closed.Can you please check the config wheather timeout is configured correct or not.

Hi,

A couple of comments and suggestions.

  • On your line 0/0/0 through 0/0/15, you should have the no exec command configured. This command prevents the terminal server from inadvertently starting its own CLI session on a particular line if a newline arrives from any of the attached devices.
  • The transport output command on your line 0/0/0 through 0/0/15 is superfluous and can be removed - that is, enter transport output all. Also, for simplicity, these lines should be configured with transport input all

Would you mind testing these two suggestions and coming back with any news?

Best regards,
Peter

Thanks for the information... I need to give no exec-timeout its enough or do i need add exec-timeout 0 0 in the line 1 16....I want to know is there any difference for the both command

Hello,

No, it is not the no exec-timeout command. It is, literally, no exec - this is a different command. The no exec-timeout configures a timeout for inactivity. The no exec prevents the terminal router from starting its own command line if the devices attached to these lines send a character that would resemble the RETURN key being hit.

By the way, writing no exec-timeout is equivalent to writing exec-timeout 0 0.

Best regards,
Peter