Avaya XNS User Manual

Configuring XNS Services

BayRS Version 13.0 0 Site Manager Software Version 7.00

Part No. 303548-A Rev 00 October 1998

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

and recomm endations in this docum ent are believed to be accurate and reliable, but are presented without express or implied warranty. U sers must take full respons ibility for their applications of any products specified in this do cum ent. The information in this document is proprietary to Bay Networks, Inc.

The software described in this document is furnished under a license agreement and may only be used in accordance with the te rms of that license. A summary of the Soft w are License is include d in this docum ent.

Trademarks

AN, BCN, BLN, BN, FRE, Optivity, PPX , and Bay Networks are registered trademarks a nd A dvanced Remote No de, ANH, ARN, ASN, BayRS, BaySecur e, BayStac k, BaySt ream, BCC, SP EX, Syst em 5000, and th e Bay Netw ork s logo are trademarks of Bay Net w orks, Inc.

Microsoft , MS, MS-DOS, Win32, Windows, Inter net Explorer, and Windows NT are reg istered trademarks of Microsoft Corporation.

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

Restricted Rights Legend

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

Notwithstanding any other license agreement th at may pertain to, or accompany the delivery of, this computer software, the ri ghts of the Un ited States Gove rnment re garding its use, reproduction, and disclosure are as set forth in the Commercial Computer Software-Restricted Rights clause at FAR 52.227-19.

Statement of Conditions

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

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

Portions of the code in this software product may be Copyright © 1988, Regents of the University of California. All rights reserve d. Redistribution and use in source and binary forms of such portions are permitted, provided that the above copyright notice and this paragrap h are duplicated in all su ch forms and th at any docume ntation, adverti sing materials, and other materials related to such distribution and use acknowledge that such portions of the software were deve loped by th e U niversity of California, Berkeley. The nam e of the University may not be used to endorse or promote products derived from such portions of the software without specific prior written permission.

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

In additi on, the program and information contained herein are li censed only pursuant to a license agreement that contains restrictions on use and disclosu re (that may incorporate by refer ence certain limitations and not ices imposed by thir d pa rt ie s).

303548-A Rev 00

Bay Networks, Inc. Software License Agreement

NOTICE: Please carefully read this license agreement before copying or using the accompanying software or instal ling the hardware unit with pre-enabled software (e ach of which is referred to as “Softw are” in this Agreement). BY COPYING OR USING THE SOFTWARE, YOU ACCEPT ALL OF THE TERMS AND CONDITIONS OF THIS LICENSE AGREEMENT. THE TERMS EXPRESSED IN THIS AGREEMENT ARE THE ONLY TERMS UNDER WHICH BAY NETWORKS WILL PERMIT YOU TO USE THE SOFTWARE. If you do not accept these terms and conditions, return the product, unused and in the o riginal shipping container, within 30 days of purchas e to obtain a credit for the full purchase price.

1. License Grant. Bay Networks, Inc. (“Bay Networks”) gra nts the end user of the Software (“Lice nsee”) a personal, nonexcl usive, nontransferable license: a) to use the Software either on a single computer or, if applic able, on a singl e authori zed de vi ce ide ntified by host ID, fo r whi ch it was origi nal ly acq uired ; b) to cop y th e Softw ar e so le ly fo r bac kup purposes in support of authorized us e of the Software; and c) to us e and copy the associated user manual solely in support of authorized use of the Soft w are by Licensee. This li cense applies to the Software only and does not extend to Bay Networks Agent software or other Bay Networks softw are products. Bay Networks Agent software or other Bay Networks software products are licensed for use under the terms of the applicable Bay Networks, Inc. Software License Agreement that accompanies such software and upon payment by the end user of the applicable licen se fees for such software.

2. Restrictions on use; reservation of rights. The Software and user manuals are protect ed under copyright laws. Bay Networks and/or its licensors retain all title and ownership in both the Sof tware and user manuals, including any revis ions made by Bay Networks or its licensors. The copyright notice must be reproduced and included wi th any copy of any por tion of the Sof tw are or use r manua ls . Licens ee may not modif y, translate, dec ompi le , disas se mble , use for any compe ti ti v e an al ysis, r e v erse e ngi ne er , dis tr ib ute , o r c rea te der i vative work s f ro m the Softw are or u se r man ual s or any copy, in whole or in part. Except as expressly provided in this Agreement, Licensee may not copy or transfer the Softw are or user man uals, in whole or in part. Th e Software and user manuals embody Bay Networks’ and it s licenso rs’ confidential and proprietary intell ectual property. Licensee shall not sublicense, assign , or otherwise disclos e to any third party the Software, or any information about the operation, design, performance, or implementation of the Software and user manuals that is confidential to Bay Networ ks and its licensors; however, Licensee m ay grant permission to its consul tants, subcontractors, and agents to use the Software at Licensee’ s facility, provided they have agreed to use the Software only in accordance with the terms of th is license.

3. Limited warranty. Bay Networks warrants each item of Software, as delivered by Bay Network s and properly installed and operated on Bay Networks hardware or other equipment it is originally licensed for, to function substantially as described in i ts accompanying user manual during its warranty period, wh ich begins on the date Softwar e is fi r st shi pped to Licen see . If any it em of Soft war e fai ls to so func ti on du ring i ts warr anty pe ri od, as t he so le remedy Bay Ne tworks will at its discretion provide a suitable fix, pat ch, or workaround for the problem tha t m ay be included in a future Software release. Bay Networks further warrants to Licensee that the media on which the Softwar e is provided will be fr ee from defects in materials and workmanship under normal use for a period of 90 days from the date Software is first shipped to Licensee. Bay Networks will replace defective media at no charge if it is returned to Bay Netw orks during the warranty per iod along with proof of the date of shipmen t. This warran ty does not apply i f the media has been damaged as a result of acci dent, misuse, or abuse. The Licensee assumes all re sponsibility for selection of the Software to achieve Licensee’s intended results and for the installation, use, and results obtained from the Software. Bay Networks does not warrant a) that the functions cont ained in the software w ill meet the Licensee ’s requirements, b) that the Software will operate in the har dw are or software combinations that the Licensee may select, c) that th e operation of the Software will be uninterrupted or error free, or d) that all defects in the operati on of the Software wi ll be corrected. Bay Networks is not ob ligated to remedy any Software defect that cannot be repro duced with the latest Software release. Thes e warranties do not apply to the Sof tware if it has been (i) altered, except by Bay Networks or in accordance with its instructions; (ii) used in conjunction with another vendor’s product, resulting in the defect; or (iii) damaged by im proper environm ent, abuse, misuse, accident, or neglige nce. THE FOREGOING WARRANTIES AND LIMITATIONS ARE EXCLUSIVE REMEDIES AND ARE IN LIEU OF ALL OTHER WARRANTIES EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Licensee is responsible for the security of

303548-A Rev 00

iii

its own data and information and for maint aining adequate procedures apart from the Software to reconstruct lost or altered files, data, or programs.

4. Limitati on of liabili ty. IN NO EVENT WILL BAY NETWORKS OR ITS LICENSORS BE LIABLE FOR ANY COST OF SUBSTITUTE PROCUREMENT; SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL DAMAGES ; OR ANY DAMAGES RESULTING FROM INACCURATE OR LOST DAT A OR LOSS OF USE OR PROFITS ARISING OUT OF OR IN CONNECTION WITH THE PERFORMANCE OF THE SOFTWARE, EVEN IF BAY NETWORKS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. IN NO EVENT SHALL THE LIABILITY OF BAY NETWORKS RELATING TO THE SOFTWARE OR THIS AGREEMENT EXCEED THE PRICE PAID TO BAY NETW ORKS FOR THE SOFTWARE LICENSE.

5. Governmen t L i c en s ees. This provisio n applies to all Software and documentation acquired directly or indirectly by or on behalf of the United States Government. The Software and documentation are commercial products, licensed on the open market at market prices, and were developed entirely at private expense and without the use of any U.S. Government funds. The license to the U.S. Government is granted only with restricte d rights, and use, duplication, or disclos ure by the U.S. Gover n m ent is subject to the restrictions set forth in subparagraph (c)(1) of the Commercial Computer So ftware––Restricted Rights clause of FAR 52.227-19 and the limitations set out in this license for civilian agencies , and subparagraph (c) (1)(ii) of the Rights in Technical Data and Computer Software clause of DFARS

252.227-7013, for agencies of t he D e partment of Defense or their suc cessors, whiche ver is applicable.

6. Use of Software in the European Communi ty. This prov ision applies to all Software acquired for use within the European Comm unity. If Lice nsee uses the Software within a countr y in the European Community, the Softwar e Directive enacted by the Counc il of European Communities Directive dated 14 May, 1991, w ill apply to the examination of the Software to facilitate interoperability. License e agrees to notify Bay Networks of any such intended examination of the Software and may procure support and assistance from Bay Networ ks.

7. Term and termination. This license is effective until terminated; however, all of the restrictions with respect to Bay Networks’ copyright in the Software and user manuals will cease being effective at the date of expiration of the Bay Networks copyright; those r estrictions relating to use and disclosure of Bay N etworks’ confidential information shall continue in effect. Licensee may terminate this license at any time. The license will automatically terminate if Licensee fails to co m ply with any of the terms and conditions of the license. Upon terminat ion for any reason, Licensee will immediately destroy or return to Bay Networks the Software, user manuals, and all copies. Bay Networks is not liable to Licensee for damages in any form solely by reason of the termination of this license.

