Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!att!pacbell.com!decwrl!ucbvax!ucsd!nic.cerf.net!pushp
From: pushp@nic.cerf.net (Pushpendra Mohta)
Newsgroups: comp.dcom.sys.cisco
Subject: Re: routeing between terminal servers
Message-ID: <224@nic.cerf.net>
Date: 10 Nov 90 17:47:44 GMT
References: <1990Nov9.122150.20305@cs.wayne.edu>
Organization: CERFnet, La Jolla, CA
Lines: 30

In article <1990Nov9.122150.20305@cs.wayne.edu> bri@jake.cc.wayne.edu (Brian Holmes) writes:
>Is is possible to connect two terminal servers across rs-232 ports
>and route between them over this line?  Or how about a terminal
>server with a special rs-232 port instead of an ethernet interface.
>I have an application for a remote terminal server without the
>need for an ethernet interface.  Any ideas?
>-- 
>Brian Holmes                                            

You may wish to consider the following for connecting a 
remote terminal server which does not need ethernet access.

cisco Terminal Servers can be ordered with synchronous interfaces.


---------|			|---------|->   
Backbone |        T1/56Kbps     |cisco    |->
cisco AGS|----------------------|Terminal |->   Terminals/
         |                      |Server   |->    Modems
---------|			|_________|->   ++++++++++

All routing, minimal as it is for the Terminal Server
is done with over the serial link.

(This is how CERFnet uses its Terminal servers for 
DIAL n' CERF, our dial-up Internet Access Service.)

--pushpendra
CERFnet
(619) 534-5056