Avaya AppleTalk User Manual

Download

Page 1

Conﬁguring AppleTalk Services

Router Software Version 11.0 Site Manager Software Version 5.0

Part No. 114048 Rev. A August 1996

Page 2

4401 Great America Parkway 8 Federal Street Santa Clara, CA 95054 Billerica, MA 01821

and recommendations in this document are believed to be accurate and reliable, but are presented without express or implied warranty . Users must take full responsibility for their applications of an y products speciﬁed in this document. The information in this document is proprietary to Bay Networks, Inc.

The software described in this document is furnished under a license agreement and may only be used in accordance with the terms of that license. A summary of the Software License is included in this document.

Restricted Rights Legend

Use, duplication, or disclosure by the United States Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013.

Notice for All Other Executive Agencies

Notwithstanding any other license agreement that may pertain to, or accompany the delivery of, this computer software, the rights of the United States Government regarding its use, reproduction, and disclosure are as set forth in the Commercial Computer Software-Restricted Rights clause at FAR 52.227-19.

Trademarks of Bay Networks, Inc.

ACE, AFN, AN, BCN, BLN, BN, BNX, CN, FN, FRE, GAME, LN, Optivity, PPX, SynOptics, SynOptics Communications, Wellﬂeet and the Wellﬂeet logo are registered trademarks and ANH, ASN, Bay•SIS, BCNX, BLNX, EZ Install, EZ Internetwork, EZ LAN, PathMan, PhonePlus, Quick2Conﬁg, RouterMan, SPEX, Bay Networks, Bay Networks Press, the Bay Networks logo and the SynOptics logo are trademarks of Bay Networks, Inc.

Third-Party T rademarks

All other trademarks and registered trademarks are the property of their respective owners.

Statement of Conditions

In the interest of improving internal design, operational function, and/or reliability, Bay Networks, Inc. reserves the right to make changes to the products described in this document without notice.

Bay Networks, Inc. does not assume any liability that may occur due to the use or application of the product(s) or circuit layout(s) described herein.

Portions of the code in this software product are Copyright © 1988, Regents of the Univ ersity of California. All rights reserved. Redistribution and use in source and binary forms of such portions are permitted, provided that the above copyright notice and this paragraph are duplicated in all such forms and that any documentation, advertising materials, and other materials related to such distribution and use acknowledge that such portions of the software were developed by the University of California, Berkeley. The name of the University may not be used to endorse or promote products derived from such portions of the software without speciﬁc prior written permission.

SUCH PORTIONS OF THE SOFTWARE ARE PROVIDED “AS IS” AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

In addition, the program and information contained herein are licensed only pursuant to a license agreement that contains restrictions on use and disclosure (that may incorporate by reference certain limitations and notices imposed by third parties).

114048 Rev. A

Page 3

Bay Networks Software License

Note:

This is Bay Networks basic license document. In the absence of a software license agreement specifying varying terms, this license -- or the license included with the particular product -- shall govern licensee’s use of Bay Networks software.

This Software License shall govern the licensing of all software provided to licensee by Bay Networks (“Software”). Bay Networks will provide licensee with Software in machine-readable form and related documentation (“Documentation”). The Software provided under this license is proprietary to Bay Networks and to third parties from whom Bay Networks has acquired license rights. Bay Networks will not grant any Software license whatsoev er , either explicitly or implicitly, except by acceptance of an order for either Software or for a Bay Networks product (“Equipment”) that is packaged with Software. Each such license is subject to the following restrictions:

1. Upon delivery of the Software, Bay Networks grants to licensee a personal, nontransferable, none xclusiv e license to use the Software with the Equipment with which or for which it was originally acquired, including use at any of licensee’s facilities to which the Equipment may be transferred, for the useful life of the Equipment unless earlier terminated by default or cancellation. Use of the Software shall be limited to such Equipment and to such facility. Software which is licensed for use on hardware not offered by Bay Networks is not subject to restricted use on any Equipment, however, unless otherwise speciﬁed on the Documentation, each licensed copy of such Software may only be installed on one hardware item at any time.

2. Licensee may use the Software with backup Equipment only if the Equipment with which or for which it was acquired is inoperative.

3. Licensee may make a single copy of the Software (but not ﬁrmware) for safekeeping (archives) or backup purposes.

4. Licensee may modify Software (but not ﬁrmware), or combine it with other software, subject to the provision that those portions of the resulting software which incorporate Software are subject to the restrictions of this license. Licensee shall not make the resulting software available for use by any third party.

5. Neither title nor ownership to Software passes to licensee.

6. Licensee shall not provide, or otherwise make available, any Software, in whole or in part, in any form, to any third party. Third parties do not include consultants, subcontractors, or agents of licensee who have licensee’s permission to use the Software at licensee’s facility, and who have agreed in writing to use the Software only in accordance with the restrictions of this license.

7. Third-party owners from whom Bay Networks has acquired license rights to software that is incorporated into Bay Networks products shall have the right to enforce the provisions of this license against licensee.

8. Licensee shall not remove or obscure any copyright, patent, trademark, trade secret, or similar intellectual property or restricted rights notice within or afﬁxed to any Software and shall reproduce and afﬁx such notice on any backup copy of Software or copies of software resulting from modiﬁcation or combination performed by licensee as permitted by this license.

114048 Rev. A

iii

Page 4

Bay Networks Software License

9. Licensee shall not reverse assemble, reverse compile, or in any way reverse engineer the Software. [Note: For licensees in the European Community, the Softw are Directiv e dated 14 May 1991 (as may be amended from time to time) shall apply for interoperability purposes. Licensee must notify Bay Networks in writing of any such intended examination of the Software and Bay Networks may provide review and assistance.]

10. Notwithstanding any foregoing terms to the contrary, if licensee licenses the Bay Networks product “Site Manager,” licensee may duplicate and install the Site Manager product as speciﬁed in the Documentation. This right is granted solely as necessary for use of Site Manager on hardware installed with licensee’s network.

11. This license will automatically terminate upon improper handling of Software, such as by disclosure, or Bay Networks may terminate this license by written notice to licensee if licensee fails to comply with any of the material provisions of this license and fails to cure such failure within thirty (30) days after the receipt of written notice from Bay Networks. Upon termination of this license, licensee shall discontinue all use of the Software and return the Software and Documentation, including all copies, to Bay Networks.

12. Licensee’s obligations under this license shall survive expiration or termination of this license.

(continued)

114048 Rev. A

Page 5

About This Guide

Before You Begin .............................................................................................................xiii

Conventions .....................................................................................................................xiv

Acronyms ......................................................................................................................... xv

Ordering Bay Networks Publications ...............................................................................xvi

Technical Support and Online Services

Bay Networks Customer Service ...................................................................................xviii

Bay Networks Information Services .................................................................................xix

World Wide Web ........................................................................................................xix

Customer Service FTP ..............................................................................................xix

Support Source CD ................................................................................................... xx

CompuServe ............................................................................................................. xx

InfoFACTS .................................................................................................................xxi

How to Get Help ........................................................................................................xxi

Chapter 1 AppleTalk Overview

AppleTalk Networking .....................................................................................................1-1

AppleTalk Addresses ................................................................................................1-2

AppleTalk Zones .......................................................................................................1-4

Seed Routers and Nonseed Routers .......................................................................1-4

How the Bay Networks AppleTalk Router Works ............................................................1-5

AppleTalk Link Access Protocols (TLAP and ELAP) ................................................1-5

AppleTalk Address Resolution Protocol (AARP) ......................................................1-6

Datagram Delivery Protocol (DDP) ..........................................................................1-8

Routing Table Maintenance Protocol (RTMP) ........................................................1-10

Zone Information Protocol (ZIP) .............................................................................1-11

Name Binding Protocol (NBP) ................................................................................1-13

AppleTalk Echo Protocol (AEP) ..............................................................................1-14

114048 Rev. A

Page 6

AppleTalk Update-based Routing Protocol (AURP) ...............................................1-14

AURP Tunneling ...............................................................................................1-14

Update-based Routing Table Maintenance ......................................................1-19

Hop Count Reduction ......................................................................................1-20

For More Information ....................................................................................................1-21

Chapter 2 AppleTalk Implementation Notes

AppleTalk Interfaces over WAN Media ............................................................................2-2

AppleTalk Running on Frame Relay or SMDS .........................................................2-2

Conﬁguring AppleTalk as a Nonextended Network over PPP ..................................2-2

Conﬁguring AppleTalk as an Extended Network over PPP ......................................2-4

Seed Router Interfaces ...................................................................................................2-5

Interface Costs ...............................................................................................................2-6

AppleTalk Routing and Bridging on the Same Interface .................................................2-8

AppleTalk Zone Information ............................................................................................2-8

Adding or Removing AppleTalk Zones .....................................................................2-8

Using AppleTalk Zone Filters .................................................................................2-10

How Zone Filters Work ....................................................................................2-11

Zone Filter Rules .............................................................................................2-14

AppleTalk Network Topology Information ......................................................................2-27

Conﬁguring the AppleTalk Router to Source Route over Token Ring Networks .....2-27

Conﬁguring the AppleTalk Router in a Non-Fully Meshed Frame Relay Topology .2-29

Reducing Excess Routing Trafﬁc on a Large AppleTalk Network ...........................2-30

Adding a Bay Networks AppleTalk Router to a Transitional Network .....................2-31

AURP Information .........................................................................................................2-31

Deciding When to Use AURP .................................................................................2-31

Setting the Update Rate .........................................................................................2-32

Setting the Last Heard From Timeout ....................................................................2-33

Setting the Hop Count Reduction ...........................................................................2-34

Setting the Command Timeout and Command Retries .........................................2-34

Setting Zone Filters ................................................................................................2-35

Setting the Interface Cost .......................................................................................2-35

AppleTalk Dial-on-Demand Routing .......................................................................2-35

114048 Rev. A

Page 7

Chapter 3 Enabling AppleTalk Services

Enabling AppleTalk on an Interface ................................................................................3-2

Conﬁguring the Zone List .........................................................................................3-5

Using Nonprintable Characters in AppleTalk Zone Names ......................................3-7

Conﬁguring AURP ..........................................................................................................3-8

Chapter 4 Editing AppleTalk Parameters

Accessing AppleTalk Parameters ...................................................................................4-2

Editing the AppleTalk Global Parameter .........................................................................4-2

Editing AppleTalk Interface Parameters ..........................................................................4-3

Conﬁguring AppleTalk Zone Lists .................................................................................4-11

Adding Zones to a Zone List ..................................................................................4-11

Deleting Zones from the Zone List .........................................................................4-13

Changing the AppleTalk Default Zone ..........................................................................4-14

Conﬁguring AppleTalk Zone Filters ...............................................................................4-15

Adding Zones to the Zone Filter List ......................................................................4-15

Editing the Zone Filter Type ....................................................................................4-17

Deleting Zones from the Zone Filter List ................................................................4-19

Selecting the Name Binding Protocol Interface ............................................................4-19

Globally Deleting AppleTalk ..........................................................................................4-21

Editing AURP Global Parameters .................................................................................4-21

Editing AURP Interface Parameters .............................................................................4-22

Editing the AURP Zone Filter List .................................................................................4-27

Appendix A AppleTalk Default Settings

Index

114048 Rev. A

vii

Page 8

Page 9

Figures

Figure 1-1. AppleTalk Address with 24 Bits ................................................................1-2

Figure 1-2. Extended and Nonextended AppleTalk Network ......................................1-3

Figure 1-3. AARP Packets ..........................................................................................1-7

Figure 1-4. DDP Packet ..............................................................................................1-9

Figure 1-5. RTMP Data Packet .................................................................................1-10

Figure 1-6. ZIP Response Packets ...........................................................................1-11

Figure 1-7. ZIP GetNetInfo Packets ..........................................................................1-12

Figure 1-8. NBP Packets ..........................................................................................1-13

Figure 1-9. AURP Tunneling across an IP Internet ...................................................1-15

Figure 1-10. Fully Connected Tunnel ..........................................................................1-16

Figure 1-11. Partially Connected Tunnel ....................................................................1-17

Figure 1-12. AppleTalk Data Packet Forwarded across an AURP Tunnel ..................1-19

Figure 2-1. AppleTalk Nonextended Conﬁguration over PPP .....................................2-3

Figure 2-2. AppleTalk Extended Conﬁguration over PPP ...........................................2-5

Figure 2-3. Assigning Circuit Costs to AppleTalk Interfaces .......................................2-7

Figure 2-4. Updating an AppleTalk Router’s Zone List ...............................................2-9

Figure 2-5. Conﬁguring Zone Filters with the Exclude Option ..................................2-12

Figure 2-6. Conﬁguring Zone Filters with the 5.X Exclude Option ...........................2-14

Figure 2-7. AppleTalk Zone Filters with the Exclude Option: Rule 1 ........................2-15

Figure 2-8. AppleTalk Zone Filters with the Exclude Option: Rule 2 ........................2-16

Figure 2-9. AppleTalk Zone Filters with the Exclude Option: Rule 3 ........................2-17

Figure 2-10. AppleTalk Zone Filters with the Exclude Option: Rule 4 ........................2-18

Figure 2-11. AppleTalk Zone Filters with the Include Option: Rule 1 ..........................2-19

