Cisco OS AppUeTalk and NovelU IPX Configuration Guide
Release 12.2
Documentation also available on CD-ROM and the World Wide Web
SYSTEMS Cisco Reader Comment Card
General Information
Years of with Cisco Years of networking experience ______experience products
have these network types fl LAN fl Backbone WAN LI Other
have these Cisco products Switches Routers Other specify models
perform these types of tasks 111W installation and/or maintenance S/W configuration Network management LI Other ______
use these types of documentation 111W installation H/W configuration S/W configuration
Command reference Quick reference Release notes Online help Other
access this information through Cisco.com CD-ROM Printed docs Other ______
prefer this access method ______
use the following three product features the most
Document Information
Document Title Cisco lOS AppleTalk and Novell IPX Configuration Guide
Part Number 78-11734-01 S/W Release if applicable Release 12.2
On scale of 15 being the best please let us know how we rate in the following areas
The document is written at my technical The information is accurate
level of understanding
The document is complete The information wanted was easy to find
useful The information is well organized The information found was to my job
Please comment on our lowest scores
Mailing Information
Company Name Date
Contact Name Job Title
Mailing Address
ZIP/Postal Code City State/Province
Country Phone Extension
Fax E-mail
No Can we contact you further concerning our documentation LI Yes LI
e-mail to or fax to 408-527-8089 You can also send us your comments by [email protected] by NO POSTAGE NECESSARY
IF MAILED
IN THE UNITED STATES
BUSINESS REPLY MAIL FIRST-CLASS MAIL PERMIT NO 4631 SAN JOSE CA
POSTAGE WILL BE PAID BY ADDRESSEE
ATTN DOCUMENT RESOURCE CONNECTION CSCO SYSTEMS NC 170 WEST TASMAN DRIVE SAN JOSE CA 95134-9883
II II Corporate Headquarters Cisco Systems Inc 170 West Tasman Drive San Jose CA 95134-1706 USA http//wwwcisco.com Tel 408 526-4000 800 553-NETS 6387 Fax 408 526-4100
Customer Order Number DOC-781 1734
Text Part Number 78-11734-01 TIlE SPECIFICATIONS AN INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE ALL STATEMENTS INFORMATION AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND EXPRESS OR IMPLIED USERS MUST TAKE FULL RESPONSIBILiTY FOR THEIR APPLICATION OF ANY PRODUCTS
THE SOFIWARE LICENSE AJID LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE IF YOU ARE UNABLE TO LOCATE THE SOFTWARE UCENSE OR LIMITED WARRANTY CONTACT YOUR CISCO REPRESENTATIVE FOR COPY
The Cisco implementation of TCP header compression is an adaptation of program developed by the University of California Berkeley UCB as part of
domain version the All reserved of the of California UCBs public of UNIX operating system rights Copyright 1981 Regents University
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED AS IS WITH ALL FAULTS CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES EXPRESSED OR IMPLIED INCLUDING WITHOUT LIMITATION THOSE OF MERCHANTABILITY FITNESS FOR PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM COURSE OF DEALING USAGE OR TRADE PRACTICE
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT SPECIAL CONSEQUENTIAL OR INCIDENTAL DAMAGES INCLUDING WITHOUT LIMITATION LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABIUTY TO USE THIS MANTJAL EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES
AccessPath AtmDirector Browse with Me CCDA CCDE CCDP CCIE CCNA CCNP CCSI CD-PAC CiscoLink the Cisco Net Works logo the Cisco
Powered Network logo Cisco Systems Networking Academy the Cisco Systems Networking Academy logo Fast Step Follow Me Browsing FormShare
FrameShare GigaStack IGX Internet Quotient IP/VC iQ Breakthrough iQ Expertise iQ FastTrack the iQ Logo iQ Net Readiness Scorecard MGX the Networkers logo Packet PIX RaIeMUX ScriptBuilder ScriptShare SlideCast SMARTneI TransPath Unity Voice LAN Wavelength Router and
WebViewer are trademarks of Cisco Systems Inc Changing the Way We Work Live Play and Learn Discover All Thats Possible and Empowering the Internet Generation are service marks of Cisco Systems Inc and Aironet ASIST BPX Catalyst Cisco the Cisco Certified Internetwork Expert logo
Cisco lOS the Cisco lOS logo Cisco Systems Cisco Systems Capital the Cisco Systems logo Enterprise/Solver EtherChannel EtherSwitch FastHub
FsstSwitch lOS IF/TV LightStream MICA Network Registrar Post-Routing Pre-Routing Registrar StrataView Plus Stratm SwitchProbe TeleRouter and VCO are registered trademarks of Cisco Systems Inc or its affiliates in the U.S and certain other countries
All other trademarks mentioned in this document Web site the their The of the word brands names or or are property of respective owners use partner does not between Cisco and other imply partnership relationship any company 0102R
Cisco lOS and Novell IPX Guide AppleTalk Configuration
Copyright 2001 Cisco Systems Inc
All rights reserved About Cisco lOS Software Documentation xiii
Documentation Objectives xiii
Audience xiii
Documentation Organization xiii
Documentation Modules xiii
Master Indexes xvi
Supporting Documents and Resources xvi
Document Conventions xvii
Obtaining Documentation xviii
World Wide Web xviii
Documentation CD-ROM xviii
Ordering Documentation xviii
Documentation Feedback xix
Obtaining Technical Assistance xix
Cisco.com xix
Technical Assistance Center xx
Contacting TAC by Using the Cisco TAC Website xx
Contacting TAC by Telephone xx
Using Cisco lOS Software xxi
Understanding Command Modes xxi
Getting Help xxii
Example How to Find Command Options xxiii
Using the no and default Forms of Commands xxv
Saving Configuration Changes xxvi
Filtering Output from the show and more Commands xxvi
Identifying Supported Platforms xxvii
Using Feature Navigator xxvii
Using Software Release Notes xxvii
AppleTalk and Novell IPX Overview P2C-1
AppleTalk Overview P2C-1
Background on AppleTalk P2C-2
Cisco lOS AppleTalk and Novell IPX Configuration Guide Contents
The Cisco Implementation of AppleTalk P2C-2
Media Support P2C-2
Standard AppleTalk Services P2C-2
Enhancements to Standard AppleTalk Services P2c-3
Security P2C-4
Novell IPX Overview P2C-4
Background on Novell IPX P2C-4
The Cisco Implementation of Novell IPX P2c-4
IPX MIB Support P2C-5
IPX Enhanced IGRP Support P2c-5
LANE Support P2C-5
VLAN Support P2C-5
Multilayer Switching Support P2C-5
Contigurinj AppleTalk P2C-7
AppleTalk Phases P2C-7
AppleTalk Phase P2C-7
AppleTalk Phase P2C-7
Types of AppleTalk Phase Networks P2C-8
AppleTalk Addresses P2C-9
Network Numbers P2c-9
Node Numbers P2C-1O
AppleTalk Address Example P2C-lo
AppleTalk Zones P2C1O
Configuration Guidelines and Compatibility Rules P2C-lo
AppleTalk Configuration Task List P2c-11
Configuring AppleTalk Routing P2c-11
Enabling AppleTalk Routing P2C-12
Configuring an Interface for AppleTalk P2C-12
Selecting an AppleTalk Routing Protocol P2C-15
Configuring Transition Mode P2c-15
Enabling Concurrent Routing and Bridging P2c-16
Configuring Integrated Routing and Bridging P2c-16
Controlling Access to AppleTalk Networks P2c-16
Types of Access Lists P2c-17
Types of Filters P2c-18
__ Cisco lOS AppleTalk and Novell IPX Configuration Guide Contents
Implementation Considerations P2c-19
Controlling Access to AppleTalk Networks Task List P2c-19
Creating Access Lists P2C-19
Creating Filters P2C-21
Configuring the Name Display Facility P2C-26
Sethng Up Special Configurations P2C-26
Configuring Free-Trade Zones PZC-26
Configuring SNMP over DDP in AppleTalk Networks P2C-27
Configuring AppleTalk Tunneling P2C-27
Configuring AppleTalk MaciP P2C-30
Configuring AppleTalk MaciP Task List P2C-32
Configuring lPTalk P2C-33
Configuring SMRP over AppleTalk P2C-36
Configuring AppleTalk Control Protocol for PPP P2c-38
Tuning AppleTalk Network Performance PZC-39
Controlling Routing Updates P2C-39
Assigning Proxy Network Numbers P2C-41
Enabling Round-Robin Load Sharing P2c-42
Disabling Checksum Generation and Verification P2C-42
Controlling the AppleTalk ARP Table P2C-42
Controlling the Delay Between ZIP Queries P2C-43
Logging Significant Network Events P2C-44
Disabling Fast Switching P2C-44
Configuring AppleTalk Enhanced IGRP P2C-44
Convergence Technology P2C-44
Enhanced IGRP Features P2C-45
Enhanced IGRP Components P2C-45
The Cisco Implementation of Enhanced IGRP P2c-46
Enhanced IGRP Configuration Task List P2C-46
Configuring AppleTalk Interenterprise Routing P2C-49
Understanding AppleTalk Domains P2C-50
Understanding Domain Routers P2C-50
AppleTalk Interenterprise Routing Features P2c-50
Redundant Paths Between Domains P2C-50
AppleTalk Interenterprise Routing Task List P2C-51
Cisco lOS AppleTalk and Novell IPX Configuration Guide Contents
Configuring AppleTalk over WANs P2c-52
AppleTalk over DDR P2C-53
AppleTalk over X.25 P2C-54
Configuring AppleTalk Between LANs P2C-54
Configuring AppleTalk Between VLANs P2C-54
Monitoring and Maintaining the AppleTalk Network P2C-54
Monitoring and Maintaining the AppleTalk Network Using Cisco lOS Software
Commands P2C-54
Monitoring the AppleTalk Network Using Network Monitoring Packages P2C-56
AppleTalk Configuration Examples P2C-57
Extended AppleTalk Network Example P2C-58
Nonextended AppleTalk Network Example P2C-58
Nonextended Network in Discovery Mode Example P2C-58
AppleTalk Enhanced IGRP Example P2C-59
AppleTalk Access List Examples P2C-59
Defining an Access List to Filter Data Packets Example P2C-fio
Defining an Access List to Filter Incoming Routing Table Updates Example P2C-6o
Comparison of Alternative Segmentation Solutions P2c-61
Defining an Access List to Filter NBP Packets Example P2c-63
Configuring Partial Zone Advertisement Example P2C-64
Transition Mode Example P2C-65
Hiding and Sharing Resources with Access List Examples P2C-66
Establishing Free-Trade Zone Example P2c-66
Restricting Resource Availability Example P2c-68
GZL and ZIP Reply Filter Examples P2C-7o
AppleTalk Interenterprise Routing over AURP Example P2C-71
SNMP Example P2C-72
MacIP Examples P2C-72
IPTalk Example P2C-73
AppleTalk Control Protocol Example P2C-76
Proxy Network Number Example P2C-76
AppleTalk Enhanced IGRP Bandwidth Configuration Example P2C-77
AppleTalk Interenterprise Routing Example P2C-77
AppleTalk over DDR Example P2c-77
AppleTalk Control Protocol for PPP Example P2C-79
Cisco lOS AppleTalk and Novell IPX Configuration Guide Contents
Configuring Novell IPX PZC-81
IPX Addresses P2C-81
Network Numbers P2c-81
Node Numbers P2C-81
IPX Address Example P2C-82
IPX Configuration Task List P2C-82
Configuring IPX Routing P2C-82
IPX Default Routes P2c-83
Enabling IPX Routing P2C-83
Assigning Network Numbers to Individual Interfaces P2C-83
Enabling Concurrent Routing and Bridging P2C-86
Configuring Integrated Routing and Bridging P2C-86
Configuring IPX Enhanced IGRP P2C-86
Enhanced IGRP Features P2C-87
Enhanced IGRP Components P2C-87
Neighbor Discovery/Recovery Pzc-81
Reliable Transport Protocol P2C-87
DUAL Finite-State Machine P2C-88
Protocol-Dependent Modules P2C-88
IPX Enhanced IGRP Configuration Task List PZC-88
Enabling IPX Enhanced IGRP P2C-88
Customizing Link Characteristics P2C-89
Customizing the Exchange of Routing and Service Information P2C-90
Redistributing Routing Information P2C-91
Disabling Split Horizon P2C-91
Controlling the Advertising of Routes in Routing Updates P2C-92
Controlling the Processing of Routing Updates P2c-92
Controlling SAP Updates P2C-92
Controlling the Advertising of Services in SAP Updates P2c-93
Controlling the Processing of SAP Updates Pzc-94
Querying the Backup Server P2c-94
Configuring NLSP P2c-94
Understanding Level 12 and Routers P2C-94
Understanding NLSP Databases P2C-95
Cisco Support of NLSP P2C-95
Cisco lOS AppleTalk and Novell IPX Configuration Guide Contents
NLSP Configuration Task List P2C-95
Defining an Internal Network P2C-96
Enabling NLSP Routing P2C-96
Configuring NLSP on an Interface P2c-96
Customizing Link Characteristics P2c-97
Configuring Route Aggregation P2C-102
Understanding Area Addresses Route Summaries and Aggregated Routes P2C-1o2
Understanding NLSP Areas P2c-1o3
Understanding Route Redistribution P2C-1o4
Understanding Route Summarization P2c-1o4
Understanding Service and Path Selection P2C1O6
Route Aggregation Configuration Task List P2C-106
Customizing the Exchange of Routing Information P2C-115
Configuring RIP and SAP Compatibility P2C-115
Redistributing Routing Information P2C-116
Configuring Next Hop Resolution Protocol P2c-117
NHRP Configuration Task List P2C-117
Enabling NHRP on an Interface P2c-117
Configuring Station with Static IPX-to-NBMA Address Mapping Pzc-iii
Statically Configuring Next Hop Server P2c-118
Configuring NHRP Authentication P2C-118
Controlling NHRP Initiation PZC-118
Controlling NHRP Packet Rate P2c-119
Suppressing Forward and Reverse Record Options P2C-120
Specifying the NHRP Responder Address P2C-12o
Changing the Time Period NBMA Addresses Are Advertised As Valid P2C-120
Configuring IPX and SPX over WANs P2c-121
Configuring IPX over DDR P2c-121
Configuring SPX Spoofing over DDR P2C-122
Configuring IPX Header Compression Pzc-in
Configuring the IPXWAN Protocol P2C-122
Controlling Access to IPX Networks P2C-1
Types of Access Lists P2C-123
Types of Filters P2c-123
Implementation Considerations P2C-125
Cisco lOS AppleTalk and Novell IPX Configuration Guide ______p Contents
Controlling Access to IPX Networks Task List P2C-125
Creating Access Lists P2C-125
Creating Access Lists Using Numbers P2c-126
Creating Access Lists Using Names P2C-126
Creating Filters P2C-130
Creating Generic Filters P2C-131
Creating Filters for Updating the Routing Table P2C-131
Creating SAP Filters P2C-132
Creating GNS Response Filters P2C-132
Creating GGS Response Filters P2c-132
Creating IPX NetBIOS Filters P2c-133
Creating Broadcast Message Filters P2C-134
Tuning IPX Network Performance P2C-135
Controlling Novell IPX Compliance P2C-135
Adjusting RIP and SAP Information P2c-140
Configuring Load Sharing P2C-146
Specifying the Use of Broadcast Messages P2C-147
Disabling IPX Fast Switching P2C-149
Adjusting the Route Cache P2C-149
Adjusting Default Routes P2C-150
Padding Odd-Length Packets P2C-1 51
Shutting Down an IPX Network P2C-151
Configuring IPX Accounting P2C-152
Switching Support P2C-152
Access List Support P2C-152
IPX Accounting Task List P2C-153
Enabling IPX Accounting P2C-153
Customizing IPX Accounting P2C-153
Configuring IPX Between LANs P2C-153
Configuring IPX Between VLANs P2C-154
Configuring IPX Multilayer Switching P2C-154
Monitoring and Maintaining the IPX Network P2c-154
General Monitoring and Maintaining Tasks P2C-154
Monitoring and Maintaining Caches Tables Interfaces and Statistics P2C-155
Specifying the Type and Use of Ping Packets P2C-155
Cisco lOS AppleTalk and Novell IPX Configuration Guide Contents
Troubleshooting Network Connectivity P2C-156
Monitoring and Maintaining IPX Enhanced IGRP P2C-156
Logging Enhanced IGRP Neighbor Adjacency Changes P2C-156
Monitoring and Maintaining NLSP P2C-157
Logging Adjacency State Changes P2C-157
Monitoring and Maintaining NHRP P2C-158
Monitoring and Maintaining IPX Accounting P2C-158
Novell IPX Configuration Examples 159
IPX Routing Examples 159
IPX Routing on Single Network Example 159
IPX Routing on Multiple Networks Examples 159
IPX Routing Protocols Examples 161
Enhanced IGRP Examples 163
IPX Enhanced IGRP Example 163
IPX SAP-Incremental IGRP Example 163
Enhanced IGRP SAP Update Examples 164
Advertisement and Processing of SAP Update Examples 164
IPX Enhanced IGRP Bandwidth Configuration Example 165
NLSP Examples 165
NLSP Multicast Addressing Examples 165
Enhanced IGRP and NLSP Route Redistribution Example 166
NLSP Route Aggregation for Multiple NLSP Version 1.1 Areas Example 166
NLSP Route Aggregation for NLSP Version .1 and Version .0 Areas Example 166
NLSP Route Aggregation for NLSP Version 1.1 Enhanced IGRP and RIP Example 167
NHRP Examples 168
NHRP Example 168
NHRP over ATM Example 170
IPX over WAN Examples 112
IPX over WAN Interface Example 172
IPX over DDR Example 174
IPX Network Access Examples 176
IPX Network Access Example 176
Standard Named Access List Example 177
Extended Named Access List Time Range Example 177
SAP Input Filter Example 178
Cisco lOS AppleTalk and Novell IPX Configuration Guide Contents
SAP Output Filter Example 118
GGS SAP Response Filter Example 119
IPX NetBIOS Filter Examples 180
Helper Facilities to Control Broadcast Examples 182
Forwarding to an Address Example 182
Forwarding to All Networks Example 184
All-Nets Flooded Broadcast Example 185
IPX Accounting Example 185
Index
Cisco lOS AppleTalk and Novell IPX Configuration Guide Contents
Cisco lOS AppleTalk and Novell IPX Configuration Guide About Cisco lOS Software Documentation
2J
This chapter discusses the objectives audience organization and conventions of Cisco lOS software
documentation It also provides sources for obtaining documentation from Cisco Systems
Documentation Objectives
Cisco lOS software documentation describes the tasks and commands necessary to configure and
maintain Cisco networking devices
Audience
The Cisco lOS software documentation set is intended primarily for users who configure and maintain Cisco networking devices such as routers and switches but who may not be familiar with the tasks the Cisco software commands to the relationship between tasks or 105 necessary perform particular
tasks The Cisco lOS software documentation set is also intended for those users experienced with
Cisco lOS software who need to know about new features new configuration options and new software
characteristics in the current Cisco 105 software release
Documentation Organization
The Cisco lOS software documentation set consists of documentation modules and master indexes In
addition to the main documentation set there are supporting documents and resources
Documentation Modules
The Cisco lOS documentation modules consist of configuration guides and corresponding command and reference publications Chapters in configuration guide describe protocols configuration tasks
Cisco lOS software functionality and contain comprehensive configuration examples Chapters in information Use each command reference publication provide complete Cisco 105 command syntax
configuration guide in conjunction with its corresponding command reference publication
Cisco lOS AppleTalk and Novell IPX Configuration Guide
XIII About Cisco 105 Software Documentation
Documentation Organization
Figure shows the Cisco lOS software documentation modules
Note The abbreviations for example FC and FR next to the book icons are page designators which are defined in key in the index of each document to help you with navigation The bullets under each module list the major technology areas discussed in the corresponding books
Figure Cisco lOS Software Documentation Modules
FC P2C Cisco ios P3C Cisco OS AppleTalk and Apollo Domain Novell IPX Banyan VINES
Configuration DECnet ISO Guide CLNS and XNS
Configuration Guide
Cisco los Cisco lOS AppleTalk and Apollo Domain Novell IPX Banyan VINES P2R P3R Command DECnet ISO Reference CLNS and XNS Command Reference
Module FC/FR Module IPC/IP1R/IP2R/IP3R Module P2C/P2R Module P3C/P3R
CiscolOSUser IP Addressing and Services AppleTalk Apollo Domain
Interfaces Routing Protocols Novell IPX Banyan VINES
File Management Multicast DECnet
System Management ISOCLNS XNS
wc IC Sc
Module WC/WR Module IC/lR Module MWC/MWR Module SC/SR
ATM LAN Interfaces General Packet AM Security Services
Broadband Access Serial Interfaces Radio Service Security Server Protocols Frame Relay Logical Interfaces Traffic Filtering and Firewalls SMDS Security and Encryption X.25 and LAPB Passwords and Privileges
Neighbor Router Authentication
Security Options
SupportedAV Pairs
Cisco lOS AppleTalk and Novell IPX Configuration Guide About Cisco lOS Software Documentation
Documentation Organization
DC TC
DC/DR Module BCIB1R Module BCIB2R Module Module TC/TR DSPU and SNA Preparing for Dial Access ARA Transparent Modem and Dial Shelf Service Point Configuration LAT Bridging SRB SNA and Management NASI Switching ISDN Token Services Configuration Telnet Ring Inter-Switch Link Cisco Transaction Signalling Configuration TN3270 Dial-onDemand Token Route Connection Routing XRemote Ring Configuration X28 PAD Switch Module Cisco Mainframe RSRB Channel Connection Dial-Backup Configuration Protocol Translation Dial-Related Addressing Services DLSw CLAW and TCP/IP
Virtual Templates Profiles and Serial Tunnel and Offload
Networks Block Serial Tunnel CSNA CMPC
PPP Configuration LLC2 and SDLC and CMPC Callback and Bandwidth Allocation IBM Network TN3270 Server
Configuration Media Translation
Dial Access Specialized Features SNA Frame Relay
Dial Access Scenarios Access
NCIA Client/Server
Airline Product Set
vC QC XC
Module VCNR Module QC/QR Module XCIXR Voice over Packet Classification CiscolOS
Call Control Signalling Congestion Management Switching Paths
Voice over Congestion Avoidance NetFiow Switching
Frame Relay Policing and Shaping Multiprotocol Label Switching Voice ATM over Signalling Multilayer Switching
Telephony Applications Link Efficiency Multicast Distributed Switching Trunk Management Mechanisms Virtual LANs
Fax Video and LAN Emulation
Modem Support
Cisco lOS AppleTalk and Novell IPX Configuration Guide About Cisco lOS Software Documentation
Documentation Organization
Master ndexes
Two master indexes provide indexing information for the Cisco lOS software documentation set
an index for the configuration guides and an index for the command references Individual books also
contain book-specific index
The master indexes provide quick way for you to find command when you know the command name but not which module contains the command When you use the online master indexes you can click the page number for an index entry and go to that page in the online document
Supporting Documents and Resources
The following documents and resources support the Cisco lOS software documentation set
Cisco 105 Command Summary two volumesThis publication explains the function and syntax of the Cisco lOS software commands For more information about defaults and usage guidelines
refer to the Cisco lOS command reference publications
Cisco lOS System Error MessagesThis publication lists and describes Cisco lOS system error
messages Not all system error messages indicate problems with your system Some are purely informational and others may help diagnose problems with communications lines internal hardware or the system software
Cisco lOS Debug Command ReferenceThis publication contains an alphabetical listing of the
debug commands and their descriptions Documentation for each command includes brief
description of its use command syntax usage guidelines and sample output
Dictionary of Interneiworking Terms and AcronymsThis Cisco publication compiles and defines
the terms and acronyms used in the internetworking industry
New feature documentationThe Cisco lOS software documentation set documents the mainline
release of Cisco lOS software for example Cisco lOS Release 12.2 New software features are
introduced in early deployment releases for example the Cisco lOS release train for 12.2 12.2xT Documentation for these new features can be found in standalone documents called
feature modules Feature module documentation describes new Cisco lOS software and hardware
networking functionality and is available on Cisco.com and the Documentation CD-ROM
Release notesThis documentation describes system requirements provides information about
new and changed features and includes other useful information about specific software releases
See the section Using Software Release Notes in the chapter Using Cisco lOS Software for more information
Caveats documentationThis documentation provides information about Cisco lOS software
defects in specific software releases
RFCsRFCs are standards documents maintained by the Internet Engineering Task Force IETF Cisco 105 software documentation references supported RFCs when applicable The full text of
referenced RFCs may be obtained on the World Wide Web at http//www.rfc-editor.org/
MIBsMIBs are used for network monitoring For lists of supported MIBs by platform and
release and to download MIB files see the Cisco MIB website on Cisco.com at
http//www.cisco.comlpublic/sw-center/netmgmt/cmtkmibs.shtml
Cisco lOS AppleTalk and Novell IPX Configuration Guide
______Cisco lOS Software Documentation
Document Conventioni
Document Conventions
Within Cisco lOS software documentation the term router is generally used to refer to variety of Cisco
products for example routers access servers and switches Routers access servers and other
networking devices that support Cisco lOS software are shown interchangeably within examples These
products are used only for illustrative purposes that is an example that shows one product does not
necessarily indicate that other products are not supported
The Cisco lOS documentation set uses the following conventions
Convention Description
or Ctrl The and Ctrl symbols represent the Control key For example the key combination AD or Ctrl-D
hold the Control while indicated in letters but means down key you press the key Keys are capital are not case sensitive string string is nonquoted set of characters shown in italics For example when setting an SNMP
conimunity string to public do not use quotation marks around the string or the string will include the
quotation marks
Command syntax descriptions use the following conventions
Convention Description boldface Boldface text indicates commands and that shown keywords you enter literally as italics Italic text indicates arguments for which you supply values
Square brackets enclose an optional element keyword or argument
vertical line indicates choice within an optional or required set of keywords or arguments
Square brackets enclosing keywords or arguments separated by vertical line indicate an optional choice
Braces enclosing keywords or arguments separated by vertical line indicate required choice
Nested of brackets braces indicate choices within sets square or optional or required optional or
required elements For example
Convention Description
Braces and vertical line within square brackets indicate required choice within an optional element
Examples use the following conventions
Convention Description screen Examples of information displayed on the screen are set in Courier font boldface screen Examples of text that you must enter are set in Courier bold font
Angle brackets enclose text that is not printed to the screen such as passwords
Cisco lOS AppleTalk and Novell IPX Configuration Guide _4A About Cisco lOS Software Documentation
Obtaining Documentation
Convention Description
An exclamation point at the beginning of line indicates comment line Exclamation points are also
displayed by the Cisco lOS software for certain processes
Square brackets enclose default responses to system prompts
The following conventions are used to attract the attention of the reader
Caution Means reader be careful In this situation you might do something that could result in equipment damage or loss of data
Note Means reader take note Notes contain helpful suggestions or references to materials not
contained in this manual
limesaver Means the described action saves time You can save time by performing the action described in the paragraph
Obtaining Documentation
The following sections provide sources for obtaining documentation from Cisco Systems
World Wide Web
The most current Cisco documentation is available on the World Wide Web at the following website
http//www.cisco.com
Translated documentation is available at the following website
http //www.cisco.comlpublic/countries_languages .html
Documentation CD-ROM
Cisco documentation and additional literature are available in CD-ROM package which ships with your product The Documentation CD-ROM is updated monthly and may be more current than
printed documentation The CD-ROM package is available as single unit or through an
annual subscription
Cisco lOS AppleTalk and Novell IPX Configuration Guide
XVII Cisco lOS Software Documentation
Documentation Feedback
Ordering Documentation
Cisco documentation can be ordered in the following ways
Registered Cisco Direct Customers can order Cisco product documentation from the Networking Products MarketPlace
http//www.cisco.comlcgi-bin/order/order_root.pl
Registered Cisco.com users can order the Documentation CD-ROM through the online
Subscription Store
http//www.cisco.com/go/subscription
Nonregistered Cisco.com users can order documentation through local account representative by
calling Cisco corporate headquarters California USA at 408 526-7208 or in North America by
calling 800 553-NETS6387
Documentation Feedback
If you are reading Cisco product documentation on the World Wide Web you can submit technical comments electronically Click Feedback in the toolbar and select Documentation After you complete
the form click Submit to send it to Cisco
You can e-mail your comments to [email protected]
To submit your conunents by mail use the response card behind the front cover of your document or
write to the following address
Cisco Systems Inc Document Resource Connection 170 West Tasman Drive
San Jose CA 95 134-9883
We appreciate your comments
Obtaining Technica Assistance
Cisco provides Cisco.com as starting point for all technical assistance Customers and partners can
obtain documentation troubleshooting tips and sample configurations from online tools For
Cisco.com registered users additional troubleshooting tools are available from the TAC website
Cisco.com
Cisco.com is the foundation of suite of interactive networked services that provides immediate open access to Cisco information and resources at anytime from anywhere in the world This highly
integrated Internet application is powerful easy-to-use tool for doing business with Cisco
Cisco.com provides broad range of features and services to help customers and partners streamline business and find information about Cisco processes improve productivity Through Cisco.com you can and our networking solutions services and programs In addition you can resolve technical issues with
online technical support download and test software packages and order Cisco learning materials and
merchandise Valuable online skill assessment training and certification programs are also available
Cisco lOS AppleTalk and Novell IPX Configuration Guide About Cisco lOS Software Documentation
Obtaining Technical Assistance
Cisco.com obtain additional information Customers and partners can self-register on to personalized check the of technical and services Registered users can order products on status an order access
support and view benefits specific to their relationships with Cisco
To access Cisco.com go to the following website
http//www.cisco.com
Technica Assistance Center
The Cisco TAC website is available to all customers who need technical assistance with Cisco product
or technology that is under warranty or covered by maintenance contract
Contacting TAC by Using the Cisco TAC Website
If you have priority level P3 or priority level P4 problem contact TAC by going to the TAC website
http//www.cisco.com/tac
P3 and P4 level problems are defined as follows
P3Your network performance is degraded Network functionality is noticeably impaired but
most business operations continue
P4You need information or assistance on Cisco product capabilities product installation or basic
product configuration
In each of the above cases use the Cisco TAC website to quickly find answers to your questions
To register for Cisco.com go to the following website
http//www.cisco.com/registen
If you cannot resolve your technical issue by using the TAC online resources Cisco.com registered
users can open case online by using the TAC Case Open tool at the following website
http//www.cisco.com/tac/caseopen
Contacting TAC by Telephone
If you have priority level P1 or priority level P2 problem contact TAC by telephone and immediately open case To obtain directory of toll-free numbers for your country go to the following website
http//www.cisco.comlwarp/public/687/Directory/DirTAC.shtml
P1 and P2 level problems are defined as follows
P1Your production network is down causing critical impact to business operations if service
is not restored quickly No workaround is available
P2Your production network is severely degraded affecting significant aspects of your business
operations No workaround is available
CiscolOS AppleTalk and Novell IPX Configuration Guide ______Using Cisco WS Software /7Z/
This chapter provides helpful tips for understanding and configuring Cisco lOS software using the
command-line interface CLI It contains the following sections
Understanding Command Modes
Getting Help
Using the no and default Forms of Commands
Saving Configuration Changes
Filtering Output from the show and more Commands
Identifying Supported Platforms
For an overview of Cisco lOS software configuration refer to the Cisco lOS Configuration
Fundamentals Configuration Guide
For information on the conventions used in the Cisco lOS software documentation set see the chapter
About Cisco lOS Software Documentation located at the beginning of this book
Understanding Command Modes
You use the CLI to access Cisco lOS software Because the CLI is divided into many different modes the commands available to you at any given time depend on the mode you are currently in Entering question mark at the CLI prompt allows you to obtain list of commands available for each command mode
When you log in to the CLI you are in user EXEC mode User EXEC mode contains only limited subset of commands To have access to all commands you must enter privileged EXEC mode normally by using password From privileged EXEC mode you can issue any EXEC commanduser or privileged modeor you can enter global configuration mode Most EXEC commands are one-time
commands For example show commands show important status information and clear commands
clear counters or interfaces The EXEC commands are not saved when the software reboots
Configuration modes allow you to make changes to the running configuration If you later save the
running configuration to the startup configuration these changed commands are stored when the
software is rebooted To enter specific configuration modes you must start at global configuration
mode From global configuration mode you can enter interface configuration mode and variety of
other modes such as protocol-specific modes
ROM monitor mode is separate mode used when the Cisco lOS software cannot load properly If
valid software image is not found when the software boots or if the configuration file is corrupted at
startup the software might enter ROM monitor mode
Cisco lOS AppleTalk and Novell IPX Configuration Gui Using Cisco lOS Software
Getting Help
Table describes how to access and exit various common command modes of the Cisco lOS software
It also shows examples of the prompts displayed for each mode
Table Accessing and Exiting Command Modes
Command
Mode Access Method Prompt Exit Method
User EXEC Log in Router Use the logout command
Privileged From user EXEC mode Router To return to user EXEC mode use the disable EXEC use the enable EXEC command command
Router Global From privileged EXEC config To return to privileged EXEC mode from global
configuration mode use the configure configuration mode use the exit or end command
terminal privileged or press Ctrl-Z EXEC command
Interface From global Router config-if To return to global configuration mode use the exit
configuration configuration mode command
specify an interface using To return to privileged EXEC mode use the end an interface command command or press Ctrl-Z
ROM monitor From privileged EXEC To exit ROM monitor mode use the continue
mode use the reload command
EXEC command Press
the Break key during the
first 60 seconds while the
system is booting
For more information on command modes refer to the Using the Command-Line Interface chapter in
the Cisco lOS Configuration Fundamentals Configuration Guide
Getting Hep
Entering question mark at the CLI prompt displays list of commands available for each command
mode You can also get list of keywords and arguments associated with any command by using the
context-sensitive help feature
To get help specific to command mode command keyword or an argument use one of the
following commands
Command Purpose
help Provides brief description of the help system in any command mode
abbreviated-command-entry Provides list of commands that begin with particular character string No space
between command and question mark
abbrevi at ad command en tryTab Completes partial command name
Lists all commands available for particular command mode
command Lists the keywords or arguments that you must enter next on the command line
Space between command and question mark
Cisco lOS AppleTalk and Novell IPX Configuration Guide Cisco lOS Software
Getting Help
ExampHe How to Find Command Options
This section provides an example of how to display syntax for command The syntax can consist of
optional or required keywords and arguments To display keywords and arguments for command enter
mark the after of followed question at configuration prompt or entering part command by space
The Cisco lOS software displays list and brief description of available keywords and arguments For
example if you were in global configuration mode and wanted to see all the keywords or arguments for the arap command you would type arap
The cr symbol in conunand help output stands for carriage return On older keyboards the carriage
return key is the Return key On most modern keyboards the carriage return key is the Enter key The of command Enter cr symbol at the end help output indicates that you have the option to press to
complete the command and that the arguments and keywords in the list preceding the cr symbol are
optional The cr symbol by itself indicates that no more arguments or keywords are available and that
you must press Enter to complete the command
Table shows examples of how you can use the question mark to assist you in entering commands The table steps you through configuring an IP address on serial interface on Cisco 7206 router that is running Cisco lOS Release 12.03
Table How to Find Command Options
Command Comment
Router enable Enter the enable command and Password password password to access privileged EXEC Router commands You are in privileged
EXEC mode when the prompt changes
to Router
Router configure terminal Enter the configure terminal Enter configuration commands one per line End with CNTL/Z privileged EXEC command to enter Router config global configuration mode You are in
global configuration mode when the
prompt changes to Router config
Router config interface aerial Enter interface configuration mode by 0-6 Serial interface number specifying the serial interface that you Router config interface serial want to configure using the interface
serial global configuration command Routerconfig interface aerial 4/ 0-3 Serial interface number Enter to display what you must enter Routerconfig interface aerial 4/0 next on the command line In this Router config-if example you must enter the serial
interface slot number and port number
separated by forward slash
You are in interface configuration mode
when the prompt changes to Router config-if
Cisco lOS and Novell IPX Guide AppleTalk Configuration E4II Using Cisco lOS Software
Getting Help
Table How to Find Command Options continued
Command Comment
Router config-if Enter to display list of all the Interface conf igurat ion commands interface configuration commands
available for the serial interface This
example shows only some of the
ip Interface Internet Protocol config commands available interface configuration keepalive Enable keepalive commands lan-name LAN Name command llc2 LLC2 Interface Subcommands
load-interval Specify interval for load calculation for an interface locaddr-priority Assign priority group logging Configure logging for interface loopback Configure internal loopback on an interface mac-address Manually set interface MAC address mls mls router sub/interface commands mpoa MPOA interface configuration commands mtu Set the interface Maximum Transmission Unit MTU netbios Use defined NETBIOS access list or enable name caching no Negate command or set its defaults nrzi-encoding Enable use of NRZI encoding ntp Configure NTP
Router config-if
Router config-if ip Enter the command that you want to Interface IP configuration subcommands configure for the interface This access-group Specify access control for packets example uses the ip command accounting Enable IP accounting on this interface address Set the IP address of an interface Enter to display what you must enter authentication authentication subcommands next on the command line This bandwidth-percent Set EIGRP bandwidth limit example shows only some of the broadcast-address Set the broadcast address of an interface cgmp Enable/disable CGMP available interface IP configuration directed-broadcast Enable forwarding of directed broadcasts commands dvmrp DVMRP interface commands hello-interval Configures IP-EIGRP hello interval helper-address Specify destination address for UDP broadcasts hold-time Configures IP-EIGRP hold time
Router config-if ip
Cisco lOS AppleTalk and Novell IPX Configuration Guide XXIV Cisco lOS Software
Using the no and default Forms of Commands
Table How to Find Command Options continued
Command Comment
address Router config-if ip Enter the command that you want to A.B.C.D IP address configure for the interface This negotiated IP Address negotiated over example uses the ip address command RouterConfig-if ip address
Enter to display what you must enter
next on the command line In this
example you must enter an IP address or the negotiated keyword
carriage return cr is not displayed therefore you must enter
additional keywords or arguments to complete the command
Routerconfig-if ip address 172.16 Enter the keyword or argument you A.B.C.D IP subnet mask want to use This example uses the Routerconfig-if ip address 172.16.0.1 172.16.0.1 IP address
Enter to display what you must enter
next on the command line In this
example you must enter an IP subnet mask
cr is not displayed therefore you
must enter additional keywords or
arguments to complete the command
Routerconfig-if ip address 172.16.0.1 255.255.255.0 Enter the IP subnet mask This example secondary Make this IP address secondary address Cr uses the 255.255.255.0 IP subnet mask Routerconfig-if ip address 172.16.0.1 255.255.255.0 Enter to display what you must enter
next on the command line In this
example you can enter the secondary
keyword or you can press Enter
cr is displayed you can press Enter to complete the command or
you can enter another keyword
address 255.255.255.0 Routerconfig-if ip 172.16.0.1 In this example Enter is pressed to Routerconfig-if complete the command
Using the no and default Forms of Commands
Almost every configuration command has no form In general use the no form to disable function
Use the command without the no keyword to reenable disabled function or to enable function that
is disabled by default For example IP routing is enabled by default To disable IP routing use the no
ip routing command to reenable IP routing use the ip routing command The Cisco lOS software
command reference publications provide the complete syntax for the configuration commands and describe what the no form of command does
Configuration commands also can have default form which returns the command settings to the
default values Most commands are disabled by default soin such cases using the default form has the
same result as using the no form of the command However some commands are enabled by default and
Cisco lOS AppleTalk and Novell IPX Configuration Guide Using Cisco lOS Software
Saving Configuration Changes
have variables set to certain default values In these cases the default form of the command enables the
command and sets the variables to their default values The Cisco lOS software command reference
publications describe the effect of the default form of command if the command functions differently than the no form
Saving Configuration Changes
Use the copy systemrunning-config nvramstartup-config command to save your configuration
changes to the startup configuration so that the changes will not be lost if the software reloads or
power outage occurs For example
Router copy system ruxming-config nvram startup-config Building configuration..
It might take minute or two to save the configuration After the configuration has been saved the
following output appears
Router
On most platforms this task saves the configuration to NVRAM On the Class Flash file system
platforms this task saves the configuration to the location specified by the CONFIG_FILE environment
variable The CONFIG_FILE variable defaults to NVRAM
Filtering Output from the show and more Commands
In Cisco lOS Release 12.OlT and later releases you can search and filter the output of show and more commands This functionality is useful if you need to sort through large amounts of output or if you want to exclude output that you need not see
To use this functionality enter show or more command followed by the pipe character one of
the keywords begin include or exclude and regular expression on which you want to search or filter
the expression is case-sensitive
command begin include exclude regular-expression
The output matches certain lines of information in the configuration file The following example
illustrates how to use output modifiers with the show interface command when you want the output to
include only lines in which the expression protocol appears
Router show interface include protocol
FastEthernetO/O is up line protocol is up Serial4/O is up line protocol is up Serial4/l is up line protocol is up Serial4/2 is administratively down line protocol is down Serial4/3 is administratively down line protocol is down
For more information on the search and filter functionality refer to the Using the Command-Line
Interface chapter in the Cisco lOS Configuration Fundamentals Configuration Guide
Cisco lOS AppleTalk and Novell IPX Configuration Guide
XXVI lOS Software
Identifying Supported PIatforiiil
dentifying Supported Patforms
Cisco lOS software is in feature packaged sets consisting of software images that support specific
platforms The feature sets available for specific platform depend on which Cisco lOS software included in release images are To identify the set of software images available in specific release
or to find out if feature is available in given Cisco lOS software image see the following sections
Using Feature Navigator
Using Software Release Notes
Using Feature Navigator
Feature is Navigator web-based tool that enables you to quickly determine which Cisco lOS software
images support particular set of features and which features are supported in particular Cisco lOS image
Feature Navigator is available 24 hours day days week To access Feature Navigator you must have an account on Cisco.com If you have forgotten or lost your account information e-mail the Contact Database Administration group at [email protected] If you do not have an account on
Cisco.com go to http//www.cisco.com/register and follow the directions to establish an account
To use Feature Navigator you must have JavaScript-enabled web browser such as Netscape 3.0 or
later or Internet Explorer 4.0 or later Internet Explorer 4.0 always has JavaScript enabled To enable
JavaScript for Netscape 3.x or Netscape 4.x follow the instructions provided with the web browser For
JavaScript support and enabling instructions for other browsers check with the browser vendor
Feature is when Cisco lOS Navigator updated major software releases and technology releases occur You can access Feature Navigator at the following URL
http//www.cisco.comlgo/fn
Using Software Release Notes
Cisco lOS software releases include release notes that provide the following information
Platform support information
Memory recommendations
Microcode support information
Feature set tables
Feature descriptions
Open and resolved severity and caveats for all platforms
Release notes are intended to be release-specific for the most current release and the information in these provided documents may not be cumulative in providing information about features that first
appeared in previous releases
Cisco lOS AppleTalk and Novell IPX Configuration Guide Using Cisco lOS Software
Identifying Supported Platforms
Cisco 105 AppleTalk and Novell IPX Configuration Guide
XXVIII AppeTaIk and Novell PX Overview
The Cisco lOS software supports variety of routing protocols The Cisco 105 AppleTalk and Novell
IPX Configuration Guide discusses AppleTalk and Novell IPX network protocols it contains these
sections
AppleTalk Overview
Novell IPX Overview
The Cisco lOS IP Configuration Guide discusses the following network protocols
IP
IP Routing
The Cisco lOS Apollo Domain Banyan VINES DECnet ISO CLNS and XNS Configuration Guide
discusses the following network protocols
Apollo Domain
Banyan VINES
DECnet
ISO CLNS
XNS
This overview chapter provides high-level description of AppleTalk and Novell IPX For configuration
information see the appropriate chapter in this publication
To identify the hardware platform or software image information associated with feature use the
Feature Navigator on Cisco.com to search for information about the feature or refer to the software
release notes for specific release For more information see the section Identifying Supported
Platforms in the Using Cisco lOS Software chapter
AppleTak Overview
This section provides background on AppleTalk and briefly describes the Cisco implementation of AppleTalk
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C AppleTalk and Novell IPX Overview
AppleTalk Overview
Background on AppleTalk
AppleTalk is LAN system designed and developed by Apple Computer Inc It can run over Ethernet
Token Ring and FDDI networks and over the Apple proprietary twisted-pair media access system
LocalTalk AppleTalk specifies protocol stack comprising several protocols that direct the flow of
traffic over the network
Apple Computer uses the name AppleTalk to refer to the Apple network protocol architecture Apple
Computer refers to the actual transmission media used in an AppleTalk network as LocalTalk TokenTalk
AppleTalk over Token Ring EtherTalk AppleTalk over Ethernet and FDDITa1k AppleTalk over FDDI
The Cisco Implementation of AppleTalk
Cisco lOS software supports AppleTalk Phase and AppleTalk Phase For AppleTalk Phase Cisco
devices support both extended and nonextended networks
Cisco router or access server may receive equivalent routes advertised by neighboring routers with one
router giving an AppleTalk Phase form of the route for example 101 and another giving an AppleTalk Phase form of the route for example 101-101 When neighboring routers advertise
equivalent overlapping routes to router the router always uses the AppleTalk Phase form of the route and discards the AppleTalk Phase route
Media Support
The Cisco implementation of AppleTalk routes packets over Ethernet Token Ring and FDDI LANs and
over X.25 High-Level Data Link Control HDLC Frame Relay and Switched Multimegabit Data Service SMDS WANs
Standard AppleTalk Services
The Cisco implementation of AppleTalk supports the following standard AppleTalk protocols
AppleTalk Address Resolution Protocol AARP
AppleTalk Port Group
Datagram Delivery Protocol DDP
Routing Table Maintenance Protocol RTMP
Name Binding Protocol NBP
Zone Information Protocol ZIP
AppleTalk Echo Protocol AEP
AppleTalk Transaction Protocol ATP
AARP DDP and RTMP provide end-to-end connectivity between internetworked nodes AARP maps
AppleTalk node addresses to the addresses of the underlying data link thus making it possible for
AppleTalk to run on several data links DDP provides socket-to-socket delivery of packets RTMP
establishes and maintains routing tables
Cisco lOS and Novell IPX Guide ______AppleTalk Configuration P2C and Novell IPX Overview
AppleTalk Overview
NBP and ZIP maintain node name and zone information NBP maps network names to AppleTalk
addresses ZIP tracks which networks are in which zones
AEP is an echo or ping-type protocol It generates packets that test the reachability of network nodes
ATP is reliable transport protocol that provides data acknowledgment and retransmission for
transaction-based applications such as file services provided by the AppleTalk Filing Protocol AFP and print services provided by the Printer Access Protocol PAP
Our software provides support for the AppleTalk MIB variables as described in RFC 1243
Enhancements to Standard AppleTalk Services
The Cisco AppleTalk implementation includes the following enhancements to standard AppleTalk
support
Support for AppleTalk Enhanced Interior Gateway Routing Protocol Enhanced IGRP AppleTalk
Enhanced IGRP provides the following features
Automatic redistribution By default AppleTalk RTMP routes are automatically redistributed into Enhanced IGRP and AppleTalk Enhanced IGRP routes are automatically redistributed into RTMP If desired you can turn off redistribution You can also completely turn off AppleTalk Enhanced IGRP and AppleTalk RTMP on the device or on individual interfaces
Configuration of routing protocols on individual interfaces You can configure interfaces that
are configured for AppleTalk to use either RTMP Enhanced IGRP or both routing protocols If
two neighboring routers are configured to use both RTMP and Enhanced IGRP the Enhanced
IGRP routing information supersedes the RTMP information However both routers continue
to send RTMP routing updates This feature allows you to control the excessive bandwidth usage of RTMP on WAN links Because WAN link is point-to-point link that is there are no other devices on the link there is no need to run RTMP to perform end-node router
discovery Using Enhanced IGRP on WAN links allows you to save bandwidth and in the case of packet-switched data networks PSDNs traffic charges
Support for EtherTalk 1.2 and EtherTalk 2.0 without the need for translation or transition routers
Support for Ethernet-emulated LANs For more information on emulated LANs ELANs and
routing AppleTalk between them refer to the Configuring LAN Emulation chapter of the
Cisco lOS Switching Services Configuration Guide
Support for VLANs For more information on VLANs and routing AppleTalk between them over
Inter-Switch Link ISL or IEEE 802.10 refer to the Configuring Routing Between VLANs with ISL Encapsulation and Configuring Routing Between VLANs with IEEE 802.10 Encapsulation
chapters of the Cisco lOS Switching Services Configuration Guide
Support for WAN protocols including SMDS Frame Relay X.25 and HDLC
Configurable protocol constants including the control of the aging of entries in the routing table and control of the AARP interval and number of retransmissions
No software limits on the number of zones or routes However per AppleTalk specification you can
only have maximum of 255 zones per segment
MacTCP support via MacIP server
Support of IPTalk which provides IP encapsulation of AppleTalk IPTalk and the Columbia AppleTalk Package CAP
Access control for filtering network traffic by network number ZIP filtering by NBP entity names
filtering routing table updates and filtering GetZoneList GZL responses
Integrated node name support to simplify AppleTalk network management
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C-3 AppleTalk and Novell IPX Overview
Novell IPX Overview
Interactive access to AEP and NBP provided by the test appletalk command
Configured seed and discovered interface configuration
Support for the AppleTalk Responder which is used by network monitoring packages such as InterPoll
Simple Network Management Protocol SNMP over AppleTalk
Encapsulation tunneling of AppleTalk RTMP packets over an if backbone
Support for AppleTalk static routes
Simple Multicast Routing Protocol SMRP over AppleTalk
Security
AppleTalk like many network protocols makes no provisions for network security The design of the
AppleTalk protocol architecture requires that security measures be implemented at higher application
levels Cisco supports AppleTalk distribution lists allowing control of routing updates on per-interface This basis security feature is similar to those that Cisco provides for other protocols
Note that the Cisco implementation of AppleTalk does not forward packets with local source and
destination network addresses This behavior does not conform with the definition of AppleTalk in the
Apple Computer Inside AppleTalk publication However this behavior is designed to prevent any
possible corruption of the AARP table in any AppleTalk node that is performing address gleaning through MAC
Novell PX Overview
This section offers background information and briefly describes the Cisco implementation of Novell IPX
Background on Novell PX
Novell Internetwork Packet Exchange IPX is derived from the Xerox Network Systems XNS Internet
Datagram Protocol IDP IPX and XNS have the following differences
IPX and XNS do not always use the same Ethernet encapsulation format
IPX uses the Novell proprietary Service Advertising Protocol SAP to advertise special network
services File servers and print servers are examples of services that typically are advertised
IPX uses delay measured in ticks while XNS uses hop count as the primary metric in determining
the best path to destination
The Cisco Hmpementation of Novell IPX
The Cisco implementation of the Novell IPX protocol is certified to provide full IPX routing
functionality
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C-4 and Novell IPX Overview AppleTalk Novell IPX Overvie
aPX MB Support
Cisco supports the IPX MIB currently read-only access is supported The IPX Accounting group
represents one of the local Cisco-specific IPX variables we support This group provides access to the
active database that is created and maintained if IPX accounting is enabled on router or access server
pPX Enhaiced IGRP Support
Cisco lOS software supports IPX Enhanced IGRP which provides the following features
Automatic redistributionIPX Routing Information Protocol RIP routes are automatically
redistributed into Enhanced IGRP and Enhanced IGRP routes are automatically redistributed into
RIP If desired you can turn off redistribution You also can completely turn off Enhanced IGRP and
IPX RIP on the device or on individual interfaces
Increased network widthWith IPX RIP the largest possible width of your network is 15 hops
When Enhanced IGRP is enabled the largest possible width is 224 hops Because the Enhanced
IGRP metric is large enough to support thousands of hops the only barrier to expanding the network
is the transport layer hop counter Cisco works around this problem by incrementing the transport
control field only when an IPX packet has traversed 15 routers and the next hop to the destination
was learned via Enhanced IGRP When RIP route is being used as the next hop to the destination
the transport control field is incremented as usual
Incremental SAP updatesComplete SAP updates are sent periodically on each interface until an
Enhanced IGRP neighbor is found and thereafter only when changes are made to the SAP table
This procedure works by taking advantage of the Enhanced IGRP reliable transport mechanism
which means that an Enhanced IGRP peer must be present for incremental SAPs to be sent If no
exists SAPs will be sent that interface until is found peer on particular interface periodic on peer
This functionality is automatic on serial interfaces and can be configured on LAN media
LANE Support
and Token Cisco lOS software supports routing IPX between Ethernet-emulated LANs Ring-emulated
LANs For more information on emulated LANs and routing IPX between them refer to the
Configuring LAN Emulation chapter of the Cisco 105 Switching Services Configuration Guide
VLAN Support
with Novell NetWare environments Cisco lOS software supports routing IPX between VLANs Users
can configure any one of the four IPX Ethernet encapsulations to be routed using ISL encapsulation
across VLAN boundaries For more information on VLANs and routing IPX between them over ISL
refer to the Configuring Routing Between VLANs with ISL Encapsulation chapter of the Cisco 105
Switching Services Configuration Guide
Multilayer Switching Support
Cisco 105 software supports IPX Multilayer Switching MLS For more information on IPX MLS refer
to the Multilayer Switching chapter of the Cisco lOS Switching Services Configuration Guide
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C AppleTalk and Novell IPX Overview
Novell IPX Overview
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C Configuring AppeTalk
This chapter describes how to configure AppleTalk and provides configuration examples For complete
description of the AppleTalk commands mentioned in this chapter refer to the AppleTalk Commands
chapter in the Cisco lOS AppleTalk and Novell IPX Command Reference publication To locate
in this the command reference index documentation of other commands that appear chapter use master or search online
To identify the hardware platform or software image information associated with feature use the
Feature Navigator on Cisco.com to search for information about the feature or refer to the software
release notes for specific release For more information see the Identifying Supported Platforms
section in the Using Cisco lOS Software chapter
AppeTaIk Phases
The AppleTalk network architecture has the following two phases
AppleTalk Phase
AppleTalk Phase
AppleTalk Phase
AppleTalk Phase is the initial implementation of AppleTalk and is designed for logical workgroups be in AppleTalk Phase supports single physical network that can have one network number and one
zone This network can have up to 254 devices which can consist of 127 end nodes and 127 servers
AppleTalk Phase
AppleTalk Phase is an enhancement to AppleTalk Phase and is designed for larger networks and has
improved routing capabilities It supports multiple logical networks on single physical network and
multiple logical networks in given zone which means that one cable segment can have multiple
network numbers Each logical network in Phase can support up to 253 devices with no restrictions
on the type of devices end nodes or servers Also in AppleTalk Phase network can be in more than one zone
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C Configuring AppleTalk
AppleTalk Phases
Types of AppeTaUk Phase Networks
AppleTalk Phase distinguishes between two types of networks based on their media-level
encapsulation and cable addressing methods The two types of networks are as follows
Nonextended
Extended
Table the of networks compares attributes nonextended and extended
Table Comparison of Nonextended and Extended Networks
Attribute Nonextended Extended
Media-level encapsulation method Encapsulation of the ISO-type
3-byte LocalTalk encapsulations only
packet in an Ethernet that is no
frame encapsulation of the
3-byte LocalTalk
packets
Physical media that supports media-level LocalTalk All physical media
encapsulation methods except LocalTalk
Node addressing method Each node number is Each network.node
unique combination is unique
Cable addressing method single number per number range
cable corresponding to one
or more logical networks
Nonextended networks were the sole network type defined in AppleTalk Phase You can consider
AppleTalk Phase networks to be nonextended networks
You can consider AppleTalk Phase networks to be extended networks
Table compares the capabilities of AppleTalk Phase and Phase
Table Comparison of AppleTalk Phase and Phase
Capability AppleTalk Phase AppleTalk Phase
Networks nodes and zones
Number of logical networks cable segments 652791
Maximum number of devices 2542 253
Maximum number of end nodes 127 Does not apply4
Maximum number of servers 127 Does not apply
Number of zones in which network can be i5 nonextended 255 extended
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C ConfiWi AppleTalk AppleTalk Addresses
Table Comparison of AppleTalk Phase and Phase continued
Capability AppleTalk Phase AppleTalk Phase
Media-level encapsulation
Nonextended network Does not apply Yes
Extended network Does not apply Yes
Cable addressing Does not apply uses Single network network numbers number nonextended
Cable range of or more extended
The 65279 value is per AppleTalk specifications
The node addresses and 255 are reserved
The node addresses 254 and 255 are reserved
There is no restriction on the types of devices There can be total of 253 end nodes and servers
In terms of zones an AppleTalk Phase network can be thought of as nonextended AppleTalk Phase network
Routers running Cisco lOS software Release 8.2 or later support AppleTalk Phase and Phase
AppIeTak Addresses
An AppleTalk address consists of network number and node number expressed in decimal in the format network.node
Network Numbers
The net-work number identifies network or cable segment network is single logical cable
Although the logical cable is frequently single physical cable bridges and routers can interconnect
several physical cables
The network number is 16-bit decimal number that must be unique throughout the entire AppleTalk internetwork
In AppleTalk Phase networks are identified by single network number that corresponds to physical network In AppleTalk Phase the network number is reserved
identified that In AppleTalk Phase networks are by cable range corresponds to one or more logical
networks In Phase single cable can have multiple network numbers
cable range is either one network number or contiguous sequence of several network numbers in the format startend For example the cable range 40964096 identifies logical network that has single
network that three network network number and the cable range 1012 identifies logical spans numbers
In AppleTalk Phase the network number is reserved
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C-9 Configuring App IeLj AppleTalk Zones
Node Numbers
The node number identifies the node which is any device connected to the AppleTalk network The node
number is an 8-bit decimal number that must be unique on that network
In AppleTalk Phase node numbers through 127 are for user nodes node numbers 128 through 254
are for servers and node numbers and 255 are reserved
In AppleTalk Phase you can use node numbers through 253 for any nodes attached to the network Node numbers 254 and 255 are reserved
AppleTalk Address Example
The following is an example of an AppleTalk network address
3.45
In this example the network number is and the node number is 45 You enter both numbers in decimal
Cisco lOS software also displays them in decimal
AppleTalk Zones
zone is logical group of networks The networks in zone can be contiguous or noncontiguous
zone is identified by zone name which can be up to 32 characters long The zone name can include
standard characters and AppleTalk special characters To include special character type colon
followed by two hexadecimal characters that represent the special character in the Macintosh character set
An AppleTalk Phase network can have only one zone
In AppleTalk Phase an extended network can have up to 255 zones nonextended network can have
only zone
Configuration Guidelines and Compatibility Rules
AppleTalk Phase and AppleTalk Phase networks are incompatible and cannot run simultaneously on
the same internetwork As result all routers in an internetwork must support AppleTalk Phase before the network can use Phase routing
If your internetwork has combination of AppleTalk Phase and Phase routers you must observe the following configuration guidelines If you do not follow these guidelines unpredictable behavior might result Note however that you do not need to upgrade all end nodes to use the features provided by our AppleTalk enhancements
The cable range must be one for example 2323
Each AppleTalk network can be member of only one zone
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 10 pgurig AppleTalk AppleTalk Configuration Task List
follow these When using Cisco routers with implementations of AppleTalk by other vendors guidelines
the Macintosh be For Macintosh with an Ethernet card to support extended AppleTalk must
running EtherTalk Version 2.0 or later This restriction does not apply to Macintoshes with only LocalTalk interfaces
Shiva FastPath routers must run K-Star Version 8.0 or later and must be explicitly configured for
extended AppleTalk
Apple Internet Router software Version 2.0 supports transition mode for translation between nonextended AppleTalk and extended AppleTalk on the same network Transition mode requires the
Apple upgrade utility and special patch file from Apple
AppIeTak Configuration Task List
To configure AppleTalk routing perform the tasks in the following sections
Configuring AppleTalk Routing Required
Controlling Access to AppleTalk Networks Optional
Configuring the Name Display Facility Optional
Setting Up Special Configurations Optional
for Configuring AppleTalk Control Protocol PPP Optional
Tuning AppleTalk Network Performance Optional
Configuring AppleTalk Enhanced IGRP Optional
Configuring AppleTalk Interenterprise Routing Optional
Configuring AppleTalk over WANs Optional
Configuring AppleTalk Between LANs Optional
Configuring AppleTalk Between VLANs Optional
Monitoring and Maintaining the AppleTalk Network Optional
for See the AppleTalk Configuration Examples section at the end of this chapter configuration examples
Configuring AppleTalk Routing
You configure AppleTalk routing by first enabling it on the router and then configuring it on each interface
To configure the AppleTalk routing protocol perform the tasks in the following sections The first two
tasks are required the rest are optional
Enabling AppleTalk Routing Required
Configuring an Interface for AppleTalk Required
Selecting an AppleTalk Routing Protocol Optional
Configuring Transition Mode Optional
Enabling Concurrent Routing and Bridging Optional
Configuring Integrated Routing and Bridging Optional
Cisco lOS AppleTalk and Novell IPX Configuration Guide ______P2C-11 Configuring AppleTalk
AppleTalk Configuration Task List
Enabling AppleTalk Routing
To enable AppleTalk routing use the following command in global configuration mode
Command Purpose
Router config appletalk routing Enables AppleTalk routing
The appletalk routing command without any keywords or arguments enables AppleTalk routing using the Routing Table Maintenance Protocol RTMP routing protocol You can enable AppleTalk routing to
use AppleTalk Enhanced IGRP routing protocol instead of RTMP For more information see the
Enabling AppleTalk Enhanced IGRP section later in this chapter
For an example of how to enable AppleTalk routing see the Extended AppleTalk Network Example
section at the end of this chapter
Configuring an Interface for AppleTalk
You configure an interface for AppleTalk by assigning an AppleTalk address or cable range to the
interface and then assigning one or more zone names to the interface You can perform these tasks either manually or dynamically
Manually Configuring an Interface
You can manually configure an interface for nonextended AppleTalk or extended AppleTalk routing
Configuring for Nonextended AppleTalk Routing
To manually configure an interface for nonextended AppleTalk routing use the following commands in
interface configuration mode
Command Purpose
Step Routerconfigif appletalk address nebwork.node Assigns an AppleTalk address to the interface
zone Step Routerconfig-if appletalk zone-name Assigns zone name to the interface
After the address and you assign zone names the interface will attempt to verify them with another
operational router on the connected network If there are any discrepancies the interface will not become
If there operational are no neighboring operational routers the device will assume the configuration of
the interface is correct and the interface will become operational
For an example of how to configure an interface for nonextended AppleTalk routing see the Nonextended AppleTalk Network Example section at the end of this chapter
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 12 guring AppleTalk AppleTalk Configuration Task List
Configuring for Extended AppleTalk Routing
To manually configure an interface for extended AppleTalk routing use the following commands in
interface configuration mode
Command Purpose
Router config-if appletalk cable-range cable-range Assigns cable to an interface Step range
Routerconfig-if appletalk zone zone-name zone name to the interface Step2 Assigns
You can assign more than one zone name to cable range If you do so the first name you assign is
considered to be the default zone You can define up to 255 zones
For an example of how to configure an interface for extended AppleTalk routing see the Extended AppleTalk Network Example section at the end of this chapter
Dynamically Configuring an Interface
If nonextended or an extended interface is connected to network that has at least one other operational
AppleTalk router you can dynamically configure the interface using discovery mode In discovery mode
an interface acquires information about the attached network from an operational router and then uses
this information to configure itself
Benefits
Using discovery mode to configure interfaces saves time if the network numbers cable ranges or zone
names change If any of these changes occur you must make the changes on only one seed router on each network
Discovery mode is useful when you are changing network configuration or when you are adding
router to an existing network
Restrictions
If there is no operational router on the attached network you must manually configure the interface as
described in the previous sections Also if discovery mode interface is restarted another operational
router must be present before the interface will become operational
Discovery mode does not run over serial lines
Caution Do not enable discovery mode on all routers on network If you do so and all the devices restart simultaneously for example after power failure the network will be inaccessible until you manually configure at least one router
Seed Router Starting Sequence
nondiscovery-mode interface also called seed router starts up as follows
The seed router acquires its configuration from memory
If the stored configuration is not completely specified when you assign an AppleTalk address to an
interface on which you assign cable range and zone name the interface will not start up
If the stored configuration is completely specified the interface attempts to verify the stored
configuration with another router on the attached network If any discrepancy exists the interface will not start up
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 13 Configuring AppleTalk
AppleTalk Configuration Task List
If there are no neighboring operational routers the device will assume the stored configuration of
the interface is correct and the interface will become operational
Response to Configuration Queries
Using discovery mode does not affect the ability of an interface to respond to configuration queries from
other routers on the connected network once the interface becomes operational
Dynamically Configuring Nonextended Interface
You can activate discovery mode on nonextended interface in one of two ways depending on whether you know the network number of the attached network
In the first method you immediately place the interface into discovery mode by specifying an AppleTalk address of 0.0 Use this method when you do not know the network number of the attached network To
activate discovery mode for this method use the following command in interface configuration mode
Command Purpose
Routerconfig-if appletalk address 0.0 Places the interface into discovery mode by assigning it the AppleTalk address 0.0
For an example of how to configure discovery mode using this method see the Nonextended Network
in Discovery Mode Example section at the end of this chapter
For the second method you first assign an address to the interface and then explicitly enable discovery mode Use this method when you know the network number of the attached network Note however that you are not required to use this method when you know the network number To activate discovery mode
for this method use the following commands in interface configuration mode
Command Purpose
Router address network.node Step config-if appletalk Assigns an AppleTalk address to the interface
Step Routerconfig-if appletalk discovery Places the interface into discovery mode
Dynamically Configuring an Extended Interface
You can activate discovery mode on an extended interface in one of two ways depending on whether you know the cable range of the attached network
In the first method you immediately place the interface into discovery mode by specifying cable range of 00 Use this method when you do not know the network number of the attached network To activate
discovery mode for this method use the following command in interface configuration mode
Command Purpose
Router 0-0 config-if appletalk cable-range Places the interface into discovery mode by assigning
it the cable range 00
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 14 AppleTalk guring AppleTalk Configuration Task List
first cable and then enable In the second method you assign ranges explicitly discovery mode Use this method when you know the cable range of the attached network Note however that you are not required know the cable To activate mode for this the to use this method if you range discovery method use
following commands in interface configuration mode
Command Purpose
Routerconfig-if appletalk cable-range cable-range Assigns an AppleTalk address to the interface Step
appletalk discovery Places the interface into mode Step2 RouterCOflfig-if discovery
Selecting an AppleTalk Routing Protocol
Once you configure AppleTalk on an interface you can select routing protocol for the interface You can enable the RTMP or Enhanced IGRP routing protocols on any interface You can also enable the AppleTalkUpdate-Based Routing Protocol AURP on tunnel interface
With the appletalk protocol command you can enable some AppleTalk interfaces to use RTMP some
to use Enhanced IGRP and others to use AURP as required by your network topology
To select an AppleTalk routing protocol for an interlace use the following command in interface
configuration mode
Command Purpose
Routerconfig-if appletalk protocol aurp eigrp rtmp Creates anAppleTalkroutingprocess
This command is optional If you do not select routing protocol for an interface Cisco lOS software uses RTMP by default
For an example of how to select an AppleTalk routing protocol using Enhanced IGRP see the
AppleTalk Access List Examples section at the end of this chapter
Configuring Transition Mode
The Cisco lOS software can route packets between extended and nonextended AppleTalk networks that
coexist on the same cable This type of routing is referred to as transition mode
To use transition mode you must have two router ports connected to the same physical cable One port
is configured as nonextended AppleTalk network and the other port is configured as an extended
AppleTalk network Each port must have unique network number because you are routing between
two separate AppleTalk networks the extended network and the nonextended network
To configure transition mode you must have two ports on the same router that are connected to the same
physical cable To configure one port as nonextended AppleTalk network use the following commands
in interface configuration mode
Command Purpose
address network.node the interface Step Routerconfig-if appletalk Assigns an AppleTalk address to
Step Router config-if appletalk zone zone-name Assigns zone name to the interface
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 15 Configuring AppleTalk
AppleTalk Configuration Task List
To configure the second port as an extended AppleTalk network use the following commands in
interface configuration mode
Command Purpose
Step Router configif appletalk cable-range cable-range Assigns an AppleTalk cable range to the interface node
Router Step configif appletalk zone zone-name Assigns zone name to the interface
When you enter interface configuration mode the type of interface must be the same for both ports for example both could be Ethernet and the interface number must be different for example and
For an example of how to configure transition mode see the Transition Mode Example section at the
end of this chapter
EnablinO Concurrent Routing and Bridging
You can route AppleTalk on some interfaces and transparently bridge it on other interfaces
simultaneously To enable this type of routing you must enable concurrent routing and bridging
enable To concurrent routing and bridging use the following command in global configuration mode
Command Purpose
Router crb config bridge Enables concurrent routing and bridging
Configuring Integrated Routing and Bridging
Integrated routing and bridging IRB enables user to route AppleTalk traffic between routed interfaces
and bridge groups or route AppleTalk traffic between bridge groups Specifically local or unroutable traffic is bridged among the bridged interfaces in the same bridge group while routable traffic is routed to other routed interfaces or bridge groups
Using IRB you can do the following
Switch packets from bridged interface to routed interface
Switch packets from routed interface to bridged interface
Switch packets within the same bridge group
For more information about configuring integrated routing and bridging refer to the Configuring
Transparent Bridging chapter in the Cisco lOS Bridging and IBM Networking Configuration Guide
Controlling Access to AppHelalk Networks
An access list is list of AppleTalk network numbers zones or Name Binding Protocol NBP named entities that is maintained by the Cisco lOS software and used to control access to or from specific zones networks and NBP named entities
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 16 onfigurifl9 AppleTalk
AppleTalk Configuration Task List
Types of Access Lists
of lists The software supports the following two general types AppleTalk access
AppleTalk-style access lists which are based on AppleTalk zones or NBP named entities
IP-style access lists which are based on network numbers
Access Lists AppleTalk-StYle
AppleTalk-style access lists regulate the internetwork using zone names and NBP named entities The
main advantage of AppleTalk-style access lists is that they allow you to define access regardless of the
existing network topology or any changes in future topologiesbecause they are based on zones and
NBP named entities zone access list is essentially dynamic list of network numbers The user
specifies zone name but the effect is as if the user had specified all the network numbers belonging to
that zone An NBP named entity access list provides means of controlling access at the network entity level
Using Zone Names
Zone names and NBP named entities are good control points because they allow for network-level
abstractions that users can access
You can express zone names either explicitly or by using generalized-argument keywords Thus using
AppleTalk zone name access lists simplifies network management and allows for greater flexibility when
adding segments because reconfiguration requirements are minimal Using AppleTalk zone name access
lists allows you to manage and control whole sections of the network
Using NBP Named Entities
NBP named entities allow you to control access at the object level Using NBP named entities you can
permit or deny NBP packets from class of objects based on the type portion of the NBP tuple name
from particular NBP named entity based on the object portion of the NBP tuple name or from all NBP
named entities within particular area based on the zone portion of the NBP tuple name You can fully three or partially qualify an NBP tuple name to refine the access control by specifying one two or parts number of the NBP name tuple as separate access list entries tied together by the same sequence
IP-Style Access Lists
IP-style access lists control network access based on network numbers This feature can be useful in
defining access lists that control the disposition of networks that overlap are contained by or exactly
match specific network number range
Additionally you can use IP-style access lists to resolve conflicting network numbers You can use an
access list to restrict the network numbers and zones that department can advertise thereby limiting
advertisement to an authorized set of networks AppleTalk- style access lists are typically insufficient for
this purpose
In general however using IP-style access lists is not recommended because the controls are not optimal
they ignore the logical mapping provided by AppleTalk zones One problem with IP-style access lists is
that when you add networks to zone you must reconfigure each secure router Another problem is that because anyone can add network segments for example when one group of users gets LaserWriter
and installs Cayman GatorBox creating new network segment the potential for confusion and
misconfiguration is substantial
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 17 Configuring AppleTalk AppleTalk Configuration Task List
Combining AppleTalk-Style and IP-Style Entries
You can combine zone network and NBP named entity entries in single access list Cisco lOS software
performs NBP filtering independently on only NBP packets The software applies network filtering in
conjunction with zone filtering However for optimal performance access lists should not include both zones AppleTalk-style and numeric network IP-style entries
Because the Cisco lOS software applies network filtering and zone filtering simultaneously be sure to
add the appropriate access-list permit other-access or access-list permit additional-zones statement the end of the to access list when using only one type of filtering For example suppose you want to deny only zone You do not want any network filtering but the software by default automatically includes
an access-list deny other-access entry at the end of each access list You must then create an access list
that explicitly permits access of all networks Therefore the access list for this example would have an access-list deny zone entry to deny zone an access-list permit additional-zones entry to permit
all other and zones an access-list permit other-access entry to explicitly permit all networks
Types of Filters
You can filter the following types of AppleTalk packets
NBP packets
Data packets
Routing table updates
GetZoneList GZL request and reply packets
Zone Information Protocol ZIP reply packets
Table shows the Cisco lOS software filters for each packet type
Table Packet-Type-to-Filter Mapping
Packet Type Filters That Can Be Applied
NBP packets appletalk access-group in
appletalk access-group out
Data packets appletalk access-group in
appletalk access-group out
Routing table update appletalk distribute-list in appletalk distribute-list out
appletalk permit-partial-zones
appletalk zip-reply-filter
ZIP reply packets appletalk zip-reply-filter
GZL request and reply packets appletalk distribute-list in appletalk distribute-list out
appletalk getzonelist-filter
appletalk permit-partial-zones
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 18 iguring AppleTalk AppleTalk Configuration Task LiiR
Note These types of filters are completely independent of each other which means that if for
example you apply data packet filter to an interface that filter has no effect on incoming
routing table updates or GZL requests that pass through that interface The exceptions to
this rule are that outgoing routing update filters can affect GZL updates and ZIP reply
filters can affect outgoing routing updates
UmpUementation Considerations
Unlike access lists in other protocols the order of the entries in an AppleTalk access list is not important
However keep the following constraints in mind when defining access lists
You must design and type access list entries properly to ensure that entries do not overlap each other
An example of an overlap is if you were to use permit network command and then use deny network command If you do use entries that overlap the last one you used overwrites and removes the previous one from the access list In this example the permit network statement would be removed from the access list when you typed the deny network statement
Each access list always has method for handling packets or routing updates that do not satisfy any
of the access control statements in the access list
To explicitly specify how you want these packets or routing updates to be handled use the
access-list other-access global configuration command when defining access conditions for
networks and cable ranges use the access-list additional-zones global configuration command
when defining access conditions for zones and use the access-list other-nbps global configuration
command when defining access conditions for NBP packets from named entities If you use one of
these commands it does not matter where in the list you place it The Cisco lOS software
automatically places an access-list deny other-access command at the end of the list It also places access-list deny additional-zones and access-list deny other-nbps commands at the end of the
access list when zones and NBP access conditions are denied respectively With other protocols
you must type the equivalent commands last
If do how handle that do of you not explicitly specify to packets or routing updates not satisfy any
the access control statements in the access list the packets or routing updates are automatically denied access and in the case of data packets are discarded
Controlling Access to AppleTalk Networks Task List
To control access to AppleTalk networks perform the tasks in the following sections
Creating Access Lists Optional
Creating Filters Optional
Creating Access Lists
Each An access list defines the conditions used to filter packets sent into or out of the interface access
list is identified by number All access-list commands that specify the same access list number create
single access list
single access list can contain any number and any combination of access-list commands You can include network and cable range access-list commands zone access-list commands and NBP named
entity access-list commands in the same access list
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 19 Configuring AppleTj
AppleTalk Configuration Task List
each of the default However you can specify only one commands that specify actions to take if none of
the access conditions are matched For example single access list can include only one access-list other-access command handle to networks and cable ranges that do not match the access
conditions only one access-list additional-zones command to handle zones that do not match the access
conditions and only one access-list other-nbps command to handle NBP packets from named entities
that do not match the access conditions
You can also set priorities for the order in which outgoing packets destined for specific network are queued based on the access list
Note For priority queueing the Cisco lOS software applies the access list to the destination network
AppleTalk access lists are automatically fast switched Access list fast switching improves the performance of AppleTalk traffic when access lists are defined on an interface
Creating AppleTalk-Style Access Lists
To create AppleTalk-style access lists perform the tasks in the following sections
Creating Zone Access Lists Optional
Creating Priority Queueing Access Lists Optional
Creating NBP A cess Lists Optional
Creating Zone Access Lists
To lists define create access that access conditions for zones AppleTalk-style access lists use one or
more of the following commands in global configuration mode
Command Purpose
access-list access-list--number Routerconfig deny permit Defines access forazone zone zone-name
Router config access-list access-list-number deny permit Defines the default action to take for access additional-zones checks that apply to zones
For examples of how to create access lists see the AppleTalk Access List Examples and Hiding and
Sharing Resources with Access List Examples sections at the end of this chapter
Creating Priority Queueing Access Lists
To assign priority in which packets destined for specific zone will be queued based on the zone
access list use the following command in global configuration mode
Command Purpose
Router corifig list-number priority-list protocol protocol-name Defines access for single network number high medium normal low list access-list-number
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 20 configuring AppleTalk
AppleTalk Configuration Task Lisi
Creating NBP Access Lists
To create access lists that define access conditions for NBP packets based on the NBP packet type from
particular NBP named entities from classes of NBP named entities or from NBP named entities within
particular zones use one or both of the following commands in global configuration mode
Purpose
outerconfig access-list access-list-number deny permit Defines access for anNBPpacket type NBP sequence-number BrRq FwdRq Lookup LkReply mbp named entity type of named entity or named object string type string zone string entities within specific zone
Routerconfig access-list access-list-number deny permit Defines the default action to take for access other-nbPs checks that apply to NBP named entities
For an example of how to create NBP packet filtering access lists see the Defining an Access List to
Filter NBP Packets Example section at the end of this chapter
Creating IP-Style Access Lists
To create access lists that define access conditions for networks and cable ranges IP-style access lists
use one or more of the following commands in global configuration mode
Command Purpose
Router config access-list access-list-number Defines access for single network number deny permit network network
access-list RouterCoflfig access-list-number Defines access for single cable range deny permit cable-range broadcast-permit
Router config access-list access-list-number Defines access for an extended or nonextended deny permit includes cable-range network that overlaps any part of the specified broadcast-permit range
Router config access-list access-list-number Defines access for an extended or nonextended permit within cable deny -range network that is included entirely within the -deny broadcast-permit specified range
Router config access-list access-list-number Defines the default action to takefor access checks deny pernit other-access that apply to network numbers or cable ranges
Creating Filters
filter examines specific types of packets that pass through an interface and permits or denies them
based on the conditions defined in the access lists that have been applied to that interface
To filter different types of AppleTalk packets perform the tasks in the following sections
Creating NBP Packet Filters Optional
Creating Data Packet Filters Optional
Creating Routing Table Update Filters Optional
Creating GetZoneList Filters Optional
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 21 Configuring AppleTalk
AppleTalk Configuration Task List
Enabling ZIP Reply Filters Optional
Enabling Partial Zone Filters Optional
You can apply any number of filters on each interface Each filter can use the same access list or different
access lists Filters can be applied to inbound and outbound interfaces
Routing update filters data packet filters and ZIP reply filters use access lists that define conditions for
networks cable ranges and zones GZL filters use access lists that define conditions for zones only NBP
packet filters use access lists that define conditions for NBP named entities
Creating NBP Packet Filters
To create an NBP packet filter first create an NBP access list as described in the Creating NBP Access
Lists section earlier in this chapter and then apply an NBP filter to an interface
To apply an NBP filter to an interface use the following command in interface configuration mode
Command Purpose
Routerconfig-if appletalk access-group Applies the data packet filter to the interface accees-list-nunther out
S4
Note Prior to Cisco lOS Release 11.2 all NBP access lists were applied to inbound interfaces by default When Cisco lOS Release 11.2 or later software is used the default interface
direction for all access lists including NBP access lists is outbound In order to retain the
inbound direction of access lists created with previous Cisco lOS software releases you
must specify an inbound interface for all NBP access lists by using the appletalk access-group command
Creating Data Packet Filters
data packet filter checks data packets being received on an interface or sent out an interface If the
source network for the packets has access denied these packets are discarded
Data packet filters use access lists that define conditions for networks cable ranges and zones
data filter to that all When you apply packet an interface ensure networks or cable ranges within zone are governed by the same filters For example create filter that works in the following way If the router
receives packet from network that is in zone that contains an explicitly denied network the router discards the packet
To create data packet filter first create network-only access list as described in the Creating Zone Access Lists and Access Lists Creating IP-Style sections earlier in this chapter and then apply data packet filter to an interface
To the data filter apply packet to an interface use the following command in interface configuration mode
Command Purpose
Router config-if access-list-number appletalk access-group Applies the data packet filter to the interface out
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 22 guring AppleTalk AppleTalk Configuration Task List
the Access List For an example of how to create data packet filters see AppleTalk Examples section
at the end of this chapter
Creating Routing Table Update Filters
Routing table update filters control which updates the local routing table accepts and which routes the
local router advertises in its routing updates You create distribution lists to control the filtering of
routing updates
Filters for incoming routing updates use access lists that define conditions for networks and cable ranges
only Filters for outgoing routing updates use access lists that define conditions for networks and cable
ranges and for zones
When filtering incoming routing updates each network number and cable range in the update is checked
against the access list If you have not applied an access list to the interface all network numbers and
table If list has been to the cable ranges in the routing update are added to the routing an access applied denied are added interface only network numbers and cable ranges that are not explicitly or implicitly
to the routing table
The following conditions are also applied when routing updates generated by the local router are filtered
The network number or cable range is not member of zone that is explicitly or implicitly denied
cable that is member of the If partial zones are permitted at least one network number or range
all network zone is explicitly or implicitly permitted If partial zones are not permitted the default
numbers or cable ranges that are members of the zone are explicitly or implicitly permitted
Creating Routing Table Update Filters for Incoming Updates
in To create filter for routing table updates received on an interface create an access list as described
the Creating IP-Style Access Lists section earlier in this chapter and then apply routing table update
filter to an interface
S4
Note Cisco lOS software ignores zone entries Therefore ensure that access lists used to filter
incoming routing updates do not contain any zone entries
command in interface To apply the filter to incoming routing updates on an interface use the following
configuration mode
Command Purpose
Router config-if appletalk distribute..lit access-list-number in Applies the routing update filter
For an example of how to create filter for incoming routing table updates see the AppleTalk Access List Examples section at the end of this chapter
Creating Routing Table Update Filters for Outgoing Updates
list described To create filter for routing table updates sent out from an interface create an access as
earlier in this in the Creating Zone Access Lists and Creating IP-Style Access Lists sections chapter
and then apply routing table update filter to an interface
Note You can use zone entries in access lists used to filter outgoing routing updates
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 23 Configuring AppleTLJ AppleTalk Configuration Task List
To filter apply to routing updates sent out from an interface use the following command in interface
configuration mode
Command Purpose
Routerconfig-if appletalk diatribute-liat ccess-1ist-number out Applies the routing update filter
Note AppleTalk zone access lists on an Enhanced IGRP interface will not filter the distribution
of Enhanced IGRP routes When the appletalk distribute-list out command is applied to Enhanced an IGRP interface any access-list zone commands in the specified access list will be ignored
Creating GetZoneList Filters
The Macintosh Chooser uses ZIP GZL requests to compile list of zones from which the user can select services router the network the Any on same as Macintosh can respond to these requests with GZL
reply You can create GZL filter to control which zones the Cisco lOS software mentions in its GZL
this of filter has the effect replies Creating type of controlling the list of zones that are displayed by the Chooser
should When defining GZL filters you ensure that all routers on the same network filter GZL replies
the Chooser will list identically Otherwise different zones depending on which device responded to the
inconsistent filters in request Also can result zones appearing and disappearing every few seconds when the remains in the Chooser user Because of these inconsistencies you should normally apply GZL filters
only when all routers in the internetwork are Cisco routers unless the routers from other vendors have similar feature
ZIP is When GZL reply generated only zones that satisfy the following conditions are included
If partial zones are permitted at least one network number or cable range that is member of the
zone is explicitly or implicitly permitted
If partial zones are not permitted the default all network numbers or cable ranges that are members
of the zone are explicitly or implicitly permitted
The zone is explicitly or implicitly permitted
also Replies to GZL requests are filtered by any outgoing routing update filter that has been applied to
the interface filter if same You must apply GZL only you want additional filtering to be applied to
This filter is GZL replies rarely needed except to eliminate zones that do not contain user services
GZL filter is not for network Using complete replacement anonymous numbers To prevent users from all seeing zone routers must implement the GZL filter If any devices on the network are from other vendors the GZL filter will not have consistent effect
To create GZL filter create an access list as described in the Creating Zone Access Lists section
earlier in this chapter and then apply GZL filter to an interface
To the apply GZL filter to an interface use the following command in interface configuration mode
Command Purpose Routerconfig-if appletalk getzonelist-filter access-1is-nurnber Applies the GZL filter
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 24 AppleTalk
AppleTalk Configuration Task Lii
For an example of how to create GZL filters see the GZL and ZIP Reply Filter Examples section at
the end of this chapter
Enabling ZIP Reply Filters
ZIP reply filters limit the visibility of zones from routers in unprivileged regions throughout the
internetwork These filters filter the zone list for each network provided by router to neighboring
devices to remove restricted zones
ZIP reply filters apply to downstream routers not to end stations on networks attached to the local router
With ZIP reply filters when downstream routers request the names of zones in network the local router
replies with the names of visible zones only It does not reply with the names of zones that have been
hidden with ZIP reply filter To filter zones from end stations use GZL filters
software sends out in ZIP reply filters determine which networks and cable ranges the Cisco lOS routing
updates Before sending out routing updates the software excludes the networks and cable ranges whose
zones have been completely denied access by ZIP reply filters Excluding this information ensures that
routers receiving these routing updates do not send unnecessary ZIP requests
Access Lists section To create ZIP reply filter create an access list as described in the Creating Zone
earlier in this chapter and then apply ZIP reply filter to an interface
To apply the ZIP reply filter to an interface use the following command in interface configuration mode
Command Purpose
Routerconfig-if appletalk zip-reply-filter access-list-number Applies the ZIP reply filter
Filter For an example of how to create GZL and ZIP reply filters see the GZL and ZIP Reply Examples
section at the end of this chapter
Enabling Partial Zone Filters
If access to any network in zone is denied access to that zone is also denied by default However if denied you enable partial zones access to other networks in that zone is no longer
control list The permitting of partial zones provides IP-style access control If enabled the access
behavior associated with prior software releases is restored In addition NBP cannot ensure consistency
and uniqueness of name bindings
affected If you permit partial zones AppleTalk caimot maintain consistency for the nodes in the zones and and the results are undefined With this option enabled an inconsistency is created for the zone
several assumptions made by some AppleTalk protocols are no longer valid
To enable partial zone filters use the following command in global configuration mode
Command Purpose
Routerconfig appletalk permit-partial-zones Permits access to networks in zone in which access to another
network in that zone is denied
Permitting partial zones affects the outgoing routing update and GZL filters
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 25 Configuring AppleTaj AppleTalk Configuration Task List
Configuring the Name Display Facility
The AppleTalk NBP associates AppleTalk network entity names that is AppleTalk network-addressable
services with network addresses NBP allows you to specify descriptive or symbolic names for entities
instead of their numerical addresses When you specify the name of an AppleTalk device NBP translates the of the device into the network address of the The entity name device name binding process includes name registration name confirmation name deletion and name lookup
Node addresses can change frequently because AppleTalk uses dynamic addresses Therefore NBP
associates numerical node addresses with aliases that continue to reference the correct addresses if the
addresses These node addresses do change not change very frequently because each device keeps track
of the last node number it was assigned Typically node numbers change only if device is shut down
for an extended period of time or if the device is moved to another network segment
To control the name display facility use one or both of the following commands in global configuration mode
Command Purpose
Router config appletalk lookup-type service-type Specifies which service types are retained in the name cache
Router config appletalk naxne-lookup-interval seconds Sets the interval between service pollings by the router on its AppleTalk interfaces
Setting Up Special Configurations
To set up special configurations perform the tasks in the following sections based on desired service implementations
Configuring Free-Trade Zones Optional
Configuring SNMP over DDP in AppleTalk Networks Optional
Configuring AppleTalk Tunneling Optional
Configuring AppleTalk MacIP Optional
Configuring IPTalk Optional
Configuring SMRP over AppleTalk Optional
Configuring Free-Trade Zones
free-trade is of zone part an AppleTalk internetwork that is accessible by two other parts of the
internetwork neither of which can access the other You might want to create free-trade zone to allow
the exchange of information between two organizations that otherwise want to keep their internetworks
isolated from each other or that do not have physical connectivity with one another
To establish free-trade zone use the following command in interface configuration mode
Command Purpose
Routerconfig-if appletalk free-trade-zone Establishes free-trade zone
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C-26 Configuring AppleTalk
AppleTalk Configuration Task List
For an example of how to configure free-trade zone see the Hiding and Sharing Resources with Access List Examples section and the Establishing Free-Trade Zone Example section at the end of
this chapter
Configuring SNMP over DDP in AppleTalk Networks
The Simple Network Management Protocol SNMP normally uses the IF connectionless datagram The Cisco lOS software lets service the User Datagram Protocol UDP to monitor network entities service Use DDP if you run SNMP using Datagram Delivery Protocol DDP the AppleTalk datagram you have SNMP consoles running on Macintosh
before You must configure AppleTalk routing globally and on an interface basis you configure SNMP command table for the router therefore you need to disable SNMP as shown in the following
in To configure SNMP in AppleTalk networks use the following commands beginning global
configuration mode
Command Purpose
Step Router config no snmp server Disables SNMP
Step Router config 4f appletalk routing Enables AppleTalk routing
Step Routerconfig appletalk event-logging Enables AppleTalk event logging
Step Router config interface type number Enters interface configuration mode
Step Routerconfig-if ip address ip-address mask Enables IP routing on the interface
Step Router config-if appletalk cable-range cable-range Enables AppleTalk routing on the interface node
the network Step Router config-if appletalk zone zone-name Sets zone name for AppleTalk
Step Router config-if snmp-server community string Enables SNMP server operations
the end of this For an example of how to configure SNMP see the SNMP Example section at chapter
and Network in For information about configuring SNMP refer to the Monitoring the Router chapter
the Cisco lOS Configuration Fundamentals Configuration Guide
Configuring AppleTalk Tunneling
via virtual interfaces Tunneling provides means for encapsulating packets inside routable protocol them inside frames from Encapsulation takes packets or frames from one network system and places
another network system There are three ways to configure AppleTalk tunneling so that you can connect the Internet IF remote AppleTalk networks across foreign protocol backbone such as or
Configuring AURP
Configuring GRE
Configuring Cayman Tunneling
The method of tunneling is chosen based on the end destination and your encapsulation type
tunnels links Multiple tunnels originating from the router are supported Logically are point-to-point link and therefore require that you configure separate tunnel for each
Guide Cisco lOS AppleTalk and Novell IPX Configuration P2C 27 Configuring App IeTa_j AppleTalk Configuration Task List
If traffic due you are experiencing congestion to RTMP overhead you can resolve this problem by using one of two AppleTalk tunneling methodsAppleTalk Update-Based Routing Protocol AURP or GRE tunneling The AppleTalk packets will be tunneled through foreign protocol such as IP Tunneling
encapsulates an AppleTalk packet inside the foreign protocol packet which is then sent across the
backbone to destination router The destination router then de-encapsulates the AppleTalk packet and
if necessary routes the packet to normal AppleTalk network The encapsulated packet benefits from
any features normally enjoyed by IP packets including default routes and load balancing
Configuring AURP
The first and most often recommended AppleTalk tunneling method is to enable AppleTalk Update-Based Routing Protocol AURP When two AppleTalk networks are connected with
non-AppleTalk backbone such as IP the relatively high bandwidth consumed by the broadcasting of RTMP data packets may impact the network performance of the backbone Using AURP will lower the
routing protocol overhead across WAN or backbone because it changes the encapsulation method as
well as the routing algorithm to something more like link state routing
Note Bandwidth is usually more constrained in WAN than on backbone
is AURP standard Apple Computer routing protocol that provides enhancements to the AppleTalk
routing protocols that are compatible with AppleTalk Phase The primary function of AURP is to
connect two or more noncontiguous AppleTalk internetworks that are separated by non-AppleTalk
network such as IP In these configurations you would want to use AURP instead of RTMP because AURP sends fewer routing packets than RTMP
You configure AURP on tunnel interface Tunneling encapsulates an AppleTalk packet inside an IP
packet which is sent across the backbone to destination router The destination device then extracts
the AppleTalk packet and if necessary routes it to an AppleTalk network The encapsulated packet
benefits from any features normally applied to IP packets including fragmentation default routes and load balancing
After domain for you configure an AppleTalk AppleTalk interenterprise features you can apply the
features to tunnel interface configured for AURP by assigning the domain number to the interface
Because route redistribution is disabled by default you need to enable it by using the appletalk
route-redistribution command Route redistribution is enabled by default only when Enhanced IGRP
is enabled
To configure AURP use the following commands beginning in global configuration mode
Command Purpose
Router Step config appletalk route-redistribution Enables route redistribution
Step Router config interface number type Configures an interface to be used by the tunnel
Step3 Routerconfig-if ip address ip-address mask Configures anIP address
interface tunnel Step Routerconfig-if number Configures tunnel interface
Step Routerconfig-if appletalk protocol aurp Creates an AURP routing process
Step Router config-if tunnel source Specifies the interface out of which the encapsulated ip-address type number packets will be sent
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 28 AppleTalk guring AppleTalk Configuration Task List
Command Purpose
destination gouterconfig-if tunnel Specifies the IP address of the router at the far end of Step hosname ip-address the tunnel
Routerconfig-if tunnel mode aurp Enables AURP tunneling Step
You can configure AURP on tunnel interface to inherit AppleTalk interenterprise routing remapping
hop count reduction and ioop detection characteristics configured for specific AppleTalk domain To
do so these features must first be configured for the AppleTalk domain using the commands described
in the tasks Enabling AppleTalk Interenterprise Routing Remapping Network Numbers and Controlling Hop Count within the section Configuring AppleTalk Interenterprise Routing later in
this chapter
To configure AURP for AppleTalk interenterprise routing features use the following commands in
interface configuration mode
Command Purpose
Router interface tunnel number the tunnel interface Step config-if Specifies
Router appletalk protocol aurp Creates an AURP Step config-if routing process
tunnel mode Enables Step Router config-if aurp AURP tunneling
Router tunnel source the interface out of which the Step configif Specifies encapsulated tie number ip-address packets will be sent
tunnel destination hostname the IP address of the router at the far end of Step Router config-if Specifies ip-address the tunnel
Router config-if appletalk domain-group the number of the Step Assigns predefined AppleTalk domain-number domain to which the AppleTalk interenterprise
features are configured to the tunnel interface
configured for AURP
For an example of how to configure AURP on tunnel interface to inherit AppleTalk interenterprise
routing features for specific AppleTalk domain see the AppleTalk Interenterprise Routing over AURP
Example section at the end of this chapter
this the By default ATJRP sends routing updates every 30 seconds To modify interval use following
command in global configuration mode
Command Purpose
Routerconfig appletalk aurp update-interval seconds Sets the minimum interval between AURP routing updates
To set the AURP last-heard-from timer value use the following command in interface configuration mode
Command Purpose
Router conf ig-if appletalk aurp tickle-time seconds Sets the AURP last-heard-from timer value
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 29 Configuring AppleTalk
AppleTalk Configuration Task List
Configuring GRE
The second AppleTalk tunneling method proprietary tunnel protocol known as generic routing
encapsulation GRE is recommended when you want to use tunneling to connect one Cisco router to another When you use GRE tunneling you must have Cisco routers at both ends of the tunnel
connection You can also reduce RTMP overhead by using GRE tunneling Since you do not need to run
RTMP through GRE tunnels you can significantly improve the network traffic
To configure GRE tunnel use the following commands in interface configuration mode
Command Purpose
Router interface tunnel number Step config-if Configures tunnel interface
Step Router config-if tunnel source Specifies the interface out of which the encapsulated ip-address type number packets will be sent
Router tunnel destination Step config-if Specifies the IP address of the router at the far end of the hostname ip-address tunnel
Step Router config-if tunnel mode gre ip Enables GRE tunneling
Configuring Cayman Tunneling
The third AppleTalk tunneling method Cayman tunneling enables routers to interoperate with Cayman GatorBoxes Cayman tunneling is used to connect remote AppleTalk networks across foreign protocol
backbone such as the Internet or backbone that is IP-only for administrative or security reasons You
can tunnel AppleTalk by using Cayman tunneling as designed by Cayman Systems
When you use Cayman tunneling you can have Cisco routers at either end of the tunnel or you can have GatorBox at one end and Cisco router at the other end
To configure Cayman tunnel use the following commands in interface configuration mode
Command Purpose
Step Router config-if interface tunnel number Configures tunnel interface
Router tunnel Step config-if source Specifies the interface out of which the encapsulated ir-address tiie number packets will be sent
Step Routerconfig-if tunnel destination Specifies the IP address of the router at the far end of the hostname ip-address tunnel
Step Routerconfig-if tunnel node cayman Enables Cayman tunneling
Caution Do not configure Cayman tunnel with an AppleTalk network address
Configur i j AppleTalk MacUP
Cisco lOS software implements MacIP which is protocol that allows routing of IP datagrams to IP
clients using the DDP for low-level encapsulation
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 30 ging AppleTalk AppleTalk Configuration Task List
The Cisco Implementation of AppleTalk MacIP
Cisco lOS software implements the MacIP address management and routing services described in the
draft Internet RFC Standard for the Transmission of Internet Packets over AppleTalk Networks Our
implementation of MacIP conforms to the September 1991 draft RFC with the following exceptions
The software does not fragment IP datagrams that exceed the DDP maximum transmission unit MTh and that are bound for DDP clients of MacIP
The software does not route to DDP clients outside of configured MacIP client ranges
When to Use AppleTalk MaciP
Some situations require the use of MacIP For example if some of your Macintosh users use AppleTalk
Remote Access ARA or are connected to the network using LocalTalk or PhoneNet cabling systems
then MacIP is required to provide access to IP network servers for those users
be useful IP address allocations for MacIP services also can when you are managing large dynamic Macintosh population
Advantages of Using MaclP
The following are advantages to using MacIP when you are managing IP address allocations for large dynamic Macintosh population
location Macintosh TCP/IP drivers can be configured in completely standard way regardless of the
of the Macintosh Essentially the dynamic properties of AppleTalk address management become available for IP address allocation
You can modify all global parameters such as IP subnet masks Domain Name System DNS
services and default routers Macintosh IP users receive the updates by restarting their local TCP/IP drivers
The network administrator can monitor MacIP address allocations and packet statistics remotely by
using the Telnet application to attach to the console allowing central administration of IP
allocations in remote locations For Internet sites it allows remote technical assistance
Implementation Considerations
Consider the following items when implementing MacIP on Cisco routers
Each packet from Macintosh client destined for an IP host or vice versa must pass through the
router if the client is using the device as MacIP server The router is not always necessary hop in so passing through the router increases traffic through the device There is also slight increase
CPU use that is directly proportional to the number of packets delivered to and from active MacIP clients
Memory usage increases in direct proportion to the total number of active MacIP clients about
80 bytes per client
Also when you configure MacIP on the Cisco lOS software you must configure AppleTalk as follows
AppleTalk routing must be enabled on at least one interface
IP routing must be enabled on at least one interface
The MacIP zone name you configure must be associated with configured or seeded zone name
The MacIP server must reside in the AppleTalk zone
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 31 Configuring Applelalk_j AppleTalk Configuration Task List
Any IF address specified in configuring MacIF server using an appletalk macip command must
be associated to specific IP interface on the router Because the Cisco lOS software is acting as for MacIP IP address proxy clients you must use an to which Address Resolution Protocol ARP can respond
If you are using MacIP to allow Macintoshes to communicate with IF hosts on the same LAN
segment that is the Macintoshes are on the router interface on which MacIP is configured and the
IF hosts have extended IF access lists these access lists should include entries to permit IP traffic
destined for these IF hosts from the MacIF addresses If these entries are not present packets
destined for IP hosts on the local segment will be blocked that is they will not be forwarded
When setting up MacIF routing keep the following address range issues in mind
Static and dynamic resource statements are cumulative and you can specify as many as necessary However if possible you should specify single all-inclusive range rather than several adjacent For ranges example specifying the range 172.31.121.1 to 172.31.121.10 is preferable to specifying
the ranges 172.31.121.1 to 172.31.121.5 and 172.31.121.6 to 172.31.121.10
Overlapping resource ranges for example 172.31.121.1 to 172.31.121.5 and 172.31.121.5 to
172.31.121.10 are not allowed If it is necessary to change range in running server use the form of the negative resource address assignment command such as no appletalk macip dynamic
ip-address ip-address zone server-zone to delete the original range followed by the corrected range statement
add You can IF address allocations to running server at any time as long as the new address range does not overlap with one of the current ranges
Corifigur ig ApplelaHk MaciP Task List
To configure MacIF perform the tasks in the following sections
Establishing MacIP Server for Zone Required
Allocating IP Addresses for Macintosh Users Required
Establishing MaciP Server for Zone
To establish MacIP server for specific zone use the following command in global configuration mode
Command Purpose
Router config appletalk macip server ip-address Establishes MacIP server for zone zone server-zone
Note Note that the MacIP server must reside in the default AppleTalk zone
You can configure multiple MacIF servers for router but you can assign only one MacIP server to and zone you can assign only one IP interface to MacIP server In general you must be able to establish an alias between the IP address you assign with the appletalk macip server global
configuration command and an existing IF interface For implementation simplicity the address you
specify in this command should match an existing IP interface address
server is not registered by NBP until at least one MacIP resource is configured
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 32 pguring AppleTalk AppleTalk Configuration Task List
Allocating IP Addresses for Macintosh Users
You allocate IP addresses for Macintosh users by specifying at least one dynamic or static resource
address assignment command for each MacIP server
Allocating IP Addresses Using Dynamic Addresses
Dynamic clients are those that accept any IP address assignment within the dynamic range specified Dynamic addresses are for users that do not require fixed address but can be assigned addresses from pooi
To allocate IP addresses for Macintosh users if you are using dynamic addresses use the following
command in global configuration mode
Command Purpose
Router config appletalk macip dynamic Allocates an IP address to MacIP client ip-address zone server-zone
the For an example of configuring MacIP with dynamic addresses see AppleTalk Interenterprise Routing over ATJRP Example section at the end of this chapter
Allocating IP Addresses Using Static Addresses
Static addresses are for users that require fixed addresses for IP DNS services and for administrators that
do not want addresses to change so they always know the IP addresses of the devices on their network
To allocate IP addresses for Macintosh users if you are using static addresses use the following
command in global configuration mode
Command Purpose
Router config appletalk macip atatic ip-address Allocates an IP address to be used by MacIP client that has
zone server-zone reserved static IP address
section at the end For an example of configuring MacIP with static addresses see the MacIP Examples
of this chapter
in for In general it is recommended that you do not use fragmented address ranges configuring ranges
MacIP However if fragmented address ranges are unavoidable use the appletalk macip dynamic static command to specify as many addresses or ranges as required and use the appletalk macip
command to assign specific address or address range
Configuring IPTaUk
in IP IPTalk is used to route IPTalk is protocol for encapsulating AppleTalk packets datagrams and communicate with on hosts that AppleTalk packets across non-AppleTalk backbones to applications cannot otherwise communicate via AppleTalk such as the Columbia AppleTalk Package CAP IPTalk
also allows serial connections to use IPTalk Serial Line Internet Protocol SLIP drivers
If your system is Sun or Digital Equipment Corporation ULTRIX system it may be possible to run
would look like other CAP directly in mode that supports EtherTalk In this case your system any AppleTalk node and does not need any special IPTaIk support However other UNIX systems for which IPTaIk EtherTalk support is not available in CAP must run CAP in mode that depends upon
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 33 Configuring AppleTalk
AppleTalk Configuration Task List
For installation instructions for refer CAP to Kinetics IP KIP gateways and the file atalkatab If you
use Cisco IPTalk it is is support not necessary nor it desirable to use atalkatab Cisco IPTallc support
assumes that you want to use the standard AppleTalk routing protocols to perform all wide-area KIP and atalkatab based AppleTalk routing are on an alternative routing strategy in which AppleTalk
packets are sent using IP routing It is possible to use both strategies at the same time however the
interaction between the two routing techniques is not well defined
If network has from other vendors your routers that support atalkatab you should disable atalka tab support on them to avoid mixing the routing strategies The installation instructions provided with some of these products encourage you to use atalkatab for complex networks However with Cisco routers it is not necessary because our implementation of IPTalk integrates IPTalk into the standard AppleTalk network routing
The network in diagram Figure illustrates how you should set up IPTaIk In this configuration you enable both standard AppleTalk EtherTalk and IPTaIk on the Ethernet networks on Router and
Router These routers then use EtherTalk to communicate with the LocalTalk routers and Macintosh and computers IPTalk to communicate with the UNIX systems On the LocalTalk routers you also should enable both EtherTalk and IPTa1k making sure you configure IPTaIk with atalkatab disabled These routers then use IPTalk to communicate with the UNIX systems adjacent to them and EtherTalk
to communicate with the remainder of the AppleTalk network This configuration strategy minimizes the number of hops between routers If you did not enable IPTalk on the LocalTalk routers systems on the LocalTalk router that wanted to communicate with the adjacent UNIX system would need to go through Router or Router creating an unnecessary extra hop
IIote In the shown in configuration Figure all traffic between systems on the left and right sides of the packet-switched network transit via Router and Router using AppleTalk
If enable routing you were to atalkatab support on the LocalTalk routers hidden path would be established between Router and Router unknown to the standard AppleTalk In routing protocols large network this hidden path could result in traffic taking
inexplicable routes
Figure IPTalk Configuration Example
UNIX Macintosh system Macintosh UNIX system
Locallalk LocalTalk
To configure IPTalk on an interface perform the following tasks
Configuring IP Encapsulation of AppleTalk Packets Required
Specifying the UDP Port Ranges Required
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 34 guring AppleTalk AppleTalk Configuration Task List
configuring IP Encapsulation of AppleTalk Packets
that do To allow AppleTalk to communicate with UNIX hosts running older versions of CAP not support
native AppleTalk EtherTalk encapsulations you must configure IP encapsulation of AppleTalk packets Typically Apple Macintosh users would communicate with these servers by routing their connections through Kinetics FastPath router running KJP software Newer versions of CAP provide native
AppleTalk EtherTalk encapsulations so the IPTalk encapsulation is no longer required The Cisco implementation of IPTalk assumes that AppleTalk is already being routed on the backbone because
there is currently no LocalTalk hardware interface for our routers
You configure IPTalk on tunnel interface Tunneling encapsulates an AppleTalk packet inside an IP
packet which is sent across the backbone to destination router The destination device then extracts
the AppleTalk packet and if necessary routes it to an AppleTalk network The encapsulated packet benefits from any features normally applied to IP packets including fragmentation default routes and load balancing
The Cisco implementation of IPTalk does not support manually configured AppleTalk-to-IP-address mapping The address mapping provided is the same as the Kinetics IPTalk implementation when This address works follows AppleTalk-to-IP-address mapping is not enabled mapping as
The IP subnet mask used on the router tunnel source interface on which IPTalk is enabled is inverted ones complement
The result is then masked against 255 OxFF hexadecimal
The result of this is then masked against the low-order bits of the IP address to give the AppleTalk node number
The following example shows how to configure address mapping
interface EthernetO
ip address 172.16.1.118 255.255.255.0 appletalk address 20.129 appletalk zone Native AppleTalk interface TunnelO tunnel source Etherneto tunnel mode iptalk appletalk iptalk 30 UDPZ0ne
is then masked with 255 First the IP subnet mask of 255.255.255.0 is inverted to 0.0.0.255 This value
to give 255 Next 255 is masked with the low-order bits of the interface IP address 118 to yield an AppleTalk node number of 118 which means that the AppleTalk address of the Ethernet interface seen
in the UDPZone zone is 30.118
Note If the host field of an IP subnet mask for an interface is longer than bits it will be possible mask for the to obtain conflicting AppleTalk node numbers For instance if the subnet
Ethernet interface above is 255.255.240.0 the host field is 12 bits wide
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 35 Configuring AppleTalk
AppleTalk Contiguration Task List
To configure IP encapsulation of AppleTalk packets use the following commands in interface
configuration mode
Command Purpose
interface number Step Routerconfig-it type Configures an interface to be used by the tunnel
Step Routerconfig-if ip address ip-address mask Configures anIP address
Step Router config-if interface tunnel number Configures tunnel interface
Router config-if tunnel source Step Specifies the interface out of which the encapsulated ip-address type number packets will be sent
Step Router config-if tunnel mode iptalk Enables IPTalk tunneling
For of an example configuring IPTalk see the IPTaIk Example section at the end of this chapter
Specifying the UDP Port Ranges
of IPTalk 1988 Implementations prior to April mapped well-known DDP socket numbers to privileged number 768 In UDP ports starting at port April 1988 the Network Information Center NIC assigned of for the defined range UDP ports DDP well-known sockets starting at UDP port number 200 and
assigned these ports the names at-nbp at-rtmp at-echo and at-zis Release and later of the CAP
program dynamically decides which port mapping to use If there are no AppleTalk service entries in the
/etc/services file of the UNIX system CAP uses the older mapping starting at UDP port number 768
The default UDP port mapping supported by our implementation of IPTalk is 768 If there are AppleTalk service entries in the /etc/services file of the UNIX system you should specify the beginning of the UDP
port mapping range
To specify the UDP port number that is the beginning of the range of UDP ports used in mapping
AppleTalk well-known DDP socket numbers to UDP ports use the following command in global
configuration mode
Command Purpose
Router config appletalk iptalk.-baseport the Specifies starting UDP port number
For an example of configuring IPTa1k see the IPTalk Example section at the end of this chapter
Configuring SMRP over AppleTalk
The Simple Multicast Routing Protocol SMRP provides an internetwork-wide multicast service that the of data supports sending from single station to multiple stations on an internetwork with minimal
is packet replication SMRP connectionless protocol that provides best-effort delivery of multicast
packets SMRP operates independently of the network layer in use SMRP supports routing of multicast
packets to multicast groups
The Cisco current implementation of SMRP provides multicast routing functions over AppleTalk networks Advanced multimedia applications such as QuickTime Conferencing QTC allow for two or machines more to communicate in session By routing AppleTalk packets to all members of
multipoint group without replicating packets on link SMRP presents an economical and efficient way this kind of to support communication while conserving network bandwidth
Cisco lOS AppleTalk and Novell IPX Configuration Guide Configuring AppleTalk
AppleTalk Configuration Task List
The Cisco implementation of SMRP can be characterized by the following aspects
Group membership services that determine which hosts receive multicast traffic SMRP allows
multicast sessions in it host to register dynamically for the which elects to participate
Dynamic multicast routing that gives Cisco routers the ability to dynamically identify the optimum
path for AppleTalk multicast traffic
Just-in-time packet replication services that duplicate packet when it reaches forks in the
destination path of the group Cisco routers send only one copy of each packet over each physical network
Fast switching of SMRP data packets that allows higher data traffic throughput and less CPU utilization
Figure shows how SMRP multicasting of packets proceeds across an AppleTalk network The source
router Router sends multicast packet only once on the local AppleTalk network
Figure SMRP Packet Transmission over AppleTalk
Sends Duplicates
single packet packet
Router Router
Sends only to ports
with group members
To this Applications produced by Apple Computer such as QTC will support SMRP provide support Cisco and Apple Computer have entered into partnership to become the first internetworking vendors
to license the SMRP technology
To enable SMRP routing over AppleTalk networks use the following command in global configuration mode
Command Purpose
Routerconfig smrp routing Enables SMRP
in interface To configure SMRP over AppleTalk for specific interface use the following command
configuration mode
Command Purpose
Router config-if smrp protocol appletalk Configures an SMRP on the interface beginning-end
Note The network-range option maps to the AppleTalk cable range by default
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 37 Configuring AppleTalk
AppleTalk Configuration Task List
Fast allows switching higher throughput by switching packet using cache created by previous packets By default fast switching is enabled on all SMRP ports network protocol and interface comprise an SMRP port
SMRP the table forward uses forwarding to packets for particular SMRP group For each group the forwarding table lists the parent interface and address and one or more child interfaces and addresses data for When an SMRP group arrives on the parent interface the router forwards it to each child interface The SMRP fast-switching cache table specifies whether to fast switch SMRP data packets out
the interfaces specified by the forwarding table
To disable SMRP fast switching on an interface use the following command in interface configuration mode
Command Purpose
Router config-if no mroute-cache smrp protocol appletalk Disables SMRP fast switching on an interface
Configuring AppleTalk Control Protocol for PPP
You can configure an asynchronous interface including the auxiliary port on some Cisco routers to use
AppleTalk Control Protocol ATCP so that users can access AppleTalk zones by dialing into the router
via PPP to this interface Asynchronous interfaces are configured with ATCP through negotiation
protocol as defined in RFC 1378 Users accessing the network with ATCP can run AppleTalk and IP natively on remote Macintosh access any available AppleTalk zones from the Chooser use networked
peripherals and share files with other Macintosh users
You create an internal network with the appletalk internal-network command This network is virtual
network and exists only for accessing an AppleTalk internetwork through the server
To create new AppleTalk zone enter the appletalk virtual-net command and use new zone name this is then the network number only one associated with this zone To add network numbers to an
existing AppleTalk zone use the existing zone name in the command the network number is then added
to the existing zone
Routing is not supported on these interfaces
To enable ATCP for PPP use the following commands in interface configuration asynchronous mode
Command Purpose
Router interface number Step config-if async Specifies an asynchronous interface
Step Routerconfig-if appletalk virtual-net Creates an internal network on the server network-number zone-name
Step Routerconfig-if encapsulation ppp Enables PPP encapsulation on the interface
Router Step config-if appletalk client-mode Enables client-mode on the interface
For an of example configuring ATCP see the AppleTalk Control Protocol Example section at the end
of this chapter
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 38 Configuring AppleTalk
AppleTalk Configuration Task List
Tuning AppUeTak Network Performance
To tune AppleTalk network performance perform one or more of the tasks described in the following
sections
Controlling Routing Updates Optional
Assigning Proxy Network Numbers Optional
Enabling Round-Robin Load Sharing Optional
Disabling Checksum Generation and Verification Optional
Controlling the AppleTalk ARP Table Optional
Controlling the Delay Between ZIP Queries Optional
Logging Significant Network Events Optional
Disabling Fast Switching Optional
Controlling Routing Updates
RTMP establishes and maintains the AppleTalk routing table To control packet routing and control
routing updates perform the tasks in the following sections
Disabling the Processing of Routed RTMP Packets Optional
Enabling RTMP Stub Mode Optional
Disabling the Transmission of Routing Updates Optional
Associated Zones Preventing the Advertisement of Routes to Networks with No Optional
Timers Setting Routing Table Update Optional
Setting the Routing Update Interval Timer Optional
Disabling the Processing of Routed RTMP Packets
By default the Cisco lOS software performs strict RTMP checking which discards any RTMP packets
sent by routers not directly connected to the local device that is sent by devices that are not neighbors
In this case the local router does not accept any routed RTMP packets whose source is remote network
In almost all situations you should leave RTMP checking enabled
To disable RTMP checking and enable the processing of routed RTMP packets use the following
command in global configuration mode
Command Purpose
Router config no appletalk strict-rtmp-checking Disables strict checking of RTMP updates
Enabling RTMP Stub Mode
You can enable AppleTalk RTMP stub mode This mode allows routers running Enhanced IGRP and
RTMP to reduce the amount of CPU time that RTMP modules use In this mode RTMP modules send
and receive only stub RTMP packets
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 39 Configuring AppleT_
AppleTalk Configuration Task List
stub packet is only the first tuple of an RTMP packet The first tuple indicates the network number
range assigned to that network End nodes use stub packets to determine if their node number is in the correct network range
To enable AppleTalk RTMP stub mode use the following command in interface configuration mode
Command Purpose
Router config-if appletalk rtmp-stub Enables RTMP stub mode
the Disabling Transmission of Routing Updates
By default routers receive routing updates from their neighboring devices and periodically send routing
updates to their neighbors You can configure the Cisco lOS software so that it only receives routing
updates but does not send any updates You might want to use this type of configuration to keep
particular router that is unreliable from sending routing updates to its neighbors
To disable the transmission of routing updates use the following command in interface configuration mode
Command Purpose
Router config-if no appletalk send..rtmps Disables the transmission of routing updates on an interface
Preventing the Advertisement of Routes to Networks with No Associated Zones
NBP uses ZIP to determine which networks belong to which zones The Cisco lOS software uses ZIP to maintain table of the AppleTalk internetwork that maps network numbers to zone names
By default the software does not advertise routes to networks that have no associated zones and
therefore prevents the occurrence of ZIP protocol storms which can arise when corrupt routes are
propagated and routers broadcast ZIP requests to determine the network-zone associations By not
routes to networks that do have advertising not associated zones you limit any ZIP protocol storms to
single network rather than allowing them to spread to the entire internetwork
To allow the advertisement of routes to networks that have no associated zones use the following
command in global configuration mode
Command Purpose
Router config no appletalk require-route-zones Allows the advertisement of routes to networks that have no associated zones
The lists be user zone can configured to vary from interface to interface However this practice is
discouraged because AppleTalk users expect to have the same user zone lists at any end node in the internetwork This kind of filtering does not prevent explicit access via programmatic methods but should be considered user optimization whereby unused zones are suppressed Use other forms of
AppleTalk access control lists to actually secure zone or network
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 40 guring AppleTalk AppleTalk Configuration Task List
Setting Routing Table Update Timers
Cisco lOS software sends routing table updates at regular intervals In rare instances you might want to
change this interval such as when router is busy and cannot send routing updates every 10 seconds or
when slower devices are incapable of processing received routing updates in large network If you do
change the routing update interval you must do so for all devices on the network
Caution Modifying the routing timers can degrade or destroy AppleTalk network connectivity for their Many other AppleTalk router vendors provide no facility modifying routing do arrive these timers so adjusting Cisco AppleTalk timers such that routing updates not at
other routers within the normal interval might result in loss of information about the
network or loss of connectivity
To change the routing table update timers use the following command in global configuration mode
Command Purpose
Router config appletalk timers update-interval Changes the routing update timers valid-interval invalid-interval
Setting the Routing Update Interval Timer
is reduce the of The interval between subsequent routing updates randomized to probability
the link This randomization is synchronization with the routing updates from other routers on same each interface achieved by maintaining separate transmission interval timer for advertising
the in To set the interval timer on router between subsequent routing updates use following command
global configuration mode
Command Purpose
Routerconfig appletalk rtmp jitter percent Sets the interval timer between subsequent routing updates
Assigning Proxy Network Numbers
nonextended It is possible to have an AppleTalk internetwork in which some routers support only enable between these AppleTalk and others support only extended AppleTalk You can interoperability
for each in which there is two types of AppleTalk networks by assigning proxy network number zone
device that supports only nonextended AppleTalk mode To assign proxy network numbers use the following command in global configuration
Command Purpose
Router network number for each in which there is config appletalk proxy-nbp Assigns proxy zone network-number zone-name device that supports only nonextended AppleTalk
Number For an example of how to configure proxy network numbers see the Proxy Network Example
section at the end of this chapter
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 41 Configuring AppleTalk
AppleTalk Configuration Task List
Caution Do not also assign the proxy network number to router or to physical network
You must network number for assign one proxy each zone You can optionally define additional proxies with different network numbers to provide redundancy Each proxy network number generates one or
more for each forward it packets request receives but discards all other packets sent to it Thus defining
redundant proxy network numbers increases the NBP traffic linearly
Enabling Round-Robin Load Sharing
In order to increase throughput in the network router can use multiple equal-cost paths to reach
destination By default the router picks one best path and sends all traffic using this path You can
configure the router to remember two or more paths that have equal costs and to balance the traffic load
across all of the available paths Note that when paths have differing costs the Cisco lOS software chooses lower-cost routes in preference to higher-cost routes
The software then distributes output on packet-by-packet basis in round-robin fashion That is the first
packet is sent along the first path the second packet along the second path and so on When the final
path is reached the next packet is sent to the first path the next to the second path and so on This
round-robin scheme is used regardless of whether fast switching is enabled
Limiting the number of can save on routers with limited with equal-cost paths memory memory or very in networks large configurations Additionally with large number of multiple paths and systems with
limited to cache ability out-of-sequence packets performance might suffer when traffic is split between many paths
To set the maximum number of the paths use following command in global configuration mode
Command Purpose
Router conE ig appletalk maxinrnm-paths paths Sets the maximum number of equal-cost paths to destination
Disabling Checksum Generation and Verification
the Cisco lOS software By default generates and verifies checksums for all AppleTalk packets except routed packets You might want to disable checksum generation and verification if you have older devices such as LaserWriter printers that cannot receive packets with checksums
To disable checksum and generation verification use the following command in global configuration mode
Command Purpose
Router config no appletalk checksum Disables the generation and verification of checksums for all
AppleTalk packets
Controlling the AppleTalk ARP Table
To control the AppleTalk ARP table you can use the following tasks
Set the timeout for ARP table entries
the time Specify interval between the retransmission of AIRP packets
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 42 figurin AppleTalk AppleTalk Configuration Task LisiU
retransmissions Specify the number of ARP
Disable the gleaning of ARP information from incoming packets
By default entries in the AppleTalk ARP table are removed from the table if no update has been received in the last hours To change the ARP timeout interval use the following command in interface
configuration mode
Command Purpose
Router conf igif appletalk arp-timeout interval Sets the timeout for ARP table entries
AppleTalk ARP associates AppleTalk network addresses with media data link addresses When
address is to AppleTalk must send packet to another network node the protocol passed AppleTalk ARP
which undertakes series of address negotiations to associate the protocol address with the media address
and overloaded file If your AppleTalk network has devices that respond slowly such as printers servers in order allow the from these you can lengthen the interval between AppleTalk ARP packets to responses both of the devices to be received To lengthen the interval between AppleTalk ARP packets use one or
following commands in global configuration mode
Command Purpose
Router config appletalk arp Specifies the time interval between retransmission of ARP packets request nterval interval
before Router config appletalk arp Specifies the number of retransmissions that will occur request retransmit-count number address abandoning address negotiations and using the selected
The Cisco lOS software automatically derives ARP table entries from incoming packets This process is table To disable the referred to as gleaning Gleaning speeds up the process of populating the ARP
gleaning of ARP table entries use the following command in interface configuration mode
Command Purpose
Router config-if no appletalk glean-packets Disables the gleaning of ARP information from incoming packets
Controlling the Delay Between ZIP Queries
seconds and the information received By default the Cisco lOS software sends ZIP queries every 10 uses the command in to update its zone table To change the ZIP query interval use following global
configuration mode
Command Purpose
Routerconfig appletalk zip-query-interval Sets the ZIP query interval interval
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 43 Configuring AppleTaJ
AppleTalk Configuration Task List
Logging Significant Network Events
You information about can log significant network events performed on the router including routing
changes zone creation port status and address To log information about significant network events
use the following conunand in global configuration mode
Command Purpose
Routerconfig appletalk event-logging Logs significant events
Disabling Fast Switching
Fast switching allows higher throughput by switching packet using cache created by previous packets
Fast switching is enabled by default on all interfaces that support fast switching
Packet transfer performance is generally better when fast switching is enabled However you may want
to disable fast in order switching to save memory space on interface cards and to help avoid congestion
when high-bandwidth interfaces are writing large amounts of information to low-bandwidth interfaces
To disable AppleTalk fast switching on an interface use the following command in interface
configuration mode
Command Purpose
Router config-if no appletalk route-cache Disables AppleTalk fast switching
Configuring AppOeTalk Enhanced IGRP
Enhanced IGRP is an enhanced version of the IGRP developed by Cisco Enhanced IGRP uses the same distance vector algorithm and distance information as IGRP However the convergence properties and the operating efficiency of Enhanced IGRP have improved significantly over IGRP
Because Enhanced IGRP supports AppleTalk Internetwork Packet Exchange IPX and IP you can use
one routing protocol for multiprotocol network environments minimizing the size of the routing tables
and the amount of routing information
Convergence Technology
The convergence technology is based on research conducted at SRI International and employs an referred the algorithm to as Diffusing Update Algorithm DUAL This algorithm guarantees loop-free instant operation at every throughout route computation and allows all routers involved in topology the change to synchronize at same time Devices that are not affected by topology changes are not involved in recomputations The convergence time with DUAL rivals that of any other existing routing protocol
Cisco lOS and Novell IPX Guide ______AppleTalk Configuration P2C 44 Configuring AppleTalk
AppleTalk Configuration Task List
Enhanced IGRP Features
Enhanced IGRP offers the following features
Fast convergenceThe DUAL algorithm allows routing information to converge extremely quickly
Partial IGRP updatesEnhanced sends incremental updates when the state of destination changes
instead of sending the entire contents of the routing table This feature minimizes the bandwidth
required for Enhanced IGRP packets
mechanismThis Neighbor discovery is simple hello mechanism used to learn about neighboring
routers It is protocol-independent
ScalingEnhanced IGRP scales to large networks
Enhanced IGRP Components
Enhanced IGRP has the following four basic components
Neighbor Discovery/Recovery
Reliable Transport Protocol
DUAL Finite-State Machine
Protocol-Dependent Modules
Neighbor Discovery/Recovery
Neighbor discovery/recovery is the process that routers use to dynamically learn of other routers on their
directly attached networks Routers must also discover when their neighbors become unreachable or
inoperative Routers achieve neighbor discovery/recovery with low overhead by periodically sending
small hello packets As long as hello packets are received device can determine that neighbor is
functioning Once this status is determined the neighboring routers can exchange routing information
Reliable Transport Protocol
The reliable transport protocol is responsible for guaranteed ordered delivery of Enhanced IGRP
packets to all neighbors It supports intermixed transmission of multicast and unicast packets Some
Enhanced IGRP packets must be sent reliably and others need not be For efficiency reliability is
provided only when necessary For example on multiaccess network that has multicast capabilities
such as Ethernet it is not necessary to send hellos reliably to all neighbors individually Therefore
Enhanced IGRP sends single multicast hello with an indication in the packet informing the receivers
that the packet need not be acknowledged Other types of packets such as updates require
which is indicated in the The send acknowledgment packet reliable transport has provision to
multicast packets quickly when there are unacknowledged packets pending Doing so helps ensure that time remains low in the of convergence presence varying speed links
DUAL Finite-State Machine
The DUAL finite-state machine embodies the decision for all It tracks all process route computations
routes advertised by all neighbors DUAL uses the distance information as routing metric to select
efficient loop-free paths DUAL selects routes to be inserted into routing table based on feasible
successors successor is neighboring router used for packet forwarding that has least-cost path to
destination that is guaranteed not to be part of routing loop When there are no feasible successors but there are neighbors advertising the destination recomputation must occur This is the process
whereby new successor is determined The amount of time it takes to recompute the route affects the
Cisco lOS and Novell IPX Guide ______AppleTalk Configuration ______P2C-45 Configuring App leTaLJ AppleTalk Configuration Task List
convergence time Recomputation is processor-intensive It is advantageous to avoid recomputation if it
is not necessary When topology change occurs DUAL will test for feasible successors If feasible will them in order avoid successors exist DUAL use to unnecessary recomputation
Protocol-Dependent Modules
The protocol-dependent modules are responsible for network layer protocol-specific tasks They are also
responsible for parsing Enhanced IGRP packets and informing DUAL of the new information received
Enhanced IGRP asks DUAL to make routing decisions but the results are stored in the AppleTalk
routing table Also Enhanced IGRP is responsible for redistributing routes learned by other AppleTalk
routing protocols
The Cisco mpIementation of Enhanced GRP
AppleTalk Enhanced IGRP provides the following features
Automatic redistributionBy default AppleTalk RTMP routes are automatically redistributed into
Enhanced IGRP and AppleTalk Enhanced IGRP routes are automatically redistributed into RTMP
If desired you can turn off redistribution
Interface-specific decisions about routing protocolsYou can configure AppleTalk interfaces to use
either RTMP Enhanced IGRP or both routing protocols If two neighboring routers are configured
to use both RTMP and Enhanced IGRP the Enhanced IGRP routing information supersedes the
RTMP information However both devices continue to send RTMP routing updates
Because Enhanced IGRP supersedes RTMP you can control the excessive bandwidth usage of
RTMP on WAN links Because WAN link is point-to-point link there are no other devices on the
link and therefore no need to run RTMP to perform end-node router discovery Using Enhanced
IGRP on WAN links allows you to save bandwidth and in the case of packet-switched data networks PSDNs traffic charges
Enhanced GRP Configuration Task List
To configure AppleTalk Enhanced IGRP perform the tasks in the following sections At minimum you
must create the AppleTalk Enhanced IORP routing process Configuring Miscellaneous Parameters is
optional
Enabling AppleTalk Enhanced IGRP Required
Configuring Miscellaneous Parameters Optional
Enabling AppleTalk Enhanced IGRP
To create an AppleTalk Enhanced IGRP routing process use the following commands beginning in
global configuration mode
Command Purpose
Router rouler-number Step config appletalk routing eigrp Enables an AppleTalk Enhanced IGRP routing
process in global configuration mode
Step Router config-if appletalk protocol eigrp Enables Enhanced IGRP on an interface in
interface configuration mode
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 46 figuring AppleTalk AppleTalk Configuration Task Lisia
For an example of how to enable AppleTalk Enhanced IGRP see the AppleTalk Access List Examples
section at the end of this chapter
To associate multiple networks with an AppleTalk Enhanced IGRP routing process you can repeat these commands
Caution When you disable Enhanced IGRP routing with the no appletalk routing eigrp command all interfaces enabled for only Enhanced IGRP and not also RTMP lose their AppleTalk instead configuration If you want to disable Enhanced IGRP and use RTMP on specific
interfaces first enable RTMP on each interface using the appletalk protocol rtmp the interface configuration command Then disable Enhanced IGRP routing using no lose appletalk routing eigrp command This process ensures that you do not AppleTalk
configurations on interfaces for which you want to use RTMP
Configuring Miscellaneous Parameters
Enhanced IGRP more of the tasks in To configure miscellaneous AppleTalk parameters perform one or
the following sections
Disabling Redistribution of Routing Information Optional
Hello Packets and the Hold Time Adjusting the Interval Between Optional
Disabling Split Horizon Optional
Adjusting the Active State Time for Enhanced IGRP Routes Optional
Logging Enhanced IGRP Neighbor Adjacency Changes Optional
Enhanced IGRP Configuring the Percentage of Link Bandwidth Used by Optional
Disabling Redistribution of Routing Information
Enhanced By default the Cisco lOS software redistributes AppleTalk RTMP routes into AppleTalk Enhanced IGRP IGRP and vice versa Internal Enhanced IGRP routes are always preferred over external
routes which means that if there are two Enhanced IGRP paths to destination the path that originated IGRP within the Enhanced IGRP autonomous system always will be preferred over the Enhanced path
that originated from outside the autonomous system regardless of the metric Redistributed RTMP
routes are always advertised in Enhanced IGRP as external
To disable route redistribution use the following command in global configuration mode
Command Purpose
Router config no appletalk route-rediatribution Disables redistribution of RTMP routes into Enhanced IGRP and
Enhanced IGRP routes into RTMP
Adjusting the Interval Between Hello Packets and the Hold Time
You can adjust the interval between hello packets and the hold time
their Routers periodically send hello packets to each other to dynamically learn of other devices on their directly attached networks This information is used to discover their neighbors and to learn when
neighbors become unreachable or inoperative
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 47 Configuring App IeTa_J AppleTalk Configuration Task List
hello seconds The is By default packets are sent every exception on low-speed nonbroadcast multiaccess NBMA media where the default hello interval is 60 seconds Low speed is considered to
be rate of Ti or slower as specified with the bandwidth interface configuration command The default
hello interval remains seconds for high-speed NBMA networks
Note For the purposes of Enhanced IGRP Frame Relay and Switched Multimegabit Data
Services SMDS networks may or may not be considered to be NBMA These networks
are considered NBMA if the interface has not been configured to use physical multicasting
otherwise they are considered not to be NBMA
You can configure the hold time in seconds on specified interface for the AppleTalk Enhanced IGRP
routing process designated by the autonomous system number The hold time is advertised in hello
packets and indicates to neighbors the length of time they should consider the sender valid The default
hold time is three times the hello interval or 15 seconds
On very congested and large networks the default hold time might not be sufficient time for all routers
to receive hello from their this packets neighbors In case you may want to increase the hold time
Note Do not adjust the hold time without consulting with Cisco technical support
To change the interval between hello packets and the hold time use the following command in interface
configuration mode
Command Purpose
Router config-if appletalk eigrp-timers Sets the interval between hello packets and the hold time hello-interval hold-time
Disabling Split Horizon
horizon controls the of Enhanced Split sending AppleTalk IGRP update and query packets When split
horizon is enabled on an interface these packets are not sent to destinations for which this interface is
the next hop therefore reducing the possibility of routing loops
By default split horizon is enabled on all interfaces
Split horizon prevents route information from being advertised by router out the interface that the information This behavior originated usually optimizes communication among multiple routers particularly when links are broken However with nonbroadcast networks such as Frame Relay and SMDS situations can arise for which this behavior is less than ideal For these situations you may wish
to disable split horizon
To disable split horizon use the following command in interface configuration mode
Command Purpose
Router config-if no appletalk eigrp-sp.ithorizon Disables split horizon
Adjusting the Active State Time for Enhanced IGRP Routes
By default Enhanced IGRP routes remain active for minute When route reaches this active state time limit of the Cisco lOS software and minute logs an error removes the route from the routing table
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C-48 Configuring AppleTalk
AppleTalk Configuration Task List
You can adjust this active state time limit To specify the length of time that Enhanced IGRP routes can
remain active use the following command in global configuration mode
Command Purpose
RouterConfig appletalk eigrp active-time Adjusts the active state time limit minutes disabled
Logging Enhanced IGRP Neighbor Adjacency Changes
An adjacency is the next hop router You can enable the logging of neighbor adjacency changes to
monitor the stability of the routing system and to help you detect problems By default adjacency changes are not logged
To enable logging of Enhanced IGRP neighbor adjacency changes use the following command in global
configuration mode
Command Purpose
Router config appletalk eigrp log-neighbor-changes Enables logging of Enhanced IGRP neighbor adjacency changes
Configuring the Percentage of Link Bandwidth Used by Enhanced IGRP
By default Enhanced IGRP packets consume maximum of 50 percent of the link bandwidth as
configured with the bandwidth interface subcommand If different value is desired use the appletalk eigrp-bandwidth-percentage command This command may be useful if different level of link
utilization is required or if the configured bandwidth does not match the actual link bandwidth it may
have been configured to influence route metric calculations
the To configure the percentage of bandwidth that may be used by Enhanced IGRP on an interface use
following command in interface configuration mode
Command Purpose
Router that be used config-if appletalk eigrp-bandwidth-percentage Configures the percentage of bandwidth may router-number percent by Enhanced IGRP on an interface
For an example of how to configure the percentage of Enhanced IGRP bandwidth see the AppleTalk
Enhanced IGRP Bandwidth Configuration Example section at the end of this chapter
Configuring AppleTalk Interenterprise Routing
domains AppleTalk interenterprise routing provides support for AppleTalk internets or AppleTalk domain router interenterprise routing allows two or more AppleTalk domains to be connected through
which can also be Cisco access server AppleTalk interenterprise routing allows the resolution of and reduction conflicting AppleTalk network numbers or cable ranges from different domains hop-count between domains
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C-49 Configuring AppIeTalkJ AppleTalk Configuration Task List
Understanding AppleTalk Domains
domain is of An AppleTalk group AppleTalk networks or cable ranges that are connected and that have the following characteristics
Each network number or cable range within domain is unique within that domain
Each domain is separated from another domain by domain router
There is no physical or virtual connection between the two AppleTalk domains other than through domain router
Understanding Domain Routers
The domain router horizon uses split across the entire domain not just across an interface which means
that domain routers do not propagate routes learned from an interface in one domain back into that
domain Rather domain routers propagate routes only to other domains
AppleTalk Interenterprise Routing Features
AppleTalk interenterprise routing provides the following features
Network remappingAllows you to remap remote network numbers to resolve numbering conflicts with network numbers on the local network segment
Hop-count reductionAllows the creation of internetworks larger When you enable hop-count the in reduction hop count packet is set to as it passes from one domain to another therefore
to circumvent the allowing you 15-hop limit imposed by DDP and RTMP when forwarding packets
detectionAvoids Loop having multiple routing table entries to the same remote network segment If the domain domain router detects loop it displays an error message on the domain router and
shuts off domains The of that there is presence loop implies connection between two separate domains that was not learned through any of the interfaces of the domain router
Fast been switchingHas implemented for networks that have been remapped or on which hop-count reduction has been configured
Redundant Paths Between Domains
Note that one domain router only can separate two domains That is you cannot have two or more domain routers to create redundant between domains You paths can however establish redundant paths between domains them by connecting through more than one interface on the domain router that
them Figure illustrates this In this separates configuration figure one domain router separates domains and of the Two interfaces of the router are in Domain Ethernet interfaces and and three in Domain are Ethernet interfaces and thus providing redundant connections between
the domains illustrates Figure an improper configuration This configuration will create adverse
effects because domains and are connected by two domain routers
Figure Allowed Configuration of Domain Router Connecting Two Domains
Domain
router
E3 EO Domain El Domain E4 so
Cisco lOS AppleTalk and Novell IPX Configuration_Guide P2C 50 1figuring AppleTalk
AppleTalk Configuration Task List
Figure Improper Configuration of Domain Routers Connecting Two Domains
Domain
router
Domain Domain Domain router
Currently you can configure AppleTalk interenterprise routing only on routers that run RTMP or Enhanced IGRP
AppIeTak Interenterprise Routing Task List
To configure AppleTalk interenterprise routing perform the tasks described in the following sections
At minimumyou must enable AppleTalk interenterprise routing The remaining tasks are optional
Enabling AppleTalk Interenterprise Routing Required
Remapping Network Numbers Optional
Controlling Hop Count Optional
After you assign AppleTalk interenterprise routing remapping hop-count reduction and loop-detection
features to an AppleTalk domain you can attribute those characteristics to tunnel interface configured
for AURI by assigning the AppleTalk domain group number to the AURP tunnel interface
Enabling AppleTalk Interenterprise Routing
To enable AppleTalk interenterprise routing perform the following tasks
Enable AppleTalk interenterprise routing on the router Required
Enable AppleTalk interenterprise routing on an interface Required
To enable AppleTalk interenterprise routing use the following command in global configuration mode
Command Purpose
Router config appletalk domain domain-number name domain-name Creates domain and assigns it name and number
To enable AppleTalk interenterprise routing on an interface use the following command in interface
configuration mode
Command Purpose
Router config-if domain-number appletalk domain-group Assigns predefined domain number to an interface
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 51 Configuring AppleTj AppleTalk Configuration Task List
For an example of how to configure AppleTalk interenterprise routing see the AppleTalk
Interenterprise Routing Example section at the end of this chapter
Remapping Network Numbers
When two AppleTalk networks are connected conflict can arise between network numbers or between
cable ranges on one network and those on the other You can avoid conflicts by remapping the network
numbers or cable ranges of the remote network
Each domain can have two mapping ranges to which to remap all incoming or outgoing network numbers or cable ranges
To remap the network numbers or cable ranges on inbound packets use the following command in global
configuration mode
Command Purpose
Router config domain domain-number in appletalk remap-range Remaps packets inbound to the domain cable-range
To the network numbers remap or cable ranges on outbound packets use the following command in
global configuration mode
Command Purpose
Router config domain domain-number appletalk remap-range out Remaps packets outbound from the domain cable-range
Controlling Hop Count
When you join AppleTalk network segments to create domains the distance across the combined
internetworks is to exceed 15 likely hops which is the maximum number of hops supported by RTMP You can extend the network topology by configuring the Cisco lOS software to reduce the hop-count
value of packets that traverse it
the value allows Reducing hop-count an AppleTalk router to control the hop-count field in DDP packets so as to ensure that the packet reaches its final AppleTalk destination Hop-count reduction allows the
router to the limitation 16 bypass of hops before aging out packets This feature is supported only on
access servers and routers configured for AppleTalk Enhanced IGRP
To enable hop-count reduction use the following command in global configuration mode
Command Purpose
Router config domain domain-number appletalk hop-reduction Enables hop-count reduction
Configuring AppeTalk over WANs
You can configure AppleTalk over dial-on-demand routing DDR Frame Relay SMDS and X.25 networks For more information about dial-on-demand routing DDR refer to the Cisco 105 Dial Technologies Configuration Guide For more information about Frame Relay SMDS and X.25 refer to
the Cisco lOS Wide-Area Networking Configuration Guide
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 52 onfiguring AppleTalk AppleTalk Configuration Task List
AppleTalk over DDR
the To use AppleTalk over DDR you must define AppleTalk static routes You can configure following
two types of static routes
Static routesThese routes have absolute precedence that is they always override any dynamically learned routes
Floating static routesThese routes can be overridden by dynamically learned routes
Be careful when assigning static routes When links associated with these static routes are lost traffic be nonexistent even an may stop being forwarded or traffic may forwarded to destination though
alternative path might be available
be Note When you configure AppleTalk over DDR the zone name assigned to the interface must
unique It cannot be the same as zone name assigned to static route If the zone names
are not unique the sequence of AppleTalk initialization and dialer operation will cause the DDR interface to go up and down
Configuring Static Routes
To add static route for an extended or nonextended AppleTalk network use one of the following
commands in global configuration mode
Command Purpose
Router config appletalk static cable-range Defines static route on an extended AppleTalk network cable-range to network.node zone zone-name
Router config appletalk static network Defines static route on nonextended AppleTalk network network-number to network.node zone zone-name
Configuring Floating Static Routes
You can use floating static route to create path of last resort that is used only when no dynamic routing
information is available To avoid the possibility of routing loop occurring floating static routes by
default are not redistributed into other dynamic protocols
use one of the To add floating static route for an extended or nonextended AppleTalk network
following commands in global configuration mode
Command Purpose
Router config appletalk static cable-range Defines floating static route on an extended AppleTalk cable-range to network.node floating zone zone-name network
Router config appletalk static network Defines floating static route on nonextended AppleTalk network-number to network.node floating zone network zone -name
For an example of how to configure AppleTalk over DDR see the AppleTalk over DDR Example
section at the end of this chapter
Guide Cisco lOS AppleTalk and Novell IPX Configuration P2C 53 Configuring AppleTalk AppleTalk Configuration Task List
AppUelalk over X25
For X.25 you can configure only nonextended AppleTalk network Logically this network is the same as LocalTalk network because both are always nonextended networks All AppleTalk nodes within an
X.25 network must be configured with the same AppleTalk network number Also the network numbers
and zone names on both sides of the serial link must be the same When mapping the AppleTalk address
to the 121 address of the router with the x25 map command include the keyword broadcast to simulate the broadcast This AppleTalk capability keyword is necessary because X.25 does not support but does The broadcast broadcasts AppleTalk simulation operates as follows If the broadcast flag is
set whenever broadcast packet is sent each X.121 address specified will receive it
Configuring AppleTalk Between LANs
For information more on Ethernet-emulated LANs and routing AppleTalk between them refer to the Emulation Configuring LAN chapter of the Cisco 105 Switching Services Configuration Guide
Configuring AppleTalk Between VLANs
For information more on VLANs and routing AppleTalk between them over Inter-Switch Link ISL or IEEE 802.10 refer to the Configuring Routing Between VLANs with ISL Encapsulation and
Configuring Routing Between VLANs with IEEE 802.10 Encapsulation chapters of the Cisco 105
Switching Services Configuration Guide
Monitoring and Maintaining the AppleTalk Network
The Cisco lOS software provides several commands that you can use to monitor and maintain an network In AppleTalk addition you can use network monitoring packages such as lnterPoll by Apple
Computer to verify that router is configured and operating properly Use the commands described in
this section to monitor an AppleTalk network using both Cisco lOS software commands and network monitoring packages
Monitoring and Maintaining the AppeTak Network Using Cisco lOS Software Commands
monitor To and maintain the AppleTalk network use one or more of the following commands in EXEC
configuration mode
Command Purpose
Router config appletalk pre-fdditalk Enables recognition of pre-FDDITa1k packets Router clear appletalk arp Deletes entries from the AppleTalk ARP AARP table Router clear appletalk neighbor Deletes entries from the neighbor table all
Router clear route network appletalk Deletes entries from the routing table
Router clear traffic appletalk Resets AppleTalk traffic counters
Router clear mcache smxp Clears the fast-switching entries in the SMRP fast-
switching cache table
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C-54 AppleTalk
AppleTalk Configuration Task List
Command Purpose
Router ping appletalk network.node Diagnoses basic AppleTalk network connectivity user-level command
Router ping Diagnoses basic AppleTalk network connectivity
privileged command
Router show appletalk access-lists Displays the AppleTalk access lists currently defined
Router show appletalk adjacent-routes Displays the routes to networks that are directly connected
or that are one hop away
Router show appletalk arp Lists the entries in the AppleTalk ARP table
Router show appletalk aurp events Displays pending events in the AppleTalk AURP
update-events queue
Router4 show appletalk aurp topology Displays entries in the AURP private path database
Router show appletalk cache Displays the contents of the AppleTalk fast-switching cache
Router show appletalk domain Displays domain-related information
Router show appletalk eigrp neighbors type number Lists the neighbors discovered by AppleTalk Enhanced IGRP
for Router show appletalk eigrp interfaces number Displays information about interfaces configured Enhanced IGRP
Router show appletalk eigrp topology Displays the contents of the AppleTalk Enhanced IGRP active zero-successors topology table
internetwork and Router show appletalk globals Displays information about AppleTalk
other parameters of the router
Router show appletalk interface number Displays AppleTalk-related interface settings
clients Router show appletalk macip-clients Displays the status of all known MacIP
Router show appletalk macip-servers Displays the status of MacIP servers of device
Router show appletalk nacip-traffic Displays statistics about MacIP traffic
offered routers Router show appletalk name-cache Displays list of NBP services by nearby
and by other devices that support NBP
table Router show appletalk nbp Displays the contents of the NBP name registration
Router show appletalk neighbors Displays information about the AppleTalk routers directly
connected to any network to which the router is directly connected
Router show appletalk remap domain-number Displays domain remapping information out from domain-network
table Router show appletalk route type number Displays the contents of the AppleTalk routing
show in all sockets in an Router appletalk sockets Displays the process-level operations interface
Router show appletalk static Displays the defined static routes
show Router appletalk traffic Displays the statistics about AppleTalk protocol traffic
including MacIP traffic
Router show appletalk zone Displays the contents of the zone information table
table Router show sxurp forward Displays the SMRP forwarding
Guide CiscolOS AppleTalk and Novell IPX Configuration P2C 55 Configuring AppleTalk AppleTalk Configuration Task List
Command Purpose
Router show smrp globals Displays global information about SMRP
Router show smrp group Displays the SMRP group table
Router show ucache sxnrp Displays the SMRP fast-switching cache table
Router show amrp neighbor Displays the SMRP neighbor table
Router show smrp port number Displays the SMRP port table
Router show route sinrp Displays the SMRP routing table type number
Router show traffic sznrp group neighbor Displays all entries or specific entries in the SMRP traffic port route transaction table
Router test appletalk Enters test mode to test NBP protocols
Monitoring the AppleTalk Network Using Network Monitoring Packages
The Cisco lOS software supports network monitoring packages such as InterPoll by Apple Computer
which are tools that use the AppleTalk responder and listener for verifying the configuration and of router The software operation answers AppleTalk responder request packets These request packets
are received by the listener which is installed on the AppleTalk interface name registration socket The include the responder request packets bootstrap firmware version string followed by the operating
software version string These strings are displayed in the Macintosh system version and the Macintosh
printer driver version fields respectively and in applications such as InterPoll by Apple Computet The
response packet contains strings similar to those displayed by the show version EXEC command
The Cisco lOS software returns the following information in response to responder request packets
System bootstrap version ROM version
Software version
AppleTalk version always version 56 which is the first Apple Macintosh version that contained AppleTalk Phase support
version AppleTalk responder always version 100 which indicates support of Version 1.0 responder packets
AppleShare status reported as not installed
illustrates Figure typical output display for Inter.Poll that lists this information
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 56 Jguring AppleTalk AppleTalk Configuration Examples
Figure InterPoII Output
Net 4042 Node evtce ______routerl .Ethernet3-ciscoRouter-Twilight Zone Stop__1 Packets 20 Using ______Echo Pkts Donej Interval 2.5 Iseos
Printer Status Packets Timeout 1.5 Secs System Info Packets
Rcvd Lost
Packets Sent Left 16 Total
Current Average Minimum Maximum
Hops Away 3.00
Delay seca 0.02 0.02 0.02 0.02
System Bootstrap Version 4.45.0 01956-1991 b.. St tus OS Software 0S3 VersIon 9.2113110 Development Software 01991
Responder NIT Version 100 AppleTalk Driver VersIon 59 AppleShara not Inotstled
AppleTalk Configuration Examples
in the sections To help you configure AppleTalk routing use the configuration examples following
Extended AppleTalk Network Example
Nonextended AppleTalk Network Example
Nonextended Network in Discovery Mode Example
AppleTalk Enhanced IGRP Example
Transition Mode Example
AppleTalk Access List Examples
Hiding and Sharing Resources with Access List Examples
GZL and ZIP Reply Filter Examples
AppleTalk Interenterprise Routing over AURP Example
SNMP Example
MacIP Examples
IPTalk Example
AppleTalk Control Protocol Example
Proxy Network Number Example
AppleTalk Enhanced IGRP Bandwidth Configuration Example
AppleTalk Interenterprise Routing Example
AppleTalk over DDR Example
AppleTalk Control Protocol for PPP Example
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 57 Configuring AppleTalk AppleTalk Configuration Examples
Extended AppleTalk Network Example
The shows following example how to configure an extended AppleTalk network It defines the zones and Personnel The Accounting cable range of allows compatibility with nonextended AppleTalk networks
appletalk routing interface ethernet
appletalk cable-range 69-69 69.128 appletalk zone Accounting appletalk zone Personnel
Nonextended AppleTalk Network Example
The shows how to following example configure nonextended AppleTalk network that allows routing between two Ethernet networks Ethernet interface is connected to Network at node 128 and Ethernet
interface is connected to Network at node 154 Network is in the Twilight zone and Network is in the No Parking zone See Figure
Figure Nonextended AppleTalk Routing Between Two Ethernet Networks
Twilight Zone
1.128 2.154
Co Network Network2
appletalk routing
interface ethernet
appletalk address 1.128 appletalk zone Twilight
interface ethernet appletalk address 2.154 appletalk zone No Parking
Nonextended Network in Discovery Mode Example
The shows how following example to configure nonextended network in discovery mode There are seed routers on both networks to provide the zone and network number information to the interfaces when they start Router supplies configuration information for Ethernet interface and Router information for supplies configuration Ethernet interface See Figure
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 58 onfiguring AppleTalk AppleTalk Configuration Exampii
Figure Routing in Discovery Mode
Router
Router
Router
The following example shows how to configure this nonextended network in discovery mode
appletalk routing
interface ethernet appletalk address 0.0
interface ethernet appletalk address 0.0
AppleTalk Enhanced IGRP Example
The following example shows how to configure AppleTalk Enhanced IGRP In this example Ethernet
interface is configured for both Enhanced IGRP and RTMP routing and serial interface is configured
for only AppleTalk Enhanced IGRP routing
appletalk routing eigrp appletalk route-redistribution
interface ethernet appletalk cable-range 10-10 10.51 appletalk zone Ethernet appletalk protocol eigrp
interface serial appletalk cable-range 111-111 111.51 appletalk zone Serial appletalk protocol eigrp no appletalk protocol rtmp
AppleTalk Access List Examples
Our implementation of AppleTalk provides several methods using access lists to control access to in AppleTalk networks The following sections show these methods and different approaches applying
access lists
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 59 Configuring AppleallJ
AppleTalk Configuration Examples
Defining an Access List to Filter Data Packets Example
The following commands create access list 601
Permit packets to be routed from network 55 access-list 601 permit network 55
Permit packets to be routed from network 500 access-list 601 permit network 500
Permit packets to be routed from networks 900 through 950 access-list 601 permit cable-range 900-950
Do not permit packets to be routed from networks 970 through 990 access-list 601 deny includes 970-990
Do not permit packets to be routed from networks 991 through 995 access-list 601 permit within 991-995
Deny routing to any network and cable range not specifically enumerated access-list 601 deny other-access
The following example shows how to use access list 601 to filter data packets by applying an interface for example Ethernet interface
appletalk routing interface ethernet appletalk cable-range 50-50 appletalk zone No Parking appletalk access-group 601 out
The following examples show how Ethernet interface would handle outgoing data packets
Packets sourced from cable range 5050 are permitted
Packets sourced from any network in the cable range 972980 are denied because they explicitly match the access-list deny includes 970-990 command
Defining an Access List to Filter Incoming Routing Table Updates Example
The following example shows how to create access list 602 This example shows how packets are
processed by access lists you cannot create such redundant access list
access-list 602 permit network 55 access-list 602 permit cable 55-55 access-list 602 permit includes 55-55 access-list 602 permit within 55-55
The shows how following example to use this access list to filter routing table updates received on Ethernet interface
appletalk routing interface ethernet appletalk cable-range 55-55 appletalk zone No Parking appletalk distribute-list 602 in
The following tables show the process for accepting or rejecting routing update information If the
outcome of test is true the condition passes the access list specification and the distribute-list
command specification is then applied
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 60 Jguing AppleTalk AppleTalk Configuration Examples
follows Routing updates that contain network 55 would be processed as
Access List Command Outcome of Test
access-list 602 permit network 55 True
access-list 602 permit cable range 5555 False
access-list 602 permit includes 5555 True
access-list 602 permit within 5555 True
follows Routing updates that contain cable range 5555 would be processed as
Access List Command Outcome of Test
False access-list 602 permit network 55
access-list 602 permit cable range 5555 True
access-list 602 permit includes 5555 True
access-list 602 permit within 5555 True
follows Routing updates that contain cable range 5556 would be processed as
Access List Command Outcome of Test
access-list 602 permit network 55 False
access-list 602 permit cable-range 5555 False
access-list 602 permit includes 5555 True
access-list 602 permit within 5555 False
Comparison of Alternative Segmentation Solutions
the method to With the flexibility allowed by our access list implementation determining optimal The scenario and segment an AppleTalk environment using access control lists can be unclear following out the inherent configuration examples illustrate two solutions to particular problem and point
advantages of using AppleTalk-style access lists
direct to several Consider situation in which company wants to permit customers to have access is be all devices in the zones named MIS and corporate file servers Access to permitted to Corporate contain sensitive but access is restricted to the Engineering zone because the file servers in these zones these information The solution is to create the appropriate access lists to enforce access policies
Guide Cisco lOS AppleTalk and Novell IPX Configuration P2C 61 Configuring App leTaIk_J AppleTalk Configuration Examples
The AppleTalk internetwork of the company consists of the following networks and zones
Zone Network Number or Cable Range
Engineering 6969
41604160
15
MIS 666777
Corporate 7070 55 51004 42624262
World 8888
90009999 multiple networks exist in this range
The router named Gatekeeper is placed between the World zone and the various company-specific zones
An arbitrary number of routers can be on either side of Gatekeeper An Ethernet backbone exists on each
side of Gatekeeper connecting these other routers to Gatekeeper On the router Gatekeeper Ethernet interface connects to the World backbone and Ethernet interface connects to the Corporate backbone
For the purposes of this configuration assume Gatekeeper is the only router that needs any access list
configuration There are two solutions depending on the level of security desired
The following example shows minimal configuration in which the Engineering zone is secured but
all other zones are publicly accessible
appletalk routing access-list 603 deny zone Engineering access-list 603 permit additional-zones access-list 603 permit other-access
interface ethernet appletalk network appletalk distribute-list 603 out appletalk access-group 603
The following example shows more comprehensive configuration in which the Corporate and MIS
zones are public and all other zones are secured
appletalk routing access-list 603 permit zone Corporate access-list 603 permit zone MIS access-list 603 deny additional-zones access-list 603 permit other-access
interface ethernet appletalk network appletalk distribute-list 603 out appletalk access 603
Both configurations satisfy the basic goal of isolating the Engineering servers but the second example will continue to be secure when more zones are added
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 62 gurig AppleTalk AppleTalk Configuration Examples
Defining an Access List to Filter NBP Packets Example
The following example shows how to add entries to access list number 607 to allow forwarding of NBP
packets from specific sources and deny forwarding of NBP packets from all other sources The first
command adds an entry that allows NBP packets from all printers of type LaserWriter The second
command adds an entry that allows NBP packets from all AppleTalk file servers of type AFPServer The
third command adds an entry that allows NBP packets from all applications called HotShotPaint For
example an application might have zone name of Accounting and an application might have zone
name of Engineering both having the object name of HotShotPaint NBP packets forwarded from both
applications will be allowed
The final access-list other-nbps command denies forwarding of NBP packets from all other sources
accesslist 607 permit nbp type LaserWriter access-list 607 permit nbp type AFPServer access-list 607 permit nbp object HotShotPaint access-list 607 deny other-nbps
inbound Ethernet The following example shows how to use this access list to filter NBP packets on interface
appletalk routing interface ethernet appletalk cable-range 55-55 appletalk zone No Parking appletalk access-group 607 in
The following example shows how to add entries to access list number 608 to deny forwarding of NBP
packets from two specific servers whose fully qualified NBP names are specified It permits forwarding
of NBP packets from all other sources
access-list 608 deny nbp object ServerA access-list 608 deny nbp type AFPServer access-list 608 deny nbp zone 51d3 access-list 608 deny nbp object ServerB access-list 608 deny nbp type AFPServer access-list 608 deny nbp zone B1d3 access-list 608 permit other-nbps access-list 608 permit other-access
The following example shows how to use this access list to filter NBP packets on Ethernet interface
appletalk routing interface ethernet appletalk cable-range 55-55 appletalk zope No Parking appletalk access-group 608 in S4
Note Prior to Cisco lOS Release 11.2 all NBP access lists were applied to inbound interfaces
by default When Cisco lOS Release 11.2 or later software is used the default interface
direction for all access lists including NBP access lists is outbound In order to retain the
inbound direction of access lists created with previous Cisco lOS software releases you
must specify an inbound interface for all NBP access lists using the appletalk
access-group command
Novell IPX Guide Cisco lOS AppleTalk and Configuration ______P2C 63 Configuring AppleTalk
AppleTalk Configuration Examples
The following example shows how to create an access list that denies forwarding of the following
All NBP Lookup Reply packets
NBP packets from the server named Bobs Server
Packets from all file AppleTalk servers of type AFPServer
All NBP Lookup Reply packets that contain the specified named entities belonging to the zone
twilight
access-list 600 deny nbp LkReply access-list 600 deny nbp object Bobs Server access-list 600 deny nbp type AFPServer access-list 600 deny nbp zone twilight access-list 600 permit other-nbps
There may be case where fully qualified filter for Bobs ServerAFPServer@twilight will not work for in an NBP Lookup Reply response to Lookup generated by the Chooser application This case would because the occur Lookup Request is sent as AFPServer@twilight and the Lookup Reply from Bobs Server comes back as Bobs ServerAFPServer@
The following example shows how to create an access list to filter Lookup Reply generated by Bobs Server the to request by Chooser application
access-list 609 deny nbp LkReply access-list 609 deny nbp object Bobs Server access-list 609 deny nbp type AFPServer access-list 609 permit other-nbps access-list 609 permit other-access
Configtiring Partia Zone Advertisement ExmpIe
illustrates Figure configuration in which you might want to allow partial advertisement of particular zone
Figure Example Topology of Partially Obscured Zone
Router
Router
cJ
Network 10 Network 15 Network 20 Network 30 Zone Zone Zone Zone
Assume that Router includes router-update filter applied with the appletalk distribute-list interface
configuration command on the Ethernet interface that does not accept routing table updates from
network does it 10 nor send routing table updates to that network
access-list 612 deny network 10 access-list 612 permit other-access interface ethernet appletalk distribute-list 612 out appletalk distribute-list 612 in
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 64 Configuring AppleTalk
AppleTalk Configuration Examples
For Network 30 normal default behavior would be for Network 10 and Network 20 to be eliminated
from any routing updates sent although Network 15 would be included in routing updates same zone as Network 30 Using the appletalk permit-partial-zones global configuration command has the
following effects
If the appletalk permit-partial-zones command is enabled the routing updates exclude Network 10 but include Network 15 and Network 20
If the no appletalk permit-partial-zones command is enabled the routing updates exclude both
Network 10 and Network 20 but still include Network 15 This configuration is generally
considered the preferred behavior and is the default
Table summarizes the associations between the networks shown in Figure Table details the effects
of enabling and disabling partial-zone advertisement with the appletalk permit-partial-zones global
configuration command
Table Zone and Interface Associations for Partial Zone Advertisement Example
Network Network 10 Network 15 Network 20 Network 30
Zone
Interfaces Ethernet Ethernet Ethernet Ethernet
Ethernet
Table Partial Zone Advertisement Control on Network 30
Command
Condition Network 10 Network 15 Network 20 Network 30
Enabled Not advertised Advertised on Advertised on on Network 30 Network 30 Network 30
Disabled Not advertised Advertised on Not advertised
on Network 30 Network 30 on Network 30
Transition Mode Example
When in transition mode the Cisco lOS software can route packets between extended and nonextended
AppleTalk networks that exist on the same cable
cable To configure transition mode you must have two ports connected to the same physical One port extended is configured as nonextended AppleTalk network and the other is configured as an AppleTalk networks network Both ports must have unique network numbers because they are two separate
Figure 10 shows an example of the topology of this configuration
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 65 Configuring AppleTalk
AppleTalk Configuration Examples
Figure 10 Transition Mode Topology and Configuration
El
Router
The following example shows how to configure the network shown in Figure 10 Note that networks 2-2
and 4-4 must have cable range of and single zone in their zone lists These parameters are required
to maintain compatibility with the nonextended network network
This is an extended network interface ethernet appletalk cable-range 2-2 appletalk zone No Parking
This is nonextended network interface ethernet appletalk address 3.128 appletalk zone Twilight
This is an extended network interface ethernet appletalk cable-range 4-4 appletalk zone Do Not Enter
Hiding and Sharing Resources with Access List Exampes
The following examples show how to use AppleTalk access lists to manage access to certain resources
Establishing Free-Trade Zone Example
The goal of the configuration shown in Figure 11 is to allow all users on all the networks connected to
Router and Router to be able to access the AppleShare servers AS1 and AS2 in the zone FreeAccessZone second requirement is to block cross access through this zone In other words users in the zones MIS MIS2 and LocalTalk which are connected to Ethernet interface on Router are
not allowed access to any of the resources on networks connected to Ethernet interface on Router Similarly users in the zones Engineering Test and LocalTalk which are connected to Ethernet interface
on Router interface E4 are not allowed access to any of the resources on networks connected to Ethernet interface on Router
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 66 Configuring AppleTalk
AppleTalk Configuration Examples
Figure 11 Controlling Access to Common AppleTalk Network
Access allowed into FreeAccessZone
Zone MIS2 Zone Engineering Network 4081 Network 20
Zone FreeAccessZone
Cable range 55
Router Router
E0 El Zone LocTalk Network 4083
AS1 AS2J_
Zone LocalTalk Zone Test Network Network AppleShare servers
in FreeAccessZone
____ Mcess out blocked
Note Although there are networks that share the same number on interfaces EO and E4 and there
are zones that have the same name none have the same network number and zone
specification except FreeAccessZone The two routers do not broadcast information
about these networks through FreeAccessZone The routers only broadcast the cable range
55 As configured FreeAccessZone sees only itself However because no other limitations have been placed on advertisements the FreeAccessZone range of 55 attached and E4 propagates out to the networks to EO Router Router thus
resources in FreeAccessZone are made accessible to users on all those networks
The following examples configure Router and Router for access control illustrated in Figure 11
You must configure only Ethernet interface on Router and Ethernet interface on Router to
provide the desired access
Configuration for Router
appletalk routing
interface ethernet appletalk cable-range 5-5 appletalk zone FreeAccesszone appletalk free-trade-zone
Configuration for Router
appletalk routing
interface ethernet appletalk cable-range 5-5 appletalk zone FreeAccessZone appletalk free-trade-zone
networks When configuring both routers you need not define any access lists to prevent users on
connected to Router from accessing resources on networks connected to Router and vice versa The
appletalk free-trade-zone interface configuration command implements the necessary restrictions
CiscolOS AppleTalk and Novell IPX Configuration Guide P2C 67 Configuring AppleTalk
AppleTalk Configuration Examples
Restricting Resource Availability Example
In the preceding example shared-resource access was granted to all users in the various AppleTalk zones connected to the two routers At the same time access between resources on either side of the common denied There zone was completely might be instances where greater degree of control is
requiredpossibly where resources in some zones are to be allowed access to resources in certain other but denied zones are access to other specific zones Figure 12 illustrates such situation
Figure 12 Controlling Resource Access Among Multiple AppleTalk Zones
Zone MIS
Zone Admin Cable range 70007010
Router Zone Engineering 2230
Cable ran
H___EEGE______
AS1 S20 ne Test-lab AppleShare servers
in FreeAccessZone
The following are the objectives of the configuration in Figure 12
Users in zones Engineering E7 and MIS E0 are to be allowed free access to each other
All users in all zones are to be allowed access to FreeAccessZone2 E6
in with the No users any zone exception of users in Finance are to be allowed access to resources in Finance
The shows following example how to meet these specifications
access-list 609 permit cable 9-9 access-list 609 deny other-access
access-list 610 permit zone Finance access-list 610 permit zone FreeAccessZone2 access-list 610 deny additional-zones
access-list 611 deny cable-range 1000-1000 access-list 611 deny cable-range 9-9 access-list 611 permit cable-range 7000-7010 access-list 611 permit cable-range 22-30
The effects of these access lists are as follows
Access list 609 is intended to be used to allow access to resources on FreeAccessZone2
Access list 610 is intended to be used to control access in and out of the zone Finance
Access list 611 is intended to be used to accommodate the requirement to allow users in zones
Engineering and MIS to mutually access network resources
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 68 guring AppleTalk AppleTalk Configuration Examples
Configuration for Ethernet Interface
Ethernet interface is associated with the MIS zone The following example shows how to configure
this interface
interface ethernet appletalk cable-range 7000-7010 appletalk zone MIS appletalk distribute-list 611 out appletalk distribute-list 611 in
Specifying access list 611 results in the following filtering
Advertisements of Finance are blocked
Advertisements between Engineering and MIS are allowed
Configuration for Ethernet Interface
Ethernet interface is associated with the Finance zone The following example shows how to configure
this interface
interface ethernet appletalk cable-range 1000-1000 appletalk zone Finance appletalk distribute-list 610 out appletalk access-group 610
he effects of these access lists are as follows
With the appletalk distribute-list out interface configuration command Finance is limited to
accessing Finance and FreeAccessZone2 only
it blocks The appletalk access-group interface configuration command filters packet traffic Thus
access to any devices in Finance from outside of this zone
Configuration for Ethernet Interface
Ethernet interface is associated with the FreeAccessZone2 zone The following example shows how to
configure this interface
interface ethernet appletalk cable 9-9 appletalk zone FreeAccessZone2 appletalk distribute-list 609 out appletalk distribute-list 609 in
Configuration for Ethernet Interface
Ethernet interface is associated with the Engineering zone The configuration for this interface mirrors that for Ethernet interface because the users in both the MIS and Engineering zones must have access
to resources from each other The following example shows how to configure Ethernet interface
interface ethernet appletalk cable-range 22-30 appletalk zone Engineering appletalk distribute-list 611 out appletalk distribute-list 611 in
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 69 Configuring AppleTalk
AppleTalk Configuration Examples
Implicit Configuration of the Admin and Test-Lab Zones
Omitted from the configuration example in Figure 12 are any specific configuration commands
pertaining to the zones Test-Lab Ethernet interface on Router and Adniin Ethernet interface on
Router No configuration is done for these zones because there are no requirements relating to them
listed in the original objectives The following access control is implicitly handled with the assignment
of the stated access lists
Users in the Admin zone can see the Finance zone but cannot see resources in that zone However
as for all zones resources in FreeAccessZone2 are available but none of the users in any of the other zones can access resources in Admin
In the absence of the assignment of access lists on Router users in Test-Lab can access the
resources in the FreeAccessZone2 and Engineering zones With the exception of Engineering no other zones can access resources in Test-Lab
GZL and ZIP Reply Filter Examples
The following examples show how to configure GZL and ZIP reply filters and the differences between
these two types of filters Both examples use the configuration shown in Figure 13
Figure 13 Sample Topology for GZL and ZIP Reply Filters
Router
Router Router
Network 600
Zones
Marketing
Accounting
Engineering
Both GZL and ZIP reply filters control the zones that can be seen on network segment GZL filters
control which zones can be seen by Macintoshes on local network segments These filters have no effect
on adjacent routers In order for GZL filters to work properly all routers on the local segment must be
configured with the same access list
ZIP reply filters control which zones can be seen by adjacent routers and by all routers downstream from
adjacent routers You can use these filters to hide zones from all Macintoshes on all networks on adjacent
routers and from all their downstream routers
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 70 Configuring AppleTalk
AppleTalk Configuration Examjiiii
the in Using configuration shown Figure 13 you would use GZL filter to prevent the Macintosh on the Ethernet network segment from viewing the zones Engineering and Accounting on network 600 These
zones would not be visible via the Macintosh Chooser The following example shows how to configure Router
access-list 600 deny zone Engineering access-list 600 deny zone Accounting access-list 600 permit additional-zones access-list 600 permit other-access
interface ethernet appletalk getzonelist-filter 600
Again using the configuration shown in Figure 13 you would use ZIP reply filter to hide the
Engineering and Accounting zones from Router and Router This filter would also hide the zones
from Router which is downstream from Router The effect of this filter is that when these routers
request the names of zones on network 600 the zones names Engineering and Accounting will not be returned
access-list 600 deny zone Engineering access-list 600 deny zone Accounting access-list 600 permit additional-zones access-list 600 permit other-access
interface ethernet appletalk zip-reply-filter 600
AppleTalk hiterenterprise Routing over AURP Example
After you configure an AppleTalk domain for AppleTalk interenterprise features you can apply the
features to tunnel interface configured for AURP by assigning the domain number to the interface
The following example shows how to define tunnel interface and configure it for AURP Then it shows
how to apply the features configured for domain to tunnel interface by assigning the AppleTalk domain group to the tunnel interface
appletalk domain name France appletalk domain remap-range in 10000-19999 appletalk domain remap-range out 200-299
interface Tunnel tunnel source ethernet tunnel destination 172.19.1.17 tunnel mode aurp appletalk protocol aurp appletalk domain-group
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 71 Configuring AppleTalk AppleTalk Configuration Examples
SNMP Example
The following example shows how to activate SNMP and AppleTalk
Disable SNMP on the router no snmp-server
Enable AppleTalk routing and event logging on the router appletalk routing appletalk event-logging
Configure IP and AppleTalk on Ethernet interface interface Ethernet
ip address 131.108.29.291 255.255.255.0 appletalk cable-range 29-29 29.180 appletalk zone MarketingAl
Enable SNNP on the router snmp-server community MarketingA2 RW snmp-server trap-authentication snmp server host 131.108.2.160 MarketingA2
MacIP Examples
The following example shows how to configure MacIP support for dynamically addressed MacIP clients with dynamically allocated IP addresses in the range 172.18.0.2 to 172.18.0.10
Specify server address and zone appletalk macip server 172.18.0.1 zone Marketing
Specify dynamically addressed clients appletalk macip dynamic 172.18.0.2 172.18.0.10 zone Marketing
Assign the address and subnet mask for Ethernet interface interface ethernet
ip address 172.18.0.2 255.255.255.0
Enable AppleTalk routing appletalk routing
interface ethernet appletalk cable range 69-69 69.128 appletalk zone Marketing
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 72 Configuring AppleTalk AppleTalk Configuration ExamplesR
clients with The following example shows how to configure MacIP support for MacIP statically allocated IP addresses
Specify the server address and zone appletalk macip server 172.18.0.1 zone Marketing
Specify statically addressed clients appletalk macip static 172.18.0.11 172.18.0.20 zone Marketing appletalk macip static 172.18.0.31 zone Marketing appletalk macip static 172.18.0.41 zone Marketing appletalk macip static 172.18.0.49 zone Marketing
Assign the address and subnet niask for Ethernet interface interface ethernet
ip address 172.18.0.1 255.255.255.0
Enable AppleTalk routing appletalk routing
interface ethernet appletalk cable range 69-69 69.128 appletalk zone Marketing
IPTaIk Exampe
Cisco lOS software to IPTalk This section describes how to set up UNIX-based systems and our use CAP and other IPTalk implementations
software and hosts for The following procedure outlines the basic steps for setting up our UNIX
operation using IPTaIk implementations
Note This procedure does not provide full instructions about how to install CAP on the UNIX
file of system However it does address the requirements for setting up the configuration the UNIX system that defines addresses and other network information Generally this is the Refer to the only file that relies on the address and configuration information of router
your UNIX system and CAP software manuals for information about building the CAP
software and setting up the UNIX startup scripts
between these routers Step Enable AppleTalk routing on all the routers that will use IPTalk and any routers
to the Step Enable IP routing on the interfaces that will communicate with the UNIX system Refer These Cisco lOS iP and IP Routing Configuration Guide for more information about configuring IP
is enabled the interfaces must be on the same subnet as the UNIX system Also ensure that IP on UNIX system
network number for Step Allocate an AppleTalk network number for IPTalk You need separate AppleTalk
each IP subnet that is to run IPTa1k
You can have number of UNIX machines on the same subnet They all use the same AppleTalk node identifiers network number for IPTalk However they must have their own individual
interface must It is possible for the same router to have IPTalk enabled on several interfaces Each
have different AppleTalk network number allocated to IPTa1k because each interface will be using
different IP subnet
IPX Guide Cisco lOS AppleTalk and Novell Configuration ______P2C 73 Configuring Applelalkj AppleTalk Configuration Examples
Determine the format Step CAP of the AppleTalk network number The CAP software is based on an older convention AppleTalk that expresses AppleTalk network numbers as two octets decimal numbers from
to 255 separated by dot The current AppleTalk convention uses decimal numbers from to 65279
Use the following formula to convert between the two
CAP format x.y Apple format
To convert from AppleTalk to CAP
d/256 represents truncating integer division
d%256 represents the remainder of the division
To convert from CAP to AppleTalk dx 256y
Example AppleTalk format 14087
CAP format 55.7
Choose for IPTalk Step zone name No special constraints are placed on zone name choices You can use the same zone name for several networks and you can combine IPTalk and normal AppleTalk networks in the same zone
Decide which to for Step UDP ports use IPTalk The default is to use ports beginning with 768 Thus RTMP uses and port 769 NBP port 770 so on These are the original AppleTalk ports and their numbers are
hardcoded into older versions of The with them is that CAP only problem using they are not officially the Internets assigned by NIC which has assigned set of UDP ports beginning with 200 Thus other could applications use them possibly causing conflictsalthough this is unlikely With CAP releases
5.0 and later can to the allocated If do you configure CAP use officially ports you so RTMP will use NBP and so Whichever both port 201 port 202 on ports you use you must configure CAP and the router to use the same ones
The following example shows how to enable IPTalk on each interface of the router as required
appletalk routing
interface ethernet
ip address 172.16.7.22 255.255.255.0 appletalk cable 1792-1792 1792.22 appletalk zone MIS-Development interface TunnelO tunnel source EthernetO tunnel mode iptalk appletalk iptalk 14087 MIS-UNIX
In this is example AppleTalk routing enabled on the interface in the following two ways
Via EtherTalk phase using the cable range 17921792 and the zone MIS -Development
Via IPTalk using the network number 14087 and the zone MIS -UNIX
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 74 u_Configuring AppleTalk AppleTalk Configuration Examples
Note The IPTaIk node identifier is chosen automatically based on the IP address It
is normally the host number portion of the IP address For example with an IP
address of 172.16.7.22 and subnet mask of 255.255.255.0 the host number
is 22 Thus the IPTalk node identifier would be 22 If the IP host number is
larger than 255 the low-order bits are used although fewer than bits may
be available depending on the IP subnet mask If the mask leaves fewer bits
the node number will be quietly truncated Be sure to use node address that
is compatible with the subnet mask In any event you may experience problems when using IPTaIk with host numbers larger than 255
If you choose to use the official UDP ports those beginning with 200 include the following global
configuration command in your configuration
appletalk iptalk-baseport 200
Step Configure each UNIX host with network number zone name and router
The following example shows the contents of the /etc/atalk.local file from UNIX system with the
IP address 172.19.7.26 and network mask of 255.255.255.0
IPTalk on net 17219.7.0 mynet mynode myzone 55.7 26 MIS-UNIX bridgenet bridgenode bridgelP 55.7 22 172.19.7.22
The first noncommented line defines the address of the UNIX system and the second
noncommented line defines the address of the router In both cases the first number is 55.7 which
is the AppleTalk network number in CAP format for use by IPTalic The second number is the
AppleTalk node identifier which must be the same as the IP host number The last number on the
first line is the zone name and on the second line it is the IP address of the router
Note the following about the entries in the /etc/atalk.local file
The AppleTalk network number in the first colunm in both lines must agree with the AppleTalk
network number used in the appletalk iptalk command However in the /etc/atalk.local file
the number must be in the CAP format while in the configuration command it must be in the
Apple format
the IP host number of the The host number in the second column in both lines must agree with of the corresponding system That is on the first line it must be the IP host number UNIX
machine and on the second line it must be the IP host number for the router
used in the The zone name in the third column on the first line must agree with the zone name
appletalk iptalk command
The IP address in the third column of the second line must be the IP address of the router
the CAP Step Ensure that your CAP software is using the same UDP port numbers as the router Currently II default is the same as the router default which is port numbers beginning with 768 you want to use
this if official UDP default you need not take any further action However you want to use the port command in numbers port numbers beginning with 200 ensure that you have included the following
your configuration
appletalk iptalk-baseport 200
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 75 Configuring AppleTalk
AppleTalk Configuration Examples
Step On the UNIX system add the following lines to the /etc/services file
at-rtmp 201/udp at-nbp 202/udp at-3 203/udp at-echo 204/udp at-5 205/udp at-zis 206/udp at-7 207/udp at-8 208/udp
If you are using Network Information Services NIS previously known as the Yellow Pages
remember to do make in after /etc/services If /var/yp changing you are using the default ports
those starting with 768 you need not modify /etc/services
AppleTalk Control Protocol Example
The shows following example how to set up router to accept AppleTalk client requests on asynchronous
interface and create virtual network number and the AppleTalk zone Twiddledee
appletalk virtual-net Twiddledee interface async encapsulation ppp appletalk client-mode
Proxy Network Number Example
Assume that network looks like the in 14 Also that your topology one Figure assume Router supports
only nonextended AppleTalk that Router supports only extended AppleTalk not in transition mode and that Router supports only extended AppleTalk
Figure 14 Sample Network Topology
Router Cable/Range Router Cable/Range Router Cable/Range
Cisco Phase Cisco Phase AppleTalk Router Router Phase Router
Router Router
Cisco Phase Cisco Phase Router Router
Cable/Range 100100
If Router generates an NBP hookup request for Zone Router will convert this request to forward
and send it Router request to Because Router supports only nonextended AppleTalk it does not handle the forward request and ignores it Hence the NBP lookup from Router fails
To work around this problem without putting transition router adjacent to the nonextended-only router Router you could configure Router with an NBP proxy
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 76 Configuring AppleTalk
AppleTalk Configuration ExampleU
If you configured Router with an NBP proxy as follows any forward requests received for Zone are
converted into lookup requests and therefore the nonextended router for Network 60 can properly
respond to NBP hookup requests generated beyond Router The following example shows the
command needed to describe this configuration
appletalk proxy 60
AppleTalk Enhanced IGRP Bandwidth Configuration Example
The following example shows how to configure the bandwidth used by AppleTalk Enhanced IGRP In
is maximum of 25 32 of this example Enhanced IGRP process configured to use percent or kbps 128-kbps circuit
interface serial bandwidth 128 appletalk eigrp-bandwidth-percentage 25
The following example shows how to configure the bandwidth of 56-kbps circuit to 20kbps This value
was chosen for routing policy reasons EIGRP process is configured to use maximum of 200 percent or 40 kbps of the circuit
interface serial bandwidth 20 appletalk eigrp-bandwidth-percentage 200
AppleTalk Interenterprise Routing Example
The following example shows how to configure AppleTalk interenterprise routing It configures domain
which is named France and places Ethernet interface into this domain
appletalk domain name France appletalk domain remap-range in 10000-19999 appletalk domain remap-range out 200-299 appletalk domain hop-reduction
interface ethernet
no ip address no keepalive appletalk cable-range 300-300 300.6 appletalk zone Europe appletalk protocol eigrp appletalk domain-group
AppleTalk over DDR Example
The following example describes how to configure AppleTalk to run over DDR interface as illustrated
in Figure 15 When configuring AppleTalk over DDR you must specify DDR on the interface on which the static neighbor resides before you specify the static route itself Also the Cisco lOS software must know the network address of the static neighbor before you specify the static route Otherwise the software will not know to which interface the static neighbor is connected To open an AppleTalk DDR
link there must be at least one AppleTalk access list bound to dialer group
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C-77 Configuring AppleTalk
AppleTalk Configuration Examples
Figure 15 AppleTalk over DDR Configuration
Macintosh Router AppleShare Router server neDDRZonemotjL
Cable Range 11 Cable Range 100110
The following example shows the steps required to configure AppleTalk over DDR on Router
Step Configure an access list and dialer group
access-list 601 permit cable 100-110 dialer-list list 601
Step Configure the serial interface
interface serial dialer in-band
dialer string 1234 appletalk cable 1-1 1.1 appletalk zone DDR dialer-group apple distribute-list 601 in
Step Create the static route
appletalk static cable 100-110 to 1.2 zone Remote
Step Open the Chooser on the Macintosh
Select Step any AppleTalk service such as AppleShare LaserWriter and so on in zone Remote to cause Router to dial up Router to open DDR link between them
Select Step an AppleTalk file server in the zone Remote After some time AppleTalk services appear in zone Remote Select the one that you need
Step Close the Chooser
Step Open the AppleTalk session to the remote service
After the Step AppleTalk session is finished close the connection to the remote service The DDR link should
go down after the DDR idle time has elapsed
Instead of static route in static creating Step you can create floating route The following example
adds floating static route to cable-range 10-11 in the Eng zone with AppleTalk address 6.5 as the next hop router
appletalk static cable-range 10-11 to 6.5 floating zone Eng
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 78 Configuring AppleTalk
AppleTalk Configuration ExampleiR
AppleTalk Control Protocol for PPP Example
The following example shows how to set up your router to accept AppleTalk client requests on interfaces and using the virtual network number and the AppleTalk zone Twiddledee
Router enable Router config terminal Routerconfig appletalk virtual-net Twiddledee Routerconfig interface async Router config-int encapsulation ppp Router config-int appletalk client-mode Routerconfig-int interface async Router config-int encapsulation ppp Router config-int appletalk client-mode
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 79 Configuring AppleTalk
AppleTalk Configuration Examples
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 80 Configuring Novell IPX i/z
This chapter describes how to configure Novell Internetwork Packet Exchange IPX and provides
configuration examples For complete description of the IPX conimands in this chapter refer to the
Novell IPX Commands chapter in the Cisco lOS AppleTalk and Novell IPX Command Reference
publication To locate documentation of other commands that appear in this chapter use the command
reference master index or search online
To identify the hardware platform or software image information associated with feature use the
Feature Navigator on Cisco.com to search for information about the feature or refer to the software
release notes for specific release For more information see the Identifying Supported Platforms
section in the Using Cisco lOS Software chapter
IPX Addresses
An IPX network address consists of network number and node number expressed in the format network.node
Network Numbers
that must be The network number identifies physical network It is 4-byte 32-bit quantity unique hexadecimal The throughout the entire IPX internetwork The network number is expressed as digits
maximum number of digits allowed is eight
omit The Cisco lOS software does not require that you enter all eight digits you can leading zeros
Node Numbers
dotted The node number identifies node on the network It is 48-bit quantity represented by triplets
of four-digit hexadecimal numbers
lOS software If you do not specify node number for router to be used on WAN links the Cisco uses address of the the hardware MAC address currently assigned to it as its node address This is the MAC the Cisco lOS first Ethernet Token Ring or FDDI interface card If there are no valid IEEE interfaces clock software randomly assigns node number using number that is based on the system
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 81 Configuring Novell LJ IPX Configuration Task List
IPX Address Example
The following example shows how to configure an IPX network address
4a.0000 OcOO 23fe
In this the example network number is 4a more specifically it is 0000004a and the node number is
0000.OcOO.23fe All digits in the address are hexadecimal
IPX Configuration Task List
To configure IPX routing perform the tasks in the following sections
Configuring IPX Routing Required
Configuring IPX Enhanced IGRP Optional
Configuring NLSP Optional
Configuring Next Hop Resolution Protocol Optional
Configuring IPX and SPX over WANs Optional
Controlling Access to IPX Networks Optional
Tuning IPX Network Performance Optional
Shutting Down an IPX Network Optional
Configuring IPX Accounting Optional
Configuring IPX Between LANs Optional
Configuring IPX Between VLANs Optional
Configuring IPX Multilayer Switching Optional
Monitoring and Maintaining the IPX Network Optional
See the Novell IPX section the end Configuration Examples at of this chapter for configuration examples
Configuring IPX Routing
You IPX first it configure routing by enabling on the router and then configuring it on each interface
can route interfaces Optionally you IPX on some and transparently bridge it on other interfaces You can also route IPX traffic between routed interfaces and bridge groups or route IPX traffic between bridge groups
To configure IPX routing perform the tasks in the following sections The first two tasks are required the rest are optional
Enabling IPX Routing Required
Assigning Network Numbers to Individual Interfaces Required
Enabling Concurrent Routing and Bridging Optional
Configuring Integrated Routing and Bridging Optional
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 82 Configuring Novell IPX
IPX Configuration Task List
IPX Default Routes
In IPX default route is the network where all packets for which the route to the destination address is
unknown are forwarded
allowed the of network -2 Original Routing Information Protocol RIP implementations use
OxFFFFFFFE as regular network number in network With the inception of NetWare Link Services Protocol NLSP network -2 is reserved as the default route for NLSP and RIP Both NLSP and RIP routers should treat network -2 as default route Therefore you should implement network -2 as the in IPX network default route regardless of whether you configure NLSP your
By default Cisco lOS software treats network -2 as the default route You should ensure that your IPX
network does not use network -2 as regular network If for some reason you must use network -2 as Default Routes regular network you can disable the default behavior To do so see the Adjusting
section later in this chapter
refer the Novell NetWare Link For more background information on how to handle IPX default routes to
Services Protocol NLSP Specification Revision 1.1 publication
Enabling IPX Routing
If do not the node number The first step in enabling IPX routing is to enable it on the router you specify
of the router to be used on WAN links the Cisco lOS software uses the hardware MAC address currently
the first Token or FDDI assigned to it as its node address This is the MAC address of Ethernet Ring
interface card If there are no valid IEEE interfaces the Cisco lOS software randomly assigns node
number using number that is based on the system clock
To enable IPX routing use the following command in global configuration mode
Command Purpose
Router config ipx routing Enables IPX routing
section at the end of this For an example of how to enable IPX routing see the IPX Routing Examples
chapter
should Caution If you plan to use DECnet and IPX routing concurrently on the same interface you MAC enable DECnet routing first then enable IPX routing without specifying the optional for IPX will be node number If you enable IPX before enabling DECnet routing routing
disrupted because DECnet forces change in the MAC-level node number
Assigning Network Numbers to Individual Interfaces
individual interfaces After you have enabled IPX routing you enable IPX routing on the by assigning
network numbers to those interfaces
networks You enable IPX routing on interfaces that support single network or multiple
to use When you enable IPX routing on an interface you can also specify an encapsulation frame type IEEE for packets being sent on that network Table lists the encapsulation types you can use on interfaces and shows the correspondence between Cisco naming conventions and Novell naming
conventions for the encapsulation types
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 83 Configuring Novell IPX IPX Configuration Task List
Table Cisco and Novell IPX Encapsulation Names on IEEE Interfaces
Interface Type Cisco Name Novell Name
Ethernet novell-ether Cisco lOS default Ethernet_802.3
arpa Ethernet_IT
sap Ethernet_802.2
snap Ethernet_Snap
Token Ring sap Cisco lOS default Token-Ring
snap Token-Ring_Snap FDDI snap Cisco lOS default Fddi_Snap
sap Fddi_802.2 novell-fddi Fddi_Raw
Note The is SNAP encapsulation type not supported and should not be configured on any IPX interfaces that are attached to FDDI-Ethernet bridge
Assigning Network Numbers to Individual Interfaces Task List
The sections describe how to enable following IPX routing on interfaces that support single network and those that on support multiple networks To enable IPX routing on an interface you must perform one of the tasks
Assigning Network Numbers to Interfaces That Support Single Network Required
Assigning Network Numbers to Interfaces That Support Multiple Networks Required
Setting the Encapsulation Type for Subinterfaces Required
Network Assigning Numbers to Interlaces That Support Single Network
single interface can support single network or networks For multiple logical single network you
can Of it should configure any encapsulation type course match the encapsulation type of the servers and clients using that network number
To network number to an interface that assign supports single network use the following command in interface configuration mode
Command Purpose
Routerconfig-if ipx network network Enables IPX routing on an interface encapsulation- type
If an be you specify encapsulation type sure to choose the one that matches the one used by the servers
and clients on that network Novell-ether or ARPA encapsulations cannot be used for FDDI-Ethernet
IPX traffic Use bridged SAP encapsulations on originating and destination IPX interfaces that are
attached to the FDDI-Ethernet See bridge Table for list of encapsulation types you can use on IEEE interfaces
For of how enable an example to IPX routing see the IPX Routing Examples section at the end of this chapter
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 84 Configuring Novell IPX
IPX ontiguration Task List
Assigning Network Numbers to Interfaces That Support Multiple Networks
When assigning network numbers to an interface that supports multiple networks you must specify networks share the different encapsulation type for each network Because multiple physical medium
the Cisco lOS software is allowed to identify the packets that belong to each network For example you can configure up to four IPX networks on single Ethernet cable because four encapsulation types are
the and clients supported for Ethernet Remember the encapsulation type should match servers using the IEEE interfaces same network number See Table for list of encapsulation types you can use on
There are two ways to assign network numbers to interfaces that support multiple networks You can use subinterfaces or primary and secondary networks
Setting the Encapsulation Type for Subinterfaces
You typically use subinterfaces to assign network numbers to interfaces that support multiple networks
subinterface is mechanism that allows single physical interface to support multiple logical
interfaces or networks That is several logical interfaces or networks can be associated with single
hardware interface Each subinterface must use distinct encapsulation and the encapsulation must
match that of the clients and servers using the same network number
Note When enabling NLSP and configuring multiple encapsulations on the same physical LAN
interface you must use subinterfaces You cannot use secondary networks
Any interface configuration parameters that you specify on an individual subinterface are applied to that subinterface only
To configure multiple IPX networks on physical interface using subinterfaces use the following
commands beginning in global configuration mode
Command Purpose
Step Router config 4t interface type Specifies subinterface number subinterface-number
Step Router config-if ipx network network Enables IPX routing specifying the first encapsulation type encapsulation type
To configure more than one subinterface repeat these two steps See Table for list of encapsulation
types you can use on IEEE interfaces
For examples of configuring multiple IPX networks on an interface see the IPX Routing on Multiple
Networks Examples section at the end of this chapter
Primary and Secondary Networks
also When assigning network numbers to interfaces that support multiple networks you can configure primary and secondary networks
The first logical network you configure on an interface is considered the primary network Any additional networks are considered secondary networks Again each network on an interface must use network distinct encapsulation and it should match that of the clients and servers using the same number
all the Any interface configuration parameters that you specify on this interface are applied to logical is used all four networks For example if you set the routing update timer to 120 seconds this value on networks
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 85 Configuring Novell IPX
Configuring IPX Enhanced IGRP
To use primary and secondary networks to configure multiple IPX networks on an interface use the
following commands in interface configuration mode
Command Purpose
Router conf if network network Step ig- ipx Enables IPX routing on the primary network encapsulati on-type
Router network network Step config-if ipx Enables IPX routing on secondary network encapsulation-type
To configure more than one secondary network repeat these steps as appropriate See Table for list
of encapsulation types you can use on IEEE interfaces
Note and When enabling NLSP configuring multiple encapsulations on the same physical LAN
interface you must use subinterfaces You cannot use secondary networks
Enabling Concurrent Routing and Bridging
route interfaces and You can IPX on some transparently bridge it on other interfaces simultaneously To
enable this type of routing you must enable concurrent routing and bridging To enable concurrent
routing and bridging use the following command in global configuration mode
Command Purpose
Router config orb bridge Enables the Cisco lOS software to both route and bridge given
protocol on separate interfaces within single router
Configuring Integrated Routing and Bridging
Integrated routing and bridging IRB enables user to route IPX traffic between routed interfaces and
bridge groups or route IPX traffic between bridge groups Specifically local or unroutable traffic is bridged among the bridged interfaces in the same bridge group Routable traffic is routed to other routed interfaces or bridge groups Using IRB you can do the following
Switch packets from bridged interface to routed interface
Switch packets from routed interface to bridged interface
Switch packets within the same bridge group
For more information about configuring integrated routing and bridging refer to the Configuring in the Transparent Bridging chapter Cisco lOS Bridging and IBM Networking Configuration Guide
Configuring IPX Enhanced IGRP
Enhanced IGRP is enhanced an version of the Interior Gateway Routing Protocol IGRP developed by Cisco Enhanced IGRP the uses same distance vector algorithm and distance information as IGRP the However convergence properties and the operating efficiency of Enhanced IGRP have improved
significantly over IGRP
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 86 Novell IPX Configuring Configuring IPX Enhanced lGU
The convergence technology is based on research conducted at SRI International and employs an algorithm referred to as the Diffusing Update Algorithm DUAL This algorithm guarantees loop-free instant and allows all routers involved in operation at every throughout route computation topology
change to synchronize at the same time Routers that are not affected by topology changes are not
involved in recomputations The convergence time with DUAL rivals that of any other existing routing protocol
Enhanced IGRP Features
Enhanced IGRP offers the following features
Fast convergenceThe DUAL algorithm allows routing information to converge as quickly as any
currently available routing protocol
Partial updatesEnhanced IGRP sends incremental updates when the state of destination changes minimizes the bandwidth instead of sending the entire contents of the routing table This feature
required for Enhanced IGRP packets
Less CPU usage than IGRPFull update packets need not be processed each time they are received
Neighbor discovery mechanismThis feature is simple hello mechanism used to learn about
neighboring routers It is protocol-independent
ScalingEnhanced IGRP scales to large networks
Enhanced GRP Components
Enhanced IGRP has four basic components discussed in the following sections
Neighbor Discovery/Recovery
Reliable Transport Protocol
DUAL Finite-State Machine
Protocol-Dependent Modules
Neighbor Discovery/Recovery
Neighbor discovery/recovery is the process that routers use to dynamically learn of other routers on their
directly attached networks Routers must also discover when their neighbors become unreachable or
inoperative The router achieves neighbor discovery/recovery with low overhead by periodically sending
small hello packets As long as hello packets are received router can determine that neighbor is alive
and functioning Once this status is determined the neighboring devices can exchange routing information
Reaiabe Transport ProtocoU
of Enhanced IGRP The reliable transport protocol is responsible for guaranteed ordered delivery unicast Some packets to all neighbors It supports intermixed transmission of multicast and packets
is Enhanced IGRP packets must be sent reliably and others need not be For efficiency reliability multicast provided only when necessary For example on multiaccess network that has capabilities
such as Ethernet it is not necessary to send hellos reliably to all neighbors individually Therefore the receivers Enhanced IGRP sends single multicast hello with an indication in the packet informing
that the packet need not be acknowledged Other types of packets such as updates require
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 87 Configuring NoveI LJ Configuring IPX Enhanced IGRP
which is indicated in the The acknowledgment packet reliable transport has provision to send multicast when there packets quickly are unacknowledged packets pending This provision helps ensure that time remains low in the convergence presence of varying speed links
DUAL FiniteState Machine
The DUAL finite-state machine embodies the decision for all process route computations It tracks all routes advertised all by neighbors DUAL uses the distance information known as metric to select
efficient loop-free paths DUAL selects routes to be inserted into routing table based on feasible successors successor is router used for neighboring packet forwarding that has least-cost path to destination that is guaranteed not to be part of routing ioop When there are no feasible successors but there are the neighbors advertising destination recomputation must occur This is the process is whereby new successor determined The amount of time it takes to recompute the route affects the
time is is convergence Recomputation processor-intensive It advantageous to avoid recomputation if it is not necessary When topology change occurs DUAL will test for feasible successors If there are
feasible it successors will use any it finds in order to avoid unnecessary recomputation
Protocol-Dependent Modules
The protocol-dependent modules are responsible for network layer protocol-specific tasks They are also for responsible parsing Enhanced IGRP packets and informing DUAL of the new information received
Enhanced IGRP asks DUAL to make but the in routing decisions results are stored the IPX routing table Enhanced IGRP is Also responsible for redistributing routes learned by other IPX routing protocols
IPX Enhanced HGRP Configtration Task List
To enable IPX Enhanced IGRP perform the tasks in the following sections Only the first task is
required the remaining tasks are optional
Enabling IPX Enhanced IGRP Required
Customizing Link Characteristics Optional
Customizing the Exchange of Routing and Service Information Optional
Querying the Backup Server Optional
Enabling IPX Enhanced IGRP
To create an IPX Enhanced IGRP the routing process use following commands beginning in global configuration mode
Command Purpose
Step Router config ipx router eigrp Enhanced Enables an IGRP routing process aUbonomous-sysbem-nunther
Step2 Routerconfig-if network network-nunther all Enables EnhancedlGRP onanetwork
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 88 figuring Novell IPX Configuring IPX Enhanced IGRP
To associate multiple networks with an Enhanced IGRP routing process you can repeat the preceding
two steps
For an example of how to enable Enhanced IGRP see the IPX Enhanced IGRP Example section at the
end of this chapter
Cllstomizing Link Characteristics
sections describe You might want to customize the Enhanced IGRP link characteristics The following
these customization tasks
Configuring the Percentage of Link Bandwidth Used by Enhanced IGRP Optional
Configuring Maximum Hop Count Optional
Adjusting the Interval Between Hello Packets and the Hold Time Optional
Configuring the Percentage of Link Bandwidth Used by Enhanced IGRP
of the link By default Enhanced IGRP packets consume maximum of 50 percent bandwidth as
value is the configured with the bandwidth interface subconimand If different desired use ipx bandwidth-percent command This command may be useful if different level of link utilization link bandwidth have been is required or if the configured bandwidth does not match the actual it may
configured to influence route metric calculations
IGRP the To configure the percentage of bandwidth that may be used by Enhanced on an interface use
following command in interface configuration mode
Command Purpose
Router config-if ipx bandwidth-percent eigrp Configures the percentage of bandwidth that may be used by
ac-number percent Enhanced IGRP on an interface
the For an example of how to configure the percentage of Enhanced IGRP bandwidth see IPX
Enhanced IGRP Bandwidth Configuration Example section at the end of this chapter
Configuring Maximum Flop Count
is recommended for Note Although adjusting the maximum hop count is possible it not Enhanced IGRP We recommend that you use the default value for the maximum hop count of Enhanced IGRP
In this By default IPX packets whose hop count exceeds 15 are discarded larger internetworks maximum hop count may be insufficient You can increase the hop count to maximum of 254 hops for Enhanced IGRP To modify the maximum hop count use the following command in global configuration mode
Command Purpose
Router config ipx maximum-hops hop Sets the maximum number of hops of an IPX packet reachable by number of non-RIP routing protocols Also sets the maximum routers
that an IPX packet can traverse before being dropped
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 89 Configuring Novell IPXJ Configuring IPX Enhanced IGRP
Adjusting the Interval Between Hello Packets and the Hold Time
You can adjust the interval between hello packets and the hold time
Routers periodically send hello packets to each other to dynamically learn of other devices on their attached networks Routers directly use this information to discover their neighbors and to discover when
their neighbors become unreachable or inoperative
hello By default packets are sent every seconds The exception is on low-speed nonbroadcast multiaccess where NBMA media the default hello interval is 60 seconds Low speed is considered to be rate of Ti or slower as specified with the bandwidth interface configuration command The default
hello interval remains seconds for high-speed NBMA networks
Note For the purposes of Enhanced IGRP Frame Relay and SMDS networks may or may not be
considered to be NBMA These networks are considered NBMA if the interface has not
been to configured use physical multicasting otherwise they are considered not to be NBMA
You can the hold time on interface for Enhanced IGRP configure specified particular routing process the designated by autonomous system number The hold time is advertised in hello packets and indicates
to neighbors the length of time they should consider the sender valid The default hold time is three times
the hello interval or 15 seconds
and On very congested large networks 15 seconds may not be sufficient time for all routers to receive hello from their packets neighbors In this case you may want to increase the hold time To increase the hold the time use following command in interface configuration mode
Command Purpose
Routerconfig-if ipx hold-time eigrp Sets the hold time autonomous-system-nurnjer seconds
To the interval between hello the change packets use following command in interface configuration mode
Command Purpose
Router config-if hello-interval ipx eigrp Sets the interval between hello packets autonomous-system-numjer seconds
Note Do not adjust the hold time without consulting with Cisco technical support
Customizing the Exchange of Routing and Service Information
You want to customize the of and might exchange routing service information The following sections describe these customization tasks
Redistributing Routing Information Optional
Disabling Split Horizon Optional
Controlling the Advertising of Routes in Routing Updates Optional
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 90 Configuring Novell IPX Configuring IPX Enhanced IGRP
Controlling the Processing of Routing Updates Optional
Controlling SAP Updates Optional
Controlling the Advertising of Services in SAP Updates Optional
Controlling the Processing of SAP Updates Optional
Redistributing Routing Information
By default the Cisco lOS software redistributes IPX RIP routes into Enhanced IGRP and vice versa
To disable route redistribution use the following command in IPX-router configuration mode
Command Purpose
Router conf ig- ipx- router no redistribute Disables redistribution of RIP routes into Enhanced
connected eigrp autonomous-system-number rip static IGRP andEnhanced IGRP routes into RIP
The Cisco lOS software does not automatically redistribute NLSP routes into Enhanced IGRP routes and commands in vice versa To configure this type of redistribution use the following beginning global
configuration mode
Command Purpose
Enhanced Step Router config ipx router eigrp From global configuration mode enables autonomous-system-number IGRP
redistribute enables Step Routerconfig-ipx-router niap From IPX-router configuration mode redistribution of NLSP into Enhanced IGRP
Step Routerconfig ipx router n.sp Enables NLSP
enables Step Router config-ipx-router redistribute eigrp From IPX-router configuration mode autonomous-system-number redistribution of Enhanced IGRP into NLSP
For an example of how to enable redistribution of Enhanced IGRP and NLSP see the Enhanced IGRP
and NLSP Route Redistribution Example section at the end of this chapter
Disabling Split Horizon
Enhanced IGRP and If horizon is Split horizon controls the sending of update query packets split is the that enabled on an interface these packets are not sent for destinations if this interface next hop to
destination
horizon is all interfaces By default split enabled on
advertised the Cisco lOS software out Split horizon blocks information about routes from being by any
interface from which that information originated This behavior usually optimizes communication broken with nonbroadcast networks among multiple routers particularly when links are However such these as Frame Relay and SMDS situations can arise for which this behavior is less than ideal For
situations you can disable split horizon
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 91 Configuring Nove_j Configuring IPX Enhanced IGRP
To disable split horizon use the following command in interface configuration mode
Command Purpose
Router config-if no ipx split-horizon eigrp Disables split horizon autonomous-system-number
Note Split horizon cannot be disabled for REP or SAP only for Enhanced IGRP
Controlling the Advertising of Routes in Routing Updates
To control which devices learn about routes you can control the advertising of routes in routing updates
To control this advertising use the following command in router configuration mode
Command Purpose
Router config-router distribute-list accesslist-number Controls the advertising of routes in routing updates out routing-process
ControHing the Processing of Routing Updates
To control the of processing routes listed in incoming updates use the following command in router
configuration mode
Command Purpose
Router config-router distribute-list access-list-number Controls which incoming route updates are processed in
Controlling SAP Updates
If IPX Enhanced IGRP peers are found on an interface you can configure the Cisco lOS software to send SAP updates either periodically or when change occurs in the SAP table When no IPX Enhanced IGRP peer is present on the interface periodic SAPs are always sent
On serial lines by default if an Enhanced IGRP neighbor is present the Cisco 105 software sends SAP when the SAP updates only table changes On Ethernet Token Ring and FDDI interfaces by default the software sends SAP updates periodically To reduce the amount of bandwidth required to send SAP
updates you might want to disable the periodic sending of SAP updates on LAN interfaces This feature should be disabled when only all nodes out of this interface are Enhanced IGRP peers otherwise loss of SAP information on the other nodes will result
To send SAP updates only when change occurs in the SAP table use the following command in
interface configuration mode
Command Purpose
Routerconfig-if ipx sap-incremental eigrp Sends SAP updates only when change in the SAP autonomous-system-number table occurs
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 92 Configuring Novell IPX
Configuring IPX Enhanced IGRP
To send SAP updates only when change occurs in the SAP table and to send only the SAP changes use
the following command in interface configuration mode
Command Purpose
Routerconfig-.if ipx sap-incremental eigrp Sends SAP updates only when change in the SAP autonomous-system-number rsup-only table occurs and sends only the SAP changes
When you enable incremental SAP using the ipx sap-incremental eigrp rsup-only command Cisco lOS software disables the exchange of route information via Enhanced IGRP for that interface
To send periodic SAP updates use the following command in interface configuration mode
Command Purpose
Router config-if no ipx sap-incremental eigrp Sends SAP updates periodically autonomous -system-number
For an example of how to configure SAP updates see the Enhanced IGRP SAP Update
Examples section at the end of this chapter
To disable split horizon for incremental SAP use the following command in interface configuration mode
Command Purpose
Router config-if no ipx sap-incremental split-horizon Disables split horizon for SAP
Note IPX incremental SAP split horizon is off for WAN interfaces and subinterfaces and on for
LAJT interfaces The global default stays off The interface setting takes precedence if the
interface setting is modified or when both the global and interface settings are unmodified
The global setting is used only when the global setting is modified and the interface setting
is unmodified
Controlling the Advertising of Services in SAP Updates
To control which devices learn about services you can control the advertising of these services in SAP
updates To control this advertising use the following command in router configuration mode
Command Purpose
Router config-router distribute-sap-list access-list-number Controls the advertising of services in SAP out routing-process updates distributed between routing processes
Advertisement For configuration example of controlling the advertisement of SAP updates see the
and Processing of SAP Update Examples section at the end of this chapter
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 93 Configuring Novell IPX
Configuring NLSP
Controlling the Processing of SAP Updates
To control the processing of routes listed in incoming updates use the following command in router
configuration mode
Command Purpose
Router config-router access-list-number ditribute-sap-1ist Controls which incoming SAP updates are in processed
For configuration example of controlling the processing of SAP updates see the Advertisement and
Processing of SAP Update Examples section at the end of this chapter
Querying the Backup Server
The table is table backup server kept for each Enhanced IGRP peer It lists the IPX servers that have
been advertised that by peer If server is removed from the main server table at any time and for any reason the Cisco lOS software examines the backup server table to learn if this just-removed server is of the Enhanced known by any IGRP peers If it is the information from that peer is advertised back into the main table server just as if that peer had readvertised the server information to this router Using this method to allow the router to keep the backup server table consistent with what is advertised by each
peer means that only changes to the table must be advertised between Enhanced IGRP routers full
periodic updates need not be sent
By default the Cisco lOS software queries its own copy of the backup server table of each Enhanced
IGRP neighbor every 60 seconds To change this interval use the following command in global
configuration mode
Command Purpose
Router config ipx Specifies the minimum period of time between successive queries of backup-server-query-interval interval the backup server table of neighbor
Configuring NLSP
NLSP is link-state routing protocol based on the Open System Interconnection OSI Intermediate System-to-Intermediate System IS-IS protocol
NLSP is designed to be used in hierarchical routing environment in which networked systems are
grouped into routing areas Routing areas can then be grouped into routing domains and domains can be grouped into an internetwork
Understanding Level 12 and Routers
Level routers connect networked systems within given routing area Areas are connected to each
other by Level routers and domains are connected by Level routers Level router also acts as
within its Level router own area likewise Level router also acts as Level router within its own domain
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 94 Configuring Novell IPX
Configuring NLS
The router at each level of the topology stores complete information for its level For instance Level routers store complete link-state information about their entire area This information includes record
of all the routers in the area the links connecting them the operational status of the devices and their
links and other related parameters For each point-to-point link the database records the end-point
devices and the state of the link For each LAN the database records which routers are connected to the
LAN Similarly Level routers would store information about all the areas in the routing domain and
Level routers would store information about all the domains in the internetwork
Although NLSP is designed for hierarchical routing environments containing Level and routers
only Level routing with area route aggregation and route redistribution has been defined in
specification
Understanding NLSP Databases
in maintains identical NLSP is link-state protocol which means that every router routing area an copy
of the link-state database This database contains all information about the topology of the area All
their of the link-state routers synchronize their views of the databases among themselves to keep copies
databases consistent NLSP has the following three major databases
AdjacencyKeeps track of the immediate neighbors of the router and the operational status of the created of directly attached links by exchanging hello packets Adjacencies are upon receipt periodic hello packets If link or router goes down adjacencies time out and are deleted from the database
the immediate Link stateTracks the connectivity of an entire routing area by aggregating
neighborhood information from all routers into link-state packets LSPs LSPs contain lists of time link adjacencies They are flooded to all other devices via reliable flooding algorithm every link-state database state changes LSPs are refreshed every hours To keep the size of the and reasonable NLSP uses fictitious pseudonodes which represent the LAN as whole designated
routers which originate LSPs on behalf of the pseudonode
shortest ForwardingCalculated from the adjacency and link-state databases using Dijkstras path first SPF algorithm
Cisco Support of NLSP
The Cisco implementation of NLSP supports the Novell NLSP specification version 1.1 Our
implementation of NLSP also includes read-only NLSP MIB variables
NLSP Configuration Task List
To configure NLSP you must have configured IPX routing on your router as described previously in this chapter Then you must perform the tasks described in the following sections
Defining an Internal Network Required
Enabling NLSP Routing Required
Configuring NLSP on an Interface Required
sections You can optionally perform the tasks described in the following
Customizing Link Characteristics Optional
Configuring Route Aggregation Optional
Customizing the Exchange of Routing Information Optional
IPX Guide Cisco lOS AppleTalk and Novell Configuration ______P2C 95 Configuring Novell IPX
Configuring NLSP
For of an example enabling NLSP see the IPX Routing Protocols Examples section at the end of this
chapter
Defining an Unterna Network
An internal network number is IPX an network number assigned to the router For NLSP to operate you must configure an internal network number for each device
To enable IPX and to define routing an internal network number use the following commands in global configuration mode
Command Purpose
Step Routerconfig ipx routing Enables IPX routing
Step Routerconfig ipx internal-network network-number Defines an internal network number
Enabaing NLSP Routing
To enable the NLSP use following commands beginning in global configuration mode
Command Purpose
Step Routerconfig ipx router nlsp Enables NLSP
Step Router config-if area-address address mask Defines of set network numbers to be part of the current NLSP area
Configuring NLSP on an Interface
You NLSP and configure differently on LAN WAN interfaces as described in the following sections
Configuring NLSP on LAN Interface Required
Configuring NLSP on WAN Interface Required
Configuring NLSP on LAN Interface
To configure NLSP on LAN interface use the following commands in interface configuration mode
Command Purpose
network network Step Routerconfig-if ipx Enables IPX routing on an interface encapsulation- type
Router Step config-if ipx nlsp tag enable Enables NLSP on the interface
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 96 Configuring Novell IPX
Contiguring NLSP
To configure multiple encapsulations on the same physical LAN interfaces you must configure
subinterfaces Each subinterface must have different encapsulation type To configure subinterfaces
use the following commands beginning in global configuration mode
Command Purpose
Step Router config interface type Specifies subinterface number subinterface -number
network network the first Step Router config-if ipx Enables IPX routing specifying encapsulation-type encapsulation type
Step Routerconfig-if ipx niep enable Enables NLSP on the subinterface
Repeat these three steps for each subinterface
Note When enabling NLSP and configuring multiple encapsulations on the same physical LAN subinterfaces cannot networks interface you must use You use secondary
Configuring NLSP on WAN Interface
the commands in To configure NLSP on WAN interface use following beginning global configuration mode
Command Purpose
number Step Router config interface serial Specifies serial interface
Step Routerconfig-if ipx ipxwan unnumbered Enables IPXWAN local-server-name retry-interval retry-limit
enable Step Routerconfig-if4 ipx nlsp Enables NLSP on the interface
Customizing Link Characteristics
You might want to customize the NLSP link characteristics The following sections describe these customization tasks
Enabling NLSP Multicast Addressing Optional
Configuring the Metric Value Optional
Configuring the Link Delay and Throughput Optional
Configuring the Maximum Hop Count Optional
Specifying Designated Router Optional
Configuring Transmission and Retransmission Intervals Optional
Modifying LSP Parameters Optional
Limiting Partial Route Calculations Optional
Enabling NLSP Multicast Addressing
of multicast for Token and router Cisco lOS supports the use NLSP addressing Ethernet Ring FDDI
interfaces This capability is only possible when the underlying Cisco hardware device or driver supports
multicast addressing
Guide Cisco lOS AppleTalk and Novell IPX Configuration P2C 97 Configuring Novell LJ Configuring NLSP
With this the feature router defaults to using multicasts on Ethernet Token Ring and FDDI interfaces instead of broadcasts to address all NLSP routers on the network If an adjacent neighbor does not
support NLSP multicasting the router will revert to using broadcasts on the affected interface
This feature is only available on routers running Cisco lOS software Release 11.3 or later When routers
running prior versions of Cisco lOS software are present on the same network with routers running Cisco lOS Release 11.3 software broadcasts will be used on any segment shared by the two routers
The NLSP multicast addressing offers the following benefits
Increases overall efficiency and performance by reducing broadcast traffic
Reduces CPU cycles on devices that use NLSP multicast addressing
Increases the Cisco level of compliance with the Novell NLSP specification version 1.1
NLSP Multicast Addressing
By default NLSP multicast addressing is enabled You need not configure anything to turn on NLSP
multicasting
do Typically you not want to substitute broadcast addressing where NLSP multicast addressing is available NLSP multicast addressing uses network bandwidth more efficiently than broadcast
addressing However there are circumstances where you might want to disable NLSP multicast addressing
For example you might want to disable NLSP multicast addressing in favor of broadcast addressing when one or more devices on segment do not support NLSP multicast addressing You might also want disable to it for testing purposes
If to disable multicast do for the entire you want NLSP addressing you can so router or for particular interface
To disable multicast addressing for the entire router use the following commands in IPX-router
configuration mode
Command Purpose
Step Router config-ipx--router router ipx niap Enters NLSP router configuration mode
Router no multicast Step config-ipx-router Disables NLSP multicast addressing on the router
To disable multicast addressing on particular router interface use the following command in interface
configuration mode
Command Purpose
Router config-if no ipx niep multicast Disables multicast addressing on the interface
For examples of how to disable NLSP multicast addressing see the NLSP Multicast Addressing Examples section at the end of this chapter
Configuring the Metric Value
NLSP default link assigns cost metric based on the link throughput If desired you can set the link cost manually
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 98 Configuring Novell IPX
Configuring NLSP
Typically you need not set the link cost manually however there are some cases where you might want to For example in highly redundant networks you might want to favor one route over another for certain kinds of traffic As another example you might want to ensure load sharing Changing the metric value
can help achieve these design goals
To set the NLSP link cost for an interface use the following command in interface configuration mode
Command Purpose
Router conf ig-if ipx nlsp metric Sets the metric value for an interface metric-number
Configuring the Link Delay and Throughput
The delay and throughput of each link are used by NLSP as part of its route calculations By default these parameters are set to appropriate values or in the case of IPXWAN are dynamically measured
Typically you need not change the link delay and throughput however there are some cases where you might want to change these parameters For example in highly redundant networks you might want to favor one route over another for certain kinds of traffic To favor one route over another you would the change metric on the less-desirable path to be slightly worse by assigning it higher metric value the using ipx-link-delay command In this case traffic is forced to route over the favorable path As another example you might want to ensure load sharing To load share you would ensure that the metrics on the equal paths are the same
The link delay and throughput you specify replaces the default value or overrides the value measured by
IPXWAN when it starts The value is also supplied to NLSP for use in metric calculations
To change the link delay use the following command in interface configuration mode
Command Purpose
Router conf ig-if ipx link-delay microseconds Specifies the link delay
To change the throughput use the following command in interface configuration mode
Command Purpose
Routerconfig-if ipx throughput bits-per-second Specifies the throughput
Configuring the Maximum Hop Count
By default IPX packets whose hop count exceeds 15 are discarded In larger internetworks this
maximum hop count may be insufficient You can increase the hop count to maximum of 127 hops for NLSP
For example if you have network with end nodes separated by more than 15 hops you can set the
maximum number of hops considered to be reachable by non-RIP routing protocols to value from 16
to 127
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 99 Configuring Novell IPX Configuring NLSP
To the maximum modify hop count use the following command in global configuration mode
Command Purpose
Router config ipx maximum-hops hop Sets the maximum number of hops of an IPX packet reachable by
non-RW routing protocols Also sets the maximum number of
routers that an IPX packet can traverse before being dropped
Specifying Designated Router
Note In the context of this discussion the term designated router can refer to an access server or router
elects router each NLSP designated on LAN interface The designated router represents all routers that
are connected to the same LAN segment It creates virtual router called apseudonode which generates information behalf of the routing on LAN and sends it to the remainder of the routing area The routing information includes generated adjacencies and RIP routes The use of designated router substantially reduces the number of entries in the LSP database
By default electing designated router is done automatically However you can manually affect the of the identity designated router by changing the priority of the system the system with the highest
priority is elected to be the designated router
the of the By default priority system is 44 To change this priority use the following command in
interface configuration mode
Command Purpose
Routerconfig-if ipx niap priority priority-number Configures the designated router election priority
Configuring Transmission and Retransmission Intervals
You can configure the hello transmission interval and time holding multiplier the complete sequence number transmission PDU CSNP interval the LSP transmission interval and the LSP retransmission interval
The hello transmission interval and time used holding multiplier together determine how long
should wait after link failure neighboring system or system the holding time before declaring this
to be unreachable The time is the hello system holding equal to transmission interval multiplied by the holding time multiplier
To the hello configure transmission interval on an interface use the following command in interface
configuration mode
Command Purpose
Router config-if ipx nlsp tag 325 seconds Configures the hello transmission interval
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 100 Configuring Novell IPX
Configuring NLSP
To the time specify holding multiplier used on an interface use the following command in interface configuration mode
Command Purpose Routerconfig-if ipx nlsp hello-multiplier Configures the hello multiplier multiplier
not Although typically necessary you can configure the CSNP transmission interval To configure the the CSNP interval use following command in interface configuration mode
Command Purpose Routerconfig-if ipx nlsp camp-interval seconds Configures the CSNP transmission interval
You can specify how fast LSPs can be flooded out an interface by configuring the LSP transmission
interval To configure the LSP transmission interval use the following command in interface
configuration mode
Command Purpose Router config-if ipx nlsp lsp-interval Configures the LSP transmission interval interval
You can set the maximum of time amount that can pass before an LSP will be resent on WAN link when
no acknowledgment is received To configure this LSP retransmission interval use the following
command in interface configuration mode
Command Purpose
Routerconfig-if ipx retransmit-interval nlsp Configures the LSP retransmission interval seconds
Modifying ISP Parameters
To modify LSP parameters use one or more of the following commands in router configuration mode
Command Purpose
Router config-router lsp-gen-interval seconds Sets the minimum LSP generation interval
Router conf ig-router max-lap-lifetime value Sets the maximum time the LSP persists
Routerconfig-routerj lap-refresh-interval seconds Sets the LSP refresh time Routerconfig-router lsp-mtu bytes Sets the maximum size of an LSP
Router config-router spf-interval seconds Sets the minimum time between SPF calculations
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C-1 01 Configuring Novell lPj Configuring NLSP
Limitinq Partial Route Calculations
You can control how often the Cisco lOS software route calculation performs partial PRC Because the partial route calculation is processor-intensive it may be useful to limit how often this calculation is
done especially on slower router models Increasing the PRC interval reduces the processor load of the
router but it also potentially slows down the rate of convergence
To modify the PRC use the following command in router configuration mode
Command Purpose
Router config-router prc-interval seconds Sets the hold-down period between partial route calculations
Configuring Route Aggregation
Prior to Cisco lOS Release 11.1 you could segregate IPX internetworks into distinct NLSP areas only them with IPX 1UP by interconnecting With Release 11.1 or later software you can easily perform the
following tasks
Divide large IPX internetworks into multiple NLSP areas
Redistribute route and service information directly from one NLSP area into other areas
Enable route summarization
In this these document independent capabilities are known collectively as the route aggregation feature
Cisco has designed the route aggregation feature to be compatible with the Novell NetWare Link Services
Protocol NLSP Specification Revision 1.1 publication
Note In the sections that follow NLSP version 1.1 routers refer to routers that support the route
aggregation feature while NLSP version 1.0 routers refer to routers that do not
Additionally all NLSP instances configured on router running Release 11.1 are NLSP 1.1
instances They are all capable of generating and using aggregated routes However in the
text and examples that follow an NLSP 1.0 instance refers to an instance of NLSP that
is in an area that includes NLSP version 1.0 routers
Understanding Area Addresses Route Summaries and Aggregated Routes
This section discusses area addresses route summaries and aggregated routes It also describes how area
addresses relate to route summaries
Area Addresses
An area address uniquely identifies an NLSP area The area addresses configured on each router
determine the areas to which router belongs
An area address consists of pair of 32-bit hexadecimal numbers that include an area number and
corresponding mask The mask indicates how much of the area number identifies the area and how much
identifies individual networks in the area For example the area address pair 12345600 FFFFFFOO
describes an area composed of 256 networks in the range 12345600 to 123456FF
You can to three addresses configure up area per NLSP process on the router Adjacencies are formed only between routers that share at least one common area address
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 102 Configuring Novell IPX
Configuring NLS
Route Summaries
route summary defines set of explicit routes that the router uses to generate an aggregated route
route summary tells the router how to summarize the set of explicit routes into single summarized route
route summary is similar in form to an area address That is the route summary described by
12345600 FFFFFFOO summarizes the 256 networks in the range 12345600 to 123456FF
Aggregated Routes
numbers An aggregated route is the single compact data structure that describes many IPX network In simultaneously The aggregated route represents all the explicit routes defined by the route summary in of the an LSP the router expresses an aggregated route as 1-byte number that gives the length bits
portion of the 32-bit network number common to all summarized addresses The aggregated route for
12345600 FFFFFFOO is 18 12345600
Relationship Between Area Addresses and Route Summaries
When you enable route summarization in Cisco lOS Release 11.1 while running multiple instances of
NLSP the router performs default route summarization based on the area address configured in each
NLSP area That is explicit routes that match the area address in given area are not redistributed route that individually into neighboring NLSP areas Instead the router redistributes single aggregated
is equivalent to the area address into neighboring areas
Understanding NLSP Areas
This section describes single versus multiple NLSP areas and discusses the behavior of the router when
you mix NLSP versions within single NLSP area
Single Versus Multiple NLSP Areas
if NLSP version 1.0 routers support only single Level area Two routers form an adjacency only they in share at least one configured area address in common The union of routers with adjacencies common form an area
Each router within the NLSP area has its own adjacencies link-state and forwarding databases Further
the link-state database of each router is identical Within the router these databases operate collectively and information about the area NLSP as single process or instance to discover select maintain route
version 1.0 routers and NLSP version 1.1 routers that exist within single area use single NLSP
instance
With NLSP version 1.1 and Cisco lOS Release 11.1 multiple instances of NLSP may exist on given Each router Each instance discovers selects and maintains route information for separate NLSP area
for its all instance has its own copy of the NLSP adjacency and link-state database area However of instances along with other routing protocols such as RIP and Enhanced IGRP share single copy the forwarding table
Mixing NLSP Versions in Single Area
You can have NLSP version 1.1 routers and NLSP version 1.0 routers in the same area However NLSP of Cisco lOS version 1.0 routers do not recognize aggregated routes For this reason the default behavior mixed Release 11.1 software is to not generate aggregated routes To prevent routing loops in if the environment packets routed via an aggregated route by an NLSP version 1.1 router are dropped next hop is an NLSP version 1.0 router
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 103 Configuring Novell
Configuring NLSP
Note In general you should ensure that all routers in an area are running NLSP version
1.1-capable software before you enable route summarization on any of the routers in an area
Understanding Route Redistribution
Because can you configure multiple NLSP areas you must understand how the router passes route information from one area to another Passing route information from one area to another or from one
protocol to another is known as route redistribution Additionally you must understand the default route
redistribution behavior of the router before configuring route summarization
This section describes the default route redistribution behavior between multiple NLSP areas between NLSP and Enhanced IGRP and between NLSP and RIP
Default Redistribution Between Multiple NLSP Areas
of the Regardless NLSP version Cisco lOS Release 11.1 redistributes routes between multiple NLSP default That areas by is redistribution between multiple NLSP version 1.1 areas between multiple NLSP version 1.0 areas and between NLSP version 1.1 and NLSP version 1.0 areas is enabled by default All routes are redistributed as individual explicit routes
Default Redistribution Between NLSP and Enhanced IGRP
Route redistribution between instances of NLSP version 1.1 or version 1.0 and Enhanced IGRP is disabled default You by must explicitly configure this type of redistribution See the Redistributing
Information section later in Routing this chapter for information about configuring redistribution between NLSP and Enhanced IGRP
Default Redistribution Between NLSP and RIP
Route redistribution between instances of NLSP version 1.1 or version 1.0 and RIP is enabled by default All routes are redistributed as individual explicit routes
Understanding Route Summarization
Route summarization is disabled by default to avoid the generation of aggregated routes in an area mixed versions running of NLSP You can explicitly enable route summarization on router running Cisco lOS Release 11.1 This section describes default route summarization customized route and the summarization relationship between filtering and route summarization
route NLSP summarization provides the following benefits to well-designed IPX networks
address Compact representationA single aggregated route efficiently represents many explicit routes
Reduced bandwidthMost in the update changes explicit routes represented by an aggregated route need not be propagated to neighboring areas
Reduced computational overheadBecause the routers in one area are unaffected by most changes in adjacent areas the SPF algorithm runs less often
information Improved managementFiltering of route and service information may be done at area boundaries
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 104 guring Novell IPX Configuring NLSP
As result of these benefits you can build larger IPX networks using route aggregation
Default Route Summarization
summarization the When you explicitly enable route summarization the default route depends on
following circumstances
All routers use NLSP version 1.1The area address for each NLSP instance is used as the basis for
generating aggregated routes
Some routers use NLSP version 1.1 and some use NLSP version .0The area address for each
NLSP instance is used as the basis for generating aggregated routes however NLSP version 1.0
routers do not recognize aggregated routes You must not enable route aggregation on the
NLSP version 1.0 instance or you must configure customized route summarization to prevent the Customized generation of aggregated routes from the NLSP version 1.0 areas See Route
Summarization section later in this chapter
Some routers use Enhanced IGRP and NLSP version 1.1There is no default route summarization from Enhanced You must configure customized route summarization to generate aggregated routes
later in this IGRP to NLSP version 1.1 See the Customized Route Summarization section chapter
Some routers use RIP and NLSP version 1.1There is no default route summarization You must
configure customized route summarization to generate aggregated routes from RIP to NLSP
version 1.1 See the Customized Route Summarization section later in this chapter
In the case of the first two circumstances the area address for each NLSP instance is used as the basis
for generating aggregated routes That is all explicit routes that match local area address generate
common aggregated route The router redistributes only the aggregated route into other NLSP areas
explicit routes and more specific aggregated routes represented by particular aggregated route are
filtered
match Note The router continues to redistribute into other areas the explicit routes that do not
the area address
Customized Route Summarization
You can also customize the route summarization behavior of the router using the redistribute IPX-router
subcommand with an access list The access list specifies in detail which routes to summarize and which
routes to redistribute explicitly In this case the router ignores area addresses and uses only the access numbered named list as template to control summarization and redistribution You can use or access
lists to control summarization and redistribution
In addition you must use customized route summarization in environments that use either of the
following combinations
Enhanced IGRP and NLSP version 1.1
RIP and NLSP version 1.1
Route summarization between Enhanced IGRP and NLSP is controlled by the access list Route redistributed from summarization is possible only in the Enhanced IGRP-to-NLSP direction Routes
NLSP to Enhanced IGRP are always explicit routes
Route summarization between RIP and NLSP is also controlled by the access list Route summarization
is possible only in the RIP-to-NLSP direction Routes redistributed from NLSP to RIP are always maximize explicit routes Use the default route instead to minimize routing update overhead yet
reachability in RIP-only area
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 105 Configuring Novell IPXJ Configuring NLSP
Note Before introducing the default route into RIP-only area be sure that all routers and
servers in the area are upgraded to understand and use the default route
In well-designed network within each NLSP area most external networks are reachable by few
while all other external networks aggregated routes are reachable either by individual explicit routes or by the default route
Relationship Between Filtering and Route Summarization
Redistribution of and routes services into and out of an NLSP area may be modified using filters Filters available for both are input and output directions Refer to the distribute-list in distribute-list out and out commands in the Novell distribute-sap-list in distribute-sap-list IPX Commands chapter in the Cisco lOS AppleTalk and Novell IPX Command Reference publication
is of Filtering independent route summarization but may affect it indirectly because filters are always before the applied aggregation algorithm is applied It is possible to filter all explicit routes that could
generate aggregated routes making the router unable to generate aggregated routes even though route aggregation is turned on
Understanding Service and Path Selection
The router service always accepts information as long as the network of the service is reachable by an explicit route an aggregated route or the default route When server for Get Nearest Server GNS is the tick value response chosen of the route to each eligible server is used as the metric No distinction is made between explicit and summary routes in this determination If the tick values are equal then the
hop count is used as tiebreaker because there is value However no hop associated with an aggregated route services reachable via an route those explicit are always preferred over reachable via only an aggregated route
version 1.1 An NLSP router always uses the most explicit match to route packets That is the router
uses an route if If then always explicit possible not matching aggregated route is used If multiple
aggregated routes match then the most explicit longest match is used If no aggregated route is present
then the default route is used as last resort
Route Aggregation Configuration Task List
To the route configure aggregation feature perform one or more of the task in the following sections
Configuring Route Aggregation for Multiple NLSP Version 1.1 Areas Optional
Configuring Route Aggregation for NLSP Version 1.1 and NLSP Version 1.0 Areas Optional
Route Configuring Aggregation for Enhanced IGRP and NLSP Version 1.1 Environments Optional
Configuring Route Aggregation for RIP and NLSP Version 1.1 Environments Optional
Configuring Route Aggregation for Multiple NLSP Version 1.1 Areas
Redistribution between multiple NLSP 1.1 areas is enabled by default Because multiple NLSP the processes are present on router tag or label identifies each For each instance configure an address appropriate area and optionally enable route summarization Enable NLSP on appropriate
interfaces Be sure to use the correct tag process identifier to associate that interface with the
appropriate NLSP area
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C-106 Configuring Novell IPX
Configuring NLSP
within the Note Note that the tag used to identify an NLSP instance is meaningful only locally interfaces router NLSP adjacencies and areas are determined by the area address and need than configured for each instance of NLSP running on each router There is no other
administrative convenience to ensure that individual tags match between routers
version The following sections describe how to configure route aggregation for multiple NLSP 1.1 areas
Configuring Route Aggregation with Default Route Summarization
Configuring Route Aggregation with Customized Route Summarization Using Numbered Access Lists
Configuring Route Aggregation with Customized Route Summarization Using Named Access Lists
Configuring Route Aggregation with Default Route Summarization
the To configure the route aggregation feature with the default route summarization behavior use
following commands beginning in global configuration mode for each NLSP process
Command Purpose
Step Router config ipx router nlsp tag Enables NLSP routing and identifies the process with
unique tag
area..addresa address mask defines three Step Router config-router From router configuration mode up to area addresses for the process
Step Router config-router route-aggregation Optional From router configuration mode enables
route summarization
enable enables Step Routerconfig-if ipx nlsp From interface configuration mode NLSP on
each network in the area described by the tag
argument
for For an example of how to configure this type of route aggregation see NLSP Route Aggregation
NLSP Version 1.1 and Version 1.0 Areas Example section at the end of this chapter
Configuring Route Aggregation with Customized Route Summarization Using numbered Access Lists
To configure the route aggregation feature with customized route summarization behavior using
numbered access lists use the following commands beginning in global configuration mode for each
NLSP process
Command Purpose
Step Router config ipx router nlsp tag Enables NLSP routing and identifies the process with
unique tag
Step Router config-router area-address address mask From router configuration mode defines up to three
area addresses for the process
Step Router config-router route-aggregation From router configuration mode enables route summarization
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 107 Configuring Novell IPX
Configuring NLSP
Command Purpose
Router conf ig router 4t redistribute Step nlsp tag From router configuration mode use the redistribute access-list access-list-number command with an access list in the range of 1200 to 1299 this the In case tag argument identifies unique NLSP process
Step Router conf ig- if ipx tag enable nlsp From interface configuration mode enables NLSP on
each network in the area described by the tag argument
Router access-list access-list-number Step config deny From global configuration mode defines the access network network-mask ticks list to redistribute an aggregated route instead of the area-count explicit route For each address range you want to summarize use the deny keyword
Step Router config access-list access-list-number Optional Terminates the access list with permit permit -l all statement to redistribute all other routes as
explicit routes
Configuring Route Aggregation with Customized Route Summarization Using Named Access Lists
To configure the route aggregation feature with customized route summarization behavior using named
access lists use the following commands beginning in global configuration mode for each NLSP
process
Command Purpose
Step Router config ipx router nlsp Enables and identifies NLSP routing the process with unique tag
Router area-address address Step corifig-router mask From router configuration mode defines up to three area addresses for the process
Step Router config-router route-aggregation From router configuration mode enables route summarization
Step Router config-router redistribute nlsp From router configuration mode redistributes NLSP access-list name version 1.0 into the NLSP version 1.1 area In this
case named access list is used and the tag argument identifies unique NLSP process
Step Routerconfig-if enable ipx nlsp From interface configuration mode enables NLSP on each network in the area described by the tag argument
Step Routerconfig ipx access-list name summary From global configuration mode specifies named IPX access list for NLSP route aggregation
Step Router config-access-list deny network network-mask In access-list configuration mode specifies the ticks area-count redistribution of aggregated routes instead of explicit
routes For each address range you want to summarize use deny command
Step Routerconfig-access-list4f -l permit Optional Terminates the access list with permit
all statement to redistribute all other routes as
explicit routes
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 108 Configuring Novell IPX guringNLSP
Configuring Route Aggregation for NLSP Version 1.1 and NLSP Version 1.0 Areas
By default redistribution is enabled between multiple instances of NLSP Route summarization when
is in direction enabled possible one onlyfromNLSP version 1.0 to NLSP version 1.1
The sections following describe how to configure route aggregation for NLSP version 1.1 and NLSP version 1.0 areas
Configuring Route Aggregation with Default Route Summarization
Configuring Route Aggregation with Customized Route Summarization Using Numbered Access Lists
Configuring Route Aggregation with Customized Route Summarization Using Named Access Lists
Configuring Route Aggregation with Default Route Summarization
To the route feature configure aggregation with default route summarization behavior use the following commands in beginning global configuration mode for each NLSP process
Command Purpose Router Step config ipx router nlsp tag Enables and identifies the NLSP routing process with unique tag
Step Router config-router area-address address mask From router configuration mode defines up to three area addresses for the process Router Step config-router route-aggregation For NLSP version 1.1 areas enables route
summarization from router configuration mode Omit
this step for NLSP version 1.0 areas
Step Router conf ig- if enable ipx nlsp tag From interface configuration mode enables NLSP on
each network in the area described by the tag argument
Route with Customized Configuring Aggregation Route Summarization Using Numbered Access Lists
To configure the route aggregation feature with customized route summarization behavior using
numbered access lists use the commands in the following two tables
For the version 1.1 the NLSP process use following commands beginning in global configuration mode
Command Purpose
Router conf ig ipx router nlsp Enables NLSP routing and identifies the process with unique tag
Step Routerconfig-router area-address address mask From router configuration mode defines up to three area addresses for the process
Step Router config-router route-aggregation From router configuration mode enables route
summarization for NLSP version 1.1 areas
Step Router config-router redistribute nlsp tag Optional From router configuration mode access-list access-list-number redistributes NLSP version 1.0 into the NLSP
version 1.1 area Include an access list number from
1200 to 1299
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 109 Configuring Novell IPX
Configuring NLSP
Command Purpose
Router conf if enable Step ig- ipx nlsp tag From interface configuration mode enables NLSP on each network in the area described by the tag argument
Router config access-list access-list-number Step deny Optional From global configuration mode defines network network-mask ticks the access list to redistribute an aggregated route area-count instead of explicit routes learned from the NLSP version 1.0 For address area each range you want to summarize use the deny keyword
Router acceas-liat access-list-number Step config Optional From global configuration mode permit -l terminates the access list with permit all
statement to redistribute all other routes as explicit routes
For the NLSP version 1.0 process use the following commands beginning in global configuration mode
Command Purpose
Step Router config ipx router niap tag Enables and identifies the NLSP routing process with unique tag
Step Router config-router area-address address mask From router configuration mode defines up to three area addresses for the process
Router conf if enable Step ig- ipx nlsp tag From interface configuration mode enables NLSP on in each network the area described by the tag argument
For of how an example to configure the route aggregation feature with this type of customized route
summarization see the NLSP Route Aggregation for NLSP Version 1.1 and Version 1.0 Areas
Example section at the end of this chapter
Route with Configuring Aggregation Customized Route Summarization Using Named Access Lists
To configure the route aggregation feature with customized route summarization behavior using named
access lists use the commands in the following two tables
For the version 1.1 NLSP process use the following commands beginning in global configuration mode
Command Purpose Router Step config ipx router nlsp tag Enables and identifies the NLSP routing process with unique tag
Step Router config-router area-address address mask From router configuration mode defines up to three area addresses for the process Router Step config-router route-aggregation From router configuration mode enables route
summarization for NLSP version 1.1 areas
Step Router conf ig-router redistribute nlsp Optional From router configuration mode access-list name redistributes NLSP version 1.0 into the NLSP
version 1.1 area
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 110 Novell IPX 1guriflg Configuring NLSP
Command Purpose
enable From interface enables NLSP on Step Routerconfig-if ipx nlsp configuration mode each network in the area described by the tag
argument
Router access list name From StepS config ipx summary Optional global configuration mode specifies named IPX access list for NLSP route aggregation
Router config-access-list deny network network-mask From access-list configuration Step Optional mode
ticks area-count defines the access list to redistribute an aggregated
route instead of explicit routes learned from the
NLSP version 1.0 area For each address range you
want to summarize use deny statement
Router -l access-list Step config-access-list permit Optional From configuration mode terminates the access list with permit all
statement to redistribute all other routes as explicit
routes
in For the NLSP version 1.0 process use the following commands beginning global configuration mode
Command Purpose
and identifies the with Step Router config ipx router nlsp tag Enables NLSP routing process unique tag
three Step Router config-router area-address address mask From router configuration mode defines up to area addresses for the process
enable enables on Step Router config-if ipx nlsp tag From interface configuration mode NLSP
each network in the area described by the tag
argument
Configuring Route Aggregation for Enhanced IGRP and NLSP Version 1.1 Environments
in the Enhanced IGRP Redistribution is not enabled by default Additionally summarization is possible
to NLSP direction only
IGRP and The following sections describe how to configure route aggregation for Enhanced NLSP
version 1.1 environments
Configuring Route Aggregation Using Numbered Access Lists
Configuring Route Aggregation Using Named Access Lists
Guide Cisco lOS AppleTalk and Novell IPX Configuration P2C 111 Configuring Novell IPX
Configuring NLSP
Configuring Route Aggregation Using Numbered Access Lists
For each NLSP version 1.1 the commands in process use following beginning global configuration mode
Command Purpose
Step Router config ipx router nlsp tag Enables and NLSP routing identifies the process with unique tag
Step Router config-router area-address address mask From router configuration mode defines up to three area addresses for the process
Step Router config-router route-aggregation Optional From router configuration mode enables route summarization
Step Router config-router redistribute Optional From router configuration mode eigrp autonomous-system--number redistributes Enhanced IGRP into the NLSP version access-list-number 1.1 area Include an access list number from 1200 to 1299
Step Router config-if enable ipx nlsp From interface configuration mode enables NLSP on
each network in the area described by the tag argument
Step Router config access-list access-list-number deny Optional From global configuration mode defines network network-mask ticks the access list to redistribute an aggregated route area-count instead of explicit routes learned from Enhanced
IGRP For each address range you want to summarize use the deny keyword
Step Router config access-list access-list-number Optional Terminates the access list with permit permit -1 all statement to redistribute all other Enhanced
IGRP routes as explicit routes
For each Enhanced IGRP autonomous the system use following commands begimiing in global configuration mode
Command Purpose
Step Routerconfig4 ipx router eigrp Enables Enhanced IGRP autonomous -system-number
Step Router config-router network From router configuration mode specifies the network-number all networks to be enabled for Enhanced IGRP
Step Router config-router redistribute nlsp From router configuration mode redistributes NLSP
version 1.1 into Enhanced IGRP
For an of how example to configure this type of route aggregation see the NLSP Route Aggregation for NLSP Version Enhanced 1.1 IGRP and RIP Example section at the end of this chapter
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C-112 Configuring Novell IPX
Configuring NLSP
Configuring Route Aggregation Using Named Access Lists
For each NLSP version 1.1 process use the following commands beginning in global configuration mode
Command Purpose
conf identifies the Step Router ig 4f ipx router nlsp tag Enables NLSP routing and process with
unique tag
area-address address mask defines three Step Router conf ig-router From router configuration mode up to area addresses for the process
Step Router config-router route-aggregation Optional From router configuration mode enables
route summarization
redistribute Step Router config-router eigrp Optional From router configuration mode access-list autonomous-system-number name redistributes Enhanced IGRP into the NLSP
version 1.1 area
Step Routerconfig-if ipx nlsp enable From interface configuration mode enables NLSP on
each network in the area described by the tag
argument
Step Router config ipx access list summary name Optional From global configuration mode specifies
named IPX access list for NLSP route aggregation
Step Router config-access-list deny network network-mask Optional From access-list configuration mode ticks area-count defines the access list to redistribute an aggregated
route instead of explicit routes learned from
Enhanced IGRP For each address range you want to
summarize use deny statement
Step Router conf ig permit -l Optional From global configuration mode terminates the access list with permit all
statement to redistribute all other Enhanced IGRP
routes as explicit routes
For each Enhanced IGRP autonomous system use the following commands beginning in global
configuration mode
Command Purpose
Step Routerconfig ipx router eigrp Enables Enhanced IGRP autonomous-system-number
Step Router config-router network From router configuration mode specifies the
network-number all networks to be enabled for Enhanced IGRP
Step Router config-router redistribute nlsp From router configuration mode redistributes NLSP
version 1.1 into Enhanced IGRP
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 113 Configuring Novell IPX Configuring NLSP
Configuring Route Aggregation for RIP and NLSP Version 1.1 Environments
Because redistribution between RIP and is NLSP enabled by default you only need to enable the route
if all summarization desired to configure the capabilities of the route aggregation feature
The following sections describe how to configure route aggregation for RIP and NLSP version 11 environments
Configuring Route Aggregation Using Numbered Access Lists
Configuring Route Aggregation Using Named Access Lists
For an example of how to configure this type of route aggregation see the NLSP Route Aggregation for NLSP Version 1.1 Enhanced IGRP and RIP Example section at the end of this chapter
Configuring Route Aggregation Using Numbered Access Lists
For each version 1.1 the NLSP process use following commands beginning in global configuration mode
Command Purpose
Step Router config ipx router nlsp tag Enables NLSP routing and identifies the process with unique tag
Step Router config-router area-address address mask From router configuration mode defines up to three area addresses for the process
Step Router config-router route-aggregation Optional From router configuration mode enables route summarization
Step Router config-router redistribute rip Optional From router configuration mode access-list-number redistributes RIP routes into the NLSP version 1.1
area Include an access list number from 1200 to 1299
Step Router config-if enable ipx nlsp From interface configuration mode enables NLSP on each network in the area described by the tag argument
Step Router config access-list access-list-number deny Optional From global configuration mode defines network network-mask ticks the access list to redistribute an aggregated route area-count instead of explicit RIP routes For each address range you want to summarize use the deny keyword
Step Router config access-list access-list-number Optional From global configuration mode permit -l terminates the access list with permit all
statement to redistributes all other RIP routes as
explicit routes
For of how an example to configure this type of route aggregation see the NLSP Route Aggregation for NLSP Version 1.1 Enhanced IGRP and RIP Example section at the end of this chapter
CiscolOS AppleTalk and Novell IPX Configuration Guide P2C 114 Configuring Novell IPX
Configuring NSP
Configuring Route Aggregation Using Named Access Lists
For each NLSP version 1.1 process use the following commands beginning in global configuration mode
Command Purpose
router Step Routerconfig ipx nlBp Enables NLSP routing and identifies the process with unique tag
Router area-address address mask Step config-router From router configuration mode defines up to three area addresses for the process
Step Router config-router route-aggregation Optional From router configuration mode enables
route summarization
Router redistribute access-list Step config-router rip Optional From router configuration mode name redistributes RIP routes into the NLSP version 1.1
area
Step Routerconfig-if ipx nlsp enable From interface configuration mode enables NLSPon
each network in the area described by the tag
argument
Step Routerconfig ipx access-list summary name Optional From global configuration mode specifies
named IPX access list for NLSP route aggregation
Step Routerconfig-access-iist deny network network-mask Optional From access-list configuration mode ticks area-count defines the access list to redistribute an aggregated
route instead of explicit RIP routes For each address
range you want to sununarize use deny statement
Step Router config-access-liat permit -l Optional From access-list configuration mode
terminates the access list with permit all
statement to redistribute all other RIP routes as
explicit routes
Customizing the Exchange of Routing Hnformation
You might want to customize the exchange of routing information The following sections describe
customization tasks
Configuring RIP and SAP Compatibility Optional
Redistributing Routing Information Optional
Configuring RP and SAP Compatibility
RIP and SAP are enabled by default on all interfaces configured for IPX and these interfaces always
respond to RIP and SAP requests When you also enable NLSP on an interface the interface by default
generates and sends RIP and SAP periodic traffic oniy if another RIP router or SAP service is sending
RIP or SAP traffic
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 115 Configuring Novell IPX
Configuring NLSP
To modify the generation of periodic RIP updates on network enabled for NLSP use one of the
following commands in interface configuration mode
Command Purpose
of Routerconfigif ipx niep rip Never generates RIP periodic traffic
Router conf ig-if on ipx flap rip Always generates RIP periodic traffic
Router conf ig- if ipx nlsp tag rip auto Sends RIP traffic if another RIP periodic only router is sending periodic
RIP traffic is the default interfaces This on configured for NLSP
To modify the generation of periodic SAP updates on network enabled for NLSP use one of the
following commands in interface configuration mode
Command Purpose
Routerconfig-if of ipx flap sap Never generates SAP periodic traffic
Routerconfig-if ipx on niap sap Always generates SAP periodic traffic
Router conf ig-if ipx nlsp sap auto Sends SAP periodic traffic only if another SAP service is sending
periodic SAP traffic This is the default on interfaces configured for NLSP
Redstrbutiiuj Routitig Hnformaton
Automatic redistribution of one routing protocol into another provides simple and effective means for IPX networks in building heterogeneous routing protocol environment Redistribution is usually effective enable as soon as you an IPX routing protocol One exception is NLSP and Enhanced IGRP You must configure the redistribution of Enhanced IGRP into NLSP and vice versa
Once enable Enhanced you IGRP and NLSP redistribution the router makes path decisions based on administrative and predefined nonconfigurable distance prevents redistribution feedback loops without via filtering stored external hop count
To enable redistribution of Enhanced IGRP into NLSP and vice versa use the following commands beginning in global configuration mode
Command Purpose
Step Routerconfig ipx router niap Enables NLSP
Step Router config-ipx-router redistribute eigrp From IPX-router configuration mode enables autonomous-system-number redistribution of Enhanced IGRP into NLSP
Step Router config router ipx eigrp From global configuration mode enables Enhanced autonomous-system-nunther IGRP
Step Router config-ipx-router redistribute nlsp From IPX-router configuration mode enables redistribution of NLSP into Enhanced IGRP
For an example of how to enable redistribution of Enhanced IGRP and NLSP see the Enhanced IGRP and NLSP Route Redistribution Example section at the end of this chapter
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 116 Configuring Novell IPX
Configuring Next Hop Resolution Protocol
Configuring Next Hop Resolution Protocol
Protocol to discover the Routers access servers and hosts can use Next Hop Resolution NHRP
addresses of other routers and hosts connected to an NBMA network NHRP provides an Address
Resolution Protocol ARP-like solution that alleviates some NBMA network problems With NHRP
network learn the address of the other systems attached to an NBMA can dynamically NBMA systems of that network These then communicate without traffic to that are part systems can directly requiring use an intermediate hop
For more information on NHRP and the Cisco implementation refer to the Configuring IP Addressing
chapter in the Cisco lOS IF Routing Configuration Guide
NHRP Configuration Task List
the tasks described in the sections The first task is the To configure NHRP perform following required
remaining tasks are optional
Enabling NHRP on an Interface Required
Address Configuring Station with Static IPX-to-NBMA Mapping Optional
Statically Configuring Next Hop Server Optional
Configuring NHRP Authentication Optional
Controlling NHRP Initiation Optional
Controlling NHRP Packet Rate Optional
Suppressing Forward and Reverse Record Options Optional
Specifying the NHRP Responder Address Optional
Changing the Time Period NBMA Addresses Are Advertised As Valid Optional
the end of this For NHRP configuration examples see the NHRP Examples section at chapter
Enabling NHRP on an Interface
To enable NHRP for an interface on router use the following command in interface configuration
mode In general all NHRP stations within logical NBMA network must be configured with the same network identifier
Command Purpose
Routerconfig-if ipx nhrp network-id number Enables NHRP on an interface
the end of this For an example of enabling NHRP see the NHRP Examples section at chapter
Configtiring Station with Static PX-to-NBMA Address Mapping
be with the IPX and To participate in NHRP station connected to an NBMA network must configured address on the medium NBMA addresses of its Next Hop Servers The format of the NBMA depends Ethernet uses you are using For example ATM uses network service access point NSAP address MAC address and SMDS uses an E.164 address
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 117 Configuring NovejJ Configuring Next Hop Resolution Protocol
These Next Hop Servers are most likely the default or routers of the peer station so their IPX addresses obtained are from the network layer forwarding table of the station
If the station is attached to several networks link-layer including logical NBMA networks the station should also be configured to receive routing information from its Next Servers Hop and peer routers so that it can determine which IPX networks are reachable through which link-layer networks To configure static IPX-to-NBMA address mapping on station host or router use the following command in interface configuration mode
Command Purpose
Routerconfig-if ipx nhrp map ipx-address nbmaaddress Configures static IPX-to-NBMA address mapping
Staticafly Configurhig Next Hop Server
Next Hop Server normally uses the network-layer forwarding table to determine where to forward NHRP and to find the packets egress point from an NBMA network Next Hop Server may alternately be statically configured with set of IPX address that prefixes correspond to the IPX addresses of the stations it serves and their logical NBMA network identifiers
To statically configure Next Hop Server use the command in following interface configuration mode
Command Purpose Router config-if 4f ipx nhrp mhe nhs-address Statically configures Next Hop Server
To configure multiple networks that the Next Server Hop serves repeat the ipx nhrp nhs command with the same Next Hop Server address but different IPX network addresses To configure additional Next Hop Servers repeat the ipx nhrp nhs command
Configuriiig NHRP Authetitication
an authentication Configuring string ensures that routers only configured with the same string can communicate using NHRP Therefore if the authentication scheme is be to used the same string must be configured in all devices for configured NHRP on fabric To the specify authentication string for NHRP on an interface use the command in following interface configuration mode
Command Purpose Router config-if ipx nhrp authentication string Specifies an authentication string
Controlling NHRP Initiation
To control when NHRP is initiated of the perform one tasks in the following sections
Triggering NHRP by IPX Packet Optional NHRP Triggering on per-Destination Basis Optional
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 118 Lconfiguring Novell IPX
Configuring Next Hop Resolution PriF
Triggering NHRP by IPX Packet
You can an IPX access list that is used specify to decide which IPX packets trigger the sending of NHRP requests By default all non-NHRP can To limit which packets trigger NHRP requests IPX packets must define trigger NHRP requests you an access list and then apply it to the interface
To define an of the access list use one following commands in global configuration mode
Command Purpose access-list Routerconfig access-list-number deny permit Defines astandardlPXaccess list source-network source-node
Routerconfig access-list access-list-number deny perinit Defines an extendedlPX access list protocol source-node source-node-mask source-node source-network-mask source-node-mask destination-node destination-node-mask destination-node destination-network-mask .destination-node-mask
To the IPX list to the apply access interface use the following command in interface configuration mode
Command Purpose
Router config-if ipx interest access-list-number nhrp Specifies an IPX access list that controls
NHRP requests
Triggering NHRP on per-Destination Basis
By default when the software attempts to send data packet to destination for which it has determined
that NHRP can be it sends used an NHRP request for that destination You can configure the system to wait until number of data specified packets have been sent to particular destination before NHRP is
To the in this attempted configure system way use the following command in interface configuration mode
Command Purpose
Router config-if ipx nhrp use usage-count Specifies how many data packets are sent to destination before NHRP is attempted
ControHling NHRP Packet Rate
By default the maximum rate at which the software sends NHRP packets is packets per 10 seconds The software maintains of per-interface quota NHRP packets whether generated locally or forwarded
that can be sent To this change maximum rate use the following command in interface configuration mode
Command Purpose
Router config-if ipx nhrp mac-send pkt-count every interval Changes the NHRP packet rate per interface
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 119 Configuring Novell IPX
Configuring Next Hop Resolution Protocol
Suppressing Forward and Reverse Record Options
To detect link-layer filtering in NBMA dynamically networks for example SMDS address screens and to provide ioop detection and diagnostic capabilities NHRP incorporates route record in requests and replies The route record contain the options network and link layer addresses of all intermethae Next Servers between Hop source and destination in the forward direction and between destination and source in the reverse direction
By default forward record options and reverse record included in options are NHRP request and reply packets To the use of these use the command in suppress options following interface configuration mode
Command Purpose
Router config-if no ipx nhrp record Suppresses forward and reverse record options
Specifying the NHRP Responder Address
If an NHRP requester wants to know which Next Server Hop generates an NHRP reply packet it can
request that information by the address in its including responder option NHRP request packet The Next Hop Server that the generates NHRP reply packet then complies by inserting its own IPX address in the NHRP The Next Server the reply Hop uses primary IPX address of the specified interface
To which interface the Next specify Hop Server uses for the NHRP responder IPX address use the command in following interface configuration mode
Command Purpose
Router config-jf ipx rthrp responder number bype Specifies which interface the Next Hop Server uses to determine the NHRP responder address
If an NHRP reply packet forwarded Next being by Hop Server contains the IPX address of that Next Hop Server the Next Hop Server generates an NHRP Loop Detected error indication and discards the reply
Changing the Time Period NBMA Addresses Are Advertised As VaJid
You can change the length of time for which NBMA addresses are advertised as valid in positive and negative NHRP In this advertised responses context means how long the Cisco lOS software tells other
routers to keep the addresses it is in providing NHRP responses The default length of time for each response is 7200 seconds To the hours change length of time use the following command in interface configuration mode
Command Purpose
Routerconfig-jf ipx nhrp lioldtime seconds-positive Specifies the number of seconds for which NBMA addresses are advertised as valid in positive or negative NHRP responses
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 120 Configuring Novell IPX
Configuring IPX and SPX over WANi
Configuring IPX and SPX over WANs
You can configure IPX over dial-on-demand routing DDR Frame Relay PPP SMDS and X.25 networks For more information about dial-on-demand routing DDR refer to the Cisco lOS Dial
Technologies Configuration Guide For more information about Frame Relay SMDS and X.25 refer to
the Cisco 105 Wide-Area Networking Configuration Guide
address for this can When you configure IPX over PPP maps are not necessary protocol Also you
enable IPX header compression over point-to-point links to increase available useful bandwidth of the time for interactive of the link link and reduce response uses
You can use fast-switching IPX serial interfaces configured for Frame Relay and SMDS and you can
use fast-switching Subnetwork Access Protocol SNAP-encapsulated packets over interfaces
configured for ATM
Additionally you can configure the IPXWAN protocol
For an example of how to configure IPX over WAN interface see the IPX over WAN Interface Example section at the end of this chapter
Configuring IPX over DDR
client session has been idle IPX sends periodic watchdog keepalive packets from servers to clients after of for approximately minutes On DDR link call would be made every minutes regardless made whether there were data packets to send You can prevent these calls from being by configuring behalf of remote the Cisco lOS software to respond to the watchdog keepalive packets of server on
client clientsometimes referred to as spoofing the server Spoofing makes server view as always the duration connected even when it is not thus reducing the number of available licenses Users can set clean of IPX watchdog spoofing and periodically disable it so that Novelle NetWare servers can up inactive connections
that When configuring IPX over DDR you might want to disable the generation of these packets so
call is made minutes call made minutes is not issue for the other WAN not every every an
protocols because they establish dedicated connections rather than establishing connections only as needed
Use the ipx watchdog-spoof command to enable and set the duration of watchdog spoofing You can
specify the number of consecutive hours spoofing is to stay enabled and the number of minutes spoofing
is to stay disabled The server can clean up inactive connections when spoofing is disabled Be sure that
fast switching and autonomous switching are disabled on the serial interface before using this command
To enable watchdog spoofing use the following command in interface configuration mode
Command Purpose
Router config-if ipx watchdog-Bpoo Enables and sets the duration of watchdog disable-time-minutes spoofing
To keep the serial interface idle when only watchdog packets are being sent refer to the tasks described
in the Deciding and Preparing to Configure DDR chapter of the Cisco 105 Dial Technologies
Configuration Guide For an example of configuring IPX over DDR see the IPX over DDR Example section at the end of this chapter
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 121 Configuring Novell IPX Configuring IPX and SPX over WANs
Configuring SPX Spoof ing over DDR
Sequenced Packet Exchange SPX sends periodic keepalive packets between clients and servers
Similar to IPX watchdog packets these are keepalive packets that are sent between servers and clients after the data has transferred On stopped being pay-per-packet or byte networks these packets can incur
large customer telephone connection charges for idle time You can prevent these calls from being made
the Cisco software to the by configuring lOS respond to keepalive packets on behalf of remote system
When configuring SPX over DDR you might want to disable the generation of these packets so that call has the opportunity to go idle Disabling the generation of packets may not be an issue for the other because establish dedicated WAN protocols they connections rather than establishing connections only as needed
To keep the serial interface idle when only keepalive packets are being sent refer to the tasks described
in the and to Deciding Preparing Configure DDR chapter of the Cisco lOS Dial Technologies Configuration Guide
For an example of how to configure SPX spoofing over DDR see the IPX over DDR Example section
at the end of this chapter
Configuring IPX Header Compression
You IPX header can configure compression over point-to-point links With IPX header compression point-to-point link can compress IPX headers only or the combined IPX and NetWare Core Protocol headers Currently point-to-point links must first negotiate IPX header compression via IPXCP or The Cisco IXPWAN lOS software supports IPX header compression as defined by RFC 1553
For details on header refer configuring IPX compression to the Configuring Medial-Independent PPP and Multilink PPP chapter in the Cisco 105 Dial Technologies Configuration Guide
Configuring the IPXWAN Protocol
The Cisco lOS software supports the IPXWAN protocol as defined in RFC 1634 IPXWAN allows
router that is IPX to via running routing connect serial link to another router possibly from another
manufacturer that is also routing IPX and using IPXWAN
is connection IPXWAN startup protocol Once link has been established IPXWAN incurs little or no overhead
You can use the IPXWAN protocol over PPP You can also use it over HDLC however the devices at both ends of the serial link must be Cisco routers
To serial configure IPXWAN on interface use the following commands in interface configuration mode
Command Purpose
Step Router config-if no ipx network Ensures that you have not configured an IPX network number on the interface
Step Routerconfig-if encapsulation ppp Enables PPP
Step Routerconfig-if ipx ipxwan Enables IPXWAN network-number unnuinbered local -server-name retry-interval retry-limit
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 122 Configuring Novell IPX
Controlling Access to IPX NetworkiR
Command Purpose
Step Routerconfig-if ipx ipxwan error Optionally defines how to handle IPXWAN when
resume shutdown serial link fails
Step Router config-if ipx ipxwan static Optionally enables static routing with IPXWAN Note that the remote site must also use static routing
Contro in Access to IPX Networks
To control access to IPX networks first create access lists and then apply them to individual interfaces
using filters
Types of Access Lists
You can create the following IPX access lists to filter various kinds of traffic
Standard access listRestricts traffic based on the source network number You can further restrict address mask Standard traffic by specifying destination address and source and destination IPX
access lists use numbers from 800 to 899 or names to identify them
Extended access listRestricts traffic based on the IPX protocol type You can further restrict traffic
by specifying source and destination addresses and address masks and source and destination
sockets Extended IPX access lists use numbers from 900 to 999 or names to identify them
SAP access listRestricts traffic based on the IPX SAP type These lists are used for SAP filters
filters Novell lists numbers from 1000 to 1099 or names to and GNS response SAP access use
identify them
IPX NetBIOS access listRestricts IPX NetBIOS traffic based on NetBIOS names not numbers
NLSP route aggregation access listSpecifies in detail which routes to summarize and which routes
to redistribute explicitly For more information about route aggregation see the Configuring Route
Aggregation section earlier in this chapter
Types of Filters
There are more than 14 different IPX filters that you can define for IPX interfaces They fall into the
following six groups
Generic filtersControl which data packets are routed in or out of an interface based on the source
and destination addresses and IPX protocol type of the packet
Routing table filtersControl which RIP updates are accepted and advertised by the Cisco lOS
software and from which devices the local router accepts RIP updates
SAP filtersControl which SAP services the Cisco lOS software accepts and advertises and which
it sends GNS response messages out
IPX NetBIOS filtersControl incoming and outgoing IPX NetBIOS packets
Broadcast filtersControl which broadcast packets are forwarded
and services into and out of an NLSP route aggregation filtersControl the redistribution of routes NLSP area
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 123 Configuring Novell IPX Controlling Access to IPX Networks
Table sunimarizes the filters the access lists they use and the commands used to define the filters in
the first five groups Use the show ipx interfaces command to display the filters defined on an interface For additional information about route aggregation see the Configuring Route Aggregation section
earlier in this chapter
Table IPX Filters
Filter Type Access List Used by Filter Command to Define Filter
Generic filters
Filters inbound or outbound packets based Standard or Extended ipx access-group
on the contents of the IPX network header access -list -number name in out
Routing table filters
Controls which networks are added to the Standard or Extended ipx input-network-filter routing table access-list-number name
Controls which networks are advertised in Standard or Extended ipx output-network- filter routing updates access-list -number name
Controls which networks are advertised in Standard or Extended distribute list access -list -number name out the Enhanced IGRP routing updates sent routing-process out by the Cisco lOS software
Controls the routers from which updates Standard or Extended ipx router-filter are accepted access-list -number name
SAP filters
Filters incoming service advertisements SAP ipx input-sap-filter access-list-number name
Filters outgoing service advertisements 5Jp ipx output sap- filter access-list-number name
Controls the routers from which SAP 5AJ ipx router-sap-filter updates are accepted access-list-number name
Filters list of in servers GNS response SAP ipx output-gns-filter messages access-list-number name
IPX NetBIOS filters
Filters incoming packets by node name IPX NetBIOS ipx netbios input-access-filter host name
Filters incoming packets by byte pattern IPX NetBIOS ipx netbios input-access-filter bytes name
Filters outgoing packets by node name IPX NetBIOS ipx netbios output-access-filter host name
Filters outgoing packets by byte pattern IPX NetBIOS ipx netbios output-access-filter bytes name
Broadcast filters
Controls which broadcast packets are Standard or Extended ipx helper-list access-list-number name forwarded
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 124 Configuring Novell IPX
Controlling Access to IPX Networks
Implementation Considerations
Remember the following information when configuring IPX network access control
Access lists entries are scanned in the order you enter them The first matching entry is used To
improve performance we recommend that you place the most commonly used entries near the beginning of the access list
is defined the end of list unless include an An implicit deny everything entry at an access you explicit
of the list permit everything entry at the end
end For numbered access lists all new entries to an existing list are placed at the of the list You
if have included an cannot add an entry to the middle of list Consequently you previously explicit
be scanned The solution is to delete the access list permit everything entry new entries will never
and reenter it with the new entries
list at the of the list For named access lists all new entries to an existing are placed end You cannot entries the no and add entries to the middle of list However you can remove specific using deny no permit commands rather than deleting the entire access list
lost One lose is when Do not set up conditions that result in packets getting way you can packets network that has lists that device or interface is configured to advertise services on access deny
these packets
them the of You cannot filter SAP packets within an NLSP area You can filter at boundary NLSP
and RIP/SAP areas though restrictions do apply For more information about filtering at these boundaries see the Relationship Between Filtering and Route Summarization section earlier in
this chapter and the Novell NetWare Link Services Protocol NLSP Specification publication
Controlling Access to IPX Networks Task List
sections To control access to IPX networks perform the required tasks in the following
Creating Access Lists Required
Creating Filters Required
Creating Access Lists
If You can create access lists using numbers or names You can choose which method you prefer you
100 lists filter If use use numbers to identify your access lists you are limited to access per type you number of lists filter names to identify your access lists you can have an unlimited access per type
The following sections describe how to perform these tasks
Creating Access Lists Using Numbers Optional
Creating Access Lists Using Names Optional
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 125 Configuring Novell
Controlling Access to IPX Networks
Creating Access Lists Using Numbers
To lists create access using numbers use one or more of the following commands in global configuration mode
Command Purpose
Router config acoess..list access-list -number Defines standard IPX access list using number Generic deny permit source-network routing and broadcast filters use this type of access list
destination-node
Router config access-list access-list-number Defines an extended IPX access list using number Generic deny permit protocol routing and broadcast filters use this type of access list Use the source-node log to access list source-node-mask keyword get logging messages including source-socket violations Specifies time range to restrict when the permit or destination-node deny statement is in effect destination-node-mask destination-socket time-range-nane
Router config access list access-I ist -number Defines SAP filtering access list using number SAP and GNS deny permit network .node response filters use this type of access list node-mask
Once have created you an access list using numbers apply it to the appropriate interfaces using filters described in the as Creating Filters section later in this chapter Applying filter will activate the access list
Creating Access Lists Using Names
IPX named lists allow access you to identify IPX access lists with an alphanumeric string name rather
than number Using IPX named access lists allows to maintain you security by using separate and easily identifiable access list for each user or interface IPX named access lists also remove the limit of
100 lists filter per type.You can configure an unlimited number of the following types of IPX named
access lists
Standard
Extended
SAP
NLSP route aggregation summarization
NetBIOS
If access list with rather you identify your name than number the mode and command syntax are
slightly different
Cisco lOS AppleTalk and Novell IPX Confiquration Guide P2C 126 Configuring Novell IPX
Controlling Access to IPX Networks
Implementation Considerations
Consider the following information before configuring IPX named access lists
not with releases Except for NetBIOS access lists access lists specified by name are compatible
prior to Cisco lOS Release 11 .24F
Access list names must be unique across all protocols
Except for NetBIOS access lists numbered access lists are also available
IPX Named Access List Configuration Task List
lists for route To configure IPX named access standard extended SAP NLSP aggregation
summarization or NetBIOS access lists perform one or more of the tasks in the following sections
Creating Named Standard Access List Optional
Creating Named Extended Access List Optional
Creating Named SAP Filtering Access List Optional
Creating Named NLSP Route Aggregation Access List Optional
Creating NetBIOS Access List Optional
Applying Time Ranges to Access Lists Optional
List Creating Named Standard Access
in To create named standard access list use the following commands beginning global configuration mode
Command Purpose
list Step Router config ipx access-list standard name Defines standard IPX access using name
Generic routing and broadcast filters use this type
of access list
Step Router config-acceas-list deny permit In access-list configuration mode specifies one or source-node source-network more conditions allowed or denied This determines destination-node whether the packet is passed or dropped
Step Router config exit Exits access-list configuration mode
Named Access List For an example of creating named standard access list see the Standard
Example section at the end of this chapter
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 127 Configuring Novell IPX Controlling Access to IPX Networks
Creating Named Extended Access List
To create named extended access use the commands list following beginning in global configuration mode
Command Purpose
Stepi Routerconfig ipx access-list extended name Defines an extended IPX access list using name and Generic routing broadcast filters use this type of access list
Step2 Routerconfig-access-list deny permit protocol In access-list configuration mode specifies the source-node-mask conditions allowed or denied Use the log keyword to
access list source-network-mask source-node-mask get logging messages including source-socket violations Specifies time range to restrict when the
destination-node-mask permit or deny statement is in effect ion -node destination-network-mask destination nodemask time-range-name
Step Router config exit Exits access-list configuration mode
Creating Named SAP Filtering Access List
To create named access list for the filtering SAP requests use following commands beginning in global configuration mode
Command Purpose Router Step config ipx access-list sap name Defines SAP filtering access list using name SAP GNS and Get General Service GGS response filters use this type of access list
Step Router config-access-list deny permit network In access-list configuration mode specifies the node node -mask type conditions allowed or denied server-flame
Step Router config exit Exits access-list configuration mode
Creating Named NLSP Route Aggregation Access List
route NLSP aggregation access lists perform one of the following functions
Permit networks be to redistributed as explicit networks without sunnnarization
the redistribution of networks Deny explicit and generate an appropriate aggregating summary route for redistribution
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 128 Configuring Novell IPX
Controlling Access to IPX Networks
To create named access list for NLSP route aggregation use the following commands beginning in
global configuration mode
Command Purpose
list NLSP Step Router config ipx access-list summary name Defines an IPX access for route
aggregation using name
network the Step Routerconfig-access-list deny permit In access-list configuration mode specifies network-mask ticks area-count conditions allowed or denied For each address range
you want to redistribute as single aggregated route use the deny keyword For each address that you want
to redistribute explicitly use the permit keyword
Step Router config exit Exits access-list configuration mode
the tasks listed For information on how to use named access list when configuring route aggregation see
in the Route Aggregation Configuration Task List section earlier in this chapter
Creating NetBIOS Access List
in To create NetBIOS access list use one or more of the following commands global configuration mode
Command Purpose
Routerconfig netbios access-list host name deny permit string Creates an access listforfiltering IPX node NetBIOS packets by name NetBIOS filters use this type of access list
Routerconfig netbios access-list bytes name deny permit offset Creates an access listforfilteringlPX
byte-pattern NetBIOS packets by arbitrary byte
filters this of pattern NetBIOS use type
access list
Modifying IPX Named Access Lists
After create access additions possibly entered from the you initially an list you place any subsequent cannot add access list command lines to terminal at the end of the list In other words you selectively
and no commands to remove the middle of specific access list However you can use no permit deny
entries from named access list
list contains Note When creating access lists remember that by default the end of the access an
if it did find match before the end implicit deny statement for everything not reaching
section at the end For an example of creating generic filter see the IPX Network Access Examples
of this chapter
Applying Named Access Lists to Interfaces
interface filters as described in After creating an access list you must apply it to the appropriate using list the Creating Filters section later in this chapter Applying filter will activate the access
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 129 Configuring Novell IPX Controlling Access to IPX Networks
Applying Time Ranges to Access Lists
It is now to possible implement access lists based on the time of day and week using the time-range command To do first define the so name of the time range and times of the day and week then reference
the time in list range by name an access to apply the restrictions of the time range to the access list
Currently IP and IPX named or numbered extended access lists are the only functions that can use time ranges The time range allows the network administrator to define when the permit or deny statements
in the list in effect Prior access are to this time range feature access list statements were always in effect once they were applied The time-range keyword and argument are referenced in the named and numbered extended access list task tables in the previous sections Creating Access Lists Using Numbers and Access Creating Lists Using Names The time-range command is configured in the Basic Performing System Management chapter of the Cisco lOS Configuration Fundamentals Configuration Guide See the IPX Network Access section the end Examples at of this chapter for configuration example of IPX time ranges
There are many possible benefits of time ranges such as the following
The network administrator has more control over permitting or denying user access to resources These resources could be an IP address/mask application identified by an pair and port number
policy routing or an on-demand link identified as interesting traffic to the dialer
Network administrators can set time-based security policy including
Perimeter security using the Cisco lOS Firewall feature set or access lists
Data confidentiality with Cisco Encryption Technology or IPS
Policy-based routing and queueing functions are enhanced
When access rates time provider vary by of day it is possible to automatically reroute traffic cost effectively
Service providers can committed rate dynamically change access CAR configuration to support the of service Service quality QoS Level Agreements SLAs that are negotiated for certain times of day
Network administrators can control logging messages Access list entries can log traffic at certain times of the day but not constantly Therefore administrators can simply deny access without needing to analyze many logs generated during peak hours
Creating Filters
Filters allow to control which you traffic is forwarded or blocked at the interfaces of the router Filters
apply specific numbered or named access lists to interfaces
To create the filters perform tasks in the following sections
Creating Generic Filters Optional
Creating Filters for Updating the Routing Table Optional
Creating SAP Filters Optional
Creating GNS Response Filters Optional
Creating OGS Response Filters Optional
Creating IPX NetBIOS Filters Optional
Creating Broadcast Message Filters Optional
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 130 Configuring Novell IPX Controlling Access to IPX Networks
Creating Generic Filters
based Generic filters determine which data packets to receive from or send to an interface on the source socket numbers and destination addresses IPX protocol type and source and destination of the packet
standard extended access list as described in the To create generic filters first create or an Creating interface Access Lists section earlier in this chapter and then apply filter to an
the command in interface To apply generic filter to an interface use following configuration mode
Command Purpose
interface Routerconfig-if ipx acceas-group Applies generic filter to an access-hat-number name out
filter interface or subinterface You cannot You can apply only one input filter and one output per
is configure an output filter on an interface where autonomous switching already configured Similarly interface where filter is you cannot configure autonomous switching on an an output already present if is on You cannot configure an input filter on an interface autonomous switching aheady configured
filters if is enabled any interface Likewise you cannot configure input autonomous switching already on any interface
Network Access section at the end For an example of creating generic filter see the IPX Examples
of this chapter
Creating Filters for Updating the Routing Table
for its Routing table update filters control the entries that the Cisco lOS software accepts routing table
and the networks that it advertises in its routing updates
extended list To create filters to control updating of the routing table first create standard or an access
section earlier in this and then one or more as described in the Creating Access Lists chapter apply
routing filters to an interface
of the commands in To apply routing table update filters to an interface use one or more following
interface configuration or router configuration mode
Command Purpose
added the table Routerconfig-if ipx input-network-filter Controls which networks are to routing received access-hist--number name when IPX routing updates are
Routerconfig-if ipx output-network-filter Controls which networks are advertised in RIP routing access-hist-number name Cisco lOS software updates sent out by the
Controls which networks are advertised in the Enhanced Router config-router 4t diatribute-lit out the Cisco lOS software access-list-number name IGRP routing updates sent out by routing-process
Routerconfg-if ipx router-filter Controls the routers from which routing updates are
access-hist-number name accepted
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 131 Configuring Novell IPX
Controlling Access to IPX Networks
Note The ipx output-network-filter command applies to the IPX RIP only To control the of when advertising routes filtering routing updates in Enhanced IGRP use the distribute-list out command See the Controlling the Advertising of Routes in Routing Updates section earlier in this chapter for more information
Creat ig SAP Filters
common of traffic source on Novell networks is SAP messages which are generated by NetWare servers and the Cisco lOS software when they broadcast their available services
To control how SAP from messages network segments or specific servers are routed among IPX first create networks SAP filtering access list as described in the Creating Access Lists section
earlier in this chapter and then apply one or more filters to an interface
To filters to apply SAP an interface use one or more of the following commands in interface
configuration mode
Command Purpose Router config-if ipx input-sap-filter Filters incoming service advertisements access-list -nuneer name
Router config-if ipx output-sap-filter Filters outgoing service advertisements access-list-number name
Router conf ig- if ipx router-sap- filter Filters service advertisements received from particularrouter access-ljst-nunther name
You can apply one of each SAP filter to each interface
For of and examples creating applying SAP filters see the SAP Input Filter Example and SAP Output Filter Example sections at the end of this chapter
Creating GNS Response Filters
To create filters for controlling which servers are included in the GNS responses sent by the Cisco lOS software first create SAP filtering access list as described in the Creating Access Lists section earlier in this and chapter then apply GNS filter to an interface
To apply GNS filter to an interface use the command in following interface configuration mode
Command Purpose Router config-if ipx output-gns-filter Filters the list of in servers GNS response messages access-list-number name
Creating GGS Response Filters
To create filters for controlling which servers are included in the Get General Service GGS responses sent the Cisco by lOS software first create list SAP filtering access as described in the Creating Access Lists section earlier in this chapter and then apply GGS filter to an interface
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 132 Configuring Novell IPX
Controlling Access to IPX Networks
ahead of SAP Note Because GGS SAP response filters are applied output SAP filters entry
filter still be filtered the permitted to pass through the GGS SAP response can by output
SAP filter
the command in interface To apply GGS filter to an interface use following configuration mode
Command Purpose
Routerconfig-if ipx output-gga-eilter Filters the list of servers in GOS response messages
Network Access section For an example of creating GGS SAP response filter see the IPX Examples
at the end of this chapter
Creating IPX NetBIOS Filters
The Novell IPX NetBIOS allows messages to be exchanged between nodes using alphanumeric names and node addresses Therefore the Cisco lOS software lets you filter incoming and outgoing NetBIOS the node in the FindName packets by the node name or by an arbitrary byte pattern such as address packet
have no effect on Note These filters apply to IPX NetBIOS FindName packets only They Logic
Link Control type LLC2 NetBIOS packets
Implementation Considerations
control Remember the following when configuring IPX NetBIOS access
Host node names are case sensitive
have the because the two of lists are independent Host and byte access lists can same names types of each other
with the destination When nodes are filtered by name the names in the access lists are compared
name field for IPX NetBIOS find name requests
the transmission rate Access filters that filter by byte offset can have significant impact on packet should these access lists when absolutely because each packet must be examined You use only
necessary
default action is to If node name is not found in an access list the deny access
Configuring IPX NeIBIOS Filters
NetBIOS list as described in To create filters for controlling IPX NetBIOS access first create access
the list to an interface the Creating Access Lists section earlier in this chapter and then apply access
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 133 Configuring Novell IPXJ Controlling Access to IPX Networks
To NetBIOS list apply access to an interface use one or more of the following commands in interface configuration mode
Command Purpose
Router config-if ipx netbios Filters incoming packets by node name input-access-filter host name
Router config-if ipx netbios Filters incoming packets by byte pattern input-access-filter bytes name
Router configif ipx netbios Filters outgoing packets by node name output-access-filter host name
Routerconfig-if ipx netbios Filters outgoing packets by byte pattern output-access-filter bytes name
You can apply one of each of these four filters to each interface
of to For an example how create filters for controlling IPX NetBIOS see the IPX NetBIOS Filter Examples section at the end of this chapter
Creating Broadcast Message Filters
Routers block all broadcast and normally requests do not forward them to other network segments therefore preventing the degradation of performance inherent in broadcast traffic over the entire network You can define which broadcast messages get forwarded to other networks by applying broadcast message filter to an interface
To create filters for controlling broadcast messages first create standard or an extended access list as described in the Access Creating Lists section earlier in this chapter and then apply broadcast message filter to an interface
To broadcast apply message filter to an interface use the following commands in interface configuration mode
Command Purpose
Step Routerconfig-if ipx helper-address network.node Specifies helper address for forwarding broadcast messages
Step Router config-if ipx helper-list Applies broadcast message filter to an interface access-hat-number name
S4
Note broadcast filter has effect message no unless you have issued an ipx helper-address or
an ipx type-20-propagation command on the interface to enable and control the
of broadcast These forwarding messages commands are discussed later in this chapter
For of and examples creating applying broadcast message filters see the Helper Facilities to Control Broadcast Examples section at the end of this chapter
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 134 Configuring Novell IPX
Controlling Access to IPX NetworksU
Tuning IPX Network Performance
To tune IPX network performance perform the tasks in one or more of the following sections
Controlling Novell IPX Compliance Optional
Adjusting RIP and SAP Information Optional
Configuring Load Sharing Optional
Specifying the Use of Broadcast Messages Optional
Disabling IPX Fast Switching Optional
Adjusting the Route Cache Optional
Adjusting Default Routes Optional
Padding Odd-Length Packets Optional
Controlling Novell IPX Compliance
The Cisco implementation of the Novell IPX protocol is certified to provide full IPX router functionality
as defined by the Novell IPX Router Specification version 1.10 publication published November 17 1992
To control compliance to Novell specifications perform the tasks in the following sections
Controlling the Forwarding of Type 20 Packets Optional
Controlling Interpacket Delay Optional
Shutting Down an IPX Network Optional
Achieving Full Novell Compliance Optional
Controlling the Forwarding of Type 20 Packets
NetBIOS over IPX uses Type 20 propagation broadcast packets flooded to all networks to get
information about the named nodes on the network NetBIOS uses broadcast mechanism to get this
information because it does not implement network layer
Routers normally block all broadcast requests By enabling Type 20 packet propagation IPX interfaces
on the router may accept and forward Type 20 packets
How Type 20 Packet Propagation Works
Cisco lOS software When an interface configured for Type 20 propagation receives Type 20 packet Novell Cisco lOS software the to the processes the packet according to specifications propagates packet
be for to next interface The Type 20 packet can propagated up eight hop counts
Loop Detection and Other Checks
Before forwarding flooding the packets the router performs loop detection as described by the IPX
router specification
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 135 Configuring Novej Controlling Access to IPX Networks
You can configure the Cisco lOS software to extra checks to 20 apply Type propagation packets above and the detection described in the beyond ioop IPX specification These checks are the same ones that
are to all-nets broadcast applied helpered packets They can limit unnecessary duplication of Type 20 broadcast packets The extra helper checks are as follows
20 Accept Type propagation packets only on the primary network which is the network that is the primary path back to the source network
Forward 20 Type propagation packets only via networks that do not lead back to the source network
Although this extra increases the robustness of checking Type 20 propagation packet handling by the amount of decreasing unnecessary packet replication it has the following two side effects
If 20 is Type packet propagation not configured on all interfaces these packets might be blocked when the primary interface changes
It might be to manual impossible configure an arbitrary spanning tree for Type 20 packet propagation
Relationship Between Type 20 Propagation and Helper Addresses
You use addresses to forward helper non-Type 20 broadcast packets to other network segments For information on other forwarding broadcast packets see the Using Helper Addresses to Forward
Broadcast Packets section later in this chapter
You can use helper addresses and 20 in Type propagation together your network Use helper addresses to forward 20 broadcast non-Type packets and use Type 20 propagation to forward Type 20 broadcast packets
Type 20 Packets Configuration Task List
You can enable the of 20 forwarding Type packets on individual interfaces Additionally you can restrict the and acceptance forwarding of Type 20 packets You can also choose to not comply with Novell and forward 20 specifications Type packets using helper addresses rather than using Type 20 propagation The following sections describe these tasks
Enabling the Forwarding of Type 20 Packets Optional
Restricting the Acceptance of Incoming Type 20 Packets Optional
Restricting the Forwarding of Outgoing Type 20 Packets Optional
Forwarding Type 20 Packets Using Helper Addresses Optional
Enabling the Forwarding of Type 20 Packets
By default Type 20 propagation are the Cisco lOS software packets dropped by You can configure the software to receive 20 Type propagation broadcast packets and forward flood them to other network segments subject to loop detection
To enable the and of receipt forwarding Type 20 packets use the following command in interface configuration mode
Command Purpose
Router conf ig- if ipx type -20 -propagation Forwards IPX Type 20 propagation packet broadcasts to other network
segments
When enable 20 Cisco lOS the you Type propagation propagates broadcast to the next interface up to eight hops
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 136 Configuring Novell IPX
Controlling Access to IPX Networks
Restricting the Acceptance of Incoming Type 20 Packets
Cisco software is default For incoming Type 20 propagation packets the lOS configured by to accept
interfaces enabled to receive 20 You can configure the software packets on all Type propagation packets from the network that is the route back to the source network to accept packets only single primary received via other networks will be which means that similar packets from the same source that are
dropped
is done if the interface is Checking of incoming Type 20 propagation broadcast packets only configured
to receive and forward Type 20 packets
in addition to the checks To impose restrictions on the receipt of incoming Type 20 propagation packets in defined in the IPX specification use the following command global configuration mode
Command Purpose
Routerconfig ipx type-20..input-checko Restricts the acceptance of IPX Type 20 propagation packets
Restricting the Forwarding of Outgoing Type 20 Packets
lOS software is default to send For outgoing Type 20 propagation packets the Cisco configured by
to detection You can packets on all interfaces enabled to send Type 20 propagation packets subject loop
that not routes back to the source configure the software to send these packets only to networks are network The software uses the current routing table to determine routes
done if the interface is Checking of outgoing Type 20 propagation broadcast packets is only configured to receive and forward Type 20 packets
To impose restrictions on the transmission of Type 20 propagation packets and to forward these packets the command in to all networks using only the checks defined in the IPX specification use following
global configuration mode
Command Purpose
Routerconfg ipx type-20-output-checks Restricts the forwarding of IPX Type 20 propagation packets
Forwarding Type 20 Packets Using Helper Addresses
addresses rather than You can also forward Type 20 packets to specific network segments using helper
using the Type 20 packet propagation
when routers in network You may want to forward Type 20 packets using helper addresses some your some routers in are running versions of Cisco lOS that do not support Type 20 propagation When your and others do can avoid flooding packets everywhere in network support Type 20 propagation not you
the network by using helper addresses to direct packets to certain segments only
Cisco lOS Release 9.1 and earlier versions do not support Type 20 propagation
with the Novell IPX Note Forwarding Type 20 packets using helper addresses does not comply
router specification
Guide Cisco lOS AppleTalk and Novell IPX Configuration P2C 137 Configuring Nove_I Controlling Access to IPX Networks
20 addresses the To forward Type packets using helper addresses use following commands beginning in global configuration mode
Command Purpose
Step Routerconfig ipx type-20-helpered Forwards IPX Type 20 packets to specific networks
segments This step turns off Type 20 propagation ______Step Router config if ipx helper addreas network node From interface configuration mode specifies helper address for forwarding broadcast messages including IPX Type 20 packets
The Cisco lOS software forwards Type 20 packets to only those nodes specified by the ipx helper-address command
Note the Using ipx type-20-helpered command disables the receipt and forwarding of Type 20 propagation packets as directed by the ipx type-20-propagation command
Controlling Interpacket Delay
To control interpacket delay you can use combination of global configuration and interface configuration commands
Use one or more of the following commands in global configuration mode
Command Purpose
Router config ipx default-output-rip-delay delay Sets the interpacket delay of multiple-packet routing
updates sent on all interfaces
Router config ipx default triggered- rip-delay delay Sets the interpacket delay of multiple-packet triggered
routing updates sent on all interfaces
Router config ipx default-output-sap-delay delay Sets the interpacket delay of multiple-packet SAP updates
sent on all interfaces
Router config ipx default triggered- sap-delay delay Sets the interpacket delay of multiple-packet triggered SAP
updates sent on all interfaces
Use one or of the more following commands in interface configuration mode
Command Purpose
Router config-if ipx output-rip-delay delay Sets the interpacket delay of multiple-packet routing
updates sent on single interface
Routerconfigjf ipx triggered-rip-delay delay Sets the interpacket delay of multiple-packet triggered
routing updates sent on single interface
Router config-if ipx output-sap-delay delay Sets the of interpacket delay multiple-packet SAP updates
sent on single interface
Router config-if ipx triggered-sap-delay delay Sets the interpacket delay of multiple-packet triggered SAP
updates sent on single interface
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 138 Configuring Novell IPX
Controlling Access to IPX Networks
Note We recommend that you use the ipx output-rip-delay and ipx output-sap-delay
commands on slower speed WAN interlaces The default delay for Cisco lOS Release 11.1
and later versions is 55 milliseconds
Shutting Down an IPX Network
command in interlace To shut down an IPX network using Novell-compliant method use the following
configuration mode
Command Purpose
Router conf ig if ipx down network Administratively shuts down an IPX network on an
interlace This removes the network from the interlace
when Convergence is laster when you shut down an IPX network using the ipx down command than
using the shutdown command
Achieving Full Novell Compliance
commands in To achieve full compliance on each interlace configured for IPX use the following
interlace configuration mode
Command Purpose
55 of Step Router config-if ipx output-rip-delay Sets the interpacket delay multiple-packet routing
updates to 55 milliseconds
Step Router config-if ipx output-sap-delay 55 Sets the interpacket delay of multiple-packet SAP
updates to 55 milliseconds
20 if Step Router conf ig- if ipx type -20 -propagation Optionally enables Type packet propagation you
want to forward Type 20 broadcast traffic across the
router
RIP and to achieve full You can also globally set interpacket delays for multiple-packet SAP updates these use the compliance eliminating the need to set delays on each interlace To set interpacket delays
following commands in global configuration mode
Command Purpose
Step Router config ipx default-output-rip-delay 55 Sets the interpacket delay of multiple-packet routing 55 milliseconds updates sent on all interfaces to
55 of SAP Step Routerconfig ipx default-output-oap-delay Sets the interpacket delay multiple-packet
interfaces to 55 milliseconds updates sent on all
milliseconds Note The default delay for Cisco lOS Release 11.1 and later versions is 55
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 139 Configuring Novell IPX
Controlling Access to IPX Networks
Adjusting RIP and SAP Information
To RIP and adjust SAP information perform one or more of the optional tasks in the following sections
Configuring Static Routes Optional
Adjusting the RIP Delay Field Optional
Controlling Responses to RIP Requests Optional
Adjusting RIP Update Timers Optional
Configuring RIP Update Packet Size Optional
Configuring Static SAP Table Entries Optional
Configuring the Queue Length for SAP Requests Optional
Adjusting SAP Update Timers Optional
Configuring SAP Update Packet Size Optional
Enabling SAP-after-RIP Optional
Disabling Sending of General RIP or SAP Queries Optional
Controlling Responses to GNS Requests Optional
Configuring Static Routes
IPX uses RIP Enhanced IGRP or NLSP to determine the best path when several paths to destination exist The then the routing protocol dynamically updates routing table However you might want to add static the routes to routing table to explicitly specify paths to certain destinations Static routes always override any dynamically learned paths
Be careful when static routes When links assigning associated with static routes are lost traffic may forwarded or traffic stop being may be forwarded to nonexistent destination even though an alternative path might be available
To add static route to the routing table use the following command in global configuration mode
Command Purpose
Router config ipx route Adds static route to the routing table network default network.node interface
You can static configure routes that can be overridden by dynamically learned routes These routes are
referred to static as floating routes You can use floating static route to create path of last resort that is used only when no dynamic routing information is available
Note static By default floating routes are not redistributed into other dynamic protocols
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 140 Configuring Novell IPX
Controlling Access to IPX Networks
To add floating static route to the routing table use the following command in global configuration mode
Command Purpose
table Router config ipx route Adds floating static route to the routing network default network.node interface
Adjusting the RIP Delay Field
of By default all LAN interfaces have RIP delay of and all WAN interfaces have RIP delay the Leaving the delay at its default value is sufficient for most interfaces However you can adjust RIP the tick the command in interface delay field by setting the tick count To set count use following
configuration mode
Command Purpose
Router coot ig-if ipx delay ticks Sets the tick count which is used in the IPX RIP delay field
Controlling Responses to RIP Requests
the command in interface mode To control responses to RIP requests use following configuration
Command Purpose
RIP Routerconfig-if ipx rip-response-delay ms Sets the delay when responding to requests
Adjusting RIP Update Timers
You also the You can set the interval between IPX RIP updates on per-interface basis can specify delay basis between the packets of multiple-packet RIP update on per-interface or global Additionally you of RIP on or can specify the delay between packets multiple-packet triggered update per-interface
global basis
Cisco in which You can set RIP update timers only in configuration in which all routers are routers or
for all devices connected to the IPX routers allow configurable timers The timers should be the same timers follows the same cable segment The update value you choose affects internal IPX as
times the value of the IPX routes are marked invalid if no routing updates are heard within three
update interval interval and are advertised with metric of infinity
heard within four times the IPX routes are removed from the routing table if no routing updates are
value of the update interval interval
in the of the timer is determined If you define timer for more than one interface router granularity wakes at this by the lowest value defined for one of the interfaces in the router The router up For information about granularity interval and sends out updates as appropriate more granularity IPX Command refer to the Novell IPX Commands chapter in the Cisco lOS AppleTalk and Novell
Reference
if there are some slower You might want to set delay between the packets in multiple-packet update
PCs on the network or on slower-speed interfaces
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 141 Configuring Novell IPX
IrntroIIing Access to IPX Networks
To RIP timers adjust update on per-interface basis use one or all of the following conimands in interface configuration mode
Command Purpose
Router config-if ipx update interval rip ap Adjusts the RIP update timer value changes-only
Router conf ig- if ipx output-rip- delay delay Adjusts the delay between multiple-packet routing updates
sent on single interface
Router config-if ipx triggered-rip-delay delay the Adjusts delay between multiple-packet triggered
routing updates sent on single interface
To adjust RIP timers on both of the update global basis use one or following commands in global configuration mode
Command Purpose
Router config ipx default-output-rip-delay Adjusts the delay between multiple-packet routing updates sent on delay all interfaces
Router config ipx default-triggered-rip-delay the Adjusts delay between multiple-packet triggered routing delay updates sent on all interfaces
the RIP for By default entry network or server ages out at an interval equal to three times the RIP timer To the that configure multiplier controls the interval use the following command in interface configuration mode
Command Purpose Router config-if ipx rip-multiplier multiplier the interval at which network Configures RIP entry ages out
Configuring RIP Update Packet Size
the By default maximum size of RIP updates sent out an interface is 432 bytes This size allows for 50
routes at bytes each plus 32-byte IPX RIP header To modify the maximum packet size use the
following command in interface configuration mode
Command Purpose Router config-if ipx rip-max-packetsize bytes the Configures maximum packet size of RIP updates sent out an interface
Configuring Static SAP Table Entries
Servers use SAP to advertise their services via broadcast packets The Cisco lOS software stores this
information in the SAP table also known as the Server Information Table This table is updated You want to add dynamically might explicitly an entry to the Server Information Table so that clients always use the services of particular server Static SAP assignments always override any identical entries in the SAP table that are learned dynamically regardless of hop count If dynamic route that is associated with static SAP is lost or the software will entry deleted not announce the static SAP entry until it relearns the route
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 142 Configuring Novell IPX
Controlling Access to IPX Networks
command in To add static entry to the SAP table use the following global configuration mode
Command Purpose
network.node table Router config ipx sap service-type name Specifies static SAP entry socket hop-count
Configuring the Queue Length for SAP Requests
all Get Nearest The Cisco 105 software maintains list of SAP requests to process including pending
the network is restarted Server GNS queries from clients attempting to reach servers When following the router be hundreds of for power failure or other unexpected event can inundated with requests these from the same clients You can the servers Typically many of are repeated requests configure received when the is maximum length allowed for the pending SAP requests queue SAP requests queue
full are dropped and the client must resend them
the command in mode To set the queue length for SAP requests use following global configuration
Command Purpose
Router config ipx sap-queue-maximum number Configures the maximum SAP queue length
Adjusting SAP Update Timers
the between You can adjust the interval at which SAP updates are sent You can also set delay packets basis can the of multiple-packet SAP update on per-interface or global Additionally you specify on or basis delay between packets of multiple-packet triggered SAP update per-interface global
Changing the interval at which SAP updates are sent is most useful on limited-bandwidth point-to-point and routers links such as slower-speed interfaces You should ensure that all IPX servers on given
is down when it is network have the same SAP interval Otherwise they might decide that server really up
which SAP sent on most PC-based servers It is not possible to change the interval at updates are interval for Ethernet Token network that has servers Therefore you should never change the an or Ring on it
the You can set the router to send an update only when changes have occurred Using changes-only link when the link is downed keyword specifies the sending of SAP update only when the comes up the router to do the administratively or when the databases change The changes-only keyword causes
following
Send single full broadcast update when the link comes up
is shut down Send appropriate triggered updates when the link
information Send appropriate triggered updates when specific service changes
Guide Cisco lOS AppleTalk and Novell IPX Configuration P2C 143 Configuring Novell IPX
Controlling Access to IPX Networks
To the timers modify SAP update on per-interface basis use one or all of the following commands in interface configuration mode
Command Purpose
Router config-if ipx update interval trip sap Adjusts the interval at which SAP updates are sent value changes-only
Router config-if ipx output-sap-delay delay the Adjusts interpacket delay of multiple-packet SAP
updates sent on single interface
Router config-if ipx triggered-sap-delay delay the of Adjusts interpacket delay multiple-packet triggered
SAP updates sent on single interface
To adjust SAP timers on basis update global eliminating the need to configure delays on per-interface use one or both of the basis following commands in global configuration mode
Command Purpose Router config ipx default-output-sap-delay delay the Adjusts interpacket delay of multiple-packet SAP
updates sent on all interfaces Router config ipx default-triggered-sap-delay delay the of Adjusts interpacket delay multiple-packet triggered SAP updates sent on all interfaces
By default the SAP of network entry or server ages out at an interval equal to three times the SAP
update interval To the that configure multiplier controls the interval use the following command in interface configuration mode
Command Purpose
Router conf ig- if ipx sap-multiplier multiplier the interval Configures at which the SAP entry of network
or server ages out
Configuring SAP Update Packet Size
the maximum size By default of SAP updates sent out on an interface is 480 bytes This size allows for seven servers 64 bytes each plus 32-byte IPX SAP header To modify the maximum packet size use the command in following interface configuration mode
Command Purpose
Routerconfig-if ipx sap-max-packetsize bytes the Configures maximum packet size of SAP updates sent out an interface
Enabling SAP-after-RIP
The IPX SAP-after-RIP feature links SAP updates to RIP updates so that SAP broadcast and unicast
updates automatically occur after the immediately completion of the corresponding RIP update This feature ensures that remote router does not service reject information because it lacks valid route to the service As result of this SAP feature periodic updates are sent at the same interval as RIP updates
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 144 Configuring Novell IPX
Controlling Access to IPX Networks
The default behavior of the router is to send RIP and SAP periodic updates with each using its own RIP and are update interval depending on the configuration In addition SAP periodic updates jittered time This feature SAP and slightly such that they tend to diverge from each other over synchronizes
RIP updates
Sending all SAP and RIP information in single update reduces bandwidth demands and eliminates
erroneous rejections of SAP broadcasts
because Linking SAP and RIP updates populates the service table of the remote router more quickly the service table more services will not be rejected due to the lack of route to the service Populating have been increased quickly can be especially useful on WAN circuits where the update intervals greatly
to reduce the overall level of periodic update traffic on the link
the command in To configure the router to send SAP update following RIP broadcast use following
interface configuration mode
Command Purpose
Router config-if ipx update sap-after-rip Configures the router to send SAP broadcast immediately
following RIP broadcast
Disabling Sending of General RIP or SAP Queries
when it first comes to reduce You can disable the sending of general RIP or SAP queries on link up
traffic and save bandwidth
circuit first comes On WAN RIP and SAP general queries are normally sent by remote routers when up
first is full broadcast circuits two full updates of each kind are often sent across the link The update
update triggered locally by the link-up event The second update is specific unicast reply triggered
the If disable the of queries when by the general query received from remote router you sending general
is reduce traffic and save bandwidth the link first comes up it possible to to single update
the following To disable the sending of general RIP or SAP query when an interface comes up use
command in interface configuration mode
Command Purpose
interface Router config-if no ipx linkup-request Disables the sending of general RIP or SAP Query when an rip sap comes up
of the command To reenable the sending of general RIP or SAP query use the positive form
Controlling Responses to GNS Requests
set the time You can set the method in which the router responds to SAP GNS requests you can delay these in responding to these requests or you can disable the sending of responses to requests altogether
if local server with better By default the router responds to GNS requests if appropriate For example
metric exists then the router does not respond to the GNS request on that segment
whose was The default method of responding to GNS requests is to respond with the server availability
learned most recently
and Novell IPX Configuration Cisco lOS AppleTalk Gup P2 C-I 45 Configuring Novell IPX Controlling Access to IPX Networks
To control responses to GNS requests use one or both of the following commands in global configuration mode
Command Purpose
Router config ipx gns-round-robin Responds to GNS requests using round-robin selection method
Routerconfig ipx gns-response-delay Sets the delay when responding to GNS requests
Note The ipx gns-response-delay command is also supported as an interface configuration
command To override the global delay value for specific interface use the
ipx gns-response-delay command in interface configuration mode
To disable GNS queries on per-interface basis use the following command in interface configuration mode
Command Purpose
Routerconfig.-if ipx gns-reply-disable Disables the sending of replies to Get Nearest Server GNS queries
Configurhuj Load Shathig
To configure IPX to perform round-robin or per-host load sharing perform the tasks described in the following sections
Enabling Round-Robin Load Sharing Optional
Enabling per-Host Load Sharing Optional
Enabling Round-Robin Load Sharing
You can set the maximum number of equal-cost parallel paths to destination Note that when paths have the Cisco lOS software chooses differing costs lower-cost routes in preference to higher-cost The software then distributes routes output on packet-by-packet basis in round-robin fashion That is the first is packet sent along the first path the second packet along the second path and so on When the final is path reached the next packet is sent to the first path the next to the second path and so on This round-robin scheme is used of regardless whether fast switching is enabled
Limiting the number of equal-cost can save routers with limited paths memory on memory or very large in networks with configurations Additionally large number of multiple paths and systems with limited
ability to cache suffer when traffic is out-of-sequence packets performance might split between many paths
To set the maximum number of paths use the following command in global configuration mode
Command Purpose Router config ipx inazimuin-patha paths Sets the maximum number of equal-cost paths to destination
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 146 Configuring Novell IPX
Controlling Access to IPX Networks
Enabling per-Host Load Sharing
Round-robin load sharing is the default behavior when you configure ipx maximum-paths to value load works data over successive cost greater than Round-robin sharing by sending packets equal paths end hosts sessions Path utilization increases transmission without regard to individual or user speed but end host take different arrive out of order because packets destined for given may paths they might
load You can address the possibility of packets arriving out of order by enabling per-host sharing With
still to achieve load per-host load sharing the router uses multiple equal-cost paths sharing however
take the if are packets for given end host are guaranteed to same path even multiple equal-cost paths load is available Traffic for different end hosts tend to take different paths but true balancing not of the workload guaranteed The exact degree of load balancing achieved depends on the exact nature
commands in mode To enable per-host load sharing use the following global configuration
Command Purpose
Sets the maximum number of cost paths to Step Router config ipx maximum-paths paths equal destination to value greater than
Router config ipx per-host-load-share Enables per-host load sharing
Specifying the Use of Broadcast Messages
broadcast the tasks described in the following sections To specify the use of messages perform
Using Helper Addresses to Forward Broadcast Packets Optional
Enabling Fast Switching of IPX Directed Broadcast Packets Optional
Using Helper Addresses to Forward broadcast Packets
forward them to other network Routers normally block all broadcast requests and do not segments the entire network However can enable therefore preventing the degradation of performance over you other network the router to forward broadcast packets to helper addresses on segments
How Helper Addresses Work
another that can receive unrecognized Helper addresses specify the network and node on segment that not broadcast packets Unrecognized broadcast packets are non-RIP and non-SAP packets are
addressed to the local network
receives broadcast When the interface configured with helper addresses an unrecognized packet the Cisco lOS software changes the broadcast packet to unicast and sends the packet to specified not flooded network and node on the other network segment Unrecognized broadcast packets are
everywhere in your network
of that the broadcast can make With helper addresses there is no limit on the number hops packet
Fast Switching Support
broadcast Cisco lOS supports fast switching of helpered packets
When to Use Helper Addresses
20 to other You use helper addresses when you want to forward broadcast packets except Type packets
network segments
Guide Cisco lOS AppleTalk and Novell IPX Configuration P2C 147 Configuring Novell IPXJ Confrolling Access to IPX Networks
broadcast Forwarding packets to helper addresses is sometimes useful when network segment does not have an end-host capable of of broadcast servicing particular type request You can specify the address of networks that server network or can process the broadcast packet
Relationship Between Helper Addresses and Type 20 Propagation
You 20 use Type packet propagation to forward Type 20 packets to other network segments For information 20 the on forwarding Type packets see Controlling the Forwarding of Type 20 Packets section earlier in this chapter
You can use helper addresses and 20 in Type propagation together your network Use helper addresses to forward 20 broadcast and non-Type packets use Type 20 propagation to forward Type 20 broadcast packets
Implementation Considerations
addresses is Using helper not Novell-compliant However it does allow routers to forward broadcast to network packets segments that can process them without flooding the network It also allows routers versions of Cisco running lOS that do not support Type 20 propagation to forward Type 20 packets
The Cisco lOS software all-networks supports flooded broadcasts sometimes referred to as all-nets These are broadcast flooding messages that are forwarded to all networks Use all-nets
flooding carefully and only when because the networks be necessary receiving may overwhelmed to the point that no other traffic can traverse them
Use the ipx helper-list command described earlier in this chapter to define access lists that control which broadcast packets get forwarded
Using Helper Addresses
To specify helper address for broadcast forwarding packets use the following command in interface configuration mode
Command Purpose
Router config-if ipx helper-addresa Specifies helper address for forwarding broadcast messages network node
You can specify multiple helper addresses on an interface
For an example of using helper addresses to forward broadcast messages see the Helper Facilities to Control Broadcast section the Examples at end of this chapter
Enabling Fast Switching of IPX Directed Broadcast Packets
By default Cisco lOS software switches that packets have been helpered to the broadcast address To enable fast switching of these IPX-directed broadcast the packets use following command in global configuration mode
Command Purpose
Router config ipx broadcaat-fastswitching Enables fast switching of IPX-directed broadcast packets
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 148 Configuring Novell IPX
Controlling Access to IPX Networks
Disabling IPX Fast Switching
fast By default fast switching is enabled on all interfaces that support switching
cache created Fast switching allows higher throughput by switching packet using by previous packets
Fast switching is enabled by default on all interfaces that support fast switching
is enabled Packet transfer performance is generally better when fast switching However you might want in order interface cards and to avoid congestion to disable fast switching to save memory space on help low-bandwidth interfaces when high-bandwidth interfaces are writing large amounts of information to
Caution Turning off fast switching increases system overhead
To disable IPX fast switching use the following command in interface configuration mode
Command Purpose
Router config-if no ipx route-cache Disables IPX fast switching
Adjusting the Route Cache
control the size of the route reduce consumption Adjusting the route cache allows you to cache memory the route cache size and and improve router performance You accomplish these tasks by controlling
invalidation The following sections describe these optional tasks
Controlling Route Cache Size Optional
Controlling Route Cache Invalidation Optional
Controlling Route Cache Size
You can limit the number of entries stored in the IPX route cache to free up router memory and aid router
processing
in the cache amount of router causing router Storing too many entries route can use significant memory situation is networks that run network management processing to slow This most common on large
applications for NetWare
all clients and servers in For example if network management station is responsible for managing than Novell network the routers on the local segment can become very large greater 50000 nodes entries these inundated with route cache entries You can set maximum number of route cache on
routers to free up router memory and aid router processing
the command in To set maximum limit on the number of entries in the IPX route cache use following
global configuration mode
Command Purpose
Router config ipx route-cache max-size size Sets maximum limit on the number of entries in the IPX route cache
deleted If the route cache has more entries than the specified limit the extra entries are not However See the Route Cache they may be removed if route cache invalidation is in use Controlling route cache entries Invalidation section later in this chapter for more information on invalidating
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 149 Configuring Novell IPX Controlling Access to IPX Networks
Controlling Route Cache Invalidation
You can configure the router to invalidate fast-switch cache entries that are inactive If these entries remain invalidated for the minute router purges the entries from the route cache
Purging invalidated entries reduces the size of the route cache reduces memory consumption and
improves router performance Also purging entries helps ensure accurate route cache information
You specify the period of time that valid fast-switch cache entries must be inactive before the router
invalidates them You can also the number of cache entries that the specify router can invalidate per minute
To the router to invalidate fast-switch cache entries that configure are inactive use the following command in global configuration mode
Command Purpose
Router route-cache config ipx inactivity-timeout period Invalidates fast-switch cache entries that are inactive
When you use the ipx route-cache inactivity-timeout command with the ipx route-cache max-size command you can ensure small route cache with fresh entries
Adjusting Defatilt Routes
You can adjust the use of default routes in your IPX network You can turn off the use of network number -2 the default as route You can also specify that the router advertise only default RIP routes out an interface The following sections describe these optional tasks
Disabling Network Number -2 as the Default Route Optional
Advertising Only Default RIP Routes Optional
Disabling Network Number -2 as the Default Route
The default is used route when route to any destination network is unknown All packets for which
route to the destination address is unknown are forwarded to the default route By default IPX treats network number -2 OxFFFFFFFE as the default route
For introduction an to default routes see the IPX Default Routes section earlier in this chapter For
more background information on how to handle IPX default routes refer to the Novell NetWare Link Services Protocol NLSP Specification Revision 1.1 publication
Cisco By default lOS software treats network -2 as the default route You can disable this default behavior and use network -2 as regular network number in your network
To disable the use of network number -2 as the default route use the following command in global configuration mode
Command Purpose
Router config no ipx default-route Disables default route handling
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 150 Configuring Novell IPX Shutting Down an IPX Network
Advertising Only Default RIP Routes
advertised out each interface can Unless configured otherwise all known RIP routes are However you
if is therefore the overhead choose to advertise only the default RIP route it known greatly reducing CPU
when routing tables are large
the command in interface To advertise only the default route via an interface use following configuration mode
Command Purpose
Routerconfig-if ipx advertise-default-route-only network Advertises only the default RIP route
Padding Odd-Length Packets
is the Some IPX end hosts accept only even-length Ethernet packets If the length of packet odd packet Cisco 105 must be padded with an extra byte so that end host can receive it By default pads odd-length
Ethernet packets
forwarded However there are cases in certain topologies where nonpadded Ethernet packets are onto intermediate media remote Ethernet network Under specific conditions you can enable padding on as under the temporary workaround for this problem Note that you should perform this task only guidance of customer engineer or other service representative
To enable the padding of odd-length packets use the following commands in interface configuration mode
Command Purpose
Step Router config-if no ipx route-cache Disables fast switching
of Step Router config-if ipx pad-process-switched-packets Enables the padding odd-length packets
Shutting Down an IPX Network
the network still exists You can administratively shut down an IPX network in two ways In the first way the network sends out in the configuration but is not active When shutting down update packets the to informing its neighbors that it is shutting down therefore allowing neighboring systems update learned via this their routing SAP and other tables without needing to wait for routes and services
network to time out
To shut down an IPX network such that the network still exists in the configuration use the following
command in interface configuration mode
Command Purpose
Router config-if ipx down network Shuts down an IPX network but allows the
network to still exist in the configuration
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 151 Configuring Novell IPX
Configuring IPX Accounting
To shut down IPX an network and remove it from the configuration use one of the following commands
in interface configuration mode
Command Purpose
Router config-if no ipx network Shuts down an IPX network and removes it from
the configuration
Router config-if no ipx network network When multiple networks are configured on an where network is the primary interface interface shuts down all networks and removes
them from the interface
Router config-if no ipx network network When multiple networks are configured on an where networkis the nunther of the secondary interface interfaceshutsdownoneofthe secondary
networks and removes it from the interface
When networks are multiple configured on an interface and you want to shut down one of the secondary
networks and remove it from the the interface use second command in the previous table specifying the network number of one of the secondary networks
For an of down example shutting an IPX network see the IPX Routing Examples section at the end of this chapter
Configuring PX Accounting
IPX accounting enables to collect information about IPX you packets and the number of bytes that are switched the Cisco lOS through software You collect information based on the source and destination IPX address IPX accounting tracks only IPX traffic that is routed out an interface on which IPX
is it does accounting configured not track traffic generated by or terminated at the router itself
The Cisco 105 software maintains two accounting databases an active database and checkpoint database The active database contains accounting data tracked until the database is cleared When the active database is its cleared contents are copied to the checkpoint database Using these two databases
together enables to monitor both current traffic you and traffic that has previously traversed the router
Switching Support
Process and fast IPX switching support accounting statistics Autonomous and silicon switching engine do SSE switching not support IPX accounting statistics
Note CiscoBus and SSE Cbus are not supported on the MIP interface
Access List Support
IPX lists access support IPX accounting statistics
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 152 Configuring Novell IPX
Configuring IPX Between LANi
IPX Accounting Task List
in the sections The first task is the To configure IPX accounting perform the tasks following required
remaining task is optional
Enabling IPX Accounting Required
Customizing IPX Accounting Optional
Enabling IPX Accounting
To enable IPX accounting use the following command in global configuration mode
Command Purpose
Router config ipx accounting Enables IPX accounting
Customizing IPX Accounting
To customize IPX accounting use one or more of the following commands in global configuration mode
Command Purpose
Router config ipx accounting-threshold Sets the maximum number of accounting entries threshold
Router config ipx accounting-transits Sets the maximum number of transit entries count
is Router config ipx accounting- list Defines the filter networks for which IPX accounting information kept number mask Use one command for each network
networks the Transit entries are entries in the database that do not match any of the specified by ipx
accounting-list commands
interface do list IPX tracks If you enable IPX accounting on an but not specify an accounting accounting the threshold limit all traffic through the interface all transit entries up to accounting
section the For an example of how to configure IPX accounting see the IPX Accounting Example at
end of this chapter
Configuring IPX Between LANs
and Token Cisco 105 software supports routing IPX between Ethernet-emulated LANs Ring-emulated refer the LANs For more information on emulated LANs and routing IPX between them to Services Guide Configuring LAN Emulation chapter of the Cisco lOS Switching Configuration
Guide Cisco lOS AppleTalk and Novell IPX Configuration P2C 153 Configuring Novel lj onfiguring IPX Between VLANs
Configuring PX Between VLANs
Cisco lOS software supports routing IPX between VLANs Users with Novell NetWare environments of the can configure any one four IPX Ethernet encapsulations to be routed using the Inter-Switch Link across boundaries For ISL encapsulation VLAN more information on VLANs and routing IPX between them over ISL refer to the Configuring Routing Between VLANs with ISL Encapsulation of the Cisco 105 chapter Switching Services Configuration Guide
Configuring IPX Multilayer Switching
Cisco lOS software IPX supports Multilayer Switching MLS For more information on IPX MLS refer to the of the Multilayer Switching chapter Cisco lOS Switching Services Configuration Guide
Monitoring and Maintaining the IPX Network
To monitor and maintain IPX the tasks described in your network perform optional the following sections
General Monitoring and Maintaining Tasks Optional
Monitoring and Maintaining IPX Enhanced IGRP Optional
Monitoring and Maintaining NLSP Optional
Monitoring and Maintaining NHRP Optional
Monitoring and Maintaining IPX Accounting Optional
Genera Monitoring and Maintaining Tasks
You can perform one or more of these general monitoring and maintaining tasks as described in the
following sections
and Monitoring Maintaining Caches Tables Interfaces and Statistics Optional
Specifying the Type and Use of Ping Packets Optional
Troubleshooting Network Connectivity Optional
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 154 Configuring Novell IPX
Monitoring and Maintaining the IPX Network
Monitoring and Maintaining Caches Tables Interfaces and Statistics
To monitor and maintain caches tables interfaces or statistics in Novell IPX network use one or more
of the following commands in EXEC mode
Command Purpose
cache Router clear ipx cache Deletes all entries in the IPX fast-switching
Router clear ipx route Deletes entries in the IPX routing table
Router clear ipx traffic Clears IPX traffic counters
Router show ipx cache Lists the entries in the IPX fast-switching cache
Router show ipx interface type number Displays the status of the IPX interfaces
configured in the router and the parameters
configured on each interface
Router show ipx route Lists the entries in the IPX routing table
Router show ipx servers sorted net Lists the servers discovered through SAP type name advertisements
Router show ipx traffic bootup show Displays information about the number and type
of IPX packets sent and received
of SSE statistics Router show sse summary Displays summary
Specifying the Type and Use of Ping Packets
defined in the The Cisco lOS software can send Cisco pings and standard Novell pings as NLSP the software Cisco To choose specification or diagnostic request packets By default generates pings in the ping type use the following command global configuration mode
Command Purpose
Routerconfig ipxping..default cisco novell diagnostic Selects theping type
related issues and unicast The IPX diagnostic ping feature addresses diagnostic by accepting processing the current IPX command to other or broadcast diagnostic packets It makes enhancements to ping ping information in the stations using the diagnostic packets and display the configuration response packet
back Note When ping is sent from one station to another the response is expected to come could immediately when the ipx ping-default command is set to diagnostics the response 0.5 seconds consist of more than one packet and each node is expected to respond within of there is and of receipt of the request Due to the absence an end-of-message flag delay arrive in verbose mode there the requester must wait for all responses to Therefore may
data is be brief delay of 0.5 seconds before the response displayed
be used to conduct The ipx ping command using the diagnostic keyword can reachability
test and should not be used to measure accurate round-trip delay
Guide Cisco lOS AppleTalk and Novell IPX Configuration P2C 155 Configuring Novell IPX Monitoring and Maintaining the IPX Network
To initiate ping use one of the following commands in EXEC mode
Command Purpose
Router ping ipx network node Diagnoses basic IPX network connectivity user-level command Router ping basic IPX Diagnoses network connectivity privileged command
Troubleshooting Network Connectivity
To trace the IPX destination and measure roundtrip delays use the following command in either user or privileged EXEC mode
Command Purpose
Router trace Traces packet routes through the network user or privileged
Note In EXEC user mode you are not allowed to change the trace route timeout interval probe minimum and maximum count time to live and verbose mode To do so use the trace command in privileged EXEC mode
Monitoring and Maintaining PX Enhanced GRP
To monitor and maintain Enhanced IGRP on an IPX network use one or more of the following commands in EXEC mode
Command Purpose
Router show ipx eigrp neighbors Lists the neighbors discovered by IPX Enhanced IGRP type number name Router show ipx eigrp interfaces type number Displays information about interfaces configured for Enhanced IGRP
Router show ipx eigrp topology Displays the contents of the IPX Enhanced IGRP topology table
Router show ipx route the Displays contents of the IPX routing table including Enhanced IGRP entries
Router show traffic ipx information about IPX Displays traffic including Enhanced IGRP traffic
Logging Enhanced UGRP Neighbor Adjacency Changes
You can enable the logging of neighbor adjacency changes to monitor the stability of the routing system and to help you detect problems By default adjacency changes are not logged
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 156 Configuring Novell IPX
Monitoring and Maintaining the IPX Network
the command in To enable logging of Enhanced IGRP neighbor adjacency changes use following
IPX-router configuration mode
Command Purpose
Router config-ipx-router log-neighbor-changes Enables logging of Enhanced IGRP neighbor adjacency changes
Monitoring and Maintaining NLSP
To monitor and maintain NLSP on an IPX network use one or more of the following commands in EXEC mode
Command Purpose
from the database Router clear ipx nlsp neighbors Deletes all NLSP adjacencies adjacency
Router clear ipx nlsp traffic Clears NLSP traffic counters
LSP database Router show ipx nlsp database Displays the entries in the
device and their Router show ipx nlsp neighbors interface Displays the NLSP neighbors of the states
calculations for Router show ipx nlsp spf-log Displays history of the SPF NLSP
traffic statistics for NLSP traffic Router show ipx nlsp traffic bootup show Displays cumulative counters
Logging Adjacency State Changes
state or You can allow NLSP to generate log message when an NLSP adjacency changes up down networks are Generating log message may be very useful when monitoring large Messages logged form using the system error message facility Messages are in the following
%CLNS-5-ADJCHlNGE NLSP Adjacency to 0000.0000.0034 SerialO Up new adjacency %CLNS-5-PDJCHANGE NLSP Adjacency to 0000.0000.0034 SerialO Down hold time expired
use the following command in To generate log messages when an NLSP adjacency changes state
IPX-router configuration mode
Command Purpose
Routerconfig-ipx--router log-adjacency-changes Logs NLSP adjacency state changes
Guide Cisco lOS AppleTalk and Novell IPX Configuration P2C 157 Configuring Novell IPX
Monitoring and Maintaining the IPX Network
Monitoring and Maintaining NHRP
To monitor the NHRP cache or traffic use either of the following commands in EXEC mode
Command Purpose
Router ahow ipx nhrp static Displays the IPX NHRP cache optionally limited to dynamic or number static cache entries for specific interface
Router show traffic ipx nhrp Displays NHRP traffic statistics
The NHRP cache can contain static entries caused by statically configured addresses and dynamic entries caused the Cisco lOS software addresses from by learning NHRP packets To clear static entries use the no To clear the cache ipx nhrp map command NHRP of dynamic entries use the following command in EXEC mode
Command Purpose Router clear ipx nhrp Clears the IPX NHRP cache of dynamic entries
Monitoring and Maintaining IPX Accounting
To monitor and maintain IPX in accounting your IPX network use the following commands in EXEC mode
Command Purpose
Router clear ipx accounting Deletes all entries in the IPX accounting or accounting
checkpoint database Router ahow ipx accounting Lists the entries in the IPX accounting or accounting checkpoint database
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2 C-I 58 Configuring Novell IPX
Novell IPX Configuration Examples
This following sections provide IPX configuration examples
IPX Routing Examples
Enhanced IGRP Examples
NLSP Examples
NHRP Examples
IPX over WAN Examples
IPX Network Access Examples
Helper Facilities to Control Broadcast Examples
IPX Accounting Example
IPX Routing Examples
with network and with This section shows examples for enabling IPX routing on interfaces single shows how enable and disable various combinations of routing protocols multiple networks It also to
The following sections provide these examples
IPX Routing on Single Network Example
IPX Routing on Multiple Networks Examples
IPX Routing Protocols Examples
IPX Routing on Single Network Example
the IPX host address to that of the The following example shows how to enable IPX routing defaulting
is then enabled Ethernet first IEEE-conformance interface in this example Ethernet Routing on
and Ethernet for IPX networks 2abc and idef respectively
ipx routing interface ethernet ipx network 2abc interface ethernet ipx network idef
IPX Routing on Multiple Networks Examples
networks You can use There are two ways to enable IPX on an interface that supports multiple of each subinterfaces or primary and secondary networks This section gives an example
Guide Cisco lOS AppleTalk and Novell IPX Configuration P2C 159 Configuring Novell IPX
Subinterfaces Example
The shows how to following example use subinterfaces to create four logical networks on Ethernet interface Each subinterface has different interface encapsulation Any configuration parameters that you specify on an individual subinterface are applied to that subinterface only
ipx routing interface ethernet 0.1 ipx network encapsulation novell-ether interface ethernet 0.2 ipx network encapsulation snap interface ethernet 0.3
ipx network encapsulation arpa interface ethernet 0.4
ipx network encapsulation sap
Note When and enabling NLSP configuring multiple encapsulations on the same physical LAN
interface you must use subinterfaces You cannot use secondary networks
You can shut down administratively each of the four subinterfaces separately by using the shutdown interface configuration command for subinterface each The following example shows how to administratively shut down subinterface
interface ethernet 0.3 shutdown
To down network the bring use following commands
interface ethernet 0.1 ipx down
To network back bring up use the following commands
interface ethernet 0.1 no ipx down
To remove all the networks on the interface use the following interface configuration commands
interface ethernet 0.1 no ipx network interface ethernet 0.2 no ipx network interface ethernet 0.3 no ipx network interface ethernet 0.4 no ipx network
Primary and Secondary Networks Example
Note The following examples discuss primary and secondary networks In future Cisco lOS software and releases primary secondary networks will not be supported Use subinterfaces
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 160 Configuring Novell IPX
the The following example shows how to use primary and secondary networks to create same four logical networks as shown earlier in this section Any interface configuration parameters that you specify on this the timer interface are applied to all the logical networks For example if you set routing update to
120 seconds this value is used on all four networks
ipx routing interface ethernet ipx network encapsulation novell-ether ipx network encapsulation snap secondary ipx network encapsulation arpa secondary ipx network encapsulation sap secondary
shut down Ethernet interface Using this method to configure logical networks if you administratively
all four networks are shut down You using the shutdown interface configuration command logical the shutdown however can cannot bring down each logical network independently using command you
bring them down using the ipx down command
network The following example shows how to shut down
interface ethernet ipx down
back The following example shows how to bring the network up
interface ethernet
no ipx down
networks the interface and remove all The following two examples show how to shut down all four on
the networks on the interface
no ipx network
no ipx network
networks the interface this The following example shows how to remove one of the secondary on in case network
no ipx network
interfaces 0.2 and 0.3 FDDI The following example shows how to enable IPX routing on FDDI On
the is the interface 0.2 the encapsulation type is SNAP On FDDI interface 0.3 encapsulation type Novell FDDI_RAW
ipx routing interface fddi 0.2 ipx network f02 encapsulation snap interface fddi 0.3 ipx network 03 encapsulation novell-fddi
PX Routing Protocols Examples
Enhanced and NLSP Three routing protocols can run over interfaces configured for IPX RIP IGRP combinations of This section provides examples of how to enable and disable various routing protocols
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 161 Configuring Novell IPX
When enable IPX you routing with the ipx routing global configuration command the RIP routing
protocol is automatically enabled The following example shows how to enable RIP on networks and
ipx routing
interface ethernet
ipx network
interface ethernet
ipx network
The following example shows how to enable RIP on networks and and Enhanced IGRP on network
ipx routing
interface ethernet
ipx network
interface ethernet
ipx network
ipx router eigrp 100 network
The following example shows how to enable RIP on network and Enhanced IGRP on network
ipx routing
interface ethernet
ipx network
interface ethernet
ipx network
ipx router eigrp 100 ipx network
ipx router rip no ipx network
The following example shows how to configure NLSP on two Ethernet interfaces of the router Note that RIP is enabled on both of these This automatically interfaces example assumes that the encapsulation type is Ethernet 802.2
ipx routing ipx internal-network
ipx router nlsp areal area-address
interface ethernet
ipx network eO encapsulation sap ipx nlsp areal enable
interface ethernet
ipx network el encapsulation sap ipx nlsp areal enable
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 162 Configuring Novell IPX
Enhanced IGRP Examples
of how IPX Enhanced IGRP The following sections show several examples to configure routing
IPX Enhanced IGRP Example
IPX SAP-Incremental IGRP Example
Enhanced IGRP SAP Update Examples
Advertisement and Processing of SAP Update Examples
IPX Enhanced IGRP Bandwidth Configuration Example
IPX Enhanced IGRP Example
shows how two interfaces for Enhanced IGRP routing in The following example to configure
autonomous system
ipx routing
interface ethernet ipx network 10
interface serial ipx network 20
ipx router eigrp network 10 network 20
IPX SAP-Incremental IGRP Example
for the IPX SAP Enhanced IGRP The following example shows sample configuration enabling
ipx routing
interface ethernet ipx network ipx sap-incremental eigrp ipx sap-incremental split-horizon
ipx router eigrp 100 network
Guide Cisco lOS AppleTalk and Novell IPX Configuration P2C 163 Configuring Novell IPX
Enhanced IGRP SAP Update Examples
If an Ethernet interface has that all neighbors are configured for Enhanced IGRP you might want to reduce the bandwidth used by SAP packets by sending SAP updates incrementally The following shows example how to send SAP updates incrementally
ipx routing
interface ethernet ipx network 10 ipx sap-incremental eigrp
interface serial ipx network 20
ipx router eigrp network 10 network 20
The shows following example how to send only incremental SAP updates on serial line that is configured for Enhanced IGRP
ipx routing
interface ethernet
ipx network 10
interface serial
ipx network 20 ipx sap-incremental eigrp rsup-only
ipx router eigrp network 10 network 20
Advertisement and Processing of SAP Update Examples
The following example shows how to cause only services from network to be advertised by an Enhanced IGRP routing process
access-list 1010 permit access-list 1010 deny -l
ipx router eigrp 100 network distribute-sap-list 1010 out
The following example shows how to configure the router to redistribute Enhanced IGRP into NLSP areal services for networks and Only are accepted by the NLSP routing process
access-list 1000 permit access-list 1000 permit access-list 1000 deny -1
ipx router nlsp areal redistribute eigrp distribute-sap-list 1000 in
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 164 Configuring Novell IPX
IPX Enhanced IGRP Bandwidth Configuration Example
used IPX Enhanced In this The following example shows how to configure the bandwidth by IGRP maximum of 25 of example Enhanced IGRP process 109 is configured to use percent or 32-kbps 128-kbps circuit
interface serial bandwidth 128
ipx bandwidth-percent eigrp 109 25
of circuit to 20 for The following example shows how to configure the bandwidth 56-kbps kbps routing maximum of 200 policy reasons The Enhanced IGRP process 109 is configured to use percent or 40 kbps of the circuit
interface serial bandwidth 20
ipx bandwidth-percent eigrp 109 200
NLSP Examples
The following sections show several examples of how to configure NSLP
NLSP Multicast Addressing Examples
Enhanced IGRP and NLSP Route Redistribution Example
NLSP Route Aggregation for Multiple NLSP Version 1.1 Areas Example
NLSP Route Aggregation for NLSP Version 1.1 and Version 1.0 Areas Example
NLSP Route Aggregation for NLSP Version 1.1 Enhanced IGRP and RIP Example
NLSP Multicast Addressing Examples
to turn on NLSP By default NLSP multicast addressing is enabled You need not configure anything
multicasting
do substitute broadcast where multicast addressing is Typically you not want to addressing NLSP than broadcast available NLSP multicast addressing uses network bandwidth more efficiently addressing However there are circumstances where you might want to disable NLSP multicast addressing
of broadcast For example you might want to disable NLSP multicast addressing in favor addressing You also want when one or more devices on segment do not support NLSP multicast addressing might
to disable it for testing purposes
do so for the entire router or for If you want to disable NLSP multicast addressing you can particular interface
for multicast The following sections provide sample configurations disabling addressing
Disabling NLSP Multicasting on the Router Example
Interface Disabling NLSP Multicasting on an Example
Disabling NLSP Multicasting on the Router Example
the router The following example shows how to disable multicast addressing on
ipx router nlsp no nulticast
Cisco lOS AppleTalk and Novell IPX Configuration Guide Configuring Novell IPX
Disabling NLSP Molticasting on an Interface Example
The following example shows how to disable multicast addressing on Ethernet interface 1.2
interface ethernet 1.2 no ipx nlsp multicast
Enhanced IGRP and NLSP Route Redistribution Example
The following example shows how to configure router to redistribute NLSP into Enhanced IGRP autonomous system 100 and Enhanced IGRP autonomous system 100 into NLSP
ipx router eigrp 100 redistribute nlsp
ipx router nlsp redistribute eigrp 100
NLSP Route Aggregation for Multiple NLSP Version 1.1 Areas Example
The shows how to the following example configure route aggregation for router connecting multiple NLSP version 1.1 areas In this example the two areas are areal and area2 Because both areas are NLSP version 1.1 areas redistribution of aggregated routes or explicit routes between the two areas is automatic
ipx routing ipx internal-network 2000
interface ethernet ipx network 1001 ipx nlsp areal enable
interface ethernet ipx network 2001 ipx nlsp area2 enable
ipx router nlsp areal area-address 1000 fffff000 route aggregation
ipx router nlsp area2 area-address 2000 fffff000 route-aggregation
NLSP Route Aggregation for NLSP Version 11 and Version 1O Areas Example
The shows following example how to configure the route aggregation feature with customized route
summarization In this example areal is an NLSP version 1.0 area and area2 is an NLSP version 1.1 area routes learned in Any explicit area that fall in the range of aaaa0000 ffff0000 are redistributed into area2 as an aggregated route Explicit routes from areal that do not fall in that range are redistributed into area2 as an explicit route
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2 C-I 66 Configuring Novell IPX
learned in area2 Because areal is an NLSP version 1.0 area it cannot accept aggregated routes Thus when redistribution into areal occurs the router sends explicit routes instead of aggregated routes
ipx routing ipx internal-network 2000
interface ethernet
ipx network 1001 ipx nlsp areal enable
interface ethernet
ipx network 2001 ipx nlsp area2 enable
access-list 1200 deny aaaa0000 ffff0000 access-list 1200 permit -l
ipx router nlsp areal area-address 1000 fffff000
ipx router nlsp area2 area-address 2000 fffff000 route- aggregation redistribute nlsp areal access-list 1200
Enhanced and RUP NLSP Route Aggregation for NLSP Version 1.1 IGRP Exampe
the router to connect two NLSP version 1.1 areas one The following example shows how to configure Enhanced IGRP area and one RIP area
ffff0000 not redistributed into Any routes learned via NLSP al that are represented by aaaa0000 are route routes learned via NLSP a2 as explicit routes Instead the router generates an aggregated Any routes into NLSP NLSP a2 that are represented by bbbb0000 ffff0000 are not redistributed as explicit routes learned via RIP that are by al Again the router generates an aggregated route Any represented a2 the router cccc0000 ffff0000 are not redistributed as explicit routes into NLSP al or NLSP Instead learned via Enhanced IGRP 129 that are by sends an aggregated route Likewise any routes represented the sends dddd0000 ffff0000 are not redistributed into NLSP al or NLSP a2 Again router an aggregated route
ipx routing ipx internal-network 2000
interface ethernet ipx network aaaa0000 ipx nlsp al enable
interface ethernet
ipx network bbbb0000 ipx nlsp a2 enable
interface ethernet ipx network cccc0000
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 167 Configuring Novell IPX
interface ethernet ipx network dddd0000
access-list 1200 deny aaaa0000 ffff0000 access-list 1200 permit -1
access-list 1201 deny bbbb0000 ffff0000 access-list 1201 permit -l
access-list 1202 deny cccc0000 ffff0000 access-list 1202 permit -l
access-list 1203 deny dddd0000 ffff0000 access-list 1203 permit -l
ipx router nlsp al area-address 10000 fffff000 route -aggregation redistribute nlsp a2 access-list 1201 redistribute rip access-list 1202 redistribute eigrp 129 access-list 1203
ipx router nlsp a2 area-address 2000 fffff000 route aggregation redistribute nlsp al access-list 1200 redistribute rip access-list 1202
redistribute eigrp 129 access-list 1203
ipx router eigrp 129 network dddd0000 redistribute nlsp al redistribute nlsp a2
NHRP Examples
The sections show following examples of how to configure NHRP
NHRP Example
NHRP over ATM Example
NHRP Example
logical NBMA network is considered the of interfaces and group hosts participating in NHRP and
having the same network identifier 16 illustrates Figure two logical NBMA networks shown as circles configured over single physical NBMA network Router communicates with Routers and because share they the same network identifier Router also communicates with Routers and because share network identifier they After address resolution is complete Router sends IPX to Router in and packets one hop Router sends them to Router in one hop as shown by the dotted lines
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 168 Configuring Novell IPX
One Network Figure 16 Two Logical NBMA Networks over Physical NBMA
Destination
network-id
Router
ipx nhrp network-id ipx nhrp network-id ipxnhrpnetwork-id7
ipx nhrp network-id ipx nhrp network-id
Source host
circuits Statically configured tunnel endpoints or permanent virtual
Dynamically created virtual circuits
of the five routers in 16 actually be that shown in Figure 17 The physical configuration Figure might host is connected to Router The same The source host is connected to Router and the destination network switch serves all five routers making one physical NBMA
CiscoiOS AppleTalk and Novell IPX Configuration Guide P2C 169 Configuring Novell IPX
Figure 17 Physical Configuration of Sample NBMA Network
Source host
Router
Router
Destination host
Refer to 16 before again Figure Initially NHRP resolves any NBMA addresses IPX packets from the
source host to the destination host travel all five routers connected to the switch through before reaching the destination When Router first forwards the IPX packet toward the destination host Router also an NHRP for the destination generates request hosts IPX address The request is forwarded to Router where is reply generated Router because it is the between replies egress router the two logical NBMA networks
Router NHRP its Similarly generates an request of own to which Router replies In this example IPX traffic between the subsequent source and the destination still requires two hops to traverse the NBMA network because the IPX traffic must be forwarded between the two logical NBMA networks
one would be if the Only hop required NBMA network was not logically divided
NHRP over ATM Example
The shows how to following example configure three routers using NHRP over ATM Router is with configured static route which it uses to reach the IPX network where Router resides Router reaches Router Router initially through Router and Router directly communicate without Router once resolves Router NHRP As and Router Cs respective NSAP addresses
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 170 Configuring Novell IPX
follow The significant portions of the configurations for Routers and
Configuration for Router
interface ATMO/0 map-group atm nsap-address li.llll.11.111111.llll.llll.l111.llll.llll.1111.ll atm rate-queue 10 atm pvc qsaal ipx network ipx nhrp network-id
map-list ipx l.0000.0c15.3588 atm-nsap 33.3333.33.333333.3333.3333.3333.3333.3333.3333.33
ipx route l.0000.OclS.3588
Configuration for Router
interface ATMO/0 map-group atm nsap-address 22.2222.22.222222.2222.2222.2222.2222.2222.2222.22 atm rate-queue 10 atm PVC qsaal ipx network ipx nhrp network-id
map-list ipx 2.0000.0c15.3628 atm-nsap 333333.33.333333.3333.3333.3333.3333.3333.3333.33
ipx route 2.0000.0C15.3628
Configuration for Router
interface ATMO/0 atm rate-queue 10 atm pvc qsaal
interface ATMO/0.l multipoint map-group atm nsapaddress 33333333333333.3333.3333.3333.3333.3333.3333.33 ipx network ipx nhrp network-id
interface ATMO/0.2 multipoint map-group atm nsapaddress 33333333.333333.3333.3333.3333.3333.3333.3333.33 ipx network ipx nhrp network-id
map-list ipx l.0000.Ocl5.4f80 atm-nsap ll.llll.ll.llllll.llll.llll.llll.llll.llll.llll.ll
map-list ipx 2.0000.Ocl5.5021 atm-nsap 22.2222.22.222222.2222.2222.2222.2222.2222.2222.22
Guide Cisco lOS AppleTalk and Novell IPX Configuration P2C 171 Configuring Novell IPX
IPX over WAN Examples
The following sections show examples of how to configure IPX over WAN and dial interfaces
IPX over WAN Interface Example
IPX over DDR Example
IPX over WAN Interface Example
When the you configure Cisco lOS software to transport IPX packets over serial interface that is WAN such X.25 running protocol as or PPP you specify how the packet will be encapsulated for This transport encapsulation is not the same as the encapsulation used on an IPX LAN interface
Figure 18 illustrates IPX over WAN interface
Figure 18 IPX over WAN Interface
Remote
Main router
The shows how to following example configure serial interface for X.25 encapsulation and for several IPX subinterfaces used in nonmeshed topology
Configuration for Main Router
hostname Main
no ip routing novell routing 0000.0c17.d726
interface ethernet
no ip address Novell network 100 media-type lOBaseT
interface serial
no ip address shutdown
interface serial
no ip address encapsulation x25 x25 address 33333 x25 htc 28
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 172 Configuring Novell IPX
interface serial 1.1 point-to-point no ip address novell network x25 map novell 2.0000.0c03.a4ad 11111 BROADCAST
interface serial 1.2 point-to-point
no ip address novell network x25 map novell 3.0000.0c07.5e26 55555 BROADCAST
Configuration for Router
hostname Remotel
no ip routing novell routing 0000.0c03.a4ad
interface ethernet
no ip address novell network
interface serial
no ip address encapsulation x25 novell network x25 address 11111 x25 htc 28 x25 map novell 2.0000.0c17.d726 33333 BROADCAST
Configuration for Router
hostname Remote2
no ip routing novell routing 0000.0c07.5e26
interface ethernet
no ip address novell network media-type loBaseT
interface serial
no ip address shutdown
interface serial
no ip address encapsulation x25 novell network x25 address 55555 x25 htc 28 x25 map novell 3.0000.0c17.d726 33333 BROADCAST
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 173 Configuring Novell IPX
IPX over DDR Example
In the shown in configuration Figure 19 an IPX client is separated from its server by DDR telephone line
Figure 19 IPX over DDR Configuration
Internal network 1234
Network 152001
Routing and service information is sent every 60 seconds The output RIP and SAP filters defined in this
filter these them from example updates preventing being sent between Router and Router If you
forwarded these packets each of the two routers would need to the other telephone once every 60 seconds On serial link whose based charges are on the number of packets sent this activity is generally not desirable This problem may not occur on dedicated serial line
Once the server and client have established contact the server will send watchdog keepalive packets When SPX is both the regularly used server and the client send keepalive packets whose purpose is to ensure that the connection between the server and the client is still functional these packets contain no other information Servers send watchdog packets approximately every minutes
If to the Router were allowed forward keepalive packets of the server to Router Router would
need to telephone Router every minutes just to send these packets Again on serial link whose are based the number of charges on packets sent this activity is generally not desirable Instead of having Router Router telephone only to send keepalive packets you can enable watchdog spoofing on Router The result will be that when the server connected to this router sends keepalive packets Router will behalf of the respond on remote client the client connected to Router When SPX is used enable of spoofing SPX keepalive packets on both routers and to inhibit the sending of them because
both the server and the client send keepalive packets
Use the ipx watchdog-spoof interface configuration command to enable and set the duration of
watchdog You can the number of consecutive hours spoofing specify spoofing is to stay enabled and the number of minutes is spoofing to stay disabled Use this command only on serial interface whose fast
switching and autonomous switching are disabled
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 174 Configuring Novell IPX
The following example shows how to configure Router Watchdog spoofing will be enabled for hour
and disabled for 20 minutes allowing the server tO clean up inactive connections before being enabled again
ipx routing 0000.0c04.4878
interface EthernetO ipx network 15200
interface SerialO PPP encap for DDRrecommended encapsulation ppp ipx network DD1DD2 Kill all rip updates ipx output-network-filter 801
Kill all sap updates ipx output-sap-filter 1001 fast-switching off for watchdog spoof ing no ipx route-cache Dont listen to rip ipx router-filter 866 Ipx watchdog spoof ing ipx watchdog-spoof 20 SPX watchdog spoof ing ipx spx-spoof Turn on DDR dialer in-band dialer idle-timeout 200 dialer map IP 198.92.96.132 name Rl3 7917 dialer map IPX DD1DD2.0000.0c03.e3c3 7917 dialer-group ppp authentication chap Chap authentication required pulse-time
access-list 801 deny FFFFFFFF access-list 866 deny FFFFFFFF Serialization packets access-list 900 deny FFFFFFFF FFFFFFFF 457 RIP packets access-list 900 deny FFFFFFFF 453 FFFFFFFF 453 SAP packets access-list 900 deny FFFFFFFP 452 FFFFFFFF 452 Permit everything else access-list 900 permit -l FFFFFFFF FFFFFFFF
access-list 1001 deny FFFFFFFF
Static ipx route for remote network ipx route DD1 DD1DD2.0000.0c03.e3c3
IPX will trigger the line up 9.21 and later dialer-list list 900
Guide Cisco lOS AppleTalk and Novell IPX Configuration P2C 175 Configuring Novell IPX
IPX Network Access Examples
The sections following show examples of how to control access to your IPX network The sections show
the configurations for various access lists and filters
IPX Network Access Example
Standard Named Access List Example
Extended Named Access List Time Range Example
SAP Input Filter Example
SAP Output Filter Example
GGS SAP Response Filter Example
IPX NetBIOS Filter Examples
PX Network Access Exampe
Using access lists to traffic is manage routing powerful tool in overall network control However it certain requires amount of planning and the appropriate application of several related commands 20 illustrates Figure network featuring two routers on two network segments
20 Figure Novell IPX Servers Requiring Access Control
Router Router
Novell Novell Novell seiver server client
aaOl .0000.0000.001 bbOl .0000.0000.001
want to clients and Suppose you prevent servers on Network aa from using the services on Network bb but want to allow the clients and you servers on Network bb to use the services on Network aa To achieve this would configuration you need an access list on Ethernet interface on Router that blocks all packets coming from Network aa and destined for Network bb You would not need any access list on Ethernet interface on Router
The following example shows how to configure Ethernet interface on Router
ipx routing
access-list 800 deny aa bbOl access-list 800 permit -l -l interface ethernet ipx network bb ipx access-group 800
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 176 Configuring Novell IPX
result the more The following example shows how you can accomplish the same as previous example You also the same efficiently by placing an input filter on interface Ethernet of Router can place
interface serial output filter on Router
ipx routing access-list 800 deny aa bbOl access-list 800 permit -1 interface ethernet
ipx network aa ipx access-group 800 in
fast turned Note When using access control list logging on an interface with switching on
slow not fast packets that match the access list and thus need to be logged are switched switched
Logging Access Control List Violations
of all control list violations using the The following example shows how you can keep log access by
keyword log at the end of the access-list command
access-list 907 deny -l -l 100 log
arrive the router from source in The previous example denies and logs all packets that at any any protocol
from any socket to any destination on network 100
The following example shows log entry for the access-list command
IPX-6--ACL 907 deny SPX B5A8 50.0000.0000.0001 B5A8 100.0000.0000.0001 10 pkts
matched list number 907 The In this example ten SPX packets were denied because they access packets for socket B5A8 were coming from socket B5A8 on networks 50.0000.0000.0001 and were destined on network 100.0000.0000.0001
Standard Named Access List Example
standard list named fred It denies communication The following example shows how to create access
with only IPX network number 5678
ipx access-list standard red deny 5678 any permit any
Extended Named Access List Time Range Example
how extended list named test It permits SPX traffic The following example shows to create an access between the hours of 800 and 600 only on Monday through Friday a.m p.m
time-range no-spx periodic weekdays 800 to 1800
ipx access-list extended test permit spx any all any all time-range no spx
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 177 Configuring Novell IPX
SAP Input Filter Example
SAP filters allow input router to determine whether to accept information about service Router Cl illustrated in Figure 21 will not accept and consequently not advertise any information about Novell server However Router Cl will accept information about all other servers on the network
3c Router C2 receives information about servers and
Figure 21 SAP Input Filter
Novell server NIC 0800.89A1.1527 3c01 .0000.0000.0001
Input SAP filter applied Novell to interface EU client 1811 .89A2.1543 Router C2 Router Cl
SO EU 3c
El El Novell server NIC 0800.89A0.6781 aa 4d 3c02.0000.0000.0001
Novell Novell Novell server server client NIC 0207.0104.0874 NIC 0800.1491.2207 0800.0123.1456 aaOl .0000.0000.0001 4d01 .0000.0000.0001
The shows how to following example configure Router Cl The first line denies server and the second line accepts all other servers
access-list 1000 deny 3c01.0000.0000.oOOl accesslist 1000 permit -1 interf ace ethernet ipx network 3c ipx input-sap-filter 1000 interface ethernet ipx network 4d interface serial ipx network 2b
Note NetWare versions 3.11 and later use an internal network and node number as their address for list access commands the first configuration command in this example
SAP Output Filter Example
SAP output filters are applied prior to the Cisco 105 software sending information out specific interface In the example that follows Router Cl in illustrated Figure 22 is prevented from advertising information about Novell server out interface Ethernet but can advertise server on network 3c
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 178 Configuring Novell IPX
Figure 22 SAP Output Filter
Novell server NIC 0800.89A1.1527 3c01 .0000.0000.0001
Novell client 181 l.89A2.1543
Router C2 Router Cl
cc E2 SO E0 3c
El El
Novell Output SAP server filters applied NIC 0800.89A0.6781 to interface El 3c02.0000.0000.0001
aa 4d
Novell Novell Novell client server server NIC 0207.0104.0874 NIC 0800.1491.2207 0800.0123.1456 aaOl .0000.0000.0001 4d01 .0000.0000.0001
The first line denies server All other The following example shows how to configure Router Cl
servers are permitted
access-list 1000 deny aaOl.0000.0000.0001 access-list 1000 permit -1 interface ethernet novell net 3c interface ethernet
ipx network 4d ipx output-sap-filter 1000 interface serial
ipx network 2b
GGS SAP RespoQse Filter ExampUe
filters shown in 23 allow router to determine whether to forward GGS SAP response as Figure
information it receives about service
IPX Guide Cisco lOS AppleTalk and Novell Configuration P2C 179 Configuring Novell IPX
Figure 23 GGS SAP Response Filter
Novell server
NIC 0800.89A0.1 527 3c01 .0000.0000.0001
II
GGS output SAP filter applied to interface El Novell server
NIC 0800.89A1 .1633 3c02.0000.0000.0001
______F Router
Novell client Novell server 0800.0123.456 NIC 0800.89A2.6781 3c03.0000.0000.0001
The shows how to following example configure GGS SAP response filters for Router When the client
issues GGS the filter denies request output GGS response from Novell Server and permits responses from Novell servers and
access-list 1000 deny 3cOl.0000.0000.000l access-list 1000 permit -l interface ethernet ipx network 3c interface ethernet ipx output-ggs-filter 1000 ipx network 10
IPX NetBIOS Filter Examples
The following example shows how to use NetBIOS host name to filter IPX NetBIOS frames The
example denies all outgoing IPX NetBIOS frames with NetBIOS host name of Boston on Ethernet interface
netbios access-list host token deny Boston netbios access-list host token permit
ipx routing 0000.Ocl7.d45d
interface ethernet ipx network 155 encapsulation ARPA ipx output-rip-delay 60 ipx triggered-rip-delay 30 ipx output-sap-delay 60 ipx triggered-sap-delay 30 ipx type-20 -propagation ipx netbios output-access-filter host token no mop enabled
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 180 Configuring Novell IPX
interface ethernet
no ip address ipx network 105
interface fddi
no ip address no keepalive ipx network 305 encapsulation SAP
interface serial
no ip address shutdown
interface serial
no ip address no keepalive ipx network 600 ipx output-rip-delay 100 ipx triggered-rip-delay 60 ipx output-sap-delay 100 ipx triggered-sap-delay 60 ipx type-2 0-propagation
NetBIOS frames This The following example shows how to use byte pattern to filter IPX example in which that all IPX permits IPX NetBIOS frames from IPX network numbers that end 05 means NetBIOS frames from Ethernet interface network 105 and FDDI interface network 305 will be forwarded by serial interface However this interface will filter out and not forward all frames from Ethernet interface network 155
netbios access-list bytes finigan permit 05
ipx routing 0000.Ocl7.d45d
ipx default-output-rip-delay 1000 ipx default-triggered-rip-delay 100 ipx default-output-sap-delay 1000 ipx default-triggered-sap-delay 100
interface ethernet
ipx network 155 encapsulation ARPA ipx output-rip-delay 55 ipx triggered-rip-delay 55 ipx output-sap-delay 55 ipx triggered-sap-delay 55 ipx type-20 -propagation media-type lOBaseT
interface ethernet
no ip address ipx network 105 ipx output-rip-delay 55 ipx triggered-rip-delay 55 ipx output-sap-delay 55 ipx triggered-sap-delay 55 media-type lOBaseT
Cisco lOS AppleTalk and Novell IPX Configuration_Guide P2C 181 Configuring Novell IPX
interface fddi
no ip address no keepalive ipx network 305 encapsulation SAP ipx output-sap-delay 55 ipx triggered-sap-delay 55
interface serial
no ip address shutdown
interface serial
no ip address no keepalive ipx network 600 ipx type-2 0-propagation ipx netbios input-access-filter bytes finigan
Helper Facilities to Control Broadcast Examples
The sections following show examples of how to control broadcast messages on IPX networks
Forwarding to an Address Example
Forwarding to All Networks Example
All-Nets Flooded Broadcast Example
that in the Note following examples is used This has been packet Type type chosen arbitrarily the actual to type use depends on the specific application
Forward ig to an Address Example
All broadcast packets are blocked the Cisco normally by lOS software However Type 20 propagation
packets be forwarded to certain may subject loop-prevention checks Other broadcasts may be directed to set of networks or host specific node on segment The following examples illustrate these options
Figure 24 shows router connected to several Cl Ethernet interfaces In this environment all IPX clients are attached to segment aa while all servers are attached to bb segments and dd In controlling broadcasts the following conditions are to be applied
Only Type and Type 20 broadcasts are to be forwarded
The IPX clients on network allowed aa are to broadcast via Type to any server on networks bb and dd
The IPX clients are allowed to broadcast via Type 20 to any server on network dd
______Cisco lOS AppleTalk and Novell IPX Configuration Guide P2 C-I 82 Configuring Novell IPX
Figure 24 IPX Clients Requiring Server Access Through Router
Novell Novell
client client
Novell
server 00b4.23cd.1 lOa
Novell
server 0090.aa23.efOl
shown in 24 The first line The following example shows how to configure the router Figure permits
broadcast traffic of Type from network aa The interface and network commands configure each commands broadcast specific interface The ipx helper-address interface configuration permit
forwarding from network aa to bb and from network aa to dd The helper list allows Type broadcasts
actual to to be forwarded Note that Type broadcasts are chosen as an example only The type use interface command is depends on the specific application The ipx type-20-propagation configuration
filter is to both the also required to allow Type 20 broadcasts The IPX helper-list applied Type packets forwarded 20 forwarded by the helper-address mechanism and the Type 20 packets by Type propagation
access-list 900 permit aa interface ethernet
ipx network aa ipx type-20 -propagation ipx helper-address bb.ffff.ffff.ffff ipx helper-address dd.ffff.ffff.ffff ipx helper-list 900 interface ethernet
ipx network bb interface ethernet ipx network dd ipx type-20 -propagation
network some This configuration means that any network that is downstream from aa for example
be able broadcast to network bb through Router Cl unless the arbitrary network aal will not to Type and aal to forward these broadcasts with series of routers partitioning networks aa are configured the for 24 These entries must be applied to configuration entries analogous to example provided Figure forward broadcasts between connected networks In this the input interface and be set to directly way network similar situation exists such traffic can be passed along in directed manner from network to
for Type 20 packets
interface command The following example shows how to rewrite the ipx helper-address configuration
line to direct broadcasts to server
ipx helper-address bb 00b4 23cd llOa Permits node-specific broadcast forwarding to Server at address 00b4.23cd.llOa on network bb
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 183 Configuring Novell IPX
Forwding to AU Networks ExampUe
In some networks it be to allow client nodes broadcast might necessary to to servers on multiple
networks If router to forward broadcasts all attached you configure your to networks you are flooding the interfaces In the environment illustrated in Figure 25 client nodes on network 2b1 must obtain services from IPX servers on networks and 5bb 3c2 4a1 through Router Cl To support this the requirement use flooding address -1 .ffff.ffff.ffff in your ipx helper-address interface configuration command specifications
Figure 25 Type Broadcast Flooding
Novell
server
3c2
Allows broadcast
flooding Novell from network 2b1 server
Novell
client
Novell
server
The first line in the following example shows how to permit traffic of Type from network 2b Then
the first interface is configured with network number The all-nets helper address is defined and the
list limits helper forwarding to Type traffic Type broadcasts from network 2b1 are forwarded to all connected networks directly All other broadcasts including Type 20 are blocked To permit broadcasts delete the ipx helper-list entry To allow Type 20 broadcast enable the ipx type-20-propagation interface configuration command on all interfaces
access-list 901 permit 2b1 interface ethernet ipx network 2b1 ipx helper-address -l.ffff.ffff.ffff ipx helper-list 901 interface ethernet ipx network 3c2 interface ethernet ipx network 4a1 interface ethernet ipx network 5bb
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 184 Configuring Novell IPX
AU-Nets Flooded Broadcast Example
interface As result of this The following example shows how to configure all-nets flooding on an
to all the configuration Ethernet interface will forward all broadcast messages except Type 20
networks it knows how to reach This flooding of broadcast messages might overwhelm these networks
with so much broadcast traffic that no other traffic may be able to pass on them
interface ethernet
ipx network 23 ipx helper-address -1 FFFF FFFF FFFF
PX Accounting Exampe
network that are connected via The following example shows how to configure two Ethernet segments enabled both the and serial link see Figure 26 On Router IPX accounting is on input output interfaces that is on Ethernet interface and serial interface which means that statistics are gathered
network and out the serial for traffic traveling in both directions that is out to the Ethernet link
and not the Ethernet On Router IPX accounting is enabled only on the serial interface on interface
the router the serial link which means that statistics are gathered only for traffic that passes out on Also will track all IPX traffic the accounting threshold is set to 1000 which means that IPX accounting 1000 and destination passing through the router up to source pairs
Figure 26 IPX Accounting Example
Router Router
Network C003 Network COOl
Configuration for Router
ipx routing interface ethernet
no ip address ipx network C003 ipx accounting interface serial
no ip address ipx network 200 ipx accounting
Configuration for Router
ipx routing interface ethernet
no ip address no keepalive ipx network COOl no mop enabled interface serial
no ip address ipx network 200 ipx accounting ipx accounting-threshold 1000
Guide Cisco lOS AppleTalk and Novell IPX Configuration P2C 185 Configuring Novell IPX
Cisco lOS and Novell IPX ______AppleTalk Configuration Guide P2C 186
network numbers P2C-17 BC Cisco lOS Bridging and IBM Networking Configuration Guide zones P2C-17 P2C-20
Guide DC Cisco lOS Dial Technologies Configuration IPx
FC Cisco lOS Configuration Fundamentals Configuration Guide configuration examples 176 to 183
IC Cisco 105 Interface Configuration Guide extended p2c-123
IPC Cisco 105 IP Routing Configuration Guide extended creating P2C-126 MWC Cisco lOS Mobile Wireless Configuration Guide implicit deny P2C-129 P2C Cisco 105 AppleTalk and Novell IPX Configuration Guide masks P2C-129 P3C Cisco lOS Apollo Domain Banyan VINES DECnet implicit
ISO CLNS and XNS Configuration Guide input P2C-124
QC Cisco 105 Quality of Service Solutions Configuration Guide named P2C-126
SC Cisco lOS Security Configuration Guide NetBIOS TC Cisco lOS Terminal Services Configuration Guide
creating P2C-129 P2C-134 VC Cisco lOS Voice Video and Fax Configuration Guide
description P2C-123 WC Cisco lOS Wide-Area Networking Configuration Guide
NLSP route P2C-123 XC Cisco lOS Switching Services Configuration Guide aggregation
routing table filtering P2C-131
SAP creating P2C-126
______standard P2C-123
Symbs standard creating P2C-126
time-based P2C-130 P2C-86 cr types P2C-123
violations logging P2C-126 P2C-128 command xxii
access-list additional-zones command P2C-19 to P2C-20
access-list command P2C-21 ______cable-range
access-list command
IPX AARP AppleTalk Address Resolution Protocol P2C-2 extended P2C-119 P2C-126 access control SAP P2C-126 AppleTalk P2C-16 to P2C-25 standard P2C-119 P2C-126 IPX P2C-123 to P2C-125 P2C-134 P2C-114 NLSP route aggregation filtering P2C-108 to access lists access-list includes command P2C-21 AppleTalk access-list network command P2C-20 P2C-21 cable ranges P2C-21 access-list other-access command P2C-21 configuration examples P2C-60 to access-list other-nbps command P2C-20 displaying P2C-55 access-list within command P2C-21 guidelines P2C-19 access-list zone command P2C-20
Guide Cisco lOS AppleTalk and Novell IPX Configuration ______P2 C-I 89 Index
accounting ATP P2C-2 IPX AURP P2C-15 P2C-28
P2C-1 52 configuring configuring P2C-28
database threshold P2C-153 enabling P2C-28
P2C-153 enabling last-heard-from timer P2C-29
filters P2C-153 private path database displaying P2C-55
transit entries P2C-153 maximum routing update interval P2C-29
Address Resolution Protocol ARP tunneling P2C-29
AppleTalk P2C-42 update-events queue displaying P2C-55
addresses cable ranges
AppleTalk P2C-9 definition P2C-9
example P2C-1O interfaces assigning P2C-13
network numbers P2C-9 remapping P2C-52
IPX P2C-81 CAP P2C-33
example P2C-82 checksums
network numbers P2C-81 generation and verification disabling P2C-42
node numbers P2C-81 Ciscos implementation P2C-3
AEP AppleTalk Echo P2C-2 Protocol concurrent routing and bridging CRB P2C-16
AppleTalk configuration P2C-11
access control P2C-16 to P2C-25 configuration examples P2C-57 to P2C-76
access lists CRB P2C-16
cable ranges P2C-21 DDP P2C-2
configuration examples P2C-60 to P2C-70 DDR P2C52
displaying P2C-55 definition P2C-2
guidelines P2C-19 discovery mode
network numbers P2C-17 example P2C-58
zones P2C-1 P2C-20 interfaces
addresses dynamic P2C-13
definition P2C-9 extended P2C-14
P2C-1O example nonextended P2C-14 P2C-58
network numbers P2C9 domains P2C-49
remapping P2C-52 domain router configuration P2C-50
adjacent networks P2C-55 domain router configuration figure P2C-50
adjacent routers P2C-55 encapsulation P2C-3 P2C-4 P2C-8 P2C-30 P2C-35
AEP P2C-2 Enhanced IGRP P2C-15
ARP P2C-2 active state time limit adjusting P2C-49
table ARP bandwidth P2C-49
See ARP table AppleTalk example P2C-77
ATCP P2C-38 Ciscos implementation P2C-3 P2C-46
CiscolOS AppleTalk and Novell IPX Configuration Guide P2C 190 Index
filters P2C-23 configuration examples P2C-59 routing update
free-trade disabling P2C-46 zone
P2C-26 enabling P2C-15 P2C-28 P2C-46 establishing
features P2C-45 example P2C-66
P2C-4 P2C-43 hello packets P2C-48 gleaning
hold time P2C-48 GZL
filters P2C-25 interfaces displaying P2C-55 P2C-24
neighbor adjacencies logging P2C-49 replies P2C-24
and neighbors displaying P2C-55 integrated routing bridging
route redistribution P2C-47 See AppleTalk IRB
InterPo1l P2C-56 routing protocol enabling P2C-46
P2C-49 split horizon P2C-48 interenterprise routing
P2C-52 topology table P2C-55 addresses remapping enhancements P2C-3 AURP example P2C-71
cable P2C-52 Ethernet card using P2C-11 ranges remapping
P2C-71 EtherTalk P2C-2 P2C-11 configuration example extended interfaces domain information P2C-55
domain names P2C-51 cable range assigning P2C-13
numbers P2C-51 configuration example P2C-58 domain
P2C-51 proxy network numbers P2C-41 domains P2C-49
P2C-52 routing P2C-12 P2C-14 P2C-15 hop count
interfaces P2C-51 routing example P2C-58
P2C-55 zones names P2C-13 remapping extended network definition P2C-8 split horizon P2C-50
interface status P2C-55 fast switching
cache entries P2C-55 interfaces P2C-12 P2C-13
interfaces P2C-44 Internet Router software P2C-11
P2C-55 FDDITaIk P2C-2 internetwork parameters
IPTalk pre-FDDITaIk packets P2C-54 filters /etc/services file P2C-36
address mapping P2C-35 data packet P2C-22 AppleTalk-to-IP
P2C-73 to P2C-76 example P2C-60 configuration example
zones P2C-22 definition P2C-33
IP P2C-37 GZL P2C-24 P2C-25 encapsulation
node identifier P2C-75 partial zones P2C-25
example P2C-64 SLIP drivers P2C-33
P2C-35 routing P2C-23 tunneling
numbers P2C-36 routing table P2C-24 UDP port
IRB P2C-16 routing table example P2C-60
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 191 Index
K-Star Shiva FastPath routers P2C-1 packets P2C-35
LANE P2C-3 performance tuning P2C-39
load sharing round-robin P2C-42 Phase
LocalTalk P2C-2 comparison with Phase P2C-8
logical cable P2C-9 compatibility with Phase P2C-1O MacIP definition P2C-7
address ranges P2C-32 Phase
addresses P2C-33 comparison with Phase P2C-8
advantages P2C-31 compatibility with Phase P2C-1O
clients P2C-55 definition P2C-7
configuration requirements P2C-31 pre-FDDITaIk packets enabling P2C-54
definition P2C-30 proxy network numbers
disadvantages P2C-31 example P2C-76
examples P2C-12 interoperability P2C-41
implementation P2C-31 responder support P2C-4 P2C-56
servers P2C-32 P2C-55 round-robin load sharing enabling P2C-42
traffic P2C-55 routing
maximum paths P2C-42 setting enabling
MIB P2C-3 on nonextended interface dynamically P2C-14 monitoring tasks P2C-54 on nonextended interface manually P2C-12 name binding example P2C-58
See AppleTalk NBP extended interfaces enabling dynamically P2C-14
NBP P2C-2 P2C-26 extended interfaces enabling manually P2C-12
name registration task table P2C-55 routing process P2C-15
services P2C-55 routing protocols specifying P2C-28
neighbor table entries P2C-54 deleting routing tables P2C-55
network connectivity testing P2C-55 entries P2C-54
network P2C-44 events logging update filters P2C-23
definition P2C-9 network update timers P2C-41
nondiscovery-mode interface P2C-1 routing updates P2C-40
nonextended interface interval timer P2C-41
addresses assigning P2C-12 routes with no zones advertising P2C-40
routing P2C-58 example strict checking P2C-39
P2C-12 routing enabling stub mode P2C-40
zone names assigning P2C-12 timers P2C-41
nonextended interfaces RTMP P2C-2 P2C-15
network numbers P2C-41 proxy enabling P2C-28
routing P2C-1 routes with no zones advertising P2C-40
nonextended network definition P2C-8 routing updates P2C-40
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2 C-I 92 Index
services P2C-2 strict checking P2C-39 standard AppleTalk
stub mode P2C-40 zones P2C-1O P2C-13 seed router P2C-14 information table P2C-55
Shiva FastPath routers P2C-11 name format P2C-1O
P2C-1O SMRP special characters
command P2C-22 fast switching P2C-38 appletalk access-group
address command P2C-12 fast switching cache table P2C-54 appletallc
forwarding table P2C-55 AppleTalk Address Resolution Protocol
global information P2C-56 ARP table AppleTalk ARP group table P2C-56 See AppleTalk
P2C-43 neighbor table P2C-56 appletalk arp interval command
retransmit-count command P2C-43 port table P2C-56 appletalk arp
timeout command P2C-43 routing table P2C-56 appletalk arp
command P2C-29 SNMP appletalk aurp update-interval
command P2C-29 configuration example P2C-72 appletalk aurp-tickle-time
command P2C-13 to P2C-16 P2C-21 configuring P2C-21 appletalk cable-range
checksum command P2C-42 sockets displaying P2C-55 appletalk
static routes appletalk client-mode command P2C-38
command P2C-1 P2C-1 defining P2C-53 appletalk discovery
distribute-list in command P2C-23 displaying P2C-55 appletalk
distribute-list out command P2C-24 test mode entering P2C-56 appletalk
command P2C-52 TokenTalk P2C-2 appletalk domain hop-reduction
traffic P2C-55 appletalk domain name command P2C-51
domain command P2C-52 traffic statistics resetting P2C-54 appletalk remap-range
transition mode P2C-15 appletalk eigrp active-time command P2C-49
command P2C-49 example P2C-65 appletalk eigrp log-neighbor-changes
command P2C-48 tunneling appletalk eigrp split-horizon
P2C-48 AURP P2C-29 appletalk eigrp timers command
command P2C-49 Cayman P2C-30 appletalk eigrp-bandwidth-percentage
P2C-44 GRE P2C-30 appletalk event-logging command P2C-27
command P2C-26 Update Routing Protocol appletalk free-trade-zone
P2C-24 See AppleTalk AURP appletalk getzonelist-filter command
command P2C-43 VLANs P2C-3 appletalk glean-packets
command P2C-36 WAN protocols supported P2C-3 appletalk iptalk-baseport
command P2C-26 ZIP appletalk lookup-type
command P2C-33 query interval P2C-43 appletalk macip dynamic
server command P2C-32 reply filters appletalk macip
static command P2C-33 configuration example P2C-71 appletalk macip
command P2C-42 overview P2C-25 appletalk maximum-paths
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 193 Index
appletalk name-lookup-interval command P2C-26
appletalk permit-partial-zones command P2C-25
appletalk pre-fdditalk command P2C-54 backup server table
appletallc protocol command P2C-15 P2C-28 P2C-46 IPX Enhanced IGRP P2C-94
appletalk proxy-nbp command P2C-41 bandwidth AppleTalk Enhanced IGRP P2C-49
appletalk require-route-zones command P2C-40 bridge crb command P2C-16 P2C-86
appletalk route-cache command P2C-44 broadcasts
appletalk route-redistribution command P2C-28 P2C-47 IPX
appletalk routing command P2C-12 P2C-27 P2C-46 forwarding P2C-134 P2C-138 P2C-148
appletallc rtmp jitter command P2C-41 type 20 packets P2C-136 P2C-137
appletalk rtmp-stub command P2C-40
appletalk send-rtmp command P2C-40
appletalk static cable command P2C-53
static net command P2C-53 appletalk cable ranges
appletalk command P2C-39 See cable strict-rtmp-checking AppleTalk ranges
timers command P2C-41 appletalk carriage return cr xxiii
Transaction Protocol AppleTalk P2C-2 cautions usage in text xviii
Transaction AppleTalk Protocol ATP P2C-2 checksums AppleTalk P2C-42
AppleTalk Update Routing Protocol Cisco lOS configuration changes saving xxvi
See AppleTalk AURP clear appletalk arp command P2C-54
virtual-net command appletalk P2C-38 clear appletalk neighbor command P2C-54
command P2C-43 appletalk zip-query-interval clear appletalk route command P2C-54
appletalk zip-reply-filter command P2C-25 clear appletalk traffic command P2C-54
zone command appletalk P2C-12 P2C-13 P2C-15 P2C-16 clear ip nhrp command P2C-1 58 P2C-27 clear ipx accounting command P2C-158 area-address command P2C-96 P2C-107 P2C-115 clear ipx cache command P2C-155 ARP clear ipx nlsp neighbors command P2C-157 ARP cache clear ipx route command P2C-155 See ARP table clear ipx traffic command P2C-155 ARP table clear smrp mcache command P2C-54 AppleTalk clock ticks IPX P2C-141 entries P2C-54 Columbia AppleTalk Package CAP P2C-33 gleaning P2C-43 command modes understanding xxi to xxii update interval P2C-43 command syntax ARP AppleTalk P2C-2 conventions xvii
ATCP AppleTalk Control Protocol async displaying example xxiii interfaces P2C-38 commands ATM fast switching IPX P2C-121
context-sensitive help for abbreviating xxii
default form using xxv
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 194 Index
See interenterprise routing no form using xxv AppleTalk configurations saving xxvi
CRB concurrent routing and bridging P2C-16
CSNP complete sequence number PDU
command P2C-151 See also NLSP eigrp log-neighbor-adjacency-changes
encapsulation
AppleTalk P2C-3 P2C-4 P2C-8 P2C-30 P2C-35
IPX P2C-4 P2C-83 to P2C-97
command P2C-38 DDP Datagram Delivery Protocol P2C-2 encapsulation ppp Enhanced IGRP DDR dial-on-demand routing
P2C-86 AppleTalk P2C-52 IPX configuring
Interior Protocol EIGRP example P2C-77 Enhanced Gateway Routing
IPX AppleTalk configuring P2C-44
P2C-122 configuring P2C-86 generation of packets disabling IPX NLSP NetWare Link Services Protocol route spoofing P2C-122 redistribution P2C-91 P2C-116 watchdog packets P2C-121 example 166 sPx /etc/services file P2C-36 spoofing P2C-122 EtherTalk P2C-2 P2C-11 watchdog packets P2C-122 extended access lists IPX default routes
See access lists IPX specifying P2C-150 extended networks AppleTalk P2C-8 understanding P2C-83
discovery mode
interfaces
dynamic P2C-13
fast switching extended P2C-14
AppleTalk P2C-44 nonextended P2C-14 cache entries P2C-55 distribute-list in command P2C-92 P2C-94
description P2C-1 49 distribute-list out command P2C-92 IPX distribute-sap-list out command P2C-93 cache entries deleting P2C-155 documentation
cache entries displaying P2C-155 conventions xvii
directed broadcast packets P2C-148 feedback providing xix disabling P2C-149 modules xiii to xv
over ATM P2C-121 online accessing xviii over Frame Relay P2C-121 ordering xviii over SMDS P2C-121 Documentation CD-ROM xviii
FastPath router documents and resources supporting xvi AppleTalk P2C-35 domains
Cisco lOS AppleTalk and Novell IPX Configuration Guide Index
K-Star P2C-11
FDDI IPX encapsulation P2C-84
FDDITa1k P2C-2 P2C-54 GGS Get General Service
Feature Navigator filters P2C-132
See platforms supported global configuration mode summary of xxii
filtering output show and more commands xxvi GNS Get Nearest Server
filters filters P2C-132
AppleTalk request response delay P2C-146
data packet requests P2C-146
example P2C-60 GZL GetZoneList
zones P2C-22 replies P2C-24
GZL P2C-24 P2C-25
partial zones P2C-25
example P2C-64
PZC-23 routing hardware platforms
table P2C-24 routing See platforms supported
table routing example P2C-60 header compression IPX P2C-122
filters P2C-23 routing update hello packets IPX AppleTalk Enhanced IGRP P2C-48
broadcast P2C-134 IPX Enhanced IGRP intervals P2C-90
generic P2C-131 IPX Enhanced IGRP timers P2C-90
P2C-132 GNS help command xxii
NetBIOS P2C-134 P2C-133 helper addresses
overview P2C-123 IPX P2C-134
routing table P2C-131 example 182
SAP P2C-132 hold time
IPX Enhanced IGRP AppleTalk Enhanced IGRP P2C-48
route updates P2C-92 IPX Enhanced IGRP P2C-90
routes P2C-92
SAP updates P2C-94
SAP P2C-116 floating static routes IPX P2C-141 IDP Internet Datagram Protocol flooded broadcasts IPX P2C-148 characteristics P2C-4
Frame Relay IGRP Interior Gateway Routing Protocol
fast switching IPX P2C-121 Cisco implementation P2C-46 free-trade zone indexes master xvi
AppleTalk interface command P2C-28 P2C-36
establishing P2C-26 interface configuration mode summary of xxii example P2C-66 interface tunnel command P2C-28 P2C-30
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2 C-I 96 Index
IP encapsulation of AppleTalk P2C-36 accounting
Internet Router software requirements P2C-1 configuring P2C-152
address command P2C-36 ip database entries deleting P2C-158
IP AppleTalk-to-IP address mapping P2C-35 database entries displaying P2C-158
IPTalk database threshold P2C-153
/etc/services file P2C-36 enabling P2C-153
AppleTalk-to-IP address mapping P2C-35 example 185
configuration example P2C-73 to P2C-76 filters P2C-153
description P2C-33 maximum transit entries P2C-1 53
IP encapsulation P2C-37 addresses P2C-81
SLIP drivers P2C-33 broadcasts P2C-98
UDP port numbers P2C-36 blocking P2C-147
IPX forwarding P2C-134 P2C-138 P2C-148
control violation access logging examples 117 type 20 packets P2C-136 P2C-137
access control configuring P2C-134 clock ticks P2C-1 41
access lists compliance with Novells IPX P2C-135
configuration examples 176 to 183 configuration examples 159 to 164
extended P2C-123 configuration task list P2C-82
extended applying time ranges P2C-130 DDR P2C-121 P2C-122
extended creating P2C-126 default routes
filtering SAP P2C-128 See NLSP default routes
implicit deny P2C-129 default routes specifying P2C-150
implicit masks P2C-129 default routes understanding P2C-83
named disabling P2C-139 P2C-151 P2C-152
creating P2C-126 encapsulation P2C-4 P2C-83 to P2C-97
extended P2C-128 IEEE interfaces table P2C-84
NLSP route aggregation P2C-129 Enhanced IGRP P2C-88
SAP P2C-128 backup server table P2C-94
standard P2C-127 Cisco implementation P2C-5
NetBIOS enabling example 163
creating P2C-129 features P2C-87
description P2C-123 filters P2C-92
route NLSP aggregation P2C-123 route updates P2C-92
routing table filtering P2C-131 SAP updates P2C-94
SAP creating P2C-126 hello packets intervals P2C-90
standard P2C-123 hello packets timers P2C-90
standard creating P2C-126 hold time P2C-90
types P2C-123 queries P2C-94
violations logging P2C-126 P2C-128 redistribution P2C-91
Cisco lOS AppleTalk and Novell IPX Configuration Guide
P2C 197 Index
routes P2C-92 failed link P2C-123
SAP network numbers P2C-122
updates example 164 PPP P2C-122
SAP updates P2C-92 static routing P2C-123
horizon P2C-91 split keepalives P2C-121 P2C-122
task list P2C-88 LANE support P2C-5
P2C-90 timers adjusting load sharing
Enhanced IGRP enabling P2C-88 per-host P2C-147
fast switching round-robin P2C-146
cache entries P2C-155 deleting maximum paths
directed broadcast packets P2C-148 description P2C-146
disabling P2C-149 setting P2C-146 P2C-147
over ATM P2C-121 messages
over Frame P2C-121 Relay filtering NetBIOS P2C-134
FDDI P2C-84 messages filtering NetBIOS P2C-134
filtering P2C-106 MIB P2C-5
filters MLS support P2C-5
broadcast P2C-134 monitoring tasks P2C-154
generic P2C-131 multicasts P2C-97
to interface P2C-132 GGS applying Multilayer Switching
GNS P2C-132 See IPX MLS support
NetBIOS P2C-134 NetBIOS
description P2C-133 access control P2C-133
overview P2C-123 filters P2C-133
table routing P2C-131 filters example 180
SAP P2C-132 messages filtering P2C-134 flooded broadcasts P2C-148 network access P2C-123 to P2C-125 GNS network connectivity testing P2C-156
control requests P2C-146 network numbers
filters P2C-132 definition P2C-81
queue length SAP requests P2C-143 interfaces P2C-83
request response delay P2C-146 node numbers P2C-81
header compression P2C-122 Novell IPX compliance P2C-135
helper addresses P2C-134 packets padding P2C-151
182 example performance tuning P2C-135
P2C-134 specifying per-host load sharing enabling P2C-147
interfaces status P2C-155 displaying ping type selecting P2C-155
IPXWAN PPP P2C-122
P2C-122 disabling restarting P2C-139 P2C-151 P2C-152
Cisco lOS and Novell ______AppleTalk IPX Configuration Guide P2C 198 Index
RIP split horizon P2C-93
static P2C-143 description P2C-140 entries configuring
entries PZC-143 updates table static
P2C-93 delay between P2C-139 updates P2C-92
P2C-1 44 delays P2C-141 setting P2C-1 43
timers P2C-1 41 secondary networks
161 round-robin load sharing enabling P2C-146 configuration example route aggregation See NLSP shutting down example 161 route cache invalidation P2C-150 servers displaying P2C-155 route cache size P2C-149 spoofing P2C-121 P2C-122
routing static routes
between emulated LANs P2C-5 description P2C-140
enabling floating P2C-141
P2C-1 41 example 159 overriding
to P2C-1 40 on multiple networks P2C85 routing table adding
on multiple networks example 160 subinterfaces
on routers P2C-83 configuration example 160
over WAN interface example 172 configuring P2C-85
P2C-97 metrics P2C-4 configuring multiple encapsulations on
routing protocols NLSP P2C-97
EIGRP P2C-86 shutting down example 160
NLSP P2C-104 tick count P2C-141
RIP P2C-140 traffic displaying statistics P2C-155
routing table entries type 20 packets
adding P2C-131 accepting P2C-137
P2C-137 deleting P2C-155 forwarding P2C-136
P2C-5 displaying P2C-155 VLAN support
SAP P2C-4 watchdog packets P2C-121 P2C-122
command P2C-131 access lists creating P2C-126 ipx access-group P2C-124
access-list command P2C-108 P2C-127 P2C-128 P2C-129 delay between packets ipx
command P2C-153 setting P2C-139 ipx accounting
command P2C-153 delay between packets setting P2C-138 P2C-139 ipx accounting-list
command P2C-153 delay setting P2C-144 ipx accounting-threshold
command P2C-1 53 filtering P2C-126 ipx accounting-transits
filters P2C-132 ipx advertise-default-route-only command P2C-151
command P2C-94 filters example 178 ipx backup-server-query-interval
command P2C-89 messages filtering P2C-132 ipx bandwidth-percent eigrp
command P2C-148 queue length setting P2C-143 ipx broadcast-fastswitching
P2C-145 command P2C-138 P2C-142 responses to GNS requests controlling ipx default-output-rip-delay
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 199 Index
ipx command default-output-sap-delay P2C-138 P2C-144 ipx maximum-paths command P2C-146 P2C-147 command ipx default-ping P2C-155 ipx netbios input-access-filter command P2C-134
ipx default-route command P2C-150 ipx netbios output-access-filter command P2C-134
ipx command default-triggered-rip-delay P2C-138 ipx network command P2C-84 P2C-86 P2C-96 P2C-97 P2C-142 P2C-122 P2C-152
ipx default-triggered-sap-delay command P2C-138 ipx nhrp authentication command P2C-118 P2C-144 ipx nhrp holdtime command P2C-12O ipx delay command P2C-141 ipx nhrp interest command P2C-119 IPX Display and Debug Enhancements configuration ipx nhrp map command P2C-118 P2C-158 GGS SAP response filter example 179 ipx nhrp max-send command P2C-119
GGS SAP response filters P2C-132 ipx nhrp network-id command P2C-117 IPX traffic statistics P2C-154 ipx nhrp nhs command P2C-118 watchdog spoofing P2C-121 ipx nhrp record command P2C-120 watchdog spoofing example 174 ipx nhrp responder command P2C-120 ipx down command P2C-139 P2C-151 ipx nhrp use command P2C-119 IPX Enhanced IGRP ipx nlsp csnp-interval command PZC-1O1 bandwidth examples 165 ipx nlsp enable command P2C-96 P2C-97
interfaces displaying P2C-156 P2C-107 to P2C-115
P2C-1 56 monitoring ipx nlsp hello-interval command P2C-100 P2C-1O1
neighbor P2C-157 adjacency changes logging ipx nlsp Isp-interval command P2C-1O1
neighbors displaying P2C-156 ipx nlsp metric command P2C-99
table entries P2C-156 routing displaying ipx nlsp multicast command P2C-98
table P2C-156 topology ipx nlsp priority command P2C-100
traffic statistics P2C-156 displaying ipx nlsp rip command P2C-116
ipx gns-reply-disable command P2C-146 ipx nlsp sap command P2C-116
ipx command gns-response-delay P2C-146 ipx nlsp-retransmit-interval command P2C-1O1
ipx gns-round-robin command P2C-146 ipx output-ggs-filter command P2C-133
ipx hello-interval command P2C-90 ipx output-gns-filter command P2C-132
ipx helper-address command P2C-134 P2C-138 P2C-148 ipx output-network-filter command P2C-131
command P2C-134 ipx helper-list ipx output-rip-delay command P2C-138 P2C-139 P2C-142
ipx hold-time command P2C-90 eigrp ipx output-sap-delay command P2C-138 P2C-139 P2C-144
ipx command input-network-filter P2C-131 ipx output-sap-filter command P2C-132
ipx command P2C-132 input-sap-filter ipx pad-process-switched-packets command P2C-151
internal-network command ipx P2C-96 ipx per-host-load-share command P2C-147
ipx ipxwan command P2C-122 ipx rip-max-packetsize command P2C-142 P2C-144
error command ipx ipxwan P2C-123 ipx rip-multiplier command P2C-1 42 ipx static command P2C-123 ipxwan ipx route command P2C-140 P2C-141 command ipx link-delay P2C-99 ipx route-cache command P2C-149 P2C-151 ipx command P2C-1 45 linkup-request ipx route-cache inactivity-timeout command P2C-150
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 200 Index
ipx route-cache max-size command P2C-149 ipx router command P2C-88 P2C-91 P2C-96 P2C-116
LANE Emulation ipx router eigrp command P2C-112 P2C-113 LAN
emulated routing between P2C-3 P2C-5 ipx router nlsp command P2C-98 P2C-1O7 to P2C-115 LANs
link-state packet ipx router-filter command P2C-131 LSP
See LSP ipx router-sap-filter command P2C-132 NLSP
LocalTalk P2C-2 ipx routing command P2C-83
log-adjacency-changes command P2C-102 P2C-157 ipx sap command P2C-143
command P2C-1O1 ipx sap-incremental command P2C-92 lsp-gen-interval
command P2C-1O1 ipx sap-incremental split-horizon command P2C-93 lsp-mtu
command P2C-1O1 ipx sap-max-packetsize command P2C-142 lsp-refresh-interval ipx sap-multiplier command P2C-144 ipx sap-queue-maximum command P2C-143 ipx split-horizon command P2C-92 ipx throughput command PZC-99 MacIP ipx triggered-rip-delay command P2C-138 P2C-142 address ranges P2C-32
ipx triggered-sap-delay command P2C-138 P2C-144 addresses P2C-33
P2C-31 ipx type-20-helpered command P2C-138 advantages
ipx type-20-input-checks command P2C-131 AppleTalk traffic P2C-55
ipx type-20-output-checks command P2C-137 clients P2C-5
ipx type-20-propagation command P2C-136 P2C-139 description P2C-30
P2C-31 ipx update interval command P2C-142 P2C-144 disadvantages
ipx update sap-after-rip command P2C-145 implementation P2C-31
P2C-31 ipx watchdog-spoof command P2C-121 requirements
IPXWAN servers P2C-32 P2C-55
See IPX IPXWAN maximum paths
IRB Integrated Routing and Bridging AppleTalk setting P2C-42
interfaces P2C-86 IPX
IPX P2C-86 description P2C-146
setting P2C-146 PZC-147
max-lsp-lifetime command P2C-1 01
messages
access list violation P2C-128 keepalives
P2C-128 IPX watchdog packets P2C-121 logging
SPX P2C-122 metrics
Kinetics FastPath router KIP software P2C-35 routing
K-Star Shiva FastPath routers P2C-1 IPX P2C-4
XNS PZC-4
Cisco lOS AppleTalk and Novell IPX Configuration Guide ZiU Index
MIB enabling P2C-1 17
AppleTalk P2C-3 IPX
IPX P2C-5 holdtime P2C-120
P2C-95 NLSP initiation controlling P2C-119
online xvi MIB descriptions ioop detection P2C-120
modes next hop server P2C-120
See command modes packet rate P2C-119
multicast command P2C-98 record options suppressing P2C-120
requests triggering P2C-119
time addresses P2C-120
NHRP Next Hop Resolution Protocol for IPX
name display facility AppleTalk P2C-26 access lists P2C-119
named IPX access lists P2C-126 authentication P2C-118
NBP Name Binding Protocol P2C-2 cache
definition P2C-3 P2C-26 dynamic entries clearing P2C-158
description P2C-26 monitoring P2C-158
name registration task table P2C-55 static entries clearing P2C-158
services P2C-55 initiation controlling P2C-119
neighbor adjacency changes logging next hop server P2C-118
AppleTalk Enhanced IGRP P2C-49 static IPX-to-NBMA address mapping P2C-118
IPX Enhanced IGRP P2C-157 task list P2C-117
NetBIOS traffic monitoring P2C-158
IPX NLSP Multicast Support
filtering messages P2C-134 node numbers IPX P2C-81
netbios access-list command P2C-129 NLSP NetWare Link Services Protocol P2C-101
NetBIOS IPX P2C-133 adjacencies P2C-157
control access P2C-133 adjacency state P2C-157
filters example 180 CSNP interval specifying P2C-89 P2C-100 P2C-101
messages filtering P2C-134 database P2C-157 NetWare Link Services Protocol NLSP default routes advertising P2C-151
Enhanced IGRP route redistribution P2C-91 designated router
example 166 definition P2C-100
RIP packets election priority specifying P2C-100
processing P2C-116 pseudonode P2C-100 network command P2C-88 P2C-112 P2C-113 Enhanced IGRP route redistribution P2C-116 network numbers IPX P2C-81 GNS queries replying to P2C-146
Next Hop Resolution Protocol NHRP for IPX hello interval specifying P2C-100 P2C-101
next hop server P2C-118 hop count maximum from RIP updates P2C-89 PZC-100
NHRP Next Hop Resolution Protocol
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 202 Index
interface enabling on NLSP 1.1 Enhanced IGRP and RIP example 167
LAN P2C-96 path selection P2C-106
WAN P2C-97 RIP and NLSP 1.1 configuring P2C-114 internal network number setting P2C-96 route summaries P2C-103 link delay specifying PZC-99 route summarization P2C-104
LSP link-state packet P2C-101 service selection P2C-106 metric specifying P2C-99 single versus multiple areas P2C-103
MIB P2C-95 route aggregation configuring P2C-102 multicast addressing SAP
disabling P2C-98 entries aging out P2C-144
disabling examples 165 packets maximum size P2C-142
multiple encapsulations P2C-85 P2C-97 shortest path first algorithm SPF
neighbors P2C-157 calculation interval P2C-101
partial route calculation setting interval P2C-102 subinterf aces P2C-85 P2C-97
pseudonode P2C-100 configuration example 160
RIP entries aging out P2C-142 shutting down example 160
RIP packets throughput specifying P2C-99
maxiiiium size P2C-144 nonbroadcast multiaccess NBMA network
route aggregation addresses advertised P2C-120
aggregated routes P2C-103 logical versus physical figure 169
area addresses P2C-102 nonbroadcast multiaccess network
area addresses and route summaries P2C-103 See NBMA network
areas P2C-103 to P2C-104 nonextended network AppleTalk P2C-8
benefits P2C-104 notes usage in text xviii
configuration task list P2C-106 Novell IPX
customized route summarization P2C-105 See IPX
default route redistribution P2C-104
default route summarization P2C-105
Enhanced IGRP and NLSP 1.1 P2C-111
filtering and route summarization padding packets IPX P2C-151
relationship P2C-106 Phase
multiple NLSP 1.1 areas See AppleTalk Phase example 166 Phase
multiple NLSP 1.1 areas configuring P2C-106 See AppleTalk Phase multiple NLSP versions in single area ping command mixing P2C-103
AppleTalk P2C-55 NLSP 1.1 and NLSP 1.0 areas
IPX P2C-156 example 166
NLSP 1.1 and NLSP 1.0 areas configuring P2C-109
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 203 Index
platforms supported linking to SAP P2C-145
Feature xxvii Navigator identify using linking to SAP updates P2C-144
release notes identify using xxvii ROM monitor mode summary of xxii
IPX P2C-122 PPP route aggregation configuring NLSP
priority-list protocol command P2C-20 See NLSP
of xxii privileged EXEC mode summary route cache invalidation controlling P2C-150
prompts system xxii route cache size P2C-149
proxy network numbers route redistribution
example P2C-76 Enhanced IGRP and NLSP example 166
P2C-41 interoperability Enhanced IGRP NLSP configuring P2C-116
pseudonode NLSP P2C-100 Enhanced IGRP NLSP P2C-91
See also redistribution
route-aggregation command P2C-1O7 to P2C-115
routes
question mark command xxii static IPX P2C-140
routing table
AppleTalk
update timers P2C-41 redistribute command P2C-91 P2C-116 IPX P2C-131 P2C-155
route aggregation P2C-1O8 P2C-11O P2C-114 P2C-115 routing tables redistribution AppleTalk P2C-55
AppleTalk Enhanced IGRP P2C-47 controlling P2C-39
IPX Enhanced IGRP P2C-91 update timers P2C-41 release notes AppleTalk update filters P2C-23
See platforms supported RTMP Routing Table Maintenance Protocol P2C-2 responder support AppleTalk P2C-56 definition P2C-2
RFC interfaces P2C-15
full text obtaining xvi routes with no zones advertising P2C-40
RFC 1243 P2C-3 routing tables update timers P2C-41
RFC 1553 IPX header compression over WAN routing updates P2C-40 media P2C-122 strict checking P2C-39
RFC 1634 P2C-122 stub mode P2C-40 RIP
IPX
description P2C-140
sending of PZC-145 general query disabling and SAP RIP updates synchronizing P2C-145 timers P2C-142 SAP Service Advertisement Protocol updates delay between packets P2C-144
delays P2C-141 setting P2C-139
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 204 Index
delay between packets setting P2C-138 show appletalk macip-traffic P2C-55
name-cache command P2C-55 description P2C-4 show appletalk
filters show appletalk nbp command P2C-55
command P2C-55 creating P2C-132 show appletalk neighbors
filters creating P2C-132 show appletalk remap command P2C-55
command P2C-55 filters examples 118 show appletalk route
general query show appletalk socket command P2C-55
command P2C-55 disabling P2C-145 show appletalk static
general query disabling P2C-145 show appletalk traffic command P2C-55
command P2C-55 queue length setting P2C-143 show appletalk zone
P2C-145 show command P2C-158 responses to GNS requests controlling ip nhrp
static entries configuring P2C-143 show ip nhrp traffic command P2C-158
table static entries P2C-143 show ipx accounting command P2C-158
update timers P2C-144 show ipx cache command P2C-155
updates show ipx eigrp interfaces command P2C-156
Enhanced IGRP P2C-92 show ipx eigrp neighbors command P2C-156
command P2C-156 linking to RIP P2C-1 45 show ipx eigrp topology
setting P2C-1 43 show ipx interface command P2C-1 55
SAP Service Advertisement Protocol Service show ipx nlsp database command P2C-1 51 Advertisement Protocol show ipx nlsp neighbors command P2C-151
filters example 118 show ipx nlsp spf-log command P2C-157 secondary networks IPX show ipx route command PZC-155 P2C-156
See IPX secondary networks show ipx servers command P2C-1 55 seed router AppleTalk P2C-14 show ipx traffic command P2C-155 P2C-156
Shiva FastPath router K-Star P2C-11 show smrp forward command P2C-55 show appletalk access-lists command P2C-55 show smrp globals command P2C-56
show appletalk adjacent-routes command P2C-55 show smrp group command P2C-56
show appletalk arp command P2C-55 show smrp mcache command P2C-56 show command P2C-55 appletalk aurp events show smrp neighbor command P2C-56
show appletalk aurp topology command P2C-55 show smrp port command P2C-56
show appletalk cache command P2C55 show smrp route command P2C-56
show appletalk domain command P2C-55 show smrp traffic command P2C-56
show appletalk eigrp interfaces command P2C-55 show sse summary command P2C-155
show appletalk eigrp neighbors command P2C-55 SLIP Serial Line Internet Protocol
show appletalk eigrp topology command P2C-55 drivers IPTalk P2C-33
show appletalk globals command P2C-55 SMDS Switched Multimegabit Data Service
show appletalk interface command P2C-55 fast switching IPX P2C-121
show appletalk macip-clients command P2C-55 smrp mroute-cache protocol appletalk command P2C-38
show appletalk macip-servers command P2C-55
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 205 Index
SMRP Simple Muhicast Routing Protocol topology table
fast switching cache table P2C-56 AppleTalk Enhanced IGRP P2C-55
traffic table P2C-56 IPX Enhanced IGRP P2C-1 56
SNMP Simple Network Management Protocol transition mode
AppleTalk configuring P2C-27 AppleTalk PZC-1
snmp-server community command P2C-27 example P2C-65
spf-interval command P2C-101 tunnel destination command P2C-29 P2C-30
horizon split tunnel mode command P2C-29 P2C-30 P2C-36
Enhanced IGRP P2C-48 AppleTalk tunnel source command P2C-28 P2C-29 P2C-30 P2C-36
IPX Enhanced IGRP P2C-91 tunneling
spoofing AURP P2C-29
IPX P2C-122 Cayman P2C-30
SPX keepalive packets over DDR P2C-122 GRE P2C30
SPX keepalive packets spoofing P2C-122 type 20 packets P2C-136 P2C-131
SSP Silicon Switch Processor
statistics summary P2C-155
standard access lists
Seeaccess lists IPX UDP port numbers IPTalk P2C-36
static routes user EXEC mode summary of xxii
AppleTalk P2C-53 P2C-55
IPX P2C-140 P2C-141
subinterfaces
defined P2C-85 VLANs
IPX P2C-97 AppleTalk support P2C-3 configuration example 160 IPX support P2C-5
shutting down example 160
NLSP P2C-97
configuration example 160
shutting down example 160 watchdog packets P2C-122
Tab key command completion xxii XNS Xerox Network Systems test appletalk command P2C-56 IDP P2C4 tick count IPX P2C-141 routing metrics P2C-4 time range command P2C-130 timers
IPX Enhanced IGRP adjusting P2C-90
TokenTalk P2C-2
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 206 Index
ZIP Zone Information Protocol
definition P2C-3
query interval P2C-43
reply filters P2C-25 zones
See AppleTalk zones
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 207 Index
Cisco lOS AppleTalk and Novell IPX Configuration Guide P2C 208 Corporate Headquarters European Headquarters Americas Headquarters Asia Pacific Headquarters Cisco Systems Inc Cisco Systems Europe Cisco Inc Systems Cisco Systems Australia Pry Ltd 170 West Tasman Drive 11 Rue Camille Desmoulins 170 West Tasman Drive Level 80 Pacific Highway San CA Jose 95134-1706 92782 Issy-les-Moulineaux San Jose CA 95134-1706 P.O Box 469 USA Cedex USA North Sydney www.cisco.com France www.cisco.com NSW 2060 Australia Tel 408 526-4000 www-europecisco.com Tel 408 526-7660 www.cisco.com 800 553-NETS Tel 33 5804 6000 6387 Fax 408 527-0883 Tel 61 8448 7100 Fax 408 526-4100 Fax 33 5804 6100 Fax 61 9957 4350
Cisco Systems has more than 200 offices in the countries and following regions Addresses phone numbers and fax numbers are listed on the Cisco Web site at www.cisco.com/go/offjces
Argentina Australia Austria Brazil Canada Chile China PRC Belgium Colombia Costa Rica Croatia Czech Republic Denmark Dubai UAE Finland France Greece SAP India Indonesia Germany Hong Kong Hungary Ireland Israel Italy Japan Korea Luxembourg Malaysia Mexico The Netherlands New Zealand Peru Poland Norway Philippines Portugal Puerto Rico Romania Russia Saudi Arabia Scotland Singapore Slovakia Slovenia South Africa Spain Sweden Switzerland Taiwan Thailand Turkey Ukraine United Kingdom United States Venezuela Vietnam Zimbabwe
Printed in the USA on 10% recycled paper containing postconsumer waste
Pm Nb 56-2343-09 78-11734-01