<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>CCIE Lab &#187; terminal server</title>
	<atom:link href="http://ccielab.ro/tag/terminal-server/feed/" rel="self" type="application/rss+xml" />
	<link>http://ccielab.ro</link>
	<description>Cry in the Lab, Laugh in the Datacenter</description>
	<lastBuildDate>Mon, 02 Jan 2012 00:15:56 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Configuring a Terminal Server</title>
		<link>http://ccielab.ro/2009/08/configuring-a-terminal-server/</link>
		<comments>http://ccielab.ro/2009/08/configuring-a-terminal-server/#comments</comments>
		<pubDate>Wed, 19 Aug 2009 15:04:32 +0000</pubDate>
		<dc:creator>bogd</dc:creator>
				<category><![CDATA[HowTo]]></category>
		<category><![CDATA[configuration]]></category>
		<category><![CDATA[terminal server]]></category>
		<category><![CDATA[tutorial]]></category>

		<guid isPermaLink="false">http://ccielab.ro/?p=3</guid>
		<description><![CDATA[Like most CCIE Lab stories, this one starts with a way to access the consoles remotely &#8211; a terminal server. In my case, a Cisco 2811 with a NM-16A module (and a CAB-OCTAL-ASYNC breakout cable for connecting 8 routers).
I have had the opportunity to work with terminal servers many times before (including the actual CCIE [...]]]></description>
			<content:encoded><![CDATA[<p>Like most CCIE Lab stories, this one starts with a way to access the consoles remotely &#8211; a terminal server. In my case, a Cisco 2811 with a NM-16A module (and a CAB-OCTAL-ASYNC breakout cable for connecting 8 routers).</p>
<p>I have had the opportunity to work with terminal servers many times before (including the actual CCIE lab) &#8211; but they were always configured by other people. This time, I had to configure the TS myself. No problem, I say&#8230;</p>
<blockquote>
<pre>TS(config)#int lo0
TS(config-if)#ip add 192.168.1.1 255.255.255.255

!--- line numbers may vary depending on module
!--- use "show line" to determine the numbers in use
TS(config-if)#line 66 81
TS(config-line)#transport input all

!--- Optional
TS(config-line)#flowcontrol hardware

!--- Optional, but it makes accessing the devices easier
TS(config)#ip host r1 2066 192.168.1.1
TS(config)#ip host r2 2067 192.168.1.1
TS(config)#ip host r3 2068 192.168.1.1
TS(config)#ip host r4 2069 192.168.1.1
TS(config)#ip host r5 2070 192.168.1.1
TS(config)#ip host r6 2071 192.168.1.1
TS(config)#ip host r7 2072 192.168.1.1
TS(config)#ip host r8 2073 192.168.1.1</pre>
</blockquote>
<p>Looks good, and I can now access the devices by telnetting to the various ports on 192.168.1.1. Yet something is wrong&#8230; The lines become busy at random intervals, which makes the terminal server refuse connections. A &#8220;clear line&#8221; solves the problem, but only for a very short time &#8211; just seconds later, the line becomes active again.</p>
<blockquote><pre>
TS#sh line
   Tty Line Typ     Tx/Rx    A Modem  Roty AccO AccI  Uses  Noise Overruns  Int

*   1/6   72 TTY   9600/9600  -    -      -    -    -     3   1448  447/1343   -
*   1/7   73 TTY   9600/9600  -    -      -    -    -     5    129   62/188    -

TS#r1
Translating "r7"
Trying r7 (192.168.1.1, 2072)...
% Connection refused by remote host
</pre>
</blockquote>
<p>After several hours of frustration (clearing lines just to have them become busy again almost immediately), I realize what I forgot:</p>
<blockquote><pre>
TS(config-if)#line 66 81
TS(config-line)#no exec
</pre>
</blockquote>
<p>The explanation? Any kind of noise on the wire was interpreted by the TS as an incoming character. As a result, the TS would activate the line, opening an exec session. A &#8220;clear line&#8221; would close the session, only to have it opened again by the noise.</p>
<p>As <a href="http://www.ciscokits.com/cisco-terminal-server/">somebody else</a> put it &#8211; &#8220;&#8216;No exec&#8217; isn&#8217;t mandatory, but it will help you keep your sanity!&#8221;</p>
]]></content:encoded>
			<wfw:commentRss>http://ccielab.ro/2009/08/configuring-a-terminal-server/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

