Cisco Howto Configure Console Port/Terminal/Comm Server with Async Cable Setup

This assumes that you've already installed the relevant HWIC cards eg. Cisco Asynchronous Serial NIM

These are essentially cards that you install into your router, once installed you connect an Async cable to one of the ports on the card which normally gives you 8 console cables and are normally labelled 1 through 8.

You connect all of the cables to the devices you need (even non-Cisco devices) whether switches, routers or firewalls, they will usually work.

The real magic happens in just checking your lines and configuring them with telnet for easy access (of course the router should be secured to only authorized users only for this reason).
 

1.) Check your cables/ports

First just type show line to know what ports and cables are available.

Normally as you can see that the lines will start with 33.  To remotely connect to line 33 you would telnet to the IP of the router on port 2033 as all ports start with 2000.  The TTY types are the ASYNC lines.

show line

 

2.) Configure line access

The standard way is to just enable telnet access like this:

From config mode just do this:

 

line tty 33 64

password realtechtalk.com

login

transport input all

end

The line tty 33 64 specifies that we are applying this config to all of our async lines as shown in the previous screen they are tty 33-64.

Then we set a password, enable login and enable all input or we could have just enabled transport input telnet etc...

 

3.) telnet into the correct line

telnet yourIP 2064

Then enter your password and you will be at the console of the attached device.

This would connect you to line 64.  It is useful to label the physical devices according to the async number, as a rule you can normally just divide by 8 to get an idea of which group of lines go where (assuming you've connected them in a sequential order).


Tags:

cisco, howto, configure, console, terminal, comm, server, async, setupthis, assumes, ve, installed, relevant, hwic, eg, asynchronous, nim, essentially, install, router, ports, cables, labelled, devices, switches, routers, firewalls, configuring, telnet, secured, authorized, users, remotely, ip, tty, enable, config, mode, password, realtechtalk, login, input, specifies, applying, previous, enabled, etc, yourip, label, divide, sequential,

Latest Articles

  • qemu: could not load PC BIOS 'bios-256k.bin' solution
  • Proxmox How To Custom Partition During Install
  • Hyper-V Linux VM Boots to Black Screen, Storage, NIC Not Found Issues
  • Ubuntu Mint How to Fix Missing/Broken /dev and /dev/pts which causes terminal to immediately close exit and not work
  • How high can a Xeon CPU get?
  • bash fix PATH environment variable "command not found" solution
  • Ubuntu Linux Mint Debian Redhat Youtube Cannot Play HD or 4K videos, dropped frames or high CPU usage with Nvidia or AMD Driver
  • hostapd example configuration for high speed AC on 5GHz using WPA2
  • hostapd how to enable and use WPS to connect wireless devices like printers
  • Dell Server Workstation iDRAC Dead after Firmware Update Solution R720, R320, R730
  • Cloned VM/Server/Computer in Linux won't boot and goes to initramfs busybox Solution
  • How To Add Windows 7 8 10 11 to GRUB Boot List Dual Booting
  • How to configure OpenDKIM on Linux with Postfix and setup bind zonefile
  • Debian Ubuntu 10/11/12 Linux how to get tftpd-hpa server setup tutorial
  • efibootmgr: option requires an argument -- 'd' efibootmgr version 15 grub-install.real: error: efibootmgr failed to register the boot entry: Operation not permitted.
  • Apache Error Won't start SSL Cert Issue Solution Unable to configure verify locations for client authentication SSL Library Error: 151441510 error:0906D066:PEM routines:PEM_read_bio:bad end line SSL Library Error: 185090057 error:0B084009:x509 certif
  • Linux Debian Mint Ubuntu Bridge br0 gets random IP
  • redis requirements
  • How to kill a docker swarm
  • docker swarm silly issues