2811 w/NM32a issues

I'm trying to replace a 2621 with a 2811 (c2800nm-advipservicesk9-mz.124-22.T.bin) and for some reason it isn't working...

An assumption I'm making:aync ports are counted just as they would be on the 2621

A few odd things pop up right away.

ACS#sh line
   Tty Line Typ     Tx/Rx    A Modem  Roty AccO AccI  Uses  Noise Overruns  Int
*     0    0 CTY              -    -      -    -    -     0      0    0/0      -
      1    1 AUX   9600/9600  -    -      -    -    -     0      0    0/0      -
    1/0   66 TTY   9600/9600  -    -      -    -    -     0      0    0/0      -
    1/1   67 TTY   9600/9600  -    -      -    -    -     0      0    0/0      -
    1/2   68 TTY   9600/9600  -    -      -    -    -     0      0    0/0      -
    1/3   69 TTY   9600/9600  -    -      -    -    -     0      0    0/0      -
    1/4   70 TTY   9600/9600  -    -      -    -    -     0      0    0/0      -
*   1/5   71 TTY   9600/9600  -    -      -    -    -     0      1  134/405    -
    1/6   72 TTY   9600/9600  -    -      -    -    -     0      0    0/0      -
    1/7   73 TTY   9600/9600  -    -      -    -    -     0      0    0/0      -
    1/8   74 TTY   9600/9600  -    -      -    -    -     0      0    0/0      -
    1/9   75 TTY   9600/9600  -    -      -    -    -     0      0    0/0      -
   1/10   76 TTY   9600/9600  -    -      -    -    -     0      0    0/0      -
   1/11   77 TTY   9600/9600  -    -      -    -    -     0      0    0/0      -
   1/12   78 TTY   9600/9600  -    -      -    -    -     0      0    0/0      -
   1/13   79 TTY   9600/9600  -    -      -    -    -     0      0    0/0      -
   1/14   80 TTY   9600/9600  -    -      -    -    -     0      0    0/0      -
   1/15   81 TTY   9600/9600  -    -      -    -    -     0      0    0/0      -
   1/16   82 TTY   9600/9600  -    -      -    -    -     0      0    0/0      -
   1/17   83 TTY   9600/9600  -    -      -    -    -     0      0    0/0      -
   1/18   84 TTY   9600/9600  -    -      -    -    -     0      0    0/0      -
   1/19   85 TTY   9600/9600  -    -      -    -    -     0      0    0/0      -
   Tty Line Typ     Tx/Rx    A Modem  Roty AccO AccI  Uses  Noise Overruns  Int

   1/20   86 TTY   9600/9600  -    -      -    -    -     0      0    0/0      -
   1/21   87 TTY   9600/9600  -    -      -    -    -     0      0    0/0      -
   1/22   88 TTY   9600/9600  -    -      -    -    -     0      0    0/0      -
   1/23   89 TTY   9600/9600  -    -      -    -    -     0      0    0/0      -
   1/24   90 TTY   9600/9600  -    -      -    -    -     0      0    0/0      -
   1/25   91 TTY   9600/9600  -    -      -    -    -     0      0    0/0      -
   1/26   92 TTY   9600/9600  -    -      -    -    -     0      0    0/0      -
   1/27   93 TTY   9600/9600  -    -      -    -    -     0      0    0/0      -
   1/28   94 TTY   9600/9600  -    -      -    -    -     0      0    0/0      -
   1/29   95 TTY   9600/9600  -    -      -    -    -     0      0    0/0      -
   1/30   96 TTY   9600/9600  -    -      -    -    -     0      0    0/0      -
   1/31   97 TTY   9600/9600  -    -      -    -    -     0      0    0/0      -
    514  514 VTY              -    -      -    -    -     0      0    0/0      -
    515  515 VTY              -    -      -    -    -     0      0    0/0      -
    516  516 VTY              -    -      -    -    -     0      0    0/0      -
    517  517 VTY              -    -      -    -    -     0      0    0/0      -
    518  518 VTY              -    -      -    -    -     0      0    0/0      -

Line(s) not in async mode -or- with no hardware support: 
2-65, 98-513

Hm, okay, this is nothing like the 2621...

ACS#sh line summary 
        0: U??? .... .... .... ..?? .... .... .... ....
       36: .... .... .... .... .... .... .... ..?? ???u
      1/6: ???? ???? ???? ???? ???? ???? ??.. .... ....
      504: .... .... ..?? ???


   2 character mode users.           (U)
  41 lines never used.               (?)
  80 lines do not exist.             (.)
   2 total lines in use, 1 not authenticated (lowercase)

Config is default other than the following

ACS#sh run | i host 
hostname ACS
ip host r1 2033 10.250.1.1
ip host r2 2034 10.250.1.1
ip host r3 2035 10.250.1.1
ip host r4 2036 10.250.1.1

...

interface Loopback0
 ip address 10.250.1.1 255.255.255.0
!
interface FastEthernet0/0
 ip address 192.168.20.1 255.255.255.0
 duplex auto
 speed auto
!

Any advice or pointers? I didn't need to do anything special on the 2621 to get this working last time.

Thanks for reading.

Edit:

I just noticed this:

!
interface Async1/1
 no ip address
 encapsulation slip

That didn't pop up in the 2621 config for the card. It has been suggested that I need to change the port type on each line but the issue there is HOW. Seriously, I've been looking over the cisco.com documentation and I'm coming up cold on any examples or hints - if plugged into a 2600 it simply works and I know (at least it is listed as such) that this NM is supported.

Any suggestions?

Find more posts tagged with

Free for TechExams community: Cybersecurity salary guide

Compare cert salaries and plan your next career move

Button

Comments

kryolla

it looks like your lines start at 66 and not 33 so change your entry to 2066

ashed1

Tried changing ports but no go. Any other suggestions?

kryolla

this is from cisco docs
Configuring a Terminal/Comm Server - Cisco Systems

Troubleshooting Procedure
Follow these instructions to troubleshoot your configuration.

If you cannot connect to the router of your choice with a name configured in the ip host command check:

Check whether the port address is configured correctly.

Verify whether the address (interface) used for the reverse Telnet is up/up. The output of the show ip interface brief command provides this information. Cisco recommends you to use loopbacks because they are always up.

Ensure that you have the correct type of cabling. For example, you must not use a crossover cable to extend the length. Refer to the Cabling section for more information.

Establish a Telnet connection to the IP address port to test direct connectivity. You must telnet from both an external device and the terminal server. For example, telnet 172.21.1.1 2003.

Ensure that you have the transport input telnet command under the line for the target device. The target device is the device that is connected to the terminal server.

Use a PC/dumb terminal to connect directly to the console of the target router. The target router is the device connected to the terminal server. This step helps you identify the presence of a port issue.

If you are disconnected, check timeouts. You can remove or adjust timeouts.

Note: If you encounter authentication failures, remember that the terminal server performs the first authentication (if configured), while the device to which you try to connect performs the second authentication (if configured). Verify whether AAA is configured correctly on both the terminal server and the connecting device.