From: Mark, Detrick (mdetrick@xxxxxxxxx)
Date: Thu Aug 19 1999 - 19:07:24 GMT-3
Thanks for the reply.
Yes, the interface was communicating IP so it must have been up physically.
As far as the apple int being up, an apple interface that does not see any
other apple out on its segment will still come up after a period of time.
It will time out looking for its node number and consider its number safe
when it does not hear back from its AARP. It takes longer than bringing up
apple nodes on a segment that already has an active node on it. This is my
experience.
Important to note...
1. (most likey) I got this wrong because I didn't know it.
2. Its not possible and we were not supposed to setup Apple on this
interface, eventhough, it was not on the list of don't configure AT on these
interfaces.
Has anybody actually configured AT over ATM?
Mark Detrick
----- Original Message -----
From: John Galt Kupec <jkupec2@san.rr.com>
To: Mark S. Detrick <mark@detrick.com>
Cc: <ccielab@groupstudy.com>
Sent: Thursday, August 19, 1999 6:32 AM
Subject: Re: Appletalk on an ATM Interface
>
>
> "Mark S. Detrick" wrote:
> >
> > I have a 3640 with an ATM interface. I have apple routing turned on and
on
> > the interface I have apple cable-range 1-1 and apple zone ATM. Then I
do sh
> > apple route. I should see the connected interfaces, I see all EXCEPT
the
> > ATM interface.
> >
> > Why won't AT show up as connected route for an ATM interface? What am I
> > missing?
>
> Is your ATM interface connected to anything? Typically, AT won't show a
> route if the interface hasn't talked with another AT interface on the
> same network.
>
> "show apple int" might report something like:
>
> AppleTalk address is 1.94, Invalid
>
> HTH
>
> --
> John Galt Kupec CCIE #4837
> jkupec@ccci.com http://www.ccci.com
> ----------------------------------------------------------------------
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:21:47 GMT-3