8. Export and Re-export. Licensee agrees not to export, direct ly or indirectly, the Software or related technical data or information without first obtaining any required export licenses or other governmental approvals. Without limiting the fore going, Licensee, on behalf of itself and its subsidiaries and affiliates, agrees that i t will not, without first obtaining all export licenses and appro vals required by the U.S. Government: (i) export , re-export, transfer, or diver t any such Sof tware or technical data, or any direct product thereof, to any coun try to which such exports or re-exports are rest ricted or embargoed under United States ex port control laws a nd regulations, or to any national or resident of such rest ricted or embargoed countries; or (ii) provide the Software or related technical data or inf ormation to any military end user or for any military end use, including the design, develop ment, or production of any chemical, nuclear, or biological weapons.

9. General. If any provision of this Agreement is held to be invalid or unenforceable by a court of competent jurisdiction, the remainder of the provisions of this Agreement shall remain in full force and effect. This Agreement will be governed by the laws of the state of California.

Should you have any questions concerning this Agreement, contact Bay Networks, Inc., 440 1 G reat America Parkway, P.O. Box 58185, Santa Clara, Californi a 95054-8185.

LICENSEE ACKNOW LEDGES THAT LICENSEE HAS READ THIS AGREEMENT, UNDERSTANDS IT, AND AGREES TO BE BOUND BY ITS TERMS AND CONDITIONS. LICENSEE FUR THER AGREES THAT THIS AGREEMENT IS THE ENTIRE AND EXCLUSIVE AGREEMENT BETWEEN BAY NETWORKS AND LICENSEE, WHICH SUPERSEDES ALL PRIOR ORAL AND WRITTEN AGREEMENTS AND COMMUNICATIONS BETWEEN THE PARTIES PERTAINING TO THE SUBJECT MATTER OF THIS AGREEMENT. NO DIFFERENT OR ADDITIONAL TERMS WILL BE ENFORCEABLE AGAINST BAY NETWORKS UNLESS BAY NETWORKS GIVES ITS EXPRESS WRITTEN CONSENT , INCLUDING AN EXPRESS WAIVER OF THE TERMS OF THIS AGREEMENT.

303548-A Rev 00

Preface

Before You Begin ..............................................................................................................xi

Text Conventions ................................................................... ...........................................xii

Acronyms ......................................................................................................................... x ii i

Bay Networks Technical Publications ..............................................................................xv

How to Get Help .............................................................................................................. xv

Chapter 1 XNS Overview

XNS Protocol Stack ........................................................................................................1-2

Protocol Layer/Level Support .........................................................................................1-3

Level 0 ......................................................................................................................1-3

Level 1 ......................................................................................................................1-4

Level 2 ......................................................................................................................1-4

XNS RIP Over view .........................................................................................................1-4

Error Protocol .................................................................................................................1-6

Echo Protocol ........................................................................................... ......................1-7

Sequenced Packet Protocol .... .......................................................................................1-8

Pack et Exchange Protocol .................................... ....... ....... .......... ....... .. ....... .......... ....... .1-8

External Server s .................................................................... .........................................1-8

Static Routes ..................... ....................................................................... ......................1-9

Adjacent Hos ts ............................................................... ..............................................1-11

Configurable Split Horizon ............................................................................................1-13

For More Information about XNS .. ................................................................................1 -14

Chapter 2 XNS Config uration Not es

Configuring XNS Without RIP .........................................................................................2-1

Configuring a MAC Address on a Token Ring Inte rface .................................................2-2

303548-A Rev 00

Chapter 3 Enabling XNS Services

Enabling XNS on an Interface ........................................................................................ 3-1

Enabling XNS Services ..................................................................................................3-2

Chapter 4 Editing XNS Parameters

Accessing XNS Parameters ..... .............. ....................................................................... .4-2

Editing XNS Global Parameters .....................................................................................4-3

Editing XNS Interface Parameters .................................................................................. 4-6

Editing RIP Interface Parameters .................................................................................4-13

Configuring Adjacent Host Parameters ........................................................................4-16

Adding an Adjacent H ost ........................................................................................ 4-17

Editing an Adjacent Host ........................................................................................4 -20

Deleting an Adjacent Host ......................................................................................4-22

Configuring Static Route Pa rameters ...........................................................................4 -22

Adding a Static Route ............................................................................................ 4 -24

Editing a Static Route .............................................................................................4-25

Deleting a Static Route ..........................................................................................4-27

Editing XNS Traffic Filters .............................................................................................4-27

Appendix A Site Manager Default Settings

Index

303548-A Re v 00

Figures

Figure 1-1. Comparison of OSI and XNS Protocol Stacks .........................................1-2

Figure 1-2. Static Route in a Sample Network .........................................................1-10

Figure 1-3. Static Adjacent Host in a Sample Network ............................................1-12

Figure 1-4. Split Horizon Enabled i n a Fully Meshed Network .................................1-13

Figure 1-5. Split Horizon Disabled in a Non-Fully Meshed Network ........................1-14

Figure 3-1. XNS Configuration Window ....................... .. .......... ....... ....... .. .......... ....... .3-2

Figure 4-1. Configuration Manager Window ...................................... ....... ..... ....... ......4-2

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

Figure 4-3. XNS Interfaces Window ...........................................................................4-6

Figure 4-4. XNS RIP Interfaces Window ..................................................................4-14

Figure 4-5. XNS Adjacent Hosts Window ........................................ .. ..... .. ..... ..... .. ....4-17

Figure 4-6. Adjacent Host Configuration Window ....................................................4-18

Figure 4-7. XNS Static Routes Window ...................................................................4-23

Figure 4-8. XNS Add Static Route Window ..............................................................4-24

303548-A Rev 00

vii

Tables

Table 1-1. XNS Error Protocol Numbers ..................................................................1-7

Table A-1. XNS Global Parameters ........ ............................ ...................................... A-1

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

Table A-3. XNS RIP Interface Parameters ............................................................... A-2

Table A-4. XNS Adjacent Host Parameters ............................................. .................A-2

Table A-5. XNS Static Route Parameters ................................................................A-2

303548-A Rev 00

This guide de scribes the Xerox Networking System (XNS) protocol and what you do to start and customize XNS services on a Bay Networks® router.

Before You Begin

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

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

• Connect the router to the networ k and create a pilot configuration f ile ( refer to

Quick-Starting Routers, Configuring BayStack Remote Access, or Connecti ng ASN Routers to a Network).

Preface

303548-A Rev 00

Make sure tha t you are running the latest version of Bay Networks BayRS Site Manager sof tware. For information about upgrading BayRS and Site Manager, see the upgr ading guide for your version of B ayRS.

™

and

Configuring XNS Services

Text Conventions

This guide use s the following text conventions:

angle brackets (< >) Indicate that you choose the text to enter based on the

description inside the brackets. Do not type the brackets when entering the command. Example: If the command syntax is:

bold text

<ip_address>

ping ping 192.32.10.12

Indicates text tha t you need to enter and command

, you enter:

names and options. Example: Enter

Example: Use the

show ip {alerts | routes

command.

dinfo

}

braces ({}) Indicate required elements in syntax descriptions

where there is more than one option. You must choose only one of the options. Do not type the braces when entering the command. Example: If the command syntax is:

, you must enter either:

show ip {alerts | routes show ip alerts or show ip routes

}

brackets ([ ]) Indicate optional elements in syntax descriptions. Do

not type the brackets when entering the command. Example: If the command syntax is:

, you can enter either:

show ip interfaces [-alerts show ip interfaces

]

show ip interfaces -alerts

xii

ellipsis points (. . . ) Indicate that you repeat the last element of the

comman d as need ed . Example: If the command syntax is:

ethernet/2/1 ethernet/2/1

parameter> <value>

and as many parameter-value pairs as

] . . .

, you enter

needed.

303548-A Re v 00

Preface

italic text Indicates file and directory names, new terms, book

titles, and variables in command syntax descriptions. Where a variable is two or more words, the words are connected by an underscore. Example: If the command syntax is:

show at

valid_route

valid_route>

is one va riable and you subs titu te one value

for it.

screen text Indicates system output , fo r exa mple, prompts and

system messages. Example:

Set Ba y Netw orks Tr ap Mo nito r Fil ters

separator ( > ) Shows menu paths.

Example: Protocol s > IP identifies the IP option on the Protocols menu.

vertical line (

) Separates choices for command keywords and

arguments. Enter only one of the choices. Do not type the vertical line when entering the command. Example: If the command syntax is:

Acronyms

303548-A Rev 00

, you enter either:

show ip {alerts | rou tes show ip alerts

}

show ip routes

, but not both.

AUI Attachment Unit In terface BootP Bootstrap Protoco l BRI Basic Rate Interface CCITT International Telegraph and Telephone Consultative

Committee (no w ITU-T) CSMA/CD carrier sense multiple access with collision detection DLCMI Data Link Control Management Inte rface GUI graphical user interface HDLC high-le vel data link control

xiii

Configuring XNS Services

IDP Internetwork Datagram Protocol IP Internet Protocol ISDN Integra ted Services Digital Network ISO International Organization for Standardiza tion ITU-T International Telecommunication

LAN local area networ k MAC media access c ontrol MAU media access unit MDI-X Media-Dependent Interface with Crossover NBMA nonbroadcast multi- access OSI Open Systems Interconnection OSPF Open Shortest Path Fi rst PPP Poin t-to-Point Protocol RIP Routing Informati on Protocol

Union–Telecommunications (formerly CCITT)

xiv

SMDS Switched Multime gabit Data Service SNMP Simple Network Management Protocol STP shielded twisted-pair TCP/IP T ransmission Control Protocol/Internet Protoco l TFTP Trivial File Transfer Protocol TPE twisted-pair Ethernet UTP unshielded twist ed-pair WAN wide area network

