From: Gerwin Boschloo (BoschlooG@xxxxxxxxx)
Date: Tue Jun 13 2000 - 17:03:37 GMT-3
Hi,
LAT should be bridged. The "LAT ENABLED" command just tells the router to
listen to LAT Service broadcasts so you can do a show lat service and start
a interactive lat session.
This is how it shows on one of our routers.
Rtrnat>sh lat services
Service Name Rating Interface Node (Address)
AP99 28 Ethernet0 AP99 (aa00.0400.04e0)
Ident: VAXstation 3100-30 Veendam VERTIS Answer 421
APPS01 136 Ethernet0 APPS01 (0000.f81b.0c2c)
Ident: Digital UNIX Version V4.0 LAT SERVICE
CALLOUT 255 Ethernet0 VDT04 (0800.2b10.654a)
Ident: Uitbel Service Storingsdienst
When you want to make the lat service available over a WAN link you should
use lat-to-telnet translation or you should bridge it. Bridging Lat over a
frame-relay link is very horrible because of the timing inside lat, it
almost forces you to use priority queuing.
What we do is, we uses a very dense access-list to allow Lat through based
on the ethernet type field.
Gerwin
E-mail: boschloog@vertis.nl
-----Original Message-----
From: David Goldsmith [mailto:dgoldsmi@cisco.com]
Sent: Thursday, June 08, 2000 6:42 PM
To: Brian Hescock
Cc: Wang, Kai; ccielab@groupstudy.com
Subject: Re: LAT over F/R
Group,
I am not a LAT expert..... But I thought you could only bridge Lat of
Frame...
I'll look this up a little later...
Dave G.
Brian Hescock wrote:
> Please let me know how it goes after saving the config without the
> mac-addr command and doing a reload. It could potentially have it in
> memory still, just as frame pvc's are even after removing them from the
> config and you have to reload the router to get rid of it.
>
> I've decoded the traceback and the error was in frame encapsulation (the
> top of the stack is the most recent function):
>
> 0x3451230:_fr_encaps(0x303932c+0x417de6)+0x11e
> 0x3450FB4:_fr_vencapsulate(0x303932c+0x417c6e)+0x1a
> 0x30F4892:_pak_encap(0x303932c+0xbb542)+0x24
> 0x363A7E4:_lat_pakout(0x303932c+0x601468)+0x50
> 0x363A986:_of_message(0x303932c+0x60153c)+0x11e
> 0x364524C:_toc_elapse(0x303932c+0x60be74)+0xac
> 0x363AB10:_lat_timer(0x303932c+0x601720)+0xc4
>
> I'll try to see if I can find anything if I have some spare time today (I
> test in less than three weeks... going nuts).
>
> Brian
>
> On Thu, 8 Jun 2000, Wang, Kai wrote:
>
> > I removed the mac-address command. I am still getting the same error
> > message.
> >
> > %LINK-3-BADMACREG: Interface Serial1, non-existent MACADDR registry for
link
> > 31
> > -Process= "LAT Timers", ipl= 0, pid= 1
> > -Traceback= 3451230 3450FB4 30F4892 363A7E4 363A986 364524C 363AB10
> >
> > -----Original Message-----
> > From: Brian Hescock [mailto:bhescock@cisco.com]
> > Sent: Thursday, June 08, 2000 11:44 AM
> > To: Wang, Kai
> > Cc: 'ccielab@groupstudy.com'
> > Subject: Re: LAT over F/R
> >
> >
> > Take off the mac-address command, the ios reference book indicates it's
> > only used for token ring interfaces. I'm somewhat surprised you could
> > configure it on a serial interface if it can only be used on token
> > ring. I checked the lat configuration guide and there isn't anything in
> > there about having to change the mac-address. The first error
> > "BADMACREG" is probably related to the fact you tried changing the mac
> > address. The second error is a traceback related to LAT Timers. The
> > first error could have possibly caused the second error in the IOS code.
> >
> > Brian
> >
> > On Thu, 8 Jun 2000, Wang, Kai wrote:
> >
> > > I am trying to configure LAT over F/R without using the protocol
> > > translation. I am unable to get it to work.
> > >
> > > The configs are shown as follows:
> > >
> > > R4 config
> > > !
> > > interface Serial1
> > > mac-address 0004.0004.0004
> > > no ip address
> > > encapsulation frame-relay
> > > lat enabled
> > > !
> > > lat service TEST enabled
> > >
> > > R3 config
> > > !
> > > interface Serial0
> > > mac-address 0003.0003.0003
> > > no ip address
> > > encapsulation frame-relay
> > > lat enabled
> > > no fair-queue
> > >
> > > I am getting the following error message from my router:
> > >
> > > %LINK-3-BADMACREG: Interface Serial1, non-existent MACADDR registry
for
> > link
> > > 31
> > > -Process= "LAT Timers", ipl= 0, pid= 29
> > > -Traceback= 3451230 3450FB4 30F4892 363A7E4 363A986 364524C 363AB10
> > >
> > > What should I do to get it to work?
> > >
> > > Thank You!
> > >
> > > Kai Wang
> > > EDS - AHSMC/Network Operation
> > > MS 3010
> > > 300 East Big Beaver
> > > Troy, MI 48083
> > >
> > >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:23:42 GMT-3