Network Protocols Configuration Guide, Part 2 Cisco

NETWORK PROTOCOLS CONFIGURATION GUIDE PART

Cisco lOS Release 113

APPLETALK NOVELL IPX

Documentation also available on CD-ROM and the World Wide Web Network Protocols Configuration Guide Part

Cisco lOS Release 11.3

AppleTalk Novell IPX

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 DOCNPCG2-1 1.3

Text Part Number 78-4737-01 THE SPECIFICATIONS AND 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 SOFTWARE LICENSE AND 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 LICENSE OR LIMITED WARRANTY CONTACT YOUR CISCO REPRESENTATIVE FOR COPY

Class devices This has been tested and found to with the limits for Class The following information is for FCC compliance of equipment comply when the to 15 of the FCC rules These limits are designed to provide reasonable protection against harmful interference digital device pursuant part

This and can radiate and if not installed and used equipment is operated in commercial environment equipment generates uses radio-frequency energy

radio communications of this in residential area is in accordance with the instruction manual may cause harmful interference to Operation equipment

to correct the interference at their own likely to cause harmful interference in which case users will be required expense

The described in this manual and radiate The following information is for FCC compliance of Class devices equipment generates may radio-frequency

it interference with radio and television This energy If it is not installed in accordance with Ciscos installation instructions may cause reception equipment device in accordance with the in 15 of the FCC rules These has been tested and found to comply with the limits for Class digital specifications part

inteiference in residential installation there is no that specifications are designed to provide reasonable protection against such However guarantee

interference will in installation not occur particular

determine whether is interference it off If the interference it was probably caused by the Cisco equipment You can your equipment causing by turning stops

devices If the interference to radio or television to correct the interference by using one or more of or one of its peripheral equipment causes reception try

the following measures

Turn the television or radio antenna until the interference stops

Move the equipment to one side or the other of the television or radio

Move the equipment farther away from the television or radio

certain the and the television or radio Plug the equipment into an outlet that is on different circuit from the television or radio That is make equipment

are on circuits controlled by different circuit breakers or fuses

authorized Cisco Inc could void the FCC and authority to operate the product Modifications to this product not by Systems approval negate your

included with and will be to the software license The following third-party software may be your product subject agreement

based in on HP under license from the Hewlett-Packard HP OpenView is CiscoWorks software and documentation are part OpenView Company

is of the of California Berkeley as part of The Cisco implementation of TCP header compression an adaptation program developed by University UCB

software for any purpose

written promote products derived from this software without specific prior persnissiois

and the of California Berkeley The Cisco implementation of TN3270 is an adaptation of the TN3270 curses tenncap programs developed by University

All reserved 1981-1988 of the University of UCB as part of UCBs public domain version of the UNIX operating system rights Copyright Regents

California

Cisco in Token Fastmar software is licensed to by Madge Cisco incorporates Fastmac and TmeView software and the RingRunner chip some Ring products

and TrueView are trademarks and in some Networks Limited and the RingRunner chip is licensed to Cisco by Madge NV Fastmac RingRunner

makes no representations about the suitability of this software for any purpose

Massachusetts All reserved The Window System is trademark of the Consortium Cambridge rights

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

INABILITY TO USE THIS MANUAL EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES

AccessPath AtnsDirector Cache Director System the CCIE logo CD-PAC Centri Centri Bronze Centri Gold Centri Security Manager Centri Silver the Cisco Capital logo Ciaco lOS the Cisco lOS logo CiscoLink the Cisco Powered Network logo the Cisco Press logo CllckStart ControlStream Fast LAN2LAN LAN2LAN Step FragmentFree lOX JumpStart Kernel Proxy Enterprise Remote Office MICA Natural Network Viewer NetBeyond

Netsys Technologies Packet PIX Point and Click Internetworking Policy Builder RouteStream Secure Script SMARTneI StrataSphere StrataSphere

BILLder StrataSphere Connection Manager StrataSphere Modeler StrataSphere Optimizer Stratm Streamyiew SwitchProbe The Cell TokenSwitch

TrafficDirector VirtualStream VlanDirector Workgroup Director Workgroup Stack and XCI are trademarks The Network Works No Excuses is service mark and BPX Catalyst Cisco Cisco Systems the Cisco Systems logo EtherChannel FastHub FsstPacket ForeSight IPX LightStream

OptiClass Phase/IP StrataCom and SlrataView Plus are registered trademarks of Cisco Systems Inc in the U.S and certain other countries All other trademarks mentioned in this document are the property of their respective owners

Network Protocols Configuration Guide Part

9711R TABLE OF CONTENTS

About the Cisco lOS Software Documentation xvii

Documentation Objectives xvii

Audience xvii

Documentation Organization xvii

Documentation Modules xvii

Master Indexes xvii

Documentation Set xvii

Document Conventions xix

Cisco Connection Online xx

Documentation CD-ROM xxi

AppleTalk and Novell IPX Overview P2C1

AppleTalk P2C-1 Background on AppleTalk P2C-

Cisco Implementation of AppleTalk P2C-2

Supported Media P2C-2

Standard AppleTalk Services P2C-2

Enhancements to Standard AppleTalk Services P2C-3

Security P2C-4

Novell IPX P2C-4

Background on Novell IPX P2C-4

Cisco Implementation of Novells IPX P2C-4

IPX Support P2C-4

IPX Enhanced IGRP Support P2C-5

LANE Support P2C-5

VLAN Support P2C-5

Configuring AppleTalk P2C7

AppleTalk Phases P2C-7 AppleTalk Phase P2C-7 AppleTalk Phase P2C-7 Types of AppleTalk Networks P2C-7 Comparison of Nonextended and Extended Networks P2C-8

Relationship between AppleTalk Phases and Network Types P2C-8 Comparison of AppleTalk Phases P2C-8

Cisco-Supported AppleTalk Phases P2C-9

AppleTalk Addresses P2C-9 Network Numbers P2C-9

AppleTalk Phase Network Numbers P2C-9 AppleTalk Phase Network Numbers P2C-9

Node Numbers P2C- 10

AppleTalk Phase Node Numbers P2C-10 AppleTalk Phase Node Numbers P2C-10

AppleTalk Address Example P2C- 10

AppleTalk Zones P2C-10

Table of Contents AppleTalk Phase Zones P2C-10 AppleTalk Phase Zones P2C- 10

Configuration Guidelines and Compatibility Rules P2C- 11

Combining AppleTalk Phase and Phase Routers P2C- 11 Combining Cisco Routers with Other Vendors P2C- 11

AppleTalk Configuration Task List P2C- 11

Enable AppleTalk Routing P2C-12

Enable AppleTalk Routing Task List P2C-12

Enable AppleTalk Routing P2C-12

Configure an Interface for AppleTalk P2C-12

Manually Configure an Interface P2C-13

Dynamically Configure an Interface P2C- 13

Select an AppleTalk Routing Protocol P2C-15

Configure Transition Mode P2C-16

Enable Concurrent Routing and Bridging P2C-16

Configure Integrated Routing and Bridging P2C-17

Control Access to AppleTalk Networks P2C-17

Types of Access Lists P2C-17

AppleTalk-Style Access Lists P2C- 17

IP-Style Access Lists P2C-18 P2C-18 Combining AppleTalk-Style and IP-Style Entries

Types of Filters P2C- 18

Implementation Considerations P2C- 19

Control Access to AppleTalk Networks Task List P2C-20

Create Access Lists P2C-20

Set Priority Queuing P2C-20

Automatic Fast Switching P2C-20

Create AppleTalk-Style Access Lists P2C-21

Create IP-Style Access Lists P2C-22

Create Filters P2C-22

Create NBP Packet Filters P2C-22

Create Data Packet Filters P2C-23

Create Routing Table Update Filters P2C-23 Create GetZoneList GZL Filters P2C-25 Enable ZIP Reply Filters P2C-26

Enable Partial Zone Filters P2C-26

Configure the Name Display Facility P2C-27

Set Up Special Configurations P2C-27

Configure AURP P2C-27

Configure Free-Trade Zones P2C-29

Configure SNMP over DDP in AppleTalk Networks P2C-29

Configure AppleTalk Tunneling P2C-30

Configure AppleTalk MacIP P2C-3

Cisco Implementation of AppleTalk MacIP P2C-3

When to Use AppleTalk MacIP P2C-3 Advantages of Using MacIP P2C-3

vi Network Protocols Configuration Guide Part Implementation Considerations P2C-32

Configure AppleTalk MacIP Task List P2C-32

Establish MacIP Server for Zone P2C-33

Allocate IP Addresses for Macintosh Users P2C-33

Configure IPTalk P2C-34

Configure IP Encapsulation of AppleTalk Packets P2C-35

Specify the UDP Port Ranges P2C-36

Configure SMRP over AppleTalk P2C-37

Configure AppleTalk Control Protocol for Point-to-Point Protocol P2C-38

Tune AppleTalk Network Performance P2C-39 Control Routing Updates P2C-39

Disable the Processing of Routed RTMP Packets P2C-39

Enable RTMP Stub Mode P2C-40

Disable the Transmission of Routing Updates P2C-40

Prevent the Advertisement of Routes to Networks with No Associated Zones P2C-40

Set Routing Table Update Timers P2C-41

Assign Proxy Network Numbers P2C-41

Enable Round-Robin Load Sharing P2C-42 Disable Checksum Generation and Verification P2C-42

Control the AppleTalk ARP Table P2C-42

Control the Delay between ZIP Queries P2C-43

Log Significant Network Events P2C-43

Disable Fast Switching P2C-43

Configure AppleTalk Enhanced IGRP P2C-44 Benefits of Using AppleTalk Enhanced IGRP P2C-44 Convergence Technology P2C-44

Enhanced IGRP Features P2C-44

Enhanced IGRP Components P2C-45

Neighbor Discoveiy/Recovery P2C-45

Reliable Transport Protocol P2C-45

DUAL Finite-State Machine P2C-45

Protocol-Dependent Modules P2C-45

Ciscos Enhanced IGRP Implementation P2C-46

Enhanced IGRP Configuration Task List P2C-46

Enable AppleTalk Enhanced IGRP P2C-46

Configure Miscellaneous Parameters P2C-47

Disable Redistribution of Routing Information P2C-47

Adjust the Interval between Hello Packets and the Hold Time P2C-47

Disable Split Horizon P2C-48

Adjust the Active State Time for Enhanced IGRP Routes P2C-48

Log Enhanced IGRP Neighbor Adjacency Changes P2C-48

Configure the Percentage of Link Bandwidth Used by Enhanced IGRP P2C-49

Configure AppleTalk Interenterprise Routing P2C-49

Understand AppleTalk Domains P2C-49 Understand Domain Routers P2C-49

AppleTalk Interenterprise Routing Features P2C-49 Redundant Paths between Domains P2C-50

Table of Contents vii AppleTalk Interenterprise Routing Task List P2C-5

Enable AppleTalk Interenterprise Routing P2C-5 Remap Network Numbers P2C-5 Control Hop Count P2C-52

Configure AppleTalk over WANs P2C-52

AppleTalk over DDR P2C-52

Configure Static Routes P2C-53

Configure Floating Static Routes P2C-53

AppleTalk over X.25 P2C-53

Monitor and Maintain the AppleTalk Network P2C-53

Monitor and Maintain the AppleTalk Network Using Cisco lOS Software Commands P2C-54

Monitor the AppleTalk Network Using Network Monitoring Packages P2C-55

AppleTalk Configuration Examples P2C-56

Extended AppleTalk Network Example P2C-57 Nonextended AppleTalk Network Example P2C-57

Nonextended Network in Discovery Mode Example P2C-57 AppleTalk Enhanced IGRP Example P2C-58 Transition Mode Example P2C-58

AppleTalk Access List Examples P2C-59

Defining an Access List to Filter Data Packets Example P2C-59

Defining an Access List to Filter Incoming Routing Table Updates Example P2C-60

Comparison of Alternative Segmentation Solutions P2C-61

Defining an Access List to Filter NBP Packets Example P2C-62

Configuring Partial Zone Advertisement Example P2C-63

Hiding and Sharing Resources with Access List Examples P2C-65

Establishing Free-Trade Zone Example P2C-65

Restricting Resource Availability Example P2C-66

GZL and ZIP Reply Filter Examples P2C-68

AppleTalk Interenterprise Routing over AURP Example P2C-69 SNMP Example P2C-70 MacIP Examples P2C-70 IPTalk Example P2C-7 AppleTalk Control Protocol Example P2C-74 Proxy Network Number Example P2C-74

AppleTalk Enhanced IGRP Bandwidth Configuration Example P2C-75

AppleTalk Interenterprise Routing Example P2C-75 AppleTalk over DDR Example P2C-75 AppleTalk Control Protocol for PPP Example P2C-76

Configuring Novell IPX P2C-79

IPX Addresses P2C-79 Network Numbers P2C-79 Node Numbers P2C-79

IPX Address Example P2C-79

IPX Configuration Task List P2C-80

Enable IPX Routing P2C-80

viii Network Protocols Configuration Guide Part IPX Default Routes P2C-80

Enable IPX Routing Task List P2C-81

Enable IPX Routing P2C-81

Assign Network Numbers to Individual Interfaces P2C-8

Assign Network Numbers to Individual Interfaces Task List P2C-82

Assign Network Numbers to Interfaces That Support Single Network P2C-82

Assign Network Numbers to Interfaces That Support Multiple Networks P2C-82

Enable Concurrent Routing and Bridging P2C-84

Configure Integrated Routing and Bridging P2C-84

Configure IPX Enhanced IGRP P2C-84 Enhanced IGRP Features P2C-85

Enhanced IGRP Components P2C-85

Neighbor Discovery/Recovery P2C-85

Reliable Transport Protocol P2C-85 DUAL Finite-State Machine P2C-86

Protocol-Dependent Modules P2C-86

Configure IPX Enhanced IGRP Task List P2C-86 Enable IPX Enhanced IGRP P2C-86

Customize Link Characteristics P2C-87

Configure the Percentage of Link Bandwidth Used by Enhanced IGRP P2C-87

Configure Maximum Hop Count P2C-87

Adjust the Interval between Hello Packets and the Hold Time P2C-87

Customize the Exchange of Routing and Service Information P2C-88 Redistribute Routing Information P2C-89

Disable Split Horizon P2C-89

Control the Advertising of Routes in Routing Updates P2C-90

Control the Processing of Routing Updates P2C-90 Control SAP Updates P2C-90

Control the Advertising of Services in SAP Updates P2C-91

Control the Processing of SAP Updates P2C-91 Query the Backup Server P2C-91

Configure NLSP P2C-9 Understand Level and Routers P2C-92

Understand NLSP Databases P2C-92

Cisco Support of NLSP P2C-92

Configure NLSP Task List P2C-92

Define an Internal Network P2C-93

Enable NLSP Routing P2C-93

Configure NLSP on an Interface P2C-93

Configure NLSP on LAN Interface P2C-93

Configure NLSP on WAN Interface P2C-94

Customize Link Characteristics P2C-94

Enable NLSP Multicast Addressing P2C-94

Configure the Metric Value P2C-96

Configure the Link Delay and Throughput P2C-96

Configure the Maximum Hop Count P2C-97

Specify Designated Router P2C-97

Table of Contents ix Configure Transmission and Retransmission Intervals P2C-97

Modify Link-State Packet Parameters P2C-98

Limit Partial Route Calculations P2C-98 P2C-99 Configure Route Aggregation Benefits of Route Summarization P2C-99

Understand Area Addresses Route Summaries and Aggregated Routes P2C-99

Understand NLSP Areas P2C-100

Understand Route Redistribution P2C-l01 Understand Route Summarization P2C-102

Understand Service and Path Selection P2C-103 P2C-103 Configure Route Aggregation Task List

Version 1.1 Areas P2C- 104 Configure Route Aggregation for Multiple NLSP

1.1 and Version 1.0 Configure Route Aggregation for NLSP Version NLSP Areas P2C-106

and Version 1.1 Configure Route Aggregation for Enhanced IGRP NLSP Environments P2C- 109

1.1 Environments P2C- 111 Configure Route Aggregation for RIP and NLSP Version

Customize the Exchange of Routing Information P2C- 112

Configure RIP and SAP Compatibility P2C-1 12

Redistribute Routing Information P2C- 113

Configure Next Hop Resolution Protocol P2C- 114

NHRP Configuration Task List P2C-1 14

Enable NHRP on an Interface P2C-1 14

Configure Stations Static IPX-to-NBMA Address Mapping P2C- 114 15 Statically Configure Next Hop Server P2C-1 P2C- 115 Configure NHRP Authentication

Control NHRP Initiation P2C-l 15

Trigger NHRP by IPX Packet P2C- 115 Basis P2C- 116 Trigger NHRP on Per-Destination Control NHRP Packet Rate P2C-116

P2C-l 16 Suppress Forward and Reverse Record Options

Specify the NHRP Responder Address P2C-l 17 Change the Time Period NBMA Addresses Are Advertised as Valid P2C-l 17

Configure IPX and SPX over WANs P2C-l 17

Configure IPX over DDR P2C- 118

Configure SPX Spoofing over DDR P2C- 118

Configure IPX Header Compression P2C- 118

Configure the IPXWAN Protocol P2C- 119

Control Access to IPX Networks P2C- 119

Types of Access Lists P2C-119 Types of Filters P2C-120

Implementation Considerations P2C- 121

Control Access to IPX Networks Task List P2C-122

Create Access Lists P2C-122

Create Access Lists Using Numbers P2C-122 Create Access Lists Using Names P2C-123

Create Filters P2C-126

Create Generic Filters P2C-127

Network Protocols Configuration Guide Part Create Filters for Updating the Routing Table P2C-127

Create SAP Filters P2C-128

Create GNS Response Filters P2C-128

Create IPX NetBIOS Filters P2C-128

Create Broadcast Message Filters P2C-129

Tune IPX Network Performance P2C-130

Control Novell IPX Compliance P2C-130 Control the Forwarding of Type 20 Packets P2C- 131

Control Interpacket Delay P2C- 134

Shut Down an IPX Network P2C-134

Achieve Full Novell Compliance P2C-135

Adjust RIP and SAP Information P2C-135

Configure Static Routes P2C-136

Adjust the RIP Delay Field P2C-136

Adjust RIP Update Timers P2C-136

Configure RIP Update Packet Size P2C-138

Configure Static SAP Table Entries P2C-138

Configure the Queue Length for SAP Requests P2C-138

Adjust SAP Update Timers P2C-138

Configure SAP Update Packet Size P2C-139 Enable SAP-after-RIP P2C-140

Disable Sending of General RIP or SAP Queries P2C-140

Control Responses to GNS Requests P2C-141

Configure Load Sharing P2C-141

Enable Round-Robin Load Sharing P2C-141

Enable Per-Host Load Sharing P2C-142

Specify the Use of Broadcast Messages P2C-142

Use Helper Addresses to Forward Broadcast Packets P2C-142

Enable Fast Switching of IPX Directed Broadcast Packets P2C-144

Disable IPX Fast Switching P2C-144

Adjust the Route Cache P2C- 144

Control Route Cache Size P2C-144

Control Route Cache Invalidation P2C-145

Adjust Default Routes P2C-145

Disable Network Number -2 as the Default Route P2C-145

Advertise Only Default RIP Routes P2C-146 Pad Odd-Length Packets P2C-146

Shut Down an IPX Network P2C-146

Configure IPX Accounting P2C-147

Switching Support P2C-147

Access List Support P2C-147

IPX Accounting Task List P2C-l48 Enable IPX Accounting P2C-148 Customize IPX Accounting P2C-148

Monitor and Maintain the IPX Network P2C-148

Perform General Monitoring and Maintaining Tasks P2C-149

Monitor and Maintain Caches Tables Interfaces and Statistics P2C-149

Table of Contents xi Packets P2C- 149 Specify the Type and Use of Ping P2C-150 Repair Corrupted Network Numbers Monitor and Maintain IPX Enhanced IGRP P2C 150 Log Enhanced IGRP Neighbor Adjacency Changes P2C-150 Monitor and Maintain NLSP P2C 151

Log Adjacency State Changes P2C- 151 Monitor and Maintain NIRP P2C- 151

Monitor and Maintain IPX Accounting P2C- 152

Novell IPX Configuration Examples P2C152

IPX Routing Examples P2C- 152 P2C- 152 IPX Routing on Single Network Example P2C-153 IPX Routing on Multiple Networks Examples

IPX Routing Protocols Examples P2C-155 Enhanced IGRP Examples P2C-156 IPX Enhanced IGRP Example P2C-156 Enhanced IGRP SAP Update Examples P2C-156 P2C- 157 Advertisement and Processing of SAP Update Examples

IPX Enhanced IGRP Bandwidth Configuration Example P2C-157

NLSP Examples P2C-157

NLSP Multicast Addressing Examples P2C158 Enhanced IGRP and NLSP Route Redistribution Example P2C-158 Areas P2C-158 NLSP Route Aggregation for Multiple NLSP Version Example

1.0 Areas P2C- 159 NLSP Route Aggregation for NLSP Version 1.1 and Version Example and RIP NLSP Route Aggregation for NLSP Version 1.1 Enhanced IGRP

Example P2C- 159 NHRP Examples P2C-160 NHRP Example P2C-161 NHRP over ATM Example P2C-162

IPX over WAN Examples P2C-164

IPX over WAN Interface Example P2C- 164

IPX over DDR Example P2C- 166

IPX Network Access Examples P2C-168 IPX Network Access Example P2C- 168 Standard Named Access List Example P2C-169 P2C- 169 SAP Input Filter Example

SAP Output Filter Example P2C-l70

IPX NetBIOS Filter Examples P2C- 171 Broadcast P2C- 173 Helper Facilities to Control Examples

Forwarding to an Address Example P2C- 173

Forwarding to All Networks Example P2C-175 All-Nets Flooded Broadcast Example P2C-176 IPX Accounting Example P2C- 176

Index

xii Network Protocols Configuration Guide Part LIST OF FIGURES

Figure Cisco lOS Software Documentation Modules xviii

Figure IPTalk Configuration Example P2C35

P2C-37 Figure SMRP Packet Transmission over AppleTalk

Domain Domains P2C-50 Figure Allowed Configuration of Router Connecting Two

P2C-50 Figure Improper Configuration of Domain Routers Connecting Two Domains

Figure InterPoll Output P2C-56

Figure Nonextended AppleTalk Routing between Two Ethernet Networks P2C-57

Figure Routing in Discovery Mode P2C-58

Figure Transition Mode Topology and Configuration P2C-59

Figure 10 Example Topology of Partially Obscured Zone P2C-64

Figure 11 Controlling Access to Common AppleTalk Network P2C-65

Figure 12 Controlling Resource Access among Multiple AppleTalk Zones P2C-66

Figure 13 GZL and ZIP Reply Filters Sample Topology P2C-69

Figure 14 Example Network Topology P2C.-74

Figure 15 AppleTalk over DDR Configuration P2C-76

Figure 16 Two Logical NBMA Networks over One Physical NBMA Network P2C-161

Figure 17 Physical Configuration of Sample NBMA Network P2C-162

Figure 18 IPX over WAN Interface P2C- 164

Figure 19 IPX over DDR Configuration P2C- 166

Figure 20 Novell IPX Servers Requiring Access Control P2C- 168

Figure 21 SAP Input Filter P2C-170

Figure 22 SAP Output Filter P2C-171

Figure 23 IPX Clients Requiring Server Access through Router P2C-174

Figure 24 Type Broadcast Flooding P2C-175

Figure 25 IPX Accounting Example P2C-176

List of Figures xiii xiv Network Protocols Configuration Guide Part LIST OF TABLES

Table Comparison of Nonextended and Extended Networks P2C-8

Table AppleTalk Phase and Phase P2C-8

Table Packet Type to Filter Mapping P2C-19

Table Zone and Interface Associations for Partial Zone Advertisement Example P2C-64

Table Partial Zone Advertisement Control on Network 30 P2C-64

Table Cisco and Novell IPX Encapsulation Names on IEEE Interfaces P2C-82

Table IPX Filters P2C-121

List of Tables xv xvi Network Protocols Configuration Guide Part About the Cisco OS Software Documentation

This section discusses the objectives audience organization and conventions of the Cisco lOS

software documentation It also discusses how to obtain documentation on Cisco Connection Online

and the Documentation CD-ROM

Documentation Objectives

This Cisco lOS software documentation describes the tasks and commands necessaiy to configure

and maintain your access server or router

Audience

The Cisco lOS software documentation is intended primarily for users who configure and maintain

access servers and routers but are not necessarily familiar with tasks the relationship between tasks

or the commands necessary to perform particular tasks

Documentation Organization

The Cisco lOS software documentation is divided into nine modules and two master indexes

Documentation Modules

Each module consists of two books configuration guide and corresponding command reference

Chapters in configuration guide describe protocols configuration tasks and Cisco lOS software

functionality and contain comprehensive configuration examples Chapters in command reference

provide complete command syntax information Each configuration guide can be used in

conjunction with its corresponding command reference

Master Indexes

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 In addition individual

books contain book-specific index

Documentation Set

The Cisco lOS software documentation set is shown in Figure

About the Cisco lOS Software Documentation xvii Documentation Organization

Figure Cisco lOS Software Documentation Modules

Module PlC

Configuration Guide

Module P1R Command

Reference

Module FC/FR Module P1C/P1R Module P2C/P2R Module P3C/P3R Module WC/WR

Configuration Network Protocols Network Protocols Network Protocols Wide-Area Fundamentals Part Part Part Networking

Access Server and Addressing AppleTalk Apollo Domain ATM

Router Product lP Services Novell IPX Banyan VINES Frame Relay Overview IP Routing Protocols DECnet SMDS Cisco lOS Software alSO CLNS X.25 and LAPB

Configuration Basics XNS

Images and

Configuration Files

Interface Configuration

System Management

Module XC

Configuration Guide

Module XR Command

Reference

Module SC/SR Module DC/DR Module XC/XR Module BC/BR Configuration

Security Dial Solutions Cisco lOS Switching Bridging and IBM Guide Master

Terminal Access Security Dial Business Services Networking Index

Network Access Security Solutions and Switching Paths for lP Transparent Bridging Networks Source-Route Accounting and Billing Examples Bridging Command

Filtering Traffic Dial-In Port Setup Fast Switching Remote Source-Route Reference

Preventing Fraudulent DDR and Dial Backup Autonomous Switching Bridging Master Index

Route Updates Remote Node and NetFlow Switching DLSw

Network Data Encryption Terminal Service Optimum Switching STUN and BSTUN Cost-Control and Virtual LAN VLAN LLC2 and SDLC

Large-Scale Dial Switching and Routing IBM Network Media Translation

Solutions Inter-Switch Link Protocol DSPU and SNA Service Point

VPDN Encapsulation SNA Frame Relay Access Support IEEE 802.10 APPN

Encapsulation NCIA Client/Server Topologies

LAN Emulation IBM Channel Attach

xviii Network Protocols Configuration Guide Part Document Conventions

Document Convenflons

The Cisco lOS documentation set uses the following conventions

The caret character represents the Control key

For example the key combinations AD and Ctrl-D are equivalent Both mean hold down the the Control key while you press key Keys are indicated in capital letters but are not case sensitive

string is defined as nonquoted set of characters

For example when setting an SNMP community string to public do not use quotation marks

around the string otherwise the string will include the quotation marks

Command descriptions use these conventions

Boldface indicates commands and keywords that are entered literally as shown

Italics indicate arguments for which you supply values in contexts that do not allow italics

arguments are enclosed in angle brackets

Square brackets indicate optional elements

Braces and group required choices vertical bars separate alternative elements

Braces and vertical bars within square brackets indicate required choice within an

optional element

Examples use these conventions

Examples that contain system prompts denote interactive sessions indicating that the user enters The commands at the prompt systemprompt indicates the current command mode For example

the prompt Router config indicates global configuration mode

Terminal sessions and information the system displays are in screen font

Information you enter is in boldface screen font

Nonprinting characters such as passwords are in angle brackets

Default responses to system prompts are in square brackets

Exclamation points at the beginning of line indicate comment line They are also displayed

by the Cisco lOS software for certain processes

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

Within the Cisco lOS software documentation the term router is used to refer to both access servers

and routers When feature is supported on the access server only the term access server is used

When feature is supported on one or more specific router platforms such as the Cisco 4500 but

not on other platforms such as the Cisco 2500 the text specifies the supported platforms

About the Cisco lOS Software Documentation xix Cisco Connection Online

Within examples routers and access servers are alternately shown These products are used only for

example purposes that is an example that shows one product does not indicate that the other product

is not supported

Cisco Connection Onfine

channel Maintenance Cisco Connection Online CCO is Cisco Systems primary real-time support information and services customers and partners can self-register on CCO to obtain additional

Available 24 hours day days week CCO provides wealth of standard and value-added

services to Ciscos customers and business partners CCO services include product information

product documentation software updates release notes technical tips the Bug Navigator

configuration notes brochures descriptions of service offerings and download access to public and

authorized files

CCO serves wide variety of users through two interfaces that are updated and enhanced

simultaneously character-based version and multimedia version that resides on the World Wide

Web The character-based CCO and Internet WWW supports Zmodem Kermit Xmodem FTP e-mail and it is excellent for quick access to information over lower bandwidths The WWW version

of CCO provides richly formatted documents with photographs figures graphics and video as well

as hyperlinks to related information

You can access CCO in the following ways

WWW http//www.cisco.com

WWW http//www-europe.cisco.com

WWW http//www-china.cisco.com

Telnet cco.cisco.com

Modem From North America 408 526-8070 from Europe 33 644640 82 Use the

following terminal settings VT100 emulation databits parity none stop bits and

connection rates up to 288 kbps

For copy of CCOs Frequently Asked Questions FAQ contact [email protected] For additional information contact cco-team@ cisco.com

Note If you are network administrator and need personal technical assistance with Cisco

product that is under warranty or covered by maintenance contract contact Ciscos Technical Assistance Center TAC at 800 553-2447 408 526-7209 or [email protected] To obtain general

information about Cisco Systems Cisco products or upgrades contact 800 553-6387

408 526-7208 or [email protected]

xx Network Protocols Configuration Guide Part Documentation CD-ROM

DocumefltataOfl CDROM

documentation and additional literature Cisco are available in CD-ROM package which ships with The Documentation your product CD-ROM member of the Cisco Connection Family is updated monthly Therefore it might be more up to date than printed documentation To order additional copies of the Documentation CD-ROM contact your local sales representative or call customer

service The CD-ROM package is available as single package or as an annual subscription You can

also access Cisco documentation on the World Wide Web at http//www.cisco.com http//www-china.cisco.com or http//www-europe.cisco.com

If you are reading Cisco product documentation on the World Wide Web you can submit comments

electronically Click Feedback in the toolbar select Documentation and click Enter the feedback

form After you complete the form click Submit to send it to Cisco We appreciate your comments

About the Cisco OS Software Documentation xxi Documentation CD-ROM

xxii Network Protocols Configuration Guide Part AppeTaHk and NoveU DPX Overview

The Cisco lOS software supports variety of routing protocols The Network Protocols

Configuration Guide Part discusses the following network protocols

AppleTalk

Novell IPX

The Network Protocols Configuration Guide Part discusses the following network protocols

IP Routing

The Network Protocols Configuration Guide Part 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 refer to the appropriate chapter in this publication

AppIeTak

This section provides background on AppleTalk and briefly describes Ciscos implementation of AppleTalk

Background on AppleTalk

AppleTalk is LAN system designed and developed by Apple Computer Inc It can run over

Ethernet Token Ring and Fiber Distributed Data Interface FDDI networks and over Apples media proprietary twisted-pair access system LocalTalk AppleTalk specifies protocol stack

comprising several protocols that direct the flow of traffic over the network

the Apple Computer uses 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

AppleTalk and Novell IPX Overview P2C-1 AppleTalk

Ciscos Implementation of AppleTalk

and Phase For Phase Cisco lOS software supports AppleTalk Phase AppleTalk AppleTalk networks Cisco devices support both extended and nonextended

with Cisco router or access server may receive equivalent routes advertised by neighboring routers the and another an one router giving an AppleTalk Phase form of route for example 101 giving advertise AppleTalk Phase form of the route for example 101-101 When neighboring routers the Phase form of the equivalent overlapping routes to router the router always uses AppleTalk

route and discards the AppleTalk Phase route

Supported Media Token and FDDI Ciscos implementation of AppleTalk routes packets over Ethernet Ring LANs and Switched and over X.25 High-Level Data Link Control HDLC Frame Relay 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

between internetworked nodes AARP AARP DDP and RTMP provide end-to-end connectivity the data thus it maps AppleTalk node addresses to the addresses of underlying link making possible socket-to-socket of for AppleTalk to run on several data links DDP provides delivery packets

RTMP establishes and maintains routing tables

NBP and ZIP maintain node name and zone information NBP maps network names to AppleTalk

addresses ZIP tracks which networks are in which zones

It that test the reachability of network AEP is an echo or ping-type protocol generates packets nodes

and retransmission for ATP is reliable transport protocol that provides data acknowledgment the Protocol transaction-based applications such as file services provided by AppleTalk Filing the Printer Access Protocol AFP and print services provided by PAP

Information Base variables as Our software provides support for the AppleTalk Management MIB

described in RFC 1243

P2C-2 Network Protocols Configuration Guide Part AppleTalk

Enhancements to Standard AppleTalk Services

The Cisco AppleTalk implementation includes the following enhancements to standard AppleTalk

support

Support for AppleTalk Enhanced Internet Gateway Protocol Enhanced IGRP AppleTalk

Enhanced IGRP provides the following features

Automatic redistribution By default AppleTalk Routing Table Maintenance Protocol

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

for either are configured AppleTalk to use 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 PSDN 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 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 105 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

limits the number No software on of zones or routes However per AppleTalk specification you maximum can only have of 255 zones per segment

MacTCP support via MacIP server

Support of IPTalk which provides Internet Protocol IP encapsulation of AppleTalk IPTaIk and the Columbia AppleTalk Package CAP

Access control for filtering network traffic by network number ZIP filtering by NBP entity

table and GetZoneList names filtering routing updates filtering GZL responses

Integrated node name support to simplify AppleTalk network management

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

SNMP over AppleTalk

Encapsulation tunneling of AppleTalk RTMP packets over an IP backbone

AppleTalk and Novell IPX Overview P2C3 Novell IPX

Support for AppleTalk static routes

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 basis This security feature is similar to those that Cisco provides for other

protocols

Note that Ciscos implementation of AppleTalk does not forward packets with local source and destination network addresses This behavior does not conform with the definition of AppleTalk in

Apple Computers 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 Media Access Control MAC

Novell PX

This section offers background information and briefly describes Ciscos implementation of Novell IPX

Background on Novell IPX

Novell Internet 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 Novells proprietary Service Advertisement 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

Ciscos Implementation of Novells IPX

Ciscos implementation of Novells IPX protocol is certified to provide full IPX routing

functionality

IPX MIB Support

Cisco supports the IPX MIB currently read-only access is supported The IPX Accounting group

This to represents one of the local Cisco-specific IPX variables we support group provides access

the active database that is created and maintained if IPX accounting is enabled on router or access

server

P2C-4 Network Protocols Configuration Guide Part Novell IPX

ipx Enhanced IGRP Support

Cisco lOS software also supports IPX Enhanced IGRP which provides the following features

Automatic redistributionIPX RIP routes are automatically redistributed into Enhanced IGRP

and Enhanced IGRP routes are automatically redistributed into Routing Information Protocol

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

IGRP is When Enhanced 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 Enhanced IGRPs reliable transport

mechanism which means that an Enhanced IGRP peer must be present for incremental SAPs to

be sent If no peer exists on particular interface periodic SAPs will be sent on that interface

until peer is found This functionality is automatic on serial interfaces and can be configured on LAN media

LANE Support

Cisco lOS software also supports routing IPX between Ethernet-emulated LANs and Token

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

Cisco 105 software supports routing IPX between VLANs Users with Novell NetWare

environments can configure any one of the four IPX Ethernet encapsulations to be routed using the

Inter-Switch Link 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 lOS Switching Services Configuration Guide

AppleTalk and Novell IPX Overview P2C-5 Novell IPX

P2C-6 Network Protocols Configuration Guide Part Configuring AppeTalk

This chapter describes how to configure AppleTalk and provides configuration examples For of the complete description AppleTalk commands mentioned in this chapter refer to the AppleTalk

Commands chapter in the Network Pmtocols Command Reference Part To locate of other commands documentation thatappear in this chapter use the command reference master index or search online

AppeTaOk Phases

The AppleTalk network architecture has the following two phases

AppleTalk Phase

AppleTalk Phase is the initial implementation of AppleTalk and is designed for logical

workgroups AppleTalk Phase supports single physical network that can have one network

number in and be one zoneThis network can have up to 254 devices which can consist of 127 end nodes and 127 servers

AppleTalk Phase

Phase is enhancement AppleTalk an to AppleTalk Phase and is designed for larger networks and has improved routing capabilities It supports multiple logical networks on single physical network

and networks in multiple logical given zone This means that one cable segment can have multiple numbers Each network 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

lypes of AppleTalk 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

Configuring AppleTalk P2C-7 AppleTalk Phases

Comparison of Nonextended and Extended Networks

Table compares the attributes of nonextended and extended networks

Table Comparison of Nonextended and Extended Networks

Attribute Nonextended Extended

Media-level encapsulation method Encapsulation of the ISO-type encapsulations

3-byte LocalTalk packet oniy that is no

in an Ethernet 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 netvorknode

unique combination is unique

Cable addressing method single number per number range

cable corresponding to one or

more logical networks

Relationship between AppleTalk Phases and Network Types

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

Comparison of AppleTalk Phases

Table compares the capabilities of AppleTalk Phase and Phase

Table 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

Media-level encapsulation

Nonextended network Does not apply Yes

P2C-8 Network Protocols Configuration Guide Part AppleTalk Addresses

Table AppleTalk Phase and Phase Continued

