#

# AppleTalk Routing

This chapter covers the following topics:

Introduction to AppleTalk routing
How AppleTalk works
Configuring an AppleTalk connection with RADIUS
Additional information about AppleTalk

## Introduction to AppleTalk routing

The MAX functions as an AppleTalk internet router, providing routing functions for AppleTalk nodes (Macintosh workstations or Apple printers) that are connected to the MAX over Ethernet or a WAN. The following AppleTalk protocols are supported:

- Datagram Delivery Protocol (DDP)

- Routing Table Maintenance Protocol (RTMP)

- AppleTalk Echo Protocol (AEP)

- Zone Information Protocol (ZIP)

- Name Binding Protocol (NBP)

- AppleTalk Control Protocol (ATCP- for router-to-router applications)

### When to use AppleTalk routing

With AppleTalk routing, connect two or more networks that have AppleTalk nodes, such as Mac OS computers or Apple printers. The primary benefits of routing AppleTalk traffic (as opposed to bridging this traffic) are:

- Reducing broadcast and multicast traffic over the WAN

- Providing startup information to local AppleTalk devices

#### Reducing broadcast and multicast traffic

Because AppleTalk uses multicast and broadcast addresses extensively, routing AppleTalk can greatly improve the efficiency of a LAN or WAN. By using AppleTalk zones to segment traffic, you can significantly reduce the amount of broadcast and multicast traffic on a LAN or WAN. When you set up a router for the first time, you identify the cable range (network-number range) for the subnetwork segment and one or more zones.

For example, when a user on a network without a router selects a device in the Chooser, the MAC OS computer sends out a Name Binding Protocol (NBP) Lookup as a broadcast packet. Since a bridge forwards all broadcast traffic, all devices on the network receive the Lookup packet. A router can significantly reduce AppleTalk traffic over the WAN because it does not forward broadcast traffic from one subnetwork to another, but stops it at the subnetwork port of the router.

Zone multicasting is intended to prevent any node not in the destination zone for the lookup from receiving the lookup packet. Any AppleTalk node responds only to NBP lookups for that node's zone name. In the example above, a router would convert the Broadcast Request packet generated by the Lookup request to a Forward Request packet for each network that contains nodes in the target zone specified by the Lookup request.

A bridge can filter directed traffic between two specific nodes but cannot filter broadcast or multicast traffic, since there is not a specific port that can be assigned to a multicast or broadcast address. This means that although filters used with bridging can reduce the number of AppleTalk packets sent to remote network segments, bridging does not reduce the number of broadcast and multicast packets over these networks.

#### Providing dynamic startup information to local devices

In addition to routing services, the Ascend AppleTalk router provides startup information to AppleTalk stations. As with other routed protocols, AppleTalk station, or node, addresses are comprised of a unique network number/node combination. AppleTalk addresses are dynamically assigned when a node starts up. In addition, the router provides an AppleTalk node with the network cable range to which it is attached, and supplies zone name information.

### Understanding AppleTalk zones and network ranges

AppleTalk zones and network ranges are configured in AppleTalk routers. Network numbers are assigned to network segments, and must be unique within the internetwork. A network range is a range of network numbers set into the port descriptor of the router port and then transmitted through RTMP to the other nodes of the network. Each of the numbers within a network range can represent up to 253 devices.

#### AppleTalk zones

A zone is a multicast address containing an arbitrary subset of the AppleTalk nodes in an internet. Each node belongs to only one zone, but a particular extended network can contain nodes belonging to any number of zones. Zones provide departmental or other groupings of network entities that a user can easily understand.

In the Ascend AppleTalk router, zone names are case-insensitive. However, since some routers regard zone names as case-sensitive, it is advisable to be consistent in spelling zone names when you configure multiple connections or routers.

#### Extended and non-extended AppleTalk networks