303548-A Re v 00

Bay Netwo rks Technical Publicati o ns

You can now print Bay Networks technical manuals and release notes free, directly from the Int ernet. Go to support.bayn etworks.com/libr ary/tpubs/. Fi nd the Bay Networks product for which you need doc umenta tion. Then locate the specific category and model or version for your hardwa re or software product. Using Adobe Acrobat Reader, you can open the manuals and release notes, search for the sections you need, and print them on most standard printers. You can download Acrobat Reader free from the Adobe Systems Web site, www.adobe.com.

You can purchase Bay Networks documentation sets, CDs, and selected technic al publications through the Bay Networks Collateral Catalog. The catalog is located on the World Wide Web at support.baynetworks.c om/catalog. html and is divided into sections arran ged alpha betically:

• The “CD ROMs” section lists available CDs.

• The “Guides/Books” section lists books on techn ical topics.

• The “Technical Manuals” section lists a vailable printed documentation sets.

Preface

Make a note of the part num bers and prices of the items that you want to order. Use the “Marketing Collateral Catalog description” link to place an order and to print the order form.

How to Get Help

For product assista nce, support contracts, or information about educational services, go to the following URL:

http://www.baynetworks.com/corporate/contacts/

Or telephone the Bay Networks Technical Solutions Center at: 800-2LANWAN

303548-A Rev 00

Chapter 1

XNS Overview

This chapter provides information on the Bay Networks implementation of the Xerox Networking System (XNS) router software. The Bay Networks implementation of XNS is based on the Xerox System Integration Standard specific ation (Xerox Corporation, December 1981), commonly referred to as The Gray Book.

This chapter describes the following topics:

• XNS Protocol Stack

303548-A Rev 00

• Protocol Layer/Level Support

• XNS Routing Information Protocol (RIP)

• Error Protocol

• Echo Protocol

• Sequenced Packet Protocol

• Packet Exchange Protocol

• External Servers

• Static Routes

• Adjacent Hosts

• Configurable Split Horizon

1-1

Configuring XNS Services

XNS Protocol Stack

XNS was deve loped at the Xerox Palo Alto Research Center (PARC). Its layered architecture is a pr ede cessor of the OS I a rchitectur al mode l. Bot h ar chitect ures are functionally simi lar. F igur e 1-1 compares the OSI and XNS protocol stacks.

OSI XNS

Layer 7 - Application

Layer 6 - Presentation

Layer 5 - Session

Layer 4 - Transport

Layer 3 - Network

Layer 2 - Data link

Layer 1 - Physical

Level 4 -Application

Level 3 - Control, process interaction

Level 2 - Transport

Level 1 - IDP

Level 0 - Transmission media protocols

XNS0001A

Figure 1-1. Comparison of OSI and XNS Protocol Stacks

A description of each XNS level follows:

• Level 0 protocols handle the physical transmission of data between two points. Lev el 0 pr otocols ar e independe nt of XNS specifications. Instead, they depend on the trans mission m edium a v ai lable be tween the t wo points e ngage d in communication. Examples of Level 0 protocols are Ethernet and Token Ring. Level 0 corresponds generally to Layers 1 and 2, the physi cal and data link layers of the OSI model.

1-2

• The Level 1 protocol, Internet Datagram Protocol (IDP), determines where each internet packet goes, addresses the source and destination of each internet packe t, a nd sel ects the transmission medium. Level 1 corresponds generally to Layer 3, the network layer of the OSI model.

303548-A Re v 00

• Level 2 protocols pro vide for the exchange of routing inf ormation between routers, handle the sequencing of packets within a packet stream, report transmission errors, retransmit packets in response to errors, suppress duplicate packets, and adjust the rate of packet transmission (flow control). Examples of Level 2 protocols are Routing Information Protocol, Error Protocol, Echo Protocol, Sequenced Packet Protocol, and the Packet Exchange Protocol. Level 2 corresponds to Layer 4, the transport layer of the OSI model.

• Level 3 protocols are control protocols; they de termine process interactions that involve remote resources, such as printer and file requests, and da ta structuring conventions. Level 3 corresponds generally to Layers 5 and 6, the session and presentat ion layers of the OSI model.

• Level 4 protocols are applic ation protocols that are implemen ted for specific platforms. Level 4 corresponds to Layer 7, the application layer of the OSI model.

Protocol Layer/Level Support

XNS Overview

Level 0

303548-A Rev 00

This section describes in detail the protocol support that Bay Networks XNS routing softwar e provide s at Lev els 0, 1, and 2 of the XNS protocol model. Lev el s 3 and 4 do not involve routing, and are beyond the sco pe of this document.

The XNS Leve l 0 protocols handle the physical transmission of data between two points. The Bay Networks router running XNS software supports the fol lowing Level 0 protocols or frame formats/encapsulations:

• Ethernet: Ethernet II

• Token Ring: SNAP

• FDDI: SNAP

• Frame Relay: Frame Relay SNAP

• SMDS: SMDS SNAP

1-3

Configuring XNS Services

Level 1

Bay Networks implements Inte rnetwork Datagram Protocol (I DP), the only XNS Leve l 1 protocol. IDP determines where each internet packet goes, addresses the source and destination of each internet packet, and selects the transmission medium. IDP is a connectionless datagram protocol. In other words, it does not need a channel establish ed for delivery. Also, IDP is unreliable. Higher-level protocols assum e the responsibility for reliability.

The Lev el 2 services provide IDP with the information necessary to route internet packets.

Level 2

Level 2 protocols correspond to the transport layers of the OSI model. The Bay Networks router runn ing XNS softwa re implements the following XNS Level 2 protocols:

• Routing Information Protocol

• Error Protocol

• Echo Protocol

• Sequenced Packet Protocol

• Packet Exchange Protocol

Note that the Bay Networks router running XNS software bridges packet s other than XNS when the bridge is config ured.

XNS RIP Over v iew

XNS Routing Information Protocol (RIP) lets workstations and routers exchange information dynamica lly to establish the route with the fewest hops and shortest delay to each network.

Each router running XNS softwar e maint ains a RIP table, which contains the following information about eve ry network in the XNS network topology:

• The network address of each network

• The number of hops (cost) to that network

1-4

303548-A Re v 00

XNS Overview

• The address of the next-hop node to which packet s dest ined for that network will be forwarded

Routers maintain RIP tables b y exch anging request a nd response pa ckets. Ro uters update their RIP tables with inf or mation from incoming response packet s. The header of each packet indicates the packet operation: request or response.

RIP request packets con tai n the number of the destination network in the header. A RIP request packet may be one of the following types:

• A general request that a router broadcasts to det ermi ne the fastest route to all networks on an internetwork. The va lue ffffffff in the network number field within the RIP data indicates tha t the packet is a general request.

• A specific request that a workstation or router broadcasts to determine the fastest rout e to a partic ular network. One or more network numbers in the network number f ield within the RIP data indicates that the packet is a specific request.

Routers at the destination network issue RIP response packets. RIP response packets contain the network number and the number of hops and ticks requi red to get to the network.

303548-A Rev 00

A RIP response may be one of the following types:

• A response to a request

• An informational broadcast from a router issued every 30 seconds

• An informational broadcast when a change occurs in the routing table; examples are changes in cost information, changes to routes, route timeouts, and additions of routes to networks new to the table

• An informational broadcast when an interface performs an orderly shutdown procedure or initializes

1-5

Configuring XNS Services

To limit traffic, RIP broadcas ts are limited to a router’s immediate segments and are not forwarded b y receiving routers.

The router running XNS software lear ns WAN addresses from RIP

Note:

broadcasts received over WANs, and therefore stores XNS address/WAN address pairs for future use as next-hop destinations. So, if RIP is not configured for a W AN interface, you must configure adjacent hosts for all transmission paths to nodes adjacent to F rame Relay or SMDS circuits when you configure an XNS interface. You must then configure static routes from the adjacent hosts to the next-hop routers.

You can enable RIP Listen and RIP Supply functions for each XNS and/or XNS interface on the router ru nning XNS software. When you enable the Listen function, the router adds routes received in RIP updates from neighboring routers to its own inter nal routing table. When you enable the Supply function, the router running XNS software transmits RIP updates to routers on neighboring networks.

Error Protocol

The Error Protocol is an optional Level 2 protocol intended to provide diagnostic and performance information.

1-6

The destination host that detects an error returns an Error Protocol packet to the socket of the host that generated the incorrect packet . The Error Protocol packet contains a copy of the first 42 bytes of the incorrect packet so that it can be validated by the source. The Packet T ype field of the Error Protocol packet identifies the erro r num b er.

Table 1-1

lists the XNS standard Error Protocol num bers. Bay Networks routers running XNS software report errors they detect using this standard. The host that detected the error disc ards the incorrect packet after cop ying its first 42 bytes to the Data field of the Error Protocol packet.

Because the protocol is opti onal, the host that receives the Error Protocol packe t may or may not use the information before dropping the packet. The Bay Networks router runn ing XNS softwa re does not use the information in the Error Protocol packet s it receives.

303548-A Re v 00

XNS Overview

Table 1-1. XNS Error Protoc ol Nu m bers

Error Number (Octal) Description of Error

0 An unspecifi ed error is detect ed at the destination. 1 A serious inconsi stency, such as an incorrect checksum, is detected

at the dest ination.

2 The destinati on socket specified in the incorrect packet does not

exist in the destination host. 3 The destinat ion dropped the packet because of resource limitations. 1000 An unspecified error occurred before reaching the dest ination. 1001 A serious inconsistency, such as an incorrect checksum, occurred