Capability AppleTalk Phase AppleTalk Phase

Extended network Does not apply Yes

Cable addressing Does not apply uses Single network number network numbers 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

Cisco-Supported AppleTalk Phases

Routers Software Release 8.2 later running or support AppleTalk Phase and Phase

AppleTak Addresses

An address consists AppleTalk of network number and node number expressed in decimal in the format network.node

Network Numbers

The network 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

AppleTalk Phase Network Numbers

In AppleTalk Phase networks are identified by single network number that corresponds to

physical network In AppleTalk Phase the network number is reserved

AppleTalk Phase Network Numbers

In Phase networks AppleTalk are identified by cable range that corresponds to one or more

logical networks In Phase single cable can have multiple network numbers

cable is either range 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 and single network number the cable range 1012 identifies logical network that spans three network numbers

In AppleTalk Phase the network number is reserved

Configuring AppleTalk P2C-9 AppleTalk Zones

Node Numbers

connected the network The The node number identifies the node which is any device to AppleTalk

node number is an 8-bit decimal number that must be unique on that network

AppleTalk Phase Node Numbers

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

AppleTalk Phase Node Numbers

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

.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

AppeTak Zones

of networks The networks in be zone is logical group zone can contiguous or noncontiguous

identified which be 32 characters The zone is by zone name can up to long 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

AppleTalk Phase Zones

An AppleTalk Phase network can have only one zone

AppleTalk Phase Zones

In AppleTalk Phase an extended network can have up to 255 zones nonextended network can

have only zone

P2C-1O Network Protocols Configuration Guide Part Configuration Guidelines and Compatibility Rules

Configuration Guidefines and Compatibifity 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

Combining AppleTalk Phasel and Phase Routers

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

Combining Cisco Routers with Other Vendors

When using Cisco routers with implementations of AppleTalk by other vendors follow these

guidelines

Macintosh with Ethernet card For an to support extended AppleTalk the Macintosh must be EtherTalk Version running 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

Apples 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

AppleTalk Configuration Task List

To configure AppleTalk routing complete the tasks in the following sections At minimum you

must enable AppleTalk routing The remaining tasks are optional

Enable AppleTalk Routing

Control Access to AppleTalk Networks

Configure the Name Display Facility

Set Up Special Configurations

Configure AppleTalk Control Protocol for Point-to-Point Protocol

Tune AppleTalk Network Performance

Configure AppleTalk Enhanced IGRP

Configure AppleTalk Interenterprise Routing

Configure AppleTalk over WANs

Monitor and Maintain the AppleTalk Network

See the AppleTalk Configuration Examples section at the end of this chapter for configuration examples

Configuring AppleTalk P2C-1 Enable AppleTalk Routing

Enabe AppHeTak Roufing

You enable AppleTalk routing by first enabling it on the router and then configuring it on each

interface

You can also enable the Cisco lOS software to perform transition mode routing from nonextended

AppleTalk to extended AppleTalk

You can route AppleTalk on some interfaces and transparently bridge it on other interfaces and simultaneously To do this you must enable concurrent routing bridging

You can also route AppleTalk traffic between routed interfaces and bridge groups or route AppleTalk traffic between bridge groups To do this you must enable integrated routing and

bridging

Enable AppleTalk Routing Task List

Complete the tasks in the following sections to enable AppleTalk routing The first two tasks are the required rest are optional

Enable AppleTalk Routing

Configure an Interface for AppleTalk

Select an AppleTalk Routing Protocol

Configure Transition Mode

Enable Concurrent Routing and Bridging

Configure Integrated Routing and Bridging

Enable AppleTalk Routing

To enable AppleTalk routing perform the following task in global configuration mode

Task Command

Enable AppleTalk routing 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

refer to the Enable AppleTalk Enhanced IGRP section 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

Configure 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

P2C-12 Network Protocols Configuration Guide Part Enable AppleTalk Routing

an Interface ManUaHY Configure

interface for nonextended You can manually configure an AppleTalk or extended AppleTalk routing

Configure for Nonextended AppleTalk Routing

interface for To manually configure an nonextended AppleTalk routing perform the following tasks

in interface configuration mode

Task Command

Step Assign an AppleTalk address to the appletalk address network.node

interface

Step Assign zone name to the interface appletalk zone zone-name

the address After you assign and zone names the interface will attempt to verify them with another the operational router on connected network If there are any discrepancies the interface will not there become operational If are no neighboring operational routers the device will assume the

interfaces configuration 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 in this chapter

Configure for Extended AppleTalk Routing

To manually configure an interface for extended AppleTalk routing perform the following tasks in

interface configuration mode

Task Command

cable Step Assign range to an interface appletalk cable-range cable-range

Step Assign zone name to the interface appletalk zone zone-name

You than can assign more 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 of how to an example configure an interface for extended AppleTalk routing see the Extended

AppleTalk Network Example section in this chapter

Dynamically Configure 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

interface discovery mode an acquires information about the attached network from an operational

router and then uses this information to configure itself

Benefits of Dynamically Configuring an Interface

mode to Using discovery configure interfaces saves time if the network numbers cable ranges or If this zone names change happens you must make the changes on only one seed router on each network

mode is useful when Discovery you are changing network configuration or when you are adding router to an existing network

Configuring AppleTalk P2C-13 Enable AppleTalk Routing

Restrictions of Dynamically Configuring an Interface

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

be before the interface will become operational router must present 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

nondiscoverymode interface also called seed router starts up as follows

The seed router acquires its configuration from memory

address If the stored configuration is not completely specified when you assign an AppleTalk to

interface an interface on which you assign cable range and zone name the will not start up

stored If the stored configuration is completely specified the interface attempts to verify the

configuration with another router on the attached network If any discrepancy exists the interface

will not start up

If there are no neighboring operational routers the device will assume the interfaces stored

configuration is correct and the interface will become operational

Response to Configuration Queries

Using discovery mode does not affect an interfaces ability to respond to configuration queries from

other routers on the connected network once the interface becomes operational

Dynamically Configure 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

the interface into In the first method you immediately place 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 use this method perform the following task in interface configuration mode

Task Command

Place the interface into discovery mode by appletalk address 0.0

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

P2C-14 Network Protocols Configuration Guide Part Enable AppleTalk Routing

In 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 use this method perform the following tasks in interface configuration mode

Task Command

Step Assign an AppleTalk address to the appletalk address network.node

interface

Step Place the interface into discovery appletalk discovery mode

Dynamically Configure 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

this method when do number of the range of 00 Use you not know the network attached network

To use this method perform the following task in interface configuration mode

Task Command

Place the interface into discovery mode by appletalk cable-range 00

assigning it the cable range 0-0

In the second method you first assign cable ranges and then explicitly enable discovery mode Use the this method when you know cable range of the attached network Note however that you are not required to use this method if you know the cable range To use this method perform the following

tasks in interface configuration mode

Task Command

Step Assign an AppleTalk address to the appletalk cable-range cable-range

interface

Step Place the interface into discovery appletalk discovery mode

Select 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 Apple Update-Based Routing Protocol AURP on tunnel interface

With this task 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 interface perform the following task in interface

configuration mode

Task Command

Create an AppleTalk routing process appletalk protocol aurp eigrp rtmp

This task is optional If you do not select routing protocol for an interface Cisco lOS uses RTMP by default

Configuring AppleTalk P2C-1 Enable AppleTalk Routing

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

Configure 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

and the other is port is configured as nonextended AppleTalk network port 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

that connected the To configure transition mode you must have two ports on the same router are to

network the same physical cable You configure one port as nonextended AppleTalk by performing

following tasks in interface configuration mode

Task Command

Step Assign an AppleTalk address to the appletalk address network.node

interface

Step Assign zone name to the interface appletalk zone zone-name

You configure the second port as an extended AppleTalk network by performing the following tasks

in interface configuration mode

Task Command

Step Assign an AppleTalk cable range to appletalk cable-range cable-range node

the interface

Step Assign zone name to the interface appletalk zone zone-name

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

Enable Concurrent Routing and Bridging

You can route AppleTalk on some interfaces and transparently bridge it on other interfaces

simultaneously To do this you must enable concurrent routing and bridging

To enable concurrent routing and bridging perform the following task in global configuration mode

Task Command

Enable concurrent routing and bridging bridge crb

P2C-16 Network Protocols Configuration Guide Part Control Access to AppleTalk Networks

Configure 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 IRE 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 Bridging and IBM Networking configuration Guide

Contro Access to AppeTak Networks

Protocol An access list is list of AppleTalk network numbers zones or Name Binding NBP

named entities that is maintained by the Cisco lOS software and used to control access to or from

specific zones networks and NEP named entities

Types of Access Lists

The software supports the following two general types of AppleTalk access lists

AppleTalk-style access lists which are based on AppleTalk zones or NBP named entities

IP-style access lists which are based on network numbers

AppleTalk-Style Access Lists

AppleTalk-style access lists regulate the internetwork using zone names and NBP named entities

Using Zone Names

Zone names and NEP named entities are good control points because they allow for network-level

abstractions that users can access

You can express zones 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 the AppleTalk zone name access lists allows you to manage and control whole sections of 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

based the of the or name from particular NBP named entity on object portion NBP tuple name

from all NBP named entities within particular area based on the zone portion of the NBP tuple

name You can fully or partially qualify an NBP tuple name to refine the access control by specifying

three of the list entries tied the one two or parts NBP name tuple as separate access together by same number sequence

Configuring AppleTalk P2C-17 Control Access to AppleTalk Networks

Benefits of AppleTalk-Style Access Lists

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 effectively dynamic list of network numbers

but the the The user specifies zone name effect is as if the user had specified all network numbers

belonging to that zone An NBP named entity access list provides means of controlling access at

the network entity level

P-Style Access Lists

IP-style access lists control network access based on network numbers This feature can be useful in

lists that defining access control the disposition of networks that overlap are contained by or exactly match specific network number range

Additionally you can use IF-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 if one group of

users LaserWriter installs this creates the gets and Cayman GatorBox new network segment

potential for confusion and misconfiguration is significant

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

the end of the list statement to access when using only one type of filtering For example suppose

you want to deny only zone You do not want to do 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

list this access for example would have an access-list deny zone entry to deny zone an

access-list permit additional-zones entry to permit all other zones and an access-list permit

other-access 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

P2C-18 Network Protocols Configuration Guide Part Control Access to AppleTalk Networks

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

Note These types of filters are completely independent of each other This 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 are that

outgoing routing update filters can affect GZL updates and ZIP reply filters can affect outgoing

routing updates

Implementation Considerations

Unlike access lists in other protocols the order of the entries in an AppleTalk access list is not

lists important However keep the following constraints in mind when defining access

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 enter permit network command and then enter deny network command If you do enter entries that overlap the last one you entered

overwrites and removes the previous one from the access list In this example this means that 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

Configuring AppleTalk P2C-19 Control Access to AppleTalk Networks

If do not how handle that do you explicitly specify to packets or routing updates not satisfy any

of 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

Control Access to AppleTalk Networks Task List

You perform the tasks in the following sections to control access to AppleTalk networks

Create access lists

Create filters

Create Access Lists

An access list defines the conditions used to filter packets sent into or out of the interface Each

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

However you can specify only one each of the commands that specify default 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 to handle networks and cable that do match the ranges not 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

Set Priority Queuing

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 queuing the Cisco lOS software applies the access list to the destination network

Automatic Fast Switching

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

P2C-20 Network Protocols configuration Guide Part Control Access to AppleTalk Networks

Create AppleTalk-Style Access Lists

Complete the tasks in the following sections to create AppleTalk-style access lists

Create Zone Access Lists

Create Priority Queuing Access Lists

Create NBP Access Lists

Create Zone Access Lists

To create access lists that define access conditions for zones AppleTalk-style access lists perform

one or more of the following tasks in global configuration mode

Task Command

Define access for zone access-list access-list-number deny permit zone

zone-name

Define the default action to take for access access-list access-list-number deny permit

checks that apply to zones additional-zones

For examples of how to create access lists see the AppleTalk Access List Examples and Hiding

Access List sections at the end of this and Sharing Resources with Examples chapter

Create Priority Queuing Access Lists

will be based the zone To assign priority in which packets destined for specific zone queued on mode access list perform the following task in global configuration

Task Command

Define access for single network number priority-list list-number protocol protocol-name high

medium normal low list access-list-number

Create NBP Access Lists

To create access lists that define access conditions for NBP packets based on the NBP packet type from NBP named from particular NBP named entities from classes of NBP named entities or

in entities within particular zones perform one or both of the following tasks global configuration mode

Task Command

Define access for an NBP packet type NBP access-list access-list-number deny permit nbp

named entity type of named entity or named sequence-number BrRq FwdRq Lookup LkReply

entities within specific zone object string type string zone stringI

Define the default action to take for access access-list access-list-number deny permit

checks that apply to NBP named entities other-nbps

the an Access List For an example of how to create NBP packet filtering access lists see Defining

section the of this to Filter NBP Packets Example at end chapter

Configuring AppleTalk P2C-21 Control Access to AppleTalk Networks

Create PP-Style Access Lists

To create access lists that define access conditions for networks and cable ranges IP-style access

lists perform one or more of the following tasks in global configuration mode

Task Command

Define access for single network number access-list access-list-number deny permit network

network broadcast-permit

Define for cable access single range access-list access-list-nunber deny permit

cable-range cable-range

broadcast-permit

Define access for an extended or nonextended access-list access-list-number deny permit includes

network that overlaps any part of the specified cable-range broadcast-permit

range

Define access for an extended or nonextended access-list access-list-number deny permit within

network that is included entirely within the cable-range broadcast-permit

specified range

Define the default action to take for access access-list access-list-number deny permit

checks that apply to network numbers or cable other-access

ranges

Create Filters

filter examines of that specific types packets 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

Complete the tasks in the following sections to filter different types of AppleTalk packets

Create NBP Packet Filters

Create Data Packet Filters

Create Routing Table Update Filters

Create GetZoneList GZL Filters

Enable ZIP Reply Filters

Enable Partial Zone Filters

number You can apply any 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

Create NBP Packet Filters

To create an NBP packet filter perform the following tasks

Step Create an NBP access list as described in the Create NBP Access Lists section of this

chapter

Step Apply an NBP filter to an interface

P2C-22 Network Protocols Configuration Guide Part Control Access to AppleTalk Networks

To apply an NBP filter to an interface perform the following task in interface configuration mode

Task Command

Apply the data packet filter to the interface appletalk access-group access-list-number out

Note Prior to Cisco lOS Release 11.2 all NBP access lists were applied to inbound interfaces by

default Using Cisco lOS 11.2 or later software 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

Create Data Packet Filters

data packet filter checks data packets being received on and 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

When you apply data packet filter to an interface ensure that all 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 perform the following tasks

Step Create network-only access list as described in the Create Zone Access Lists and

Create IP-Style Access Lists sections of this chapter

Step Apply data packet filter to an interface

To apply the data packet filter to an interface perform the following task in interface configuration mode

Task Command

Apply the data packet filter to the interface appletalk access-group access-list-number out

For an example of how to create data packet filters see the AppleTalk Access List Examples

section at the end of this chapter

Create 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

Filters conditions for networks ranges only for outgoing routing updates use access lists that define

and cable ranges and for zones

in the is When filtering incoming routing updates each network number and cable range update

checked against the access list If you have not applied an access list to the interface all network

list has numbers and cable ranges in the routing update are added to the routing table If an access

been applied to the interface only network numbers and cable ranges that are not explicitly or

implicitly denied are added to the routing table

Configuring AppleTalk P2C-23 Control Access to AppleTalk Networks

The following conditions are also applied when filtering routing updates generated by the local router

The network number cable is member that is or range not of zone explicitly or implicitly denied

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 cable or ranges that are members of the zone are explicitly or implicitly

permitted

Create Routing Table Update Filters for Incoming Updates

To filter for table create routing updates received on an interface perform the following tasks

Step Create an access list as described in the Create IP-Style Access Lists section of this

chapter

Step Apply routing table update filter to an interface

Note Cisco lOS software ignores zone entries Therefore ensure that access lists used to filter do contain incoming routing updates not any zone entries

To the filter apply to incoming routing updates on an interface perform the following task in

interface configuration mode

Task Command

Apply the routing update filter appletalk distribute-list access-list-number in

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

Create Routing Table Update Filters for Outgoing Updates

To create filter for routing table updates sent out an interface perform the following tasks

Step Create an access list as described in the Create Zone Access Lists and Create IF-Style

Access Lists sections of this chapter

Step Apply routing table update filter to an interface

Note You can use zone entries in access lists used to filter outgoing routing updates

To apply filter to routing updates sent out on an interface perform the following task in interface

configuration mode

Task Command

Apply the routing update filter appletalk distribute-list access-list-number out

P2C-24 Network Protocols Configuration Guide Part Control Access to AppleTalk Networks

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 an Enhanced

IGRP interface any access-list zone commands in the specified access list will be ignored

Create GetZoneList GZL Filters

The Macintosh Chooser uses ZIP GZL requests to compile list of zones from which the user can

select services Any router on the same network as the Macintosh can respond to these requests with

GZL reply You can create GZL filter to control which zones the Cisco lOS software mentions

in its GZL replies This has the effect of controlling the list of zones that are displayed by the Chooser

When defining GZL filters you should ensure that all routers on the same network filter GZL replies

identically Otherwise the Chooser will list different zones depending on which device responded to

inconsistent filters result in and the request Also can zones appearing disappearing every few

seconds when the user remains in the Chooser 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

When ZIP GZL reply is 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

Replies to GZL requests also are filtered by any outgoing routing update filter that has been applied

to the same interface You must apply GZL filter only if you want additional filtering to be applied

to GZL replies This filter is rarely needed except to eliminate zones that do not contain user

services

filter is for numbers Using GZL not complete replacement anonymous network To prevent users

all the the from seeing zone routers must implement GZL filter If any devices on network are from

other vendors the GZL filter will not have consistent effect

To create GZL filter perform the following tasks

Step Create an access list as described in the Create Zone Access Lists section of this

chapter

Step Apply GZL filter to an interface

To apply the GZL filter to an interface perform the following task in interface configuration mode

Task Command

Apply the GZL filter appletalk getzonelist-filter access-list-number

For an example of how to create GZL filters see the GZL and ZIP Reply Filter Examples section

at the end of this chapter

Configuring AppleTalk P2C-25 Control Access to AppleTalk Networks

Enable ZIP Reply Filters

ZIP reply filters limit the visibility of zones from routers in unprivileged regions throughout the

internetwork These filters filter the list for each network zone 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

ZIP filters determine which networks reply and cable ranges the Cisco lOS software sends out in

routing updates Before sending out routing updates the software excludes the networks and cable whose have been ranges zones completely denied access by ZIP reply filters Excluding this

information that ensures routers receiving these routing updates do not send unnecessary ZIP

requests

To create ZIP reply filter perform the following tasks

Step Create an access list as described in the Create Zone Access Lists section of this

chapter

Step Apply ZIP reply filter to an interface

the To apply ZIP reply filter to an interface perform the following task in interface configuration mode

Task Command

Apply the ZIP reply filter appletalk zip-reply-filter access-list-number

For of how to create and an example GZL ZIP reply filters see the GZL and ZIP Reply Filter

Examples section at the end of this chapter

Enable Partial Zone Filters

If to network in is access any zone denied access to that zone is also denied by default However

if you enable partial zones access to other networks in that zone is no longer denied

The permitting of partial zones provides IP-style access control If enabled the access control list

behavior associated with prior software releases is restored In addition NBP cannot ensure

consistency and uniqueness of name bindings

If you permit partial zones AppleTalk cannot maintain consistency for the nodes in the affected

and the results undefined zones are With this option enabled an inconsistency is created for the and several zone assumptions made by some AppleTalk protocols are no longer valid

To enable partial zone filters perform the following task in global configuration mode

Task Command

Permit access to networks in zone in which appletalk permit-partial-zones

access to another network in that zone is denied

Permitting partial zones affects the outgoing routing update and GZL filters

P2C-26 Network Protocols Configuration Guide Part Configure the Name Display Facility

Configure the Name Display Facility

Protocol associates network The AppleTalk Name Binding NBP AppleTalk 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 NEP translates the devices entity name into the devices network includes address The name binding process 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 colTect addresses if

the addresses change These node addresses do 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 it is moved to another network segment

To control the name display facility perform one or both of the following tasks in global

configuration mode

Task Command

Specify which service types are retained in the appletalk lookup-type service-type name cache

Set the interval between service pollings by the appletalk name-lookup-interval seconds

router on its AppleTalk interfaces

Set Up Special Configurations

the tasks in the desired To set up special configurations perform following sections based on service

implementations

Configure AURP

Configure Free-Trade Zones

Configure SNMP over DDP in AppleTalk Networks

Configure AppleTalk Tunneling

Configure AppleTalk MacIP

Configure IPTalk

Configure SMRP over AppleTalk

Configure AURP

The AppleTalk Update Routing Protocol AURP is 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 ercapsulates an AppleTalk packet inside an

IP packet which is sent across the backbone to destination router The destination device then

the if network The extracts AppleTalk packet and necessary routes it to an AppleTalk encapsulated

benefits from features default packet any normally applied to IP packets including fragmentation

routes and load balancing

Configuring AppleTalk P2C-27 Set Up Special Configurations

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

Since 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 perform the following tasks beginning in global configuration mode

Task Command

Step Enable route redistribution appletalk route-redistribution

Step Configure an interface to be used by interface type number

the tunnel

Step Configure an IP address ip address ip-address mask

Step Configure tunnel interface interface tunnel number

Step Create an AURP routing process appletalk protocol aurp

Step Specify the interface out of which the tunnel source ip-address type number

encapsulated packets will be sent

Step Specify the IP address of the router at tunnel destination hostname ip-address

the far end of the tunnel

AURP Step Enable tunneling tunnel mode aurp

You can configure AURP on tunnel interface to inherit AppleTalk interenterprise routing

remapping hop count reduction and loop detections 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 Enable AppleTalk Interenterprise Routing Remap Network

Numbers and Control Hop Count within the section Configure AppleTalk Interenterprise

Routing later in this chapter

To configure AURP for AppleTalk interenterprise routing features perform the following tasks

starting in global configuration mode

Task Command

Step Specify the tunnel interface interface tunnel number

Step Create an AURP routing process appletalk protocol aurp

Step Enable AURP tunneling tunnel mode aurp

Step Specify the interface out of which the tunnel source ip-address type nuinber

encapsulated packets will be sent

Step Specify the IP address of the router at tunnel destination hostnwne ipaddress the far end of the tunnel

Step Assign the number of the predefined appletalk domain-group domain-number

AppleTalk domain to which the

AppleTalk interenterprise features are

configure 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

P2C-28 Network Protocols Configuration Guide Part Set Up Special Configurations

By default AURP sends routing updates every 30 seconds To modify this interval perform the

following task in global configuration mode

Task Command

Set the minimum interval between AURP appletalk aurp update-interval seconds

routing updates

To set the last-heard-from timer the AURP value perform following task in interface configuration mode

Task Command

Set the AURP last-heard-from timer value appletalk aurp tickle-time seconds

Configure Free-Trade Zones

free-trade is of zone part an AppleTalk internetwork that is accessible by two other parts of the neither of internetwork which can access the other You might want to create free-trade zone to allow the of exchange 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 perform the following task in interface configuration mode

Task Command

Establish free-trade zone appletalk free-trade-zone

For an example of how to configure free-trade zone see the Hiding and Sharing Resources with

Access List section and the Examples Establishing Free-Trade Zone Example section at the end

of this chapter

Configure SNMP over DDP in AppleTalk Networks

The Network Simple Management Protocol SNMP normally uses the IP connectionless datagram service the User Datagram Protocol UDP to monitor network entities The Cisco lOS software lets SNMP you run using Datagram Delivery Protocol DDP the AppleTalk datagram service Use DDP if you have SNMP consoles running on Macintosh

You must configure AppleTalk routing globally and on an interface basis before you configure for the SNMP router therefore you need to disable SNMP as shown in the following task table

To configure SNMP in AppleTalk networks perform the following tasks starting in global

configuration mode

Task Command

Step Disable SNMP no snmp server

Enable Step AppleTalk routing appletalk routing

Enable Step AppleTalk event logging appletalk event-logging

Enter Step interface configuration mode interface type number

Enable IP Step routing on the interface ip address ip-address mask

Enable Step AppleTalk routing on the appletalk cable-range cable-range

interface

Configuring AppleTalk P2C-29 Set Up Special Configurations

Task Command

Step Set zone name for the AppleTalk appletalk zone zone-name network

Step Enable SNMP server operations snmp-server community string

For an example of how to configure SNMP see the SNMP Example section at the end of this

chapter

For information about configuring SNMP refer to the Monitoring the Router and Network chapter

in the Configuration Fundamentals Configuration Guide

Configure AppleTalk Tunneling

When connecting two AppleTalk networks with non-AppleTalk backbone such as IP the relatively

high bandwidth consumed by the broadcasting of Routing Table Maintenance Protocol RTMP data

the backbones network You solve this packets can severely hamper performance can problem by

tunneling AppleTalk through foreign protocol such as IP Tunneling encapsulates an AppleTalk

inside the which is then sent the backbone to destination packet foreign protocol packet across

router The destination router then de-encapsulates the AppleTalk packet and if necessary routes the

normal network Because the is sent in packet to AppleTalk encapsulated AppleTalk packet

IP bandwidth is reduced the directed manner to remote address usage greatly Furthermore

benefits from features IP default encapsulated packet any normally enjoyed by packets including

routes and load balancing

There are two ways to tunnel AppleTalk The first method implements Cayman tunneling as

GatorBoxes The second method is proprietary tunnel protocol known as generic routing

encapsulation GRE

When you use Cayman tunneling you can have Cisco routers at either end of the tunnel or you can

end Cisco the have GatorBox at one and router at other end When you use GRE tunneling you

must have Cisco routers at both ends of the tunnel connection

Multiple tunnels originating from the router are supported

Logically tunnels are point-to-point links This requires that you configure separate tunnel for each link

in To configure Cayman tunnel perform the following tasks interface configuration mode

Task Command

Step Configure tunnel interface interface tunnel number

Step Specify the interface out of which the tunnel source ip-address type number

encapsulated packets will be sent

Step Specify the IP address of the router at tunnel destination hostnaine ip-address

the far end of the tunnel

Step Enable Cayman tunneling tunnel mode cayman

Caution Do not configure Cayman tunnel with an AppleTalk network address

P2C-30 Network Protocols Configuration Guide Part Set Up Special Configurations

To configure GRE tunnel perform the following tasks

Task Command

Step Configure tunnel interface interface tunnel number

Step Specify the interface out of which the tunnel source ip-address type number

encapsulated packets will be sent

Step Specify the IP address of the router at tunnel destination hostname ip-address

the far end of the tunnel

Step Enable GRE tunneling tunnel mode gre ip

Configure AppleTalk MaciP

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 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

MTU and that are bound for DDP clients of MacJR

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 Remote Access AppleTalk 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

MacIP services also be useful can when you are managing IP address allocations for large dynamic

Macintosh population

Advantages of Using MaciP

The following are advantages to using MacIP when you are managing IP address allocations for

large dynamic Macintosh population

Macintosh TCP/IP drivers can be configured in completely standard way regardless of the location 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 DNS services and default Macintosh routers 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 This allows central administration of IP

allocations in remote locations For Internet sites it allows remote technical assistance

Configuring AppleTalk P2C-31 Set Up Special Configurations

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

so this increases traffic through the device There is also slight increase in 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

Any IP address specified in configuring MacIP server using an appletalk macip command

must be associated to specific IP interface on the router Because the Cisco lOS software is

acting as proxy for MacIP clients you must use an IP address to which ARP can respond

If you are using MacIP to allow Macintoshes to communicate with IP hosts on the same LAN segment that is the Macintoshes are on the router interface on which MacIP is configured and

the IP hosts have extended IP access lists these access lists should include entries to permit IP

traffic destined for these IP hosts from the MacIP addresses If these entries are not present

blocked will be packets destined for IP hosts on the local segment will be that is they not forwarded

in mind When setting up MacIP routing keep the following address range issues

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 ranges For example specifying the range 131.108.121.1 to 131.108.121.10 is

preferable to specifying the ranges 131.108.121.1 to 131.108.121.5 and 131.108.121.6 to 131 108 121 10

Overlappingresourceranges for example 131.108.121.1 to 131.108.121.5 and 131.108.121.5

to 131108.121.10 are not allowed If it is necessary to change range in running server use

the negative form of the 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

You can add IP address allocations to running server at any time as long as the new address

does with of the range not overlap one current ranges

Configure AppleTalk MaciP Task List

To configure MacIP perform the following tasks

Step Establish MacIP Server for Zone

Step Allocate IP Addresses for Macintosh Users You do this by specifying at least one

dynamic or static resource address assignment command for each MacIP server

P2C-32 Network Protocols Configuration Guide Part Set Up Special Configurations

Establish MaciP Server for Zone

To establish MacIP server for specific zone perform the following task in global configuration mode

Task Command

Establish MacIP for server zone appletalk macip server ip-address zone server-zone

Note that the MacIP server must reside in the default AppleTalk zone

You can configure multiple MacIP servers for router but you can assign only one MacIP server to

and can one IP interface to MacIP zone you assign only server In general you must be able to establish an alias between the IP address with the you assign appletalk macip server global command and an IP interface configuration existing For implementation simplicity the address you in this specify command should match an existing IP interface address

server is not registered by NBP until at least one MacIP resource is configured

Allocate 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

Allocate IF Addresses Using Dynamic Addresses

Dynamic clients are those that IP address within the accept any assignment dynamic range specified addresses for Dynamic are users who 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 perform the

following task in global configuration mode

Task Command

Allocate an IP address to MacIP client appletalk macip dynamic ip-address zone

server-zone

For an of MacIP with example configuring dynamic addresses see the AppleTalk Interenterprise

Routing over AURP Example section at the end of this chapter

Allocate IF Addresses Using Static Addresses

Static addresses are for users who require fixed addresses for IP DNS services and for administrators

who 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 perform the following

task in global configuration mode

Task Command

Allocate an IP address to be used by MacIP appletalk macip static ip-address zone

client that has reserved static 1P address server-zone

For of an example configuring MacIP with static addresses see the MacIP Examples section at the

end of this chapter

Configuring AppleTalk P2C-33 Set Up Special Configurations

In general it is recommended that you do not use fragmented address ranges in configuring ranges

for MacIP However if this is unavoidable use the appletalk macip dynamic command to specify

as many addresses or ranges as required and use the appletalk macip static command to assign

specific address or address range

Configure IPTaIk

IPTalk is protocol for encapsulating AppleTalk packets in IP datagrams IPTalk is used to route

AppleTalk packets across non-AppleTalk backbones and to communicate with applications on hosts that 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

ULTRIX it be to If your system is Sun or Digital Equipment Corporation system may possible run

would look like other CAP directly in mode that supports EtherTalk In this case your system any

other for AppleTalk node and does not need any special IPTalk support However UNIX systems in mode that IPTalk which EtherTalk support is not available in CAP must run CAP depends upon

The installation instructions for CAP refer to Kinetics IP KIP gateways and to the file atalkatab If atalkatab Cisco IPTaIk you use Cisco IPTalk support it is not necessary nor is it desirable to use all support assumes that you want to use the standard AppleTalk routing protocols to perform

in which wide-area AppleTalk routing KIP and atalkatab are based on an alternative routing strategy both the AppleTalk packets are transmitted using IP routing It is possible to use strategies at same

time however the interaction between the two routing techniques is not well defined

that should disable atalkatab If your network has other vendors routers support atalkatab you

The installation instructions with support on them to avoid mixing the routing strategies provided

atalkatab for networks with Cisco some of these products encourage you to use complex However

of IPTa1k IPTallc into the routers this is not necessary because our implementation integrates

standard AppleTalk network routing

The network diagram in Figure illustrates how you should set up IPTa1k In this configuration you enable both standard AppleTalk EtherTalk and IPTalk on the Ethernet networks on Router and

Router These routers then use EtherTalk to communicate with the LocalTalk routers and

Macintosh computers and IPTalk to communicate with the UNIX systems On the LocalTalk IPTalk with routers you also should enable both EtherTalk and IPTalk making sure you configure ataikatab 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

If did not enable IPTalk configuration strategy minimizes the number of hops between routers you communicate with the on the LocalTalk routers systems on the LocalTalk router that wanted to This adjacent UNIX system would have to go through Router or Router creates an unnecessary extra hop

Note In the configuration in Figure all traffic between systems on the left and right sides of the

and If were to enable packet-switched network transit via Routers using AppleTalk routing you

this would establish hidden between Routers atalkatab support on the LocalTalk routers path

and unknown to the standard AppleTalk routing protocols In large network this could result in

traffic taking inexplicable routes

P2C-34 Network Protocols Configuration Guide Part Set Up Special Configurations

Figure IPTaIk Configuration Example

UNIX Macintosh system Macintosh UNIX system -i

LocalTalk LocalTalk Router Router

LocalTalk LocalTalk

To IPTalk configure on an interface perform the following tasks

Step Configure IP encapsulation of AppleTalk packets

the number that is the of the Step Specify UDP port beginning range of UDP ports used in

mapping AppleTalk well-known DDP socket numbers to UDP ports

Configure IP Encapsulation of AppleTalk Packets

To allow AppleTalk to communicate with UNIX hosts running older versions of CAP that do 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 KIP software Newer versions of native EtherTalk CAP provide AppleTalk encapsulations so the IPTalk encapsulation is no longer Cisco of IPTalk required implementation assumes that AppleTalk is already being routed on the

backbone because there is currently no LocalTalk hardware interface for our routers

You IPTalk tunnel configure on 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 if AppleTalk packet and necessary routes it to an AppleTalk network The encapsulated benefits from features packet any normally applied to IP packets including fragmentation default

routes and load balancing

Cisco implementation of IPTalk does not support manually configured AppleTalk-to-IP-address The address mapping mapping provided is the same as the Kinetics IPTalk implementation when

AppleTalk-to-IP-address mapping is not enabled This address mapping works as follows The IP subnet mask used the on router tunnel source interface on which IPTalk is enabled is inverted ones The complement result is then masked against 255 OxFF hexadecimal and 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 configuration illustrates how the address mapping is done

interface EthernetO ipaddress 172.16.1.118 255.255.255.0 appletalk address 20.129 appletalk zone Native AppleTalk interface TunnelO

Configuring AppleTalk P2C-35 Set Up Special Configurations

tunnel source Ethernet0 tunnel mode iptalk appletalk iptalk 30 UDPZ0ne

is First the IP subnet mask of 255.255.2550 is inverted to give 00.0.255 This value then masked

with 255 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 This 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 Ethernet to obtain conflicting AppleTalk node numbers For instance if the subnet

interface above is 255.255.240.0 the host field is 12 bits wide

To configure IP encapsulation of AppleTalk packets perform the following tasks in interface

configuration mode

Task Command

Configure an interface to be used by the tunnel interface type nunber

Configure an IP addresi ip address ip-address mask

Configure tunnel interface interface tunnel number

Specify the interface out of which the tunnel source ip-address type number

encapsulated packets will be sent

Enable IPTalk tunneling tunnel mode iptalk

For an example of configuring IPTalk see the IPTalk Example section at the end of this chapter

Specify the UDP Port Ranges

socket numbers Implementations of IPTalk prior to April 1988 mapped well-known DDP to the Network Information Center privileged UDP ports starting at port number 768 In April 1988

of for the defined well-known sockets at NIC assigned range UDP ports DDP starting UDP port and at-zis Release and number 200 and assigned these ports the names at-nbp at-rtmp at-echo there later of the CAP program dynamically decides which port mapping to use If are no AppleTalk

service entries in the UNIX systems /etc/services file CAP uses the older mapping starting at UDP

port number 768

there The default UDP port mapping supported by our implementation of IPTaIk is 768 If are

AppleTalk service entries in the UNIX systems /etc/services file 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 perform the following task in global

configuration mode

Task Command

Specify the starting UDP port number appletalk iptak-baseport

For an example of configuring IPTalk see the IPTalk Example section at the end of this chapter

P2C-36 Network Protocols Configuration Guide Part Set Up Special Configurations

Configure SMRP over AppleTalk

The Simple Multicast Routing Protocol SMRP provides an internetwork-wide multicast service

that the of data from supports sending 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

Ciscos current of implementation SMRP provides multicast routing functions over AppleTalk networks Advanced multimedia applications such as QuickTime Conferencing QTC allow for two machines or more to communicate in session By routing AppleTalk packets to all members of without multipoint group replicating packets on link SMRP presents an economical and

efficient to this kind way support of communication while conserving network bandwidth

Ciscos of implementation SMRP can be characterized by the following aspects

Group membership services that determine which hosts receive multicast traffic SMRP allows

host to for the multicast sessions in register dynamically which it elects to participate

multicast that Cisco Dynamic routing gives 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 Cisco send groups path routers only one copy of each packet over each physical network

Fast of data switching SMRP packets that allows higher data traffic throughput and less CPU

utilization

shows how Figure SMRP multicasting of packets proceeds across an AppleTalk network The router sends source Router multicast packet only once on the local AppleTalk network

Figure SMRP Packet Transmission over AppleTalk

Duplicates

packet

Sends only to ports with group members

Applications produced by Apple Computer Inc such as QTC will support SMRP To provide this Cisco and support Systems Apple Computer Inc have entered into partnership becoming the first

vendors to license internetworking the SMRP technology

To enable SMRP routing over AppleTalk networks perform the following task in global configuration mode

Task Command

Enable SMRP smrp routing

Configuring AppleTalk P2C-37 Configure AppleTalk Control Protocol for Point-to-Point Protocol

To configure SMRP over AppleTalk for specific interface perform the following task in interface

configuration mode

Task Command

Configure an SMRP on the interface smrp protocol appletalk

beginning-end

the cable default Note The network-range maps to AppleTalk range by

