From: Michael Bausenwein (mikeb55@xxxxxxxx)
Date: Mon Oct 09 2000 - 11:25:57 GMT-3
look on CCO. there is a good doc on it....
http://www.cisco.com/univercd/cc/td/doc/product/software/ssr83/tsc_r/54006.h
tm
you don't need to buy any hardware other than the routers you already have.
You can configure a lat service on one router, then connect to it from
another. Once you have that working, setup autocommands for a lat service,
with and without passwords. Lastly run lat over a tcp network, using
protocol translation. If you can do these, you've got a decent decnet
(sorry I couln't resist) understanding...
Michael Bausenwein
CCIE #5865
Senior Network Engineer
Greenwich Technology Partners
email:mbausenwein@greenwichtech.com
----- Original Message -----
From: "Andrew" <arousch@home.com>
To: "John Conzone" <jkconzone@home.com>; "ccielab" <ccielab@groupstudy.com>
Sent: Sunday, October 08, 2000 12:03 PM
Subject: Re: LAT help
> LAT is DEC's "Local Area Transport." It's the transport used with DEC (or
> compatible) terminal servers to communicate with a VAX or Alpha running
> VMS. Typically a Cisco was thrown into the mix when people wanted to
> migrate from LAT to TCP/IP via the protocol translation feature of IOS (at
> least that's what I used them for back in the day.)
>
> You could probably pick up a cheap DEC terminal and run it into the Cisco
> and play with it there.
>
> At 09:41 AM 10/8/00 -0400, John Conzone wrote:
> > Hi, all. The archives are kinda thin on this subject, and I've never
> > used lat.
> > Can you guys point me in the right direction on this? How is it most
> > ususally deployed? I see some references to bridging it, which seems
> > straight forward, and also translating it.
> > It seems we can set up a LAT service on a router to test as well,
bit
> > I can't get this to work. Any help is appreciated.
> > Thanks!
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:25:24 GMT-3