System information

Troubleshooting AppleTalk 9-189
AppleTalk: Users Cannot Access Zones or Services
AppleTalk Configuration Mismatches
A configuration mismatch occurs if all the AppleTalk routers on a given cable do not agree on the
configuration of that cable. This means that all routers must have matching network numbers, a
matching default zone, and a matching zone list.
To protect against configuration errors that violate this rule, Cisco AppleTalk routers block activation
of any port on which a violation of this rule exists. At interface initialization, if other routers on the
network do not agree with the way a router is configured, the router does not allow AppleTalk to
become operational on that interface. Cisco routers attempt to restart such an interface every
two minutes to avoid outages that result from transient conditions.
However, if the router is already operational and another router whose configuration does not match
becomes active, the router continues to operate on that interface until the interface is reset. At that
point, the interface fails to become active. When the show appletalk interface exec command is
issued, the router indicates a port configuration mismatch.
Phase 1 and Phase 2
rule violations
Step 1 Use the show appletalk globals exec command to determine whether the
internetwork is in compatibility mode.
Step 2 Enable the appletalk name-lookup-interval global configuration command
and use the show appletalk neighbors exec command to determine which
specific neighbor (by NBP
1
name) is in compatibility mode.
Step 3 To resolve the problem, you can perform one of the following actions:
• Upgrade AppleTalk Phase 1 routers to AppleTalk Phase 2 and reconfigure
the internetwork
• Ensure that all routers are in compliance with the two Phase 1 and Phase 2
rules
For more information on Phase 1 and Phase 2 rule violations, see the section “Phase 1
and Phase 2 Rule Violations” later in this chapter.
Misconfigured access
lists or other filters
Step 1 Use the show appletalk access-list exec command on routers in the path
from source to destination.
Step 2 Disable any access lists (or just those on a particularly suspect router) using
the no appletalk access-group interface configuration command. If there
are distribution lists or other filters configured, disable them.
Step 3 After disabling access lists, check whether remote zones and services
become accessible.
Step 4 If zones and services are now available, a misconfigured access list is the
likely problem. To isolate the problem access list, enable lists one at a time
until connectivity fails.
Step 5 Check the access lists and associated configuration commands for errors.
Configure explicit permit statements for traffic that you want to pass
through the router normally.
Step 6 If problems persist, there might be more than one misconfigured access list.
Continue enabling access lists one at a time and fixing misconfigured access
lists until the problem is solved.
1 NBP = Name Binding Protocol
Possible Problems Solution