cisco terminal server config

Hi all

I'm putting together a how-to for a 2511 terminal server that I'll eventually post in the CCNA forum. Here's my config, which I'm posting here in the hopes that someone can point out any errors they see. It's from a working terminal server, but I needed to change the IPs so I'm hoping it is still a good config. Any comments/suggestions are appreciated.

And if you have a 2511 to test it with, all the better.

IOS is 12.3, unrelated commands have been removed

The smiley face with the sunglasses should be an 8

ip host FRAM 2009 10.1.28.11
ip host SW6 2008 10.1.28.11
ip host R02 2014 10.1.28.11
ip host SW2 2002 10.1.28.11
ip host SW5 2005 10.1.28.11
ip host R01 2001 10.1.28.11
ip host R03 2004 10.1.28.11
ip host R07 2006 10.1.28.11
ip host R20 2012 10.1.28.11
ip host R02 2010 10.1.28.11
ip host SW3 2003 10.1.28.11
ip host R10 2007 10.1.28.11
ip host SW7 2015 10.1.28.11
ip host rtn 10.1.28.11
ip host R07A 2007 10.1.28.11
ip host R03A 2016 10.1.28.11
ip host R01A 2010 10.1.28.11
ip host R06 2016 10.1.28.11
ip host R08 2011 10.1.28.11
ip host SW8 2013 10.1.28.11
!
interface Loopback0
ip address 10.1.28.11 255.255.255.255
!
interface Ethernet0
ip address 172.16.1.11 255.255.255.0
!
menu TS title ^CC
*******************************************************
CCNP Lab Terminal Server
*******************************************************
^C
menu TS text 1 Connect to R01 (1)
menu TS command 1 resume R01 /connect telnet R01
menu TS text 2 Connect to R01a (2)
menu TS command 2 resume R02 /connect telnet R02
menu TS text 3 Connect to R02 (3)
menu TS command 3 resume R02 /connect telnet R02
menu TS text 4 Connect to R07 (4)
menu TS command 4 resume R07 /connect telnet R07
menu TS text 5 Connect to R07A (5)
menu TS command 5 resume R10 /connect telnet R10
menu TS text 6 Connect to R20 (6)
menu TS command 6 resume R20 /connect telnet R20
menu TS text 7 Connect to R03 (7)
menu TS command 7 resume R03 /connect telnet R03
menu TS text 8 Connect to R03a (
menu TS command 8 resume R06 /connect telnet R06
menu TS text 9 Connect to R08 (9)
menu TS command 9 resume R08 /connect telnet R08
menu TS text 10 Connect to FRAM (10)
menu TS command 10 resume FRAM /connect telnet FRAM
menu TS text 11 Connect to SW2 (11)
menu TS command 11 resume SW2 /connect telnet SW2
menu TS text 12 Connect to SW3 (12)
menu TS command 12 resume SW3 /connect telnet SW3
menu TS text 13 Connect to SW5 (13)
menu TS command 13 resume SW5 /connect telnet SW5
menu TS text 14 Connect to SW6 (14)
menu TS command 14 resume SW6 /connect telnet SW6
menu TS text 15 Connect to SW7 (15)
menu TS command 15 resume SW7 /connect telnet SW7
menu TS text 16 Connect to SW8 (16)
menu TS command 16 resume SW8 /connect telnet SW8
menu TS text s Show all established sessions
menu TS command s show sessions
menu TS options s pause
menu TS text e Exit menu
menu TS command e menu-exit
menu TS command c1 c1
menu TS command c2 c2
menu TS command c3 c3
menu TS command c4 c4
menu TS command c5 c5
menu TS command c6 c6
menu TS command c7 c7
menu TS command c8 c8
menu TS command c9 c9
menu TS command c10 c10
menu TS command c11 c11
menu TS command c12 c12
menu TS command c13 c13
menu TS command c14 c14
menu TS command c15 c15
menu TS command c16 c16
!
alias exec c1 disconnect 1
alias exec m menu TS
alias exec c3 disconnect 3
alias exec c4 disconnect 4
alias exec c5 disconnect 5
alias exec c6 disconnect 6
alias exec c7 disconnect 7
alias exec c8 disconnect 8
alias exec c9 disconnect 9
alias exec c10 disconnect 10
alias exec c11 disconnect 11
alias exec c12 disconnect 12
alias exec c13 disconnect 13
alias exec c14 disconnect 14
alias exec c15 disconnect 15
alias exec c16 disconnect 16
alias exec c2 disconnect 2
!
line con 0
exec-timeout 0 0
logging synchronous
line 1 16
no exec
transport input all
line aux 0
transport input all
line vty 0 4
exec-timeout 0 0
logging synchronous
login

Find more posts tagged with

Comments

tiersten

Netwurk wrote: »

ip host FRAM 2009 10.1.28.11
ip host SW6 2008 10.1.28.11
ip host R02 2014 10.1.28.11
ip host SW2 2002 10.1.28.11
ip host SW5 2005 10.1.28.11
ip host R01 2001 10.1.28.11
ip host R03 2004 10.1.28.11
ip host R07 2006 10.1.28.11
ip host R20 2012 10.1.28.11
ip host R02 2010 10.1.28.11
ip host SW3 2003 10.1.28.11
ip host R10 2007 10.1.28.11
ip host SW7 2015 10.1.28.11
ip host rtn 10.1.28.11
ip host R07A 2007 10.1.28.11
ip host R03A 2016 10.1.28.11
ip host R01A 2010 10.1.28.11
ip host R06 2016 10.1.28.11
ip host R08 2011 10.1.28.11
ip host SW8 2013 10.1.28.11

Why don't you just use regular telnet instead of reverse telnet from the 2511? I've never understood the need for people to use reverse telnet with a 2511.

Telnet to the 2511 on port 2011 from your workstation and you'll connect direct to R08 in your configuration.

Telnet to the 2511 on port 2015 from your workstation and you'll connect direct to SW7 in your configuration.

You should get the idea. Each port from 2001 to 2016 corresponds to the numbered serial lines. A 2509 would only go up to 2008. I just use SecureCRT with tabs or just multiple windows and away I go.

2000 = Telnet
3000 = Telnet rotary
4000 = Raw TCP
5000 = Raw TCP rotary
6000 = Telnet binary
7000 = Telnet binary rotary
9000 = XRemote
10000 = XRemote rotary

You generally only want to use regular telnet and the normal line instead of the rotary versions since you don't want the rotary group functionality as you're trying to connect to a specific line/device.

version 12.3
no service pad
service tcp-keepalives-in
service tcp-keepalives-out
service timestamps debug datetime msec localtime show-timezone
service timestamps log datetime msec localtime show-timezone
service password-encryption
service sequence-numbers
!
no aaa new-model
ip subnet-zero
!
interface Loopback0
 ip address 10.99.99.1 255.255.255.0
!
interface Null0
 no ip unreachables
!
interface Ethernet0
 ip address 192.168.1.180 255.255.255.0
!
interface Serial0
 no ip address
 shutdown 
!
interface Serial1
 no ip address
 shutdown
!
no ip http server
ip classless
!
no cdp run
!
line con 0
line 1 16
 no exec  
 transport input all
line aux 0
 transport input all
line vty 0 4
 login
!

Netwurk

Yes, for example, you could just use the command telnet 172.16.1.11 2011 from the Windows or Unix/Linux command line.

I like the menus and the reverse telnet thing as it keeps everything on one box and in one window. Comes in handy when you already have 12 windows open but also want to work on your lab. But I'll definitely include the regular telnet method in my how-to. And I'm sure I'll here from security-minded folks who think it should all be ssh.

tiersten

Netwurk wrote: »

I like the menus and the reverse telnet thing as it keeps everything on one box and in one window.

Tabbed telnet or just have enough screen real estate that you can tile them IMO

Netwurk wrote: »

And I'm sure I'll here from security-minded folks who think it should all be ssh.

You can do SSH with 12.2.15T17 on a 2511 as they added it in that specific version but then removed it very quickly after that. The CPU in a 2511 is just too slow to handle SSH properly.

Netwurk

Cool tips, Tiersten

One other reason I use the menu/reverse telnet method is that the telnet to port method doesn't work remotely, at least not with my config. I use NAT to point any incoming telnets to my terminal server. Of course I could point NAT to any old router and then telnet to port from there but for some reason I think my menus rock.

Netwurk

My original thought here was to post a way cool TE config for the noble old 2500 Cisco terminal servers. Tiersten has more or less convinced me to post it here instead of in the CCNA forum as I would no doubt confuse the kids.

There are some cool non-Cisco terminal servers, but doing a config for a Cisco 2511 (or some other flavor) has the added benefit of helping a student learn IOS commands.

Anyhow, this is my longwinded attempt to bump this thread.

tiersten

Netwurk wrote: »

My original thought here was to post a way cool TE config for the noble old 2500 Cisco terminal servers. Tiersten has more or less convinced me to post it here instead of in the CCNA forum as I would no doubt confuse the kids.

Sorry! That wasn't my intention. If you do want to do your remote access method via NAT then you're going to need your menu. I have a VPN setup along with port forwarding for IPv4 NAT and IPv6 so I've got plenty of choices for direct connection to the console server.