Figure 2-12. AppleTalk Zone Filters with the Include Option: Rule 2 ..........................2-20

Figure 2-13. AppleTalk Zone Filters with the Include Option: Rule 3 ..........................2-21

Figure 2-14. AppleTalk Zone Filters with the 5.X Exclude Option: Rule 1 ..................2-22

Figure 2-15. AppleTalk Zone Filters with the 5.X Exclude Option: Rule 2 ..................2-23

Figure 2-16. AppleTalk Zone Filters with the 5.X Exclude Option: Rule 3 ..................2-24

Figure 2-17. AppleTalk Zone Filters with the 5.X Include Option: Rule 1 ...................2-25

114048 Rev. A

Page 10

Figure 2-18. AppleTalk Zone Filters with the 5.X Include Option: Rule 2 ...................2-26

Figure 2-19. AppleTalk Zone Filters with the 5.X Include Option: Rule 3 ...................2-27

Figure 2-20. AppleTalk Routers Source Routing across a Token Ring Network ........2-28

Figure 2-21. AppleTalk Routers in a Non-Fully Meshed Frame Relay Topology ........2-30

Figure 2-22. Network Loop .........................................................................................2-34

Figure 3-1. AppleTalk Interface Conﬁguration Window ..............................................3-2

Figure 3-2. AT Zone Conﬁguration Window ................................................................3-6

Figure 3-3. AppleTalk Zone Conﬁguration Window ....................................................3-6

Figure 3-4. Edit Apple AURP Global Parameters Window .........................................3-8

Figure 3-5. AT AURP Interface Conﬁguration Window .............................................3-10

Figure 3-6. AppleTalk AURP Conﬁguration Window .................................................3-10

Figure 4-1. Conﬁguration Manager Window ...............................................................4-2

Figure 4-2. Edit AppleTalk Global Parameters Window ..............................................4-3

Figure 4-3. AT Interface Conﬁguration Window ..........................................................4-4

Figure 4-4. AT Zone Conﬁguration Window ..............................................................4-12

Figure 4-5. AppleTalk Zone Filter Conﬁguration Window .........................................4-16

Figure 4-6. AppleTalk Zone Filter Conﬁguration Window .........................................4-16

Figure 4-7. AT Interfaces Window ............................................................................4-20

Figure 4-8. Edit Apple AURP Global Parameters Window .......................................4-21

Figure 4-9. AT AURP Interface Conﬁguration Window .............................................4-23

114048 Rev. A

Page 11

Tables

Table 4-1. Time Equivalents in Seconds .................................................................4-25

Table A-1. AppleTalk Global Parameters ..................................................................A-1

Table A-2. AppleTalk Interface Parameters .............................................................. A-1

Table A-3. AURP Global Parameters ....................................................................... A-2

Table A-4. AURP Interface Parameters .................................................................... A-2

Table A-5. AURP Zone Filter List Parameters .......................................................... A-2

114048 Rev. A

Page 12

Page 13

About This Guide

If you are responsible for conﬁguring Bay Networks router software for AppleTalk services, refer to this guide for

• A brief look at the AppleTalk routing protocol in relation to Bay Networks routing services (see Chapter 1, “AppleT

• Implementation notes to help you conﬁgure AppleTalk routing services (see Chapter 2, “AppleT

• Instructions on initially conﬁguring an AppleTalk interface (see Chapter 3, “Enabling

AppleTalk Services”)

alk Implementation Notes”)

alk Overview”)

• Instructions on editing AppleTalk global and interface parameters and conﬁguring AppleTalk services (see Chapter 4, “Editing

Parameters”)

For information and instructions about the following tasks, see

Routers

• Retrieving a conﬁguration ﬁle

• Rebooting the router with a conﬁguration ﬁle

Before Y ou Begin

Before using this guide, you must complete the following procedures. For a new router:

• Install the router (refer to the installation manual that came with your router).

• Connect the router to the network and create a pilot conﬁguration ﬁle (refer to

Quick-Starting Routers and BNX Platforms, Connecting BayStack AN and ANH Systems to a Network to a Network)

AppleTalk

Conﬁguring

, or

Connecting ASN Routers and BNX Platforms

114048 Rev. A

xiii

Page 14

Configuring AppleTalk Services

Make sure that you are running the latest version of Bay Networks Site Manager and router software. For instructions, refer to

7–10.xx to Version 11.0

Conventions

Upgrading Routers from Version

bold text

Indicates text that you need to enter and command names in text.

dinfo

command.

italic text

Example: Use the Indicates variable values in command syntax

descriptions, new terms, ﬁle and directory names, and book titles.

quotation marks (“ ”) Indicate the title of a chapter or section within a book.

screen text

Indicates data that appears on the screen. Example:

Set Bay Networks Trap Monitor Filters

separator ( > ) Separates menu and option names in instructions and

internal pin-to-pin wire connections. Example: Protocols > AppleTalk identiﬁes the

AppleTalk option in the Protocols menu. Example: Pin 7 > 19 > 20

vertical line (

) Indicates that you enter only one of the parts of the

command. The vertical line separates choices. Do not type the vertical line when entering the command. Example: If the command syntax is

show at routes show at routes

nets

, you enter either

show at nets

, but not both.

xiv

114048 Rev. A

Page 15

Acronyms

About This Guide

AARP AppleTalk Address Resolution Protocol AEP AppleTalk Echo Protocol AMT Address Mapping Table ATCP AppleTalk Control Protocol AURP AppleTalk Update-based Routing Protocol DDP Datagram Delivery Protocol DI Domain Identiﬁer DLCI Data Link Connection Identiﬁer FDDI Fiber Distributed Data Interface ELAP EtherTalk Link Access Protocol IP Internet Protocol LAN local area network NBP Name Binding Protocol PPP Point-to-Point Protocol RFC Request For Comments RTMP Routing Table Maintenance Protocol SMDS Switched Multimegabit Data Services SNAP Subnetwork Access Protocol SNMP Simple Network Management Protocol TLAP TokenTalk Link Access Protocol UDP User Datagram Protocol WAN wide area network ZIP Zone Information Protocol

114048 Rev. A

Page 16

Configuring AppleTalk Services

Ordering Bay Networks Publications

To purchase additional copies of this document or other Bay Networks publications, order by part number from the Bay Networks Press telephone or fax numbers:

• Telephone - U.S./Canada 1-888-4BAYPRESS

• Telephone - International 1-510-490-4752

• Fax 1-510-498-2609

You can also use these numbers to request a free catalog of Bay Networks Press product publications.

™

at the following

xvi

114048 Rev. A

Page 17

Technical Support and Online Services

To ensure comprehensive network support to our customers and partners worldwide, Bay Networks Customer Service has Technical Response Centers in key locations around the globe:

• Billerica, Massachusetts

• Santa Clara, California

• Sydne y , Australia

• Tokyo, Japan

• Valbonne, France

114048 Rev. A

The Technical Response Centers are connected via a redundant Frame Relay Network to a Common Problem Resolution system, enabling them to transmit and share information, and to provide live, around-the-clock support 365 days a year.

Bay Networks Information Services complement the Bay Networks Service program portfolio by giving customers and partners access to the most current technical and support information through a choice of access/retrieval means. These include the World W ide Web, CompuServ e, Support Source CD, Customer Support FTP, and InfoFACTS document fax service.

xvii

Page 18

Configuring AppleTalk Services

Bay Networks Customer Service

If you purchased your Bay Networks product from a distributor or authorized reseller, contact that distributor’s or reseller’s technical support staf f for assistance with installation, conﬁguration, troubleshooting, or integration issues.

Customers can also purchase direct support from Bay Networks through a variety of service programs. As part of our PhonePlus™ program, Bay Netw orks Service sets the industry standard, with 24-hour, 7-days-a-week telephone support available worldwide at no extra cost. Our complete range of contract and noncontract services also includes equipment staging and integration, installation support, on-site services, and replacement parts delivery -- within approximately 4 hours.

To purchase any of the Bay Networks support programs, or if you have questions on program features, use the following numbers:

Region Telephone Number Fax Number

United States and Canada

1-800-2LANWAN; enter Express Routing Code (ERC) 290 when prompted

(508) 670-8766

xviii

(508) 436-8880 (direct) Europe (33) 92-968-300 (33) 92-968-301 Asia/Paciﬁc Region (612) 9927-8800 (612) 9927-8811 Latin America (407) 997-1713 (407) 997-1714

In addition, you can receive information on support programs from your local Bay Networks ﬁeld sales ofﬁce, or purchase Bay Networks support directly from your authorized partner.

114048 Rev. A

Page 19

Bay Networks Information Services

Bay Networks Information Services provide up-to-date support information as a ﬁrst-line resource for network administration, expansion, and maintenance. This information is available from a variety of sources.

W orld Wide Web

The Bay Networks Customer Support Web Server offers a diverse library of technical documents, software agents, and other important technical information to Bay Networks customers and partners.

A special beneﬁt for contracted customers and resellers is the ability to access the Web Server to perform Case Management. This feature enables your support staff to interact directly with the network experts in our worldwide Technical Response Centers. A registered contact with a valid Site ID can

• View a listing of support cases and determine the current status of any open case. Case history data includes severity designation, and telephone, e-mail, or other logs associated with the case.

Technical Support and Online Services

• Customize the listing of cases according to a variety of criteria, including date, severity, status, and case ID.

• Log notes to existing open cases.

• Create new cases for rapid, efﬁcient handling of noncritical network situations.

• Communicate directly via e-mail with the speciﬁc technical resources assigned to your case.

The Bay Networks URL is menu item on that home page.

Customer Service FTP

Accessible via URL combines and organizes support ﬁles and documentation from across the Bay Networks product suite, including switching products from our Centillion™ and Xylogics site lets you quickly locate information on any of your Bay Networks products.

114048 Rev. A

http://www.baynetworks.com

ftp://support.baynetworks.com

. Customer Service is a

(134.177.3.26), this site

business units. Central management and sponsorship of this FTP

xix

Page 20

Configuring AppleTalk Services

Support Source CD

This CD-ROM -- sent quarterly to all contracted customers -- is a complete Bay Networks Service troubleshooting knowledge database with an intelligent text search engine.

The Support Source CD contains extracts from our problem-tracking database; information from the Bay Networks Forum on CompuServe; comprehensive technical documentation, such as Customer Support Bulletins, Release Notes, software patches and ﬁxes; and complete information on all Bay Networks Service programs.

You can run a single version on Macintosh Windows 3.1, Windows 95, Windows NT, DOS, or UNIX computing platforms. A Web links feature enables you to go directly from the CD to various Bay Networks Web pages.

CompuServe

For assistance with noncritical network support issues, Bay Networks Information Services maintain an active forum on CompuServe, a global bulletin-board system. This forum provides ﬁle services, technology conferences, and a message section to get assistance from other users.

The message section is monitored by Bay Networks engineers, who provide assistance wherever possible. Customers and resellers holding Bay Networks service contracts also have access to special libraries for advanced levels of support documentation and software. To take advantage of CompuServe’ s recently enhanced menu options, the Bay Networks Forum has been re-engineered to allow links to our Web sites and FTP sites.

We recommend the use of CompuServe Information Manager software to access these Bay Networks Information Services resources. To open an account and receive a local dial-up number in the United States, call CompuServe at 1-800-524-3388. Outside the United States, call 1-614-529-1349, or your nearest CompuServe ofﬁce. Ask for Representative No. 591. When you are on line with your CompuServe account, you can reach us with the command

GO BAYNET

114048 Rev. A

Page 21

InfoFACTS

InfoFACTS is the Bay Networks free 24-hour fax-on-demand service. This automated system has libraries of technical and product documents designed to help you manage and troubleshoot your Bay Networks products. The system responds to a fax from the caller or to a third party within minutes of being accessed.

To use InfoFACTS in the United States or Canada, call toll-free 1-800-786-3228. Outside North America, toll calls can be made to 1-408-764-1002. In Europe, toll-free numbers are also available for contacting both InfoFACTS and CompuServe. Please check our Web page for the listing in your country.

How to Get Help

Use the following numbers to reach your Bay Networks Technical Response Center:

Technical Response Center Telephone Number Fax Number

Billerica, MA 1-800-2LANWAN (508) 670-8765 Santa Clara, CA 1-800-2LANWAN (408) 764-1188 Valbonne, France (33) 92-968-968 (33) 92-966-998 Sydney, Australia (612) 9927-8800 (612) 9927-8811 Tokyo, Japan (81) 3-5402-0180 (81) 3-5402-0173

Technical Support and Online Services

114048 Rev. A

xxi

Page 22

Page 23

Chapter 1

AppleTalk Overview

Conﬁguring AppleTalk services on your router involves

• AppleTalk network organization, addresses, and zones

• Seed routers and nonseed routers

• The Bay Networks implementation of AppleTalk routing protocols

• Initialization of Bay Networks AppleTalk interfaces

• The Bay Networks implementation of AppleTalk Update-based Routing Protocol (AURP)

• More information about AppleTalk

AppleTalk Networking

The AppleTalk network system, developed by Apple Computer Inc., lets you communicate and share resources (such as printers or ﬁle servers) with other Apple and non-Apple users.

AppleTalk’s dynamic addressing scheme lets you plug into an AppleTalk network to gain immediate access without complicated conﬁguration procedures.