Fast switching allows higher throughput by switching packet using cache created by previous

and interface packets By default fast switching is enabled on all SMRP ports network protocol

comprise an SMRP port

SMRP uses the forwarding table to forward 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 When data for an SMRP group arrives on the parent interface the router forwards it to

each child interface The SMRP fast switching cache table specifies whether or not to fast switch

SMRP data packets out the interfaces specified by the forwarding table

To disable SMRP fast switching on an interface perform the following task from interface

configuration mode

Task Command

Disable SMRP fast switching on an interface no smrp mroute-cache protocol appletalk

Configure AppeTak Contro Protoco for Pont4oPont Protoco

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 Point-to-Point Protocol PPP to this interface This is done 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 is virtual the network and exists only for accessing an AppleTalk internetwork through server

To create new AppleTalk zone issue the appletalk virtual-net command and use new zone

name this network number is then the 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 perform the following tasks in interface configuration asynchronous mode

Task Command

Step Specify an asynchronous interface interface async number

Step Create an internal network on the appletalk virtual-net network-number zone-name

server

P2C-38 Network Protocols Configuration Guide Part Tune AppleTalk Network Performance

Task Command

Step Enable PPP encapsulation on the encapsulation ppp interface

Step Enable client-mode on the interface appletalk client-mode

For an of example configuring ATCP see the AppleTalk Control Protocol Example section at the end of this chapter

Tune AppeTak Network Performance

To tune network AppleTalk performance you can perform one or more of the tasks described in the following sections

Control Routing Updates

Assign Proxy Network Numbers

Enable Round-Robin Load Sharing

Disable Checksum Generation and Verification

Control the AppleTalk ARP Table

Control the Delay between ZIP Queries

Log Significant Network Events

Disable Fast Switching

Control Routing Updates

The Table Maintenance Routing Protocol RTMP establishes and maintains the AppleTalk routing table You the tasks can perform in the following sections to control packet routing and control routing updates

Disable the Processing of Routed RTMP Packets

Enable RTMP Stub Mode

Disable the Transmission of Routing Updates

Prevent the Advertisement of Routes to Networks with No Associated Zones

Set Routing Table Update Timers

Disable the Processing of Routed RTMP Packets

By default the Cisco lOS software strict discards performs RTMP checking which any RTMP sent routers packets by not directly connected to the local device that is sent by devices that are not

neighbors This means that 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

Configuring AppleTalk P2C-39 Tune AppleTalk Network Performance

To disable RTMP checking and enable the processing of routed RTMP packets perform the

following task in global configuration mode

Task Command

Disable strict checking of RTMP updates no appletalk strict-rtmp-checking

Enable 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

The first indicates the network number stub packet is only the first tuple of an RTMP packet tuple

determine if their node number is in range assigned to that network End nodes use stub packets to

the right network range

To enable AppleTalk RTMP stub mode perform the following task in interface configuration mode

Task Command

Enable RTMP stub mode appletalk rtmp-stub

Disable the Transmission of Routing Updates

and send By default routers receive routing updates from their neighboring devices periodically

that it receives routing updates to their neighbors You can configure the Cisco lOS software so only

routing updates but does not send any updates You might want to do this to keep particular router

that is unreliable from sending routing updates to its neighbors

To disable the transmission of routing updates perform the following task in interface configuration mode

Task Command

Disable the transmission of routing updates on no appletalk send-rtmps

an interface

Prevent 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 This which arise when routes prevents the occurrence of ZIP protocol storms can corrupt are propagated

and routers broadcast ZIP requests to determine the network-zone associations By not advertising

limit ZIP storms to routes to networks that do not have associated zones you any protocol 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 perform the

following task in global configuration mode

Task Command

Allow the advertisement of routes to networks no appletalk require-route-zones

that have no associated zones

P2C-40 Network Protocols Configuration Guide Part Tune AppleTalk Network Performance

The user zone lists can be to from interface interface configured vary to However this practice is

discouraged because users to have the AppleTalk expect same user zone lists at any end node in the internetwork This kind of does not filtering 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

Set 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 and cannot send busy routing updates every 10 seconds or when slower devices of are incapable 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 timers can or network routing degrade destroy AppleTalk connectivity other router vendors Ak Many AppleTalk provide no facility for modifying their routing timers so

adjusting Cisco AppleTalk timers such that routing updates do not arrive at these other routers within

the normal interval result in loss of information about the network loss might or of connectivity

To the table change routing update timers perform the following task in global configuration mode

Task Command

Change the routing update timers appletalk timers update-interval valid-interval

invalid-interval

Assign Proxy Network Numbers

It is to have an possible AppleTalk internetwork in which some routers support only nonextended and others extended AppleTalk support only AppleTalk You can enable interoperability between these two of networks types AppleTalk by assigning proxy network number for each zone in which

there is device that supports only nonextended AppleTalk

To network assign proxy numbers perform the following task in global configuration mode

Task Command

Assign proxy network number for each zone appletalk proxy-nbp network-nwn her zone-name

in which there is device that supports only

nonextended AppleTalk

For of how an example to configure proxy network numbers see the Proxy Network Number section the Example at end of this chapter

Caution Do not also the network assign proxy number to router or to physical network

You must one network number for assign proxy each zone You can optionally define additional

proxies with different network numbers to provide redundancy Each proxy network number

one or more for each generates packets forward request it receives but discards all other packets sent to it redundant network Thus defining proxy numbers increases the NBP traffic linearly

Configuring AppleTalk P2C-41 Tune AppleTalk Network Performance

Enable Round-Robin Load Sharing

reach In order to increase throughput in the network router can use multiple equal-cost paths to

this destination By default the router picks one best path and sends all traffic using path You can

balance the configure the router to remember two or more paths that have equal costs and to 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 equal-cost paths can save memory on routers with limited memory or with in with number of and very large configurations Additionally networks large multiple paths

suffer when traffic systems with limited ability to cache out-of-sequence packets performance might

is split between many paths

To set the maximum number of paths perform the following task in global configuration mode

Task Command

Set the maximum number of equal-cost paths appletalk maximum-paths paths

to destination

Disable Checksum Generation and Verification

By default the Cisco lOS software generates and verifies checksums for all AppleTalk packets

if except routed packets You might want to disable checksum generation and verification you have

older devices such as LaserWriter printers that cannot receive packets with checksums

To disable checksum generation and verification perform the following task in global configuration mode

Task Command

Disable the generation and verification of no appletalk checksum

checksums for all AppleTalk packets

Control the AppleTalk ARP Table

You can perform the following tasks to control the AppleTalk ARP table

Set the timeout for ARP table entries

Specify the time interval between the retransmission of ARP packets

Specify the number of ARP retransmissions

Disable the gleaning of ARP information from incoming packets

been By default entries in the AppleTalk ARP table are removed from the table if no update has in received in the last hours To change the ARP timeout interval perform the following task

interface configuration mode

Task Command

Set the timeout for ARP table entries appletalk arp-tinieout interval

P2C-42 Network Protocols Configuration Guide Part Tune AppleTalk Network Performance

AppleTalk ARP associates AppleTalk network addresses with media data link addresses When send AppleTalk must packet to another network node the protocol address is passed to AppleTalk undertakes ARP which series of address negotiations to associate the protocol address with the media address

If has devices that your AppleTalk network respond slowly such as printers and overloaded file

servers you can lengthen the interval between AppleTalk ARP packets in order to allow the

from these devices to be received To do responses this perform one or both of the following tasks in global configuration mode

Task Command

the Specify time interval between appletalk arp request interval interval retransmission of ARP packets

the number of Specify retransmissions that will appletalk arp requesti retransmit-count

occur before abandoning address negotiations nwnber

and using the selected address

The Cisco lOS software automatically derives ARP table entries from incoming packets This

is referred to process as gleaning Gleaning speeds up the process of populating the ARP table To

disable the of table gleaning ARP entries perform the following task in interface configuration mode

Task Command

Disable the gleaning of ARP information from no appletalk glean-packets incoming packets

Control the Delay between ZIP Queries

the Cisco lOS software sends ZIP By default queries every 10 seconds and uses the information

received to its table To the update zone change ZIP query interval perform the following task in global configuration mode

Task Command

Set the ZIP query interval appletalk zip-query-interval interval

Log Significant Network Events

You information can log about significant network events performed on the router including routing

changes zone creation port status and address To do this perform the following task in global

configuration mode

Task Command

Log significant events appletalk event-logging

Disable 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

Configuring AppleTalk P2C-43 Configure AppleTalk Enhanced IGRP

Packet transfer performance is generally better when fast switching is enabled However you may

want to disable fast switching in order to save memory space on interface cards and to help avoid

congestion when high-bandwidth interfaces are writing large amounts of information to

low-bandwidth interfaces

To disable AppleTalk fast switching on an interface perform the following task in interface

configuration mode

Task Command

Disable AppleTalk fast switching no appletalk route-cache

Configure AppeTak Enhanced GRP

Protocol Enhanced IGRP is an enhanced version of the Interior Gateway Routing IGRP developed

by Cisco Systems Inc Enhanced IGRP uses the same distance vector algorithm and distance of Enhanced information as IGRP However the convergence properties and the operating efficiency

IGRP have improved significantly over IGRP

Benefits of Using AppleTalk Enhanced IGRP

Because Enhanced IGRP supports AppleTalk IPX and IP you can use one routing protocol for of multiprotocol network environments minimizing the size of the routing tables and the amount

routing information

Convergence Technology

is research conducted at SRI International and an The convergence technology based on employs algorithm referred to as the Diffusing Update Algorithm DUAL This algorithm guarantees and allows all routers involved loop-free operation at every instant throughout route computation

time Devices that not affected in topology change to synchronize at the same are by topology

time with rivals that of changes are not involved in recomputations The convergence DUAL any

other existing routing protocol

Enhanced IGRP Features

Enhanced IGRP offers the following features

Fast convergenceThe DUAL algorithm allows routing information to converge extremely

quickly

Partial updatesEnhanced IGRP sends incremental updates when the state of destination

minimizes the changes instead of sending the entire contents of the routing table This feature

bandwidth required for Enhanced IGRP packets

Neighbor discovery mechanismThis is simple hello mechanism used to learn about

neighboring routers It is protocol-independent

ScalingEnhanced IGRP scales to large networks

P2C-44 Network Protocols Configuration Guide Part Configure AppleTalk Enhanced IGRP

Enhanced JGRP 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 Neighbor discovery/recovery is achieved with low overhead by

periodically sending small hello packets As long as hello packets are received device can

determine that is alive and this neighbor functioning Once status is determined the neighboring

routers can exchange routing information

Reliable Transport Protocol

The reliable is transport protocol responsible for guaranteed ordered delivery of Enhanced IGRP

packets to all neighbors It supports intermixed transmission of multicast and unicast packets Some Enhanced IGRP be packets must transmitted 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 Enhanced IGRP Therefore sends single multicast hello with an indication in the packet informing

the that the receivers packet need not be acknowledged Other types of packets such as updates

require acknowledgment and this is indicated in the packet The reliable transport has provision send to multicast packets quickly when there are unacknowledged packets pending Doing so helps

ensure that convergence time remains low in the presence of varying speed links

DUAL Finite-State Machine

The finite-state machine embodies the decision DUAL process for all route computations It tracks

all routes advertised all the by neighbors DUAL uses 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 to destination that is path guaranteed not to be part of routing ioop When there are no

feasible but there successors are neighbors advertising the destination recomputation must occur

This is the is process whereby new successor determined The amount of time it takes to recompute

the route affects the time convergence Recomputation is processor-intensive It is advantageous to

avoid if it is not recomputation necessary When topology change occurs DUAL will test for

feasible If feasible successors successors exist DUAL will use them in order to avoid unnecessary

recomputation

Protocol-Dependent Modules

The modules protocol-dependent are responsible for network layer protocol-specific tasks It is 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 table Enhanced AppleTalk routing Also IGRP is responsible for redistributing routes learned by

other AppleTalk routing protocols

Configuring AppleTalk P2C-45 Configure AppleTalk Enhanced IGRP

Ciscos Enhanced IGRP Implementation

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

supersede 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 hence 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 Public Switched Data Networks PSDNs traffic charges

Enhanced IGRP Configuration Task List

To configure AppleTalk Enhanced IGRP complete the tasks in the following sections At

minimum you must create the AppleTalk Enhanced IGRP routing process Configuring

Miscellaneous Parameters is optional

Enable AppleTalk Enhanced IGRP

Configure Miscellaneous Parameters

Enable AppleTalk Enhanced IGRP

To create an AppleTalk Enhanced IGRP routing process perform the following tasks

Task Command

Step Enable an AppleTalk Enhanced IORP appletalk routing eigrp router-number

routing process in global configuration mode

Step Enable Enhanced IGRP on an appletalk protocol eigrp

interface in interface configuration mode

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

this task

Caution When disabling Enhanced IGRP routing with the no appletalk routing eigrp command

all interfaces enabled for only Enhanced IGRP and not also RTMP lose their AppleTalk

configuration If you want to disable Enhanced IGRP and use RTMP instead on specific interfaces

first enable RTMP on each interface using the appletalk protocol rtmp interface configuration

command Then disable Enhanced IGRP routing using the no appletalk routing eigrp command

This process ensures that you do not lose AppleTalk configurations on interfaces for which you want

to use RTMP

P2C-46 Network Protocols Configuration Guide Part Configure AppleTalk Enhanced IGRP

Configure Miscellaneous Parameters

To configure miscellaneous AppleTalk Enhanced IGRP parameters perform one or more of the tasks

in the following sections

Disable Redistribution of Routing Information

Adjust the Interval between Hello Packets and the Hold Time

Disable Split Horizon

Adjust the Active State Time for Enhanced IGRP Routes

Log Enhanced IGRP Neighbor Adjacency Changes

Configure the Percentage of Link Bandwidth Used by Enhanced IGRP

Disable Redistribution of Routing Information

By default the Cisco 105 software redistributes AppleTalk RTMP routes into AppleTalk Enhanced

IGRP and vice versa Internal Enhanced IGRP routes are always preferred over external Enhanced

IGRP routes This means that if there are two Enhanced IGRP paths to destination the path that

originated within the Enhanced IGRP autonomous system always will be preferred over the

Enhanced IGRP path that originated from outside the autonomous system regardless of the metric

Redistributed RTMP routes always are advertised in Enhanced IGRP as external

To disable route redistribution perform the following task in global configuration mode

Task Command

Disable redistribution of RTMP routes into no appletalk route-redistribution

Enhanced IGRP and Enhanced IGRP routes

into RTMP

Adjust 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

directly attached networks This information is used to discover who their neighbors are and to learn

when their neighbors become unreachable or inoperative

By default hello packets are sent every seconds The exception is 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 that 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 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 In this want to increase the hold packets neighbors case you may time

Configuring AppleTalk P2C-47 Configure AppleTalk Enhanced IGRP

Note Do not adjust the hold time without advising Cisco technical support

To change the interval between hello packets and the hold time perform the following task in

interface configuration mode

Task Command

Set the interval between hello packets and the appletalk eigrp-timers hello-interval hold-tune hold time

Disable Split Horizon

Split horizon controls the sending of AppleTalk Enhanced 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 This reduces the of hop possibility routing loops

horizon is enabled all interfaces By default split on

Split horizon prevents route information from being advertised by router out the interface that

originated the information This behavior usually optimizes communication among multiple routers

links nonbroadcast networks and particularly when are broken However with such as Frame Relay

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 perform the following task in interface configuration mode

Task Command

Disable horizon split no appletalk eigrp-splithorizon

Adjust 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 minute the Cisco lOS software logs an error and removes the route from the routing table

You can adjust this active state time limit To specify the length of time that Enhanced IGRP routes

can remain active perform the following task in global configuration mode

Task Command

Adjust the active state time limit appletalk eigrp active-time minutes disabled

Log 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 perform the following task in

global configuration mode

Task Command

Enable logging of Enhanced IGRP neighbor appletalk eigrp log-neighbor-changes

adjacency changes

P2C-48 Network Protocols Configuration Guide Part Configure AppleTalk Interenterprise Routing

configure 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-percent 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

Enhanced IGRP To configure the percentage of bandwidth that may be used by on an interface perform the following task in interface configuration mode

Task Command

Configure the percentage of bandwidth that appletalk eigrpbandwidth-percent percent

may be used 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

Configure AppeTak nterenterprise Routing

AppleTalk interenterprise routing provides support for AppleTalk internets or domains AppleTalk

interenterprise routing allows two or more AppleTalk domains to be connected through domain

router which can also be Cisco access server AppleTalk interenterprise routing allows the

from different domains and resolution of conflicting AppleTalk network numbers or cable ranges

hop-count reduction between domains

Understand AppleTalk Domains

An AppleTalk domain is group of 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

Understand Domain Routers

The domain router uses split horizon across the entire domain not just across an interface This

means that domain routers do not propagate routes learned from an interface in one domain back into

that domain Rather it propagates routes only to other domains

AppleTalk lnterenterprise Routing Features

AppleTalk interenterprise routing provides the following features

numbers resolve Network remappingAllows you to remap remote network to numbering

conflicts with network numbers on the local network segment

When enable Hop-count reductionAllows the creation of larger internetworks you hop-count domain another This allows reduction the hop count in packet is set to as it passes from one to

you to circumvent the 15-hop limit imposed by DDP and RTMP when forwarding packets

Configuring AppleTalk P2C-49 Configure AppleTalk Interenterprise Routing

Loop detectionAvoids having multiple routing table entries to the same remote network

segment domain If the domain router detects loop it displays an error message on the domain

router and shuts off domains The presence of loop implies that there is connection between

two separate domains that was not learned through any of the interfaces of the domain router

Fast switchingHas been implemented for networks that have been remapped or on which

hop-count reduction has been configured

Redundant Paths between Domains

Note that only one domain router can separate two domains That is you cannot have two or more

domain routers to create redundant paths between domains You can however establish redundant

paths between domains by connecting them through more than one interface on the domain router

that separates them Figure illustrates this configuration In this figure one domain router separates

domains and Two of the routers interfaces are in domain Ethernet interfaces and and

three are in domain Ethernet interfaces and thus providing redundant connections

between the domains Figure illustrates 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 Domain Router El Domain E4 so

Figure Improper Configuration of Domain Routers Connecting Two Domains

EQ EO Domain Router El E4 so

Domain Domain

Currently you can configure AppleTalk interenterprise routing only on routers running RTMP or Enhanced IGRP

P2C-50 Network Protocols Configuration Guide Part Configure AppleTalk Interenterprise Routing

Interenterprise Routing Task List AppleTalk You the configure AppleTalk interenterprise routing by completing tasks described in the following

sections At minimum you must enable AppleTalk interenterprise routing The remaining tasks are

optional

Enable AppleTalk Interenterprise Routing

Remap Network Numbers

Control Hop Count

After you assign AppleTalk interenterprise routing remapping hop-count reduction and features loop-detection to an AppleTalk domain you can attribute those characteristics to tunnel

interface for configured AURP by assigning the AppleTalk domain group number to the AURP tunnel interface

Enable AppleTalk Interenterprise Routing

To enable AppleTalk interenterprise routing perform the following steps

Enable Step AppleTalk interenterprise routing on the router

Enable Step AppleTalk interenterprise routing on an interface

To enable AppleTalk interenterprise routing perform the following task in global configuration mode

Task Command

Create domain and assign it name and appletalk domain domain-number name domain-name number

To enable AppleTalk interenterprise routing on an interface perform the following task in interface configuration mode

Task Command

Assign predefined domain number to an appletalk domain-group domain-number interface

For an of how example to configure AppleTalk interenterprise routing see the AppleTalk

Interenterprise Routing Example section at the end of this chapter

Remap Network Numbers

When connecting two AppleTalk networks conflict can arise between network numbers or between cables on one network and those the other ranges on You can avoid conflicts by remapping the remote networks network numbers or cable ranges

Each domain can have two mapping ranges to which to remap all incoming or outgoing network numbers or cable ranges

To the network numbers cable inbound remap or ranges on packets perform the following task in global configuration mode

Task Command

inbound the Remap packets to domain appletalk domain domain-number remap-range in cable-range

Configuring AppleTalk P2C-51 Configure AppleTalk over WANs

To remap the network numbers or cable ranges on outbound packets perform the following task in

global configuration mode

Task Command

Remap packets outbound from the domain appletalk domain domain-number remap-range out

cable-range

Control Hop Count

When you join AppleTalk network segments to create domains the distance across the combined

internetworks is likely to exceed 15 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

Reducing the hop-count value allows 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 bypass the limitation of 16 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 perform the following task in global configuration mode

Task Command

Enable hop-count reduction appletalk domain donain-n umber hop-reduction

Configure AppeTak over WANs

You can configure AppleTalk over dial-on-demand routing DDR Frame Relay SMDS and X.25

networks To do this configure the address mappings as described in the appropriate chapters for

each protocol

AppleTalk over DDR

To use AppleTalk over DDR you must define AppleTalk static routes You can configure the

following two types of static routes

Static routes that have absolute precedence that is they always override any dynamically learned

routes

Floating static routes that can be overridden by dynamically learned routes

Be careful when assigning static routes When links associated with these static routes are lost traffic

may stop being forwarded or traffic may be forwarded to nonexistent destination even though an

alternative path might be available

Note When configuring AppleTalk over DDR the zone name assigned to the interface must be

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

P2C-52 Network Protocols Configuration Guide Part Monitor and Maintain the AppleTalk Network

Configure Static Routes

To add static route for an extended or nonextended AppleTalk network peiform one of the

following tasks in global configuration mode

Task Command

Define static route on an extended AppleTalk appletalk static cable-range cable-range to

network network.node zone zone-name

Define static route on nonextended appletalk static network network-number to

AppleTalk network neiwork.node zone zone-name

Configure 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

To add floating static route for an extended or nonextended AppleTalk network perform one of the

following tasks in global configuration mode

Task Command

Define floating static route on an extended appletalk static cable-range cable-range to

AppleTalk network network.node floating zone zone-name

Define floating static route on nonextended appletalk static network network-number to

AppleTalk network network.node floating zone 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

AppleTalk over X.25

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 AppleTalk broadcast capability This is necessaly because X.25

does not support broadcasts but AppleTalk does The broadcast simulation is done as follows If

the broadcast flag is set whenever broadcast packet is sent each 121 address specified will

receive it

Monitor and Maintain the AppHeTak Network

The Cisco lOS software provides several commands that you can use to monitor and maintain an

AppleTalk network In addition you can use network monitoring packages such as Apple

Computers InterPoll 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

Configuring AppleTalk P2C-53 Monitor and Maintain the AppleTalk Network

Monitor and Maintain the AppleTalk Network Using Cisco lOS Software Commands

To monitor and maintain the AppleTalk network perform one or more of the following tasks at the EXEC prompt

Task Command

Enable recognition of pre-EDDITaIk packets appletalk pre-fdditalk

Delete entries from the AppleTalk ARP clear appletalk arp AARP table

Delete entries from the neighbor table clear appletalk neighbor all

Delete entries from the routing table clear appletalk route network

Reset AppleTalk traffic counters clear appletalk traffic

Clear the fast switching entries in the SMRP clear smrp mcache

fast switching cache table

Diagnose basic AppleTalk network ping appletalk networknode

connectivity user-level command

Diagnose basic AppleTalk network ping

connectivity privileged command

Display the AppleTalk access lists currently show appletalk access-lists defined

Display the routes to networks that are directly show appletalk adjacent-routes

connected or that are one hop away

List the entries in the AppleTalk ARP table show appletalk arp

Display pending events in the AppleTalk AURP show appletalk aurp events

update-events queue

Display entries in the AURP private path show appletalk aurp topology database

Display the contents of the AppleTalk show appletalk cache

fast switching cache

Display domain-related information show appletalk domain

List the neighbors discovered by AppleTalk show appletalk eigrp neighbors Enhanced IGRP

Display information about interfaces show appletalk eigrp interfaces

configured for Enhanced IGRP

Display the contents of the AppleTalk show appletalk eigrp topology

Enhanced IGRP topology table active zero-successors

Display information about the routers show appletalk globals

AppleTalk internetwork and other parameters

Display AppleTalk-related interface settings show appletalk interface numberj

Display the status of all known MacIP clients show appletalk macip-clients

Display the status of devices MacIP servers show appletalk macip-servers

Display statistics about MaciP traffic show appletalk macip-traffic

Display list of NBP services offered by show appletalk name-cache

nearby routers and by other devices that

support NBP

Display the contents of the NBP name show appletalk nbp

registration table

P2C-54 Network Protocols Configuration Guide Part Monitor and Maintain the AppleTalk Network

Task Command

Display information about the AppleTalk show appletalk neighbors

routers directly connected to any network to

which the router is directly connected

Display domain remapping information show appletalk remap domain-number

out from domain-n etworkljl

Display the contents of the AppleTalk routing show appletalk route type numbe

table

Display the process-level operations in all show appletalk sockets

sockets in an interface

Display the defined static routes show appletalk static

Display the statistics about AppleTalk protocol show appletalk traffic

traffic including MacIP traffic

Display the contents of the zone information show appletalk zone

table

Display the SMRP forwarding table show smrp forward

information about Display global SMRP show smrp globals

the SMRP Display group table show smrp group

the SMRP fast Display switching cache table show smrp mcache

Display the SMRP neighbor table show smrp neighbor

Display the SMRP port table show smrp port number

Display the SMRP routing table show smrp route type number

Display all entries or specific entries in the show smrp traffic group neighbor port route SMRP traffic table transaction

Enter test mode to test NBP protocols test appletalk

Monitor the AppleTalk Network Using Network Monitoring Packages

The Cisco lOS software supports network monitoring packages such as Apple Computers

which tools that InterPoll are use the AppleTalk responder and listener for verifying routers and configuration operation The software answers AppleTalk responder request packets These

request packets are received by the listener which is installed on the AppleTalk interface name socket The registration responder request packets include the bootstrap firmware version string followed the by operating software version string These strings are displayed in the Macintosh version and the System Macintosh printer driver version fields respectively and in applications such

as Apples InterPoll The response packet contains strings similar to those displayed by the show version EXEC command

The Cisco 105 software returns the following information in response to responder request packets

System bootstrap version ROM version

Software version

AppleTalk version this is always 56 which is the first Apple Macintosh version that contained AppleTalk Phase support

AppleTalk responder version his is always 100 which indicates support of Version 1.0 responder packets

AppleShare status this is reported as not installed

Configuring AppleTalk P2C-55 AppleTalk Configuration Examples

Figure illustrates typical output display for InteroPoll that lists this information

Figure Inter.PollOutput

Net 4042 Node Device routerl .Ethernet3-ciscoRouter.Twillght Zone

Packets 20 Using

Echo Pkts Donej Interval 2.5 Isecs

Printer Status Packets Timeout 1.5 Secs System Into Packets

Rcvd Lost

Packets Sent Left 16 Total

Current Average Minimum Maximum

Hops Away 3.00

Delay secs 0.02 0.02 0.02 0.02

System Bootstrap Version 445.0 1906-1991 b.. Status ls Software GSa Version 9.213110 Development Software 1991

Responder NiT Version 100 ______AppteTalk Driver VersIon 56 AppteShare not installed

AppeTak Configuraflon ExampHes

Use the following configuration examples in the following sections to help you configure AppleTalk

routing

Extended AppleTalk Network Example

Nonextended AppleTalk Network Example

Nonextended Network in Discovery Mode Example

AppleTalk Access List Examples

Transition Mode Example

AppleTalk 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

P2C-56 Network Protocols Configuration Guide Part AppleTalk Configuration Examples

Extended AppleTalk Network Example

The following example configures an extended AppleTalk network It defines the zones Accounting

and Personnel The cable range of one 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 following example configures 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

No Parking Zone

Network Network

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 following example configures nonextended network in discoveiy 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 supplies

configuration information for Ethernet interface See Figure

Configuring AppleTalk P2C-57 AppleTalk Configuration Examples

Figure Routing in Discovery Mode

Use the following commands to configure this nonextended network in discovery mode

appletalk routing

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

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

To configure transition mode you must have two ports connected to the same physical cable One

port is configured as nonextended AppleTalk network and the other is configured as an extended

AppleTalk network Both ports must have unique network numbers because they are two separate

networks Figure shows an example of the topology of this configuration

P2C-58 Network Protocols Configuration Guide Part AppleTalk Configuration Examples

Figure Transition Mode Topology and Configuration

EO El

CD ______to

Use tile following commands to configure this network Note that networks 2-2 and 4-4 must have

of and in their lists This is to maintain cable range one single zone zone required 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

AppleTalk Access List Examples

Our implementation of AppleTalk provides several methods using access lists to control access to AppleTalk networks The examples that follow illustrate these methods and show different

approaches in applying access lists

Defining an Access List to Filter Data Packets Example

The following commands create access list 601

Permit packets to be routed from network 55 accesslist 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 accesslist 601 deny includes 970990

Do not permit packets to be routed from networks 991 through 995 accesslist 601 permit within 991995

Deny routing to any network and cable range not specifically enumerated access-list 601 deny other-access

Configuring AppleTalk P2C-59 AppleTalk Configuration Examples

To use access list 601 to filter data packets you apply it an interface for example Ethernet interface

using the following commands

appletalk routing interface ethernet appletalk cable-range 50-50 appletalk zone No Parking appletalk access-group 601 out

The following examples illustrate how Ethernet interface would handle outgoing data packets

Packets sourced from cable would be range 5050 permitted

sourced from in the cable 972980 denied because Packets any network range are they explicitly

match the access-list deny includes 970-990 command

Defining an Access List to Filter Incoming Routing Table Updates Example

The following commands create access list 602 This example illustrates how packets are processed

by access lists you cannot create such redundant access list

access-list 602 permit network 55 accesslist 602 permit cable 5555 access-list 602 permit includes 55-55 accesslist 602 permit within 55-55

To use this access list to filter routing table updates received on Ethernet interface apply it to the

interface using the following commands

appletalk routing interface ethernet appletalk cable-range 55-55 appletalk zone No Parking appletalk distributelist 602 in

The tables illustrate following the process for accepting or rejecting routing update information If

of is the list and the the outcome test true condition passes the access specification distribute-list

command specification is then applied

Routing updates containing network 55 would be processed as follows

Access List Command Outcome of Test

access-list 602 permit network 55 True

access-list 602 permit cable range 55-55 False

access-list 602 permit includes 55-55 True

access-list 602 permit within 55-55 True

Routing updates containing cable range 55-55 would be processed as follows

Access List Command Outcome of Test

access-list 602 permit network 55 False

access-list 602 permit cable range 55-55 True

access-list 602 permit includes 55-55 True

access-list 602 permit within 55-55 True

P2C-60 Network Protocols Configuration Guide Part AppleTalk Configuration Examples

cable Routing updates containing range 55-56 would be processed as follows

Access List Command Outcome of Test

access-list 602 permit network 55 False

access-list 602 permit cable-range 55-55 False

access-list 602 permit includes 55-55 True

access-list 602 permit within 55-55 False

Comparison of Alternative Segmentation Solutions

With the flexibility allowed by our access list implementation determining the optimal method to

segment an AppleTalk environment using access control lists can be unclear The following scenario

and configuration examples illustrate two solutions to particular problem and point out the

inherent advantages of using AppleTalk-style access lists

Consider situation in which company wants to permit customers to have direct access to several

corporate file servers Access is to be permitted to all devices in the zones named MIS and Corporate

but access is restricted to the Engineering zone because the file servers in these zones contain

sensitive information The solution is to create the appropriate access lists to enforce these access

policies

The companys AppleTalk internetwork consists of the following networks and zones

Zone Network Number or Cable Range

Engineering 6969

41604160

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

minimal configuration might be as follows In this configuration 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

Configuring AppleTalk P2C-61 AppleTalk Configuration Examples

interface ethernet appletalk network

appletalk distributelist 603 out appletalk accessgroup 603

more comprehensive be the configuration might following in which the Corporate and MIS zones

are public and all other zones are secured

appletalk routing

accesslist 603 permit zone Corporate access-list 603 permit zone MIS access-list 603 deny additional-zones accesslist 603 permit otheraccess

interface ethernet appletalk network

appletalk distribute-list 603 out appletalk access 603

Both configurations the basic satisfy goal of isolating the Engineering servers but the second will continue example to be secure when more zones are added in the future

Defining an Access List to Filter NBP Packets Example The following example adds entries to access list number 607 to allow forwarding of NBP packets from specific sources and deny of from forwarding NBP packets all other sources The first

command adds an entry that allows NBP from all packets printers of type LaserWriter The second command adds an that allows entry NBP packets from all file AppleTalk servers of type AFPServe The third command adds an that allows from entry NBP packets all applications called HotShotPaint For example an application might have zone name of Accounting and an application have might zone name of engineering both the name of having object 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

access-list 607 permit nbp type LaserWriter access-list 607 permit nbp type AFpserver access-list 607 permit nbp object HotShotpaint access-list 607 deny other 0bps

To use this access list to filter inbound NBP packets on Ethernet interface apply it to the interface using the following commands

appletalk routing interface ethernet

appletalk cable-range 55-55 appletalk zone No Parking appletalk access-group 607 in

The following example adds 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 B1d3 access-list 608 deny obp object ServerB access-list 608 deny nbp type AFPServer access-list 608 deny nbp zone Bld3 access-list 608 permit other-obps access-list 608 permit other-access

P2C-62 Network Protocols Configuration Guide Part AppleTalk Configuration Examples

To use this access list to filter NEP packets on Ethernet interface apply it to the interface using the

following commands

appletalk routing interface ethernet appletalk cable-range 55-55 appletalk zone No Parking appletalk access-group 608 in

Note Prior to Cisco lOS Release 11.2 all NBP access lists were applied to inbound interfaces by

default Using Cisco lOS 11.2 or later software 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 lists the command NBP access using appletalk access-group

The following example creates an access list that denies forwarding of the following

All NBP Lookup Reply packets

NBP packets from the server named Bobs Server

all Packets from AppleTalk file 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

filter for There may be case where fully qualified Bobs Server.AFPServer@twilight will not

work for an NBP Lookup Reply in response to Lookup generated by the Chooser application This

is because the Lookup Request is transmitted as AFPServer@lwiiight and the Lookup Reply from

Bobs Server comes back as Bobs Server.AFPServer@

The following example creates an access list to filter Lookup Reply generated by Bobs Server to

request by the 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

Configuring Partial Zone Advertisement Example

Figure 10 illustrates configuration in which you might want to allow partial advertisement of

particular zone

Configuring AppleTalk P2C-63 AppleTalk Configuration Examples

Figure 10 Example Topology of Partially Obscured Zone

Router

E0 E4 El

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 10 nor does it 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 distributelist 612 in

For Network 30 normal default behavior would be for Network 10 and Network 20 to be eliminated from be any routing updates sent although Network 15 would included in routing updates

same zone as Network 30 Using the appletalk permit-partial-zones global configuration

command has the following effects

If permit-partial-zones is enabled appletalk permit-partial-zones the routing updates exclude Network 10 but include Network 15 and Network 20

If permit-partial-zones is disabled no appletalk permit-partial-zones the routing updates

exclude both Network 10 and Network 20 but still include Network 15 This is generally

considered the preferred behavior and is the default

Table summarizes the associations between the networks shown in Figure 10 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 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 on Advertised on Advertised on

Network 30 Network 30 Network 30

Disabled Not Advertised on Advertised on Not Advertised on Network 30 Network 30 Network 30

P2C-64 Network Protocols Configuration Guide Part AppleTalk Configuration Examples

Hiding and Sharing Resources with Access List Examples

The following examples illustrate the use of 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 Routers and to be able to access the AppleShare servers AS1 and AS2 in the zone

FreeAccessZone second is requirement to block cross access through this zone In other words

in the users zones MIS MIS2 and LocalTalk which are connected to Ethernet interface on Router not allowed are access to any of the resources on networks connected to Ethernet

interface Router on Similarly users in the zones Engineering Test and LocalTalk which are

connected to Ethernet interface on Router interface allowed E4 are not access to any of the resources on networks connected to Ethernet interface on Router

Figure 11 Controlling Access to Common AppleTalk Network

Access allowed into FreeAccessZone

Zone MIS2 Zone Engineering Network 4081 Network 20

Zone FreeAccessZone

Cable range 5-5

Zone MIS1 Router Zone LocalTalk E2 E4 Network 4083 Network 10

Zone Locallalk Zone Test Network Network AppleShare servers

in FreeAccessZone CC Co CO

Access out blocked

Note Although there are networks that share the same number on interfaces ED and E4 and there

that the are zones have same name none have the same network number and zone specification

except FreeAccessZone The two routers do not broadcast information about these networks

FreeAccessZone The routers broadcast the cable through only range 55 As configured FreeAccessZone only sees itself However since no other limitations have been placed on the advertisements FreeAccessZone range of 55 propagates out to the networks attached to E0

Router and E4 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

Configuring AppleTalk P2C-65 AppleTalk Configuration Examples

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

When configuring both routers you do not need to define any access lists to prevent users on

networks connected to Router from accessing resources on networks connected to Router and

vice versa The appletalk free-trade-zone interface configuration command implements the restrictions necessary

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 zone was completely denied There 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 zones but are denied access to other specific zones Figure 12 illustrates such situation

Figure 12 Controlling Resource Access among Multiple AppleTalk Zones

Zone MIS

Cable range 7000-7010

Admin

Zone Engineering Zone Finance Cable range 22-30

Cable range 1000-1 000

Zone FreeAccessZone2

Cable range 9-9 ______

Zone Test-lab

AppleShare servers

in FreeAccessZone

The following are the objectives of the configuration in Figure 12

Users in zones Engineering E7 and MIS EO are to be allowed free access to each other

All users in all zones are to be allowed access to FreeAccessZone2 E6

P2C-66 Network Protocols Configuration Guide Part AppleTalk Configuration Examples

No in users any zone with the exception of users in Finance are to be allowed access to resources

in Finance

To these meet specifications you define the following access lists

