Re: LAT

From: Chuah Eng Wee (chuahew@xxxxxxxxxxxxxxx)
Date: Wed Jul 28 1999 - 01:22:39 GMT-3


   
Hi Bill,

Here are a few from www.bossom

HTH
Eng Wee

Telnet to LAT Practice Lab
--------------------------
An easy lab to start your weekend

[R1]--[R2]--[R3]

Router 1 is running strictly TCP/IP.
Router 3 is running strictly LAT and is advertising a LAT service called
COOL5.

R1
int S1
ip address 157.89.8.1 255.255.255.0

R3
lat service COOL5 autocommand sh protocols
int S0
lat enable

Configure Router 2 so that R1 can connect to R3's LAT service. You may not
make any changes to R1 or R3. For router R1 connecting to this LAT service
should be a one-step process.

For Answer:

      Protocol translation allows a router to translate from one protocol,
like TCP to another protocol like LAT.
      Two-step protocol translation works like this
      User telnets into the router and logs into the router.
      User then LATs to the lat device.

      might look like this:
      telnet 157.89.8.2
      Welcome to R2
      username: john
      password: secret
      R2#
      R2#LAT COOL5
      Welcome to COOL5
      .....

      One-Step Protocol translation work like this
      User telnets to an ip address monitored by the router, the router
automatically connects them to the lat service.

      might look liks this:
      telnet 157.89.8.3
      Welcome to COOL5
      .....

      The answer:

      R2
      translate tcp 157.89.8.3 lat COOL5
      int s0
      ip address 157.89.8.2 255.255.255.0
      int s1
      lat enable

----------------------------------------------------------------------------
------

Your challenge. Configure a LAT service on R3 called COOLBEANS that
automatically displays the version information when a user
     connects to it.

     R1 should be able to access this service.

     Current Minimalized Config:

     R1
     int serial 0
         ip address 10.10.12.1 255.255.255.0

     R2
     int serial 0
         ip address 10.10.12.2 255.255.255.0
     int serial 0
         ip address 10.10.23.2 255.255.255.0

     R3
     int serial 0
         ip address 10.10.23.3 255.255.255.0

     Stumped??? The answer is here.

at only needs to be enable on routers R1 and R3. Lat is a non routable
protocol so it only need to bridged through R2.

     R1
     int s0
         lat enable

     R2
     int s0
         bridge-group 1
     int s1
         bridge-group 1

     R3
     lat service enable
     lat service COOLBEANS autocommand show version
     int s1
         lat enable

http://www.boson.com
Click on CCIE Study
Click on LAT-to-Telnet

At 22:32 27/07/99 -0500, Bill Carter wrote:
>I am looking for help on LAT. Any suggestions, advice, and labs would
>be appreciated.
>
>--
>~~~~~~~~~~~~~~~~~~~~~~~~
>Bill Carter
>Favorite Quote
>"bodega stuck again... "
> -Cisco Bug CSCdk37204
>~~~~~~~~~~~~~~~~~~~~~~~~
>
>



This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:21:43 GMT-3