before reaching the destina ti on. 1002 The destinati on host cannot be reached from here. 1003 The packet’s hop count reached its upperbound threshold without

reaching it s destination. 1004 The packet is too large for an intermediate network. The Error

Parameter field of the Error Protocol packet contains the maximum

pack et l ength allowed.

Echo Protocol

The Echo Protocol is a Level 2 protocol. It provide s a relatively simple means to verify the existence and correct operatio n of a host’s IDP implementation and a path to a host.

The Echo Protocol packet contains an Operation field, which indicates whether the packet is a request (1) or a response (2). The Bay Networks router running XNS software generates responses only to echo requests it receives on the well-kno wn error socket, Socket 2. It does not gener at e echo request packets.

When the destina tion host receives an echo request packet, it generates a response packet and copies the data from the Data field of the request packet to the Data field of the response packet. The destination host then forwards the response packet to the source socket of the host that sent the echo request. This lets the requesting host verify the data.

303548-A Rev 00

1-7

Configuring XNS Services

Sequenced Packet Protocol

The Sequenced Packe t Protocol (SPP) is a Level 2 protoc ol. It supports the reliable transmission of sequenced internet packets between clients on the network. SPP uses IDP to create a virtual circuit between the source and destination endpoints.

SPP has an open connection when it knows the address (host and socket number) and the connection identification for both connection endpoints. When packets start passing over a new connection, SPP assigns sequ ence number 0 (zero) to the first packet transmitted.

SPP supports e xtende d sess ions between c onnection endpoint s, as oppo sed to PEP (Packet Exchange Protocol), which requires no connection and supports only request-response transactions.

SPP specifications provide information on packet format, standard packet sequences, and recommendations on how best to use the protocol.

Packet Excha n ge Proto c o l

The Packet Exchange Protoc ol (PEP) is a Level 2 protocol that XNS uses to send a request and receive a response reliably. PEP handles request-response transactions without the need to establish a connection between clients. The Packet Exchange Protocol can send packets to or from any valid socket address.

External Ser vers

The Bay Networks XNS routing software features external server support. External server support provides client access to a service on another ne twork if the service is not available on the client’s network.

You enable external server support from the XNS Interfaces window (refer to “Editing XNS Interface Parameters

1-8

” in Chapter 4).

303548-A Re v 00

When you enable external server support on a particular XNS interface, you specify the service r equest t ype to be rout ed and the de stinat ion o f the se rvic e. The router then forwar ds incoming requests for that service type to the remote destination.

Note:

ava ilable on the local network. The default setting for this feature is Disabled.

Static Routes

Static routes are manually c onfigured routes that specify the next hop in the transmission path a datagram must follow based on the datagram’s destination address. A static route specifies a transmission path to another network.

The Bay Networks router running XNS softwa re allows you to configure static routes on each logical XNS interface. For example, in Figure 1-2 the interface on Router Host ID 1 to Network 5 is a static route. Unlike r outes learned through RIP, static routes remain in the RIP tables until you delete them.

XNS Overview

You should enable external server support only when a service is not

the route from

303548-A Rev 00

Static route support for XNS allows you to do the following:

• Direct all XNS traffic destined to a given network to an adja cent host

• Reduce routing traff ic by disabling RIP Supply on all or a subset of attached interfaces and by manually configuring static routes

• Eliminate all dynamic routing capabil ities and all RIP Supply and listen activities over an XNS interface

Caution:

T o establish a data link layer connection in a Frame Relay or SMDS network (with the route r sending frames over a static route ), you must configure an adjacent host and enter a locally signif icant DLCI. (Refer to “Configuring Adja cent Host Parameters

” in Chapter 4.)

1-9

Configuring XNS Services

Static route configuration for all XNS traffic to network 5

Parameters

Target network Next hop network Next hop host

Frame Relay or SMDS Network 2

Key

Values

5 2 4

Router

Host ID 1

Frame Relay or SMDS Network 3

Generic XNS Router

Host ID 4

Frame Relay or SMDS Network 5

Static route Route closed

to XNS traffic Route not

affected

Generic XNS router

Host ID 6

Figure 1-2. Static Route in a Sample Network

1-10

XNS0002A

303548-A Re v 00

Adjacent Hosts

An adjacent host i s a network device that is local to a dir ectly connected netw ork. This devic e may or m ay not be a route r. For example, Host ID 4 in Figure 1-3 is an adjacent host to Router Host ID 1. Host ID 6 is not an adjacent host because it is not connected logically to a directly adjacent network.

The Bay Networks router running XNS softwa re allows you to specify static transmission pa ths to adjac ent hosts . A st atic transm ission pa th to an a djacent host establishes the data link con nection necessary for packet tr ans mission along a static route in a Frame Relay or SMDS network when RIP is not enabled. For example, in Figure 1-3 configured as a statically adjacent host. This provides a data link c onnection that allows the static routing to occur between Host ID 1 and Network 5.

With adjacent host support, you can do the following:

• Configure the router to map XNS addresses of network devices that are local

to adjacent WANs to their associated WAN addresses

• Configure many static rout es that use a single adjacent host as their next-hop

node, thereby reducing manual configur ation tasks

XNS Overview

the XNS interface on Router Host ID 1 has Host 4

303548-A Rev 00

You must use the locally significant data link control identifier (DLCI)

Note:

parameter to iden tify a vir tual circuit when yo u config ure a sta tic ad jacent hos t in a Frame Relay or SMDS network. You must enter the DLCI in hexadecimal format. (Refer to “Configuring Adjacent Host Parameters” in Chapter 4.)

1-11

Configuring XNS Services

Adjacent host configuration for all XNS traffic to host 4

Parameters Values

2Target host network 4Host ID

Next hop interface

Frame relay DLCI address Decimal (Hexadecimal)

Frame Relay or SMDS Network 2

Adjacent host

0x191Locally significant DLCI

Router

Host ID 1

402 (0x192)401 (0x191)

Frame Relay or SMDS Network 3

404 (0x194)403 (0x193)

Generic XNS router Host ID 4

Key

Static route Route closed

to XNS traffic Route not

affected

Frame Relay or SMDS Network 5

Generic XNS router

Host ID 6

Figure 1-3. Static Adjacent Host in a Sample Network

1-12

XNS0003A

303548-A Re v 00

Configurable Split Horizon

The purpose of the Split Horizo n algorit hm is to pr e v ent c ircula r route s and reduce network traffic. The Bay Networks implementation of Split Horizon excludes RIPs and SAPs learne d from a ne ig hbor when f orwardi ng RIP a nd SAP updat es to that neighbor. Split Horizon is enabled by default for each inte rface .

XNS Overview

Caution:

necessary.

If you have a star or non-fully meshed Frame Relay topology, you may need to disable Split Horizon on certain interfaces for the routers to learn about the other networks.

A fully meshed network is a WAN in which all nodes have a logica lly direct connection to each other. In a fully meshed environment, all routers will learn about all networks and have complete routing tables. Figure 1-4 fully meshed network with Split Horizon e nabled.

Split Horizon enabled on this interface to eliminate all redundant RIP and SAP traffic.

W e advise you not to disable Split Horizon unles s it is abso lutely

shows a sa mple

Network

Router A

WAN

Network

Figure 1-4. Split Horizon Enabled in a Fully Meshed Network

303548-A Rev 00

Router B

Router C

Network

XNS0004A

1-13

Configuring XNS Services

A non-fully meshed network is a WAN in which one or more nodes do not have logically direct c onnections to all other nodes. Figure 1-5 shows a sample non-fully meshed network with Split Horizon disabled.

Network

Split Horizon disabled on this interface so that Router B can learn about Network 3 and Router C can learn about Network 2.

Router A

WAN

Network

Router B

Router C

Figure 1-5. Split Horizon Disabled in a Non-Fully Meshed Network

If you enable Split Horizon on Router A, as in Figure 1-4, Router B will never learn about Router C’s networks and vice versa. If users on Network 2 need to communicate with user s on Network 3, you must dis abl e Split Horizon on Router A, as in Figure 1-5. You do not, howe ver, need to disable Split Hor izon on R outers B and C.

For More Information about XNS

Network

XNS0005A

1-14

The followin g documents provide technical detail on XNS protocol implementation:

Xerox System Integration Standard. Xerox Corporation, December 1981. Xerox Network Systems Architecture General Information Manual. Xerox

Corporation, 1985.

303548-A Re v 00

Refer to this chap ter w h en you are configuring the following XNS services:

• XNS without RIP

• XNS on a To ken Ring int erfa ce

Configuring XNS Without RIP

The router running XNS software lea rns WAN addresses from RIP broadcasts receiv ed over WANs. The router stores the XNS address/WAN address pairs in its RIP table for future determination of next-hop destinations.

Chapter 2

XNS Configuration Notes

303548-A Rev 00

Every router running XNS software on the internetwork learns about all the other routers running XNS software through the propaga tion of RIP tables. These table s can become very large in large internetworks.

You may want to configure XNS without RIP to control the size of these tables and to reduce bandwidth. However, you must do the following when you configure an XNS WAN interface without RIP:

Configure an adjace nt hos t, and edi t th e DLCI paramete r in t he XNS Adj acent Host Configuration window for each host on an adjacent Frame Relay or SMDS network.

Refer to “Configuring Adjacent Host Pa ramete rs

Configure a static route to the next-hop router for each adjacent host. Refer to “Configuring Static Route Parameters

” in Chapter 4.

2-1

Configuring XNS Services

Configuring a MAC Address on a Token Ring Interface

Any physical int erface (such as LANCE, ILACC, an d FSI) that can run in indiscriminat e mode allows multiple protocols to r egister a media access control (MAC) address for which the protocol software can li sten. Therefore, XNS can register its host number as the MAC address for each interface.