access-list 609 permit cable 99 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 accesslist 611 permit cable-range 70007010 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

Configuration for Ethernet Interlace

Ethernet interface is associated with the MIS zone Use the following commands to configure this interface

interface ethernet appletalk cable-range 7000-7010 appletalk zone MIS appletalk distribute-list 611 out appletalk distributelist 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 Interlace

Ethernet interface is associated with the Finance zone Use the following commands to configure this interface

interface ethernet appletalk cablerange 1000-1000 appletalk zone Finance appletalk distribute-list 610 out appletalk access-group 610

The 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

The appletalk access-group interface configuration command filters packet traffic Thus it blocks access to any devices in Finance from outside of this zone

Configuring AppleTalk P2C-67 AppleTalk Configuration Examples

Configuration for Ethernet Interlace

Ethernet interface is associated with the FreeAccessZone2 zone Use the following commands 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 Interlace

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 each others resources Use the following commands to configure Ethernet interface

interface ethernet appletalk cable-range 22-30 appletalk zone Engineering appletalk distribute-list 611 out appletalk distribute-list 611 in

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 Admin 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 examples in this section show how to configure GZL and ZIP reply filters and they illustrate the

differences between these two types of filters Both examples use the configuration shown in

Figure 13

P2C-68 Network Protocols Configuration Guide Part AppleTalk Configuration Examples

Figure 13 GZL and ZIP Reply Filters Sample Topology

Router 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

the shown in would Using configuration Figure 13 you use GZL filter to prevent the Macintosh on

the Ethernet network segment from viewing the zones Engineering and Accounting on network

600 These would be visible the zones not via Macintoshs Chooser To do this you configure

Router as follows

access-list 650 deny zone Engineering access-list 650 deny zone Accounting access-list 650 permit additionalzones access-list 650 permit other-access

interface ethernet appletalk getzonelist-filter 650

Again using the configuration shown in Figure 13 you would use ZIP reply filter to hide the

Engineering and Accounting zones from Routers and 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 650 deny zone Engineering access-list 650 deny zone Accounting access-list 650 permit additional-zones access-list 650 permit other-access

interface ethernet appletalk zip-reply-filter 650

AppleTalk Interenterprise Routing over AURP Example

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

Configuring AppleTalk P2C-69 AppleTalk Configuration Examples

The following example defines tunnel interface and configures it for AURP Then it applies the features for domain tunnel interface configured to 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 131.108.1.17 tunnel mode aurp appletalk protocol aurp appletalk domain-group

SNMP Example

The following example configuration sequence illustrates proper activation of 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 SNMP 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 illustrates MacIP support for dynamically addressed MacIP clients with

dynamically allocatedlP addresses in the range 131108.0.2 to 131.108.0.10

Specify server address and zone appletalk macip server 131.108.0.1 zone Marketing

Specify dynamically addressed clients appletalk nacip dynamic 131.108.0.2 131.108.0.10 zone Marketing

lAssign the address and subnet mask for Ethernet interface interface ethernet ipaddress 131.108.0.2 255.255.255.0

Enable AppleTalk routing appletalk routing

interface ethernet

appletalk cable range 69-69 69.128 appletalk zone Marketing

P2C-70 Network Protocols Configuration Guide Part AppleTalk Configuration Examples

The following example illustrates MacIP support for MacIP clients with statically allocated IP addresses

Specify the server address and zone appletalk macip server 131.10801 zone Marketing

Specify statically addressed clients appletalk macip static 131.108.0.11 131.108.0.20 zone Marketing appletalk macip static 131.108.0.31 zone Marketing appletalk macip static 131.108.0.41 zone Marketing appletalk macip static 131.108.0.49 zone Marketing

Assign the address and subnet mask for Ethernet interface interface ethernet ipaddress 131.108.0.1 255.255.255.0

Enable AppleTalk routing appletalk routing

interface ethernet appletalk cable range 69-69 69.128 appletalk zone Marketing

IPTaIk Example

This section describes how to set up UNIX-based systems and our Cisco lOS software to use CAP

IPTalk and other IPTalk implementations

The following procedure outlines the basic steps for setting up our software and UNIX hosts for

operation using IPTalk implementations

Note This procedure does not provide full instructions about how to install CAP on the UNIX

it does address the the system However requirements for setting up UNIX systems configuration

file that defines addresses and other network information Generally this is the only file that relies the routers on address and configuration information Refer to your UNIX systemand CAP software

manuals for information about building the CAP softwaie and setting up the UNIX startup scripts

Step Enable AppleTalk routing on all the routers that will use IPTalk and any routers between these routers

Step Enable IP routing on the interfaces that will communicate with the UNIX system Refer

to the Network Pmtocols Configuration Guide Part for more information about

configuring IP These interfaces must be on the same subnet as the UNIX system Also

ensure that IP is enabled on the UNIX system

Step Allocate an AppleTalk network number for IPTalk You need separate AppleTalk

network number for 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 network number for IPTalk However they must have their own individual

node identifiers

It is possible for the same router to have IPTa1k enabled on several interfaces Each

interface must have different AppleTalk network number allocated to IPTalk because

each interface will be using different IP subnet

Configuring AppleTalk P2C-71 AppleTalk Configuration Examples

Step Determine the CAP forthat of the AppleTalk network number The CAP software is based

on an older AppleTalk convention 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 256

Example AppleTalk format 14087 CAP format 557

Step Choose zone name for IPTalk 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

Step Decide which UDP ports to use for IPTalk The default is to use ports beginning with 768

Thus RTMP uses port 769 NBP port 770 and so on These are the original AppleTalk

ports and their numbers are hardcoded into older versions of CAP The only problem with

using them is that they are not officially assigned by the Internets Network Information

Center NIC which has assigned set of UDP ports beginning with 200 Thus other

applications could use them possibly causing conflictsalthough this is unlikely With

CAP releases 5.0 and later you can configure CAP to use the officially allocated ports If

you do so RTMP will use port 201 NBP port 202 and so on Whichever ports you use you must configure both CAP and the router to use the same ones

Step Enable IPTalk on each interface of the router as required This is illustrated by the following example

appletalk routing

interface ethernet ipaddress 128.6.7.22 255.255.255.0 appletalk cable 17921792 1792.22 appletalk zone MIS-Development interface TunnelO tunnel source EthernetO tunnel node iptalk appletalk iptalk 14087 MIS-UNIX

In this example AppleTalk routing is enabled on the interface in the following two ways

Via EtherTalk the cable 17921792 and the phase using range zone MIS -Development

Via IPTalk using the network number 14087 and the zone MIS-UNIX

P2C-72 Network Protocols Configuration Guide Part AppleTalk Configuration Examples

Note The IPTalk 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 128.6.722 and subnet of the host mask 255.255.255.0 number is 22 Thus the IPTaIk node identifier would be 22 If the

IP host number is than the larger 255 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 truncated Be quietly sure to use node address that is compatible with the subnet mask In any event

you may experience problems when using IPTalk with host numbers larger than 255

If choose you 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

As an example the following are the contents of the /etc/ataik local file from UNIX

system with the IP address 128.6.7.26 and network mask of 255.255.255.0

IPTalk on net 128.6.7.0

mynet mynode inyzone 55.7 26 MIS-UNIX bridgenet bridgenode bridgelP 55.7 22 128.6.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 column is

55.7 which is the AppleTalk network number in CAP format for use by IPTalk The

is the second column AppleTalk node identifier which must be the same as the IP host

number The third column 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 network number in the first column in both lines AppleTalk 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 host number in the second column in both lines must agree with the IP host

number of the corresponding system That is on the first line it must be the IP host

number of the UNIX machine and on the second line it must be the IP host number

for the router

The in the third column zone name on the first line must agree with the zone name

used in the appletalk iptalk command

The IP address in the third column of the second line must be the IP address of the

router

Ensure that Step your CAP software is using the same UDP port numbers as the router the Currently CAP default is the same as the router default which is port numbers

with 768 If want to this do not need take beginning you use default you to any further action if However you want to use the official UDP port numbers port numbers

with ensure that have included the command in beginning 200 you following your configuration

appletalk iptalk-baseport 200

Configuring AppleTalk P2C-73 AppleTalk Configuration Examples

Step 10 On the UNIX system add the following lines to the /etc/services file

atrtmp 201/udp at-nbp 202/udp at3 203/udp at-echo 204/udp at5 205/udp atzis 206/udp at7 207/udp at8 208/udp

If you are using Network Information Services NIS previously known as the Yellow Pages remember to do make in /var/yp after changing let c/services If you are using the need default ports those starting with 768 you do not to modify /etc/services

AppleTalk Control Protocol Example

The following example illustrates how to set up router to accept AppleTalk client requests on interface This example creates 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 your network topology looks like the one in Figure 14 Also assume that Router

supports only nonextended AppleTalk that Router supports only extended AppleTalk not in

transition mode and that Router supports only extended AppleTalk

Figure 14 Example Network Topology

Router Router Router

Cable/Range Cable/Range ______Cable/Range ____ Network 60 Cisco Phase Cisco Phase AppleTalk Zone Router Router Phase Router

Cisco Phase Router Router Router

Co Cable/Range Co 100-1 00

If Router generates an NBP hookup request for Zone Router will convert this request to

forward request and send it to Router Since Router supports only nonextended AppleTalk it

does not handle the forward request andignores 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

P2C-74 Network Protocols Configuration Guide Part AppleTalk Configuration Examples

If Router with you configured 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

to properly respond NBP hookup requests generated beyond Router The following example

demonstrates 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 this example Enhanced IGRP process is configured to use maximum of 25 percent or 32 kbps of 128 kbps circuit

interface serial bandwidth 128 appletalk eigrp-bandwidth-percent 25

In the following example the bandwidth of 56 kbps circuit has been configured to be 20 kbps for

routing policy reasons EIGRP process is configured to use maximum of 200 percent or 40kbps of the circuit

interface serial bandwidth 20

appletalk eigrp-bandwidth-percent 200

AppleTalk Interenterprise Routing Example

The following example configures 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 15 When Figure 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 the route Otherwise 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

Configuring AppleTalk P2C-75 AppleTalk Configuration Examples

Figure 15 AppleTalk over DDR Configuration

Appleshare

Cable Range 1-1 Cable Range 100-110

To configure AppleTalk over DDR perform the following tasks on Router

Step Configure an access list and dialer group

accesslist 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 distributelist 601 in

Step Create the static route

appletalk static cable 100-110 to 1.2 zone Remote

Step Open the Chooser on the Macintosh

Step Select any AppleTalk service such as AppleShare LaserWriter and so on in zone Remote This causes Router to dial up Router to open DDR link between them

Step Select 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

Step After the AppleTalk session is finished close the connection to the remote service The link DDR should go down after the DDR idle time has elapsed

Instead of creating static route in Step you can create floating static route The following adds example floating static route to cable-range 10-il 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

AppleTalk Control Protocol for PPP Example

The illustrates the to following example steps required 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

P2C-76 Network Protocols Configuration Guide Part AppleTalk Configuration Examples

Routerconfigint interface async Router configint encapsulation ppp Router config-int appletalk client-mode

Configuring AppleTalk P2C-77 AppleTalk Configuration Examples

P2C-78 Network Protocols Configuration Guide Part Configuring NoveU OPX

This chapter describes how to configure Novell Internet Packet Exchange IPX and provides

configuration examples For complete description of the IPX commands in this chapter refer to the

Novell IPX Commands chapter in the Network Protocols Command Reference Part To locate

documentation of other commands that in this appear chapter use the command reference master index or search online

IPX Addresses

address consists An IPX network of network number and node number expressed in the format network.node

Network Numbers

The network number identifies physical network It is 4-byte 32-bit quantity that must be unique

throughout the entire IPX internetwork The network number is expressed as hexadecimal digits

The maximum number of digits allowed is eight

The Cisco lOS software does not require that you enter all eight digits you can omit leading zeros

Node Numbers

The node number identifies node on the network It is 48-bit quantity represented by dotted

triplets of four-digit hexadecimal numbers

If you do not specify node number for router to be used on WAN links the Cisco lOS software the hardware Media Access Control uses MAC address currently assigned to it as its node address

This is the MAC address of the first Ethernet Token Ring or FDDI interface card If there are no valid IEEE then the Cisco interfaces lOS software randomly assigns node number using number that is based on the system clock

IPX Address Example

The following is an example of an IPX network address

4a 0000 0c00 23fe

In this example the network number is 4a more specifically it is 0000004a and the node number

is 0000.OcOO.23fe All digits in the address are hexadecimal

Configuring Novell IPX P2C-79 IPX Configuration Task List

PX Configuration Task List

To IPX configure routing complete the tasks in the following sections At minimum you must enable IPX routing The remaining tasks are optional

Enable IPX Routing

Configure IPX Enhanced IGRP

Configure NLSP

Configure Next Hop Resolution Protocol

Configure IPX and SPX over WANs

Control Access to IPX Networks

Tune IPX Network Performance

Shut Down an IPX Network

Configure IPX Accounting

Monitor and Maintain the IPX Network

See the Novell IPX Configuration Examples section at the end of this chapter for configuration examples

Enabe PX Routing

You enable IPX routing by first enabling it on the router and then configuring it on each interface

Optionally you can route IPX on some interfaces and transparently bridge it on other interfaces You also IPX traffic can route between routed interfaces and bridge groups or route IPX traffic between bridge groups

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

RIP allowed the of network Original implementations use -2 OxFFFFFFFE as regular network number in network With the inception of 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 should network -2 the default you implement as route regardless of whether you configure NLSP in

your IPX network

By default Cisco lOS software treats network -2 as the default route You should that ensure your IPX network does not use network -2 as regular network If for some reason you must use network -2 as regular network you can disable the default behavior To do so see the Adjust

Default Routes section in this chapter

For more background information on how to handle IPX default routes refer to Novells NetWare

Link Services Protocol NLSP Specification Revision 1.1

P2C-80 Network Protocols Configuration Guide Part Enable IPX Routing

Enable IPX Routing Task List

Complete the tasks in the sections to enable IPX following routing The first two tasks are required the rest are optional

Enable IPX Routing

Assign Network Numbers to Individual Interfaces

Enable Concurrent Routing and Bridging

Configure Integrated Routing and Bridging

Enable IPX Routing

The first in IPX is step enabling routing to enable it on the router If you do not specify the node number of the router to be used on WAN links the Cisco lOS software uses the hardware Media Access Control address MAC currently assigned to it as its node address This is the MAC address

of the first Token Ethernet Ring or FDDI interface card If there are no valid IEEE interfaces then the Cisco lOS software node number number randomly assigns using that is based on the system clock

To enable IPX routing perform the following global configuration task

Task Command

Enable IPX routing ipx routing

For an of how to enable IPX the example routing see IPX Routing Examples section at the end of this chapter

Caution If to use DECnet and you plan IPX routing concurrently on the same interface you should enable DECnet then enable routing first IPX routing without specifying the optional MAC node number If enable IPX before you enabling DECnet routing routing for IPX will be disrupted because DECnet forces change in the MAC-level node number

Assign Network Numbers to Individual Interfaces

After have enabled IPX you routing you assign network numbers to individual interlaces This enables IPX routing on those interfaces

You enable IPX routing on interfaces that network those support single or on that support multiple networks

When enable IPX on an also you routing interface you can specify an encapsulation frame type to for use packets being transmitted on that network Table lists the encapsulation types you can use on IEEE interfaces and shows the correspondence between Cisco naming conventions and Novell

conventions for the naming encapsulation types

Configuring Novell IPX P2C-81 Enable IPX Routing

Table Cisco and Novell IPX Encapsulation Names on IEEE Interfaces

Interface Type Cisco Name Novell Name

Ethernet novell-ether Cisco lOS default Ethernet_8023

arpa Ethernet_TI

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_8022

novell-fddi Fddi_Raw

Assign Network Numbers to lndviduaI Interfaces Task List

The sections describe enable following how to IPX routing on interfaces that support single

network and on those that support multiple networks You must perform one of the tasks to enable

IPX routing on an interface in these sections

Assign Network Numbers to Interfaces That Support Single Network

Assign Network Numbers to Interfaces That Support Multiple Networks

Assign Network Numbers to Interlaces That Support Single Network

interface single can support single network or multiple logical networks For single network

you can configure any encapsulation type Of course it should match the encapsulation type of the

servers and clients using that network number

To assign network number to an interface that supports single network perform the following

interface configuration task

Task Command

Enable IPX routing on an interface ipx network network

encapsulation-type

If you specify an encapsulation type be sure to choose the one that matches the one used by the

and clients that network Refer servers on to Table for list of encapsulation types you can use on IEEE interfaces

For an example of how to enable IPX routing see the IPX Routing Examples section at the end of

this chapter

Assign Network Numbers to Interlaces That Support Multiple Networks When assigning network numbers to an interface that supports multiple networks you must specify

different encapsulation type for each network Because multiple networks share the physical

this medium allows the Cisco lOS software 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 supported for Ethernet Again the encapsulation type should match the

servers and clients using the same network number Refer to Table for list of encapsulation types

you can use on IEEE interfaces

There are two ways to assign network numbers to interfaces that support multiple networks You can

use subinterfaces or primary and secondary networks

P2C-82 Network Protocols Configuration Guide Part Enable IPX Routing

Subintertaces

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 perform the following tasks starting in global configuration mode

Task Command

Step Specify subinterface interface type numbensubinteiface-number

Step Enable IPX routing specifying the ipx network network

first encapsulation type encapsulation-type

To configure more than one subinterface repeat these two steps Refer to 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

When assigning network numbers to interfaces that support multiple networks you can also

configure primary and secondary networks

Note In future Cisco lOS software releases primary and secondary networks will not be supported

interface is considered the network The first logical network you configure on an primary Any

additional networks are considered secondary networks Again each network on an interface must

use distinct encapsulation and it should match that of the clients and servers using the same network number

Any interface configuration parameters that you specify on this interface are applied to all the logical

networks For example if you set the routing update timer to 120 seconds this value is used on all four networks

Configuring Novell IPX P2C-83 Configure IPX Enhanced IGRP

To use primary and secondary networks to configure multiple IPX networks on an interface perform

the following tasks in interface configuration mode

Task Command

Step Enable IPX routing on the primary ipx network network

network encapsulation-type

Step Enable IPX routing on secondary ipx network network

network encapsulation-type

To than configure more one secondary network repeat Step as appropriate Refer to Table for

list of encapsulation types you can use on IEEE interfaces

Note When and enabling NLSP configuring multiple encapsulations on the same physical LAN

interface you must use subinterfaces You cannot use secondary networks

Enable Concurrent Routing and Bridging

You route IPX can on some interfaces and transparently bridge it on other interfaces simultaneously To do enable this you must concurrent routing and bridging To enable concurrent routing and

bridging perform the following task in global configuration mode

Task Command

Enable concurrent routing and bridging bridge crb

Configure 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 the interfaces in the bridged among bridged 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 within the packets same bridge group

For more information about configuring integrated routing and bridging refer to the Configuring

Transparent Bridging chapter in the Bridging and IBM Networking Configuration Guide

Configure PX Enhanced UGRP

Enhanced IGRP is enhanced version an of the Interior Gateway Routing Protocol IGRP developed Cisco Inc Enhanced IGRP by Systems uses the same distance vector algorithm and distance information IGRP the as However convergence properties and the operating efficiency of Enhanced

IGRP have improved significantly over IGRP

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 operation at every instant throughout route computation and allows all routers involved

P2C-84 Network Protocols Configuration Guide Part Configure IPX Enhanced IGRP

in topology change to synchronize at the same time Routers that are not affected by topology

involved in The time changes are not recomputations convergence 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 instead of sending the entire contents of the routing table This feature minimizes the

bandwidth required for Enhanced IGRP packets

Less CPU usage than IGRPThis occurs because full update packets do not have to be processed

each time they are received

Neighbor discovery mechanismThis 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 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/recoveiy 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 Neighbor discovery/recovery is achieved 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

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 transmitted reliably and others need not be For efficiency

is when reliability provided only necessary For example on multiaccess network that has

multicast it is hellos capabilities such as Ethernet not necessary to send reliably to ll neighbors

individually Therefore Enhanced IGRP sends single multicast hello with an indication in the

the receivers that the packet informing packet need not be acknowledged Other types of packets

such as updates require acknowledgment and this is indicated in the packet The reliable transport

has provision to send multicast packets quickly when there are unacknowledged packets pending

that Doing so helps ensure convergence time remains low in the presence of varying speed links

Configuring Novell IPX P2C-85 Configure IPX Enhanced IGRP

DUAL Finite-State Machine

The DUAL finite-state machine embodies all the decision process for 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 is successors successor neighboring router used for packet forwarding that has

least-cost to destination that is path guaranteed not to be part of routing loop When there are no

feasible but there successors are neighbors advertising the destination recomputation must occur

This is the successor is determined The of time process whereby new amount it takes to recompute the route affects the convergence time Recomputation is processor-intensive It is advantageous to

avoid if it is recomputation not necessary When topology change occurs DUAL will test for

feasible If there successors are feasible successors it 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 routing decisions but the results are stored in the IPX

table Enhanced IGRP is for routing Also responsible redistributing routes learned by other IPX routing protocols

Configure IPX Enhanced IGRP Task List

To enable IPX Enhanced the tasks in the IGRP complete following sections Only the first task is the required remaining tasks are optional

Enable IPX Enhanced IGRP

Customize Link Characteristics

Customize the Exchange of Routing and Service Information

Query the Backup Server

Enable IPX Enhanced IGRP

To create an IPX Enhanced IGRP routing process perform the following tasks

Task Command

Step Enable an Enhanced IGRP router routing ipx eigrp autonoinous-systeni-numbe

process in global configuration mode

Step Enable Enhanced IGRP on network network network-number all

in IPX router configuration mode

To associate networks with an Enhanced IGRP multiple routing process you can repeat Step

For an of how example to enable Enhanced IGRP see the IPX Enhanced IGRP Example section at the end of this chapter

P2C-86 Network Protocols Configuration Guide Part Configure IPX Enhanced IGRP

Customize Link Characteristics

You might want to customize the Enhanced IGRP link characteristics The following sections describe these customization tasks

Configure the Percentage of Link Bandwidth Used by Enhanced IGRP

Configure Maximum Hop Count

Adjust the Interval between Hello Packets and the Hold Time

Configure the Percentage of Link Bandwidth Used by Enhanced GRP Enhanced IGRP By default packets consume maximum of 50 percent of the link bandwidth as with the configured bandwidth interface subcommand If different value is desired use the ipx bandwidth-percent 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

To configure the percentage of bandwidth that may be used by Enhanced IGRP on an interface

perform the following task in interface configuration mode

Task Command

Configure the percentage of bandwidth that ipx bandwidth-percent eigrp as-number percent

may be used by Enhanced IGRP on an

interface

For an example of how to configure the percentage of Enhanced IGRP bandwidth see the IPX

Enhanced IGRP Bandwidth Configuration Example section at the end of this chapter

Configure Maximum Hop Count

Note While adjusting the maximum hop count is possible it is not recommended for Enhanced IGRP Cisco recommends that you use the default value for the maximum hop count of Enhanced IGRP

By default IPX packets whose hop count exceeds 15 are discarded In larger internetworks this may be insufficient You can increase the hop count to maximum of 254 hops for Enhanced IGRP To

modify the maximum hop count perform the following task in global configuration mode

Task Command

Set the maximum hop count accepted from RIP ipx maximum-hops hop

update packets

Adjust 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

directly attached networks Routers use this information to discover who their neighbors are and to

discover when their neighbors become unreachable or inoperative

Configuring Novell IPX P2C-87 Configure IPX Enhanced IGRP

hello By default packets are sent evejy seconds The exception is on low-speed nonbroadcast multiaccess where the default NBMA media 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 pulposes 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

configured to use physical multicasting otherwise they are considered not to be NBMA

You can configure the hold time on specified interface for particular Enhanced IGRP routing the autonomous process designated by 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 times the hello interval or 15 seconds

To the interval between hello change packets perform the following task in interface configuration mode

Task Command

Set the interval between hello packets ipx hello-interval eigrp autonomous-system-number seconds

On and 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

do this perform the following task in interface configuration mode

Task Command

Set the hold time ipx hold-time eigrp autonomous-system-number seconds

Note Do not the hold time adjust without consulting with Cisco technical support

Customize the Exchange of Routing and Service Information

You customize the might want to exchange of routing and service information The following sections describe these customization tasks

Redistribute Routing Information

Disable Split Horizon

Control the Advertising of Routes in Routing Updates

Control the Processing of Routing Updates

Control SAP Updates

Control the Advertising of Services in SAP Updates

Control the Processing of SAP Updates

P2C-88 Network Protocols Configuration Guide Part Configure IPX Enhanced IGRP

Information Redistribute Routing

default the Cisco lOS software By redistributes IPX RIP routes into Enhanced IGRP and vice versa

To disable route redistribution perform the following task in IPX router configuration mode

Task Command

Disable redistribution of RIP routes into no redistribute rip eigrp autonomous-systent-nwnber Enhanced IGRP and Enhanced IGRP routes connected static into RIP

The Cisco lOS software does not automatically redistribute NLSP routes into Enhanced IGRP routes

and vice versa You must this of configure type redistribution To do so perform the following tasks beginning in global configuration mode

Task Command

From Step global configuration mode ipx router eigrp autonomous-system-number enable Enhanced IGRP

From IPX-router Step configuration mode redistribute nlsp

enable redistribution of NLSP into Enhanced IGRP

Enable NLSP Step ipx router nlsp

Step From IPX-router configuration mode redistribute eigrp autonomous-system-number enable redistribution of Enhanced

IGRP into NILSP

For an of how to enable example redistribution of Enhanced IGRP and NLSP see the Enhanced

IGRP and NLSP Route Redistribution section the Example at end of this chapter

Disable Split Horizon

Split horizon controls the of Enhanced sending IGRP update and query packets If split horizon is enabled on an interface these packets are not sent for destinations if this interface is the next hop to that destination

By default split horizon is enabled on all interfaces

horizon blocks Split information about routes from being advertised by the Cisco lOS software out

interface from which that information any originated This behavior usually optimizes communication among multiple routers particularly when links are broken However with nonbroadcast networks Frame such as Relay and SMDS situations can arise for which this behavior is less than ideal For these situations you can disable split horizon

To disable the split horizon perform following task in interface configuration mode

Task Command

Disable horizon split no ipx split-horizon eigrp autonomous-system-n umber

Note horizon be Split cannot disabled for RIP or SAP only for Enhanced IGRP

Configuring Novell IPX P2C-89 Configure IPX Enhanced IGRP

Control 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 do this perform the following task in router configuration mode

Task Command

Control the advertising of routes in routing distribute-list access-list-number out

updates routing-p rocessl

Control the Processing of Routing Updates

To control the processing of routes listed in incoming updates perform the following task in router

configuration mode

Task Command

Control which incoming route updates are distribute-list access-list-number in

processed

Control SAP Updates

If IPX Enhanced IGRP found peers are 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 is the peer present on interface periodic SAPs are always sent

On serial if Enhanced lines by default an IGRP neighbor is present the Cisco lOS software sends SAP when the SAP updates only table changes On Ethemet Token Ring and FDDI interfaces by the software sends SAP default 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 Do this only when all nodes out 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 and to send only the SAP changes

perform the following task in interface configuration mode

Task Command

Send SAP when in the updates only change ipx sap-incremental eigrp autonomous-system-number SAP table occurs and send only the SAP rsup-only changes

When you enable incremental SAP using the ipx sap-incremental eigrp rsup-only command Cisco 105 software disables the exchange of route information via Enhanced IGRP for that interface

To send periodic SAP updates perform the following task in interface configuration mode

Task Command

Send SAP updates periodically no ipx sap-incremental eigrp

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

P2C-90 Network Protocols Configuration Guide Part Configure NLSP

Control 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 do this perform the following task in router configuration mode

Task Command

Control the advertising of services in SAP distribute-sap-list access-list-number out

updates Unteiface-nane routing-process

For configuration example of controlling the advertisement of SAP updates see the Advertisement and Processing of SAP Update Examples section at the end of this chapter

Control the Processing of SAP Updates

To control the processing of routes listed in incoming updates perform the following task in router

configuration mode

Task Command

Control which incoming SAP updates are distribute-sap-list access-list-number 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

Query the Backup Server

The table is backup server table kept for each Enhanced IGRP peer It lists the IPX servers that have been advertised by that peer If server is removed from the main server table at any time and for the Cisco any reason lOS software examines the backup server table to see if this just-removed

server is known by any of the Enhanced IGRP peers If it is the information from that peer is advertised back into the main server table 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 do not need to be sent

By default the Cisco 105 software queries its own copy of each Enhanced IGRP neighbors backup

server table every 60 seconds To change this interval perform the following task in global

configuration mode

Task Command

Specify the minimum period of time between ipx backup-server-query-interval interval

successive queries of neighbors backup

server table

Configure NLSP

The NetWare Link Services Protocol 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

Configuring Novell IPX P2C-91 Configure NLSP

Understand Level 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 Level router within its own area likewise Level router also acts as Level router within

its own domain

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

Understand NLSP Databases

NLSP is link-state protocol This means that every router in routing area maintains an identical

copy of the link-state database which contains all information about the topology of the area All

routers synchronize their views of the databases among themselves to keep their copies of the

link-state databases consistent NLSP has the following three major databases

AdjacencyKeeps track of the routers immediate neighbors and the operational status of the

directly attached links by exchanging hello packets Adjacencies are created upon receipt of link time and deleted from periodic hello packets If or router goes down adjacencies out are the database

Link stateTracks the connectivity of an entire routing area by aggregating the immediate

contain lists of neighborhood information from all routers into link-state packets LSP5 LSPs

adjacencies They are flooded to all other devices via reliable flooding algorithm every time

link state changes LSPs are refreshed every two hours To keep the size of the link-state database

reasonable NLSP uses fictitious pseudonodes which represent the LAN as whole and

designated routers which originate LSPs on behalf of the pseudonode

ForwardingCalculated from the adjacency and link state databases using Dijkstras shortest

path first SPF algorithm

Cisco Support of NLSP

Ciscos implementation of NILSP supports the Novell NLSP specification version 1.1 Our

implementation of NLSP also includes read-only NLSP MIB variables

Configure NLSP 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

Define an Internal Network

Enable NLSP Routing

Configure NLSP on an Interface

P2C-92 Network Protocols Configuration Guide Part Configure NLSP

You can optionally perform the tasks described in the following sections

Customize Link Characteristics

Configure Route Aggregation

Customize the Exchange of Routing Information

For of the an example enabling NLSP see IPX Routing Protocols Examples section at the end of

this chapter

Define an Internal Network

An internal network number is an IPX network number assigned to the router For NLSP to operate

you must configure an internal network number for each device

To enable IPX routing and to define an internal network number perform the following tasks in

global configuration mode

Task Command

Enable IPX routing ipx routing

Define an internal network number ipx internal-network network-number

Enable NLSP Routing

To enable NLSP perform the following tasks starting in global configuration mode

Task Command

Step Enable NLSP ipx router nlsp

Step Define set of network numbers to be area-address address mask

part of the current NLSP area

Configure NLSP on an Interface

You configure NILSP differently on LAN and WAN interfaces as described in the following sections

Configure NLSP on LAN interface

Configure NLSP on WAN interface

Configure NLSP on LAN Interface

To configure NLSP on LAN interface perform the following tasks in interface configuration mode

Task Command

Step Enable IPX routing on an interface ipx network network

encapsulation-type

Step Enable NLSP on the interface ipx nlsp enable

Configuring Novell IPX P2C-93 Configure NLSP

To the configure multiple encapsulations on same physical LAN interfaces you must configure

subinterfaces Each subinterface must have different encapsulation type To do this perform the

following tasks starting in global configuration mode

Task Command

subinterface Step Specify interface type number.subinteiface-number

Step Enable IPX routing specifying the ipx network network

first encapsulation type encapsulation-type

Step Enable NLSP on the subinterface ipx nlsp enable

Repeat these three steps for each subinterface

Note When NLSP and enabling configuring multiple encapsulations on the same physical LAN must interface you use subinterfaces You cannot use secondary networks

Configure NLSP on WAN Interface

To NLSP on WAN the tasks configure interface perform following starting in global configuration mode

Task Command

Step Specify serial interface interface serial number

Enable IPXWAN Step ipx ipxwan unnumbered local-server-name

retiyinferval retiy-litn it

Enable NLSP the Step on interface ipx nlsp enable

Customize Link Characteristics

You want to customize the link might NLSP characteristics The following sections describe these customization tasks

Enable NLSP Multicast Addressing

Configure the Metric Value

Configure the Link Delay and Throughput

Configure the Maximum Hop Count

Specify Designated Router

Configure Transmission and Retransmission Intervals

Modify Link-State Packet Parameters

Limit Partial Route Calculations

Enable NLSP Multicast Addressing

Cisco lOS the of supports use NLSP multicast addressing for Ethernet Token Ring and FDDI router

interfaces This is capability only possible when the underlying Cisco hardware device or driver

supports multicast addressing

P2C-94 Network Protocols Configuration Guide Part Configure NLSP

With this feature the router defaults to using multicasts on Ethernet Token Ring and FDDI instead of interfaces 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 Release 11.3 or later software When

routers running prior versions of Cisco lOS software are present on the same network with routers

Cisco lOS Release 11.3 broadcasts will be used running software on any segment shared by the two routers

Benefits of NLSP Multicast Addressing 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 Ciscos level of compliance with the Novell NLSP specification version 1.1

Enable NLSP Multicast Addressing Task List

The sections describe following configuration tasks associated with the NLSP multicast addressing

Enable NLSP Multicast Addressing

Disable NLSP Multicast Addressing

Enable NLSP Multicast Addressing

multicast By default NLSP addressing is enabled You do not need to configure anything to turn on

NLSP multicasting

Disable NLSP Multicast Addressing 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 want to disable multicast in example you might NLSP addressing favor of broadcast addressing when one or more devices on segment do not support NLSP multicast addressing You might also want to disable it for testing purposes

If want to disable multicast do for the you NLSP addressing you can so entire router or for particular interface

To disable multicast for the entire the addressing router perform following steps in IPX-router configuration mode

Task Command

Step Enter NLSP router configuration ipx router nlsp mode

Step Disable NLSP multicast addressing on no multicast

the router

Configuring Novell IPX P2C-95 Configure NLSP

To disable multicast addressing on particular router interface perform the following task in interface configuration mode

Task Command

Disable multicast addressing on the interface no ipx nlsp multicast

For of how disable examples to NLSP multicast addressing see the NLSP Multicast Addressing

Examples section at the end of this chapter

Configure the Metric Value

NLSP default link assigns cost metric based on the link throughput If desired you can set the link cost manually

Typically you do not need to 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 link cost for the NLSP an interface perform following task in interface configuration mode

Task Command

Set the metric value for an interface ipx nlsp metric metric-n umber

Configure the Link Delay and Throughput

The and of each link delay throughput are used by NLSP as part of its route calculations By default

these set to parameters are appropriate values or in the case of IPXWAN are dynamically measured

do not need the Typically you to change link delay and throughput however there are some cases

where want to these For in redundant you might change parameters example highly networks you want to favor might one route over another for certain kinds of traffic To do this you would change the metric the less-desirable on path to be slightly worse by assigning it higher metric value using the ipx-link-delay command This forces the traffic 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

when it by IPXWAN starts The value is also supplied to NLSP for use in metric calculations

To the link change delay perform the following task in interface configuration mode

Task Command

Specify the link delay ipx link-delay microseconds

To the change throughput perform the following task in interface configuration mode

Task Command

Specify the throughput ipx throughput bits-per-second

P2C-96 Network Protocols Configuration Guide Part Configure NLSP

configure the Maximum Hop Count

By default IPX whose count exceeds 15 packets hop are discarded In larger internetworks this may be insufficient You can increase the hop count to maximum of 127 hops for NLSP

For example if have network with end nodes than 15 you separated by more hops you can set the maximum hop count to value between 16 and 127

To the maximum the modify hop count perform following task in global configuration mode

Task Command

Set the maximum hop count accepted from RIP ipx maximum-hops hop update packets

Specify Designated Router

Note In the context of this the discussion term designated router can refer to an access server or router

NLSP elects designated router on each interface The LAN designated router represents all routers that are connected to the same LAN segment It creates virtual router called pseudonode which

generates routing information on behalf of the and transmits it LAN to the remainder of the routing area The information routing generated includes adjacencies and RIP routes The use of router designated significantly reduces the number of entries in the LSP database

By default router is done electing designated automatically However you can manually affect the

identity of the router the the designated by changing priority of system the system with the highest priority is elected to be the designated router

By default the of the is 44 To priority system change it perform the following task in interface configuration mode

Task Command

the Configure designated router election ipx nlsp priority priority-number

priority

Configure Transmission and Retransmission Intervals

You can configure the hello transmission interval and time holding multiplier the complete sequence number PDU transmission CSNP interval the LSP transmission interval and the LSP retransmission interval

The hello transmission interval and time used holding multiplier together determine how long

neighboring should wait after link or failure system system the holding time before declaring this system to be unreachable The time is to the hello holding equal transmission interval multiplied the by holding time multiplier

To configure the hello transmission interval on an interface perform the following task in interface configuration mode

Task Command

the hello Configure transmission interval ipx nlsp hello-interval seconds

Configuring Novell IPX P2C-97 Configure NLSP

To specify the holding time multiplier used on an interface perform the following task in interface

configuration mode

Task Command

Configure the hello multiplier ipx nlsp hello-multiplier multiplier

Although not typically necessary you can configure the CSNP transmission interval To do so

perform the following task in interface configuration mode

Task Command

Configure the CSNP transmission interval ipx nisp csnp-interval seconds

You can specify how fast LSPs can be flooded out an interface by configuring the LSP transmission

interval To configure the LSP transmission interval perform the following task in interlace

configuration mode

Task Command

Configure the LSP transmission interval ipx nlsp lsp-interval interval

You the maximum of time that before LSP will be retransmitted can set amount can pass an on