An AppleTalk internet unites physically distinct networks composed of AppleTalk end nodes connected by routers. The end nodes send and receive messages; the routers (like the Bay Networks AppleTalk router) send and recei ve messages, and also route messages, in datagram format, throughout the AppleTalk network.

114048 Rev. A

1-1

Page 24

Configuring AppleTalk Services

AppleTalk Addresses

There are two types of AppleTalk networks:

extended

and

nonextended

. An extended network theoretically supports up to 16 million nodes and has the following characteristics:

range

• The network is assigned a

of 16-bit network numbers.

• Each node within the network is dynamically assigned a 24-bit AppleTalk

address (Figure

1-1) that consists of a 16-bit network number, chosen from

within the range assigned, combined with an 8-bit node number. The v alues 0, $FF, and $FE are reserved for future use.

16 bits

Network Number

Figure 1-1. AppleTalk Address with 24 Bits

8 bits

Node Number

APT0001A

For example, in Figure 1-2, Networks 2-3, 4-4, 5-7, and 8-11 are extended networks.

A nonextended network supports up to 254 nodes and has the following characteristics:

1-2

single

• The entire network is assigned a

16-bit network number.

• Each node within the network is dynamically assigned a 24-bit AppleTalk address that consists of the assigned network number combined with a unique, 8-bit node number.

For example, in Figure

1-2, Network 1 is a nonextended network.

114048 Rev. A

Page 25

1.1 1.2

Network 1

Administrative (default)

6.1 6.2

7.1 7.2

AppleTalk Overview

Network 5-7

Accounting

(default)

Finance

Network NumberRange

2-3

4-4 5-7

Network 2-3 Marketing (default)

8.1

8.2

(default)

Network Type Nonextended

Extended

Extended Extended

Network 8-11

9.1

9.2

Manufacturing

Default Zone Administrative

Marketing

Marketing Accounting

Network 4-4 Marketing (default)

10.1

10.2

11.1

11.2

EngineeringMarketing

Zone List Adminstrative

Marketing

Marketing Finance

Accounting

8-11

Extended

Marketing

Figure 1-2. Extended and Nonextended AppleTalk Network

114048 Rev. A

Marketing Manufacturing Engineering

APT0002A

1-3

Page 26

Configuring AppleTalk Services

AppleTalk Zones

Each AppleTalk network is logically divided into the location of a network entity or service. Similar network services are usually assigned to the same zone.

A network’s nonextended network consists of only a single zone. You can divide an extended network into 255 zones, with one zone designated as the zone can be part of many different networks. When a new node ﬁrst starts on the network, it is assigned to the default zone. Later, you can reassign it to any valid zone on the zone list.

zone list

contains all the zones assigned to the network. A

Seed Routers and Nonseed Routers

Each AppleTalk network must have at least one designated seed router, which is a router conﬁgured with the following network information:

• Network number start range

• Network number end range

• Default zone name

• Zone list for the network

Seed routers share this network information with all other nonseed routers on the network. Multiple seed routers can reside on the same network, but their network ranges, default zone name, and zone list must be identical.

zones

. Zones help you identify

default zone

. The same

1-4

114048 Rev. A

Page 27

How the Bay Networks AppleTalk Router Works

This section describes the following AppleTalk protocols and notes any Bay Networks divergences from these standards:

• TokenTalk Link Access Protocol (TLAP)

• EtherTalk Link Access Protocol (ELAP)

• AppleTalk Address Resolution Protocol (AARP)

• Datagram Delivery Protocol (DDP)

• Routing Table Maintenance Protocol (RTMP)

• Zone Information Protocol (ZIP)

• Name Binding Protocol (NBP)

• AppleTalk Echo Protocol (AEP)

• AppleTalk Update-based Routing Protocol (AURP)

This section also describes how a Bay Networks AppleTalk interface initializes on the network.

AppleTalk Overview

AppleTalk Link Access Protocols (TLAP and ELAP)

The Bay Networks AppleTalk router uses AppleTalk Link Access protocols to transmit packets between nodes on the same physical network. (TokenTalk controls data transmission on Token Ring networks; EtherTalk controls data transmission on Ethernet networks.) The router also supports Fiber Distributed Data Interface (FDDI) and Bay Networks-proprietary synchronous encapsulation.

Note: The Bay Networks AppleTalk router does not support LocalTalk or

AppleT alk Phase 1 routing and therefore cannot directly attach to none xtended networks.

114048 Rev. A 1-5

Page 28

Configuring AppleTalk Services

AppleTalk Address Resolution Protocol (AARP)

For a Bay Networks AppleTalk router to forward a packet to a directly connected AppleTalk node, the router needs to know the

• P acket’ s AppleT alk address

• Corresponding hardware address of the node where the AppleTalk address resides

The router uses the AppleTalk Address Resolution Protocol (AARP) to map AppleTalk addresses to their equivalent hardware addresses. The router saves this information in its Address Mapping Table (AMT), which lists all known AppleTalk addresses, corresponding hardware addresses, and the circuit/port where the address resolution is in effect.

The router updates and maintains its AMT by broadcasting and receiving AARP packets (Figure address, it scans its AMT to ﬁnd the address. If the address is not found, the router broadcasts a single Request packet to ﬁnd out which node is using the address.

If the address exists, the node whose address matches that speciﬁed in the Request packet sends back a Response, which identiﬁes the hardware address that maps to the AppleTalk address. The router then updates its AMT with this new information. The router waits 2 seconds for a response.

1-3). When the router needs to send a packet to a gi ven AppleT alk

AARP is also responsible for generating a unique AppleTalk address for each of the router’s AppleTalk interfaces that have not been explicitly assigned. This process is called probing. The Bay Netw orks AppleTalk router implements this by ﬁrst generating a tentative AppleTalk address for the interface in the format

<start_network_number>.<start_node_number>

where

• <start_network_number> is the lowest end of the network number range assigned to the network to which this interface connects.

• <start_node_number> is a randomly selected node number that could be assigned to this interface.

1-6 114048 Rev. A

Page 29

AppleTalk Overview

AARP Request

AARP Response

AARP Probe

Hardware

type

Protocol

type ($809B)

Hardware address length

Protocol address length

Function Request = 1

Source hardware

address

Source AppleTalk

address

Desired AppleTalk

address

Hardware

type

Protocol

type ($809B)

Hardware address length Hardware address length

Protocol address length

Function Request = 2

Source hardware

address

Source AppleTalk

address

Destination hardware

address

Desired AppleTalk

address

Hardware

type

Protocol

type ($809B)

Protocol address length

Function Request = 3

Source hardware

address

Tentative AppleTalk

address

Tentative AppleTalk

address

AppleTalk Address in AARP Packets

Note: The $ indicates

Network Number

Node Number

a hexadecimal

value.

APT0003A

Figure 1-3. AARP Packets

114048 Rev. A 1-7

Page 30

Configuring AppleTalk Services

Next, the router checks the validity of the address by broadcasting 10 AARP probe packets containing this address at 0.2-second intervals. (For WAN interfaces, the frequency is ﬁve AARP packets at 1.0-second intervals.) AARP probe packets inquire if any other node on the network is already using this address. If the router does not receive a response, then it kno ws that the address is unique on the network and assigns the address to the interface. If the router receives a response (or a probe for the same address), it knows the address is already in use. So the router increments the node number by 1, then sends out 10 more probes. It repeats this process until it does not receive a response, or runs out of all possible node numbers.

If the router runs out of possible node numbers, it increments the start_network_number by 1 and repeats the entire probe process. Finally, if the router is still unable to generate a unique address, it logs the error and shuts down the interface.

Note: If you statically conﬁgure the AppleT alk interf ace’s address (setting the

network ID and node ID to a nonzero value) and another AppleTalk de vice has already acquired this address, the router logs a message indicating that the address is already in use. The router cannot bring up such an interface.

Datagram Delivery Protocol (DDP)

The Bay Networks AppleTalk router uses the Datagram Delivery Protocol (DDP) to transmit packets between nodes on the network. The Datagram Delivery Protocol is an unreliable network layer protocol.

An AppleTalk datagram consists of the DDP header, immediately followed by the data. The Bay Networks router encapsulates all packets in an extended 13-byte DDP header (Figure sending a packet out onto the network. Each router that receives the packet increments the hop count by one until it either reaches the destination end node, or reaches the maximum hop count (15), in which case it is discarded.

1-8 114048 Rev. A

1-4). The source node sets the hop count ﬁeld to zero before

Page 31

AppleTalk Overview

DDP Header

Hop Count

Datagram Length

DDP Checksum

Destination Network

Number

Source Network

Number

Destination Node ID

Source Node ID

Destination Socket No.

Source Socket No.

DDP Type

Datagram Data (0 to 586 bytes)

Sockets 0 = Invalid

1 = RTMP 2 = NIS

4 = AEP 6 = ZIS 3, 5, $07 - $3F reserved $40 - $7F experimental $80 - $FE dynamic

DDP Types

0 = In valid 1 = R TMP 2 = NBP

3 = A TP 4 = AEP 5 = R TMP Req 6 = ZIP

7 = ADSP $08 - $0F reserved

Special Addresses

0000.FF = network-wide broadcast

nnnn.

FF = broadcast to net

nnnn

.00 = any router on net

nnnn

.FE = reserved

net FF00 - FFFE = startup range

nnnn

APT004A

Figure 1-4. DDP Packet

When the Bay Networks AppleTalk router receives a packet, it checks to see if the packet’ s destination network number is the local network. If it is, the router passes it down to the data link layer that forwards the packet to ward the destination node. If the destination network number is a different network, the router refers to its routing tables to determine the next hop on the shortest path to the destination.

Finally, the router increments the hop count by one, and forwards the packet toward the next hop. The router’s routing tables are maintained using the Routing Table Maintenance Protocol.

114048 Rev. A 1-9

Page 32

Configuring AppleTalk Services

Routing Table Maintenance Protocol (RTMP)

The Bay Networks AppleT alk router uses the Routing Table Maintenance Protocol (RTMP) to create and maintain the routing information DDP uses to transmit packets across an internet. Routing information is contained in the AppleTalk routing table.

Each table entry includes the following:

• Destination network range

• AppleTalk protocol address (network number and node number) through which the destination is reached

• Number of router hops to the destination

• Route status

Routers create and update their routing tables by periodically constructing and broadcasting RTMP data packets to all other routers on directly connected links. An RTMP data packet contains the source address and the information stored in the originating router’s routing table. All routers receiving the data packet use this information to update their own routing tables (Figure

1-5).

RTMP Data

Router’s Network

Number

Node ID Length

Router’s Node ID

First Tuple (Network

Range, Distance

and Version)

Second Tuple

APT0005A

Figure 1-5. RTMP Data Packet

1-10 114048 Rev. A

Page 33

Zone Information Protocol (ZIP)

The Bay Networks AppleTalk router uses the Zone Information Protocol (ZIP) to map networks to zone names on the internet. The router stores this information in its zone information table, also called a zone list. The zone information table contains one entry for each network on the internet. The entry is in the format

<network_start, zone list>

The zone list ﬁeld consists of a number of text strings that identify the zone names that are speciﬁed for that network. The router maintains and updates the zone list by broadcasting ZIP Query packets for zone list information to all other routers in the network. Other routers respond with ZIP response packets that have the zone lists (Figure

1-6).

ZIP Query ZIP Reply

Function = 1

AppleTalk Overview

Function = 2(Reply)

8 (Extended Reply)

Network Count

Network 1

Network 2

Network Count

Network 1

Length of Zone Name 1

Zone Name 1

Network 2

Length of Zone Name 2

Zone Name 2

Figure 1-6. ZIP Response Packets

APT0006A

114048 Rev. A 1-11

Page 34

Configuring AppleTalk Services

When an AppleTalk node starts on the network, it requests zone and network information from all routers on the circuit by broadcasting ZIP GetNetInfo request packets (Figure replies with a GetNetInfo response packet that conﬁrms or denies the validity of the zone name and supplies the correct network range. If the stored zone name is invalid, the node uses the default zone name that is conﬁgured for the network instead.

ZIP GetNetInfo Request ZIP GetNetInfo Reply

1-7). Upon receiving a GetNetInfo request, the router

Command = 5

Zone Name Length

Zone Name

Only one zone oneUse broadcast Zone invalid

Flags

Command = 6

Flags

Network Number

Range Start

Network Number

Range End

Zone Name Length

Zone Name

Multicast Address Length

Multicast Address

Default Zone Length

Default Zone

APT0007A

Figure 1-7. ZIP GetNetInfo Packets

1-12 114048 Rev. A

Page 35

Name Binding Protocol (NBP)

Macintosh users on an AppleTalk network refer to services by name, rather than by physical location. For example, if you want to locate a printer, select the Chooser and then pick the printer by name, rather than by its AppleTalk address.

The Bay Networks AppleTalk router uses the Name Binding Protocol (NBP) and the Zone Information Protocol to map names of services to AppleTalk addresses.

When the router receives an NBP Broadcast Request packet for a named entity from an AppleTalk node, it refers to its zone list to see in which network the requested entity’s zone is located. If the zone is on the local netw ork, it broadcasts an NBP Lookup Request packet. If the zone is located on a different network, it sends out an NBP Forward Request packet toward the router connected to the network with the destination zone. Upon receiving a forward request, that router then broadcasts an NBP Lookup Request (Figure

NBP Broadcast Request NBP Lookup Request, and

NBP Forward Reply

Function

1-8).

