Table Of Contents
appletalk ignore-verify-errors
appletalk name-lookup-interval
appletalk permit-partial-zones
appletalk route-redistribution
appletalk strict-rtmp-checking
appletalk event-logging
To log significant network events, use the appletalk event-logging command in global configuration mode. To disable this function, use the no form of this command.
appletalk event-logging
no appletalk event-logging
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
The appletalk event-logging command logs a subset of messages produced by debug appletalk command. These messages include routing changes, zone creation, port status, and address.
Examples
The following example enables logging of AppleTalk events:
appletalk routingappletalk event-loggingRelated Commands
appletalk free-trade-zone
To establish a free-trade zone, use the appletalk free-trade-zone command in interface configuration mode. To disable a free-trade zone, use the no form of this command.
appletalk free-trade-zone
no appletalk free-trade-zone
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
A free-trade zone is a part of an AppleTalk internetwork that is accessible by two other parts of the internetwork, neither of which can access the other. You might want to create a free-trade zone to allow the exchange of information between two organizations that otherwise want to keep their internetworks isolated from each other or that do not have physical connectivity with one another.
You apply the appletalk free-trade-zone command to each interface attached to the common-access network. This command has the following effect on the interface:
•
All incoming RTMP updates are ignored.
•
•
The GZL for free-trade zone nodes will be empty.
Examples
The following example establishes a free-trade zone on Ethernet interface 0:
interface ethernet 0appletalk cable-range 5-5appletalk zone FreeAccessZoneappletalk free-trade-zoneappletalk getzonelist-filter
To filter GetZoneList (GZL) replies, use the appletalk getzonelist-filter command in interface configuration mode. To remove a filter, use the no form of this command.
appletalk getzonelist-filter access-list-number
no appletalk getzonelist-filter [access-list-number]
Syntax Description
Defaults
No filters are preconfigured.
Command Modes
Interface configuration
Command History
Usage Guidelines
GZL filters define conditions for zones only. They cannot use access lists that define conditions for network numbers or cable ranges. All network number and cable range information in the access list assigned to an interface with the appletalk getzonelist-filter command is ignored.
Using a GZL filter is not a complete replacement for anonymous network numbers. In order to prevent users from seeing a zone, all routers must implement the GZL filter. If there are any routers from other vendors on the network, the GZL filter will not have a consistent effect.
The Macintosh Chooser uses ZIP GZL requests to compile a list of zones from which the user can select services. Any router on the same network as the Macintosh can respond to these requests with a GZL reply. You can create a GZL filter on the router to control which zones the router mentions in its GZL replies. This has the effect of controlling the list of zones that are displayed by the Chooser.
When defining GZL filters, you should ensure that all routers on the same network filter GZL reply identically. Otherwise, the Chooser will list different zones depending upon which router responded to the request. Also, inconsistent filters can result in zones appearing and disappearing every few seconds when the user remains in the Chooser. Because of these inconsistencies, you should normally use the appletalk getzonelist-filter command only when all routers in the internetwork are our routers, unless the routers from other vendors have a similar feature.
Replies to GZL requests are also filtered by any appletalk distribute-list out filter that has been applied to the same interface. You must specify an appletalk getzonelist-filter command only if you want additional filtering to be applied to GZL replies. This filter is rarely needed except to eliminate zones that do not contain user services.
Examples
The following example does not include the zone Engineering in GZL replies sent out Ethernet interface 0:
access-list 600 deny zone Engineeringinterface ethernet 0appletalk getzonelist-filter 600Related Commands
appletalk glean-packets
To derive AppleTalk Address Resolution Protocol (AARP) table entries from incoming packets, use the appletalk glean-packets command in interface configuration mode. To disable this function, use the no form of this command.
appletalk glean-packets
no appletalk glean-packets
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled
Command Modes
Interface configuration
Command History
Usage Guidelines
The Cisco IOS software automatically derives AARP table entries from incoming packets. This process, referred to as gleaning, speeds up the process of populating the AARP table.
Our implementation of AppleTalk does not forward packets with local source and destination network addresses. This behavior does not conform with the definition of AppleTalk in Apple Computer's Inside AppleTalk publication. However, this behavior is designed to prevent any possible corruption of the AARP table in any AppleTalk node that is performing MAC-address gleaning.
Examples
The following example disables the building of the AARP table using information derived from incoming packets:
interface ethernet 0appletalk address 33no appletalk glean-packetsappletalk ignore-verify-errors
To allow the Cisco IOS software to start functioning even if the network is misconfigured, use the appletalk ignore-verify-errors command in global configuration mode. To disable this function, use the no form of this command.
appletalk ignore-verify-errors
no appletalk ignore-verify-errors
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command only under the guidance of a customer engineer or other service representative. A router that starts routing in a misconfigured network will serve only to make a bad situation worse; it will not correct other misconfigured routers.
Examples
The following example allows a router to start functioning without verifying network misconfiguration:
appletalk ignore-verify-errorsappletalk iptalk
To enable IPTalk encapsulation on a tunnel interface, use the appletalk iptalk command in interface configuration mode. To disable IPTalk encapsulation, use the no form of this command.
appletalk iptalk network zone
no appletalk iptalk [network zone]
Syntax Description
network
AppleTalk network address assigned to the interface. The argument network is the 16-bit network number in decimal.
zone
Name of the zone for the connected AppleTalk network.
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
Use the appletalk iptalk command to enable IPTalk encapsulation on a tunnel interface. This command encapsulates AppleTalk in IP packets in a manner compatible with the Columbia AppleTalk Package (CAP) IPTalk and the Kinetics IPTalk implementations. IPTalk is configured on a tunnel interface.
This command allows AppleTalk communication with UNIX hosts running older versions of CAP that do not support native AppleTalk EtherTalk encapsulations. Typically, Apple Macintosh users wishing to communicate with these servers would have their connections routed through a Kinetics FastPath router running Kinetics IPTalk software.
This command is provided as a migration command; newer versions of CAP provide native AppleTalk EtherTalk encapsulations, and the IPTalk encapsulation is no longer required. Our implementation of IPTalk assumes that AppleTalk is already being routed on the backbone; there is currently no LocalTalk hardware interface for our routers.
Our implementation of IPTalk does not support manually configured AppleTalk-to-IP address mapping (atab). The address mapping provided is the same as the Kinetics IPTalk implementation when the atab facility is not enabled. This address mapping functions as follows: The IP subnet mask used on the Ethernet interface on which IPTalk is enabled is inverted (ones complement). This result is then masked against 255 (0xFF hexadecimal). This is then masked against the low-order 8 bits of the IP address to obtain the AppleTalk node number.
Examples
The following example configuration illustrates how to configure IPTalk:
interface Ethernet0ip address 172.31.255.118 255.255.255.0interface Tunnel0tunnel source Ethernet0tunnel mode iptalkappletalk iptalk 30 UDPZoneIn this configuration, the IP subnet mask would be inverted:
255.255.255.0 inverted yields: 0.0.0.255Masked with 255 it yields 255, and masked with the low-order 8 bits of the interface IP address it yields 118.
This means that the AppleTalk address of the Ethernet 0 interface seen in the UDPZone zone is 30.118. This caveat should be noted, however: Should the host field of an IP subnet mask for an interface be more than 8 bits wide, it will be possible to obtain conflicting AppleTalk node numbers. For instance, consider a situation where the subnet mask for the Ethernet 0 interface above is 255.255.240.0, meaning that the host field is 12 bits wide.
Related Commands
appletalk iptalk-baseport
To specify the User Datagram Protocol (UDP) port number when configuring IPTalk, use the appletalk iptalk-baseport command in global configuration mode. To return to the default UDP port number, use the no form of this command.
appletalk iptalk-baseport port-number
no appletalk iptalk-baseport [port-number]
Syntax Description
port-number
First UDP port number in the range of UDP ports used in mapping AppleTalk well-known Datagram Delivery Protocol (DDP) socket numbers to UDP ports.
Defaults
768
Command Modes
Global configuration
Command History
Usage Guidelines
Implementations of IPTalk prior to April 1988 mapped well-known DDP socket numbers to privileged UDP ports starting at port number 768. In April 1988, the Network Information Center (NIC) assigned a range of UDP ports for the defined DDP well-known sockets starting at UDP port number 200 and assigned these ports the names at-nbp, at-rtmp, at-echo, and at-zis. Release 6 and later of the CAP program dynamically decides which port mapping to use. If there are no AppleTalk service entries in the UNIX system's /etc/services file, CAP uses the older mapping starting at UDP port number 768.
The default UDP port mapping supported by our implementation of IPTalk is 768. If there are AppleTalk service entries in the UNIX system's /etc/services file, you should specify the beginning of the UDP port mapping range with the appletalk iptalk-baseport command.
Examples
The following example sets the base UDP port number to 200, which is the official NIC port number, and configures IPTalk on Ethernet interface 0:
appletalk routingappletalk iptalk-baseport 200!interface Ethernet 0ip address 172.31.255.118 255.255.255.0appletalk address 20.129appletalk zone Native AppleTalkappletalk iptalk 30.0 UDPZoneRelated Commands
appletalk lookup-type
To specify which Name Binding Protocol (NBP) service types are retained in the name cache, use the appletalk lookup-type command in global configuration mode. To disable the caching of services, use the no form of this command.
appletalk lookup-type service-type
no appletalk lookup-type service-type
Syntax Description
service-type
AppleTalk service types. The name of a service type can include special characters from the Apple Macintosh character set. To include a special character, type a colon followed by two hexadecimal numbers. For zone names with a leading space character, enter the first character as the special sequence :20. For a list of possible types, see Table 3 in the "Usage Guidelines" section.
Defaults
The entries from active adjacent Cisco routers are retained in the name cache.
Command Modes
Global configuration
Command History
Usage Guidelines
You can issue multiple appletalk lookup-type commands. The Cisco IOS software does not query the entire zone, but instead polls only the connected networks. This reduces network overhead and means that the name cache contains entries only for selected services that are in a directly connected network or zone, not for all the selected services in a network or zone.
Table 3 lists some AppleTalk service types.
Table 3 AppleTalk Service Types
ciscoRouter
Active adjacent Cisco routers. This service type is initially enabled by default.
IPADDRESS
Addresses of active MacIP server.
IPGATEWAY
Names of active MacIP server.
SNMP Agent
Active SNMP agents in Cisco routers.
AppleRouter
Apple internetwork router.
FastPath
Shiva LocalTalk gateway.
GatorBox
Cayman LocalTalk gateway.
systemRouter
Cisco's OEM router name.
Workstation
Macintosh running System 7. The machine type also is defined, so it is possible to easily identify all user nodes.
1 Type all service names exactly as shown. Spaces are valid. Do not use leading or trailing spaces when entering service names.
If you omit the service-type argument from the no appletalk lookup-type command, no service types except those relating to our devices are cached.
To display information that is stored in the name cache about the services being used by our routers and other vendors' routers, use the show appletalk name-cache command.
If a neighboring router is not our device or is running our software that is earlier than Release 9.0, it is possible our device will be unable to determine the name of the neighbor. This is normal behavior, and there is no workaround.
If AppleTalk routing is enabled, enabling Simple Network Management Protocol (SNMP) will automatically enable SNMP over DDP.
Name cache entries are deleted after several interval periods expire without being refreshed. (You set the interval with the appletalk name-lookup-interval command.) At each interval, a single request is sent via each interface that has valid addresses.
Examples
The following example caches information about GatorBox services, Apple internetwork routers, MacIP services, and workstations. Information about our devices is automatically cached.
appletalk lookup-type GatorBoxappletalk lookup-type AppleRouterappletalk lookup-type IPGATEWAYappletalk lookup-type WorkstationRelated Commands
appletalk macip dynamic
To allocate IP addresses to dynamic MacIP clients, use the appletalk macip dynamic command in global configuration mode. To delete a MacIP dynamic address assignment, use the no form of this command.
appletalk macip dynamic ip-address [ip-address] zone server-zone
no appletalk macip dynamic ip-address [ip-address] zone server-zone
Syntax Description
Defaults
No IP addresses are allocated.
Command Modes
Global configuration
Command History
Usage Guidelines
Use the appletalk macip dynamic command when configuring MacIP.
Dynamic clients are those that accept any IP address assignment within the dynamic range specified.
In general, it is recommended that you do not use fragmented address ranges in configuring ranges for MacIP. However, if this is unavoidable, use the appletalk macip dynamic command to specify as many addresses or ranges as required and use the appletalk macip static command to assign a specific address or address range.
To shut down all running MacIP services, use the following command:
no appletalk macip
To delete a particular dynamic address assignment from the configuration, use the following command:
no appletalk macip dynamic ip-address [ip-address] zone server-zone
Examples
The following example illustrates MacIP support for dynamically addressed MacIP clients with IP addresses in the range 172.16.1.28 to 172.16.1.44:
! This global statement specifies the MacIP server address and zone:appletalk macip server 172.16.1.27 zone Engineering!! This global statement identifies the dynamically addressed clients:appletalk macip dynamic 172.16.1.28 172.16.1.44 zone Engineering!! These statements assign the IP address and subnet mask for Ethernet interface 0:interface ethernet 0ip address 172.16.1.27 255.255.255.0!! This global statement enables AppleTalk routing on the router.appletalk routing!! These statements enable AppleTalk routing on the interface and! set the zone name for the interfaceinterface ethernet 0appletalk cable-range 69-69 69.128appletalk zone EngineeringRelated Commands
appletalk macip server
To establish a MacIP server for a zone, use the appletalk macip server command in global configuration mode. To shut down a MacIP server, use the no form of this command.
appletalk macip server ip-address zone server-zone
no appletalk macip server ip-address zone server-zone
Syntax Description
Defaults
No MacIP server is established.
Command Modes
Global configuration
Command History
Usage Guidelines
Use the appletalk macip server command when configuring MacIP.
You can configure only one MacIP server per AppleTalk zone, and the server must reside in the default zone. A server is not registered via NBP until at least one MacIP resource is configured.
You can configure multiple MacIP servers for a router, but you can assign only one MacIP server to a particular zone and only one IP interface to each MacIP server. In general, you must be able to establish an alias between the IP address you assign with the appletalk macip server command and an existing IP interface. For implementation simplicity, it is suggested that the address specified in this command match an existing IP interface address.
To shut down all active MacIP servers, use the following command:
no appletalk macip
To delete a specific MacIP server from the MacIP configuration, use the following command:
no appletalk macip server ip-address zone server-zone
Examples
The following example establishes a MacIP server on Ethernet interface 0 in AppleTalk zone Engineering. It then assigns an IP address to the Ethernet interface and enables AppleTalk routing on a router and its Ethernet interface.
appletalk macip server 172.19.1.27 zone Engineeringip address 172.19.1.27 255.255.255.0appletalk routinginterface ethernet 0appletalk cable-range 69-69 69.128appletalk zone EngineeringRelated Commands
appletalk macip static
To allocate an IP address to be used by a MacIP client that has reserved a static IP address, use the appletalk macip static command in global configuration mode. To delete a MacIP static address assignment, use the no form of this command.
appletalk macip static ip-address [ip-address] zone server-zone
no appletalk macip static ip-address [ip-address] zone server-zone
Syntax Description
Defaults
No IP address is allocated.
Command Modes
Global configuration
Command History
Usage Guidelines
Use the appletalk macip static command when configuring MacIP.
Static addresses are for users who require fixed addresses for IP name domain name service and for administrators who do want addresses to change so they can always know who has what IP address.
In general, it is recommended that you do not use fragmented address ranges in configuring ranges for MacIP. However, if this is unavoidable, use the appletalk macip dynamic command to specify as many addresses or ranges as required, and then use the appletalk macip static command to assign a specific address or address range.
To shut down all running MacIP services, use the following command:
no appletalk macip
To delete a particular static address assignment from the configuration, use the following command:
no appletalk macip static ip-address [ip-address] zone server-zone
Examples
The following example illustrates MacIP support for MacIP clients with statically allocated IP addresses. The IP addresses range is from 172.31.1.50 to 172.31.1.66. The three nodes that have the specific addresses are 172.31.1.81, 172.31.1.92, and 172.31.1.101.
! This global statement specifies the MacIP server address and zone:appletalk macip server 172.31.1.27 zone Engineering!! These global statements identify the statically addressed clients:appletalk macip static 172.31.1.50 172.31.1.66 zone Engineeringappletalk macip static 172.31.1.81 zone Engineeringappletalk macip static 172.31.1.92 zone Engineeringappletalk macip static 172.31.1.101 zone Engineering!! These statements assign the IP address and subnet mask for Ethernet interface 0:interface ethernet 0ip address 172.31.1.27 255.255.255.0!! This global statement enables AppleTalk routing on the router.appletalk routing!! These statements enable AppleTalk routing on the interface and! set the zone name for the interfaceinterface ethernet 0appletalk cable-range 69-69 69.128appletalk zone EngineeringRelated Commands
appletalk maximum-paths
To define the maximum number of equal-cost paths that the router should use when balancing the traffic load, use the appletalk maximum-paths command in global configuration mode. To restore the default value, use the no form of this command.
appletalk maximum-paths [paths]
no appletalk maximum-paths [paths]
Syntax Description
paths
(Optional) Maximum number of equal-cost paths to be used for balancing the traffic load. The paths argument is a decimal number in the range of 1 to 16.
Defaults
The default value is 1.
Command Modes
Global configuration
Command History
Usage Guidelines
Use the appletalk maximum-paths command when configuring AppleTalk load balancing.
The appletalk maximum-paths command increases throughput by allowing the software to choose among several equal-cost, parallel paths. (Note that when paths have differing costs, the software chooses lower-cost routes in preference to higher-cost routes.)
When the value of paths is greater than 1, packets are distributed over the multiple equal-cost paths in round-robin fashion on a packet-by-packet basis.
Examples
The following example defines four equal-cost paths:
! Sets the maximum number of equal-cost paths to 4.appletalk maximum-paths 4The following example restores the default value:
! Restores the default value.no appletalk maximum-paths 4appletalk name-lookup-interval
To set the interval between service pollings by the router on its AppleTalk interfaces, use the appletalk name-lookup-interval command in global configuration mode. To purge the name cache and return to the default polling interval, use the no form of this command.
appletalk name-lookup-interval seconds
no appletalk name-lookup-interval [seconds]
Syntax Description
seconds
Interval, in seconds, between NBP lookup pollings. This can be any positive integer; there is no upper limit. It is recommended that you use an interval between 300 seconds (5 minutes) and 1200 seconds (20 minutes). The smaller the interval, the more packets are generated to handle the names. Specifying an interval of 0 purges all entries from the name cache and disables the caching of service type information that is controlled by the appletalk lookup-type command, including the caching of information about our routers.
Defaults
The default is 0, which purges all entries from the name cache and disables the caching of service type information.
Command Modes
Global configuration
Command History
Usage Guidelines
The Cisco IOS software collects name information only for entities on connected AppleTalk networks. This reduces overhead.
If you enter an interval of 0, all polling for services (except ciscoRouter) is disabled. If you reenter a nonzero value, the configuration specified by the appletalk lookup-type command is reinstated. You cannot disable the lookup of ciscoRouter.
Examples
The following example sets the lookup interval to 20 minutes:
appletalk name-lookup-interval 1200Related Commands
appletalk permit-partial-zones
To permit access to the other networks in a zone when access to one of those networks is denied, use the appletalk permit-partial-zones command in global configuration mode. To deny access to all networks in a zone if access to one of those networks is denied, use the no form of this command.
appletalk permit-partial-zones
no appletalk permit-partial-zones
Syntax Description
This command has no arguments or keywords.
Defaults
Access is denied.
Command Modes
Global configuration
Command History
Usage Guidelines
The permitting of partial zones provides IP-style access control.
When you enable the use of partial zones, the NBP protocol cannot ensure the consistency and uniqueness of name bindings.
If you enable the use of partial zones, access control behavior is compatible with that of Cisco IOS Release 8.3.
Examples
The following example allows partial zones:
appletalk permit-partial-zonesRelated Commands
appletalk pre-fdditalk
To enable the recognition of pre-FDDITalk packets, use the appletalk pre-fdditalk command in global configuration mode. To disable this function, use the no form of this command.
appletalk pre-fdditalk
no appletalk pre-fdditalk
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command to have the Cisco IOS software recognize AppleTalk packets sent on the FDDI ring from routers that are running Cisco software releases prior to Release 9.0(3) or Release 9.1(2).
Examples
The following example disables the recognition of pre-FDDITalk packets:
no appletalk pre-fdditalkappletalk protocol
To specify the routing protocol to use on an interface, use the appletalk protocol command in interface configuration mode. To disable a routing protocol, use the no form of this command.
appletalk protocol {aurp | eigrp | rtmp}
no appletalk protocol {aurp | eigrp | rtmp}
Syntax Description
Defaults
RTMP
Command Modes
Interface configuration
Command History
Usage Guidelines
You can configure an interface to use both RTMP and Enhanced IGRP. If you do so, route information learned from Enhanced IGRP will take precedence over information learned from RTMP. The Cisco IOS software will, however, continue to send out RTMP routing updates.
You cannot disable RTMP without first enabling AURP or Enhanced IGRP.
Enabling AURP automatically disables RTMP.
You can enable AURP only on tunnel interfaces.
Examples
The following example enables AURP on tunnel interface 1:
interface tunnel 1appletalk protocol aurpThe following example enables AppleTalk Enhanced IGRP on serial interface 0:
interface serial 0appletalk protocol eigrpThe following example disables RTMP on serial interface 0:
interface serial 0no appletalk protocol rtmpRelated Commands
appletalk proxy-nbp
To assign a proxy network number for each zone in which there is a router that supports only nonextended AppleTalk, use the appletalk proxy-nbp command in global configuration mode. To delete the proxy, use the no form of this command.
appletalk proxy-nbp network-number zone-name
no appletalk proxy-nbp [network-number zone-name]
Syntax Description
Defaults
No proxy network number is assigned.
Command Modes
Global configuration
Command History
Usage Guidelines
The appletalk proxy-nbp command provides compatibility between AppleTalk Phase 1 and AppleTalk Phase 2 networks.
Proxy routes are included in outgoing RTMP updates as if they were directly connected routes, although they are not really directly connected, since they are not associated with any interface. Whenever an NBQ BrRq for the zone in question is generated by anyone anywhere in the internetwork, an NBP FwdReq is directed to any router connected to the proxy route. The Phase 2 router, which is the only router directly connected, converts the FwdReq to LkUps, which are understood by Phase 1 routers, and sends them to every network in the zone.
In an environment in which there are Phase 1 and Phase 2 networks, you must specify at least one appletalk proxy-nbp command for each zone that has a nonextended-only AppleTalk router.
The proxy network number you assign with the appletalk proxy-nbp command cannot also be assigned to a router, nor can it also be associated with a physical network.
You must assign only one proxy network number for each zone. However, you can define additional proxies with different network numbers to provide redundancy. Each proxy generates one or more packets for each forward request it receives. All other packets sent to the proxy network address are discarded. Defining redundant proxy network numbers increases the NBP traffic linearly.
Examples
The following example defines network number 60 as an NBP proxy for the zone Twilight:
appletalk proxy-nbp 60 TwilightRelated Commands
show appletalk route
Displays all entries or specified entries in the AppleTalk routing table.
appletalk require-route-zones
To prevent the advertisement of routes (network numbers or cable ranges) that have no assigned zone, use the appletalk require-route-zones command in global configuration mode. To disable this option and allow the Cisco IOS software to advertise to its neighbors routes that have no network-zone association, use the no form of this command.
appletalk require-route-zones
no appletalk require-route-zones
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled
Command Modes
Global configuration
Command History
Usage Guidelines
The appletalk require-route-zones command ensures that all networks have zone names prior to advertisement to neighbors.
The no appletalk require-route-zones command enables behavior compatible with Cisco IOS Release 8.3.
Using this command helps prevent ZIP protocol storms. ZIP protocol storms can arise when corrupt routes are propagated and routers broadcast ZIP requests to determine the network/zone associations.
When the appletalk require-route-zones command is enabled, the Cisco IOS software will not advertise a route to its neighboring routers until it has obtained the network-zone associations. This effectively limits the storms to a single network rather than the entire internet.
As an alternative to disabling this option, use the appletalk getzonelist-filter interface configuration command to filter empty zones from the list presented to users.
You can configure different zone lists on different interfaces. However, you are discouraged from doing this because AppleTalk users expect to have the same user zone lists at any end node in the internet.
The filtering provided by the appletalk require-route-zones command does not prevent explicit access via programmatic methods, but should be considered a user optimization to suppress unused zones. You should use other forms of AppleTalk access control lists to actually secure a zone or network.
Examples
The following example configures a router to prevent the advertisement of routes that have no assigned zone:
appletalk require-route-zonesappletalk route-cache
To enable fast switching on all supported interfaces, use the appletalk route-cache command in interface configuration mode. To disable fast switching, use the no form of this command.
appletalk route-cache
no appletalk route-cache
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled on all interfaces that support fast switching.
Command Modes
Interface configuration
Command History
Usage Guidelines
Fast switching allows higher throughput by switching a packet using a cache created by previous packets. Fast-switching is enabled by default on all interfaces that support fast switching, including Token Ring, Frame Relay, PPP, High-Level Data Link Control (HDLC), SMDS, and ATM. Note that fast switching is not supported over X.25 and Link Access Procedure, Balanced (LAPB), encapsulations, or on the CSC-R16, CSC-1R, or CSC-2R STR Token Ring adapters.
Packet transfer performance is generally better when fast switching is enabled. However, you may want to disable fast switching in order to save memory space on interface cards and to help avoid congestion when high-bandwidth interfaces are writing large amounts of information to low-bandwidth interfaces.
Fast switching of extended AppleTalk is supported on serial lines with several encapsulation types (for example, SMDS and HDLC). Fast switching of nonextended AppleTalk is not supported on serial lines.
Examples
The following example disables fast switching on an interface:
interface ethernet 0appletalk cable-range 10-20appletalk zone Twilightno appletalk route-cacheRelated Commands
show appletalk cache
Displays the routes in the AppleTalk fast-switching table on an extended AppleTalk network.
appletalk route-redistribution
To redistribute Routing Table Maintenance Protocol (RTMP) routes into AppleTalk Enhanced Interior Gateway Routing Protocol (EIGRP) and vice versa, use the appletalk route-redistribution command in global configuration mode. To keep Enhanced IGRP and RTMP routes separate, use the no form of this command.
appletalk route-redistribution
no appletalk route-redistribution
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled when Enhanced IGRP is enabled.
Command Modes
Global configuration
Command History
Usage Guidelines
Redistribution allows routing information generated by one protocol to be advertised in another.
In the automatic redistribution of routes between Enhanced IGRP and RTMP, an RTMP hop is treated as having a slightly worse metric than an equivalent Enhanced IGRP hop on a 9.6-kbps link. This allows Enhanced IGRP to be preferred over RTMP except in the most extreme of circumstances. Typically, you will see this only when using tunnels. If you want an Enhanced IGRP path in a tunnel to be preferred over an alternate RTMP path, you should set the interface delay and bandwidth parameters on the tunnel to bring the metric of the tunnel down to being better than a 9.6-kbps link.
Examples
In the following example, RTMP routing information is not redistributed:
appletalk routing eigrp 23no appletalk route-redistributionappletalk routing
To enable AppleTalk routing, use the appletalk routing command in global configuration mode. To disable AppleTalk routing, use the no form of this command.
appletalk routing [eigrp router-number]
no appletalk routing [eigrp router-number]
Syntax Description
Defaults
Disabled
Command Modes
Global configuration
Command History