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

+ 50 hidden pages

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