Terminal Server config not working, 2901 HWIC-16A

[wilson_1234_2]

I have a 2901 with an HWIC 16A module to be used as a terminal server, I am using the green Cisco 8-port async cabl The menu is working and I can see the line go active when I try to launch a console session, but the session just hangs as if there is no connection to the remote device, which is a cisco 3560X switch: Trying ASA_1 (1.1.1.1, 2003)… Open I can establish a console session to the switch outside of the terminal server with no problem. Attempting to launch the session directly from the host name (bypassing the menu) gives me the same result   Anyone see anything glaring? I have the cable connected to HWIC 0 and I am assuming that cable P0 would correspond to line 3 (0/0/0) Building configuration... Current configuration : 5696 bytes ! ! No configuration change since last restart version 15.2 service timestamps debug datetime msec service timestamps log datetime msec no service password-encryption ! hostname Peak10_TS ! boot-start-marker boot-end-marker ! ! logging buffered 51200 warnings ! no aaa new-model ! no ipv6 cef ! username admin privilege 15 password 0 password ! ! ! ! ! ! interface Loopback0  description 1.1.1.1         Terminal Server Interface  ip address 1.1.1.1 255.255.255.255 ! interface Embedded-Service-Engine0/0  no ip address  shutdown ! interface GigabitEthernet0/0  description 192.168.30.252  Uplink to Core  ip address 192.168.30.252 255.255.255.0  duplex auto  speed auto ! interface GigabitEthernet0/1  no ip address  shutdown  duplex auto  speed auto ! interface Async0/0/0  no ip address  encapsulation slip ! interface Async0/0/1  no ip address  encapsulation slip ! interface Async0/0/2  no ip address  encapsulation slip ! interface Async0/0/3  no ip address  encapsulation slip ! interface Async0/0/4  no ip address  encapsulation slip ! interface Async0/0/5  no ip address  encapsulation slip ! interface Async0/0/6  no ip address  encapsulation slip ! interface Async0/0/7  no ip address  encapsulation slip ! interface Async0/0/8  no ip address  encapsulation slip ! interface Async0/0/9  no ip address  encapsulation slip ! interface Async0/0/10  no ip address  encapsulation slip ! interface Async0/0/11  no ip address  encapsulation slip ! interface Async0/0/12  no ip address  encapsulation slip ! interface Async0/0/13  no ip address  encapsulation slip ! interface Async0/0/14  no ip address  encapsulation slip ! interface Async0/0/15  no ip address  encapsulation slip ! ip forward-protocol nd ! ip http server ip http access-class 23 ip http authentication local ip http secure-server ip http timeout-policy idle 60 life 86400 requests 10000 ! ip route 0.0.0.0 0.0.0.0 192.168.30.198 ! access-list 23 permit 10.10.10.0 0.0.0.7 ! ! menu TS title ^C  **********************************************************  JSA Terminal Server  To exit from a device, use CTRL+SHIFT+6 then press x  **********************************************************  ^C menu TS prompt ^C Your selection : ^C menu TS text 1 Connect to ASA_1 - ASA_Active menu TS command 1 resume ASA_1 /connect telnet ASA_1 menu TS text 2 Connect to ASA_2 - ASA_Standby menu TS command 2 resume ASA_2 /connect telnet ASA_2 menu TS text 3 Connect to 4500_1 - Core_Active menu TS command 3 resume 4500_1 /connect telnet 4500_1 menu TS text 4 Connect to 4500_2 - Core_Standby menu TS command 4 resume 4500_2 /connect telnet 4500_2 menu TS text s show all established sessions menu TS command s show sessions menu TS options s pause menu TS text c<no> clear the session by number ie: c5 menu TS text e menu-exit menu TS command e menu-exit menu TS text q Quit terminal server session menu TS command q exit menu TS command c1 c1 menu TS command c2 c2 menu TS command c3 c3 menu TS command c4 c4 menu TS clear-screen menu TS line-mode menu TS single-space ! ! control-plane ! ! alias exec c1 disconnect ASA_1 alias exec c2 disconnect ASA_2 alias exec c3 disconnect 4500_1 alias exec c4 disconnect 4500_2 ! line con 0  login local line aux 0 line 2  no activation-character  no exec  transport preferred none  transport input all  transport output pad telnet rlogin lapb-ta mop udptn v120 ssh  stopbits 1 line 0/0/0 0/0/15  exec-timeout 0 0  no exec  transport input telnet  transport output all  stopbits 1  flowcontrol hardware line vty 0 4  privilege level 15  password password  login local  autocommand  menu TS  transport input all  transport output all line vty 5 15  privilege level 15  password password  login local  autocommand  menu TS  transport input all  transport output all ! scheduler allocate 20000 1000 ! Below is the console config of the switch I am trying to establish a connection with. ! line con 0 exec-timeout 0 0 password password login local no exec transport output all

[Richard Burts]

OK. The first thing you need to do is to remove the command no exec from the console of the switch. That for sure causes problems.