AppleTalk subnetworks are either non-extended or extended. Non-extended networks theoretically allow up to 254 nodes. A non-extended network has one network number (not a range) and one zone. Examples of non-extended networks are LocalTalk and ARA dial-up networks.

An extended network is a group of non-extended networks on the same physical data link, and contains a range of network numbers. Each network in the range supports up to 253 devices. EtherTalk and TokenTalk are examples of extended networks.

At least one router on a network, called the seed router, must have the network number range set into its port description. Other routers on the network can have a network range of 0 (zero), which specifies that they acquire the network-number range from RTMP packets sent by the seed router. AppleTalk routers on a network must not have conflicting network-number ranges for that network. A 0 value does not cause a conflict, but otherwise, all seed routers on the same network must have the same value for the start and end of the network-number range.

Figure 5-1 shows a network with three routers and three zones configured. Each zone has a range of network numbers.

Figure 5-1. AppleTalk LAN

Router X, Router Y, and Router Z connect to the backbone network (Range 1001-1010). Each router has an additional connection to a local network segment. For example, Router X has a connection to the network range 100-109. User A's computer also connects to the 100-109 range.

Because Router X is configured with only one zone, any AppleTalk device joining the segment belongs to the SALES zone. But User B's computer can belong to either the SALES zone or the MKTG. zone. Some AppleTalk devices allow you to select the zone to which they belong. If there is no way to manually assign the zone, the AppleTalk device is put into the default zone, which is defined on the AppleTalk router.

Figure 5-1 shows two important concepts about network numbers and zones. When a network range is defined, all values within that range are unusable for any other segment. The segment to which user C's computer connects uses network range 300-309. No other network segment in this AppleTalk network can use network numbers 300, 301, 302, etc., in their ranges. As an example, network number 310 is available to a new network segment

Zones can be shared among network segments. In Figure 5-1, network 100-109 supports zone SALES. So does network 300-309.

## How AppleTalk works

The following is a brief description of how the workstation user sees a typical AppleTalk connection and describes in a general way what is happening as the user makes the choices that lead to a connection. This example supposes a connection between a workstation on a MAX 4000 connected to Pipeline 75 over a synchronous PPP connection, as shown in Figure 5-2.

Figure 5-2. Routed connection

1. An AppleTalk workstation user opens the Chooser for the first time since it has been attached to the router and configured.

The zones that appear are in the local Ethernet zone (in this case the WAN zone is the same as the local Ethernet zone), configured in the Connection profile for the MAX. This information is stored in the MAX.

2. The workstation sends a ZIP Query to obtain an updated zone list from the MAX, and the MAX returns the updated zone list. This list might contain different zones than did the initial list.

3. The user selects a zone and a specific device in the Chooser.

4. The workstation sends an NBP Broadcast Request to the MAX, which checks its Zone Information Table to determine which subnetwork that printer is located in, and sends the request to the other MAX via the port configured in the Connection Profile.

5. The remote MAX determines the port to which the subnetwork is attached and performs the lookup in the appropriate multicast address (multicast addresses are assigned to zones).

6. All devices in the appropriate zone on the subnetwork hear and pick up the NBP Lookup.

7. The selected printer obtains the sender's address from the Lookup packet (in this case the routers are forwarders; the workstation is the sender) and sends the reply through the routers to the workstation.

8. The user sends the print job to the printer.

9. When the print job is complete and no data packets are passing through the connection, the MAXs continue to pass routing information.

### How AppleTalk works

Figure 2 shows a typical AppleTalk connection. The AppleTalk workstation is part of an Ethernet LAN connected to a Pipeline 75, which has a synchronous PPP WAN connection to a MAX 4000. One of the MAX 4000 ports is on a LAN that includes an Apple Laserwriter printer. Following is a brief, generalized description of how the workstation sends a file to the Laserwriter for printing:

Figure 5-3. Routed connection

1. The AppleTalk workstation user opens the Macintosh Chooser.