However, if XNS is running over a Token Ring interface, you must enter the host ID in the MAC Address Over r ide parameter and set the MAC Address Select parameter to Cnfg for e ve ry Token Ring interface on which XNS is running, as follows:

Select Circuits > Edit Circuits from the Configuration Manager window.

Select the Token Ring circuit in the Circuit List window and click on

Edit. Select Line s in the Circui t D efinitio n w indo w.

Select the interface from the Edit Lines window and click on Edit.

Enter the router’s XNS host ID in the MAC Address Override parameter

box.

2-2

Set the MAC Address Select pa ra meter to Cnfg in the Token Ring

Parameters window. Repeat steps 2 through 6 for every Token Ring circuit on which XNS is

running.

303548-A Re v 00

Chapter 3

Enabling XNS Services

This chapter describes how to enable XNS services. It assumes you have read Configuring and Managing Routers with Site Manager and that you have

1. Opened a configuration file

2. Specified router hardware if this is a local mode conf iguration file

3. Selected the link or net module connect or on which you are enabling XNS When you enable XNS services, you do not have to configure any XNS

parameters. The Configuration Manager supplies default values for al l XNS parameters. If you want to edit these default value s, r efer to Chapter 4 XNS Parameter s. ”

Enablin g XNS on an Interface

To enable XNS on an interface:

Select XNS from the WAN Proto co ls menu; this menu ap pears after you

select a link or net module connector that requires a WAN circuit.

Protocol prioritization is enabled automatically when you select XNS. For detailed information on protocol prioritization, refer to Configuring Traffic

Filters and Protocol Prioritization.

Click on OK to enab le default XNS Servic es .

The Configurat ion Manager displ ay s the Select Protoc o ls wind ow. Refer to the appropriate protocol-specific guide for information on enabling the protocols you want to run on this interface.

, “Editing

303548-A Rev 00

3-1

Configuring XNS Services

Enabling XNS Serv ices

You enable XNS services from the XNS Configuration window (Figure 3-1). Refer to the parameter descriptions in this se ction to specify the pa rameters. When you have specified all parameters in the window, click on OK to enable default XNS services and to displa y t he next protoc ol-spe cifi c pop- up windo w. T o edit the default values, refer to Chapter 4

, “Editing XNS Parameters,” for instructions.

Figure 3-1. X N S Configurat io n W in dow

Parameter : Network Addres s

Default: None

Options: Any valid XNS network ad dress

Function: Assigns an XNS address in hexadecimal notation to the interface.

Instructions: Enter the XNS address of the interface in hexadecimal nota tion.

MIB Object ID: 1.3.6.1.4.1.18.3.5.10.3.1.6

3-2

303548-A Re v 00

Enabling XNS Services

Parameter: Base Host Number

Default: The Configuration Manager automatically generates a unique 6-byte host

number from the Bay Net works router’s serial number if you do not enter a value. (This automatically generated number is not displayed.)

Options: Any host number

Function: Sets a host ID and source MAC address for all sl ots. By means of this

paramete r, XNS interfaces configured on any slot in the node share the same host ID and source MAC address.

Instructions: Do not ente r a number in this box if you want the Configuration Manager

to generate a host number automatically, or if the interface is on a Token Ring circuit and you are setting the Token Ring Mac Address Select parameter to Boxwide.

Enter the MAC address in hexadecimal notation only if the interface is on a Token Ring circuit and you are setting the Token Ring MAC Address Select parameter to Cnfg. Refe r to the se cti on “Configur ing a MAC

Address on a Token Ring Interface” in Chapter 2 for more information

about this pa rameter.

MIB Object ID: 1.3.6.1.4.1.18.3.5.10.1.4

Note:

If you already have XNS configured on the router, this field does not

appear.

303548-A Rev 00

3-3

Configuring XNS Services

Parameter : Configure RIP

Default: Depends on whether you have RIP configured

Options: Yes

Function: Indicates whether you have RIP configured on this int erface.

Instructions: The Configur ation Manager sets the defaul t value for the Configure RIP

Note:

If you already have XNS configured on the router, this field does not

appear.

Parameter: Implementation

Default: Xerox

Options: Xerox

parameter based on your selection in the Select Protocols window. You can, however, change the value of this parameter as long as the XNS Configura tion window remains in the workstation display.

Function: Specifies the version of XNS you want to add to this circuit. At this time,

your only option is Xerox.

Instructions: Accept the default value.

MIB Object ID: 1.3.6.1.4.1.18.3.5.10.1.6

Note:

You can change the value of the Network Address, Base Host Number, and Implementation parameters only as long as the XNS Configuration window remains in the workstation display. However, once you save the contents of this window, these parameters appear only in the list of XNS interfaces in the XNS option configuration screens. You cannot edit the Network Address parameter in any option configuration screen. To change the network address of a specific XNS interface, you must delete the interface from its circuit, then add the interface again to the same circuit, this time specifying the new network address.

3-4

303548-A Re v 00

Chapter 4

Editing XNS Parameters

Refer to this chap ter w h en you are using Site Manager to

• Access XNS para me te rs

• Edit XNS global parameters

• Edit XNS interface p aram eters

• Edit XNS RIP interfac e pa ram et ers

• Add, edi t, a nd delete adjacent hosts

303548-A Rev 00

• Add, edi t, a nd delete static routes

• Edit XNS traffic filters

• Delete XNS services fro m the ro uter After you successfully enable an XNS interface on the router, you can use Site

Manager to edit XNS parameters and customize XNS services, as described in this chapter.

We assume that you have already added one or more XNS default interfaces to a router configuration file that you now want to edit. (Refer to Configuring and Managing Routers w ith Site Manager if you need to add XNS inte rface s to the configura tion file.)

For each XNS parameter , this chapter provides information about default settings, valid parameter options, the parameter function, inst ructions for setting the parameter, and the management informatio n base (MIB) obj ect ID.

4-1

Configuring XNS Services

The Technician Interface allows you to modify parameters by issuing

commit

commands with the MIB object ID. This process is equivalent to modifying parameters using Site Manager. For more information about using the T echnician Interface to access the MIB, refer to Using Technician Interface Software.

Caution:

The Technician Interface does not verify tha t the value you enter fo r

a parameter is valid. Entering an invalid value can corrupt your configur ation.

Accessing XNS Parameters

You can access all XNS operational parameters from the Conf iguration Manager window (Figure 4-1) Manager if you need instructions on how to access this window.

. Refer to Configuring and Managing Routers with Site

set

and

4-2

Figure 4-1 . Configuration Manager Window

303548-A Re v 00

Editing XNS Global Parameters

To edit XNS Global parameters, begin at the Configuration Manager window

(Figure 4-1):

Select Protocols > XNS > Global.

Editing XNS Parameters

The Edit XNS Global Parameters window appears (Figure 4-2)

Figure 4-2. Edi t XN S Glo bal Parameters Window

Edit those parameters you want to change.

Click on OK to save you r changes and exit the window.

303548-A Rev 00

A description follows of the parameters in the XNS Global Paramete rs window.

4-3

Configuring XNS Services

Parameter : Enable

Default: Enable

Options: Enable

Function: Globally enables or disable s the syst em software mechanisms that allo w

users to add XNS i nte rface s to th e node configuration.

Disable forces every XNS interface existing on the node into the down

(inoperative) state.

Enable reinitializes every XNS interface existing on the node, with each

interface maintai ning the most recent setting of its own

Interface E nab le

of each interface at the time of glob al rei nitialization furth er depends on

the current up/down state of the associated circuit.

Instructions: Select Disable to force every XNS interface existing on the node into the

down (inope rative) state.

Select Enable to globally reinitialize all XNS interfaces configured on the

node, with each i nter face maintaining the most recent setting of its own

Interface E nab le

MIB Object ID: 1.3.6.1.4.1.18.3.5.10.1.2

Disable

Disable parameter. The actual up/down operating state

Disable parameter.

4-4

303548-A Re v 00

Parameter: Host Number

Default: The Configuration Manager automatically generates a unique 6-byte host

number from the Bay Net works router’s serial number if you do not enter

a value. (This automatically generated number does not appear on the

screen.)

Options: Any host number

Function: Sets a host ID and source MAC address for all sl ots. By means of this

paramete r, XNS interfaces configured on any slot in the node share the

same host ID and source MAC address.

Instructions: Do not ente r a number in this box if you want the Configuration Manager

to generate a host number automatically, or if the interface is on a Token

Ring circuit and you are setting the Token Ring MAC Address Select

parameter to Boxwide.

Enter the MAC address in hexadecimal notation only if the i nterface is on

a Token Ring circuit and you are setting the Token Ring MAC Address

Select parameter to Cnfg.

MIB Object ID: 1.3.6.1.4.1.18.3.5.10.1.4

Editing XNS Parameters

Note:

Refer to “Configuring a MAC Address on a Token Ring Interface” in

Chapter 2 for more information about this parameter .

Parameter: Implementation

Default: XEROX

Options: None

Function: Specifies the impl ementation of the XNS protocol on the router.

Instructions: Use the default setting.

MIB Object ID: 1.3.6.1.4.1.18.3.5.10.1.6

303548-A Rev 00

4-5

Configuring XNS Services

Editing XNS Interface Parameters

Any XNS interface you add to a Token Ring circuit acquires from the system a default set of XNS parameter values. You can use the Configuration Manager to enable or disable a specific XNS interface. To access the XNS Interfaces window, begin at the Configur ation Manager window ( refer to Figure 4-1) a nd complete the follo wing steps:

Select Protocols > XNS > In terfaces to display the XNS Interfaces