WAN link when no acknowledgment is received To configure this LSP retransmission interval

perform the following task in interface configuration mode

Task Command

Configure the LSP retransmission interval ipx nlsp retransmit-interval seconds

Modify Link-State Packet Parameters

To modify link-state packet LSP parameters perform one or more of the following tasks in router

configuration mode

Task Command

Set the minimum LSP generation interval isp-gen-interval seconds

Set the maximum time the LSP persists max-isp-lifetime value

Set the LSP refresh time isp-refresh-interval seconds

Set the maximum size of link-state packet isp-mtu bytes

Set the minimum time between SPF spf-interval seconds

calculations

Limit Partial Route Calculations

You control how often the Cisco lOS software calculation can performs partial route PRC

the calculation is it be useful limit how often this Because partial route processor-intensive may to

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

P2C-98 Network Protocols Configuration Guide Part Configure NLSP

To modify the partial route calculation perform the following task in router configuration mode

Task Command

Set the hoiddown period between partial route prc-interval seconds

calculations

Configure Route Aggregation

Prior to Cisco lOS Release 11.1 you could segregate IPX intemetworks into distinct NLSP areas them with IPX With only by interconnecting RIP 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 Novells NetWare

Link Services Protocol NLSP Specification Revision 1.1

Note In the sections that version 1.1 follow NLSP routers refers to routers that support the route

while version 1.0 routers aggregation feature NLSP refers to routers that do not Additionally all instances Release NLSP configured on router running 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

Benefits of Route Summarization NLSP route summarization provides the following benefits to well-designed IPX networks

address route Compact representationA single aggregated efficiently represents many explicit routes

Reduced update bandwidthMost changes in the explicit routes represented by an aggregated

route do not need to be propagated to neighboring areas

Reduced computational overheadSince the routers in one area are unaffected by most changes

in adjacent areas the SPF algorithm runs less often

Improved information managementFiltering of route and service information may be done at area boundaries

As result you can build larger IPX networks using route aggregation

Understand 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

Configuring Novell IPX P2C-99 Configure NLSP

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 configure up to three area addresses per NLSP process on the router Adjacencies are formed

only between routers that share at least one common area address

Route Summaries

route summaiy defines set of explicit routes that the router uses to generate an aggregated route

route sunmiary 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

An aggregated route is the single compact data stnicture that describes many IPX network numbers

route all the routes defined the route simultaneously The aggregated represents explicit by summary

In an LSP the router expresses an aggregated route as 1-byte number that gives the length in bits

of the 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 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

individually into neighboring NLSP areas Instead the router redistributes single aggregated route

that is equivalent to the area address into neighboring areas

Understand NLSP Areas

This section describes single versus multiple NLSP areas and discusses the routers behavior when mix NLSP you NLSP versions within single area

Single Versus Multiple NLSP Areas

NLSP version 1.0 routers support only single Level area Two routers form an adjacency only if

they share at least one configured area address in common The union of routers with adjacencies in

common form an area

Each router within the NLSP area has its own adjacencies link-state and forwarding databases

Further each routers link-state database is identical Within the router these databases operate and maintain information about collectively as single process or instance to discover select route

the area NLSP version 1.0 routers and NLSP version 1.1 routers that exist within single area use

single NLSP instance

P2C-100 Network Protocols Configuration Guide Part Configure NLSP

With NLSP version 1.1 and Cisco lOS Release 11.1 multiple instances of NLSP may exist on given router Each instance and maintains discovers selects route information for separate NLSP

area Each instance has its own copy of the NLSP adjacency and link state database for its area

all instances with However along other routing protocols such as RIP and Enhanced IGRP share single copy of the forwarding table

Mixing NLSP Versions in Single Area

You have NLSP can version 1.1 routers and NLSP version 10 routers in the same area However

version 1.0 NLSP routers do not recognize aggregated routes For this reason the default behavior

of Cisco lOS Release 11.1 software is to not generate aggregated routes To prevent routing loops in mixed environment packets routed via an aggregated route by an NLSP version 1.1 router are

dropped if the next hop is an NLSP version 1.0 router

Note In should general you ensure that all routers in an area are running NLSP version 1.1 capable software before enable you route summarization on any of the routers in an area

Understand 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 routers default route redistribution behavior 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 Cisco lOS Release Regardless NLSP version 11.1 redistributes routes between multiple

NLSP areas default That redistribution by is 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 Refer to the Redistribute Information Routing section in 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

Configuring Novell IPX P2C-1O1 Configure NLSP

Understand Route Summarization

Route summarization is disabled by default to avoid the generation of aggregated routes in an area mixed versions of running NLSP You can explicitly enable route summarization on router running Cjsco lOS Release 11.1 This section describes default route summarization customized route

summarization and the relationship between filtering and route summarization

Default Route Summarization When you explicitly enable route summarization the default route summarization depends on the

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 1.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

generation of aggregated routes from the NLSP version 1.0 areas See the Customized Route

Summarization section

Some routers use Enhanced IGRP and NLSP version 1.1There is no default route

summarization You must configure customized route summarization to generate aggregated

routes from Enhanced IGRP to NLSP version 1.1 See the Customized Route Summarization

section

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

In the case of the first two circumstances the area address for each NLSP instance is used as the basis

for That all generating aggregated routes is explicit routes that match local area address generate

common aggregated route The router redistributes only the aggregated route into other NLSP routes areas explicit and more specific aggregated routes represented by particular aggregated

route are filtered

The Note router continues to redistribute into other areas the explicit routes that do not match the

area address

Customized Route Summarization

You can also customize the routers route summarization behavior using the redistribute IPX-router

subcomn-iand 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 list as template to control summarization and redistribution You can use numbered or

named 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

P2C1O2 Network Protocols Configuration Guide Part Configure NLSP

Route summarization between Enhanced IGRP and NLSP is controlled by the access list Route

summarization is possible only in the Enhanced IGRP-to-NLSP direction Routes redistributed from

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 explicit routes Use the default route instead to minimize routing update overhead

yet maximize reachability in RiP-only area

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

aggregated routes while all other external networks are reachable either by individual explicit routes or by the default route

Relationship between Filtering and Route Summarization

Redistribution of routes and services into and out of an NLSP area may be modified using filters

Filters are available for both input and output directions Refer to the distribute-list in

distribute-list out distribute- mp-list in and distribute-sap-list out commands in the Novell IPX Commands Chapter

is of Filtering independent route summarization but may affect it indirectly since filters are always

applied before the 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

Understand Service and Path Selection

The router always accepts service information as long as the services network is reachable by an

explicit route an aggregated route or the default route When choosing server for Get Nearest

Server the tick GNS response value 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 However because there is no hop value associated with an aggregated route services reachable via an explicit route are always preferred over those

reachable via only an aggregated route

An NLSP version 1.1 router always uses the most explicit match to route packets That is the router

always uses an explicit route if possible If not then 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

Configure Route Aggregation Task List

To configure the route aggregation feature perform one or more of the task in the following sections

Configure Route Aggregation for Multiple NLSP Version 1.1 Areas

Configure Route Aggregation for NLSP Version 1.1 and NLSP Version 1.0 Areas

Configure Route Aggregation for Enhanced IGRP and NLSP Version 1.1 Environments

Configure Route Aggregation for RIP and NLSP Version 1.1 Environments

Configuring Novell IPX P2C-103 Configure NLSP

Configure Route Aggregation for Multiple NLSP Version .1 Areas

Redistribution between multiple NLSP 11 areas is enabled by default Because multiple NILSP

processes are present on the router tag or label identifies each For each instance configure an

appropriate area address and optionally enable route summarization Finally enable NLSP on

appropriate interfaces Be sure to use the correct tag process identifier to associate that interface

with the appropriate NLSP area

Note Note that the tag used to identify an NLSP instance is meaningful only locally within the

router NLSP adjacencies and areas are determined by the area address and interfaces configured for

each instance of NLSP running on each router There is no need other than administrative

convenience to ensure that individual tags match between routers

The following sections describe how to configure route aggregation for multiple NLSP Version 1.1

areas

Configure Route Aggregation with Default Route Summarization

Configure Route Aggregation with Customized Route Summarization Using Numbered Access

Lists

Configure Route Aggregation with Customized Route Summarization Using Named Access Lists

Configure Route Aggregation with Default Route Summarization

To configure the route aggregation feature with the default route summarization behavior perform

these tasks for each NLSP process

Task Command

Step Enable NILSP routing and identify the ipx router nlsp

process with unique tag

Step From router configuration mode area-address address mask

define up to three area addresses for

the process

Step Optional From router configuration route-aggregation

mode enable route summarization

Step From interface configuration mode ipx nlsp enable

enable NILSP on each network in the

area described by the tag argument

For an example of how to configure this type of route aggregation see NLSP Route Aggregation

for NLSP Version 1.1 and Version 1.0 Areas Example section at the end of this chapter

P2C-104 Network Protocols Configuration Guide Part Configure NLSP

Configure Route with Aggregation Customized Route Summarization Using Numbered Access Lists

To configure the route aggregation feature with customized route summarization behavior using numbered access these lists peiform tasks for each NLSP process

Task Command

Enable NLSP Step routing and identify the ipx router nlsp process with unique tag

From router Step configuration mode area-address address mask

define up to three area addresses for

the process

Step Enable route summarization from route-aggregation

router configuration mode

Step From router configuration mode use redistribute nlsp access-list access-list-number the redistribute command with an

list in access the range of 1200 to 1299 In this case the tag argument identifies unique NLSP process

Step From interface configuration mode ipx nlsp enable

enable NLSP on each network in the

area described the by tag argument

Step From global configuration mode access-list access-list-number deny network define the access list to redistribute an network-mask ticks area-couni aggregated route instead of the route For each explicit address range you want to summarize use the deny keyword

Step Optional Terminate the list access access-list access-list-number permit -1 with permit all statement to

redistribute all other routes as explicit routes

Configure Route with Aggregation Customized Route Summarization Using Named Access Lists

To configure the route feature with aggregation customized route summarization behavior using named access lists perform these tasks for each NLSP process

Task Command

Step Enable NLSP and routing identify the ipx router nlsp with process unique tag

From router Step configuration mode area-address address mask

define up to three area addresses for

the process

Step Enable route summarization from route-aggregation

router configuration mode

Step From router configuration mode use redistribute nlsp access-list name the redistribute command with

named access list In this case the tag

argument identifies unique NLSP process

Configuring Novell IPX P2C-105 Configure NLSP

Task Command

From Step interface configuratica mode ipx nlsp enable

enable NLSP on each network in the

area described by the tag argument

From Step global configuration mode ipx access-list summary name

specify named IPX access list for

NLSP route aggregation

In access.list Step configuration mode deny network network-mask ticks

specify the redistribution of area-count

aggregated routes instead of explicit

routes For each address range you

want to summarize enter deny statement

Step Optional Terminate the access list permit -1

with permit all statement to

redistribute all other routes as explicit routes

Configure Route Aggregation for NLSP Version 1.1 and NLSP Version Areas

By default redistribution is enabled between multiple instances of NLSP Route summarization

when enabled is possible in one direction onlyfrom NLSP version 1.0 to NLSP version 1.1

The sections describe following how to configure route aggregation for NLSP Version 1.1 and NLSP Version 1.0 areas

Configure Route Aggregation with Default Route Summarization

Route Configure Aggregation with Customized Route Summarization Using Numbered Access Lists

Route with Customized Configure Aggregation Route Summarization Using Named Access Lists

Configure Route Aggregation with Default Route Summarization

To configure the route feature with default route aggregation summarization behavior perform the tasks for each following NLSP process

Task Command

Enable NLSP Step routing and identify the ipx router nlsp with process unique tag

From Step router configuration mode area-address address mask define up to three area addresses for

the process

For NLSP Step version 1.1 areas enable route-aggregation

route summarization from router

configuration mode Skip this step for

NLSP version 1.0 areas

From Step interface configuration mode ipx nlsp enable

enable NLSP on each network in the

area described by the tag argument

P2C-106 Network Protocols Configuration Guide Part Configure NLSP

Configure Route Aggregation with Customized Route Summarization Using Numbered Access Lists

To the route configure aggregation feature with customized route summarization behavior using numbered access lists perform the tasks in the following two tables

For the NLSP version 1.1 process perform these tasks

Task Command

Step Enable NLSP routing and identify the ipx router nlsp

process with unique tag

Step From router configuration mode area-address address mask

define up to three area addresses for

the process

For NLSP version Step 1.1 areas enable route-aggregation

route summarization from router

configuration mode

Step Optional From router configuration redistribute nlsp access-list access-list-number

mode redistribute NILSP version 1.0

into the NLSP version 1.1 area

Include an access list number between

1200 and 1299

From Step interface configuration mode ipx nlsp enable

enable NLSP on each network in the

area described by the tag argument

Step Optional From global configuration access-list access-list-number deny network

define the list mode access to network-mask ticks area-count area-countll

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 the deny keyword

Step Optional Terminate the access list access-list access-list-number permit -1 with permit all statement to

redistribute all other routes as explicit routes

For the version 1.0 NLSP process perform these tasks

Task Command

Enable Step NLSP routing and identify the ipx router nlsp

process with unique tag

Step From router configuration mode area-address address mask

define up to three area addresses for the process

Step From interface configuration mode ipx nlsp enable

enable NLSP on each network in the

area described by the tag argument

For an of how to the route feature example configure aggregation with this type of customized route refer summarization to the NILSP Route Aggregation for NLSP Version 1.1 and Version 1.0 Areas section Example at the end of this chapter

Configuring Novell IPX P2C-107 Configure NLSP

Configure 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 perform the tasks in the following two tables

For the NLSP version 1.1 process perform these tasks

Task Command

step Enable NILSP routing and identify the ipx router nlsp

process with unique tag

step From router configuration mode area-address address mask

define up to three area addresses for the process

Step For NLSP version 1.1 areas enable routeaggregation

route summarization from router

configuration mode

Step Optional From router configuration redistribute nlsp access-list name mode redistribute NLSP version 1.0

into the NLSP version 1.1 area

Step From interface configuration mode ipx nlsp enable

enable NLSP on each network in the

area described by the tag argument

Step Optional From global configuration ipx access-list summary name

mode specify named IPX access list

for NLSP route aggregation

Step Optional From access-list deny netsvork network-mask ticks

configuration mode define the access area-count

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

enter deny statement

Step Optional Terminate the access list permit -1

with permit all statement to

redistribute all other routes as explicit

routes

For the NLSP version 1.0 process perform these tasks

Task Command

Step Enable NLSP routing and identify the ipx router nlsp

process with unique tag

Step From router configuration mode area-address address mask

define up to three area addresses for the process

Step From interface configuration mode ipx nlsp enable

enable NLSP on each network in the

area described by the tag argument

P2C-108 Network Protocols Configuration Guide Part Configure NLSP

Configure Route Aggregation for Enhanced IGRP and NLSP Version Environments

Redistribution is not enabled by default Additionally summarization is possible in the Enhanced IGRP to NLSP direction only

The following sections describe how to configure route aggregation for Enhanced IGRP and NLSP

Version 1.1 environments

Configure Route Aggregation Using Numbered Access Lists

Configure Route Aggregation Using Named Access Lists

Configure Route Aggregation Using Numbered Access Lists

For each version 1.1 NLSP process perform these tasks beginning in global configuration mode

Task Command

Step Enable NLSP routing and identify the ipx router nlsp

process with unique tag

Step From router configuration mode area-address address mask

define up to three area addresses for

the process

Step Optional From router configuration route-aggregation mode enable route sunimarization

From router Step Optional configuration redistribute eigrp autonoinous-system-number

mode redistribute Enhanced IGRP access-list-number

into the NLSP version 1.1 area

Include an access list number between 1200 and 1299

Step From interface configuration mode ipx nlsp enable

enable NLSP on each network in the

area described by the tag argument

From Step Optional global configuration access-list access-list-number deny network define mode the access list to network-mask ticks area-countlj

redistribute an aggregated route

instead of explicit routes learned from

Enhanced IGRP For each address

range you want to sununarize use the

deny keyword

Step Optional Terminate the access list access-list access-list-number permit -1 with permit all statement to

redistribute all other Enhanced IGRP

routes as explicit routes

Configuring Novell IPX P2C-109 Configure NLSP

For each Enhanced IGRP autonomous system perform these tasks beginning in global configuration mode

Task Command

Step Enable Enhanced IGRP ipx router eigrp autonomous-system-number

Step From router configuration mode network network-n umber all

specify the networks to be enabled for Enhanced IGRE

Step From router configuration mode redistribute nlsp

redistribute NLSP version 1.1 into

Enhanced IGRP

For an example of how to configure this type of route aggregation refer to the NLSP Route

Aggregation for NLSP Version 11 Enhanced IGRP and RIP Example section at the end of this

chapter

Configure Route Aggregation Using Named Access Lists

For each NLSP version 1.1 process perform these tasks beginning in global configuration mode

Task Command

Step Enable NLSP routing and identify the ipx router nlsp

process with unique tag

Step From router configuration mode area-address address mask

define up to three area addresses for

the process

Step Optional From router configuration route-aggregation mode enable route summarization

Step Optional From router configuration redistribute eigrp autonomous-system-number mode redistribute Enhanced IGRP access-list name

into the NLSP version area

Step From interface configuration mode ipx nlsp enable

enable NLSP on each network in the

area described by the tag argument

From Step Optional global configuration ipx access-list summary name

mode specify named IPX access list

for NLSP route aggregation

Step Optional From access-list deny network network-mask ticks

configuration mode define the access area-count

list to redistribute an aggregated route

instead of explicit routes learned from

Enhanced IGRP For each address

range you want to suimnarize enter deny statement

Step Optional Terminate the access list permit -1

with permit all statement to

redistribute all other Enhanced IGRP

routes as explicit routes

P2C-11O Network Protocols Configuration Guide Part Configure NLSP

For each Enhanced IGRP autonomous system perform these tasks beginning in global configuration mode

Task Command

Step Enable Enhanced IGRP ipx router eigrp autonomous-system-number

Step From router configuration mode network network-number all

specify the networks to be enabled for Enhanced IGRP

Step From router configuration mode redistribute nlsp

redistribute NLSP version 1.1 into

Enhanced IGRP

Configure Route Aggregation for RIP and NLSP Version .1 Environments

Because redistribution between RIP and NLSP is enabled by default you only need to enable the

route summarization if desired to configure all the capabilities of the route aggregation feature

The following sections describe how to configure route aggregation for RIP and NLSP Version 1.1 environments

Configure Route Aggregation Using Numbered Access Lists

Configure Route Aggregation Using Named Access Lists

Configure Route Aggregation Using Numbered Access Lists

For each NLSP version 1.1 process perform these tasks beginning in global configuration mode

Task Command

Step Enable NLSP routing and identify the ipx router nlsp

process with unique tag

Step From router configuration mode area-address address mask

define up to three area addresses for

the process

Step Optional From router configuration route-aggregation

mode enable route summarization

Step Optional From router configuration redistribute rip access-list-number

mode redistribute RIP routes into the

NLSP version 1.1 area Include an

access list number between 1200 and 1299

Step From interface configuration mode ipx nlsp enable

enable NLSP on each network in the

area described by the tag argument

Step Optional From global configuration access-list access-list-number deny network

mode define the access list to network-mask ticks area-count

redistribute an aggregated route

instead of explicit RIP routes For

each address range you want to summarize use the deny keyword

Step Optional Terminate the access list access-list access-list-number permit -1

with permit all statement to

redistribute all other RIP routes as

explicit routes

Configuring Novell IPX P2C-111 Configure NLSP

For an example of how to configure this type of route aggregation refer to the NLSP Route for Version Enhanced Aggregation NLSP 11 IGRP and RIP Example section at the end of this

chapter

Configure Route Aggregation Using Named Access Lists

For each version 1.1 NLSP process perform these tasks beginning in global configuration mode

Task Command

Step Enable NLSP routing and identify the ipx router nlsp

process with unique tag

Step From router configuration mode area-address address mask

define up to three area addresses for

the process

Step Optional From router configuration route-aggregation

mode enable route summarization

Step Optional From router configuration redistribute rip access-list name

mode redistribute RIP routes into the

NLSP version 11 area

Step From interface configuration mode ipx nlsp enable

enable NLSP on each network in the

area described by the tag argument

From Step Optional global configuration ipx access-list summary name

mode specify named IPX access list

for NLSP route aggregation

Step Optional From access-list deny network network-mask ticks

configuration mode define the access area-count

list to redistribute an aggregated route

instead of explicit RIP routes For

each address range you want to summarize enter deny statement

Step Optional Terminate the access list permit -1 with permit all statement to

redistribute all other RIP routes as

explicit routes

Customize the Exchange of Routing Information

You customize might want to the exchange of routing information The following sections describe customization tasks

Configure RIP and SAP Compatibility

Redistribute Routing Information

Configure RIP and SAP Compatibility

Routing Information Protocol RIP and Service Advertisement Protocol 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 only if another RIP router or SAP service is sending RIP or SAP traffic

P2C-112 Network Protocols Configuration Guide Part Configure NLSP

To modify the generation of periodic RIP updates on network enabled for NLSP perform one of

the following tasks in interface configuration mode

Task Command

Never generate RIP periodic traffic ipx nlsp rip off

Always generate RIP periodic traffic ipx nlsp rip on

Send RIP periodic traffic only if another RIP ipx nlsp rip auto

router is sending periodic RIP traffic This is

the default on interfaces configured for NLSP

To the modify generation of periodic SAP updates on network enabled for NLSP perform one of

the following tasks in interface configuration mode

Task Command

Never SAP generate periodic traffic ipx nlsp sap off SAP Always generate periodic traffic ipx nlsp sap on

Send SAP periodic traffic only if another SAP ipx nlsp sap auto

service is sending periodic SAP traffic This is

the default on interfaces configured for NLSP

Redistribute Routing Information

Automatic redistribution of one routing protocol into another provides simple and effective means

for building IPX networks in heterogeneous routing protocol environment Redistribution is

effective enable usually 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 IGRP you and NLSP redistribution the router makes path decisions based

on predefined nonconfigurable administrative distance and prevents redistribution feedback loops

without filtering via stored external hop count

To enable redistribution of Enhanced IGRP into NLSP and vice versa perform the following tasks

beginning in global configuration mode

Task Command

Step Enable NLSP ipx router nlsp

From IPX-router Step configuration mode redistribute eigrp autonomous-systein-nwnber enable redistribution of Enhanced

IGRP into NLSP

From Step global configuration mode ipx router eigrp autonoinous-system-nu.nber enable Enhanced IGRP

IPX-router Step From configuration mode redistribute nlsp

enable 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

Configuring Novell IPX P2C-113 Configure Next Hop Resolution Protocol

Configure Next Hop Resoution Protocol

Routers access servers and hosts can use Next Hop Resolution Protocol NHRP to discover the addresses of other routers and hosts connected to nonbroadcast multiaccess NBMA network NHRP provides an ARP-like solution that alleviates some NBMA network problems With NHRP

systems attached to an NBMA network can dynamically learn the NBMA address of the other

systems that are part of that network These systems can then directly communicate without requiring traffic to use an intermediate hop

For more information on NHRP and Ciscos implementation refer to the Configuring IP

Addressing chapter in the Network Protocols Configuration Guide Part

NHRP Configuration Task List

To configure NHRP perform the tasks described in the following sections The first task is required

the remainder are optional

Enable NHRP on an Interface

Configure Stations Static IPX-to-NBMA Address Mapping

Statically Configure Next Hop Server

Configure NHRP Authentication

Control NHRP Initiation

Control NHRP Packet Rate

Suppress Forward and Reverse Record Options

Specify the NHRP Responder Address

Change the Time Period NBMA Addresses Are Advertised as Valid

For NHRP configuration examples see the NHRP Examples section at the end of this chapter

Enable NHRP on an Interlace

To enable NHRP for an interface on router perform the following task in inteiface configuration

mode In general all NHRP stations within logical NBMA network must be configured with the

same network identifier

Task Command

Enable NHRP on an interface ipx nhrp network-id number

For an example of enabling NHRP see the NHRP Examples section at the end of this chapter

Configure Stations Static IPX-to-NBMA Address Mapping

To participate in NHRP station connected to an NBMA network must be configured with the IPX

and NBMA addresses of its Next Hop Servers The format of the NBMA address depends on the

medium you are using For example ATM uses network-layer service access point NSAP address Ethernet uses MAC address and SMDS uses an E.164 address

These Next Hop Servers are most likely the stationss default or peer routers so their IPX addresses

are obtained from the stations network layer forwarding table

P2C-114 Network Protocols Configuration Guide Part Configure Next Hop Resolution Protocol ______

is attached to several link If the station layer networks including logical NBMA networks the should also be to receive station configured routing information from its Next Hop Servers and peer

that it can determine which IPX networks routers so are reachable through which link layer networks

IPX-to-NBMA To configure static address mapping on station host or router perform the following task in interface configuration mode

Task Command

IPX-to-NBMA address Configure static mapping ipx nhrp map ipx-address nbtna-address

Configure Next Hop Server

Server uses the network Next Hop normally layer forwarding table to determine where to forward

and to find the from NHRP packets egress point an NBMA network Next Hop Server may be with set of alternately statically configured IPX address prefixes that correspond to the IPX

addresses of the stations it serves and their logical NBMA network identifiers

Next To statically configure Hop Server perform the following task in interface configuration mode

Task Command

Server Statically configure Next Hop ipx nhrp nhs nhs-address

To networks that the Next Server configure multiple Hop serves repeat the ipx nhrp nhs command with the same Next Server address but different IPX Hop network addresses To configure additional Next Hop Servers repeat the ipx nhrp nhs command

igure NHRP Authentication

an authentication ensures that Configuring string only routers configured with the same string can

intercommunicate NHRP if the using Therefore authentication scheme is to be used the same string be in all devices for must configured configured NHRP on fabric To specify the authentication

for on an interface the string NHRP perform following task in interface configuration mode

Command

authentication Specify an string ipx nhrp authentication string

trol NHRP Initiation

one of the tasks in the Complete following sections to control when NHRP is initiated

Trigger NHRP by IPX Packet

Trigger NHRP on Per-Destination Basis

NHRP by IPX Packet

an IPX access list that is used You can specify to decide which IPX packets trigger the sending of default all non-NHRP NHRP requests By packets can trigger NHRP requests To limit which IPX

NHRP define list packets trigger requests you must an access and then apply it to the interface

Configuring Novell IPX P2C-115 Configure Next Hop Resolution Protocol

To define an access list perform one of the following tasks in global configuration mode

Task Command

Define standard IPX list access source-networkaccess-list access-list-n umber deny permit -network .destination-node

-node-mnaskl

Define an extended IPX access list access-list access-list-number deny permit

protocol

source-node-nask

source-network-mnasksource-node-naskJ

network

destination-node-mask destination-network-mask

.destination-nodemnask

Then apply the IPX access list to the interface by performing the following task in interface

configuration mode

Task Command

Specify an IPX access list that controls NHRP ipx nhrp interest access-list-n umber

requests

Trigger NHRP on Per-Destination Basis

when the software By default attempts to transmit data packet to destination for which it has

determined that be NHRP can used it transmits an NHRP request for that destination You can the configure system to wait until specified number of data packets have been sent to particular destination before NHRP is attempted To do so perform the following task in interface

configuration mode

Task Command

how data Specify many packets are sent to ipx nhrp use usage-count destination before NHRP is attempted

Control NHRP Packet Rate

By default the maximum rate at which the software sends is NHRP packets packets per 10 seconds The software maintains per-interface quota of NHRP packets whether generated

or that be locally forwarded can transmitted To change this maximum rate perform the following

task in interface configuration mode

Task Command

the NHRP rate interface Change packet per ipx nhrp max-send pkt-count every interval

Suppress Forward and Reverse Record Options

To detect dynamically link-layer filtering in NBMA networks for example SMDS address screens and to detection provide loop and diagnostic capabilities NHRP incorporates route record in and The requests replies route record options contain the network and link layer addresses of all

intermediate Next Hop Servers between source and destination in the forward direction and

between destination and source in the reverse direction

P2C-116 Network Protocols Configuration Guide Part Configure IPX and SPX over WANs

record and record included in NHRP and By default forward options reverse options are request the of these the task in interface reply packets To suppress use options perform following

configuration mode

Task Command

and record no record Suppress forward reverse options ipx nhrp

the NHRP Address ly Responder

know it If an NHRP requester wants to which Next Hop Server generates an NHRP reply packet can

information the address in its The request that by including responder option NHRP request packet the Next Hop Server that generates NHRP reply packet then complies by inserting its own IPX

address in the NHRP reply The Next Hop Server uses the primary IPX address of the specified

interface

interface the Next Server for the IPX To specify which Hop uses NHRP responder address perform

the following task in interface configuration mode

Task Command

Server Specify which interface the Next Hop uses ipx nhrp responder type number

to determine the NHRP responder address

Server contains that If an NHRP reply packet being forwarded by Next Hop Next Hop Servers

own IPX address the Next Hop Server generates an NHRP Loop Detected error indication and

discards the reply

iange the Time Period NBMA Addresses Are Advertised as Valid

You can change the length of time that NBMA addresses are advertised as valid in positive and

In this advertised the Cisco lOS software tells negative NHRP responses context means how long

the addresses it is in default of time for other routers to keep providing NHRP responses The length

seconds To the task each response is 7200 hours change the length of time perform following

in interface configuration mode

Task Command

number of seconds that NBMA holdtime Specify the ipx nhrp seconds-positive

addresses are advertised as valid in positive or

negative NHRP responses

Dnfigure PX and SPX over WANs

You can configure IPX over dial-on-demand routing DDR Frame Relay Point-to-Point Protocol PPP Switched Multimegabit Data Service SMDS and X.25 networks To do this you configure address mappings as described in the appropriate chapter

address When you configure IPX over PPP maps are not necessary for this protocol Also you can enable IPX header compression over point-to-point links to increase available useful bandwidth of time for the link and reduce response interactive uses of the link

You can use fast-switching IPX serial interfaces configured for Frame Relay and SMDS and you

can use fast-switching SNAP-encapsulated packets over interfaces configured for ATM

the Additionally you can configure IPXWAN protocol

Configuring Novell IPX P2C-117 Configure IPX and SPX over WANs

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

Configure IPX over DDR

IPX sends These periodic watchdog keepalive packets are keepalive packets that are sent from

to clients after client session has been idle servers for approximately minutes On DDR link

this that call would be made means every minutes regardless of whether there were data packets

to send You can prevent these calls from being made by configuring the Cisco lOS software to

respond to the servers watchdog packets on remote clients behalf This is sometimes referred to

as spoofing the server

When IPX configuring over DDR you might want to disable the generation of these packets so that

call is not made minutes This is very not an issue for the other WAN protocols because they

establish dedicated connections rather than establishing connections only as needed

To the serial interface idle keep when only watchdog packets are being sent refer to the tasks

described in the Deciding and Preparing to Configure DDR chapter of the Dial Solutions Guide For Configuration an example of configuring IPX over DDR see the IPX over DDR

Example section at the end of this chapter

Configure SPX Spoofing 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 stopped being On pay-per-packet or byte networks these can incur customer connection packets large telephone charges for idle time You can prevent these

calls from made the Cisco lOS being by configuring software to respond to the keepalive packets on behalf of remote system

When SPX over configuring DDR you might want to disable the generation of these packets so that

call has the to idle This be opportunity go may not an issue for the other WAN protocols because

establish dedicated connections rather than they establishing connections only as needed

To the serial interface idle when keep only keepalive packets are being sent refer to the tasks

described in the and Deciding Preparing to Configure DDR chapter of the Dial Solutions Configuration Guide

For an of how to SPX example configure spoofing over DDR see the IPX over DDR Example section at the end of this chapter

Configure IPX Header Compression

You can IPX header 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 IXPWAN The Cisco lOS software IPX header supports compression as defined by RFC 1553

For details on IPX header configuring compression refer to the Configuring Media-Independent PPP and Multilink in PPP chapter the Dial Solutions Configuration Guide

P2C-118 Network Protocols Configuration Guide Part Control Access to IPX Networks

Configure the IPXWAN Protocol

Cisco software the The lOS supports IPXWAN protocol as defined in RFC 1634 IPXWAN allows

router that is IPX running routing to connect via serial link to another router possibly from

another that is also manufacturer routing IPX and using IPXWAN

IPXWAN is connection start-up protocol Once link has been established IPXWAN incurs little or no overhead

You the can use 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 configure IPXWAN perform the following tasks in interface configuration mode on serial interface

Task Command

Step Ensure that you have not configured no ipx network

an IPX network number on the

interface

Step Enable PPP encapsulation ppp

Step Enable IPXWAN ipx ipxwan netvork-number

unnumbered local-server-name retiy-interval

retiylimit

Step Optionally define how to handle ipx ipxwan error resume shutdown 1PXWAN when serial link fails

Step Optionally enable static routing with ipx ipxwan static

IPXWAN Note that the remote site

must also use static routing

Contro Access to IIPX Networks

To control access to IPX networks you 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 traffic by specifying destination address and source and destination address mask

Standard 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 Service Advertisement Protocol SAP type

These lists used for SAP filters and Get are Nearest Server GNS response filters Novell SAP

access lists use numbers from 1000 to 1099 or names to identify them

IPX NetBIOS access listRestricts IPX NetBIOS traffic based on NetBIOS names not numbers

Configuring Novell IPX P2C-119 Control Access to IPX Networks

NLSP route aggregation access listSpecifies in detail which routes to summarize and which

routes to redistribute Route is explicitly aggregation discussed in detail in the Configure Route Aggregation section Refer to that section for more information

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

packets source and destination addresses and IPX protocol type

table filtersControl which Routing Routing Information Protocol RIP updates are accepted

and advertised the Cisco lOS and from which devices the local by software router accepts RIP updates

SAP filtersControl which SAP services the Cisco lOS software accepts and advertises and which Get Nearest Server GNS response messages it sends out

IPX NetBIOS filtersControl incoming and outgoing IPX NetBIOS packets

Broadcast filtersControl which broadcast packets are forwarded

NLSP route aggregation filtersControl the redistribution of routes and services into and out of an NLSP area

Table summarizes 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 Route aggregation is discussed in detail in the Configure Route Aggregation section

Refer to that section for additional information

P2C-120 Network Protocols Configuration Guide Part Control Access to IPX Networks

Table IPX Filters

Filter Type Access List Used by Filter Command to Define Filter

Generic filters

Filter inbound or outbound packets based on the Standard or Extended ipx access-group access-list-number name out

contents of the IPX network header

Routing table filters

Control which networks are added to the routing Standard or Extended ipx input-network-filter access-list-number name

table

Control which networks are advertised in Standard or Extended ipx output-network-filter access-list-nuinber name

routing updates

Control which networks are advertised in the Standard or Extended distribute-list access-list-number name out

Enhanced IGRP routing updates sent out by the routing-process Cisco lOS software

Control the routers from which updates are Standard or Extended ipx router-filter access-list-number name

accepted

SAP filters

Filter incoming service advertisements SAP ipx input-sap-filter access-list-number name

Filter outgoing service advertisements SAP ipx output-sap-filter access-list-nutnber name

Control the routers from which SAP updates are SAP ipx router-sap-filter access-list-number name

accepted

Filter list of servers in GNS response messages SAP ipx output-gns-filter access-list-nunmber name

IPX NetBIOS filters

Filter incoming packets by node name IPX NetBIOS ipx netbios input-access-filter host name

Filter incoming packets by byte pattern IPX NetBIOS ipx netbios input-access-filter bytes name

Filter outgoing packets by node name IPX NetBIOS ipx netbios output-access-filter host name

Filter outgoing packets by byte pattern IPX NetBIOS ipx netbios output-access-filter bytes name

Broadcast filters

Control which broadcast packets are forwarded Standard or Extended ipx helper-list access-list-nunmber name

Implementation Considerations

Keep the following information in mind when configuring IPX network access control

in The first is used To Access lists entries are scanned the order you enter them matching entry

the used entries the improve performance it is recommended that you place most commonly near

beginning of the access list

An implicit deny everything entry is defined at the end of an access list unless you include an

explicit permit everything entry at the end of the list

For numbered access lists all new entries to an existing list are placed at the end of the list You included cannot add an entry to the middle of list This means that if you have previously an

The solution is to delete the explicit permit everything entry new entries will never be scanned

access list and re-enter it with the new entries

For named access lists all new entries to an existing list are placed at the end of the list You

entries the cannot add entries to the middle of list However you can remove specific using no

deny and no permit commands rather than deleting the entire access list

Configuring Novell IPX P2C-121 Control Access to IPX Networks

Do not to set conditions that result in up packets getting lost One way this can happen is when

device interface is or configured to advertise services on network that has access lists that deny

these packets

You cannot filter SAP packets within an NLSP area You can filter them at the boundary of NLSP and RIP/SAP areas though restrictions do apply For more information about filtering at these

refer the boundaries to Relationship between Filtering and Route Summarization section in the and the chapter Novell NetWare Link Services Protocol NLSP Specification

Control Access to IPX Networks Task List

the You perform required tasks in the following section to control access to IPX networks

Create Access Lists

Create Filters

Create Access Lists

You create lists numbers can access using or names You can choose which method you prefer If you use numbers to identify your access lists you are limited to 100 access lists per filter type If you

names to access lists can have an unlimited number of lists filter identify your you access per type

The following sections describe how to perform these tasks

Create Access Lists Using Numbers

Create Access Lists Using Names

Create Access Lists Using Numbers

To create access lists using numbers you can perform one or more of the following tasks in global

configuration mode

Task Command

Create standard IPX access list using access-list access-list-number deny permit number Generic routing and broadcast filters source-network source-node use this type of access list etwork

Create an extended IPX access list access-list access-list-number using deny permit protocol

number Generic routing and broadcast filters etwork .source-node

use this type of access list

source-socket

elivork-inask.destination-node-inaskj

destination-socketl