The screen displays the network zones specified by the Connection profile stored in the Pipeline. (The first time a user opens the chooser, only the local Ethernet zones appear. That is, the WAN zone is the same as the local Ethernet zone.)

2. The Pipeline places the call and negotiates the WAN connection with the MAX 4000.

3. The workstation sends a ZIP Query to obtain an updated zone list from the MAX 4000, and the MAX returns the updated zone list. The new list, which might contain different zones from the initial zone list, replaces the initial list in the display and updates the Connection profile in the Pipeline.

4. The user selects a zone and a specific device in the Chooser. For example:

1. The workstation sends a Name Binding Protocol (NBP) Broadcast Request to the Pipeline, which checks its Zone Information Table to identify the subnetwork in which that printer is located, and then sends the request to the MAX via the port configured in the Connection Profile.

2. The MAX determines the port to which the printer's subnetwork is attached, and looks up the printer by searching the multicast address assigned to the zone specified by the Pipeline.

3. All devices in the zone detect and process the NBP-lookup packet.

4. The selected printer obtains the sender's address from the lookup packet (sent by the workstation and forwarded by the routers), and sends the reply through the routers to the workstation.

5. The user sends the print job to the printer.

6. When the print job is complete and no data packets are passing through the connection, the MAX and the Pipeline continue to pass routing information until the idle timeout closes the connection. RTMP and ZIP packets do not reset the idle timer, but any other routeable packet to the network number or zone name specified for this connection does reset the timer.

After the link is dropped, the Pipeline retains in memory the last zone list displayed. If the workstation user opens the Chooser again, the list reappears and the process can begin again.

### Configuring AppleTalk routing

To configure AppleTalk routing, you must complete the steps outlined in System-level AppleTalk routing parameters and Per-connection AppleTalk routing parameters(if required).

#### System-level AppleTalk routing parameters

To set the required parameters in the Ethernet Configuration profile,

1. Open the Ethernet > Mod Config > Ether Options menu.

2. Set AppleTalk to Yes.

   You must set AppleTalk to Yes to be allowed to configure the remaining parameters.

3. In the Ethernet > Mod Config > AppleTalk Options menu, set the Zone Name parameter to the name of any of the zones, assigned to the network segment, to which the Ascend unit is connected. Enter up to 33 alphanumeric characters. For example, for router X in Figure 5-1:

       90-B00 Mod Config
               AppleTalk Options
                   Peer=Router
                >Zone Name=SALES
                   AppleTalk Router=Seed
                   Net Start=300
                   Net End=309
                   Default Zone=SALES
                   Zone Name #1=MKTG
                   Zone Name #2=ENGINEERING
                   Zone Name #3=
                   Zone Name #4=

4. Set the AppleTalk Router parameter to Seed or Non-Seed to specify whether the Ascend unit is a seed or nonseed router. For example:

       90-B00 Mod Config
               AppleTalk Options
                   Peer=Router
                 >Zone Name=SALES
                   AppleTalk Router=Seed
                   Net Start=300
                   Net End=309
                   Default Zone=SALES
                   Zone Name #1=MKTG
                   Zone Name #2=ENGINEERING
                   Zone Name #3=
                   Zone Name #4=

   A seed router has a manually defined network configuration. When a non-seed router boots, it has no local network configuration. It examines local network traffic and learns its local network configuration.

   Note: You should configuring the MAX as a non-seed router provided there is at least one seed router on the local network. Having only one seed router on a local network simplifies potential network configuration changes. Should you need to change the network numbering, only the seed router needs to be reconfigured. The remaining non-seed routers simply need to be rebooted to learn the changes.

5. If the MAX is to be a seed router, set the Net Start and Net End parameters to specify the range for the network to which the unit is attached. (For example, the menu shown in step 4 specifies a range of 300-309.)

   If there are other seed routers sharing the MAX's network segment, this information must be identical on all routers that share the network segment. If there are no other seed routers, every network number from Net Start to Net End must be unique for the entire internet. Valid network numbers are of from 1 to 65,534.