window (Figure 4-3).

4-6

Figure 4-3. XNS Interfaces Window

303548-A Re v 00

Editing XNS Parameters

The reference for each interface in the list appears in the form

network address, circuit name

where

• The network address of the interface is in hexadecimal format.

• The name of the physic al circuit supporting that interface is in alphanumeric format .

Select the interface you want to modify. The parameter values associated

with that interface appear (lower right) in the parameter windows. Modify the values of thos e paramete rs you want to chang e .

Click on Apply to sa ve your changes.

Click on Done to exit the XNS Interfaces window.

A description of the parameter s in the XNS Interfaces window follows.

Parameter : Enable

Default: The Configuration Manager automatically sets this interface-specific

parameter to Enable when you add XNS support to this interface.

Options: Enable

Disable

Function: Enables or disables XNS routing on this interface.

Instructions: Select Enable if you previously set this parameter to Disable and now

want the interface to support XNS routing. Select Disable only if you want to disable XNS routing ov er thi s interf ace.

MIB Object ID: 1.3.6.1.4.1.18.3.5.10.3.1.2

303548-A Rev 00

4-7

Configuring XNS Services

Parameter: Cost

Default: 0 (for each hop)

Options: 1 to 15

Function: Sets the cost (number of hops) for this interface. This parameter allows

you to configure the shortest path. The cost is added to routes learned on this interface through RIP and is specified in subseque nt RIP packets se nt to other interfac es. X NS d isposes of the packet when its hop count surpasses 15.

Instructions: Enter the inte rface cost value. Standard RIP implementa tion assigns a cost

of 1. Increasing this value causes the RIP Network Diameter to reach the upper bound of 15 more quickly.

MIB Object ID: 1.3.6.1.4.1.18.3.5.10.3.1.7

Parameter: Xsum On

Default: Enable

Options: Enable

Disable

Function: Performs checksumming and compares the checksum to the number in

the Checksum f ield of each XNS p acket. Ho we v er , XNS does not perf orm a checksum on a packet it receives if the value 0xffff is in the Checksum field. If XNS performs a checksum on a packet, a nd its value does not match the value in the Chec ksum field, XNS drops the packet.

Instructions: Select Enable if you want XNS to perfor m checksumming.

Select Disable to byp ass checksumming.

MIB Object ID: 1.3.6.1.4.1.18.3.5.10.3.1.8

Parameter : MAC Address

Default: None (the base host number that you entered when you added XNS to the

circuit overrides the MAC Address paramet er)

Options: Any valid MAC address

Function: Specifies the MAC address of this interface.

Instructions: Lea ve this parameter blank.

MIB Object ID: 1.3.6.1.4.1.18.3.5.10.3.1.10

4-8

303548-A Re v 00

Parameter : SMDS Grou p Address

Default: None

Options: A complete SMDS E.164 address specified by the SMDS subscription

agreement that you ha ve with your SMDS provider

Function: Provides a MA C-layer multicast address for thi s SMDS interface. This

network-level interface parameter overrides the Group Address setting you entered when adding SMDS at the circuit leve l.

Instructions: Leave blank if this interface is not on an SMDS circuit.

Enter the complete SMDS E.164 group address, for example, E16175552876FFFF. If only one telephone number is assigned to the circuit, enter the same telephone number that you entered when you added SMDS to this circuit. You can display this number in the SMDS Interface Param eters w indow. Refer to Configuring SMDS for more information.

MIB Object ID: 1.3.6.1.4.1.18.3.5.10.3.1.11

Editing XNS Parameters

Parameter : External Se rver

Default: Disable

Options: Enable

Disable

Function: Specifies whethe r external server capabi lities are active. If you select

Enable, the interface forwards packets of a particular type to a specific destination.

Instructions: Select Enable to tur n on e xter nal serv er capabil iti es. Select Disa ble to turn

off exte rnal serv er capa bilitie s. Use the Ext Serv Pack etType parameter to specify the packet type . Use the Ext Serv Network, Ext Serv Host ID, and Ext Serv Socke t Num parameters to specify the destination.

MIB Object ID: 1.3.6.1.4.1.18.3.5.10.3.1.13

303548-A Rev 00

4-9

Configuring XNS Services

Parameter : Ext Serv Netwo rk

Default: Enable

Options: Any valid network address

Function: Specifies the net work of the remote server to supply external server

capabilitie s. Use this setting only if you set the External Server parameter to Enable.

Instructions: Enter the netw ork address of the remote server to which you want to

supply externa l server capabilities. Leave bla nk if you are not using external serve r capabilities.

MIB Object ID: 1.3.6.1.4.1.18.3.5.10.3.1.14

Parameter: Ext Serv Host ID

Default: 0

Options: Any valid host ID

Function: Specifies the host ID of the remote server to supply external server

capabilitie s. Use thi s setting only if the External Server paramete r is set to Enable.

Instructions: Enter the host ID of the remote server to which you want to supply

external ser ver capabilities. Leave bla nk if you are not using external serve r capabilities.

MIB Object ID: 1.3.6.1.4.1.18.3.5.10.3.1.15

4-10

303548-A Re v 00

Parameter : Ext Serv Packet Type

Default: None

Options: Any valid pack et type

Function: Specifies the packe t type of the service requests to forward to the remote

server. Use this setting only if the External Server parameter is set to Enable.

Instructions: Enter the packe t type of the service requests to forwa rd to the remo te

server. Leave bla nk if you are not using external serve r capabilities.

MIB Object ID: 1.3.6.1.4.1.18.3.5.10.3.1.16

Parameter : Ext Serv Soc ket Num

Default: None

Options: Any valid destination socket number

Function: Specifies the dest ination socket number of the remote server to which to

forward service requests. Use this setting only if the External Server parameter is set to Enable.

Editing XNS Parameters

Instructions: Lea ve blank if you are not using external se rver capabilities or if you are

using external server capabilities and you want to forward all packets of the specifi ed type that this interface receives to the specified remo t e server.

Otherwise, enter the destination socket number of the remote server to which to forward servic e requ ests.

MIB Object ID: 1.3.6.1.4.1.18.3.5.10.3.1.17

303548-A Rev 00

4-11

Configuring XNS Services

Parameter: WAN Broadcast

Default: ffffff (not displayed)

Options: Default value or a user-specified Frame Relay broadcast address

Function: Specifies a Frame Relay broadcast address for this XNS interface.

Instructions: Lea ve blank to accept the default value. With the defaul t value, the router

sends all broadcast tra ffic through all logical connections associated with the XNS interface you are configuring.

Enter a Frame Relay broadcast address to send all broadcast traffic through the XNS interface you are configurin g.

MIB Object ID: 1.3.6.1.4.1.18.3.5.10.3.1.28

Parameter: WAN Multicast

Default: ffffff (not displayed)

Options: Default value or a user-specified Frame Relay multicast a ddress

Function: Specifies a Frame Relay multi cast address for this XNS interface.

Instructions: Lea ve blank to accept the default value. With the defaul t value, the router

sends all multicast traffic through all logical connections associated with the XNS interface you are configuring.

Enter a Frame Relay multi cast address to s end all m ulti cast tr af f ic t hrough the XNS interface you are configuring.

MIB Object ID: 1.3.6.1.4.1.18.3.5.10.3.1.29

4-12

303548-A Re v 00

Parameter: Split Horizon Algorithm

Default: Enable

Options: Enable

Function: When the interface forwards RIP and SAP updates, it can exclude RIP

and SAP broadcast updates learned on that interface.

Instructions: Select Enable if you previously set this parameter to Disable and now do

not want the router to transmit RIP and SAP updates received fr om the interface over that interface.

Select Disable only if you want the router to transmit RIP and SAP updates it receives from the interface over that interface.

MIB Object ID: 1.3.6.1.4.1.18.3.5.10.3.1.30

Disable

Editing RIP Interface Parameters

If you enable RI P on an XNS interface, you can edit its RIP parameters by accessing the XNS RIP Interfaces window. (The following instructions describe a RIP-enabled XNS interface as an XNS RIP interface.)

Editing XNS Parameters

303548-A Rev 00

For instructions on how to add an XNS RIP interface to a circuit, refer to Configuring and Managing Routers with Site Manager. To edit the configurable RIP parameters of an XNS interface, begin at the Configuration Manager window (refer to Figure 4-1):

Select Protocols > XNS > RIP Interfaces.

The XNS RIP Interfaces windo w app ears (Figure 4-4) the upper left a list of all XNS RIP interfaces configured on the selected circuit.

. The window shows at

4-13

Configuring XNS Services

4-14

Figure 4-4. XNS RIP Interfaces Window

Select the int erfa c e you want to edit by clic ki ng o n the a pp rop riat e entr y

in the list of RIP interfaces. Click on any para m ete r valu e you wan t to chan g e; the n en ter a new

value. Click on Apply to sa ve your changes.

Click on Done to exit the XNS RIP Interfaces window.

A description of the parameter s in the XNS RIP Interfaces window follows.

303548-A Re v 00

Parameter : Enable

Default: Enable

Options: Enable

Function: Specifies whethe r you enabled the Routing Information Protocol on this

XNS interface.

Instructions: Select Enable to enable RIP on this interface.

Select Disable to disable RIP on this interface.

MIB Object ID: 1.3.6.1.4.1.18.3.5.10.4.1.2

Parameter : Supply

Default: Enable

Options: Enable

Function: Specifies whether the interface transmits all RIP updates to routers in

neighboring networ ks.

Disable

Editing XNS Parameters

Instructions: Select Enable to configure the interface to transmit all RIP updates.