Create SAP filtering access list using access-list access-list-number deny permit number SAP and GNS response filters use this network node-mask

type of access list

Once you have created an access list using numbers apply it to the appropriate interfaces using filters

as described in the Create Filters section of this chapter This activates the access list

P2C-122 Network Protocols Configuration Guide Part Control Access to IPX Networks

Names Access Lists Using Create lists allow to IPX lists with IPX named access you identify access an alphanumeric string name

rather than number You can configure an unlimited number of the following types of IPX named

access lists

Standard

Extended

SAP

NLSP route aggregation summarization

NetBIOS

If you identify your access list with name rather than number the mode and command syntax are

slightly different

Benefits of IPX Named Access Lists

Using IPX named access lists allow you to maintain 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 per filter type

Implementation Considerations for Configuring IPX Named Access Lists

Consider the following information before configuring IPX named access lists

Except for NetBIOS access lists access lists specified by name are not compatible with releases

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

To configure IPX named access lists for standard extended SAP NLSP route aggregation

summarization or NetBIOS access lists complete one or more of the tasks in the following

sections

Create Named Standard Access List

Create Named Extended Access List

Create Named SAP Filtering Access List

Create Named NLSP Route Aggregation Access List

Create NetBIOS Access List

Configuring Novell IPX P2C-123 Control Access to IPX Networks

Create Named Standard Access List

named standard To create access list perform the following tasks beginning in global configuration mode

Task Command

Step Define standard IPX access list using ipx access-list standard name

name Generic routing and

broadcast filters use this type of access

list

Step In access-list configuration mode deny permit source-nelivork

specify one or more conditions

allowed or denied This determines

whether the packet is passed or

dropped

Step Exit access-list configuration mode exit

For an example of creating named standard access list see the Standard Named Access List

Example section at the end of this chapter

Create Named Extended Access List

To create named extended access list perform the following tasks beginning in global

configuration mode

Task Command

Step Define an extended IPX access list ipx access-list extended name

using name Generic routing and

broadcast filters use this type of access

list

Step In access-list configuration mode deny permit protocol

specify the conditions allowed or source-node-maskll .source-node

denied Use the log keyword to get source-network-mask.source-node-nask

access list logging messages

including violations destination-node-mask -node

destination-network-mask.destination-node-mask

Step Exit access-list configuration mode exit

P2C-124 Network Protocols Configuration Guide Part Control Access to IPX Networks

Create Named SAP Filtering Access List

To create named access list for filtering SAP requests perform the following tasks beginning in global configuration mode

Task Command

Step Define SAP filtering access list ipx access-list sap name

using name SAP and GNS

response filters use this type of access list

Step In access-list configuration mode deny permit network

specify the conditions allowed or

denied

Step Exit access-list configuration mode exit

Create Named NLSP Route Aggregation Access List

NLSP route aggregation access lists perform one of the following functions

Permit networks to be redistributed as explicit networks without summarization

the redistribution of networks Deny explicit and generate an appropriate aggregating summary

route for redistribution

To create named access list for NLSP route aggregation perform the following tasks beginning in global configuration mode

Task Command

Step Define an IPX access list for NLSP ipx access-list summary name

route aggregation using name

Step In access-list configuration mode deny permit network network-mask ticks

specify the conditions allowed or area-count

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

Exit access-list exit Step configuration mode

For information on how to use named access list when configuring route aggregation refer to the tasks listed in the Configure Route Aggregation Task List section of this chapter

Configuring Novell IPX P2C-125 Control Access to IPX Networks

Create NetBIOS Access List

To create NetBIOS access list perform one or more of the following tasks in global configuration mode

Task Commands

Create an access list for filtering iPX NetBIOS netbios access-list host na/ne deny permit node packets by name NetBIOS filters use this string

type of access list

Create list for an access filtering IPX NetBIOS netbios access-list bytes name deny permit

packets by arbitrary byte pattern NetBIOS filters offset byte-pattern

use this type of access list

Modifying IPX Named Access Lists

After create an access you initially list you place any subsequent additions possibly entered from

the terminal at the end of the list In other words you cannot selectively add access list command lines to the middle of specific access list However you can use no permit and no deny commands

to remove entries from named access list

Note When creating access lists remember that by default the end of the access list contains an

statement for if implicit deny everything it did not find match before reaching the end

For an of creating generic filter see the example IPX Network Access Examples section at the end of this

chapter

Applying Named Access Lists to Interfaces

After creating an access list must it to the you apply appropriate interface using filters as described

in the Create Filters section of this chapter This activates the access list

Create Filters

Filters allow you to control which traffic is forwarded or blocked at routers interfaces Filters apply

specific numbered or named access lists to interfaces

The sections describe how to the following perform tasks for creating filters

Create Generic Filters

Create Filters for Updating the Routing Table

Create SAP Filters

Create GNS Response Filters

Create IPX NetBIOS Filters

Create Broadcast Message Filters

P2C-126 Network Protocols Configuration Guide Part Control Access to IPX Networks

Create Generic Filters

Generic filters determine which data packets to receive from or send to an interface based on the

packets source and destination addresses IPX protocol type and source and destination socket numbers

To create generic filters perform the following tasks

Step Create standard or an extended access list as described in the Create Access Lists

section of this chapter

Step Apply filter to an interface

To apply generic filter to an interface perform the following task in interface configuration mode

Task Command

Apply generic filter to an interface ipx access-group access-list-number name lin out

filter and filter You can apply only one input one output per interface or subinterface You cannot

configure an output filter on an interface where autonomous switching is already configured

Similarly you cannot configure autonomous switching on an interface where an output filter is

already present You cannot configure an input filter on an interface if autonomous switching is

already configured on any interface Likewise you cannot configure input filters if autonomous

switching is already enabled on any interface

For an example of creating generic filter see the IPX Network Access Examples section at the

end of this chapter

Create Filters for Updating the Routing Table

Routing table update filters control the entries that the Cisco lOS software accepts for its routing

table and the networks that it advertises in its routing updates

To create filters to control updating of the routing table perform the following tasks

Step Create standard or an extended access list as described in the Create Access Lists

section of this chapter

Step Apply one or more routing filters to an interface

To apply routing table update filters to an interface perform one or more of the following tasks in

interface configuration mode

Task Command

Control which networks are added to the ipx input-network-filter access-list-nuinber name

routing table when IPX routing updates are received

Control which networks are advertised in RIP ipx output-network-filter access-list-number name

routing updates sent out by the Cisco lOS software

Control which networks are advertised in the distribute-list access-list-number name out

Enhanced IGRP routing updates sent out by the routing-process Cisco lOS software

Control the routers from which routing updates ipx router-filter access-iist-nuniber naine

are accepted

Configuring Novell IPX P2C-127 Control Access to IPX Networks

Note The ipx output-network-filter command applies to the IPX RIP only To control the of routes when in advertising filtering routing updates Enhanced JGRP use the distribute-list out command See the Control the of Routes in Advertising Routing Updates section in this chapter for more information

Create SAP Filters

common source of traffic on Novell networks is SAP messages which are generated by NetWare and the servers Cisco 105 software when they broadcast their available services To control how SAP messages from network or servers routed segments specific are among IPX networks perform the following steps

Create SAP list Step filtering access as described in the Create Access Lists section of this chapter

Step Apply one or more filters to an interface

To apply SAP filters to an interface of the perform one or more following tasks in interface configuration mode

Task Command

Filter incoming service advertisements ipx input-sap-filter access-list-nunber name

Filter outgoing service advertisements ipx output-sap-filter access-list-number name

Filter service advertisements received from ipx router-sap-filter access-list-number name particular router

You can apply one of each SAP filter to each interface

For of and SAP examples creating applying filters see the SAP Input Filter Example and SAP Filter Output Example sections at the end of this chapter

Create GNS Response Filters

To create filters for which servers included in controlling are the GNS responses sent by the Cisco lOS software perform the following tasks

Create SAP Step filtering access list as described in the Create Access Lists section of this chapter

Step Apply GNS filter to an interface

To apply GNS filter to an the interface perform following task in interface configuration mode

Task Command

Filter the list of servers in GNS response ipx output-gns-filter access-list-number name messages

Create IPX NetBIOS Filters

Novells IPX NetBIOS allows to be messages exchanged between nodes using alphanumeric names

and node addresses Therefore the Cisco lOS software lets you filter incoming and outgoing

NetBIOS FindName the node packets by name or by an arbitrary byte pattern such as the node address in the packet

P2C-128 Network Protocols Configuration Guide Part Control Access to IPX Networks

Note These filters apply to IPX NetBIOS FindName packets only They have no effect on LLC2

NetBIOS packets

Implementation Considerations

Keep the following in mind when configuring IPX NetBIOS access control

Host node names are case sensitive

Host and lists the byte access can have same names because the two types of lists are independent of each other

When node filtering by name the names in the access lists are compared with the destination

name field for IPX NetBIOS find name requests

Access filters that filter by byte offset can have significant impact on the packet transmission

rate because each packet must be examined You should use these access lists only when

absolutely necessary

If node name is not found in an access list the default action is to deny access

IPX NetBIOS Filters Configuration Tasks

To create filters for controlling IPX NetBIOS access perform the following tasks

Step Create NetBIOS access list as described in the Create Access Lists section of this

chapter

Step Apply the access list to an interface

To NetBIOS list apply access to an interface perform one or more of the following tasks in

interface configuration mode

Task Command

Filter incoming packets by node name ipx netbios input-access-filter host name

Filter incoming packets by byte pattern ipx netbios input-access-filter bytes name

Filter outgoing packets by node name ipx netbios output-access-filter host name

Filter outgoing packets by byte pattern ipx netbios output-access-filter bytes name

You can apply one of each of these four filters to each interface

For an example of how to create filters for controlling IPX NetBIOS see the IPX NetBIOS Filter

Examples section at the end of this chapter

Create Broadcast Message Filters

Routers normally block all broadcast requests and do not forward them to other network segments

This is done to prevent 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

Configuring Novell IPX P2C-129 Tune IPX Network Performance

To create filters for controlling broadcast messages perform the following tasks

Step Create standard or an extended access list as described in the Create Access Lists

section of this chapter

Step Apply broadcast message filter to an interface

To apply broadcast message filter to an interface perform the following tasks in interface

configuration mode

Task Command

Step Specify helper address for ipx helper-address network.node

forwarding broadcast messages

Step Apply broadcast message filter to an ipx helper-list access-list-number name

interface

Note broadcast message filter has no effect unless you have issued an ipx helper-address or an

ipx type-20-propagation command on the interface to enable and control the forwarding of

broadcast messages These commands are discussed later in this chapter

For examples of creating and applying broadcast message filters see the Helper Facilities to

Control Broadcast Examples section at the end of this chapter

Tune PX Network Performance

You can tune IPX network performance by completing the tasks in one or more of the following

sections

Control Novell IPX Compliance

Adjust RIP and SAP Information

Configure Load Sharing

Specify the Use of Broadcast Messages

Disable IPX Fast Switching

Adjust the Route Cache

Adjust Default Routes

Pad Odd-Length Packets

Control Novell IPX Compliance

Ciscos implementation of Novells IPX protocol is certified to provide full IPX router functionality

as defined by Novells IPX Router Specification Version 1.10 published November 17 1992

You can control compliance to Novell specifications by performing the tasks in these sections

Control the Forwarding of Type 20 Packets

Control Interpacket Delay

Shut Down an IPX Network

Achieve Full Novell Compliance

P2C-130 Network Protocols Configuration Guide Part Tune IPX Network Performance

Control the Forwarding of Type 20 Packets

NetBIOS over IPX uses 20 type propagation broadcast packets flooded to all networks to get information about the named nodes the on network NetBIOS uses broadcast mechanism to get this

information because it does not implement network layer

Routers block all broadcast normally requests By enabling type 20 packet propagation IPX

interfaces on the router and may accept forward type 20 packets

How Type 20 Packet Propagation Works

When interface an configured for type 20 propagation receives type 20 packet Cisco lOS software the processes packet according to Novell specifications Cisco lOS software propagates the packet

to the interface The next type 20 packet can be propagated for up to 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

You can the Cisco lOS software to configure apply extra checks to type 20 propagation packets above and beyond the loop detection described in the 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

Accept type 20 propagation packets only on the primary network which is the network that is the

primary path back to the source network

Forward type 20 propagation packets only via networks that do not lead back to the source network

While this extra increases the checking robustness of 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 be might impossible to configure an arbitrary manual spanning tree for type 20 packet

propagation

Relationship between Type 20 Propagation and Helper Addresses

You addresses use helper to forward non-type 20 broadcast packets to other network segments For information on forwarding other broadcast packets see the Use Helper Addresses to Forward

Broadcast Packets section in this chapter

You can use addresses and 20 in helper type propagation together your network Use helper addresses to forward non-type 20 broadcast packets and use type 20 propagation to forward type 20

broadcast packets

Configuring Novell IPX P2C-131 Tune IPX Network Performance

Type 20 Packets Configuration Task List

You can enable the of 20 forwarding type packets on individual interfaces Additionally you can restrict the and of 20 acceptance forwarding type packets You can also choose to not comply with Novell specifications and forward type 20 addresses rather than packets using helper using type 20 propagation The following sections describe these tasks

Enable the Forwarding of Type 20 Packets

Restrict the Acceptance of Incoming Type 20 Packets

Restrict the Forwarding of Outgoing Type 20 Packets

Forward 20 Type Packets Using Helper Addresses

Enable the Forwarding of Type 20 Packets

By default type 20 propagation are the Cisco packets dropped by lOS software 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 receipt and of 20 forwarding type packets perform the following task in interface configuration mode

Task Command

Forward IPX 20 type propagation packet ipx type-20-propagation broadcasts to other network segments

When enable 20 you type propagation Cisco lOS propagates the broadcast to the next interface up to eight hops

Restrict the Acceptance of Incoming Type 20 Packets

For 20 incoming type propagation packets the Cisco lOS software is default configured by to accept packets on all interfaces enabled to receive 20 type propagation packets You can configure the software to from the accept packets only single network that is the primaly route back to the source

network This means that similar from packets the same source that are received via other networks will be dropped

of Checking incoming 20 broadcast is type propagation packets done oniy if the interface is to receive configured and forward type 20 packets

To impose restrictions on the of 20 receipt incoming type propagation packets in addition to the checks defined in the IPX the specification perform following task in global configuration mode

Task Command

Restrict the of IPX acceptance type 20 ipx type-20-input-checks propagation packets

Restrict the Forwarding of Outgoing Type 20 Packets

For outgoing type 20 the Cisco propagation packets lOS software is configured by default to send

packets on all interfaces enabled to send 20 type propagation packets subject to ioop detection You can the software configure to send these packets only to networks that are not routes back to the source network software The uses the current routing table to determine routes

P2C-132 Network Protocols Configuration Guide Part Tune IPX Network Performance

of 20 Checking outgoing type propagation broadcast packets is done only if the interface is receive and configured to forward type 20 packets

To restrictions on the transmission of impose type 20 propagation packets and to forward these

to all networks using only the checks defined in the IPX packets specification perform the following task in global configuration mode

Task Command

the of IPX Restrict forwarding type 20 ipx type-20-output-checks propagation packets

Forward Type 20 Packets Using Helper Addresses

also forward 20 You can type packets to specific network segments using helper addresses rather than using the type 20 packet propagation

want to forward 20 You may type packets using helper addresses when some routers in your network versions of Cisco lOS are running that do not support type 20 propagation When some routers in network 20 and others your support type propagation do not you can avoid flooding packets in the network addresses everywhere by using helper to direct packets to certain segments only

lOS Release 9.1 and earlier Cisco versions do not support type 20 propagation

Note Forwarding type 20 packets using helper addresses does not comply with the Novell IPX router specification

To forward type 20 packets addresses using helper addresses perform the following tasks beginning in global configuration mode

Task Command

Forward IPX 20 Step type packets to ipx type-20-helpered networks specific segments This step

turns off type 20 propagation

From interface Step configuration mode ipx helper-address nel-wo.node

specify helper address for

forwarding broadcast messages

including IPX type 20 packets

The Cisco lOS software forwards 20 type packets to only those nodes specified by the ipx helper-address command

Note Using the ipx command disables the type-20-helpered receipt and forwarding of type 20 propagation packets as directed by the ipx type-20-propagation command

Configuring Novell IPX P2C-133 Tune IPX Network Performance

Control Interpacket Delay

To control interpacket delay you can use combination of global configuration and interface

configuration commands

You can perform one or more of the following tasks in global configuration mode

Task Command

Set the interpacket delay of multiple-packet ipx default-output-rip-delay delay

routing updates sent on all inteifaces

Set the of interpacket delay multiple-packet ipx default-triggered-rip-delay delay

triggered routing updates sent on all interfaces

Set the interpacket delay of multiple-packet ipx default-output-sap-delay delay

SAP updates sent on all interfaces

Set the interpacket delay of multiple-packet ipx default-triggered-sap-delay delay

triggered SAP updates sent on all interfaces

You also can perform one or more of the following tasks in interface configuration mode

Task Command

Set the interpacket delay of multiple-packet ipx output-rip-delay delay

routing updates sent on single interface

Set the of interpacket delay multiple-packet ipx triggered-rip-delay delay

triggered routing updates sent on single

interface

Set the of interpacket delay multiple-packet ipx output-sap-delay delay

SAP updates sent on single interface

Set the of interpacket delay multiple-packet ipx triggered-sap-delay delay

triggered SAP updates sent on single

interface

Note We recommend that use you an ipx output-rip-delay and ipx output-sap-delay on slower

speed WAN interfaces.The default for Cisco Release 11.1 and later versions delay lOS is 55 ms

Shut Down an IPX Network

To shut down an IPX network using Novell-compliant method perform the following task in interface configuration mode

Task Command

shut down Administratively an IPX network on ipx down network

an interface This removes the network from

the interface

is faster when shut Convergence you down an IPX network using the ipx down command than when using the shutdown command

P2C-134 Network Protocols Configuration Guide Part Tune IPX Network Performance

Full Novell Compliance chieve To achieve full compliance issue the following interface configuration commands on each interface

configured for IPX

Task Command

Step Set the interpacket delay of ipx output-rip-delay 55

multiple-packet routing updates to 55 ms

Step Set the interpacket delay of ipx output-sap-delay 55

multiple-packet SAP updates to 55 ms

Step Optionally enable type 20 packet ipx type-20-propagation

propagation if you want to forward

type 20 broadcast traffic across the

router

You can also globally set interpacket delays for multiple-packet RIP and SAP updates to achieve full

compliance eliminating the need to set delays on each interface To do so issue the following

commands from global configuration mode

Task Command

Step Set the interpacket delay of ipx default-output-rip-delay 55

multiple-packet routing updates sent

on all interfaces to 55 ms

Set the Step interpacket delay of ipx default-output-sap-delay 55

multiple-packet SAP updates sent on

all interfaces to 55 ms

Note The default delay for Cisco lOS Release 11.1 and later versions is 55 ms

Information Adjust RIP and SAP

You can adjust RIP and SAP information by completing one or more of the optional tasks in the

following sections

Configure Static Routes

Adjust the RIP Delay Field

Adjust RIP Update Timers

Configure RIP Update Packet Size

Configure Static SAP Table Entries

Configure the Queue Length for SAP Requests

Adjust SAP Update Timers

Configure SAP Update Packet Size

Enable SAP-after-RIP

Disable Sending of General RIP or SAP Queries

Control Responses to GNS Requests

Configuring Novell IPX P2C-135 Tune IPX Network Performance

Configure Static Routes

IPX uses RIP Enhanced IGRP or NLSP to determine the best path when several paths to

destination exist The routing protocol then dynamically updates the routing table However you

might want to add static routes to the routing table to explicitly specify paths to certain destinations

Static routes always override any dynamically learned paths

Be careful when assigning static routes When links associated with static routes are lost traffic may

stop being forwarded or traffic may be forwarded to nonexistent destination even though an

alternative path might be available

To add static route to the routing table perform the following task in global configuration mode

Task Command

Add static route to the routing table ipx route network default network.node inteiface

You can configure static routes that can be overridden by dynamically learned routes These routes

are referred to 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

Note By default floating static routes are not redistributed into other dynamic protocols

To add floating static route to the routing table perform the following task in global configuration mode

Task Command

Add floating static route to the routing table ipx route network default network.node inteface

Adjust the RIP Delay Field

By default all LAN interfaces have RIP delay of and all WAN interfaces have RIP delay of

Leaving the delay at its default value is sufficient for most interfaces However you can adjust the

RIP delay field by setting the tick count To set the tick count perform the following task in interface

configuration mode

Task Command

Set the tick count which is used in the IPX RIP ipx delay number

delay field

Adjust RIP Update Timers

You set the interval between can IPX RIP updates on per-interface basis You can also specify the between the of delay packets multiple-packet RIP update on per-interface or global basis the Additionally you can specify delay between packets of multiple-packet triggered RIP update

on per-interface or global basis

P2C-136 Network Protocols Configuration Guide Part Tune IPX Network Performance

You can set RIP update timers only in configuration in which all routers are Cisco routers or in

which the IPX routers allow configurable timers The timers should be the same for all devices

connected to the cable The value same segment update you choose affects internal IPX timers as follows

IPX routes are marked invalid if no routing updates are heard within three times the value of the

interval and update interval are advertised with metric of infinity

IPX routes removed from the are routing table if no routing updates are heard within four times

the value of the update interval interval

If define timer for you more than one interface in router the granularity of the timer is

determined by the lowest value defined for one of the interfaces in the router The router wakes

this up at granularity interval and sends out updates as appropriate For more information about the granularity see Novell IPX Commands chapter in the Network Protocols Command Reference Part

You might want to set delay between the packets in multiple-packet update if there are some

slower PCs on the network or on slower-speed interfaces

To RIP timers all adjust update on per-interface basis perform any or of the following tasks in interface configuration mode

Task Command

the RIP Adjust update timer ipx update interval rip sap value changes-only

the between Adjust delay multiple-packet ipx output-rip-delay delay routing updates sent on single interface

Adjust the delay between multiple-packet ipx triggered-rip-delay delay triggered routing updates sent on single interface

To RIP timers adjust update on global basis perform any or all of the following tasks in global configuration mode

Task Command

Adjust the delay between multiple-packet ipx default-output-rip-delay delay routing updates sent on all interfaces

Adjust the delay between multiple-packet ipx default-triggered-rip-delay delay triggered routing updates sent on all interfaces

the By default RIP entry for network or server ages out at an interval equal to three times the RIP timer To configure the multiplier that controls the interval perform the following task in interface configuration mode

Task Command

Configure the interval at which network RIP ipx rip-multiplier multiplier entry ages out

Configuring Novell IPX P2C-137 Tune IPX Network Performance

Configure RIP Update Packet Size

By default the 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

perform the following task in interface configuration mode

Task Command

Configure the maximum packet size of RIP ipx rip-max-packetsize bytes

updates sent out an interface

Configure 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

Information Table that clients dynamically You might want to explicitly add an entry to the Server so

override identical always use the services of particular server Static SAP assignments always any

entries in the SAP table that are learned dynamically regardless of hop count If dynamic route that

the static SAP is associated with static SAP entry is lost or deleted the software will not announce

entry until it relearns the route

mode To add static entry to the SAP table perform the following task in global configuration

Task Command

Specify static SAP table entry ipx sap service-type name network node socket

hop-count

Configure the Queue Length for SAP Requests

The Cisco lOS software maintains list of SAP requests to process including all pending GNS

queries from clients attempting to reach servers When the network is restarted following power

failure or other unexpected event the router can be inundated with hundreds of requests for servers

from the clients You the Typically many of these are repeated requests same can configure maximum length allowed for the pending SAP requests queue SAP requests received when the client resend them queue is full are dropped and the must

task in mode To set the queue length for SAP requests perform the following global configuration

Task Command

Configure the maximum SAP queue length ipx sap-queue-maximum number

Adjust SAP Update Timers

You can adjust the interval at which SAP updates are sent You can also set the delay between packets

of multiple-packet SAP update on per-interface or global basis Additionally you can specify the

delay between packets of multiple-packet triggered SAP update on per-interface or global basis

Changing the interval at which SAP updates are sent is most useful on limited-bandwidth

point-to-point links such as slower-speed interfaces You should ensure that all IPX servers and decide routers on given network have the same SAP interval Otherwise they might that server

is down when it is really up

It is not possible to change the interval at which SAP updates are sent on most PC-based servers

should the interval for Ethernet or network that has This means that you never change an Token Ring

servers on it

P2C-138 Network Protocols Configuration Guide Part Tune IPX Network Performance

You can set the router to send an update oniy when changes have occurred Using the changes-only the keyword specifies sending of SAP update only when the link comes up when the link is

downed administratively or when the databases change The changes-only keyword causes the

router to do the following

Send single full broadcast update when the link comes up

Send appropriate triggered updates when the link is shut down

Send appropriate triggered updates when specific service information changes

To modify the SAP update timers on per-interface basis perform any or all of the following tasks

in interface configuration mode

Task Command

Adjust the interval at which SAP updates are ipx update interval rip sap value changes-only sent

Adjust the interpacket delay of multiple-packet ipx output-sap-delay delay

SAP updates sent on single interface

Adjust the interpacket delay of multiple-packet ipx triggered-sap-delay delay

triggered SAP updates sent on single

interface

To adjust SAP update timers on global basis eliminating the need to configure delays on

per-interface basis perform any or all of the following tasks in global configuration mode

Task Command

Adjust the interpacket delay of multiple-packet ipx default-output-sap-delay delay

SAP updates sent on all interfaces

Adjust the interpacket delay of multiple-packet ipx default-triggered-sap-delay delay

triggered SAP updates sent on all interfaces

By default the SAP entry of network or server ages out at an interval equal to three times the SAP

update interval To configure the multiplier that controls the interval perform the following task in

interface configuration mode

Task Command

Configure the interval at which networks or ipx sap-multiplier multiplier

servers SAP entry ages out

Configure SAP Update Packet Size

By default the maximum size of SAP updates sent out an interface is 480 bytes This size allows for

servers 64 bytes each plus 32-byte IPX SAP header To modify the maximum packet size

perform the following task in interface configuration mode

Task Command

Configure the maximum packet size of SAP ipx sap-max-packetsize bytes

updates sent out an interface

Configuring Novell IPX P2C-139 Tune IPX Network Performance

Enable SAP-after-RIP

The IPX SAP-after-RIP feature links Service Advertisement Protocol SAP updates to Routing Information Protocol RIP updates so that SAP broadcast and unicast updates automatically occur

immediately after the completion of the corresponding RIP update This feature ensures that

remote router does not reject service information because it lacks valid route to the service As

result of this feature periodic SAP updates are sent at the same interval as RIP updates

The default behavior of the router is to send RIP and SAP periodic updates with each using its own

update interval depending on the configuration In addition RIP and SAP periodic updates are

jittered slightly such that they tend to diverge from each other over time This feature synchronizes SAP and RIP updates

Benefits of SAP-after-RIP

Sending all SAP and RIP information in single update reduces bandwidth demands and eliminates

erroneous rejections of SAP broadcasts

Linking SAP and RIP updates populates the remote routers service table more quickly because

services will not be rejected due to the lack of route to the service This can be especially useful on

WAN circuits where the update intervals have been greatly increased to reduce the overall level of

periodic update traffic on the link

Send SAP Update after RIP Broadcast

To configure the router to send SAP update following RIP broadcast perform the following task

in interface configuration mode

Task Command

Configure the router to send SAP broadcast ipx update sap-after-rip

immediately following RIP broadcast

Disable Sending of General RIP or SAP Queries

You can disable the sending of general RIP and/or SAP queries on link when it first comes up to

reduce traffic and save bandwidth

RIP and SAP general queries are normally sent by remote routers when circuit first comes up On

WAN circuits two full updates of each kind are often sent across the link The first update is full

broadcast update triggered locally by the link-up event The second update is specific unicast

reply triggered by the general query received from the remote router By disabling the sending of

general queries when the link first comes up it is possible to reduce traffic to single update and

save bandwidth

To disable the sending of general RIP and/or SAP query when an interface comes up perform the

following task in interface configuration mode

Task Command

Disable the sending of general RIP and/or no ipx linkup-request rip sap

SAP Query when an interface comes up

the of RIP SAP the form of the command To re-enable sending general and/or query use positive

P2C-140 Network Protocols Configuration Guide Part Tune IPX Network Performance

to GNS ResPonses Requests trol Qofl in which the router to can set the You can set the method responds SAP GNS requests you delay these time in responding to these requests or you can disable the sending of responses to requests

altogether

to GNS if For if local server with By default the router responds requests appropriate example the router does not to the on that better metric exists then respond GNS request segment

The default method of responding to GNS requests is to respond with the server whose availability

was learned most recently

both of the tasks in To control responses to GNS requests perform one or following global

configuration mode

Task Command

round-robin Respond to GNS requests using ipx gns-round-robin

selection method

to GNS Set the delay when responding ipx gns-response-delay

requests

command is also as an interface Note The ipx gns-response-delay supported configuration

command To override the global delay value for specific interface use the

command in interface mode ipx gns-response-delay configuration

You can also disable GNS queries on per-interface basis To do so perform the following task from

interface configuration mode

Task Command

Disable the sending of replies to GNS queries ipx gns-reply-disable

Configure Load Sharing round-robin load described in the You can configure IPX to perform or per-host sharing as following

sections

Enable Round-Robin Load Sharing

Enable Per-Host Load Sharing

Enable Round-Robin Load Sharing destination that when You can set the maximum number of equal-cost parallel paths to Note

have costs the Cisco 105 software chooses lower-cost routes in preference to paths differing The software then distributes on basis in round-robin higher-cost routes output packet-by-packet the second the second fashion That is the first packet is sent along first path the packet along path

the the the and so on When the final path is reached the next packet is sent to first path next to

fast is second path and so on This round-robin scheme is used regardless of whether switching enabled

of can save on routers with limited or Limiting the number equal-cost paths memory memory very in networks with number of and large configurations Additionally large multiple paths systems

traffic is with limited ability to cache out-of-sequence packets performance might suffer when split between many paths

Configuring Novell IPX P2C-141 Tune IPX Network Performance

To set the maximum number of the paths perform following task in global configuration mode

Task Command

Set the maximum number of equal-cost paths ipx maximum-paths paths to destination

Enable Per-Host Load Sharing

Round-robin load is the default sharing behavior when you configure ipx maximum-pathsto value greater than Round-robin load works data sharing by sending packets over successive equal cost paths without regard to individual end hosts or sessions Path user utilization is good but because destined for end packets given host may take different paths they might arrive out of order

You can address the of out of order possibility packets arriving by enabling per-host load sharing With per-host load the router still uses sharing multiple equal-cost paths to achieve load sharing

however packets for end host are to take the given guaranteed same path even if multiple

equal-cost paths are available Traffic for different end hosts tend to take different paths but true load balancing is not The exact of load guaranteed degree balancing achieved depends on the exact nature of the woridoad

To enable per-host load the sharing perform following tasks in global configuration mode

Task Command

Set the maximum number of Step equal ipx maximum-paths paths

cost paths to destination to value

greater than

Step Enable per-host load sharing ipx per-host-load-share

Specify the Use of Broadcast Messages

You can the use of broadcast specify messages as described in the following sections

Use Helper Addresses to Forward Broadcast Packets

Enable Fast Switching of IPX Directed Broadcast Packets

Use Helper Addresses to Forward Broadcast Packets

Routers normally block all broadcast and do requests not forward them to other network segments This is done to the of prevent degradation performance over the entire network However you can enable the router to forward broadcast packets to helper addresses on other network segments

How Helper Addresses Work

addresses the Helper specify network and node on another that segment can receive unrecognized broadcast packets broadcast Unrecognized packets are non-RIP and non-SAP packets that are not addressed to the local network

When the interface with addresses configured helper receives unrecognized broadcast packet Cisco lOS software changes the broadcast to unicast and sends the packet packet to the specified network and node on the other network segment Unrecognized broadcast packets are not flooded everywhere in your network

With helper addresses there is no limit the on number of hops that the broadcast packet can make

P2C-142 Network Protocols Configuration Guide Part Tune IPX Network Performance

Fast Switching Support

broadcast Cisco lOS supports fast switching of helpered packets

When to Use Helper Addresses

broadcast 20 to You use helper addresses when you want to forward packets except type packets

other network segments

useful when network does Forwarding broadcast packets to helper addresses is sometimes segment You the not have an end-host capable of servicing particular type of broadcast request can specify

address of server network or networks that can process the broadcast packet

Relationship between Helper Addresses and Type 20 Propagation

to forward 20 to other network For You use type 20 packet propagation type packets segments

information on forwarding type 20 packets see the Control the Forwarding of Type 20 Packets

section in this chapter

You can use helper addresses and type 20 propagation together in your network Use helper

addresses to forward non-type 20 broadcast packets and use type 20 propagation to forward type 20

broadcast packets

Implementation Considerations

it does allow routers to forward broadcast Using helper addresses is not Novell-compliant however

the network It also allows packets to network segments that can process them without flooding

to forward 20 routers running versions of Cisco lOS that do not support type 20 propagation type

packets

referred to all-nets The Cisco lOS software supports all-networks flooded broadcasts sometimes as flooding These are broadcast messages that are forwarded to all networks Use all-nets flooding

be overwhelmed to the carefully and only when necessary because the receiving networks may point

that no other traffic can traverse them

lists that control Use the ipx helper-list command described earlier in this chapter to define access

which broadcast packets get forwarded

Use Helper Addresses

task in interface To specify helper address for forwarding broadcast packets perform the following

configuration mode

Task Command

ode Specify helper address for forwarding ipx helper-address network.n

broadcast messages

You can specify multiple helper addresses on an interface

Facilities For an example of using helper addresses to forward broadcast messages see the Helper

to Control Broadcast Examples section at the end of this chapter

Configuring Novell IPX P2C-143 Tune IPX Network Performance

Enable Fast Switching of IPX Directed Broadcast Packets

By default Cisco lOS software switches packets that have been helpered to the broadcast address

To enable fast switching of these IPX-directed broadcast packets perform the following task in

global configuration mode

Task Command

Enable fast switching of IPX directed broadcast ipx broadcast-fastswitching

packets

Disable IPX Fast Switching

By default fast switching is enabled on all interfaces that support fast switching However you

might want to turn off 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 traiisfer is performance generally better when fast switching is enabled However you might

disable fast in want to switching order to save memory space on interface cards and to help avoid

congestion when high-bandwidth interfaces are writing large amounts of information to low-bandwidth interfaces

Caution Turning off fast switching increases system overhead

To disable IPX fast switching perform the following task in interface configuration mode

Task Command

Disable IPX fast switching no ipx route-cache

Adjust the Route Cache

Adjusting the route cache allows you to control the size of the route cache reduce memory

consumption and improve router performance You accomplish these tasks by controlling the route

cache size and invalidation The following sections describe these optional tasks

Control Route Cache Size

Control Route Cache Invalidation

Control 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

too entries in the route cache Storing many can use significant amount of router memory causing

router processing to slow This situation is most common on large networks that run network

management applications for NetWare

For example if network management station is responsible for managing all clients and servers in

very large greater than 50000 nodes Novell network the routers on the local segment can become inundated with route cache entries You can set maximum number of route cache entries

on these routers to free up router memory and aid router processing

P2C-144 Network Protocols Configuration Guide Part Tune IPX Network Performance

To set maximum limit on the number of entries in the IPX route cache complete this task in global

configuration mode

Task Command

Set maximum limit on the number of entries ipx route-cache max-size size

in the IPX route cache

If the route cache has more entries than the specified limit the extra entries are not deleted However

they may be removed if route cache invalidation is in use See the Control Route Cache

Invalidation section in this chapter for more information on invalidating route cache entries

Control Route Cache Invalidation

You can configure the router to invalidate fast switch cache entries that are inactive If these entries

the the entries from the route cache remain invalidated for one minute router purges

size the reduces and Purging invalidated entries reduces the of route cache memory consumption

entries cache information improves router performance Also purging helps ensure accurate route

entries be inactive before the router You specify the period of time that valid fast switch cache must

invalidates them You can also specify the number of cache entries that the router can invalidate per minute

this task in To configure the router to invalidate fast switch cache entries that are inactive complete

global configuration mode

Task Command

Invalidate fast switch cache entries that are ipx route-cache inactivity-timeoutperiod

inactive

max-size When you use the ipx route-cache inactivity-timeout command with the ipx route-cache command you can ensure small route cache with fresh entries

Adjust Default Routes

You can adjust the use of default routes in your IPX network You can turn off the use of network

number -2 as the default route You can also specify that the router advertise only default RIP routes

out an interface The following sections describe these optional tasks

Disable Network Number -2 as the Default Route

Advertise Only Default RIP Routes

Disable Network Number -2 as the Default Route

destination network is unknown All for which The default route is used when route to any packets

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 an introduction to default routes see the IPX Default Routes section in this chapter For more

background information on how to handle IPX default routes refer to Novells NetWare Link

Services Protocol NLSP Specification Revision 1.1

By default Cisco 105 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

Configuring Novell IPX P2C-145 Shut Down an IPX Network

To disable the use of network number -2 as the default route perform the following task in global configuration mode

Task Command

Disable default route handling no ipx default-route

Advertise Only Default RIP Routes

Unless configured otherwise all known RIP routes are advertised out each interface However you

can choose to advertise the default RIP route if it is only known This greatly reduces the CPU overhead when routing tables are large

To advertise the default route via only an interface perform the following task in interface configuration mode

Task Command

Advertise the default RIP only route ipx advertise-default-route-only network

Pad Odd-Length Packets

Some IPX end hosts accept only even-length Ethernet packets If the length of packet is odd the

packet must be padded with an extra so that end host receive it byte can By default Cisco lOS pads odd-length Ethernet packets

However there are cases in certain where topologies non-padded Ethernet packets are being forwarded onto remote Ethernet network Under specific conditions you can enable padding on

intermediate media as workaround for this temporary problem Note that you should perform this task under the of only guidance customer engineer or other service representative