NBP Lookup Reply

Function

NBP ID

AppleTalk Overview

Tuple Count

NBP ID

NBP Tuple

Function = 1 = BrRq Function = 2 = LkUpRq Function = 3 = FwdRq

NBP Tuple 1

NBP Tuple 2

NBP Tuple 3

APT0008A

Figure 1-8. NBP Packets

114048 Rev. A 1-13

Page 36

Configuring AppleTalk Services

An NBP named entity consists of the name, type, and zone name, where

• Name is the name assigned to the device that identiﬁes it on the network.

• Type speciﬁes the device type; for example, the type speciﬁed for a laser printer is identiﬁed by the type LaserWriter.

• Zone name speciﬁes the AppleTalk zone in which the device resides.

AppleTalk Echo Protocol (AEP)

The Bay Networks AppleTalk router supports the AppleTalk Echo Protocol (AEP), which allows the router to respond to echo packets it receives from other nodes on the network.

AppleTalk Update-based Routing Protocol (AURP)

The Bay Networks AppleTalk router supports the AppleTalk Update-based Routing Protocol (AURP), which pro vides an optional set of features that you can use with an AppleTalk Phase 2 network. AURP provides more efﬁcient use of network bandwidth, increased network security, and enables AppleTalk networks to exchange data through a tunnel.

Bay Networks supports three major AURP features:

• AURP tunneling to allow AppleTalk communications over existing wide-area Internet Protocol (IP) backbones

• Update-based routing table maintenance to reduce bandwidth use over a tunnel

• Hop count reduction to extend the current AppleTalk 15-hop limit

The following sections provide a brief overview of the AURP features that Bay Networks router software supports.

AURP T unneling

AURP tunneling lets you connect tw o or more pre viously unconnected AppleT alk internets over an IP internet (Figure 1-9). The sending router encapsulates each AppleTalk data packet in IP and delivers it to the router on the other side of the tunnel. The router receiving the encapsulated packet removes the IP header and forwards the packet to the appropriate destination using standard AppleTalk delivery mechanisms.

1-14 114048 Rev. A

Page 37

AppleTalk Overview

AppleTalk routers that connect to an AURP tunnel are exterior routers. Exterior routers function as AppleTalk routers within the AppleTalk internet, and as end nodes within the IP internet. Exterior routers assign unique domain identiﬁers (DI) to AppleTalk internets to distinguish between multiple AppleTalk internets connected to the same tunnel.

IP Internet

Tunnel

Exterior Router

AppleTalk

Internet

AppleTalk Internet

APT0009A

Figure 1-9. AURP Tunneling across an IP Internet

A Bay Networks AppleTalk router supports one fully connected or partially connected tunnel with multiple connections. In a fully connected tunnel, all exterior routers have connections to all other exterior routers in the tunnel and, as a result, have full access to all resources these routers provide (Figure 1-10).

114048 Rev. A 1-15

Page 38

Configuring AppleTalk Services

AppleTalk Internet

APT0010A

AppleTalk Internet

A sees B and C B sees A and C C sees A and B

Figure 1-10. Fully Connected Tunnel

In a partially connected tunnel, two or more exterior routers do not have a connection. In such a tunnel, routers without an explicit connection cannot see each other’s networks. This lets network administrators control the view and access that users have to the resources on various protected networks. An exterior router in a partially connected tunnel advertises only its local internet. It does not advertise network information learned through a different connection on the tunnel (Figure

1-11).

1-16 114048 Rev. A

Page 39

AppleTalk Overview

AppleTalk Internet

APT0011A

AppleTalk Internet

A sees B, not C B sees A and C C sees B, not A

Figure 1-11. Partially Connected Tunnel

Tickle Request and Tickle Acknowledgment packets maintain the connection between two exterior routers. When an exterior router receives an AppleTalk data packet destined for an end system located across the IP internet, the router encapsulates the packet with the following headers before forwarding the packet onto the IP internet:

• Data Link Header, which speciﬁes the data link frame information

• IP Header, which speciﬁes the source and destination IP address

• UDP Header, which speciﬁes the destination User Datagram Protocol (UDP) port

• Domain Header, which speciﬁes the source and destination AppleTalk domain identiﬁers (DIs); for AURP tunneling, DIs are derived from IP addresses

114048 Rev. A 1-17

Page 40

Configuring AppleTalk Services

A Domain Header consists of the following ﬁelds:

• Destination DI, which contains the DI of the e xterior router to which a packet is forwarded

• Source DI, which contains the DI of the exterior router that is forwarding a packet

• Version Number, which contains the value 0001

• Reserved, which is reserved for future use and contains the value 0000

• Packet Type, which contains the value 0002 to identify the data that follows as AppleTalk data, distinguishing it from other data, such as routing data (value

0003)

The receiving exterior router decapsulates the datagram, then forwards it to the destination AppleTalk end system. Figure data packet forwarded across an AURP tunnel.

1-12 shows the format of an AppleTalk

1-18 114048 Rev. A

Page 41

AppleTalk Overview

Data Link Header

IP Header

UDP Header

Dest DI

Src DI

0001

0000

0002

DDP Header

(13 b ytes)

AppleT alk Data

(0 to 586 b ytes)

Domain Header

APT0012A

Figure 1-12. AppleTalk Data Packet Forwarded across an AURP Tunnel

Update-based Routing Table Maintenance

Exterior routers connected to a tunnel use AURP to exchange routing information with other exterior routers connected to the same tunnel.

Note: Within its local AppleTalk internet, an exterior router uses Routing

Table Maintenance Protocol (RTMP) to maintain current routing information.

114048 Rev. A 1-19

Page 42

Configuring AppleTalk Services

When two exterior routers establish a connection via an AURP tunnel, they exchange complete routing information. Once the initial routing exchange takes place, there are no more complete routing table exchanges.

Instead, an exterior router only generates routing updates when an event occurs that changes its routing information, thus reducing the amount of routing protocol trafﬁc on the network. (Events that change routing information include network additions or deletions, metric changes, and next-hop changes.) In addition, the exterior router buffers updates until the next update interval occurs for the AURP connection.

Hop Count Reduction

When two AppleTalk networks communicate via a tunnel, the distance one of their packets must go to reach its destination can easily exceed the AppleTalk 15-hop limit. To ensure full access to resources beyond 15 hops, AURP provides a way to reduce the hop count within the DDP header of an AppleTalk packet. With Hop Count Reduction enabled, all nodes across the network appear reachable within the AppleTalk 15-hop limit.

Upon receiving an AppleTalk packet through a tunnel conﬁgured with Hop Count Reduction, AURP routers examine the routing table entry for that packet’s destination network. If the destination network’s distance plus the packet’s hop count exceed 15 hops, the AURP router reduces the hop count value of the packet to ensure delivery of the packet.

For example, an AppleTalk router with AURP conﬁgured receives an IP-encapsulated packet with a DDP header hop count ﬁeld containing a value of 7. Prior to sending the packet to its ﬁnal destination, the router checks the appropriate distance metric in its RTMP table and determines that the pack et must travel another 10 hops to reach its ﬁnal destination. The AppleTalk router then resets the hop count ﬁeld of the DDP header to a value of 5, allowing the packet to reach its destination within the AppleTalk router’s local network.

When using Hop Count Reduction on a tunneling port, an exterior router must represent all networks in its local internet as being only one hop away. Hop count reduction allows the router to send and maintain routing information about networks beyond the 15-hop limit, thus ensuring full connectivity.

1-20 114048 Rev. A

Page 43

For More Information

The following documents provide technical detail on AppleTalk protocol implementation:

• Sidhu, G., R. Andrews, and A. Oppenheimer. Inside AppleTalk. 2nd edition. Reading, Massachusetts: Addison-Wesley Publishing Company, 1990.

• Apple Computer. AppleTalk Update-Based Routing Protocol. Cupertino, California: Apple Computer, 1993.

• Apple Computer. The Design and Planning of Enterprise-Wide AppleTalk Internetworks. San Francisco, California: AppleTalk Networking Forum,

1993.

AppleTalk Overview

114048 Rev. A 1-21

Page 44

Page 45

Chapter 2

AppleTalk Implementation Notes

This chapter contains Bay Networks speciﬁc implementation notes that you should consider if you want to

• Conﬁgure AppleTalk interfaces on WAN media

• Conﬁgure seed router interfaces

• Specify interface costs

• Enable both AppleTalk routing and bridging on the same interface

• Specify zone information for interfaces (add or remove zones; edit network and zone list information; conﬁgure zone ﬁlters)

• Conﬁgure AppleTalk interfaces in a Token Ring network

• Conﬁgure AppleTalk interfaces in a non-fully meshed Frame Relay topology

• Reduce excess routing trafﬁc on a large AppleTalk network

• Add AppleTalk routers to a transitional network

• Conﬁgure A URP connections

114048 Rev. A 2-1

Page 46

Configuring AppleTalk Services

AppleTalk Interfaces over WAN Media

The Bay Networks AppleTalk implementation includes Frame Relay, Switched Multimegabit Data Services (SMDS), and Point-to-Point Protocol (PPP) support that conforms to the following:

• RFC 1294: Multiprotocol Interconnect over Frame Relay

• Oppenheimer , Alan. SMDSTalk: AppleTalk over SMDS. Apple Computer, August 17, 1992

• RFC 1378: The PPP AppleTalk Control Protocol (ATCP)

AppleTalk Running on Frame Relay or SMDS

When you enable AppleTalk on a Frame Relay or SMDS circuit, you must specify a MAC address and a broadcast address for the circuit using the WAN MAC Address and WAN Broadcast Address parameters. See the section “Editing

AppleTalk Interface Parameters” in Chapter 4 for instructions. If you do not

specify these values, then

• For Frame Relay circuits, the router broadcasts to all DLCIs

• For SMDS circuits, the router uses the addresses speciﬁed at the SMDS circuit level

Conﬁguring AppleTalk as a Nonextended Network over PPP

To make the Bay Networks AppleTalk software work with router software that uses nonextended network conﬁgurations over PPP (RFC 1378 compliant), you must conﬁgure the AppleTalk interface as a seed router for a nonextended network. (For more information about seed routers, see “Seed Router Interf later in this chapter.)

Chapter 3 describes how to initially conﬁgure an AppleTalk interface on a PPP circuit. To edit an AppleTalk interface you have already conﬁgured, see “Editing

AppleTalk Interface Parameters” in Chapter 4.

2-2 114048 Rev. A

aces”

Page 47

AppleTalk Implementation Notes

Make sure you conﬁgure the AppleTalk parameters as follows:

• Set the Network Start parameter to the desired value.

• Set the Network End parameter to 0, which indicates that the network is nonextended.

• Set the Default Zone parameter for the interface. The network can have only one zone, the Default Zone.

• Set the Network ID and the Node ID for the interface.

Figure

2-1 shows a sample AppleTalk Interface Conﬁguration window for a

nonextended conﬁguration. Note that in the ﬁgure, the Network End equals 0.

Note: If two routers are running Bay Networks Version 7.70 router software or

higher, and you want to conﬁgure an interface for AppleT alk o ver PPP on each router, both interfaces must be conﬁgured the same way for an extended or nonextended network.

Figure 2-1. AppleTalk Nonextended Conﬁguration over PPP

114048 Rev. A 2-3

Page 48

Configuring AppleTalk Services

Conﬁguring AppleTalk as an Extended Network over PPP

If you want to conﬁgure AppleTalk over PPP for an interface that is connected to a router running Bay Networks Version 5.70 or higher router software or Bay Networks Version 7.60 or higher router software, you must conﬁgure the AppleTalk interface as a seed router for an extended network. (For more information about seed routers, see “Seed Router Interf

Chapter 3 describes how to initially conﬁgure an AppleTalk interface on a PPP circuit. To edit an AppleTalk interface you have already conﬁgured, see “Editing

AppleTalk Interface Parameters” in Chapter 4.

Make sure you conﬁgure the AppleTalk parameters as follows:

• Set the Network Start and Netw ork End parameters. The network must have a range of one (for example, 4-4 or 10-10).

• Set the Default Zone. The network can have only one zone, the Default Zone.

• Set the Network ID and Node ID for the interface.

aces” later in this chapter.)

Figure

2-2 shows a sample AppleTalk Interface Conﬁguration window for an

extended conﬁguration. Note that in the ﬁgure, the Network Start and Network End are equal.

Note: If two routers are running Bay Networks Version 7.70 router software or

higher, and you want to conﬁgure an interface for AppleT alk o ver PPP on each router, both interfaces must be conﬁgured the same way for an extended or nonextended network.

2-4 114048 Rev. A

Page 49

AppleTalk Implementation Notes

Figure 2-2. AppleTalk Extended Conﬁguration over PPP

Seed Router Interfaces

If you specify a value for the Network Start parameter when enabling an AppleTalk interface, then the interface functions as a seed router. (If you do not set the Network Start parameter, then the interface is nonseed by default.)

In addition, a seed router interface requires you to

• Specify the Network End parameter.

• Specify the Default Zone parameter.

• Deﬁne a zone list. If there are multiple seed routers on the network, all must be conﬁgured with the

