Oh, AppleTalk, my favorite subject! ;-) See comments inline: Harold Monroe wrote: > > 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.
The packets won't show you zone names unless you have one of the Macs pull up the Chooser or whatever it's called on recent Mac OSs. The zones are only relevant during "resource discovery." But the packets should definitely tell you the network number(s). Just like an IP packet has source and destination network-layer IP addresses, an AppleTalk packet has source and destination DDP addresses. For AppleTalk, look for source and destination network, node, socket. My first thought was that maybe you aren't seeing DDP addresses because the Macs are using the Apple Filing Protocol application-layer protocol on top of TCP/IP. But that doesn't use ATP. It uses a new protocol called Data Stream Interface (DSI) which runs above TCP. More comments below..... 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. Macs used to be able to act as routers by running Apple's Internet Router software (which did AppleTalk, not IP!) But that hasn't been updated in years. Only a device that's acting as a router can define network number(s) and zone names and act as a seed router. > > 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 This probably won't work, as you have discovered, because there probably isn't another router out there. > > #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 If a device decides that its network number is in the 65,280-65,534 range, it means the device kept a network number from the startup range because it never got a response to its ZIPGetNetInfo packet to find a router. More evidence that there is no router on your network. By the way, can you do an AppleTalk ping? You have an address so theoretically you should be able to ping the devices in your AARP table, but it might not work since it says "AppleTalk port disabled." > 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 > > Yes, this is consistent with there being no router. All the devices have chosen network numbers in the startup range. It's OK that their network numbers don't match. That still works. So, this is good news actually. You wouldn't want to configure a new router in the situation where you don't know the network number and zone names. Well, you could use discovery mode, I guess and then you would be OK hopefully. So, the bottom line (finally! ;-) is that you should assign a cable range and zone name. Be careful, though. Although the Macintoshes shouldn't have a problem with this change as the protocols do deal with a router coming up after the clients, it could get ugly nontheless. Is this a mission-critical network? Probably not or it wouldn't still be AppleTalk!? There's much more info on this and other CIT topics in my new book, Troubleshooting Campus Networks, by the way. ;-) Good luck! Priscilla Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=51430&t=51406 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
