Path: utzoo!utgpu!watserv1!watmath!att!pacbell!pacbell.com!ucsd!swrinde!zaphod.mps.ohio-state.edu!ncar!boulder!daemon
From: BILLW@mathom.cisco.com (WilliamChops Westfield)
Newsgroups: comp.dcom.sys.cisco
Subject: Re: LAT-Telnet Translation over Ethernet Media
Message-ID: <25806@boulder.Colorado.EDU>
Date: 7 Sep 90 02:45:29 GMT
Sender: daemon@boulder.Colorado.EDU
Lines: 41


    I need bidirectional translation between LAT and Telnet over LAN
    (Ethernet) media.  cisco has announced LAT support in the CPT (cisco
    Protocol Translator) device.  Therefore:

	1.	Will the CPT support Ethernet-Ethernet configurations?

Yes.  You can buy it with a single ethernet interface now (or, when 8.2
comes out, anyway.)  It isn't designed to have LAT and TCP on separate
ethernets - do you think that would be a useful addition?  It doesn't
seem like a common configuration for people to have their LAT network
completely distinct from their IP network.


	2.	If so, what mappings are available at the CPT to effect the
		LAT-Telnet translations?  Any translation gotchas?

LAT is a pretty trivial protocol.  There isn't much to map.  Since the
new CPT is just about to start Beta test, we haven't found any gotchas
yet.  I'd be surprised if the code were already perfect though.  :-)

The command looks something like:

	TRANSLATE LAT <servicename> TCP <hostname> [PORT <port>] [QUIET]
		[LOGIN] [MAX-USERS <n>]
or
	TRANSLATE TCP <hostname> [PORT <port>] LAT <servicename>  [QUIET]
		[LOGIN] [MAX-USERS <n>]



	3.	The CSC/3 processor seems a win for this application.  Is the
		CSC/3 board available in the CPT configuration?

It is (or will be).  Everyone should buy csc/3 processors with everything
they get nowdays.  The price difference is so much lower than the upgrade
cost that it's almost embarrassing.

Bill Westfield
cisco Systems.
-------