same values.

114048 Rev. A 2-5

Page 50

Configuring AppleTalk Services

You must conﬁgure the interface as a seed router interface if it is the only AppleTalk router on the network. If a seed router already is conﬁgured on this network, you can conﬁgure this interface to be a nonseed router.

Chapter 3 describes how to initially conﬁgure a seed router interface. To edit an AppleTalk interface you have already conﬁgured, see “Editing

Interface Parameters” in Chapter 4.

Interface Costs

You can assign a relative cost value to AppleTalk interfaces. When you specify a cost, the router adds it to the routes that the interface learns via RTMP data packets.

Since the AppleTalk router always chooses the least-cost (most direct) path to a destination, you can limit the use of an interface by assigning it a high cost.

Figure

process. In Example 1, when no cost values are assigned to any of the AppleTalk

interfaces, Router A always reaches Network 4-4 directly through Router C (because it advertises the least costly route).

2-3 demonstrates how interface cost affects the router’s decision-making

AppleTalk

As shown in Example 2, if an interface cost of 2 is assigned to Interface 3.1 (which increases the advertised hop count by 2), Router A now reaches Network 4-4 through Router B, because it advertises a lower cost route.

Note: The AppleTalk router does not route to networks that are more than 15

network hops away. Thus, when you assign an interface cost, make certain that the actual hop count, plus the interface cost you assign, does not exceed the 15-hop restriction.

For instructions on how to set the Cost parameter for an interface, see the section “Editing

2-6 114048 Rev. A

AppleTalk Interface Parameters” in Chapter 4.

Page 51

AppleTalk Implementation Notes

Network 1-1 Network 2-2

1-1

3-1

Network 5-5

Interface Cost Actual Hops to Hop Count Learned

1.1

3.1 0 1

Example 1. Router A's preferred path to Network 4-4 = 3.1.

Network 3-3

Network 4-4 2

by Interface 2

4-1

Network 4-4

Interface Cost Actual Hops to Hop Count Learned

Network 4-4 by Interface

1.1

3.1

Example 2. Router A's preferred path to Network 4-4 = 1.1.

0 21 3

APT0013A

Figure 2-3. Assigning Circuit Costs to AppleTalk Interfaces

114048 Rev. A 2-7

Page 52

Configuring AppleTalk Services

AppleTalk Routing and Bridging on the Same Interface

If you enable both AppleTalk routing and bridging on the same interface, conﬁgure a bridge ﬁlter on the interface to drop all AppleTalk Phase 2 AARP and DDP packets.

If you do not conﬁgure a ﬁlter, you may experience problems when you reboot the router. (This is because the bridge enables ahead of the AppleTalk router, causing packets to be bridged before AppleTalk routing starts.)

We suggest creating a ﬁlter that speciﬁes a drop (with no log) action on all SNAP packets with Ethertype ranges of 0x809B to 0x809B and 0x80F3 to 0x80F3. The hierarchical menu for the ﬁeld is as follows:

Data link – 802.2 SNAP – 802.2 SNAP Ethertype

See Conﬁguring Trafﬁc Filters and Protocol Prioritization for more information about how to construct ﬁlters for the bridge.

AppleTalk Zone Information

This section describes information speciﬁc to conﬁguring AppleTalk zone information.

Adding or Removing AppleTalk Zones

When a router initially learns about a new network, it sends out query packets requesting the network’s zone information. The router uses this information to update its zone table. However, because routers query for this information only the ﬁrst time they learn about a network, any changes later made to the network’s zone list do not propagate to other routers on the internet.

To add, remove, or change an AppleTalk zone from an AppleTalk interface’s zone list or default zone, follow this procedure:

1. Disable all AppleTalk router interfaces (both Bay Networks and

otherwise) that connect to the network for which the zone name change is being applied.

For example, in Figure Network 1-3, disable AppleTalk Interfaces 1.1, 1.2, and 1.3.

2-8 114048 Rev. A

2-4, to add the new zone name Blue to the zone list for

Page 53

AppleTalk Implementation Notes

Edit the interface’s zone list. See “Conﬁguring AppleTalk Zone Lists” in

Chapter 4 for instructions.

Make certain that you change the zone list for any other seed routers on the affected network as well.

3. Wait approximately 10 minutes.

This allows all routers on the AppleTalk internet to time out the network and zone information for the network from their zone lists.

Note: To expedite the aging of a network in an internet containing AURP

tunnels, you may need to manually reset AURP connections that have large update intervals.

4. Re-enable the router interfaces that connect to the network.

1.1

Network 1-3

Red Zone, White Zone

1.2

1.3

New Zone = Blue

Old Zone List = Red, White New Zone List = Red, White, Blue

APT0014A

Figure 2-4. Updating an AppleTalk Router’s Zone List

114048 Rev. A 2-9

Page 54

Configuring AppleTalk Services

Using AppleTalk Zone Filters

Bay Networks AppleTalk zone ﬁlters let network administrators control the zone information that Bay Networks routers distribute, providing a level of security unavailable through the standard AppleTalk protocol.

The Bay Networks AppleTalk implementation lets you conﬁgure zone ﬁlters on a per-interface basis. Use zone ﬁlters to

• Impose network security.

Zone ﬁlters can impose security measures by controlling which AppleTalk zones and networks are accessible to endstations on the network.

• Simplify a user’s network access.

Zone ﬁlters can screen out unwanted zones and reduce the number of zones on a user’s Chooser.

You conﬁgure zone ﬁlters by constructing an Include, Exclude, 5.X Include, or

5.X Exclude zone ﬁlter list for an interface.

• When you conﬁgure an Include zone ﬁlter list, the interface advertises that it

can reach only those zones speciﬁed on the list. This type of ﬁlter is useful if you want to ﬁlter out most of the zones that the router knows about.

• When you conﬁgure an Exclude zone ﬁlter list, the interface advertises that it

can reach all zones except those speciﬁed on the list. This type of ﬁlter is useful if you want to ﬁlter out only a few of the zones that the router knows about.

• When you conﬁgure a 5.X Include or 5.X Exclude zone ﬁlter list, the interface

advertises that it can reach only those zones allowed or denied on the list. However, the interface will advertise all networks, regardless of the zones in its zone ﬁlter list.

For instructions on conﬁguring zone ﬁlters, see “Conﬁ

Filters” in Chapter 4.

2-10 114048 Rev. A

guring AppleTalk Zone

Page 55

AppleTalk Implementation Notes

How Zone Filters Work

When you conﬁgure zone ﬁlters on an interface using the Exclude or Include options, the interface no longer sends out zone or network information about the ﬁltered zones.

• RTMP packets the interface generates do not contain the networks mapped to

the ﬁltered zones.

• ZIP GetZoneList response packets the interface sends out do not contain the

ﬁltered zones.

• NBP Broadcast Request packets the interface receives for the ﬁltered zones

are not propagated as Forward Request packets or Lookup packets by the interface.

• NBP Response packets are not routed if the source network number is from a

network with a zone that is to be ﬁltered.

When you are using the Exclude or Include options, be aware that if part of a network’s zone list is ﬁltered on a port, then the entire network is ﬁltered on that port. Within an AppleTalk network, a router must communicate all zone information about a network if it knows the network’s associated zone list.

Note: Communicating a partial zone list for a given network violates the

AppleT alk speciﬁcation and can result in ZIP storms. ZIP storms occur when a router receiving conﬂicting ZIP information from different sources continuously broadcasts ZIP requests onto locally attached network segments.

For example, the network administrator for the network shown in Figure

2-5

wants to impose a security ﬁlter that restricts all AppleTalk users, except those in the Human Resources zone, from accessing the Finance zone. To accomplish this, the administrator adds the Finance zone to the exclude zone ﬁlter list for Interface

3.1.

114048 Rev. A 2-11

Page 56

Configuring AppleTalk Services

A Zone

1-1

Finance Zone

Human Resources Zone

B Zone

3-1

2-2

3-3

Engineering Zone

Filter

Exclude Zone Filter List Networks Filtered

Finance 1-1

Figure 2-5. Conﬁguring Zone Filters with the Exclude Option

With the ﬁlter in place, the RTMP and ZIP packets that Interface 3.1 generates no longer advertise the Finance zone as being reachable. Any NBP Broadcast Request packets the interface receives for the Finance zone are not propagated as Forward Request packets or Lookup packets. As a result, the services of the Finance zone are no longer visible to end users in the Engineering zone and Sales zone.

4-4

Sales Zone

APT0015A

2-12 114048 Rev. A

Page 57

AppleTalk Implementation Notes

When you conﬁgure zone ﬁlters on an interface using the 5.X Exclude or 5.X Include options, the interface no longer sends out zone information about the ﬁltered zones:

• The interface sends out ZIP Reply packets that do not contain the ﬁltered

zones. If all the zones for a network are ﬁltered, then the default zone of the ﬁltering interface represents the network. However, if the network being queried is learned on the receiving interface of the ZIP Request packet, then the ZIP Reply packet must contain the correct zone for that network.

• The interface sends out ZIP GetZoneList Response packets that do not

contain the ﬁltered zones.

• The interface does not propagate NBP Broadcast Request packets for the

ﬁltered zones as Forward Request packets or Lookup packets.

Note: When you are using the 5.X Exclude or 5.X Include option, the

interface advertises all networks. The interface may not advertise the network with the complete zone list because some of the zones are ﬁltered. To avoid different sources advertising conﬂicting ZIP information, the 5.X Exclude and

5.X Include options do not support loop topologies.

For example, the network administrator for the network shown in Figure

2-6

114048 Rev. A 2-13

Page 58

Configuring AppleTalk Services

A Zone

1-1

Finance Zone

B Zone

5.X Exclude Zone Filter List Networks Associated with Zones Advertised for Zones in the Zone Filter List the Network for ZIP Reply

Finance

1-1

Human Resources Zone

3-1

Engineering Zone

Filter

2-2

3-3

Engineering (Default Zone

of Interface 3.1)

Figure 2-6. Conﬁguring Zone Filters with the 5.X Exclude Option

4-4

Sales Zone

APT0016A

With the ﬁlter in place, the ZIP packets that Interface 3.1 generates no longer advertise the Finance zone as being reachable. Any NBP Broadcast Request packets that the interface receives for the Finance zone are not propagated as Forward Request packets or Lookup packets. As a result, the services of the Finance zone are no longer visible to end users in the Engineering zone and Sales zone.

Zone Filter Rules

AppleTalk has several basic ﬁltering rules, or conditions that govern how zone ﬁltering works, depending on whether you use the Exclude, Include, 5.X Exclude, or 5.X Include options, as explained in the following sections.

2-14 114048 Rev. A

Page 59

AppleTalk Implementation Notes

Zone Filter Rules for the Exclude Option

Rule 1. The AppleTalk router always advertises its own network information.

For example, if the zone ﬁlter list shown in Figure

2-7 for Interface 3.1 is

expanded to include the Engineering zone, the router would still advertise zone and network information about Network 3-3 through Interface 3.1 in response to a GetZoneList or GetLocalZones command.

A Zone

1-1

Finance Zone

B Zone

Exclude Zone Filter List Networks Filtered Networks not Filtered

Human Resources Zone

3-1

Engineering Zone

Filter

2-2

3-3

Sales Zone

4-4

Finance

1-1

3-3 due to Rule 1

APT0017A

Figure 2-7. AppleTalk Zone Filters with the Exclude Option: Rule 1

Rule 2. The AppleTalk router always advertises the network information it learns on an interface back out that interface. The AppleTalk router advertises all zone information in response to a GetLocalZones Reply request. The router applies zone ﬁlters to corresponding network information in RTMP data packets, ZIP replies, GetZoneList replies, and NBP forward requests.

114048 Rev. A 2-15

Page 60

Configuring AppleTalk Services

For example, if the zone ﬁlter list shown in Figure 2-8 for Interface 3.1 were expanded to include the Sales zone, the router would still advertise Network 4-4 because it was learned about on Interface 3.1.

A Zone

1-1

Finance Zone

Exclude Zone Filter List Networks Filtered Networks not Filtered Finance, Engineering, 1-1 3-3, due to Rule 1,

Sales 4-4 due to Rule 2

Human Resources Zone

B Zone

3-1

Engineering Zone

Filter

2-2

3-3

Figure 2-8. AppleTalk Zone Filters with the Exclude Option: Rule 2

Rule 3. The AppleTalk router ﬁlters out all networks that reside in the ﬁltered zones.

4-4

Sales Zone

APT0018A

For example, Networks 10-10 and 20-20 sho wn in Figure

2-9 are both assigned to

the Marketing zone. If you add the Marketing zone to the zone ﬁlter list for Interface 3.1, then both Network 10-10 and Network 20-20 are ﬁltered out.

2-16 114048 Rev. A

Page 61

AppleTalk Implementation Notes

A Zone

1-1

Finance

B Zone

10-10

Marketing

Exclude Zone Filter List Networks Filtered

Marketing 10-10, 20-20

Human Resources

Filter

2-2

3-1

3-3

Engineering

Figure 2-9. AppleTalk Zone Filters with the Exclude Option: Rule 3

Rule 4. Depending on the network conﬁguration, Rule 3 can be amended by Rule

20-20

Marketing

4-4

Sales

APT0019A

For example, suppose that the network conﬁguration is like the one shown in