To enable the padding of the odd-length packets perform following tasks in interface configuration mode

Task Command

Disable Step fast switching no ipx route-cache

Enable the of Step padding odd-length ipx pad-process-switched-packets packets

Shut Down an PX Network

You can administratively shut down an IPX network in In the first the two ways way network still

exists in the but is not active When configuration shutting down the network sends out update

packets its that it is informing neighbors shutting down This allows the neighboring systems to their update routing SAP and other tables without having to wait for routes and services learned via this network to time out

To shut down an IPX network such that the network still exists in the configuration perform the following task in interface configuration mode

Task Command

Shut down an 1PX network but have the ipx down network

network still exist in the configuration

P2C-146 Network Protocols Configuration Guide Part Configure IPX Accounting

the To do In the second way you shut down an IPX network and remove it from configuration this perform one of the following tasks in interface configuration mode

Task Command

Shut down an IPX network and remove it from no ipx network

the configuration

When multiple networks are configured on an no ipx network network

interface shut down all networks and remove where network is the primary interface

them from the interface

When multiple networks are configured on an no ipx network network of the interface interface shut down one of the secondary where network is the number secondary

networks and remove it from the interface

interface and shut down of the When multiple networks are configured on an you want one secondary

networks and remove it from the interface perform the second task in the previous table specifying

the network number of one of the secondary networks

be Note In future Cisco lOS software releases primary and secondary networks will not supported

For an example of shutting down an IPX network see the IPX Routing Examples section at the

end of this chapter

Configure IPX Accounfing

information about IPX and the number of that IPX accounting enables you to collect packets bytes

collect information based the source and are switched through the Cisco lOS software You on

destination IPX address IPX accounting tracks only IPX traffic that is routed out an interface on

traffic terminated at the router which IPX accounting is configured it does not track generated by or

itself

The Cisco lOS 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 cleared its contents are copied to the checkpoint database Using these two

traffic that has databases together enables you to monitor both current traffic and previously

traversed the router

Switching Support

do not Process and fast switching support IPX accounting statistics Autonomous and SSE switching

statistics support IPX accounting

Access List Support

IPX access lists support IPX accounting statistics

Configuring Novell IPX P2C-147 Monitor and Maintain the IPX Network

IPX Accounting Task List

You can IPX configure accounting by completing the tasks in the following sections The first task

is required The remaining tasks are optional

Enable IPX Accounting

Customize IPX Accounting

Monitor and Maintain IPX Accounting

Enable IPX Accounting

To enable IPX the accounting perform following task in interface configuration mode

Task Command

Enable IPX accounting ipx accounting

Customize IPX Accounting

To customize IPX of the accounting perform one or more following tasks in global configuration mode

Task Command

Set the maximum number of accounting ipx accounting-threshold threshold

entries

Set the maximum number of transit entries ipx accounting-transits count

Filter networks for which IPX accounting ipx accounting-list number mask

information is kept Enter one command for each network

Transit entries are entries in the database that do not match any of the networks specified by the ipx accounting-list commands

If enable IPX interface you accounting on an but do not specify an accounting list IPX accounting

tracks all traffic the interface through all transit entries up to the accounting threshold limit

For an of how to IPX example configure accounting see the IPX Accounting Example section at the end of this chapter

Monitor and Maintain the PX Network

You can monitor and maintain your IPX network by performing the optional tasks described in the following sections

Perform General Monitoring and Maintaining Tasks

Monitor and Maintain IPX Enhanced IGRP

Monitor and Maintain NLSP

Monitor and Maintain NHRP

Monitor and Maintain IPX Accounting

P2C-148 Network Protocols Configuration Guide Part Monitor and Maintain the IPX Network

Perform General Monitoring and Maintaining Tasks

You can perform one or more of these general monitoring and maintaining tasks as described in the

following sections

Monitor and Maintain Caches Tables Interfaces and Statistics

of Packets Specify the Tpe and Use Ping

Numbers Repair Coirupted Network

Monitor and Maintain Caches Tables Interfaces and Statistics

To monitor and maintain caches tables interfaces or statistics in Novell IPX network perform

one or more of the following tasks at the EXEC prompt

Task Command

Delete all entries in the IPX fast-switching clear ipx cache

cache

Delete entries in the IPX routing table clear ipx route

List the entries in the IPX fast-switching cache show ipx cache

Display the status of the IPX interfaces show ipx interface number

configured in the router and the parameters

configured on each interface

List the entries in the IPX routing table show ipx route

sorted net List the servers discovered through SAP show ipx servers type

advertisements name

Display information about the number and type show ipx traffic

of IPX packets transmitted and received

Display summary of SSP statistics show sse summary

Specify the Type and Use of Ping Packets

The Cisco lOS software can transmit Cisco pings or standard Novell pings as defined in the NLSP Cisco To choose the the specification By default the software generates pings ping type perform

following task in global configuration mode

Task Command

Select the ping type ipx ping-default cisco novell

To initiate ping perform one of the following tasks in EXEC mode

Task Command

Diagnose basic IPX network connectivity ping ipx network.node

user-level command

Diagnose basic IPX network connectivity ping

privileged command

Configuring Novell IPX P2C-149 Monitor and Maintain the IPX Network

Repair Corrupted Network Numbers

To repair corrupted network numbers on an interface perform the following tasks in interface

configuration mode

Task Command

Step Disable fast switching no ipx route-cache

Step Repair corrupted network numbers ipx source-network-update

Caution The ipx source-network-update interface configuration command interferes with the

proper working of OS/2 Requestors Do not use this command in network that has OS/2 Requestors

Caution Do the not use ipx source-network-update interface configuration command on

interfaces which on NetWare servers are using internal network numbers that is all NetWare lx 4.x and NetWare IntraNetWare servers

Monitor and Maintain IPX Enhanced IGRP

To monitor and maintain Enhanced IGRP on an IPX network perform one or more of the following tasks at the EXEC prompt

Task Command

List the neighbors discovered by iPX Enhanced show ipx eigrp neighbors IGRE interface

information about Display interfaces show ipx eigrp interfaces

configured for Enhanced IGRE

the of Display contents the IPX Enhanced show ipx eigrp topology IGRP topology table

the of the Display contents IPX routing table show ipx route

including Enhanced IGRP entries

Display information about IPX traffic show ipx traffic

including Enhanced IGRP traffic

Log Enhanced IGRP Neighbor Adjacency Changes

You enable the of can logging neighbor adjacency changes to monitor the stability of the routing

and to detect system help you problems By default adjacency changes are not logged

To enable of Enhanced logging IGRP neighbor adjacency changes perform the following task in

global configuration mode

Task Command

Enable logging of Enhanced IGRP neighbor log-neighbor-changes adjacency changes

P2C-150 Network Protocols Configuration Guide Part Monitor and Maintain the IPX Network

Monitor and Maintain NLSP

To monitor and maintain NLSP on an IPX network perform one or more of the following tasks at

the EXEC prompt

Task Command

Delete all NLSP adjacencies from the clear ipx nlsp neighbors

adjacency database

Display the entries in the linkstate packet show ipx nlsp database LSP database

Display the devices NLSP neighbors and their show ipx nlsp neighbors

states

Display history of the SPF calculations for show ipx nlsp spf-log NLSP

Log Adjacency State Changes

state You can allow NLSP to generate log message when an NLSP adjacency changes up or networks the down This may be very useful when monitoring large Messages are logged using form system error message facility Messages are of the following

%CLNS-5-ADJCHANGE NLSP Adjacency to 0000.0000.0034 SerialO Up new adjacency %CLNS-5-ADJCHANGE NLSP Adjacency to 0000.0000.0034 SerialO Down hold time expired

the task in To generate log messages when an NLSP adjacency changes state perform following

router configuration mode

Task Command

Log NLSP adjacency state changes log-adjacency-changes

Monitor and Maintain NHRP

To monitor the NHRP cache or traffic perform either of the following tasks in EXEC mode

Task Command

Display the IPX NHRP cache optionally limited to show ipx nhrp static number

dynamic or static cache entries for specific

interface

Display NHRP traffic statistics show ipx nhrp traffic

The NHRP cache can contain static entries caused by statically configured addresses and dynamic

entries caused by the Cisco lOS software learning addresses from NHRP packets To clear static cache of entries use the no ipx nhrp map command To clear the NHRP dynamic entries perform

the following task in EXEC mode

Task Command

Clear the IPX NIHRP cache of dynamic entries clear ipx nhrp

Configuring Novell IPX P2C-151 Novell IPX Configuration Examples

Monitor and Maintain IPX Accounting

To monitor and maintain IPX in IPX accounting your network perform the following tasks in EXEC mode

Task Command

Delete all entries in the IPX accounting or clear ipx accounting

accounting checkpoint database

List the entries in the IPX accounting or show ipx accounting

accounting checkpoint database

NoveD PX Configuraflon Exampes

This section provides configuration examples for the following IPX configuration situations

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

This section shows for examples enabling IPX routing on interfaces with single network and with

networks It also shows how enable multiple to and disable various combinations of routing protocols

The following sections contain 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 following configuration commands enable IPX routing defaulting the IPX host address to that

of the first IEEE-conformance interface in this example Ethernet Routing is then enabled on Ethernet and Ethernet for IPX networks 2abc and ldef respectively

ipx routing interface ethernet ipx network 2abc interface ethernet ipx network idef

P2C-152 Network Protocols Configuration Guide Part Novell IPX Configuration Examples

IPX Routing on Multiple Networks Examples

There are two ways to enable IPX on an interface that supports multiple networks You can use

subinterfaces or primary and secondary networks This section gives an example of each

Subinterfaces Example

The following example uses subinterfaces to create four logical networks on Ethernet interface

Each subinterface has different encapsulation Any interface configuration parameters that you

specify on an individual subinterface are applied to that subinterface only

ipx routing interface ethernet 0.1

ipx network encapsulation novellether 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 enabling NLSP and configuring multiple encapsulations on the same physical LAN

interface you must use subinterfaces You cannot use secondary networks

You can administratively shut down each of the four subinterfaces separately by using the shutdown

interface configuration command for each subinterface For example the following commands

administratively shut down subinterface

interface ethernet 0.3 shutdown

To bring down network use the following commands

interface ethernet 0.1

ipx down

To bring network back 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

Configuring Novell IPX P2C-153 Novell IPX Configuration Examples

Primary and Secondary Networks Example

Note The following examples discuss primary and secondary networks In future Cisco lOS software releases primary and secondary networks will not be supported Use subinterfaces

The following example uses primary and secondary networks to create the same four logical

networks as shown earlier in this section interface Any configuration parameters that you specify on

this interface all are applied to the logical networks For example if you set the routing update timer

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

this Using method to configure logical networks if you administratively shut down Ethernet

interface the interface using shutdown configuration command all four logical networks are shut

down You cannot bring down each logical network independently using the shutdown command however you can do this using the ipx down command

To shut down network use the following command

interface ethernet

ipx down

To bring the network back up use the following command

interface ethernet

no ipx down

To shut down all four networks on the interface and remove all the networks on the interface use one

of the following interface configuration commands

no ipx network

To of the remove one secondaiy networks on the interface in this case network use the following

interface configuration command

no ipx network

The following example enables IPX routing on FDDI interfaces 0.2 and 0.3 On FDDI interface

the is 0.2 encapsulation type SNAP On FDDI interface 0.3 the encapsulation type is Novells FDDI_RAW

ipx routing interface fddi 0.2

ipx network f02 encapsulation snap interface fddi 0.3 ipx network f03 encapsulation novell-fddi

P2C-154 Network Protocols Configuration Guide Part Novell IPX Configuration Examples

IPX Routing Protocols Examples

Three routing protocols can run over interfaces configured for IPX RIP Enhanced IGRP and NLSP This section of how provides examples to enable and disable various combinations of routing

protocols

When enable IPX with the you routing ipx routing global configuration command the RIP routing

protocol is automatically enabled The following example enables RIP on networks and

ipx routing

interface ethernet

ipx network

interface ethernet

ipx network

The following example enables 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 enables 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 configures NLSP on two of routers Ethernet interfaces Note that RIP is

automatically enabled on both of these interfaces This example assumes that the encapsulation type

is Ethernet 802.2

ipx routing ipx internal-network

ipx router nlsp areal areaaddress

interface ethernet

ipx network eQ encapsulation sap ipx nlsp areal enable

interface ethernet

ipx network el encapsulation sap ipx nlsp areal enable

Configuring Novell IPX P2C-155 Novell IPX Configuration Examples

Enhanced IGRP Examples

This section shows several examples for configuring IPX Enhanced IGRP routing The following sections contain these examples

IPX Enhanced IGRP Example

Enhanced IGRP SAP Update Examples

Advertisement and Processing of SAP Update Examples

IPX Enhanced IGRP Bandwidth Configuration Example

IPX Enhanced IGRP Example

The following example configures two interfaces for Enhanced IGRP routing in autonomous

system

ipx routing

interface ethernet

ipx network 10

interface serial

ipx network 20

ipx router eigrp network 10 network 20

Enhanced IGRP SAP Update Examples

If an Ethernet interface has neighbors that are all configured for Enhanced IGRP you might want to

reduce the bandwidth used by SAP packets by sending SAP updates incrementally To do this you

would configure the interface as follows

ipx routing

interface ethernet

ipx network 10 ipx sap-incremental eigrp

interface serial

ipx network 20

ipx router eigrp network 10 network 20

If you want to send only incremental SAP updates on serial line that is configured for Enhanced

IGRP but periodic RIP updates use the following commands

ipx routing

interface ethernet

ipx network 10

interface serial

ipx network 20 ipx sap-incremental eigrp rsup-only

ipx router eigrp network 10

P2C-156 Network Protocols Configuration Guide Part Novell IPX Configuration Examples

network 20

Advertisement and Processing of SAP Update Examples

The following example causes only services from network to be advertised by an Enhanced IGRP

routing process

accesslist 1010 permit accesslist 1010 deny -l

ipx router eigrp 100 network distribute-saplist 1010 out

In the following example the router redistributes Enhanced IGRP into NLSP area Only services

for networks and are accepted by the NLSP routing process

access-list 1000 permit access-list 1000 permit access-list 1000 deny -l

ipx router nlsp areal redistribute eigrp distributesaplist 1000 in

IPX Enhanced IGRP Bandwidth Configuration Example

The following example shows how to configure the bandwidth used by IPX Enhanced IGRP In this

example Enhanced IGRP process 109 is configured to use maximum of 25 percent or 32 kbps of

128 kbps circuit

interface serial bandwidth 128

ipx bandwidth-percent eigrp 109 25

In the following example the bandwidth of 56 kbps circuit has been configured to be 20 kbps for

The Enhanced IGRP 109 is routing policy reasons process configured to use maximum of 200

percent or 40 kbps of the circuit

interface serial bandwidth 20

ipx bandwidth-percent eigrp 109 200

NLSP Examples

This section shows several examples for configuring NSLP The following sections contain these examples

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

Configuring Novell IPX P2C-157 Novell IPX Configuration Examples

NLSP Multicast Addressing Examples

By default NLSP multicast addressing is enabled You do not need to configure anything to turn on

NLSP multicasting

1pically you do 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

disable it for want to testing purposes

If you want to disable NLSP multicast addressing you can do so for the entire router or for

particular interface

The following sections provide sample configurations for disabling multicast addressing

Disable NLSP Multicasting on the Router Example

Disable NLSP Multicasting on an Interface Example

Disable NLSP Multicasting on the Router Example

The following example disables multicast addressing on the router

ipx router nlsp no multicast

Disable NLSP Multicasting on an Interface Example

The following example disables multicast addressing on Ethernet interface 1.2

interface ethernetl .2

no ipx nlsp multicast

Enhanced IGRP and NLSP Route Redistribution Example

The following example configures router to redistribute NLSP into Enhanced IGRP autonomous

system 100 and Enhanced IGRP autonomous system 100 into NILSP

ipx router eigrp 100 redistribute nlsp

ipx router nlsp redistribute eigrp 100

NLSP Route Aggregation for Multiple NLSP Version .1 Areas Example

The following example shows the route aggregation configuration for router connecting multiple

NLSP version 1.1 areas In this example the two areas are area 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 interna1network 2000

interface ethernet

P2C-158 Network Protocols Configuration Guide Part Novell IPX Configuration Examples

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 .1 and Version .0 Areas Example

customized route The following example configures the route aggregation feature with

is version 1.1 summarization In this example area is an NLSP version 1.0 area and area2 an NLSP

learned in that fall in the of are redistributed area Any explicit routes area range aaaa0000ffff0000

in that into area2 as an aggregated route Explicit routes from area that do not fall range are

redistributed into area2 as an explicit route

learned in area2 Because area is an NLSP version 1.0 area it cannot accept aggregated routes

into the router sends routes instead of Thus when redistribution area occurs explicit 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

accesslist 1200 deny aaaa0000 ffff0000 access-list 1200 permit -l

ipx router nlsp areal areaaddress 1000 fffff000

ipx router nlsp area2 area-address 2000 fffff000 route-aggregation redistribute nlsp areal access-list 1200

NLSP Route Aggregation for NLSP Version .1 Enhanced IGRP and RIP Example Enhanced IGRP In the following example the router connects two NLSP version 1.1 areas one area

and one 1UP area

redistributed into Any routes learned via NLSP that are represented by aaaa0000ffff0000 are not learned via NLSP a2 as explicit routes Instead the router generates an aggregated route Any routes into NLSP a2 that are represented by bbbb0000ffff0000 are not redistributed as explicit routes NLSP

that Again the router generates an aggregated route Any routes learned via RIP are represented redistributed into or a2 Instead the by cccc0000ffff0000 are not as explicit routes NLSP NLSP

Configuring Novell IPX P2C-159 Novell IPX Configuration Examples

router sends an aggregated route Likewise any routes learned via Enhanced IGRP 129 that are

represented by dddd0000ffff0000 are not redistributed into NLSP or NLSP a2 Again the router

sends 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

interface ethernet ipx network dddd0000

accesslist 1200 deny aaaa0000 ffff0000 access-list 1200 permit

accesslist 1201 deny bbbb0000 ffff0000 accesslist 1201 permit

accesslist 1202 deny cccc0000 ffff0000 accesslist 1202 permit

accesslist 1203 deny dddd0000 ffff0000 accesslist 1203 permit

ipx router nlsp al areaaddress 10000 fffff000 routeaggregation redistribute nlsp a2 accesslist 1201 redistribute rip access-list 1202 redistribute eigrp 129 accesslist 1203

ipx router nlsp a2 areaaddress 2000 fffff000 route-aggregation redistribute nlsp al access-list 1200 redistribute rip accesslist 1202 redistribute eigrp 129 access-list 1203

ipx router eigrp 129 network dddd0000

redistribute nlsp al redistribute nlsp a2

NHRP Examples

This section shows examples for configuring NHRP The following sections contain these examples

NHRP Example

NHRP over ATM Example

P2C-160 Network Protocols Configuration Guide Part Novell IPX Configuration Examples

NHRP Example

logical NBMA network is considered the group of interfaces and hosts participating in NHRP and

having the same network identifier Figure 16 illustrates two logical NBMA networks shown as

circles configured over single physical NBMA network Router communicates with Routers

and because they share the same network identifier Router also communicates with

Routers and because they share network identifier After address resolution is complete

Router sends IPX packets to Router in one hop and Router sends them to Router in one

hop as shown by the dotted lines

Figure 16 Two Logical NBMA Networks over One Physical NBMA Network

ipx nhrp network-id ipx nhrp network-id ipx nhrp network-id

ipx nhrp network-id

Statically configured tunnel end points or permanent virtual circuits

Dynamically created virtual circuits

be that shown in 17 The physical configuration of the five routers in Figure 16 might actually Figure

The source host is connected to Router and the destination host is connected to Router The same

switch serves all five routers making one physical NBMA network

Configuring Novell IPX P2C-161 Novell IPX Configuration Examples

Figure 17 Physical Configuration of Sample NBMA Network

Refer to 16 before again Figure Initially NHRP resolves any NBMA addresses IPX packets from

the source host to the destination host travel through all five routers connected to the switch before

reaching the destination When Router first forwards the IPX packet toward the destination host Router also generates an NHRP request for the destination hosts IPX address The request is

forwarded Router where is to reply generated Router replies because it is the egress router

between the two logical NBMA networks

Router Similarly generates an NHRP request of its own to which Router replies In this

example subsequent IPX traffic between the source and the destination still requires two hops to the network because traverse NBMA the IPX traffic must be forwarded between the two logical networks NBMA Only one hop would be required if the NBMA network was not logically divided

NHRP over ATM Example

The following example shows configuration of three routers using NHRP over ATM Router is

configured with static route which it uses to reach the IPX network where Router resides Router

initially reaches Router through Router Router and Router directly communicate without

Router once NRRP resolves Router As and Router Cs respective NSAP addresses

P2C-162 Network Protocols Configuration Guide Part Novell IPX Configuration Examples

The significant portions of the configurations for Routers and follow

Router

interface ATMO/0 map-group atm nsapaddress l1.1lll.llllllll.1l111l11llllllllllllflflfl atm rate-queue 10 atm PVC qsaal ipx network ipx nhrp network-id

map-list ipx l.00000c153588 atm-nsap 33.333333.33333333333333.3333.33333333333333

ipx route l.0000.0c15.3588

Router

interface ATMO/0 map-group atm nsapaddress 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 33.3333.33.333333.3333.333333333333.3333.3333.33

ipx route 2.0000.0c153628

Router

interface ATMO/0 atm rate-queue 10 atm pvc qsaal

interface ATMO/0.l multipoint map-group atm nsap-address 33.3333.33.3333333333.3333333333333333333333 ipx network ipx nhrp network-id

interface ATMO/0.2 multipoint map-group atm nsapaddress 33.3333.33.333333.3333.3333333333333333333333 ipx network ipx nhrp network-id

map-list ipx l.0000.0c15.4f80 atm-nsap ll.llll.ll.llllllllllllllllll.llll.llllllll.ll

map-list ipx 2.0000.0c15.502l atm-nsap 22.2222.22.2222222222.2222.2222.2222.2222.2222.22

Configuring Novell IPX P2C-163 Novell IPX Configuration Examples

IPX over WAN Examples

This section shows examples for configuring IPX over WAN and dial interfaces The following sections contain these examples

IPX over WAN Interface Example

IPX over DDR Example

IPX over WAN Interface Example

When you configure the Cisco lOS software to transport IPX packets over serial interface that is running WAN protocol such as X.25 or PPP you specify how the packet will be encapsulated for

transport This 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 aWAN Interface

The following examples 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

interface serial 1.1 point-to-point

P2C-164 Network Protocols Configuration Guide Part Novell IPX Configuration Examnies

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.OcQ3.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.0c17d726 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 novefl 3.0000.Ocl7.d725 33333 BROADCAST

Configuring Novell IPX P2C-165 Novell IPX Configuration Examples

IPX over DDR Example

In the configuration shown in Figure 19 an IPX client is separated from its server by DDR

telephone line

Figure 19 IPX over DDR Configuration

Novell

Server-A client

Internal network 234 Network DDI

Network 152001

Routing and service information is sent every minute The output RIP and SAP filters defined in this

example filter these updates preventing them from being sent between Routers and If you were

to forward these packets the two routers would each have to telephone the other once minute On

serial link that charges based on the number of packets transmitted this is generally not desirable

This might not be an issue on dedicated serial line

Once the server and client have established contact the server will send keepalive watchdog

packets regularly When SPX is used both the server and the client send keepalive packets The

purpose of these packets 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 you were to allow Router to forward the servers keepalive packets to Router Router would

have to telephone Router every minutes just to send these packets Again on serial link that

charges based on the number of packets transmitted this is generally not desirable Instead of having

Router telephone Router only to send keepalive packets you can enable watchdog spoofing on

Router This way when the server connected to this router sends keepalive packets Router will

respond on behalf of the remote client the client connected to Router When SPX is used you

must enable spoofing of SPX keepalive packets on both Router and Router to inhibit the sending

of them because both the server and the client send keepalive packets

Configuration for Router

novell routing 0000.0c04.4878

interface Ethernet0 novell network 15200

interface SerialO ppp encap for DDRrecommended encapsulation ppp novell network DD1DD2

kill all rip updates novell output-network-filter 801 kill all sap updates novell output-sap-filter 1001 fast-switching off for watchdog spoofing no novell routecache

dont listen to rip

P2C-166 Network Protocols Configuration Guide Part Novell IPX Configuration Examples

novell router-filter 866 novell watchdog spoof ing novell watchdog-spoof SPX watchdog spoof ing

ipx spx-spoof turn on ODR dialer in-band dialer idle-timeout 200 dialer map IP 198.92.96.132 name R13 7917 dialer map NOVELL OD1002.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 FFFFFFFF 452 FFFFFFFF 452 permit everything else access-list 900 permit -l FFFFFFFF FFFFFFFF

access-list 1001 deny FFFFFFFF

static novell route for remote network novell route OD1 OO1DO2.0000.0c03.e3c3

IPX will trigger the line up 9.21 and later dialer-list list 900

Configuration for Router

novell routing 0000.0c03.e3c3

interface Ethernetl/0 novell network DD1

interface Serial2/0 encapsulation ppp novell network DD1DO2 novell output-network-filter 801 novell output-sap-filter 1001 no novell route-cache novell router-filter 866

ipx spx-spoof dialer in-band dialer idle-timeout 200 dialer map IP 198.92.96.129 name R5 7919 dialer map NOVELL DO1002.0000.0c04.4878 7919 dialer-group ppp authentication chap pulse-time

Configuring Novell IPX P2C-167 Novell IPX Configuration Examples

accesslist 801 deny -l accesslist 866 deny accesslist 900 deny FFFFFFFF FFFFFFFF 457 accesslist 900 deny FFFFFFFF 453 FFFFFFFF 453 accesslist 900 deny FFFFFFFF 452 FFFFFFFF 452 accesslist 900 permit -l FFFFFFFF FFFFFFFF accesslist 1001 deny FFFFFFFF

static novell route for servers internal network novell route 1234 DD1DD2.0000.0c04.4878 novell route 15200 DD1DD2.0000.0c04.4878 static route

The following line is the static novell sap required to get to the remote server It informs the router of the next hop novell sap CE1LAB 1234.0000.0000.0001 451

dialer-list list 900

IPX Network Access Examples

This section contains examples for controlling access to your IPX network It shows the

configurations for various access lists and filters The following sections contain these examples

IPX Network Access Example

Standard Named Access List Example

SAP Input Filter Example

SAP Output Filter Example

IPX NetBIOS Filter Examples

IPX Network Access Example

Using access lists to manage traffic routing is powerful tool in overall network control However

it requires certain amount of planning and the appropriate application of several related commands

Figure 20 illustrates network featuring two routers on two network segments

Figure 20 Novell IPX Servers Requiring Access Control

Router Router

EO SO So El EO

Novell Novell

client client

aaOl .0000.0000.001 bbOl .0000.0000.001

Suppose you want to prevent clients and servers on Network aa from using the services on Network but allow the bb you want to clients and servers on Network bb to use the services on Network aa To do would need this you an access list on Ethernet interface on Router that blocks all packets

from Network aa and destined for Network You would need coming bb not any access list on Ethernet interface on Router

P2C-168 Network Protocols Configuration Guide Part Novell IPX Configuration Examples

You would configure Ethernet interface on Router with the following commands

ipx routing access-list 800 deny aa bbOl access-list 800 permit -l -l interface ethernet

ipx network bb ipx access-group 800

You the result the can accomplish same as previous example more efficiently For example you can

the filter Router place same output on interface serial Or you could also place an input filter on

interface Ethernet of Router as follows

ipx routing access-list 800 deny aa bbOl accesslist 800 permit interface ethernet

ipx network aa ipx access-group 800 in

Note When control list using access logging on an interface with fast switching turned on packets

that match the access list and thus need to be logged are slow switched not fast switched

Logging Access Control List Violations

You can keep log of all access control list violations by using the keyword log at the end of the access-list command as follows

access-list 907 deny 100 log

The denies and all that arrive at the router from in previous example logs packets any source any

protocol from any socket to any destination on network 100

The following is an example of log entry for the access-list command

%IPX6ACL 907 deny SPX B5A8 50.0000.0000.0001 B5A8 l00.0000.0000.000l 10 pkts

In this example 10 SPX packets were denied because they matched access list number 907 The

packets were coming from socket B5A8 on networks 50.0000.0000.0001 and were destined for socket B5A8 on network 100.0000.0000.0001

Standard Named Access List Example

The creates standard following example access list namedfred It denies communication with only IPX network number 5678

ipx access-list standard fred deny 5678 any permit any

SAP Input Filter Example

SAP filters allow input router to determine whether to accept information about service

Router illustrated in Cl 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

Configuring Novell IPX P2C-169 Novell IPX Configuration Examples

Figure 21 SAP Input Filter

Novell server NIC 080089A1.1527 3c01 .0000.0000.0001

Input SAP filter applied to interface EO

cc Novell server NIC 0800.89A0.6781 3c02.0000.0000.0001

aa 4d

Novell Novell Novell server server client NIC 0207.0104.0874 NIC 0800.1491.2207 0800.0123.1456 tO aaOl .0000.0000.0001 4d01 .0000.0000.0001

The following example configures Router Cl The first line denies server and the second line

accepts all other servers

accesslist 1000 deny 3c01.00000000.000l accesslist 1000 permit interface 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

access list commands the first configuration command in this example

SAP Output Filter Example

SAP filters output are applied prior to the Cisco 105 software sending information out specific

interface In the that example follows Router Cl illustrated in Figure 22 is prevented from

advertising information about Novell server out interface Ethernet but can advertise server on network 3c

P2C-170 Network Protocols Configuration Guide Part Novell IPX Configuration Examples

Figure 22 SAP Output Filter

Novell server NIC 0800.89A1.1527 3c01 .0000.0000.0001

Novell

client 1811 .89A2.1543

-i Novell server NIC 0800.89A0.6781 Output SAP 3c02.0000.0000.0001

filters applied to interface El aa 4d

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 following example refers to Router Cl The first line denies server All other servers are

permitted

accesslist 1000 deny aaOl.0000.0000.000l 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

IPX NetBIOS Filter Examples

filter NetBIOS frames The The following is an example of using NetBIOS host name to IPX

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.0c17.d45d

Configuring Novell IPX P2Cl71 Novell IPX Configuration Examples

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-2 0-propagation ipx netbios output-access-filter host token no mop enabled

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

The is of following an example using byte pattern to filter IPX NetBIOS frames This example

permits IPX NetBIOS frames from IPX network numbers that end in 05 This means that all IPX NetBIOS frames from Ethernet interface network 105 and FDDI interface network 305 will

be forwarded serial interface by 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.0c17.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

P2C-172 Network Protocols Configuration Guide Part Novell IPX Configuration Examples

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

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-20-propagation ipx netbios input-access-filter bytes finigan

Helper Facilities to Control Broadcast Examples

The following examples illustrate how to control broadcast messages on IPX networks The

following sections contain these examples

Forwarding to an Address Example

Forwarding to All Networks Example

All-Nets Flooded Broadcast Example

Note that in the following examples packet type is used This type has been chosen arbitrarily the

actual type to use depends on the specific application

Forwarding to an Address Example

All broadcast packets are normally blocked by the Cisco lOS software However type 20

propagation packets may be forwarded subject to certain loop-prevention checks Other broadcasts host The may be directed to set of networks or specific node on segment following examples

illustrate these options

Figure 23 shows router Cl connected to several Ethernet interfaces In this environment all IPX

clients are attached to segment aa while all servers are attached to segments bb and dd In

controlling broadcasts the following conditions are to be applied

Only type and type 20 broadcasts are to be forwarded

networks bb The IPX clients on network aa are allowed to broadcast via type to any server on and dd

network dd The IPX clients are allowed to broadcast via type 20 to any server on

Configuring Novell IPX P2C-173 Novell IPX Configuration Examples

Figure 23 IPX Clients Requiring Server Access through Router

Novefi

server 00b423cd.llOa

Novell

server Novell 0090.aa23.efOl server 0090.aa23.dlcO

The the following example configures router shown in Figure 23 The first line permits broadcast traffic of type from network aa The interface and network commands configure each specific interface The ipx helper-address commands permit broadcast forwarding from network aa to bb and from network to dd The aa helper list allows type broadcasts to be forwarded Note that

type broadcasts are chosen as an The actual to example only type use depends on the application

The ipx type-20-propagation command acts as specific permission to allow type 20 broadcasts to be forwarded between networks and aa dd is also required

access-list 900 permit aa interface ethernet

ipx network aa ipx type-2 0-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

This that configuration means any network that is downstream from network aa for example some network will be arbitrary aal not able to broadcast type to network bb through Router Cl unless the routers networks partitioning aa and aal are configured to forward these broadcasts with series

of entries configuration analogous to the example provided for Figure 23 These entries must be

applied to the interface and be set to forward broadcasts input between directly connected networks In this such traffic be way can passed along in directed manner from network to network similar

situation exists for type 20 packets

The rewrites following example the ipx helper-address interface configuration command line to direct broadcasts to server

ipx helper-address bb.00b4.23cd.llOa

Permits node-specific broadcast forwarding to Server at address 00b4.23cd.llQa on network bb

P2C-174 Network Protocols Configuration Guide Part Novell IPX Configuration Examples

Forwarding to All Networks Example

In some networks it might be necessary to allow client nodes to broadcast to servers on multiple

networks If you configure your router to forward broadcasts to all attached networks you are

flooding the interfaces In the environment illustrated in Figure 24 client nodes on network 2b must

obtain services from IPX servers on networks 3c2 4a1 and Sbb through Router Cl To support this

requirement use the flooding address -1 .ffff.ffff.ffff in your ipx helper-address interface

configuration command specifications

Figure 24 Type Broadcast Flooding

Novell

server

3c2

Allows broadcast

flooding from network 2b1

Novell

client

2b Then the first In the following example the first line permits traffic of type from network

is defined and the interface is configured with network number The all-nets helper address helper

2b1 forwarded to all list limits forwarding to type traffic.Tpe broadcasts from network are blocked To directly connected networks All other broadcasts including type 20 are permit enable the broadcasts delete the ipx helper-list entry To allow type 20 broadcast

ipx type-20-propagation interface configuration command on all interfaces

accesslist 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 4al interface ethernet

ipx network 5bb

Configuring Novell IPX P2C-175 Novell IPX Configuration Examples

All-Nets Flooded Broadcast Example

The all-nets following example configures flooding on an interface As result of this configuration

Ethernet interface will forward all broadcast messages except type 20 to all the networks it knows

how to reach This flooding of broadcast messages might overwhelm these networks with so much

broadcast traffic that other traffic be no may able to pass on them

interface ethernet

ipx network 23 ipx helper-address -l FFFF FFFF FFFF

IPX Accounting Example

The following example configures two Ethernet network segments that are connected via serial link On Router see Figure 25 IPX accounting is enabled on both the input and output interfaces that

Ethernet interface and is on serial interface This means that statistics are gathered for traffic

traveling in both directions that is out to the Ethernet network and out the serial link

On Router IPX accounting is enabled only on the serial interface and not on the Ethernet interface

This that statistics means are gathered only for traffic that passes out the router on the serial link

Also the threshold is accounting set to 1000 which means that IPX accounting will track all IPX

traffic the passing through router up to 1000 source and destination pairs

Figure 25 IPX Accounting Example

Network 200 Router SO E0

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

P2C-176 Network Protocols Configuration Guide Part index extended P2C-119

extended creating P2C-122 BC Bridging and IBM Networking Configuration implicit deny P2C-126 Guide implicit masks P2C-126 DC Dial Solutions Configuration Guide input P2C-121 named P2C-123 FC Configuration Fundamentals Configuration Guide NetBIOS

PlC Network Protocols Configuration Guide Part creating P2C-129

description P2C-l 19 P2C Network Protocols Configuration Guide Part NetBIOS creating P2C-126

NLSP route aggregation P2C-120 P3C Network Protocols Configuration Guide

routing table filtering P2C-127

SC Security Configuration Guide SAP

creating P2C-122 WC Wide-Area Networking Configuration Guide standard P2C-119

standard P2C-122 XC Cisco 105 Switching Services Configuration creating

Guide types P2C- 119

violations logging P2C-124 command P2C-22 Symbols access-list within access-list zone command P2C-21

accounting characters IPX usage in text xix configuring P2C-147 characters database threshold P2C-148 usage in text xix enabling P2C-148

filters P2C-148

maximum transit entries P2C-148

addresses

AppleTalk P2C-9 AARP example P2C-10

See also AppleTalk ARP P2C-2 network numbers P2C-9

access control IPX P2C-79

AppleTalk P2C-17 to P2C-26 example P2C-79

IPX P2C-1 19 to P2C-122 P2C- 130 network numbers P2C-79

access-list additional-zones command P2C-19 to P2C-21 node numbers P2C-79

access-list cable-range command P2C-22 AEP P2C-2

access-list conimand AppleTalk P2C-35

IPX access control P2C- 17 to P2C-26

extended P2C-1 16 P2C-122 access lists

SAP P2C-122 cable ranges P2C-22

standard P2C- 116 P2C-122 configuration examples P2C-59 to P2C-68

NLSP route aggregation displaying P2C-54

filtering P2C-105 to P2C-1 11 guidelines P2C-19

access-list includes command P2C-22 network numbers P2C-18

access-list network command P2C-21 P2C-22 zones P2C-17 P2C-21

access-list other-access command P2C-22 addresses

access-list other-nbps command P2C-20 example P2C-l0

access lists definition P2C-9

AppleTalk network numbers P2C-9 P2C-5 cable ranges P2C-22 remapping

configuration examples P2C-59 to P2C-68 adjacent networks P2C-54

displaying P2C-54 adjacent routers P2C-55

guidelines P2C-19 AEP P2C-2 network numbers P2C-18 ARP P2C-2

zones P2C-17 P2C-21 IPX

