Terminal Server Setup
Terminal Server Setup
Table of Contents
Configuring a Terminal/Comm Server.............................................................................................................1
Introduction.............................................................................................................................................1
Before You Begin...................................................................................................................................1
Conventions......................................................................................................................................1
Prerequisites.....................................................................................................................................1
Components Used.............................................................................................................................1
Cabling....................................................................................................................................................2
Design Strategy.......................................................................................................................................2
Configure................................................................................................................................................2
Network Diagram.............................................................................................................................3
Configurations..................................................................................................................................3
Command Summary.........................................................................................................................5
Switching Between Active Sessions.......................................................................................................6
Terminating Active Sessions..................................................................................................................6
Verify and Troubleshoot.........................................................................................................................6
Related Information................................................................................................................................7
i
Configuring a Terminal/Comm Server
Introduction
Before You Begin
Conventions
Prerequisites
Components Used
Cabling
Design Strategy
Configure
Network Diagram
Configurations
Command Summary
Switching Between Active Sessions
Terminating Active Sessions
Verify and Troubleshoot
Related Information
Introduction
A terminal or comm server commonly provides out−of−band access for multiple devices. A terminal server is
a router with multiple, low speed, asynchronous ports that are connected to other serial devices, such as
modems or console ports on routers or switches.
The terminal server allows you to use a single point to access the console ports of many devices. Using a
terminal server avoids the need for configuring backup scenarios such as modems on auxiliary ports for every
device. You can also configure a single modem on the auxiliary port of the terminal server, thus providing
dial−up service to the other devices during a network connectivity failure.
This document shows how to configure a terminal server to access only the console ports on other routers
using Reverse Telnet. Reverse Telnet allows you to Telnet out from a device you are telnetting from, but on a
different interface. For more information on Reverse Telnet refer to Establishing a Reverse Telnet Session to a
Modem.
Prerequisites
There are no specific prerequisites for this document.
Components Used
This document is not restricted to specific software and hardware versions.
Note: The async ports from the 68−pin connector are data terminal equipment (DTE) devices. DTE to DTE
devices require a rolled (null modem) cable and DTE to data circuit−terminating equipment (DCE) devices
require a straight−through cable. Since the CAB−OCTAL−ASYNC cable is itself rolled, you can connect
each cable directly to the console ports of devices with RJ−45 interfaces. However, if the console port of the
device you are connecting to is a 25 pin interface (DCE) use the RJ−45 to 25 pin adapter marked "Modem" (to
reverse the "roll") to complete the connection.
Port types for console and auxiliary ports on Cisco routers and switches are:
Interface Type
DB25 Interface RJ−45 Interface
Console
DCE DTE
AUX
DTE DTE
Design Strategy
Configure the terminal server so that it is accessible from anywhere by giving it a registered public Internet
address, and by locating it outside the firewall so that firewall issues will not interrupt your connection. This
ensures that you can always maintain connectivity to the terminal server and have access to the connected
devices. If you are concerned about security, you may want to configure access lists to only allow access to
the terminal server from certain addresses. You can also configure server−based authentication, authorization,
and accounting (AAA) such as RADIUS or TACACS+ for a more robust security solution. For more
information on AAA refer to the Cisco AAA Implementation Case Study.
You can configure a modem on the auxiliary port of the terminal server for dial backup in the event your
primary connection (through the Internet) goes down. This eliminates the need to configure a dial backup for
each device, as the terminal server is connected through its async ports to the console ports of the other
devices. For more information on connecting a modem to the AUX port, refer to Modem−Router Connection
Guide.
Use the ip default gateway statement pointing to the the next hop router on the Internet. This allows you to
have connectivity to the terminal server through the Internet even if routing is not enabled. For example, the
terminal server is in ROM monitor (ROMMON) mode as a result of a bad reboot after a power outage.
Configure
In this section, you are presented with the information to configure the features described in this document.
Note: To find additional information on the commands used in this document, use the Command Lookup
Tool ( registered customers only) .
Configurations
This document uses the configuration shown below.
Cisco 2511
aus−comm−server#show running−config
!
version 12.0
no ip directed−broadcast
!
interface Ethernet0
ip address 171.55.31.5 255.255.255.192
No ip directed−broadcast
no ip mroute−cache
!
interface Serial0
no ip address
no ip directed−broadcast
no ip mroute−cache
shutdown
!
ip default−gateway 171.55.31.1
ip classless
ip route 0.0.0.0 0.0.0.0 171.55.31.1
no ip http server
!
line con 0
transport input all
line 1 16
session−timeout 20
no exec
exec−timeout 0 0
line aux 0
Command Summary
ip host − Used to define the static host's name−to−address mapping in the host cache. To remove the
name−to−address mapping, use the no form of this command.
♦ name − Name of the host. The name field does not have to match the actual name of the
router you are trying to connect to, but it should be a name you would want to use in the
reverse Telnet. By using this command and the name field, the user does not have to know the
actual port number of the remote device.
♦ tcp−port−number − TCP port number to connect to when using the defined host name in
conjunction with an EXEC connect or telnet command. In our example configuration, we are
using a reverse Telnet so the port number must be 2000+line number.
♦ address1 − Associated IP address. In our example configuration, we use the loopback IP
address.
transport input − Used to define which protocols to use to connect to a specific line of the router.
• transport input {all | lat | mop | nasi | none | pad | rlogin | telnet | v120}
telnet − This EXEC command is used to login to a host that supports Telnet.
♦ host − A host name or IP address. This can be one of the name fields defined in the ip host
command as shown above.
♦ port − A decimal TCP port number; the default is the Telnet router port (decimal 23) on the
host. For the reverse Telnet, the port number must be 2000+line number. Line numbers would
be from 1−16 in our configuration. Use the show line EXEC command to see the available
lines.
1. Escape from the current session by using the escape sequence Ctrl−Shift−6−x.
2. Display all open connections use the show sessions command.
aus−comm−server#show sessions
Conn Host Address Byte Idle Conn Name
1 2511−1 171.69.163.26 0 0 2511−1
2 2511−2 171.69.163.26 0 0 2511−2
* 3 2511−3 171.69.163.26 0 0 2511−3
1. Suspend/escape from the current session. To suspend a Telnet session, enter the escape sequence
Ctrl−Shift−6−x.
Note: Ensure that you can reliably issue the escape sequence to suspend a Telnet session. Some
terminal emulator packages have difficulty sending the correct sequence, Ctrl−Shift−6, x.
2. Display all open connections using the show sessions command.
3. Disconnect the desired session using the disconnect [connection] command.
Certain show commands are supported by the Output Interpreter Tool ( registered customers only) , which allows
you to view an analysis of show command output.
If you cannot connect to the router of your choice using a name configured in the ip host command check:
Related Information
• Modem−Router Connection Guide
• Establishing a Reverse Telnet Session to a Modem
• Configuring Terminal Lines and Modem Support
• Terminal Line and Modem Support Commands
• Cabling Guide for RJ−45 Console and AUX Ports
• Serial Cable Guide
• Field Notice: Terminal Server Break Character on Cisco Access Servers
• Cisco AAA Implementation Case Study
• Access Products Support Pages
• Dial Technology Support Pages
• Technical Support − Cisco Systems
All contents are Copyright © 1992−2004 Cisco Systems, Inc. All rights reserved. Important Notices and Privacy Statement.