Figure

2-10. If you add the Marketing zone to the zone ﬁlter list for Interface 3.1,

the ﬁlter behaves differently than in the previous example. That is, the interface still ﬁlters out Network 10-10, because it belongs to the

Marketing zone. However, even though Network 20-20 also belongs to the Marketing zone, it is not ﬁltered out because it was learned about on this same interface (conforming to Rule 2).

114048 Rev. A 2-17

Page 62

Configuring AppleTalk Services

A Zone

1-1

Finance

B Zone

10-10

Marketing

Exclude Zone Filter List Networks Filtered Networks not Filtered

Marketing 10-10 20-20, due to Rule 2

Human Resources

Filter

2-2

3-1

3-3

Engineering

APT0020A

Figure 2-10. AppleTalk Zone Filters with the Exclude Option: Rule 4

Zone Filter Rules for the Include Option

Rule 1. The AppleTalk router always advertises its own network information.

20-20

Marketing

For example, if the Include zone ﬁlter list shown in Figure

2-11 for Interface 3.1

includes the Human Resources zone, the router would still advertise zones and network information about Network 3-3 out through Interface 3.1.

2-18 114048 Rev. A

Page 63

AppleTalk Implementation Notes

A Zone

1-1

Finance

B Zone

Include Zone Filter List Networks Advertised Zones Advertised

Human Resources Human Resources

2-2 (include list)

3-3 (Rule 1)

Human Resources

Filter

2-2

3-1

3-3

Engineering

APT0021A

Figure 2-11. AppleTalk Zone Filters with the Include Option: Rule 1

4-4

Sales

Rule 2. The AppleTalk router always advertises the network information it learns on an interface back out the interface.

For example, if the Include zone ﬁlter list shown in Figure

2-12 for Interface 3.1

includes the Human Resources zone, the router would still advertise zone and network information about Network 4-4 out through Interface 3.1.

114048 Rev. A 2-19

Page 64

Configuring AppleTalk Services

A Zone

1-1

Finance

B Zone

Filter

Include Zone Filter List Networks Advertised Zones Advertised

Human Resources

2-2 (in Include list) Human Resources 3-3 (Rule 1) Engineering 4-4 (Rule 2) Sales

Human Resources

3-1

2-2

3-3

Engineering

APT0022A

Figure 2-12. AppleTalk Zone Filters with the Include Option: Rule 2

4-4

Sales

Rule 3. The AppleTalk router advertises all network and zone information for networks that reside in the Include zone list.

For example, if the Include zone ﬁlter list shown in Figure

2-13 for Interface 3.1

includes the Human Resources zone, and Network 2-2 is associated with the Human Resources and Marketing zones, the router would advertise all zones assigned to Network 2-2 out through Interface 3.1.

2-20 114048 Rev. A

Page 65

AppleTalk Implementation Notes

A Zone

1-1

Finance

B Zone

10-10

Marketing

Include Zone Filter List Networks Advertised Zones Advertised Human Resources

2-2 (in Include list) Human Resources

3-3 (Rule 1) 4-4 (Rule 2) Sales

Human Resources

Filter

2-2

Marketing

3-1

3-3

Engineering

Marketing (Rule 3) Engineering

APT0023A

Figure 2-13. AppleTalk Zone Filters with the Include Option: Rule 3

4-4

Sales

Zone Filter Rules for the 5.X Exclude Option

Rule 1. The AppleTalk router always advertises its own network information.

For example, if the 5.X Exclude zone ﬁlter list shown in Figure

2-14 for Interface

3.1 includes the Finance and Engineering zones, the router would still advertise zone and network information about Network 3-3 out through Interface 3.1.

114048 Rev. A 2-21

Page 66

Configuring AppleTalk Services

A Zone

2-2

Human Resources

Finance

B Zone

3-1

3-3

Engineering

Filter

5.X Exclude Zone Filter List Networks Advertised Zones Advertised Finance, Engineering

2-2 Human Resources (not

in 5.X Exclude list)

3-3 Engineering (Rule 1)

Figure 2-14. AppleTalk Zone Filters with the 5.X Exclude Option: Rule 1

Rule 2. The AppleTalk router always advertises the network information it learns on an interface back out the interface.

For example, if the 5.X Exclude zone ﬁlter list shown in Figure

3.1 includes the Finance, Engineering, and Sales zones, the router would still advertise zone and network information about Network 4-4 out through Interface

3.1.

4-4

Sales

APT0024A

2-15 for Interface

2-22 114048 Rev. A

Page 67

AppleTalk Implementation Notes

A Zone

2-2

Human Resources

Finance

B Zone

3-1

3-3

Engineering

Filter

5.X Exclude Zone Filter List Finance, Engineering, Sales

Networks Advertised Zones Advertised

2-2

3-3

4-4

Human Resources (not in 5.X Exclude list)

Engineering (Rule 1)

Sales (Rule 2)

APT0025A

Figure 2-15. AppleTalk Zone Filters with the 5.X Exclude Option: Rule 2

Rule 3. The AppleTalk router advertises all networks. If the 5.X Exclude zone ﬁlter list speciﬁes all of the zones associated with a network, the router would advertise that network with the default zone of the ﬁltering interface.

For example, if the 5.X Exclude zone ﬁlter list shown in Figure

3.1 includes the Finance, Engineering, and Sales zones, the router would still advertise Network 1-1 out through Interface 3.1, except that the router would advertise the default zone of Interface 3.1, Engineering, with Network 1.1.

4-4

Sales

2-16 for Interface

114048 Rev. A 2-23

Page 68

Configuring AppleTalk Services

A Zone

1-1

Finance

B Zone

Filter

5.X Exclude Zone Filter List Networks Advertised Zones Advertised

Finance, Engineering, Sales

2-2 Human Resources (not

3-3 Engineering (Rule 1) 4-4 Sales (Rule 2)

1-1 Engineering (Default Zone

Human Resources

3-1

2-2

3-3

Engineering

in 5.X Exclude list)

of Interface 3.1, Rule 3)

4-4

Sales

APT0026A

Figure 2-16. AppleTalk Zone Filters with the 5.X Exclude Option: Rule 3

Zone Filter Rules for the 5.X Include Option

Rule 1. The AppleTalk router always advertises its own network information.

For example, if the 5.X Include zone ﬁlter list shown in Figure

2-17 for Interface

3.1 includes the Human Resources zone, the router would still advertise zone and network information about Network 3-3 out through Interface 3.1.

2-24 114048 Rev. A

Page 69

AppleTalk Implementation Notes

A Zone

2-2

Human Resources

Finance

B Zone

3-1

3-3

Engineering

Filter

5.X Include Zone Filter List Networks Advertised Zones Advertised Human Resources 2-2 Human Resources

(in 5.X Include list)

3-3 Engineering (Rule 1)

APT0027A

Figure 2-17. AppleTalk Zone Filters with the 5.X Include Option: Rule 1

Rule 2. The AppleTalk router always advertises the network information it learns on an interface back out the interface.

For example, if the 5.X Include zone ﬁlter list shown in Figure

3.1 includes the Human Resources zone, the router would still advertise zone and network information about Network 4-4 out Interface 3.1.

4-4

Sales

2-18 for Interface

114048 Rev. A 2-25

Page 70

Configuring AppleTalk Services

A Zone

2-2

Human Resources

Finance

B Zone

3-1

3-3

Engineering

Filter

5.X Include Zone Filter List Networks Advertised Zones Advertised Human Resources

2-2 Human Resources

(in 5.X Include list) 3-3 Engineering (Rule 1) 4-4 Sales (Rule 2)

APT0028A

Figure 2-18. AppleTalk Zone Filters with the 5.X Include Option: Rule 2

Rule 3. The AppleTalk router advertises all networks. If the 5.X Include zone list speciﬁes none of the zones associated with a network, the default zone of the ﬁltering interface is advertised with that network.

For example, if the 5.X Include zone ﬁlter list shown in Figure

3.1 includes the Human Resources zone, the router would still advertise Network 1-1 out through Interface 3.1, except that the router would advertise the default zone of Interface 3.1, Engineering, with Network 1-1.

4-4

Sales

2-19 for Interface

2-26 114048 Rev. A

Page 71

AppleTalk Implementation Notes

A Zone

1-1

Finance

B Zone

Filter

5.X Include Zone Filter List Networks Advertised Zones Advertised Human Resources 2-2 Human Resources

3-3 Engineering (Rule 1)

4-4 Sales (Rule 2) 1-1 Engineering (Default Zone

Human Resources

3-1

2-2

3-3

Engineering

(in 5.X Include list)

of Interface 3.1, Rule 3)

4-4

Sales

APT0029A

Figure 2-19. AppleTalk Zone Filters with the 5.X Include Option: Rule 3

AppleTalk Network Topology Information

This section describes information speciﬁc to AppleTalk network topologies.

Conﬁguring the AppleTalk Router to Source Route over Token Ring Networks

The Bay Networks AppleTalk router supports routing over Token Ring networks that contain one or more source-routing bridges.

114048 Rev. A 2-27

Page 72

Configuring AppleTalk Services

In a Source Routing network, every endstation that sends out a frame supplies the frame with the necessary route descriptors so that it can be source routed across the network. Thus, for routers to route packets across a Source Routing network, they must act like endstations, supplying route descriptors for each packet before they send the packet out onto the network (Figure

End Station 1

2-20).

DATA

Token

Ring

End Station 2

Packet sent from Router 1

Router 2

APT0030A

Router 1

WF2 WF1

Token

Ring

Bridge A

SNAP

0830 001A002B 0030

SNAP

AppleTalk

Source Route RIF

AppleTalk

DATA

SNAP

DATA

Token

Ring

Bridge B

Packet sent from End Station 1

AppleTalk

Packet sent from Router 2

Figure 2-20. AppleTalk Routers Source Routing across a Token Ring Network

2-28 114048 Rev. A

Page 73

AppleTalk Implementation Notes

With end-node support enabled, whenever a Bay Networks AppleTalk router receives a packet and determines that the packet’s next hop is located across a Source Routing network, the router does the following:

• Adds the necessary RIF information to the packet’s MAC header

• Sends the packet out onto the network where it is source routed toward the next hop

Upon receiving the packet from the Token Ring network, the peer router strips off the RIF ﬁeld and continues to route the packet toward the destination network address.

You conﬁgure source route end-node support for each individual routing protocol on a per-circuit basis. See “Editing for instructions.

AppleTalk Interface Parameters” in Chapter 4

Conﬁguring the AppleTalk Router in a Non-Fully Meshed Frame Relay Topology

If an AppleTalk interface connects to a non-fully meshed Frame Relay topology, and you want all of the routers connecting to the Frame Relay network to learn about each other, then you must

• Set the Enable Split Horizon parameter for this interface to Disable.

• Statically conﬁgure the Network ID and Node ID for each AppleT alk interface connecting to the Frame Relay network.

A non-fully meshed network is a WAN in which one or more routers do not have logically direct connections to all other routers. Figure non-fully meshed network with Split Horizon disabled. (A fully meshed network is a WAN in which all routers have a logically direct connection to each other.)

114048 Rev. A 2-29

2-21 shows a sample

Page 74

Configuring AppleTalk Services

Disable Split Horizon

1.2

Router A

1.1

Figure 2-21. AppleTalk Routers in a Non-Fully Meshed Frame Relay

Topology

Frame Relay

Network 1-1

1.3

Router B

Router C

APT0031A

For example, if you enable Split Horizon on Interface 1.1, then Router A learns about Router B and Router C; however, Router B does not learn about Router C (and vice versa). For all routers to learn about each other, you must disable Split Horizon for Interface 1.1, and you must statically conﬁgure Network ID and Node ID for Interfaces 1.1, 1.2, and 1.3.

See “Editing

AppleTalk Interface Parameters” in Chapter 4 for instructions on

how to set the Enable Split Horizon, Network ID, and Node ID parameters.

Reducing Excess Routing Trafﬁc on a Large AppleTalk Network

If you are adding Bay Networks AppleTalk routers to a large internet (such as one that has more than 200 routers and networks), consider the following network conﬁguration tips to reduce the amount of routing trafﬁc on your network:

• Keep the physical network topology as hierarchical as possible. Using a functional (organizational) hierarchy isolates groups on the network and reduces the amount of excess broadcast trafﬁc.

• Reduce the number of devices on a single physical network (or bridged network) by dividing the internet into a greater number of networks. This also helps to reduce the amount of trafﬁc that is broadcast to all nodes on the network.

• Limit the amount of Name Binding Protocol trafﬁc on the network; avoid conﬁguring the same zone on multiple networks. Instead, keep the ratio of zones to networks as close to 1-1 as possible.

2-30 114048 Rev. A

Page 75

AppleTalk Implementation Notes

Adding a Bay Networks AppleTalk Router to a Transitional Network

You can add the Bay Networks AppleTalk router to a transitional network (one that generates both AppleTalk Phase 1 and AppleTalk Phase 2 trafﬁc). For performance reasons, however, we do not recommend it.

If you choose to add the Bay Networks AppleTalk router to a transitional network, you must consider the following conﬁguration requirements:

• An AppleTalk Phase 1 to Phase 2 transitional router must reside on the internet.

• All deﬁned network ranges must consist of a single number; for example, 1-1 is a valid network range, while 1-5 is invalid.

