I'll try this from memory. The concept of a "seed router" was to eliminate
configuration mistakes. Config one router and let the others learn from it.
Sounds nice but isn't necessary. Might be useful in a backbone with scores
or routers hanging off one wire.

AppleTalk Phase 1 is long obsolete so Phase 2 is expected.
Configure a cable range. Each network number is equal to about 250 hosts. So
a range of 23-23 would be one network. 23-24 would double that ... etc.
Remember that Macs choose their node address and then advertise it to see if
anyone else is using it. If it is being used, they pick a new address. Best
to have quite a few more addresses than computers. Less time is wasted in
booting. (A Mac will attempt to reuse the last address it had.)
The router interface also picks an address unless hard coded.
appletalk cable-range 23-24 23.1 gives you about 500 nodes and sets the
interface address. It's useful to pick an addressing scheme that follows
your ip addressing scheme.

You must specify appletalk zones. If you only configure one zone the Mac's
Chooser doesn't display it. Why bother when there's only one. So I often
configure two zones. The Mac will use the first as it's default zone unless
told otherwise. Case sensitive.
appletalk zone testzone1
appletalk zone testzone2
I've never used the appletalk discovery command. Is it used to find a config
from the seed router?

HTH

> -----Original Message-----
> From: Harold Monroe [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, August 14, 2002 5:41 PM
> To: [EMAIL PROTECTED]
> Subject: Setting up Appletalk on router for CIT [7:51406]
> 
> 
> I'm getting ready for my CIT test for CCNP. I've heard there 
> may be some
> Appletalk on the test. I'm trying to experiment with the 
> Appletalk show &
> debug commands. Since this is the first time I've even seen 
> Appletalk I
> can't seem to get it to work.
> 
> The department with the Macs doesn't know anything about 
> their settings so
> I've tried using a packet sniffer/protocol analyzer. The 
> analyzer sees ATP
> and Appletalk phase 2, but doesn't give any information about 
> the cable
> range, nor zone. I set the appletalk cable-range 0-0 (as 
> mentioned on CCO).
> CCO says you need a seed router, but unless one of the Macs 
> is supplying
> that service we don't have one.
> 
> Although the FastEthernet interface is up/up and AARP is 
> working none of the
> show appletalk commands like show appletalk zone, traffic, 
> globals, nor
> debug appletalk display any information. I do have "appletalk 
> routing" in my
> config
> 
> #sh run
> 
> appletalk routing
> interface FastEthernet0/1
>  ip address 192.168.1.10 255.255.255.0
>  no ip directed-broadcast
>  appletalk cable-range 0-0 65347.122
>  appletalk discovery
> 
> #sh ap int f0/1
> 
> FastEthernet0/1 is up, line protocol is up
>   AppleTalk port disabled, Acquiring port net information
>   AppleTalk cable range is not known.
>   AppleTalk address is 65347.122, Valid
>   AppleTalk zone is not set.
>   AppleTalk discovery mode is enabled
>   AppleTalk address gleaning is disabled
>   AppleTalk route cache is not initialized
> 
> AARP is working
> #sh apple arp
> 4.4                  1  Dynamic   0030.65c8.5cc8.0000  SNAP
> FastEthernet0/1
> 5.5                  1  Dynamic   0030.65d2.c17c.0000  SNAP
> FastEthernet0/1
> 6.3                  0  Dynamic   0030.6583.da6c.0000  SNAP
> FastEthernet0/1
> 65281.11            15  Dynamic   0010.83f5.32cb.0000  SNAP
> FastEthernet0/1
> 65319.82            27  Dynamic   00c0.7587.3cc7.0000  SNAP
> FastEthernet0/1
> 65347.122            -  Hardware  0030.1946.1f21.0000  SNAP
> FastEthernet0/1
> 65406.137            0  Dynamic   0030.65ca.ef78.0000  SNAP
> FastEthernet0/1
> 65507.224          161  Dynamic   00c0.755e.c59d.0000  SNAP
> FastEthernet0/1




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=51420&t=51406
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to