6. If the MAX is to be a seed router, specify the default-zone name assigned to the local AppleTalk network segment. Enter up to 33 alphanumeric characters in the Default Zone field. (For example, the menu shown in step 4 specifies SALES as the default zone.)

   AppleTalk routers assign the default zone to any AppleTalk device that is connected to the local Ethernet segment but has not explicitly been assigned to another zone.

   The Default Zone and additional zone list need to be identical for any AppleTalk router sharing the local network segment.

   Note: Zones can be shared across network segments.

7. If the MAX is to be a seed router, specify the names of any other zones assigned to the network segment to which the MAX is connected. Enter up to 33 alphanumeric characters in each of one or more of the Zone Name fields. (For example, the menu shown in step 4 specifies MKTG in the Zone Name #1 field and SALES, MKTG in Zone Name #2.)

   The Default Zone and additional zone list need to be identical for any AppleTalk router sharing the local network segment.

   Note: Zones can be shared across network segments.

#### Answer profile parameter

If you configure the MAX to authenticate via names and passwords, enable AppleTalk routing in the Ethernet > Answer profile by selecting Route AppleTalk=Yes. For example:

    90-700 Answer
        PPP Options
           >Route IP=No
          Route IPX=No
          Route AppleTalk=Yes
          Bridge=Yes
          Recv Auth=None
          MRU=1524

(You cannot set the Route AppleTalk parameter if AppleTalk is set to No in the Ethernet Configuration profile or if AppleTalk Router is set to Off in that profile's AppleTalk Options submenu.)

#### Per-connection AppleTalk routing parameters

To enable AppleTalk routing for a specific connection:

1. Open the Ethernet > Connections > Any Connection profile.

2. Set Route AppleTalk to Yes.

   You cannot set the Route AppleTalk parameter unless you set Ethernet > Mod Config > AppleTalk Options > AppleTalk to No or Ethernet > Answer profile > Route AppleTalk to No in the Answer profile.

3. Set the Encaps option to PPP, MPP, or MP.

4. Set Dial # to the number the MAX dials when it receives AppleTalk data that it should forward to the remote network specified by this profile.

5. Open the AppleTalk Options menu

6. Set Zone Name to specify the zone name for the AppleTalk router at the remote end of the connection. For example:

       90-101 Macintosh 1
           >AppleTalk options...
               Peer=Router
               Zone Name=ENGINEERING
               Net Start=2001
               Net End=2010

   This zone name appears in the AppleTalk Zones window of the Chooser. If the WAN segment for the zone is not already connected when packets for the zone are received (for example, when a user selects this zone in the Chooser, and then selects AppleShare), the Ascend unit places a call to the number in the Dial # field of the Connection Profile.

7. Enter the network range in the Net Start and Net End fields.

   This range defines the networks available for packets that are to be routed to this static route. Valid entries for these fields are in the range from 1 to 65,534. If there are other AppleTalk routers on the network, it is necessary to configure the network ranges to coincide with the other routers on the LAN.

## Configuring an AppleTalk connection with RADIUS

You can configure an AppleTalk-routed connection via a RADIUS user profile and configure static AppleTalk routes in a RADIUS pseudo-user file. See the MAX RADIUS Configuration Guide for more information.

## Additional information about AppleTalk

This feature note provides only a very brief description of AppleTalk networking. For more complete information, see the following books:

Apple Computer. Inside Macintosh: Networking.

Chappell, Laura A., and Roger L. Spicer. Novell's Guide to Multiprotocol Internetworking.

Sidhu, Andrews, and Alan B. Oppenheimer. Inside AppleTalk, Second Edition.

Cougias, Dell, and Heiberger. Designing AppleTalk Network Architectures.

Copyright © 1998, Ascend Communications, Inc. All rights reserved.