• You can only specify a single zone name for each network.

AURP Information

Before conﬁguring AURP on a router, you must conﬁgure AppleTalk on at least one of the router’s circuits. Then you can use AURP to create a wide-area link between two or more AppleTalk networks.

Unlike other AppleTalk protocols, AURP does not require you to conﬁgure any circuits for AURP services. Use AURP to conﬁgure the router’s interface to another router that is set up for AURP services (known as the peer IP address).

Deciding When to Use AURP

You may ﬁnd AURP desirable when faced with one of the following scenarios:

• You want to link two or more AppleTalk networks across an existing IP internet.

• You want to reduce the amount of RTMP trafﬁc on an AppleTalk network.

• You have a large AppleTalk network that is approaching the 15-hop AppleTalk limit.

If possible, use AURP without RTMP in a nonloop topology.

114048 Rev. A 2-31

Page 76

Configuring AppleTalk Services

Note that AURP supports the following AppleTalk commands over the IP connecting network:

• Open request and response

• Routing Info request, response, and ack

• Zone Information request and response

• Router down notiﬁcation

• Tickle and Tickle ack (based on conﬁgurable timer)

AURP does not support the following AppleTalk commands over the IP connecting network:

• GetDomainZoneList request and response

• GetZonesNet request and response

In addition, the following features are not available in the Bay Networks implementation of AURP:

• Loop detection

• Network number remapping

• Conﬁgured alternative backup paths

• Network hiding

The following sections provide general guidelines for understanding and using some of the most important AURP parameters.

Setting the Update Rate

You should carefully consider how often you want to update your AppleTalk network. A smaller update rate (for example, 10 seconds) causes routers to conver ge more quickly on a netw ork, making most changes to the network appear quickly in the Chooser application. Though a smaller update rate provides users with quick access to any zones added to a network, it may also prove to be expensive (for example, in a dial-on-demand conﬁguration, or over Frame Relay).

2-32 114048 Rev. A

Page 77

AppleTalk Implementation Notes

A larger update rate (for example, 1 hour) causes routers to con v erge less quickly, making changes to the network appear less quickly in the Chooser application. Zones may still appear in the Chooser even though their associated networks are no longer reachable across the tunnel. Also, new network information does not become accessible until the update occurs. This could prove frustrating for some users.

For information on editing the Update Rate parameter, refer to “Editing AURP Parameters” in Chapter 4.

AURP uses the following packets to update its AppleTalk routing information:

• Routing Information Update (RI-Upd)

• Routing Information Request (RI-Req)

• Routing Information Response (RI-Rsp)

• Routing Information Acknowledgment (RI-Ack)

• Zone Information Request (ZI-Req)

• Zone Information Response (ZI-Rsp)

Setting the Last Heard From Timeout

The AppleTalk router uses the Last Heard From Timeout parameter to periodically check that the other end of the connection is up. If the router does not receive an RI-Upd, RI-Rsp, or ZI-Rsp packet within the Last Heard From T imeout period, it sends a Tickle Request and expects a Tickle Acknowledgment.

If the router does not receive the acknowledgment within the Command Timeout period, the router repeats its Tickle Request up to the Command Retries amount. If the router does not receive an acknowledgment, the connection is closed.

A large Last Heard From Timeout value may postpone the discovery of a failed connection by an exterior router. If you are using AURP to create an AppleTalk wide area network, you may want to increase the value to an hour (3600 seconds) if the WAN is relatively stable. Howev er, if you know a network may be unstable, you may want to decrease this value to as little as 30 seconds to ensure that you are aware of any disruptions in service.

For information on editing the Last Heard From Timeout parameter, refer to “Editing AURP Parameters” in Chapter 4.

114048 Rev. A 2-33

Page 78

Configuring AppleTalk Services

Setting the Hop Count Reduction

Enable hop count reduction only when the diameter of your network is greater than 15 hops.

If you use hop count reduction, make sure you do not create a network loop like the one shown in Figure AppleTalk networks that are linked by an AURP tunnel.

2-22. Hop count reduction can only take place across two

Tunnel

APT0032A

Figure 2-22. Network Loop

For information on editing the Hop Count Reduction parameter, refer to “Editing AURP Parameters” in Chapter 4.

Setting the Command Timeout and Command Retries

The Command Timeout speciﬁes the amount of time to wait for an acknowledgment before retrying the command. The Command Retries parameter speciﬁes how many attempts are made before the connection is considered closed. For a typical network (that is, a network that is relatively stable), the recommended Command Timeout value is 3 seconds. If a network is busy or requires long-distance travel, larger values may be required.

For information on editing the Command Timeout and Command Retries parameters, refer to “Editing AURP Parameters” in Chapter 4.

2-34 114048 Rev. A

Page 79

Setting Zone Filters

See the section “AppleTalk Zone Information” in this chapter. AURP zone ﬁlters work the same way as AppleTalk zone ﬁlters.

Setting the Interface Cost

See the section “Interface Costs” in this chapter. The AURP interface cost parameter works the same way as the AppleTalk Interface Cost parameter.

AppleTalk Dial-on-Demand Routing

In addition to supporting standard AURP functionality, Bay Networks software enables users to combine AURP and IP dial-on-demand routing to provide dial-on-demand routing for AppleTalk networks. This service allows the Bay Networks router to activate the physical connection for a circuit only when retransmitting data over the line, thus signiﬁcantly reducing your line costs.

The dial-on-demand service enables more efﬁcient use of modems. Because modems usually require between 30 and 60 seconds to make a connection, you must increase AURP’s default timeout and retry values if you intend to use a modem.

AppleTalk Implementation Notes

To enable AppleTalk dial-on-demand routing with Bay Networks software, use Site Manager to modify the following conﬁguration parameters:

1. Conﬁgure all the necessary parameters for IP dial-on-demand r outing on

the WAN interface being used for AppleTalk dial-on-demand routing.

2. Conﬁgure the AURP connection(s) for trafﬁc using the WAN interface

conﬁgured for dial-on-demand routing with the following parameters deﬁned:

a. Modify the A ppleTalk timeout and retry intervals (the default is three

tries with a 3-second interval) to slightly exceed the connect delay characteristics of the modem being used for dial-on-demand routing.

For example, if the modem takes 45 seconds to connect, set the timeout and retry parameters so that the AURP connection does not time out before the modem connects; for example, eight tries with an 8-second interval between tries (a total of 64 seconds, which exceeds the 45-second modem timeout).

114048 Rev. A 2-35

Page 80

Configuring AppleTalk Services

b. Set the AURP Update Rate timer to a large value to prevent topology

change information from initiating a dial-on-demand session.

A small value (for example, 5 minutes) could potentially result in a call every 5 minutes, depending on the stability of the network. A larger value (for example, 24 hours) results in fewer calls due to routing updates, but also greatly increases the amount of time before the peer router (and other routers in its local internet) learns about network changes over the tunnel.

c. Increase the A URP Last Heard From Timeout inter val to a high value

to prevent Tickle packets from initiating a dial-on-demand connection.

The AURP connection attempts to send a Tickle if it has not heard from the peer within this interval. A Last Heard From Timeout of 24 hours results in (at least) one call per day.

For more information on conﬁguring dial-on-demand services, see Conﬁguring Dial Services.

2-36 114048 Rev. A

Page 81

Chapter 3

Enabling AppleTalk Services

This chapter describes how to enable AppleTalk services. It assumes you have read Conﬁguring Routers and that you have

1. Opened a conﬁguration ﬁle

2. Speciﬁed router hardware if this is a local mode conﬁguration ﬁle

3. Selected the link or net module connector on which you are enabling

AppleTalk, or conﬁgured a WAN circuit if this connector requires one

When you enable AppleTalk services, you must conﬁgure a subset of all AppleTalk parameters. The Conﬁguration manager supplies default values for the remaining parameters. If you want to edit these default values, refer to Chapter 4, “Editing

For each AppleTalk parameter, this manual provides information about default settings, valid parameter options, the parameter function, instructions for setting the parameter, and the Management Information Base (MIB) object ID.

The Technician Interface lets you modify parameters by issuing commands that specify the MIB object ID. This process is equivalent to modifying parameters using Site Manager. For more information about using the Technician Interface to access the MIB, refer to Using Technician Interface Software.

Caution: The Technician Interface does not v erify that the value you enter for

a parameter is valid. Entering an invalid value can corrupt your conﬁguration.

AppleTalk Parameters.”

set and commit

114048 Rev. A 3-1

Page 82

Configuring AppleTalk Services

Enabling AppleTalk on an Interface

If you enable AppleTalk routing services on an interface, the AppleTalk Interface Conﬁguration window appears (Figure

3-1).

Figure 3-1. AppleTalk Interface Conﬁguration Window

Specify whether this interface functions as a seed or nonseed router:

• A seed router supplies the Network Start, Network End, Default Zone, and Zone List information for all other nonseed routers on this network. Each network must contain at least one seed router. To conﬁgure a seed router interface, specify the Network Start, Network End, and Default Zone and Zone List (if multiple zones are to be conﬁgured on this interface). Then click on Apply, followed by Done. See the parameter descriptions that follow.

• A nonseed router acquires its Network Start, Netw ork End, Default Zone, and Zone List information from the other seed routers on the network. To conﬁgure a nonseed router interface, simply accept all of the default parameters and click on Done.

3-2 114048 Rev. A

Page 83

Enabling AppleTalk Services

For information on editing all of the parameters in the AppleTalk Interface Conﬁguration window, refer to Chapter 4.

Parameter: Network Start

Default: 0

Range: 0 to 65279

Function: Speciﬁes the lower boundary (minimum) of the range of network

numbers available for use by nodes on the network to which this interf ace connects.

This parameter’s setting determines whether this interface functions as a seed or nonseed router.

Instructions: To conﬁgure this interface as a nonseed router, accept the default, 0.

To conﬁgure this interface as a seed router, specify this parameter as follows:

– If this is the only seed router on the network, determine the network

range for this interface, and enter the lower boundary network number.

– If there are already seed routers on the network, enter the same

Network Start value that is conﬁgured on all other seed routers.

MIB Object ID: 1.3.6.1.4.1.18.3.5.4.3.1.13

Note: If you specify a Network Start other than the default, 0, the router

automatically becomes a seed router and you must also specify values for the Network End and Default Zone parameters.

114048 Rev. A 3-3

Page 84

Configuring AppleTalk Services

Parameter: Network End

Default: 0

Range: 0 to 65279

Function: Speciﬁes the upper boundary (maximum) of the range of network

numbers available for use by nodes on the network to which this interf ace connects.

You use this parameter with the Network Start parameter to help deﬁne a seed router. If you have not speciﬁed a Network Start for this interface, this parameter is ignored.

Instructions: To conﬁgure this interface as a nonseed router, accept the default, 0.

To conﬁgure this interface as a seed router, specify the Network End as follows:

– If this is the only seed router on the network, determine the network

range for this interface, and enter the upper boundary network number.

– If there are already seed routers on the network, enter the same

Network End value that is conﬁgured on all other seed routers.

MIB Object ID: 1.3.6.1.4.1.18.3.5.4.3.1.14

3-4 114048 Rev. A

Page 85

Enabling AppleTalk Services

Parameter: Default Zone

Default: None

Options: Any valid zone name

Function: Speciﬁes the name of the default zone to which all new nodes are

assigned when they ﬁrst start up on this network. This parameter is used in conjunction with the Network Start and

Network End parameters to help deﬁne a seed router. If you have not

speciﬁed a Network Start for this interface, this parameter is ignored.

Instructions: To conﬁgure this interface as a nonseed router, leave this ﬁeld blank.

To conﬁgure this interface as a seed router, specify the Default Zone as follows:

– If this is the only seed router on the network, enter any valid Default

Zone name.

– If there are already seed routers on the network, enter the same

Default Zone name as is conﬁgured on all other seed routers.

A valid zone name can consist of a maximum of 32 characters and can include any character except an asterisk (*). See “Using Nonprintable Characters in AppleTalk Zone Names” in this chapter.

MIB Object ID: 1.3.6.1.4.1.18.3.5.4.3.1.15

Conﬁguring the Zone List

To conﬁgure a Zone List, you must add zones to the list. Complete the following steps:

1. Click on Zone List in the AppleTalk Interface Conﬁguration window

e 3-1).