Also in a terminal server there is usually a host definition that ties a host name to an address and port. I see in your description something that looks like it is there (Trying ASA_1 (1.1.1.1, 2003)) but I am not seeing anything like that in the config that you posted.

If that fixes the issue then great we are done. If that does not fix the problem then there is something else we have to find. I have not used this model router with this type of interface as a terminal server so I have no real experience in this particular environment and am guessing at the issue. But I worry about the encapsulation slip configured under all of the async lines. When I have configured terminal servers that work I have not had encapsulation slip on those interfaces.

If that does not get it to work then I wonder about the relationship of line numbers to port numbers. Would you post the output of show line from the router?

HTH

Rick

[wilson_1234_2]

The host lines are there, I think I just cut them off :

ip host ASA_1 2003 1.1.1.1
ip host ASA_2 2004 1.1.1.1
ip host 4500_1 2005 1.1.1.1
ip host 4500_2 2006 1.1.1.1

Here is the "sh line" I am using the 16 port HWIC and the green octal cables. I have the cable plugged into the HWIC 0

#sh line
   Tty Line Typ     Tx/Rx    A Modem  Roty AccO AccI  Uses  Noise Overruns  Int
*     0    0 CTY              -    -      -    -    -     1      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      0    0/0      -
  0/0/9   12 TTY   9600/9600  -    -      -    -    -     0      0    0/0      -
 0/0/10   13 TTY   9600/9600  -    -      -    -    -     0      0    0/0      -
 0/0/11   14 TTY   9600/9600  -    -      -    -    -     0      0    0/0      -
 0/0/12   15 TTY   9600/9600  -    -      -    -    -     0      0    0/0      -
 0/0/13   16 TTY   9600/9600  -    -      -    -    -     0      0    0/0      -
 0/0/14   17 TTY   9600/9600  -    -      -    -    -     0      0    0/0      -
 0/0/15   18 TTY   9600/9600  -    -      -    -    -     0      0    0/0      -
    388  388 VTY              -    -      -    -    -     0      0    0/0      -
    389  389 VTY              -    -      -    -    -     0      0    0/0      -
    390  390 VTY              -    -      -    -    -     0      0    0/0      -
   Tty Line Typ     Tx/Rx    A Modem  Roty AccO AccI  Uses  Noise Overruns  Int

    391  391 VTY              -    -      -    -    -     0      0    0/0      -
    392  392 VTY              -    -      -    -    -     0      0    0/0      -
    393  393 VTY              -    -      -    -    -     0      0    0/0      -
    394  394 VTY              -    -      -    -    -     0      0    0/0      -
    395  395 VTY              -    -      -    -    -     0      0    0/0      -
    396  396 VTY              -    -      -    -    -     0      0    0/0      -
    397  397 VTY              -    -      -    -    -     0      0    0/0      -
    398  398 VTY              -    -      -    -    -     0      0    0/0      -
    399  399 VTY              -    -      -    -    -     0      0    0/0      -
    400  400 VTY              -    -      -    -    -     0      0    0/0      -
    401  401 VTY              -    -      -    -    -     0      0    0/0      -
    402  402 VTY              -    -      -    -    -     0      0    0/0      -
    403  403 VTY              -    -      -    -    -     0      0    0/0      -

Line(s) not in async mode -or- with no hardware support:
19-387

[Richard Burts]

Thanks for the additional information. You asked if we see anything glaring and the absence of port assignments to host names was pretty glaring. I am glad to know that they are really in the config and just did not make it into what you posted.

And the correlation of line number and port number looks right.

So what about the other issues/possible issues that I mentioned? Have you removed the no exec from the switch console? Have you tried removing the encapsulation slip from one of the lines that you are testing?

HTH

Rick

[wilson_1234_2]

I can see that line 3 is the one attempting to make the connection.

I am assuming that slot 0 in the HWIC and P0 is the correct cable to be using for this connection.

I did try each one of the eight cables earlier though and still couldn't get a connection.

[wilson_1234_2]

It is either on or the other, if you remove one, it flips to the other encapsulation type.

[Richard Burts]

I am surprised that it requires one or the other of slip or ppp. I wonder what would happen if you did this in global config mode

default interface Async0/0/0

HTH

Rick

[wilson_1234_2]

Thanks for the help Rick,

The problem turned out to be the cable.

Also, the interfaces are configured for SLIP encapsulation and are working.

[Richard Burts]

I am glad to know that you have solved the problem and that it turned out to be the cable. Thanks for letting us know that the interfaces are configured with slip and are working. I am slightly surprised and glad to have confirmation of this. 

HTH

Rick

[wilson_1234_2]

I noticed the encapsulation SLIP also, but wasn't sure if that was an issue or not.

I just changed the encapsulation to PPP with the same results and the "no exec" has been removed from the console port of the device I am attempting to connect to.

Still no luck.

[Richard Burts]

Thanks for the additional information. Sorry it still is not working. What about removing the encapsulation ppp and not specifying any encapsulation on the async interfaces?

HTH

Rick