configuration examples P2C-168 to P2C-174

Index P2Cl79 horizon AppleTalk continued split P2C-48 ARP table topology table P2C-54 See ARP table AppleTalk enhancements P2C-3

ATCP P2C-38 Ethernet card ATP P2C-2 using P2C-l1 AURP P2C-15 P2C-27 EtherTalk P2C-l P2C-1

configuring P2C-28 extended interfaces

enabling P2C-28 cable range last-heard-from timer P2C-29 assigning P2C- 13

private path database P2C-54 displaying configuring example P2C-57 routing update interval P2C-29 proxy network numbers P2C-41 P2C-28 tunneling routing P2C-13 P2C-15 P2C-16 update-events P2C-54 queue displaying routing example P2C-57

cable ranges zones

definition P2C-9 names P2C-13

interfaces assigning P2C-13 extended network P2C-5 remapping definition P2C-7 CAP P2C-34 fast switching checksums cache entries P2C-54 and generation verification disabling P2C-42 interfaces P2C-44

Ciscos implementation P2C-3 FDDITaIk P2C-l

concurrent and P2C-16 routing bridging CRB pre-FDDITa1k packets P2C-54 P2C-l configuration filters

P2C-56 to P2C-74 configuration examples data packet P2C-21 P2C-23 CRB P2C-16 example P2C-59 DDP P2C2 zones P2C-23

DDR P2C-52 GZL P2C-25 P2C-26 definition P2C-1 partial zones P2C-26 mode discovery example P2C-63 P2C-57 example routing P2C-23 interfaces routing table P2C-24 dynamic P2C-13 routing table example P2C-60 extended P2C-15 routing update filters P2C-24 nonextended P2C-15 free-trade zone nonextended interface P2C-57 example P2C-65 domains P2C-49 establishing P2C-29 domain router configuration P2C-50 gleaning P2C-4 P2C-43 domain router configuration figure P2C-50 GZL P2C-3 P2C-8 P2C-3 P2C-35 encapsulation filters P2C-25 P2C-26 Enhanced IGRP P2C-15 replies P2C-25

active state time limit P2C-48 adjusting integrated routing and bridging bandwidth P2C-49 See AppleTalk IRB P2C-75 example InterPoll P2C-55 Ciscos implementation P2C-46 P2C-3 interenterprise routing P2C-49

configuration examples P2C-58 addresses

disabling P2C-46 remapping P2C-51 enabling P2C-15 P2C-28 P2C-46 AURP

features P2C-44 example P2C-70

hello packets P2C-48 cable ranges hold time P2C-47 remapping P2C-5 interfaces P2C-54 displaying configuring example P2C-75 log neighbor adjacencies P2C-48 domain information P2C-54

neighbors displaying P2C54 domain names P2C-5 route redistribution P2C-47 domain numbers P2C-51

routing protocol enabling P2C-46 domains P2C-49 P2C-51

P2C-180 Network Protocols Configuration Guide Part AppleTalk continued assigning an address P2C-13

hop count P2C-52 enabling routing P2C-12 P2C-13 P2C-14

interfaces P2C-5 routing example P2C-57 P2C-13 remapping P2C-55 zone name assigning horizon P2C-49 nonextended interfaces split

interfaces P2C- 13 proxy network numbers P2C-41

interface status P2C-54 routing P2C-l6

Internet Router software P2C-1 nonextended network P2C-7 internetwork parameters P2C-54 definition

IPTalk performance tuning P2C-39

/etc/services file P2C-36 Phase Phase P2C-8 AppleTalk-to-IP address mapping P2C-35 comparison with Phase P2C- 11 configuration example P2C-7 to P2C-74 compatibility with

definition P2C-34 definition P2C-7

IP encapsulation P2C-37 P2C-38 Phase

node identifier P2C-73 comparison with Phase P2C-8

SLIP drivers P2C-34 compatibility with Phase P2C-1

tunneling P2C-35 definition P2C-7

UDP port numbers P2C-36 pre-EDDITaIk packets

IRB P2C-17 enabling P2C-54

K-Star proxy network numbers

Shiva FastPath routers P2C- 11 example P2C-74

LANE P2C-3 interoperability P2C-41

load sharing responder support P2C-3 P2C-55

round-robin P2C-42 round-robin load sharing enabling P2C-42

LocalTalk P2C-1 routing

logical cable P2C-9 example P2C-57

MacIP extended interfaces enabling

examples P2C-70 dynamically P2C- 15

addresses P2C-33 extended interfaces enabling manually P2C-13

address ranges P2C-32 routing enabling advantages P2C-31 on nonextended interface dynamically P2C-14

clients P2C-54 on nonextended interface manually P2C-12

configuration requirements P2C-32 P2C-l3

definition P2C-3 routing process P2C-15

disadvantages P2C-32 routing protocols P2C-28 implementation P2C-3 specifying

servers P2C-33 P2C-54 routing table P2C-55

traffic P2C-54 P2C-55 entries P2C-54

maximum paths update timers P2C-4l

setting P2C-42 routing tables

MIB P2C-2 update filters P2C-23 P2C-40 monitoring tasks P2C-54 routing updates

name binding advertising routes with no zones P2C-40 P2C-40 See AppleTalk NBP strict checking P2C-39 NBP P2C-2 P2C-27 stub mode P2C-40

name registration timers P2C-41

task table P2C-54 RTMP P2C-2 P2C-15

services P2C-54 advertising routes with no zones P2C-40

neighbor table deleting entries P2C-54 enabling P2C-28

network definition P2C-9 routing updates P2C-40

network connectivity testing P2C-54 strict checking P2C-39

network events logging P2C-43 stub mode P2C-40

nondiscovery-mode interface P2C- 14 seed router P2C-14

nonextended interface Shiva FastPath routers P2C-1

Index P2C-181 AppleTalk continued appletalk arp retransmit-count command P2C-43

SMRP appletalk arp timeout command P2C-42

fast switching P2C-38 appletalk aurp-tickle-time command P2C-29

table P2C-54 fast switching cache appletalk aurp update-interval command P2C-29

forwarding table P2C-55 appletalk cable-range command P2C-13 P2C-l5

global information P2C-55 P2C-16 P2C-29

group table appletalk checksum command P2C-42

P2C-55 appletalk client-mode command P2C-39

neighbor table P2C-55 AppleTalk Control Protocol

port table P2C-55 See AppleTalk ATCP P2C-38

routing table P2C-55 AppleTalk Datagram Delivery Protocol SNMP See DDP

configuring P2C-29 appletalk discovery command P2C-15

configuring example P2C-70 appletalk distribute-list in command P2C-24

sockets displaying P2C-55 appletalk distribute-list out command P2C-24

static routes appletalk domain hop-reduction command P2C-52

defining P2C-53 appletalk domain name command P2C-5

displaying P2C-55 appletalk domain remap-range command P2C-5

test mode entering P2C-55 P2C-52

TokenTalk P2C- AppleTalk Echo Protocol P2C-2

traffic P2C-55 appletalk eigrp active-time command P2C-48

traffic statistics appletalk eigrp-bandwidth-percentage command P2C-49

resetting P2C-54 appletalk eigrp log-neighbor-changes command P2C-48

transition mode P2C-16 appletalk eigrp split-horizon command P2C-48

P2C-58 timers example appletalk eigrp command P2C-48

tunneling appletalk event-logging command P2C-29 P2C-43

AURP P2C-28 appletalk free-trade-zone command P2C-29

cayman P2C-30 appletalk getzonelist-filter command P2C-25

GRE P2C-31 appletalk glean-packets command P2C-43

methods P2C-30 appletalk iptalk-baseport command P2C-36

Update Routing Protocol appletalk lookup-type command P2C-27

See AppleTalk AURP appletalk macip dynamic command P2C-33

VLANs P2C-3 appletalk macip server command P2C-33

WAN protocols supported P2C-3 appletalk macip static command P2C-33

ZIP appletalk maximum-paths command P2C-42

ZIP query interval P2C-43 appletalk name-lookup-interval command P2C-27

ZIP reply filters appletalk permit-partial-zones command P2C-26

configuration example P2C-69 appletalk pre-fdditalk command P2C-54

overview P2C-26 appletalk protocol command P2C-15 P2C-28 P2C-46

zones P2C-1O P2C-13 appletalk proxy-nbp command P2C-41

information table P2C-55 appletalk require-route-zones command P2C-40

name format P2C-1O appletalk route-cache command P2C-44

special characters P2C-lO appletalk route-redistribution command P2C-28 P2C-47

appletalk access-group command P2C-21 P2C-23 appletalk routing command P2C-12 P2C-29 P2C-46

AppleTalk Access List Enhancements appletalk rtmp-stub command P2C-40

fast switching P2C-20 appletalk send-rtmp command P2C-40

filters P2C-22 appletalk static cable command P2C-53

overview P2C-20 appletalk static net command P2C-53

types P2C-21 appletalk strict-rtmp-checking command P2C-40 appletalk address command P2C-13 P2C-14 P2C-15 appletalk timers command P2C-41

P2C-16 AppleTalk Transaction Protocol P2C-2

AppleTalk Address Resolution Protocol AppleTalk Update Routing Protocol

See AppleTalk ARP See AppleTalk AURP

See ARP table AppleTalk appletalk virtual-net command P2C-38 appletalk arp interval command P2C-43 appletalk zip-query-interval command P2C-43

P2C-182 Network Protocols Configuration Guide Part appletalk zip-reply-filter command P2C-26 clear ipx accounting command P2C-152

appletalk zone command P2C-13 P2C-16 P2C-30 clear ipx cache command P2C-149

area-address command P2C-93 P2C-104 P2C- 112 clear ipx nlsp neighbors command P2C- 151

ARP clear ipx route command P2C-149

AppleTalk P2C-2 P2C-42 clear smrp mcache command P2C-54

ARP cache clock ticks

See ARP table IPX P2C-136

ARP table Columbia AppleTalk Package

AppleTalk See CAP

entries P2C-54 command syntax

gleaning P2C-43 document conventions xix

update interval P2C-42 P2C-43 complete sequence number PDU ATCP See CSNP

async interfaces P2C-38 concurrent routing and bridging ATM See CRB

fast switching IPX P2C-1 17 concurrent routing and bridging CRB P2C-16 ATP P2C-2 CRB P2C-16

AURP IPX enabling P2C-84

See AppleTalk AURP P2C-27 CSNP See also NLSP CSNP

backup server table

IPX Datagram Delivery Protocol

Enhanced IGRP P2C-91 See AppleTalk DDP bandwidth See DDP

AppleTalk Enhanced IGRP P2C-49 DDP P2C-2

bridge crb command P2C-16 P2C-84 DDR broadcasts AppleTalk P2C-52 IPX example P2C-75

forwarding P2C-130 P2C-133 P2C-143 IPX P2C-118

type 20 packets P2C-132 P2C-133 spoofing P2C-118

watchdog packets P2C-1 18 SPX

spoofing P2C-118

watchdog packets P2C- 118

default routes cable ranges specifying P2C-146 See AppleTalk cable ranges understanding P2C-80 CAP P2C-34 discovery mode cautions interfaces usage in text xix dynamic P2C-13 CCO extended P2C-15 accessing xx nonextended P2C-15 definition xx distribute-list in command P2C-90 P2C-91 checksums distribute-list out command P2C-90 AppleTalk P2C-42 distribute-sap-list out command P2C-91 Cisco Connection Online domains See CCO See AppleTalk interenterprise routing clear appletalk arp command P2C-54

clear appletalk neighbor command P2C-54

clear appletalk route command P2C-54

clear appletalk traffic command P2C-54

clear ip nhrp command P2C-151

Index P2C-183 routing table example P2C-60

routing update filters P2C-24 IPX eigrp log-neighbor-adjacency-changes broadcast P2C-129 P2C-130 command P2C-150

generic P2C-127 encapsulation GNS P2C-128 AppleTalk P2C-3 P2C-8 P2C-31 P2C-35 NetBIOS P2C-128 P2C-129 IPX P2C-4 P2C-81 to P2C-94 overview P2C-120 encapsulation ppp command P2C-39 table P2C- 127 Enhanced IGRP routing SAP P2C-128 AppleTalk configuring P2C-44 IPX Enhanced IGRP IPX configuring P2C-84 routes P2C90 NLSP route redistribution P2C-89 P2C-1 13 route P2C-90 example P2C-158 updates SAP updates P2C-91 /etc/services file P2C-36 SAP P2C- 113 EtherTalk P2C-1 P2C-1 floating static routes examples IPX P2C- 136 document conventions xix flooded broadcasts extended access lists irx IPX P2C-143 Frame Relay See access lists ipx fast extended networks switching IPX P2C117 AppleTalk P2C-7 free-trade zone

AppleTalk

example P2C-65

free-trade zone AppleTalk

establishing P2C-29

FastPath router

AppleTalk P2C-35 K-Star P2C-1 fast switching P2C-43

AppleTalk P2C-44 Get Nearest Server cache entries P2C-54 See GNS description P2C-144 ipx GetZoneList See GZL cache entries deleting P2C-149 GNS cache entries displaying P2C-149 filters P2C-128 directed broadcast packets P2C-144 request response delay P2C-141 disabling P2C-144 P2C-141 over ATM P2C-1 17 requests GZL over Frame Relay P2C-1 17 P2C-25 over SMDS P2C-l 17 replies EDDI

IPX encapsulation P2C-82 FDDITaIk P2C-1 P2C-54 filters

AppleTalk header compression

data packet P2C-21 P2C-23 IPX P2C-1 18 example P2C-59 hello packets zones P2C-23 AppleTalk GZL P2C-25 P2C-26 Enhanced IGRP P2C-48 zones P2C-26 partial IPX Enhanced IGRP intervals P2C-88 P2C-63 example IPX Enhanced IGRP timers P2C-88

routing P2C-23

routing table P2C-24

P2C-184 Network Protocols Configuration Guide Part helper addresses NetBIOS P2C-119

IPX P2C-129 P2C-130 description P2C- 119

example P2C-173 NetBIOS creating P2C-126 hold time NLSP route aggregation P2C-l20

AppleTalk routing table filtering P2C-127 Enhanced IGRP P2C-47 SAP IPX creating P2C-122

Enhanced IGRP P2C-88 standard P2C-1 19

standard creating P2C-122

types P2C-119

violations logging P2C-124

accounting example P2C-176 IDP configuring P2C- 147 characteristics P2C-4 database entries deleting P2C-152 IGRP database entries displaying P2C-152 Ciscos implementation P2C-46 database threshold P2C-148 Integrated Routing and Bridging enabling P2C-148 See IRB filters P2C-148 integrated routing and bridging maximum transit entries P2C-148 See IRB addresses P2C-79 interface command P2C-28 P2C-36 broadcasts P2C-95 interface tunnel command P2C-28 P2C-30 blocking P2C-142 IP encapsulation of AppleTalk P2C36 forwarding P2C- 129 P2C-130 P2C- 133 Internet Datagram Protocol P2C-143 See IDP type 20 packets P2C-132 P2C-133 Internet Router software clock ticks P2C-136 requirments P2C- 11 compliance with Novells IPX P2C-130

configuration examples P2C-152 to P2C-157 address mapping configuration task list P2C-80 AppleTalk corrupted network numbers P2C-150 See AppleTalk lPTallc DDR P2C-118 ip address command P2C-36 DDR configuring over IPTalk example P2C- 166 /etc/services file P2C-36 default routes AppleTalk-to-IP address mapping P2C-35 See NLSP default routes configuration example P2C-7 ito P2C-74 default routes specifying P2C-146 description P2C-34 default routes understanding P2C-80 IP encapsulation P2C-37 P2C-38 disabling P2C-134 P2C-146 P2C-147 SLIP drivers P2C-34 encapsulation P2C-4 UDP port numbers P2C-36 encapsulations P2C-81 to P2C-94 IPX on IEEE interfaces table P2C-82 access control configuring P2C-130 Enhanced IGRP P2C-86 access control violation logging examples P2C-169 backup server table P2C-91 access lists Ciscos implementation P2C-5 configuration examples P2C-168 to P2C-174 enabling example P2C-l56 extended P2C-119 features P2C-85 extended creating P2C-122 filters P2C-90 implicit deny P2C-126 route updates P2C-90 implicit masks P2C-126 SAP updates P2C-91 named P2C-123 hello packets intervals P2C-88 named extended P2C-124 hello packets timers P2C-88 named NILSP route aggregation P2C-125 hold time P2C-88 named SAP P2C-125 queries P2C-91 named standard P2C-124 redistribution P2C-89

Index P2C-185 IPX continued maximum paths routes P2C-90 description P2C-141 SAP setting P2C-l42 P2C- 156 updatesexample messages SAP P2C-90 updates filtering NetBIOS P2C-129 horizon split P2C-89 MB P2C-4

task list P2C-86 monitoring tasks P2C-148

timers adjusting P2C-88 multicasts P2C-94

Enhanced IGRP enabling P2C-86 NetBIOS

fast switching access control P2C-129 cache entries deleting P2C-149 filters P2C-128

directed broadcast packets P2C-144 filters example P2C-171

disabling P2C-144 messages over ATM P2C-117 filtering P2C-129

over Frame Relay P2C-1 17 NetWare internal network numbers P2C-150 FDDI P2C-82 network access P2C-l 19 to P2C-122

filters network connectivity testing P2C-149 broadcast P2C-129 P2C-130 network numbers

generic P2C-l27 corrupted P2C- 150

INS P2C-128 definition P2C-79

GNS description P2C-128 interfaces P2C-81 NetBIOS P2C-129 internal to NetWare P2C-150

description P2C-128 NILSP See NLSP overview P2C-120 node numbers P2C-79 table P2C-127 routing Novell IPX compliance P2C- 130 SAP P2C-128 OS/2 Requestors P2C-150 flooded broadcasts P2C-143 padding packets P2C-146 GNS performance tuning P2C-130 control P2C-141 requests per-host load sharing enabling P2C-142 filters P2C-128 ping type selecting P2C-149 queue length PPP P2C-119 SAP P2C-138 requests restarting P2C- 134 P2C-146 P2C-147 request response delay P2C-141 RIP

header P2C-1 18 compression description P2C- 136 addresses P2C-130 helper updates delay between P2C-135 P2C-173 example updates delays P2C-136

helper addresses specifying P2C-129 updates timers P2C-136 and integrated routing bridging round-robin load sharing enabling P2C-141 See IRB IPX route aggregation See NLSP

interfaces displaying status P2C- 149 route cache

internal network numbers P2C-150 size P2C-144

IPXWAN P2C-119 route cache invalidation P2C-145 P2C-1 19 disabling routing failed link P2C- 119 between emulated LANs P2C-5 network numbers P2C-1 19 enabling P2C-81 PPP P2C-119 enabling example P2C-152

static P2C-1 19 routing enabling on multiple networks P2C-83 IRB enabling on multiple networks P2C-1 18 keepalives example P2C-153 LANE P2C-5 support enabling over WAN interface load sharing example P2C-164

per-host P2C-142 metrics P2C-4 round-robin P2C- 141 routing table entries

deleting P2C-149

displaying P2C-149

P2C-186 Network Protocols Configuration Guide Part IPX continued ipx default-output-rip-delay command P2C-134

routing table entries adding P2C-127 P2C-137

SAP P2C-4 ipx default-output-sap-delay command P2C- 134

access lists P2C- 139

creating P2C-122 ipx default-ping command P2C- 149

delay ipx default-route command P2C-146

setting P2C-139 ipx default-triggered-rip-delay command P2C-134

delay between packets P2C-137

setting P2C-134 P2C-135 ipx default-triggered-sap-delay command P2C-134

filters P2C-128 P2C-139

filters example P2C-169 P2C-170 ipx delay command P2C-136

messages ipx down command P2C-134 P2C-146

filtering P2C-128 IPX Enhanced IGRP

queue length bandwidth

setting P2C-138 examples P2C- 157

responses to GNS requests interfaces displaying P2C-150

controlling P2C-141 log neighbor adjacencies P2C-150

static entries monitoring P2C-150

configuring P2C-138 neighbors displaying P2C-150

table routing table displaying entries P2C-150

static entries P2C-138 topology table P2C-1S0

updates P2C-90 traffic displaying statistics P2C-l50

setting P2C-138 P2C-139 ipx gns-reply-disable command P2C-141

secondary networks ipx gns-response-delay command P2C-14l

configuring example P2C-154 ipx gns-round-robin command P2C-141

shutting down example P2C-154 ipx hello-interval command P2C-88

servers displaying P2C-149 ipx helper-address command P2C-130 P2C-133

spoofing P2C-118 P2C-143

static routes ipx helper-list command P2C-130

adding to routing table P2C-136 ipx hold-time eigrp command P2C-88

description P2C-136 ipx input-network-filter command P2C-127

floating P2C-136 ipx input-sap-filter command P2C-l28

static routes overriding P2C-136 ipx internal-network command P2C-93

subinterfaces P2C-94 ipx ipxwan command P2C-119 P2C-l configuring P2C-83 ipx ipxwan error command 19 P2C-1 19 configuring example P2C-l53 ipx ipxwan static command

NLSP P2C-94 ipx link-delay command P2C-96

shutting down example P2C-153 ipx linkup-request command P2C-140

tick count P2C-136 ipx maximum-paths command P2C-142

traffic displaying statistics P2C- 149 IPX Named Access Lists

type 20 packets types

accepting P2C-132 task list P2C-123

forwarding P2C-132 P2C-133 ipx netbios input-access-filter command P2C-129

VLANs support P2C-5 ipx netbios output-access-filter command P2C-129

watchdog packets P2C-1 18 ipx network command P2C-82 P2C-84 P2C-93 P2C-94 P2C-127 ipx access-group command P2C-121 P2C-119P2C-147 ipx access-list command P2C-106 P2C-124 P2C-125 ipx nhrp authentication command P2C-1 15 ipx accounting command P2C-148 ipx nhrp holdtime command P2C-117 ipx accounting-list command P2C-148 ipx nhrp interest command P2C-1 16 ipx accounting-threshold command P2C-148 ipx nhrp map command P2C-l 15 P2C-15 ipx accounting-transits command P2C-148 ipx nhrp max-send command P2C-116 ipx advertise-default-route-only command P2C-146 ipx nhrp network-id command P2C- 114 ipx backup-server-query-interval command P2C-91 ipx nhrp nhs command P2C-115 ipx bandwidth-percent eigrp command P2C-87 ipx nhrp record command P2C- 117 ipx broadcast-fastswitching command P2C-144 ipx nhrp responder command P2C-117

Index P2C-187 ipxnbrp use command P2C-116 IRB

ipx nlsp csnp-interval command P2C-98 interfaces

ipx nlsp enable command P2C-93 P2C-94 IPX

P2C-104 to P2C-112

ipx nlsp hello-interval command P2C-97 P2C-98

ipx nlsp lsp-interval command P2C-98

ipx nlsp metric command P2C-96

ipx nlsp multicast command P2C-96 keepalives ipx nlsp priority command P2C-97 IPX P2C-118 ipx nlsp-retransmit-interval command P2C-98 SPX P2C-118 ipx nlsp rip command P2C- 113 Kinetics FastPath router ipx nlsp sap command P2C-113 KIP software P2C-35 ipx output-gns-filter command P2C-128 K-Star ipx output-network-filter command P2C-127 Shiva FastPath routers P2C- 11 ipx output-rip-delay command P2C- 134 P2C-135 P2C-137

ipx output-sap-delay command P2C-134 P2C- 135 P2C- 139

ipx output-sap-filter command P2C-128

ipx pad-process-switched-packets command P2C-146 LANE command P2C-142 ipx per-host-load-share routing between emulated LANs P2C-3 P2C-5 command P2C-139 ipx rip-max-packetsize P2C-138 link-state packet LSP ipx rip-multiplier command P2C-137 See NLSP LSP

ipx route-cache command P2C-144 P2C-146 LocalTalk P2C-1

route-cache command P2C-145 ipx inactivity-timeout log-adjacency-changes command P2C-99 P2C- 151 route-cache max-size command P2C-145 ipx log neighbor adjacencies route command P2C-136 ipx AppleTalk enhanced IGRP P2C-48 ipx router command P2C-86 P2C-89 P2C-93 P2C-113 IPX Enhanced IGRP P2C-150

router command P2C- P2C-1 11 ipx eigrp 110 lsp-gen-interval command P2C-98 router-filter command P2C-127 ipx lsp-mtu command P2C-98 router command P2C-104 P2C-1 12 ipx nlsp P2C-95 to lsp-refresh-interval command P2C-98

ipx router-sap-filter command P2C-128

ipx routing command P2C-8

IPX SAP-after-RIP

queries disabling P2C-140

task table P2C-140 MacIP updates P2C-140 addresses P2C-33 ipx sap command P2C-138 address ranges P2C-32 ipx sap-incremental command P2C-90 advantages P2C-3 ipx sap-max-packetsize command P2C-138 AppleTalk traffic P2C-54 ipx sap-multiplier command P2C-139 clients P2C-54 ipx sap-queue-maximum command P2C-138 description P2C-3 ipx source-network update command P2C-150 disadvantages P2C-32 ipx split-horizon command P2C-89 implementation P2C-3 ipx throughput command P2C-96 requirements P2C-32 ipx triggered-rip-delay command P2C-134 P2C-137 servers P2C-33 P2C-54 ipx triggered-sap-delay command P2C-134 P2C-139 maximum paths ipx type-20-helpered command P2C-133 AppleTalk ipx type-20-input-checks command P2C-132 setting P2C-42 ipx type-20-output-checks command P2C-133 IPX ipx type-20-propagation command P2C- 132 P2C-135 description P2C- 141 ipx update interval command P2C-137 P2C-139 setting P2C-142 ipx update sap-after-rip command P2C-140 command P2C-98 TPXWAN max-lsp-lifetime See IPX IPXWAN

P2C-188 Network Protocols Configuration Guide Part messages NHRP for IPX

access list violation P2C-124 access lists P2C-115

logging P2C-124 authentication P2C-1 15 metrics cache

routing clearing dynamic entries P2C-151

IPX P2C-4 clearing static entries P2C-151

XNS P2C-4 monitoring P2C-15

MIB initiation controlling P2C-115

AppleTalk P2C-2 next hop server P2C-1 15

IPX P2C-4 static IPX-to-NBMA address mapping P2C-1 15

NLSP P2C-92 task list P2C-1 14 multicast command P2C-95 traffic monitoring P2C-151 NLSP

adjacencies P2C- 151

area network numbers P2C-93

CSNP interval specifying P2C-87 P2C-97 P2C-98

database P2C-151 Name Binding Protocol default routes See NBP advertising P2C-146 named IPX access lists P2C-123 designated router name display facility definition P2C-97 AppleTalk P2C-27 election priority specifying P2C-97 NBMA network pseudonode P2C-97 addresses advertised P2C- 117 enabling on an interface logical versus physical figure P2C-161 LAN P2C-93 NBP P2C-2 WAN P2C-94 definition P2C-2 P2C-27 Enhanced IGRP route redistribution P2C-89 description P2C-27 P2C-1 13 name registration example P2C-158 task table P2C-54 for IPX services P2C-54 adjacency state changes P2C-151 NetBIOS GNS queries replying to P2C-141 IPX hello interval specifying P2C-97 P2C-98 filtering messages P2C-129 hop count maximum from RIP updates P2C-87 NetBIOS IPX P2C-128 P2C-97 access control P2C-129 internal network number setting P2C-93 filters example P2C-171 link delay specifying P2C-96 netbios access-list command P2C-126 LSP P2C-98 NetWare Link Services Protocol LSP link-state packet P2C-98 See NLSP metric specifying P2C-96 network command P2C-86 P2C-1lO P2C-111 MIB P2C-92 network numbers multicast addressing IPX P2C-79 disabling P2C-95 P2C-96 Next Hop Resolution Protocol disabling examples P2C-158 See NHRP P2C-83 P2C-94 NHRP multiple encapsulations neighbors P2C-151 enabling P2C-l 14 partial route calculation setting interval P2C-99 IPX pseudonode P2C-97 holdtime P2C- 117 RIP entries aging out P2C-137 initiation controlling P2C-116 RIP packets ioop detection P2C-1 16 maximum size P2C-139 next hop server P2C-117 processing P2C-113 packet rate P2C-116 route aggregation P2C-99 record options suppressing P2C-l 17 aggregated routes P2C-100 requests triggering P2C-l 16 area addresses P2C-100 time addresses P2C- 117

Index P2C-189 NLSP continued Novell IPX

area addresses and route summaries P2C-100 See IPX

areas P2C-l00 to P2C-lOl

benefits P2C-99

configuration task list P2C-103

customized route summarization P2C-102

default route redistribution P2C-101 online documentation default route summarization P2C- 102 See CCO Enhanced IGRP and NLSP 11 P2C-l09

filtering and route summarization

relationship P2C 103

multiple NLSP areas example P2C-158

NILSP 1.1 multiple areas configuring padding packets IPX P2C-146 for P2C-104 Phase

NLSP versions in multiple single area See AppleTalk Phase mixing P2C-1O1 Phase NLSP Enhanced and RIP 1.1 IGRP See AppleTalk Phase P2C-159 example ping command

NLSP 1.1 and NLSP 1.0 areas AppleTalk P2G-54 example P2C-159 IPX P2C- 149

NLSP 1.1 and NLSP 1.0 areas configuring Plain English IPX Access List for P2C-106 types P2C-123

path selection P2C-103 PPP

RIP and NLSP 1.1 configuring P2C- 111 IPX P2C119 route summaries P2C-100 P2C-21 priority..list protocol command route summarization P2C-102 to P2C-l03 proxy network numbers service selection P2C-103 example P2C-74 P2C-100 single versus multiple areas interoperability P2C-41 SAP pseudonode NLSP P2C-97 entries

aging out P2C-139

packets

maximum size P2C-138

shortest path first algorithm SPF redistribute command P2C-113 calculation interval P2C-98 P2C-89

route aggregation P2C-105 P2C-108 P2C-111 subinterfaces P2C-83 P2C-94 P2C-1 12 configuring example P2C-153 redistribution shutting down example P2C-153 AppleTalk Enhanced IGRP P2C-47 throughput specifying P2C-96 IPX Enhanced IGRP P2C-89 NLSP Multicast Addressing responder support examples P2C-158 AppleTalk P2C-55 task list P2C-94 RFC 1243 P2C-2 NLSP Multicast Support RFC 1553 IPX header compression over WAN overview P2C-94 media P2C-118 see also NLSP Multicast Addressing RFC 1634 P2C-119 node numbers RIP IPX P2C-79 IPX nonbroadcast multiaccess network description P2C-136 See NBMA network disable sending of general P2C- 140 nonextended network query timers P2C437 AppleTalk P2C-7 updates P2C436 notes delays updates linking to SAP P2C-140 usage in text xix updates linking to SAP updates P2C-140

P2C-190 Network Protocols Configuration Guide Part route aggregation configuring for NLSP static entries

See NLSP configuring P2C-138 route-aggregation command P2C-104 to P2C-l 12 table route cache static entries P2C-138

size P2C-144 updates route cache invalidation Enhanced IGRP P2C-90

controlling P2C-145 linking to RIP P2C-140 route redistribution setting P2C-138

Enhanced IGRP update timers P2C-139

NLSP P2C-89 secondary networks IPX

Enhanced IGRP and NLSP See IPX secondary networks

example P2C-158 seed router

Enhanced IGRP NLSP configuring P2C-l 13 AppleTalk P2C-14

See also redistribution Sequenced Packet Exchange SPX P2C-118 routes Service Advertisement Protocol

static See SAP

IPX P2C-136 Shiva FastPath router routing table K-Star P2C-l1

AppleTalk P2C-55 show appletalk access-lists command P2C-54

controlling P2C-39 show appletalk adjacent-routes command P2C-54

update timers P2C-41 show appletalk arp command P2C-54 IPX P2C-127 P2C-149 show appletalk aurp events command P2C-54

Routing Table Maintenance Protocol show appletalk aurp topology command P2C-54

See RTMP show appletalk cache command P2C-54 routing tables show appletalk domain command P2C-54

AppleTalk show appletalk eigrp interfaces command P2C-54

update filters P2C-23 show appletalk eigrp neighbors command P2C-54

RTMP P2C-2 show appletalk eigrp topology command P2C-54

advertising routes with no zones P2C-40 show appletalk globals command P2C-54

definition P2C-2 show appletalk interface command P2C-54

interfaces P2C-15 show appletalk macip-clients command P2C-54

routing table show appletalk macip-servers command P2C-54

update timers P2C-4l show appletalk macip-traffic P2C-54

routing updates P2C-40 show appletalk name-cache command P2C-54

strict checking P2C-39 P2C-40 show appletalk nbp command P2C-54

stub mode P2C-40 show appletalk neighbors command P2C-55

show appletalk remap command P2C-55

show appletalk route command P2C-55

show appletalk socket command P2C-55

show appletalk static command P2C-55

show traffic command P2C-55 SAP appletalk show appletalk zone command P2C-55 delay between packets P2C-139 show ip nhrp command P2C-l51 setting P2C-134 P2C-135 show ip nhrp traffic command P2C- 151 description P2C-4 show ipx accounting command P2C- 152 filters show ipx cache command P2C-149 creating P2C-128 show ipx eigrp interfaces command P2C-150 filters example P2C-169 show ipx eigrp neighbors command P2C-150 filters examples P2C-170 show ipx eigrp topology command P2C-150 general query show ipx interface command P2C-149 disabling P2C-l40 show ipx nlsp database command P2C-151 queue length show ipx nlsp neighbors command P2C-151 setting P2C-138 show ipx nlsp spf-log command P2C- 151 responses to GNS requests show ipx route command P2C-149 P2C-150 controlling P2C-141 show ipx servers command P2C-149

Index P2C-191 show ipx traffic command P2C-149 P2C-l50 tick count show smrp forward command P2C-55 IPX P2C-136 show smrp globals command P2C-55 timers show smrp group command P2C-55 IPX Enhanced IGRP adjusting P2C88 show smrp mcache command P2C-55 TokenTalk P2C-1 show smrp neighbor command P2C-55 topology table show smrp port command P2C-55 AppleTalk Enhanced IGRP P2C-54 show smrp route command P2C-55 IPX Enhanced IGRP P2C-150 show smrp traffic command P2C-55 transition mode show sse summary command P2C-149 AppleTalk P2C-l6 Silicon Switch Processor SSP statistics example P2C-58 summary P2C-149 tunnel destination command P2C28 P2C-30 P2C-31

SLIP tunneling drivers AURP P2C-28

IPTalk P2C-34 cayman P2C-30 SMDS GRE P2C-31

fast switching methods P2C-30

TPX P2C-117 tunnel mode command P2C-28 P2C-30 P2C-31 P2C-36

SMRP tunnel source command P2C-28 P2C-30 P2C-31

fast switching cache table P2C-55 P2C-36

traffic table P2C-55 type 20 packets P2C-132 P2C-133 smrp mroute-cache protocol appletalk command P2C-38 SNMP

AppleTalk configuring P2C-29 snmp-server community command P2C-30 spf-interval command P2C-98 UDP port numbers split horizon IPTalk P2C-36 AppleTalk Enhanced IGRP P2C-48 IPX Enhanced IGRP P2C-89 spoofing IPX P2C418

SPX keepalive packets over DDR P2C-1 18

SPX spoofing of keepalive packets P2C-118 VLANs SSP AppleTalk support P2C-3 See also Silicon Switch Processor SSP IPX support P2G-5 SSP statistics summary P2C-149 standard access lists

See access lists IPX static routes

AppleTalk P2C-53 P2C-55 P2C-1 18 IPX P2C-136 watchdog packets DDR P2C-118 subinterfaces

defined P2C-83

IPX P2C-94

configuring example P2C-153

shutting down example P2C-153 NLSP P2C-94 Xerox Network Systems configuring example P2C-153 See XNS shutting down example P2C-153 XNS synchronizing SAP and RIP updates P2C-140 IDP P2C-4

routing metrics P2C-4

test appletalk command P2C-55

P2C-192 Network Protocols Configuration Guide Part ZIP

definition P2C2

query interval P2C-43

reply filters P2C-26

Zone Information Protocol

See ZIP zones

See AppleTalk zones

Index P2C-193 P2C-194 Network Protocols Configuration Guide Part Cisco SYSTEMS

Corporate Headquarters European Headquarters Americas Asia Headquarters Cisco Systems Inc Cisco Systems Europe s.a.rL Headquarters Nihon Cisco Systems K.K 170 West Tasman Drive Parc Evolic Batiment L1/L2 Cisco Systems Inc Fuji Building 9th Floor San Jose CA 95134-1706 16 Avenue du Quebec 170 West Tasman Drive 3-2-3 Marunouchi USA Villebon BP 706 San Jose CA 95 134-1706 Chiyoda-ku Tokyo 100 http//www.cisco.com 91961 Courtaboeuf Cedex USA Japan Tel 408 526-4000 France http//www.cisco.com http//www.cisco.com 800 553-NETS 6387 http//www-europe.cisco.com Tel 408 526-7660 Tel 81 5219 6250 Fax 408 526-4100 Tel 33 6918 61 00 Fax 408 527-0883 Fax 81 5219 6001 Fax 33 6928 83 26

Cisco Systems has more than 200 offices in the following countries Addresses phone numbers and fax numbers are listed on the

Cisco Connection Online Web site at http//www.cisco.com

Argentina Australia Austria Belgium Brazil Canada Chile China PRC Colombia Costa Rica Czech Republic Denmark

England France Greece India Indonesia Ireland Israel Korea Germany Hungary Italy Japan Luxembourg Malaysia Mexico The Netherlands New Zealand Norway Peru Philippines Poland Portugal Russia Saudi Arabia Scotland Singapore South Africa Spain Sweden Switzerland Taiwan ROC Thailand Turkey United Arab Emirates United States Venezuela

Printed in the USA on recycled paper containing 10% postcnnsumer waste

Cor Pn Nb S6-2343-04 78-473 7-0