(Figur

The AT Zone Conﬁguration window appears (Figure

114048 Rev. A 3-5

3-2).

Page 86

Configuring AppleTalk Services

Figure 3-2. AT Zone Conﬁguration Window

Click on Add.

The AppleTalk Zone Conﬁguration window appears (Figure

Figure 3-3. AppleTalk Zone Conﬁguration Window

Enter a name for the zone in the Zone Name box and click on OK.

3-3).

You return to the AT Zone Conﬁguration window.

3-6 114048 Rev. A

Page 87

Enabling AppleTalk Services

Either repeat Steps 2 and 3 for each zone you want to add, or click on

Done to exit the window.

Note: The default zone should not appear in the Zone List.

Using Nonprintable Characters in AppleTalk Zone Names

Note: To enter nonprintable characters in AppleTalk zone names, you must

access the Conﬁguration Manager tool in local or remote mode. You cannot enter nonprintable characters if you are using dynamic mode.

Using nonprintable characters in AppleTalk zone names requires some additional steps. Enter nonprintable characters into the Default Zone ﬁeld or Zone Name ﬁeld as follows:

1. Type \xx, where xx is the two-hexadecimal-digit representation of each

nonprintable character, as shown in the AppleTalk character set mapping.

Type two backslashes (\\) to indicate a literal backslash. The router counts \\ as a single character.

2. Click on Apply.

3. Save the conﬁguration.

4. Transfer the conﬁguration ﬁle to the router, using the Router Files

Manager tool if the Conﬁguration Manager is in local conﬁguration mode.

5. Reboot the router with the new conﬁguration ﬁle.

114048 Rev. A 3-7

Page 88

Configuring AppleTalk Services

Caution: Nonprintable characters in these parameters appear as different

characters when you transfer the ﬁle to the router and reopen it using the Conﬁguration Manager. SNMP translates the characters when transferring the conﬁguration to Site Manager.

To edit Default Zone or Zone List parameters where you previously saved nonprintable characters, overtype the zone name and retype the nonprintable characters, following the steps in this section.

Conﬁguring AURP

Before conﬁguring AURP on a router, you must conﬁgure AppleTalk on at least one of the router’s circuits. Once you ha v e conﬁgured an AppleTalk interf ace, you can use AURP to create a wide-area link between two or more AppleTalk networks.

To conﬁgure AURP global parameters, begin at the Conﬁguration Manager window and proceed as follows:

1. Select Protocols > AppleTalk > AURP > Global.

The Edit Apple AURP Global Parameters window appears (Figure

Figure 3-4. Edit Apple AURP Global Parameters Window

Set the Enable parameter to Enable.

3-8 114048 Rev. A

3-4).

Page 89

Enter the appropriate IP address (using dotted decimal notation) in the

Local IP Address ﬁeld.

4. Click on OK to exit the window and save your changes when you are

ﬁnished.

Parameter: Enable

Default: Enable

Options: Enable | Disable

Function: Enables or disables AURP on the router.

Instructions: Set to Enable to globally enable AURP.

MIB Object ID: 1.3.6.1.4.1.18.3.5.4.8.2

Parameter: Local IP Address

Default: None

Enabling AppleTalk Services

Options: Any valid 32-bit IP address in dotted decimal notation

Function: Identiﬁes an IP interface on the router. This is the IP interface used for

AURP.

Instructions: Enter the IP address of the interface on this router that AURP should use.

MIB Object ID: 1.3.6.1.4.1.18.3.5.4.8.5

T o conﬁgure the AURP connection, enter the IP address for the remote peer. T o do this, begin at the Conﬁguration Manager window and proceed as follows:

1. Select Protocols > AppleTalk > AURP > Interfaces.

The AT AURP Interface Conﬁguration window appears (Figure

114048 Rev. A 3-9

3-5).

Page 90

Configuring AppleTalk Services

Figure 3-5. AT AURP Interface Conﬁguration Window

Click on Add.

The AppleTalk AURP Conﬁguration window appears (Figure

Figure 3-6. AppleTalk AURP Conﬁguration Window

3-10 114048 Rev. A

3-6).

Page 91

Enabling AppleTalk Services

Enter the appropriate IP address in the Remote AURP IP Address ﬁeld

and click on OK.

The AT AURP Interface Conﬁguration window reappears.

4. Repeat Steps 2 and 3 to add additional remote peers to the AURP

connection.

5. Click on Done to exit the window.

For information on customizing AURP service or conﬁguring AURP zone ﬁlter lists, refer to Chapter 4.

Parameter: Remote AURP IP Address

Default: None

Options: Any valid 32-bit IP address

Function: Identiﬁes the peer’s IP address for the AURP connection.

Instructions: Enter an IP address using dotted decimal notation.

MIB Object ID: 1.3.6.1.4.1.18.3.5.4.9.1.14

114048 Rev. A 3-11

Page 92

Page 93

Chapter 4

Editing AppleTalk Parameters

Once you have enabled an AppleTalk interface, you can use Site Manager to edit AppleTalk parameters and customize AppleTalk services.

Use Site Manager to

• Edit AppleTalk global parameters

• Edit AppleTalk interface parameters

• Conﬁgure AppleTalk zone lists

• Change the AppleTalk Default Zone

• Conﬁgure AppleTalk zone ﬁlters

• Select the Name Binding Protocol interface

• Globally delete AppleTalk

• Edit AURP global parameters

• Edit AURP interface parameters

• Edit the AURP zone ﬁlter list

114048 Rev. A 4-1

Page 94

Configuring AppleTalk Services

Accessing AppleTalk Parameters

You can access and edit the AppleTalk parameters for all AppleTalk interfaces conﬁgured on the router.

Note: Before you can edit the parameters, you must have already conﬁgured at

least one AppleTalk interface. To conﬁgure an AppleTalk interface, or to add additional interfaces, refer to Chapter 3.

You access all AppleTalk parameters from the Conﬁguration Manager window

(Figure 4-1). Refer to Conﬁguring Routers for instructions on accessing this

window.

Figure 4-1. Conﬁguration Manager Window

Editing the AppleTalk Global Parameter

To edit the AppleTalk global parameter, begin at the Conﬁguration Manager window and proceed as follows:

1. Select Protocols > AppleTalk > Global.

The Edit AppleTalk Global Parameters window appears (Figure

4-2 114048 Rev. A

4-2).

Page 95

Editing AppleTalk Parameters

Figure 4-2. Edit AppleTalk Global Parameters Window

Set the Enable parameter to Disable or Enable, using the following

parameter description as a guide.

3. Click on OK to exit the window and save your changes when you are

ﬁnished.

Parameter: Enable

Default: Enable

Options: Enable

| Disable

Function: Enables or disables AppleTalk on the entire Bay Networks router.

Instructions: Set to Disable if you want to disable AppleTalk globally.

MIB Object ID: 1.3.6.1.4.1.18.3.5.4.1#2

Editing AppleTalk Interface Parameters

To edit an AppleTalk interface, begin at the Conﬁguration Manager window and proceed as follows:

1. Select Protocols > AppleTalk > Interfaces.

The AT Interface Conﬁguration window appears (Figure

114048 Rev. A 4-3

4-3).

Page 96

Configuring AppleTalk Services

Figure 4-3. AT Interface Conﬁguration Window

Click on the interface you want to edit.

3. Edit those parameters you want to change, using the following parameter

descriptions as a guide.

4. Click on Apply to implement your changes.

5. Click on Done to exit the window.

Note: When you reconﬁgure an interface in dynamic conﬁguration mode,

AppleTalk restarts on that interface.

4-4 114048 Rev. A

Page 97

Editing AppleTalk Parameters

Parameter: Enable

Default: Enable

Options: Enable

| Disable

Function: Enables or disables AppleTalk on this interface.

Instructions: Set to Disable only if you want AppleTalk disabled on this interface (for

example, if you are editing the interface’s zone list).

MIB Object ID: 1.3.6.1.4.1.18.3.5.4.3.1#2

Parameter: Network Start

Default: 0

Range: 0 to 65279

Function: Speciﬁes the lower boundary (minimum) of the range of network

numbers that are available for use by nodes on the network to which this interface connects.

This parameter’s setting determines whether this interface functions as a seed or nonseed router.

Instructions: To conﬁgure this interface as a nonseed router, accept the default, 0.

To conﬁgure this interface as a seed router, specify the Network Start parameter as follows:

– If this is the only seed router on the network, determine the network

range for this interface and enter the lower boundary network number here.

– If there are already seed routers on the network, enter the same

Network Start value that is conﬁgured on all other seed routers.

MIB Object ID: 1.3.6.1.4.1.18.3.5.4.3.1#13

Note: If you specify a Network Start other than the default 0, then

(1) the router becomes a seed router automatically, and (2) you must also specify values for the Network End and Default Zone parameters.

114048 Rev. A 4-5

Page 98

Configuring AppleTalk Services

Parameter: Network End

Default: 0

Range: 0 to 65279

Function: Speciﬁes the upper boundary (maximum) of the range of network

numbers that are available for nodes to use on the network to which this interface connects.

This parameter is used with the Network Start parameter to help deﬁne a seed router. If you have not speciﬁed a Network Start, this parameter is ignored.

Instructions: To conﬁgure this interface as a nonseed router, accept the default, 0.

To conﬁgure this interface as a seed router, specify the Network End parameter as follows:

– If this is the only seed router on the network, determine the network

range for this interface and enter the upper boundary network number here.

– If there are already seed routers on the network, enter the same

Network End value that is conﬁgured on all other seed routers.

MIB Object ID: 1.3.6.1.4.1.18.3.5.4.3.1#14

4-6 114048 Rev. A

Page 99

Editing AppleTalk Parameters

Parameter: Default Zone

Default: None

Options: Any valid zone name

Function: Speciﬁes the name of the Default Zone where all new nodes are assigned

when they ﬁrst start on this network. This parameter is used with the Network Start and Network End

parameters to help deﬁne a seed router. If you have not speciﬁed a Network Start, this parameter is ignored.

Instructions: To conﬁgure this interface as a nonseed router, leave this ﬁeld blank.

To conﬁgure this interface as a seed router, specify the Default Zone as follows:

– If this is the only seed router on the network, enter any valid Default

Zone name.

– If there are already seed routers on the network, enter the same

Default Zone name conﬁgured on all other seed routers.

A valid zone name can consist of up to 32 characters and can include any character except an asterisk (*). For more information, refer to “Using

Nonprintable Characters in AppleTalk Zone Names” in Chapter 3.

MIB Object ID: 1.3.6.1.4.1.18.3.5.4.3.1#15

Parameter: Network ID

Default: 0

Range: 0 to 65279

Function: Identiﬁes the network number of the network to which this interface

connects.

Instructions: We recommend accepting the default, 0, in which case the router

dynamically acquires a Network ID and Node ID for the interface during startup (thus ensuring that the AppleTalk address for this interface is unique within the network).

If you change the default value, make certain that the number you specify is within the correct network range. The router then uses the Network ID that you specify.

MIB Object ID: 1.3.6.1.4.1.18.3.5.4.3.1#12

114048 Rev. A 4-7

Page 100

Configuring AppleTalk Services

Note: If the AppleTalk address (Network ID.Node ID) matches that of any

other node on the internet, the interface is automatically disabled.

Parameter: Node ID

Default: 0

Range: 0 to 253

Function: Identiﬁes the node number assigned to this interface.

Instructions: We recommend accepting the default, 0, in which case the router

dynamically acquires a Network and Node ID for the interface during startup (thus ensuring that the AppleTalk address for this interface is unique within the network).

If you change the default value, the router uses the Node ID you specify.

MIB Object ID: 1.3.6.1.4.1.18.3.5.4.3.1#11

Parameter: Interface Cost

Default: 0

Range: 0 to 15

Function: Speciﬁes the additional number of hops (cost) added to routes that this

interface learns via RTMP data packets.

Instructions: If you want to limit the use of an interface, assign a high cost. If you do

not want to limit the use of an interface, assign a low cost.

MIB Object ID: 1.3.6.1.4.1.18.3.5.4.3.1#79

4-8 114048 Rev. A

Avaya AppleTalk User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Contents

Figures

Tables

About This Guide

Before Y ou Begin

Conventions

Acronyms

Ordering Bay Networks Publications

Technical Support and Online Services

Bay Networks Customer Service

Bay Networks Information Services

W orld Wide Web

Customer Service FTP

Support Source CD

CompuServe

InfoFACTS

How to Get Help

AppleTalk Networking

AppleTalk Addresses

AppleTalk Zones

Seed Routers and Nonseed Routers

How the Bay Networks AppleTalk Router Works

AppleTalk Link Access Protocols (TLAP and ELAP)

AppleTalk Address Resolution Protocol (AARP)

Datagram Delivery Protocol (DDP)

Routing Table Maintenance Protocol (RTMP)

Zone Information Protocol (ZIP)

Name Binding Protocol (NBP)

AppleTalk Echo Protocol (AEP)

AppleTalk Update-based Routing Protocol (AURP)

AURP T unneling

Update-based Routing Table Maintenance

Hop Count Reduction

For More Information

AppleTalk Interfaces over WAN Media

AppleTalk Running on Frame Relay or SMDS

Seed Router Interfaces

Interface Costs

AppleTalk Routing and Bridging on the Same Interface

AppleTalk Zone Information

Adding or Removing AppleTalk Zones

Using AppleTalk Zone Filters

How Zone Filters Work

Zone Filter Rules

Zone Filter Rules for the Exclude Option

Zone Filter Rules for the Include Option

Zone Filter Rules for the 5.X Exclude Option

Zone Filter Rules for the 5.X Include Option

AppleTalk Network Topology Information

Adding a Bay Networks AppleTalk Router to a Transitional Network

AURP Information

Deciding When to Use AURP

Setting the Update Rate

Setting the Last Heard From Timeout

Setting the Hop Count Reduction

Setting the Command Timeout and Command Retries

Setting Zone Filters

Setting the Interface Cost

AppleTalk Dial-on-Demand Routing

Enabling AppleTalk on an Interface

Using Nonprintable Characters in AppleTalk Zone Names

Accessing AppleTalk Parameters

Editing the AppleTalk Global Parameter

Editing AppleTalk Interface Parameters