Select Disable to prohibit the interface from transmitting all RIP updates.

MIB Object ID: 1.3.6.1.4.1.18.3.5.10.4.1.5

303548-A Rev 00

4-15

Configuring XNS Services

Parameter : Listen

Default: Enable

Options: Enable

Function: Specifies whethe r this interface listens to RIP updates from neighboring

networks.

Instructions: Sel ect Enable to configur e this XNS interface to listen to RIP updates, and

to convey received routing information to its internal routing table. Select Disable to configure this XNS interface to ignore RIP updates from

neighboring routers. Disabling RIP also prevents this interface from conveying any received routing information to its internal routing table.

MIB Object ID: 1.3.6.1.4.1.18.3.5.10.4.1.6

If you set this parameter to Enable, a route filter can still prohibit the

Note:

interface from updating its internal routing tables.

Disable

Configuring Adjacent Host Parameters

4-16

The sections tha t follow describe how to add, edit, and delete adjacent host routes in a Bay Networks router configuration. You perform these actions via the XNS Adjacent Hosts window.

To access the Adjacent Hosts window, begin at the Configuration Manager window (refer to Figure 4-1) and select Protocols > XNS > Adjacent Hosts. The XNS Adjacent Hosts window appe ars ( Figure 4-5) Hosts currently assoc iated with a specific Host ID. (The Host ID is a global parameter for XNS interfaces defined on any slot.)

, showing a list of all Adjacent

303548-A Re v 00

Editing XNS Parameters

Figure 4-5. X N S Adj ac ent Hosts Wi ndow

Adding an Adjacent Host

To add an adjacent host, begin from the XNS Adjacent Hosts window

(Figure 4-5):

Click on Add.

The Adjacent Host Confi guration window appears (Figure 4-6)

303548-A Rev 00

4-17

Configuring XNS Services

Figure 4-6. Adjacent Host Configuration Window

4-18

Enter hexadecimal values for the Target Host Network and Host ID

parameters.

After you enter appropriate values, these parameters are a vailable for viewing as statistics only.

Enter hexa dec im a l value s for the Next H op In terf a ce a nd the DLC I , if

appropriate.

Refer to the descriptions at the end of this section for information about these parameters.

Click on OK to save your entries to the co n figura ti on file.

The XNS Adjacent Hosts window (refer to Figure 4-5) reappears.

A description of the parameter s in the Adjacent Host Configuration window follows.

303548-A Re v 00

Parameter : Ta rget Ho s t Netw o rk (hex )

Default: None

Options: Valid network address of the adjacent host

Function: Specifies the net work address of the adjacent host.

Instructions: Enter a network a ddress of up to 8 hexadecimal characters.

MIB Object ID: 1.3.6.1.4.1.18.3.5.10.5.1.3

Parameter: Host ID (hex)

Default: None

Options: Valid host ID of the adjacent host

Function: Specifies the Host ID of the device you want to configure as an adjacent

host.

Instructions: Enter a Host ID of up to 12 hexadecimal characters.

MIB Object ID: 1.3.6.1.4.1.18.3.5.10.5.1.4

Editing XNS Parameters

Parameter : Next Hop Interface (hex)

Default: None

Options: Configured network address of the next hop

Function: Specifies the network address of the next- hop interface.

Instructions: Enter a network a ddress of up to 8 hexadecimal characters.

MIB Object ID: 1.3.6.1.4.1.18.3.5.10.5.1.5

303548-A Rev 00

4-19

Configuring XNS Services

Parameter : DLCI (he x)

Default: None

Options: Data Link Control Identifier

Function: Identifies the virtual circuit in a Frame Relay or SMDS network.

Instructions: Enter a loc ally significant DLCI of up to 1 6 hexadecimal characters if the

interface is on a Frame Relay or SMDS network. Leave bla nk if the interface is not on a Frame Relay or SMDS network.

MIB Object ID: 1.3.6.1.4.1.18.3.5.10.5.1.6

Caution:

The router cannot pass traffic through an interface to an adjacent host on a Frame Relay or SMDS network if the adjacent host is configured without the correct DLCI.

Editing an Adjacent Host

You can edit the configurable parameters of an Adjacent Host entry in the node configura tion. The Configuration Manager does not allow you to change the Target Host Network and Host ID parameters you set in any Adjacent Host Configura tion window. To establish new values for these parameters, you must delete that host and configure a new host. You can, however, reconfigure all other parameters associa ted with an adjacent host.

To edit the configurable parameters associated with an existing adjacent host, begin at the Configur ation Manager window ( refer to Figure 4-1) a nd select Protocols > XNS > Adjacent Hosts.

From the XNS Adja cent Hosts window (refer to Figure 4-5):

Select the adjacent host you want to edit. Click on the appropriate entry

in the list of Adjacent Hosts. Click on any para m ete r valu e you wan t to chan g e; the n en ter a new

value.

4-20

Click on Apply to sa ve your changes.

Click on Done to exit the XNS Adjacent Hosts window.

A description of parameters in the XNS Adjacent Hosts window follows.

303548-A Re v 00

Parameter : Enable

Default: The Configuration Manager automatically sets this pa rameter to Enable

when you click on Add in the XNS Adjacent Hosts window.

Options: Enable

Disable

Function: Specifies whethe r the selected adjacent host record is enabled or disabled

in the XNS routing tab les. The router does not consider any adjacent host record you disable.

Instructions: Select Disable to make the adjacent host record inactive in the XNS

routing table; the route r will not consider this adjacent host. Select Enable to make the adjacent host record active again in the XNS

routing table.

MIB Object ID: 1.3.6.1.4.1.18.3.5.10.5.1.2

Parameter : Next Hop Intf

Default: None

Editing XNS Parameters

Options: Configured network address of the next hop

Function: Specifies the network address of the next- hop interface.

Instructions: Enter a network a ddress of up to 8 hexadecimal characters.

MIB Object ID: 1.3.6.1.4.1.18.3.5.10.5.1.5

303548-A Rev 00

4-21

Configuring XNS Services

Parameter : DLCI

Default: None

Options: Data Link Control Identifier

Function: Identifies the virtual circuit in a Frame Relay or SMDS network.

Instructions: Enter a loc ally significant DLCI of up to 1 6 hexadecimal characters if the

interface is on a Frame Relay or SMDS network. Leave bla nk if the interface is not on a Frame Relay or SMDS network.

MIB Object ID: 1.3.6.1.4.1.18.3.5.10.5.1.6

Caution:

The router cannot pass traffic through an interface to an adjacent host on a Frame Relay or SMDS network if the adjacent host is configured without the correct DLCI.

Deleting an Adjacent Host

To delete an adjacent host:

From the XNS Adjacent Hosts window (Figure 4-5), select the ad jacent

host you want to dele te from th e no de configuration. Click on Delete.

The system software delete s the Adjacent Host entry you selected, and the entr y disappears from the list of adjacent hosts in the XNS Adjacent Hosts window.

Configuring Static Route Parameters

XNS static routes are user-specified transmission paths that XNS internet packets follow. You configure static routes whe n you want to re strict the paths that pa cke ts can follow. Static routes, like routes learned through RIP, appear in the X NS routing table. Unlike routes learned through RIP, however, static routes do not time out. Static routes remai n in the XNS routing table until you reconfigure them manually.

4-22

303548-A Re v 00

Editing XNS Parameters

The sections that follow show you how to add, edit, and delete XNS static routes in a Bay Networks router configuration. You perform these functions from the XNS Static Routes windo w. Begin at the Configuration Manager window

(Figure 4-1)

and select Protocols > XNS > Static Routes. The XNS Static Routes

window appears (Figure 4-7).

303548-A Rev 00

Figure 4-7. X N S St at ic Routes Window

Caution:

T o establish a data link layer connection in a Frame Relay or SMDS network, which allows the router to send packets over a static route, you must configure an adjacent host and edit the DLCI parameter in the XNS Adjacent Hosts window.

4-23

Configuring XNS Services

Adding a Static Route

To add a static route, begin at the XNS Static Routes window (Figure 4-7):

Click on Add.

The XNS Add Static Route window appears (Figure 4-8)

Figure 4-8. XNS Add Static Route Window

Enter values for the Target Network and Next Hop Network parameters.

4-24

After you enter appropriate v alue s, those paramete rs are av ai lable for viewi ng as statistics only. Use the descriptions that follow as a guide.

Click on OK to save your entries.

The XNS Add Static Route window (Figure 4-8)

reappear s.

303548-A Re v 00

Parameter : Ta rget N etw ork (hex)

Default: None

Options: Any valid network address in hexadecimal nota tion

Function: Specifies the address of the network to which you want to configure the

static route.

Instructions: Enter a network a ddress of up to 8 hexadecimal characters.

MIB Object ID: 1.3.6.1.4.1.18.3.5.10.6.1.3

Parameter : Next Hop Network (hex)

Default: None

Options: Any valid network address in hexadecimal nota tion

Function: Specifies the network address of the next hop.

Instructions: Enter a network a ddress of up to 8 hexadecimal characters.

MIB Object ID: 1.3.6.1.4.1.18.3.5.10.6.1.5

Editing XNS Parameters

Editing a Static Route

You can edit the config urable paramet ers of a st ati c route t hat you sp ecif ied e arli er in the node configuration. The Configuration Manager does not allow you to reconfi gure the T arget Network and Next Hop Network parameters for a static route. If you want to change these parameters, you must delete the st atic route and add a new route with the proper information. However, you can reconfigure all other parameters asso ci ated with a static route.

To edit the configurable parameters associated with an existing sta tic route, begin at the Configuration Manager window (Figure 4-1) Static Routes. The XNS Stati c Routes windo w appe ars (refe r to Figure 4-7). From this window:

