From: Tony Olzak (aolzak@xxxxxxxxxxxxxxxxxxx)
Date: Mon Dec 11 2000 - 17:46:23 GMT-3
When I configured it myself the original way, the interface didn't go down
either, but I couldn't ping. Guess it's just another example where appletalk
needs to have the router reload.
Tony
----- Original Message -----
From: "Justin Menga" <Justin.Menga@computerland.co.nz>
To: "'Tony Olzak'" <aolzak@buckeye-express.com>; "Justin Menga"
<Justin.Menga@computerland.co.nz>; <ccielab@groupstudy.com>
Sent: Monday, December 11, 2000 2:51 PM
Subject: RE: Appletalk on Serial Interfaces
> Hi,
>
> With the 'no appletalk send-rtmps', the serial interface does NOT go
down -
> I have tested this over HDLC, PPP and Frame - no routes are exchanged but
> you can still ping each other......
>
> The tunnel interface is a creative solution - but - would this be allowed
in
> the actual lab if the goal was to configure appletalk for each interface
on
> a router and advertise them?
>
> Regards,
>
> Justin Menga MCSE+I CCNP CCSE ASE
> WAN Specialist
> Computerland New Zealand
> PO Box 3631, Auckland
> DDI: (+64) 9 360 4864 Mobile: (+64) 25 349 599
> mailto: justin.menga@computerland.co.nz
>
>
> -----Original Message-----
> From: Tony Olzak [mailto:aolzak@buckeye-express.com]
> Sent: Monday, 11 December 2000 2:54 p.m.
> To: Justin Menga; ccielab@groupstudy.com
> Subject: Re: Appletalk on Serial Interfaces
>
>
> I finally figured out the answer to this scenario.
>
> R1------R2--------R3--Ethernet
>
> If R3 has an Ethernet segment that you do not want advertised to the rest
of
> the network, but you can't use filtering, most people say to use "no apple
> send-rtmps".
>
> The problem with this command on a serial interface is that the interface
> will go down in appletalk and then you won't be able to apple ping the
rest
> of the network.
>
> The solution is to create a GRE tunnel between R2 and R3 and only
configure
> appletalk on this interface, not the serial interface. Then use the
command
> "no apple send-rtmps" on the tunnel interface on R3. This will not bring
> down the appletalk protocol and it will not send any RTMP updates about
the
> ethernet segment attached to the router.
>
>
> Tony
>
> ----- Original Message -----
> From: "Justin Menga" <Justin.Menga@computerland.co.nz>
> To: <ccielab@groupstudy.com>
> Sent: Sunday, December 10, 2000 12:44 AM
> Subject: Appletalk on Serial Interfaces
>
>
> > Hi,
> >
> > If you have for example a frame-relay cloud with an attached router that
> is
> > configured for Appletalk, and all other attached routers are NOT
> configured
> > for Appletalk, I have found that this serial appletalk interface will
not
> > come up and therefore not be in the routing table.
> >
> > Does anyone know how to force the serial interface up? If you have
> > appletalk running on an Ethernet interface, this will come up even if it
> is
> > the only
> > appletalk device.
> >
> > I have tried using the appletalk ignore-verify-errors command, but this
> does
> > not work.
> >
> > Regards,
> >
> > Justin Menga MCSE+I CCNP CCSE ASE
> > WAN Specialist
> > Computerland New Zealand
> > PO Box 3631, Auckland
> > DDI: (+64) 9 360 4864 Mobile: (+64) 25 349 599
> > mailto: justin.menga@computerland.co.nz
> >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:26:01 GMT-3