Select the static route you want to edit. Click on the appropriate entry in

the list of static rou tes. Click on any parameter value you want to change; enter a new value.

Click on Apply to sa ve your changes.

Click on Done to exit the XNS Static Routes window.

303548-A Rev 00

and select Protocols > XNS >

4-25

Configuring XNS Services

A description of parameters in the XNS Static Routes window follows.

Parameter : Enable

Default: The Configuration Manager automatically sets this pa rameter to Enable

when you click on Add in the XNS Static Routes window.

Options: Enable

Disable

Function: Specifies the sta te (acti v e or inac tiv e) of the static r oute r ecord in the XNS

routing tables.

Instructions: Select Di sable to make the sta tic route record inactive in the XNS routing

table; the r outer will not consider this static route. Select Enable to make the static route record active in the XNS routing

table.

MIB Object ID: 1.3.6.1.4.1.18.3.5.10.6.1.2

Parameter: Cost

Default: 0 router hops

Options: 0 to 15 router hops

Function: Specifies the number of router hops added to an XNS data packet. The

router uses this paramete r when determinin g the best r oute for a datagram to follo w. The cost is also propa gated t hro ugh RIP. The default setti ng of 0 for static routes gives them priority over RIP-learned routes.

Instructions: Enter the number of router hops.

MIB Object ID: 1.3.6.1.4.1.18.3.5.10.6.1.4

Parameter : Next Hop Host

Default: None

Options: Any valid host address in hexadecimal notation

Function: Specifies the addre ss of the next host in the static routing path.

Instructions: Enter a host addres s of up to 12 hexa decimal characters.

MIB Object ID: 1.3.6.1.4.1.18.3.5.10.6.1.6

4-26

303548-A Re v 00

Deleting a Static Route

To delete an XNS static route:

From the XNS Static Routes window (Figure 4-7), select the static route

you want to delete from the node configuration. Click on Delete.

The system software deletes the static route entry you selected, and the entry disappears from the XNS Static Routes window.

Editing XNS Traffic Filters

Traffic filters allow you to control network traffic on configured network interface s. You can configure traff ic filters to drop inboun d protocol-specific network packets and datagrams when they arrive at a configured network interface on the router. You can al so configure these filters to accept outbound traffic and forward it to specific destination nodes on the network. XNS traffic filters, for example, allow to you to drop, accept, or forward XNS packets on those interfaces that you configur e for XNS.

Editing XNS Parameters

303548-A Rev 00

For informatio n about traffi c filters for XNS and other protocols that support this capability, refer to Configuring Traffic Filt ers and P roto c o l Prioritization.

To delete XNS from the node, begin at the Configuration Manager window (refer to Figure 4-1) and complete the following steps:

Select Protocols > XNS > Delete XNS.

A confirmation window appears.

Select OK.

The Configuration Manager window appears.

XNS is no longer configured on the Bay Networks router.

4-27

Appendix A

Site Manager Default Settings

Tables A-1 to A-5 describe the Site Manager default parameter sett ings for the Xerox Networking Syste m (XNS) protocol and for XNS RIP.

Table A-1. X NS Gl ob a l Parameters

Parameter Default

Enable Enable Host Number None Implementation Xerox

303548-A Rev 00

Table A-2. X NS Interface Parameters

Parameter Default

Enable Enable Cost 0 Xsum On Enable MAC Address None SMDS Group Address None External Server Disable Ext Serv Network Enable Ext Serv Host ID 0 Ext Serv Packet Type None Ext Serv Socket Num None

(continued)

A-1

Configuring XNS Services

Table A-2. X NS Interface Parameters

Parameter Default

WAN Broadcas t ffffff WAN Multicast ffffff Split Horizon Algorith m Enable

(continued)

Table A-3. X NS RIP Interface Parameters

Parameter Default

Enable Enable Supply Enable Listen Enable

Table A-4. XNS Adjacent Host Parameters

Parameter Default

Target Host Network (hex) None Host ID (hex) None Next Hop Interface (hex) None DLCI (hex) None Enable Enable Next Hop Intf None DLCI None

A-2

Table A-5. XNS Static Route Parameters

Parameter Default

Target Network (hex) None Next Hop Network (hex) None Enable Enable Cost 0 Next Hop Host None

(continued)

303548-A Re v 00

Site Manager Default Settings

Table A-5. XNS Static Route Parameters

Parameter Default

Next Hop Interface None DLCI None

(continued)

303548-A Rev 00

A-3

Index

acronyms, xiii

adjacent host parameters

4-17

4-22

4-20

1-11

adjacent hosts

adding deleting editing

4-16

broadcasts, 1-6

configurable split horizon algorithm, 1-13

configuration notes conventions, text

2-1

xii

defaults

XNS para meters

DLCI (Data Li nk Connection Identif ier)

2-1, 4-18, 4-20, 4-22, 4-23

A-1

1-9, 1-11

filters, 4-27

Frame Relay

fully mesh ed netwo rk non-fully meshed network

fully mesh ed netwo rk

1-11, 2-1, 4-12, 4-23

1-13

1-14

implement ation notes, 2-1

indiscriminate mode

2-2

medi a ac c ess cont r ol (MAC), 2-2

non-fully meshed network, 1-13

OSI prot ocol stack, 1-2

1-14

E.164 address, 4-9 Echo Proto col

XNS, description educational service s Error Protocol

XNS, description

XNS, numbers external server

XNS, description

303548-A Rev 00

, ,

1-7

1-7 xv

1-6

1-8

Packet Exchange Protocol, 1-8 parameters

adjacent host

DLCI

4-20, 4-22

Enable

4-21

Host ID Next Hop Interface T arget Host Network

editing adjacent host

4-19

4-19, 4-21

4-19

4-16

Index-1

parameters (continued)

4-8

4-26

1-2

1-2, 1-3

1-2, 1-4

1-3, 1-4

1-3

4-7

4-15

4-16

4-15

4-26

4-3

4-22

4-5

4-8

4-12

4-8

4-26

4-25

3-4

editing global

editing RIP interface

editing static route

global

Host Number

interface

Checksum on Cost Enable External Server Enable External Server Host ID External Server Network External Server Packet Type Externa l Server Socket Number MAC Address SMDS Group Addr ess Split Horizon Algorithm WAN Broadcast WAN Multicast Xsum on

RIP interface

Enable Listen Supply

static route

Cost Enable Next Hop Host Next Hop Network Target Network

XNS

Base Host Number Configure RIP Implementation Network Address (hex )

1-8

PEP product support protocol stack

OSI

1-2

XNS protocols

Level 0

Level 1

Level 2

Level 3

Level 4

4-12

4-25

3-3

publications, Bay Networks

RIP

request response

1-6

2-1

1-5

1-4

broadcasts configuring without packet type

4-9

4-10

4-11

RIP (Routing Information Protocol) Routing Information Protocol

XNS, description

4-9

4-13

3-2

Sequence d Packet Protocol, 1-8

Site Manager SMDS split ho r iz on

fully mesh ed netwo rk non-fully meshed network purpose support

1-8

SPP static route

adding deleting

editing static routes static transmission path s support , Bay Networks

4-1

1-9, 1-11, 2-1, 4-9, 4-23

1-13

1-14

4-24

4-27

4-25

1-9

1-11

1-13

1-14

technical publications, xv

technical support text conventions The Gray Book Token Ring traffic filters

xii

1-1

2-2, 4-5, 4-6

4-27

Index-2

303548-A Re v 00

WAN, 1-6, 1-11, 2-1

Broadcast Multicast

4-12

Xerox Network Systems

see XNS

XNS

1-1 acces si n g parame ters adjacent host, de scription Comparison to OSI confi guring filters for, se e filtering deleting from the Bay Networks router Echo Proto col, description editi ng adjacent host parame ters editi ng global parameters editing static route parameters enabli ng on a circuit Error Pr otocol, description Error Pr otocol, numbers external server, description level 0 services level 1 services level 2 services MAC ad dress on a Token R ing Packe t Exchange Protocol parameters

Configure RIP description of, see parameters Implementation

Network Address (hex ) protocol stack Routing Information Protocol (RIP), descr iption

1-4 Routing Information Protocol, configurin g w ithout

2-1 Sequence d Packet Protocol static routes, description

4-2

1-11

1-2

4-27

1-7

4-16

4-3

4-22

3-2

1-6

1-7

1-8

1-3

1-4

2-2

1-8

3-4

3-2

1-2

1-8

1-9

303548-A Rev 00

Index-3

Avaya XNS User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Configuring XNS Services

Contents

Figures

Tables

Before You Begin

Preface

Text Conventions

Acronyms

Bay Netwo rks Technical Publicati o ns

How to Get Help

XNS Protocol Stack

Protocol Layer/Level Support

Level 0

Level 1

Level 2

XNS RIP Over v iew

Error Protocol

Echo Protocol

Sequenced Packet Protocol

Packet Excha n ge Proto c o l

External Ser vers

Static Routes

Adjacent Hosts

Configurable Split Horizon

For More Information about XNS

Configuring XNS Without RIP

Configuring a MAC Address on a Token Ring Interface

Enablin g XNS on an Interface

Enabling XNS Serv ices

Accessing XNS Parameters

Editing XNS Global Parameters

Editing XNS Interface Parameters

Editing RIP Interface Parameters

Configuring Adjacent Host Parameters

Adding an Adjacent Host

Editing an Adjacent Host

Deleting an Adjacent Host

Configuring Static Route Parameters

Adding a Static Route

Editing a Static Route

Deleting a Static Route

Editing XNS Traffic Filters

Index