#EDIR DATA#
DOCTYPE='BOOK' PUBLICID='' SYSTEMID='/dtd/docbook.dtd'NLSP Migration GuideNLSP Migration GuideNovell, Inc.DisclaimerNovell, Inc. makes no representations or warranties with
respect to the contents or use of this manual, and specifically
disclaims any express or implied warranties of merchantability or
fitness for any particular purpose. Further, Novell, Inc. reserves the
right to revise this publication and to make changes to its content,
at any time, without obligation to notify any person or entity of such
revisions or changes.Further, Novell, Inc. makes no representations or warranties
with respect to any NetWare software, and specifically disclaims any
express or implied warranties of merchantability or fitness for any
particular purpose. Further, Novell, Inc. reserves the right to make
changes to any and all parts of NetWare software, at any time, without
any obligation to notify any person or entity of such changes.TrademarksThe following are registered trademarks of Novell, Inc.: DR DOS, Fastpath, LAN WorkPlace, LANalyzer, NetWare, NetWare Name Service, Novell Press, UnixWare, WordPerfect.UNIX is a registered trademark of Novell, Inc. in the United States and other countries, licensed exclusively through X/Open Company, Ltd.The following are trademarks of Novell, Inc.: Advanced NetWare, Enterprise Certified NetWare Engineer, ECNE, EXOS, FirstMail, Global MHS, HSM, Hardware Specific Module, Hot Fix, IPX, IPX/SPX, IPXWAN, Internetwork Packet Exchange, LSL, Link Support Layer, MLI, MLID, MSL, MSM, MacIPX, MacNCP, MacNDS, Media Support Module, Mirrored Server Link, Multiple Link Interface, Multiple Link Interface Driver, NCP, NDR, NDS, NE/2, NE/2-32, NE1000, NE1500T, NE2000, NE2100, NE3200, NE32HUB, NLM, NLSP, NMS, NSE Pro, NTR2000, NVT, NetSync, NetWare 3, NetWare 4, NetWare 4.01, NetWare 4.1, NetWare Application Notes, NetWare Care, NetWare Client, NetWare Core Protocol, NetWare DOS Requester, NetWare Directory Services, NetWare Express, NetWare IPX Router, NetWare Link Services Protocol, NetWare Link/Frame Relay, NetWare Link/PPP, NetWare Link/X.25, NetWare Loadable Module, NetWare Logotype (teeth logo), NetWare MHS, NetWare Management Agent, NetWare Management System, NetWare Message Handling Service, NetWare MultiProtocol Router, NetWare Navigator, NetWare Peripheral Architecture, NetWare Ready, NetWare Requester, NetWare Runtime, NetWare SFT, NetWare SFT III, NetWare Tools, NetWare UAM, NetWare/IP, Netware Notify, Network Support Encyclopedia Professional Volume, Novell Labs, Novell Research Reports, Novell Virtual Terminal, ODI, Open Data-Link Interface, Packet Burst, Personal NetWare, RX-Net, RXNet/2, Red Box, SFT, SFT III, SMS, SPX, Sequenced Packet Exchange, Storage Management Services, Streams, TSM, Topology Specific Module, Transaction Tracking System, TTS, VLM, Virtual Loadable Module, "Yes, It Runs With NetWare Logo", and the "Yes, NetWare Tested and Approved Logo".The following are registered service marks of Novell, Inc.: Novell Technology Institute, NetWire.The following are service marks of Novell, Inc.: Novell Registry, Certified NetWare Administrator, CNA, Certified NetWare Engineer, CNE, Certified NetWare Instructor, CNI, Novell Authorized Service Center, NASC, Novell Technical Support.The following are collective marks of Novell, Inc.: Novell Authorized Reseller, Technical Support Alliance, TSA.3Com, 3+Share, and TokenLink are registered trademarks of 3Com Corporation.4.3BSD is a trademark of the Regents of University of California, Berkeley.ARCnet is a registered trademark of Datapoint Corporation.AT is a registered trademark of International Business Machines Corporation.AT&T is a registered trademark of American Telephone & Telegraph.Adobe and PostScript are registered trademarks of Adobe Systems Incorporated.Apple, AppleShare, AppleTalk, EtherTalk, ImageWriter, LaserWriter, LocalTalk, Macintosh, and MultiFinder are registered trademarks, and Finder and Mac are trademarks, of Apple Computer, Inc.Btrieve is a registered trademark of Btrieve Technologies, Inc.Canon is a registered trademark of Canon, Inc.COMPAQ is a registered trademark of COMPAQ Computer Corporation.Cisco Systems is a trademark of Cisco Systems, Inc.Citizen is a registered trademark of Tokei Kabushiki Kaisha.Claris is a trademark and MacWrite is a registered trademark of Claris Corporation.CompuServe is a registered trademark of CompuServe, Inc.DEC, DECnet, and Digital are trademarks of Digital Equipment Corporation.DeskJet, DeskWriter, LaserJet, PaintJet, PaintWriter, and PCL are registered trademarks of Hewlett-Packard Company.Diablo is a registered trademark of Xerox Corporation.DynaText is a registered trademark of Electronic Book Technologies, Inc.Epson is a registered trademark of Seiko Epson Corporation.EtherPrint is a trademark of 3Com Corporation.TokenPrint is a registered trademark of Dayna Communications.EtherFlex is a registered trademark of Extended Systems International.GatorBox is a registered trademark of Cayman Systems.Hewlett Packard, HP, HP-GL, LaserJet, and PCL are registered trademarks of Hewlett-Packard Company.Hayes is a registered trademark of Hayes Microcomputer Products, Inc.IBM, OS/2, Micro Channel, ProPrinter, and PS/2 are registered trademarks and AFP, Presentation Manager, and SAA are trademarks of International Business Machines Corporation.Intel is a registered trademark and Pentium is a trademark of Intel Corporation.LaserBridge is a registered trademark of Sonic Systems.Lotus is a registered trademark of Lotus Development Corporation.MS-DOS and Microsoft are registered trademarks and LAN Manager is a trademark of Microsoft Corporation.MacPlot is a registered trademark of Microspot.NEC, Spinwriter, and Pinwriter are registered trademarks of NEC Corporation.NFS is a registered trademark of Sun Microsystems, Inc.Okidata and MicroLine are registered trademarks of Oki Electric Industry Co., Ltd.PageMaker is a registered trademark of Aldus Corporation.Panasonic is a registered trademark of Panasonic Office Automation.PowerPrint is a trademark of GDT Softworks, Inc.SQL Server is a trademark of Sybase, Inc.SprintTalk is a registered trademark of Digital Products.Ultra is a trademark of Hayes Microcomputer Products, Inc.Unicode is a registered trademark of Transoft Ltd.Word is a registered trademark of Microsoft Corporation.XT is a trademark of International Business Machines Corporation.Xerox is a registered trademark and XNS is a trademark of Xerox Corporation.cc:Mail is a trademark of cc:Mail, a Division of Lotus.All other trademarks, service marks, certification marks, and
collective marks --- registered or not --- are the property of their
respective owners.Copyright Notices© Copyright 1983-1994 Novell, Inc. All rights reserved. No
part of this publication may be reproduced, photocopied, stored on a
retrieval system, or transmitted without the express written consent
of the publisher.TYPE="VERT"Novell, Inc.122 East 1700 SouthProvo, UT 84606U.S.A.User Comment FormNovell encourages and welcomes your feedback and suggestions on ways we can improve our manuals. You can help us by sharing your comments and suggestions about how our manuals could be made more useful to you, and about any inaccuracies or information gaps they contain.Submit your comments by printing this User Comment form (click on the icon to display the form, then select "Print" from the "File" menu), filling it in, then faxing or mailing it to us.LABEL="0" FLOAT="0"User Comment FormFILEREF="ucomment.tif"PAGENUM=9 ID="BP1"About This GuideThis guide provides the information you need to implement NetWare® Link Services ProtocolTM (NLSPTM) software in a Novell® Internetwork Packet ExchangeTM (IPXTM) internetwork. Implementing NLSP in a RIP-based IPX network, a process known as migration, involves adding NLSP link state routing functionality to NetWare servers and dedicated routers. In most cases, NLSP can eventually replace Routing Information Protocol (RIP), the routing protocol that NetWare has traditionally used to carry out network-level operations.This guide is written for network managers, administrators, and consultants responsible for planning, installing, and managing an IPX internetwork.RENDERAS="SECT1"Chapter SummariesThis section briefly summarizes each chapter in this guide. Use these summaries to help you locate specific topics, or to help you decide which portions of this guide contain new information.IDREF="FM22213"Chapter 1, "NetWare Link Services Protocol," presents a brief technical overview of NLSP.IDREF="FM66347"Chapter 2, "Why You Should Migrate Your IPX Network from RIP to NLSP," is a benefits-oriented chapter that focuses on what NLSP can do for your network. It also answers some commonly asked questions about NLSP.IDREF="FM47651"Chapter 3, "Trying Out NLSP on Your IPX Network," is for the busy---or skeptical---network professional who wants to "test drive" NLSP before implementing it throughout an entire network.PAGENUM=9 ID="BP2"PAGENUM=10IDREF="FM89629"Chapter 4, "Developing a Migration Strategy," helps you develop a strategy for migrating your network that is both comprehensive and easy to implement. If you are already familiar with NLSP and want to start migrating your network, see this chapter first.IDREF="FM88235"Chapter 5, "Partitioning an Internetwork into Routing Areas," provides guidelines for creating administrative domains called routing areas. Read this chapter only if you are migrating a very large IPX internetwork or if you want to filter routes and services between NetWare LANs.IDREF="FM79804"Chapter 6, "Migrating a Network with Different NetWare Versions," explains how to migrate or interoperate with servers running NetWare 2 software, NetWare 3TM software, or NetWare 4TM software.IDREF="FM38483"Chapter 7, "Migrating a Network with Products That Require RIP and SAP," explains how to configure a NetWare server or dedicated router running NLSP so that it can interoperate with Novell products that still rely on RIP and SAP.RENDERAS="SECT1"Conventions Used in This GuideThe NetWare 4.1 NLSP Migration Guide uses the documentation conventions described in this section. The following sections describe the conventions used:MARK=BULLETIDREF="FM22964""Parameter Paths"IDREF="FM65437""Terminology"IDREF="FM82010""New Terms and Important Information"IDREF="FM96771""System Messages"IDREF="FM61200""User Input"IDREF="FM88050""Special Characters"IDREF="FM50216""Graphic Symbols"PAGENUM=11 ID="BP3"RENDERAS="SECT2"ID="FM22964"Parameter PathsThis guide uses a special format to show the path to a parameter. For example, rather than specifying "Load INETCFG; from the CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu, select CLASS=MENUITEM MOREINFO="NONE"Protocols; from the CLASS=MENUITEM MOREINFO="NONE"Protocol Configuration menu, select CLASS=MENUITEM MOREINFO="NONE"IPX; from the CLASS=MENUITEM MOREINFO="NONE"IPX Protocol Configuration menu, select CLASS=MENUITEM MOREINFO="NONE"Static Routes for On-Demand Calls (the CLASS=MENUITEM MOREINFO="NONE"Static Routes for On-Demand Calls menu appears); then press MOREINFO="NONE"<Insert> (the CLASS=MENUITEM MOREINFO="NONE"Static Route Configuration menu appears)," the following format is used:Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"Static Routes for On-Demand Calls (CLASS=MENUITEM MOREINFO="NONE"Static Routes for On-Demand Calls menu appears) > Press MOREINFO="NONE"<Insert> (CLASS=MENUITEM MOREINFO="NONE"Static Route Configuration menu appears)The name of the menu that appears after each selection is specified only if it is not obvious.RENDERAS="SECT2"ID="FM65437"TerminologyThe following terms summarize frequently performed actions:MARK=BULLET"Select" means to use the cursor keys to highlight an item and press MOREINFO="NONE"<Enter>. "Enter" means to type the indicated text and press MOREINFO="NONE"<Enter> (as one complete operation). It is shown in one of two ways; for example:Enter MOREINFO="NONE"LOAD MOREINFO="NONE"INETCFG or MOREINFO="NONE"LOAD INETCFG MOREINFO="NONE"<Enter>RENDERAS="SECT2"ID="FM82010"New Terms and Important InformationHighlighting emphasizes new terms and important information.PAGENUM=11 ID="BP4"PAGENUM=12RENDERAS="SECT2"ID="FM96771"System MessagesRegular (nonboldface, nonitalic) monospaced character strings represent system prompts or responses; for example:FORMAT="LINESPECIFIC"MOREINFO="NONE"message exampleRENDERAS="SECT2"ID="FM61200"User InputThis guide uses the following conventions to denote user input:MARK=BULLETMOREINFO="NONE"Highlighted monospaced character strings represent user input, which must be entered exactly as shown; for example:FORMAT="LINESPECIFIC"MOREINFO="NONE"MOREINFO="NONE"LOAD INETCFG MOREINFO="NONE"<Enter> or MOREINFO="NONE"Load inetcfg MOREINFO="NONE"<Enter>Highlighted and lowercase character strings show descriptive names for items that you must replace with appropriate values. For example, in the following NetWare console command, you replace driver with the specific name of a driver:FORMAT="LINESPECIFIC"MOREINFO="NONE"UNBIND IPX FROM driver MOREINFO="NONE"<Enter>RENDERAS="SECT2"ID="FM88050"Special CharactersThis guide uses special characters to denote the following:MARK=BULLETAsterisks * in text denote third-party trademarks.Angle brackets < >, brackets [ ], braces { }, vertical bar |, parenthesis ( ), and quotation marks " are used as metacharacters and, as such, you must not type these as part of user input.Angle brackets < > enclose a descriptive name for any value that is provided as output by a computer; for example:FORMAT="LINESPECIFIC"MOREINFO="NONE"IPXRTR:3.00:32:Failed to unbind duplicate
    LAN board <name>PAGENUM=12 ID="BP5"PAGENUM=13Characters enclosed in angle brackets can also represent keys; for example:MARK=BULLET"Press MOREINFO="NONE"<Ins>" means you press the MOREINFO="NONE"<Insert> key on your keyboard. Keys joined by a plus sign are pressed in combination. "Press MOREINFO="NONE"<Ctrl>+<Alt>+<Delete>" means you press those keys simultaneously.Square brackets [ ] enclose an option item; for example:FORMAT="LINESPECIFIC"MOREINFO="NONE"BIND IPX TO board_name NET=network_number
   [RIP=RIP_state] [SAP=SAP_state] MOREINFO="NONE"<Enter>If a command, such as the preceding one, is too long to fit on one line, it wraps to the next line; such a command must be entered after the console prompt (:) but before the end-of-line (EOL) character.Braces { } enclose multiple items separated by the vertical bar | character. You must specify only one of the items; for example:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD IPXRTR [ROUTING={NLSP|RIPSAP|NONE}]Vertical bars | separate items in a list of alternatives. If the list is enclosed in square brackets [ ], you can use any one or none of the items. If the list is enclosed in braces { }, you must use any one, but only one, of the items. RENDERAS="SECT2"ID="FM50216"Graphic SymbolsIn printed documentation, the following symbols appear in the left margin to identify different categories of information:PERFORMANCE="REQUIRED"This symbol identifies the first step of a procedure. To accomplish a specific task, follow the steps in the procedure.This symbol indicates sidelights, discussions, and general points of interest related to the current subject.This symbol points out key concepts or facts about the product. PAGENUM=14 ID="BP6"This symbol alerts you to situations that can produce critical or irreversible errors if you do not follow instructions carefully.This symbol points out hints, tips, or helpful information that you should know.Online documentation omits these symbols, but either maintains the font change or labels the information for easy identification.RENDERAS="SECT1"Related Novell PublicationsSee the following Novell publications for information about IPX, NLSP, RIP, SAP, and related topics:MARK=BULLETBOOK="ipxicenu" COLLECTION="ipxrug10"IPX Upgrade for NetWare Servers 1.0 Installation and Configuration Guide (Novell part number 100-002431-001)BOOK="cfg1_enu" COLLECTION="nw41"NetWare 4.1 Basic Protocol Configuration Guide  (Novell part number 100-002446-001)BOOK="cfg2_enu" COLLECTION="nw41"NetWare 4.1 Advanced Protocol Configuration and Management Guide  (Novell part number 100-002447-001)BOOK="ipxrtenu" COLLECTION="nw41"NetWare 4.1 IPX Reference (Novell part number 100-002101-001)NetWare Link Services Protocol In-Depth (Novell part number 481-000085-001)NetWare Link Services Protocol Specification (Novell part number 100-001708-002)The Novell Network Registry (Novell part number 461-000248-001)PAGENUM=14 ID="BP7"PAGENUM=15RENDERAS="SECT1"Additional ReadingThe following publications provide general technical information about routing and related topics:MARK=BULLETInterconnections: Bridges and Routers, by Radia Perlman. Addison-Wesley Publishing Company, Inc.Routing in Today's Internetworks, by Mark Dickie. Van Nostrand Reinhold, an International Thomson Publishing company.Novell's Guide to Multiprotocol Internetworking, by Laura A. Chappell and Roger L. Spicer. Novell Press: Sybex.LABEL="1"PAGENUM=1 ID="BP8"ID="FM22213"NetWare Link Services ProtocolThis chapter introduces NetWare® Link Services ProtocolTM (NLSPTM) software, Novell's link state routing protocol for IPXTM internetworks.NetWare 4.1 provides NLSP and RIP/SAP routing only for LAN-based servers. You must use other Novell or third-party products if you want to run NLSP or RIP/SAP over a WAN connection.This chapter includes the following sections:MARK=BULLETIDREF="FM95907""About NLSP"This section gives a brief overview of what NLSP is and how it works.For more detailed information about NLSP, see the BOOK="ipxrtenu" COLLECTION="nw41"NetWare 4.1 IPX Reference.IDREF="FM21520""NLSP Memory Requirements"This section gives some general memory requirements for NLSP to run on networks of different sizes.IDREF="FM61224""Novell Products That Provide NLSP Functionality"This section lists the Novell products that provide NLSP functionality. You will install at least one of these products when you migrate your network.If you are already familiar with NLSP and want to start implementing it in your network, turn to IDREF="FM89629"Chapter 4, "Developing a Migration Strategy."PAGENUM=1 ID="BP9"PAGENUM=2RENDERAS="SECT1"ID="FM95907"About NLSPIDXID="w4899"BOOK="_idx" COLLECTION="nw41" TIDREF="i2927"
NetWare servers have traditionally used the Routing Information Protocol (RIP) to route IPX packets, and the Service Advertising Protocol (SAP) to exchange service information with other NetWare servers. In addition to providing this same functionality for network devices that rely on RIP and SAP (NetWare 2 servers, for example), NLSP provides IDXID="w4900"BOOK="_idx" COLLECTION="nw41" TIDREF="i2115"
link state routing for IPX internetworks.NLSP is derived from IDXID="w4901"BOOK="_idx" COLLECTION="nw41" TIDREF="i1990"
IS-IS (Intermediate System-to-Intermediate System), the link state routing protocol developed by the IDXID="w4902"BOOK="_idx" COLLECTION="nw41" TIDREF="i1860"
International Standards Organization (ISO). Like IS-IS, NLSP exchanges routing information between routers and makes routing decisions based on that information. For workstation-to-router communication, NLSP routers continue to use RIP and SAP.NLSP routers exchange information such as connectivity states, path costs, throughput, maximum packet size (MTU size), and networks learned through RIP (external network numbers). In networks with RIP/SAP devices, the routers keep track of services and IDXID="w4903"BOOK="_idx" COLLECTION="nw41" TIDREF="i1413"
external (RIP-based) routes. This information is carried in a IDXID="w4904"BOOK="_idx" COLLECTION="nw41" TIDREF="i2111"Link State Packet (LSP). By exchanging this information with its peer routers, each NLSP router builds and maintains a logical map of the entire network.Unlike RIP and SAP, which periodically broadcast routing and service information, NLSP transmits routing information only when a change occurs in a route or service, or every two hours---whichever occurs first.Migrating an IPX network to NLSP involves only the NetWare servers and routers; you do not need to install any additional software on the NetWare IDXID="w4905"BOOK="_idx" COLLECTION="nw41" TIDREF="i4845"
workstations. NLSP is compatible with all NetWare IDXID="w4906"BOOK="_idx" COLLECTION="nw41" TIDREF="i2927"
workstations and RIP/SAP routers, and with other network devices---such as print servers---that use SAP to advertise their services.Although NLSP is a routing protocol specifically for IPX, it is not limited to pure IPX LANs. NLSP operates seamlessly within multiprotocol LAN and WAN environments, such as TCP/IP, AppleTalk*, Frame Relay, and X.25, to name a few.PAGENUM=2 ID="BP10"PAGENUM=3RENDERAS="SECT2"The IPXRTR NLMIDXID="w4907"BOOK="_idx" COLLECTION="nw41" TIDREF="i1971"
The IPXRTR NetWare Loadable ModuleTM (NLMTM) file is the IPX protocol stack for the NetWare operating system. IPXRTR provides combined NLSP routing and full RIP/SAP functionality for network-level operations.IPXRTR allows you to enable or disable RIP, SAP, and NLSP selectively on network interfaces within the same server or router. For example, you can use RIP and SAP exclusively on one interface and NLSP on another. Additionally, an interface can use NLSP as the active routing protocol but still accept and process RIP and SAP broadcasts from network devices that use RIP and SAP.IPXRTR also allows you to bind IPX to two or more network interface boards connected to the same LAN. This enables NetWare workstations on that LAN to use either interface when accessing the server---a feature called IDXID="w4908"BOOK="_idx" COLLECTION="nw41" TIDREF="i2146"load balancing or load sharing.RENDERAS="SECT2"Current and Future NLSP FunctionalityNLSP currently supports link state routing within a single routing area; this is called level 1 routing. A IDXID="w4909"BOOK="_idx" COLLECTION="nw41" TIDREF="i3898"
routing area is an administrative domain in which all users have Network-layer access to the same services.Future releases of IDXID="w4910"BOOK="_idx" COLLECTION="nw41" TIDREF="i2927"
NLSP will link routing areas into routing domains (level 2 routing), and routing domains into a IDXID="w4911"BOOK="_idx" COLLECTION="nw41" TIDREF="i1605"global IPX internetwork (level 3 routing). A IDXID="w4912"BOOK="_idx" COLLECTION="nw41" TIDREF="i3899"
routing domain can be a company, a university, an agency, or even a public carrier connecting two or more business or academic organizations. Within a routing domain, each local campus---or other suborganization---constitutes a routing area.To read more about routing areas, see IDREF="FM88235"Chapter 5, "Partitioning an Internetwork into Routing Areas."PAGENUM=3 ID="BP11"PAGENUM=4RENDERAS="SECT1"ID="FM21520"NLSP Memory RequirementsIDXID="w4913"BOOK="_idx" COLLECTION="nw41" TIDREF="i1971"
IPXRTR and its internal stack processes occupy about 290 KB of system memory. The amount of memory required beyond this baseline depends on the size of the network---specifically, how many network numbers, RIP routes, and SAP-based services are supported throughout the network.For example, on an IPX network using only NLSP as the routing protocol and having 400 network numbers, NLSP uses about 240 KB in addition to the 290 KB that IPXRTR requires. On an IPX network using both NLSP and RIP/SAP and having about 3000 network numbers and 1600 services, NLSP uses about 600 KB in addition to the 290 KB baseline requirement.RENDERAS="SECT1"ID="FM61224"Novell Products That Provide NLSP FunctionalityWhich products you need to migrate your network depends on the specifics of the network topology---that is, how many NetWare LANs it comprises, whether it uses WAN connections or third-party routers, and so on. Novell currently offers the following products with NLSP functionality:MARK=BULLETIPX Upgrade for NetWare Servers 1.0This product provides NLSP routing for IPX on NetWare 3TM servers, NetWare 4.01 servers, and NetWare 4.02 servers by upgrading only the IPX protocol stack. You retain all the functionality of the base NetWare operating system but gain the efficiency of NLSP routing.PAGENUM=4 ID="BP12"PAGENUM=5This product is available from the following sources:MARK=BULLETIDXID="w4914"BOOK="_idx" COLLECTION="nw41" TIDREF="i2836"
NetWire® electronic bulletin board. Type MOREINFO="NONE"GO NOVLIB, then download the NOVLIB\08\IPXRTR.EXE file.IDXID="w4915"BOOK="_idx" COLLECTION="nw41" TIDREF="i1581"
ftp.novell.com, by anonymous FTP. Log in, then copy the pub/novlib/08/ipxrtr.exe file.IDXID="w4916"BOOK="_idx" COLLECTION="nw41" TIDREF="i3011"
Novell Network Support Encyclopedia Professional VolumeSM (NSE ProSM) CD-ROM. Type MOREINFO="NONE"CD DOWNLOAD, then download the IPXRTR.EXE file.NetWare 4.1 softwareThis product is Novell's newest release of the NetWare operating system and the first to offer NLSP routing for IPX.LABEL="2"PAGENUM=7 ID="BP13"ID="FM66347"Why You Should Migrate Your IPX Network from RIP to NLSPThis chapter explains how the NLSPTM routing protocol can benefit your IPXTM network.This chapter includes the following sections:MARK=BULLETIDREF="FM11095""How NLSP Can Benefit Your Network"This section presents several reasons supporting the use of NLSP on an IPX network.IDREF="FM37600""Answers to Commonly Asked Questions"This section answers questions that NetWare® administrators often ask about NLSP.RENDERAS="SECT1"ID="FM11095"How NLSP Can Benefit Your NetworkThis section summarizes the principal benefits of running NLSP on your network.RENDERAS="SECT2"Less Routing and Service Traffic on the NetworkEach RIP router broadcasts its entire routing table and service database every 60 seconds, even if none of the information has changed since the previous broadcast. This generates a significant amount of traffic on the network.By contrast, NLSP transmits information only when a change occurs in a route or service, or every two hours---whichever occurs first. Although this information is broadcast by default, it can be multicast if the network interface driver supports multicast transmission.PAGENUM=8 ID="BP14"RENDERAS="SECT2"Faster Network ConvergenceWhen a router or a link comes up or goes down, or when a service becomes available or inaccessible, it takes time for that information to become known to all routers throughout the network. Convergence is the process by which a routing protocol learns of a topology or service change and makes that change known to each of the active routers on the network. A network is said to have converged when all routers once again share the same view of the network.As a link state routing protocol, NLSP converges faster than RIP, the traditional distance vector routing protocol for IPX networks. Fast convergence is important for the following reasons:MARK=BULLETIt helps keep sessions active across the network.While a network is converging, there is a brief period during which the routers are busy rebuilding their routing databases. In-transit packets are often lost during this process.It enables you to discover network problems more quickly.It reduces routing loops.RENDERAS="SECT2"Larger IPX Networks PossibleWith NLSP, you can build and operate larger IPX networks than are possible with RIP.Whereas packets relayed by RIP routers can travel no more than 15 hops between their source and destination, packets relayed by NLSP can travel up to 127 hops.RENDERAS="SECT2"Load BalancingNLSP makes efficient use of network resources by automatically distributing forwarded traffic across network interfaces. That is, given two or more equal-cost routes between two network nodes, NLSP distributes the traffic evenly among them. You can use the Internetworking Configuration utility (INETCFG) to specify up to eight equal-cost routes or even configure a router to use a single route.PAGENUM=9 ID="BP15"For more information about load balancing and equal-cost routes, see the BOOK="ipxrtenu" COLLECTION="nw41"NetWare 4.1 IPX Reference.RENDERAS="SECT2"More Extensive Network ManagementAny network management application that uses Simple Network Management Protocol (SNMP)---such as Novell's NetWare Management SystemTM (NMSTM) software---can monitor an NLSP router or a RIP router implemented to the Management Information Base (MIB) specification. You can then use these applications to derive a topology map of your entire IPX internetwork from a single NLSP router.Such far-reaching management capability enables you to detect problems such as duplicate network numbers, inactive routers or links, and even failed interface boards anywhere on your network.RENDERAS="SECT2"Configurable Link-Cost AssignmentNLSP routers know the cost of every link and use this information to choose the most efficient route for each outgoing packet.INETCFG enables you to change the cost of a link. For example, you can increase the cost of a particular link so that NLSP routes traffic through a preferred, less-expensive link.RENDERAS="SECT2"Compatibility with IPX RIP and SAPBecause NLSP is fully compatible with IPX RIP and SAP, you can use NLSP and RIP routers together in the same network. NLSP routers also interoperate with devices and applications that use or depend on RIP and SAP. NLSP encapsulates and propagates the routing and service information it receives from RIP/SAP devices and networks.You can also migrate NetWare LANs from RIP to NLSP as needed; you do not need to migrate your entire network at the same time.PAGENUM=9 ID="BP16"PAGENUM=10RENDERAS="SECT1"ID="FM37600"Answers to Commonly Asked QuestionsThe following sections answer some commonly asked questions about NLSP.RENDERAS="SECT2"Do Link State Protocols Use More CPU Than Distance Vector Protocols?Each large network is different in its complexity and the network events it must process. Some events are processed more quickly by distance vector protocols; others are processed more quickly by link state protocols.Link state protocols dispense with many of the time-consuming tasks associated with traditional distance vector protocols. Also, older implementations of distance vector protocols are often inefficient.Novell has tested NLSP in very large networks, and has verified that the algorithms perform well and use a nominal amount of CPU.RENDERAS="SECT2"Do Link State Protocols Use More Memory Than Distance Vector Protocols?Typically they do, but not in every network. In addition to the 290 KB that IPXRTR requires, NLSP uses about 600 KB in a large internetwork of 3000 network numbers and 1600 services.RENDERAS="SECT2"Can I Use NLSP to Migrate a NetWare 2 Network to NetWare 3?Yes. NLSP automatically detects the presence of NetWare 2 software on the network. However, wherever you have a mix of NetWare 2 and NetWare 3TM servers, you run NLSP, RIP, and SAP.RENDERAS="SECT2"How Many NLSP Routers Can I Have on a Single LAN Segment?NLSP allows for up to 230 systems---routers and servers combined---on an Ethernet LAN segment. This number is higher for token ring and FDDI networks, depending on the maximum packet size you configure on each server on the LAN.PAGENUM=11 ID="BP17"RENDERAS="SECT2"Can NLSP Run on the Same Network with OSPF and IS-IS?Yes. NLSP can run on the same network---or even the same router---with Open Shortest Path First (IDXID="w4917"BOOK="_idx" COLLECTION="nw41" TIDREF="i3130"
OSPF) and IS-IS routing protocols. Because NLSP information is carried within IPX packets, it does not interfere with other routing protocols running on the same network.RENDERAS="SECT2"Can I Use Third-Party Network Management Software with NLSP?Yes. NLSP, IPX RIP, and SAP use MIB variables in SNMP format that are fully compatible with the following network management products:MARK=BULLETNovell NMS softwareSunNet Manager*Hewlett-Packard* OpenView*IBM* NetView*Some of these products have already integrated the NLSP, IPX RIP, and SAP MIB variables. IPX Upgrade for NetWare Servers 1.0 provides these MIB variables in ASN.1 format so that you can use your MIB compiler to convert them into a format that your network management software can use.RENDERAS="SECT2"What is the Difference Between Fast and Default Convergence?The primary difference is the rate at which NLSP routers send "keep-alive" messages---in the form of Hello packets---to their peers. If a system is not forwarding packets (that is, not operating as a router), there is little need to send Hello packets frequently. On an NLSP router, however, you should consider increasing the CLASS=MENUITEM MOREINFO="NONE"Hello Interval frequency. This enables other NLSP routers on the network to detect failed routers more quickly so that an alternate route can be chosen.PAGENUM=11 ID="BP18"PAGENUM=12RENDERAS="SECT2"Where in My Network Should I Start Migrating to NLSP?If you have a large network, first decide how you intend to partition it into routing areas, then migrate the routers at the area boundaries. You should also migrate one LAN at a time. Guidelines for partitioning your network are presented in IDREF="FM49385""Defining Routing Areas in an Internetwork.".Even if your network uses third-party routers that support RIP/SAP but not NLSP, you can still migrate your NetWare servers to NLSP. In this case, the servers and third-party routers can continue to exchange routing information using RIP/SAP. When you later migrate your dedicated routers and integrated server-routers to NLSP, your NetWare servers automatically use NLSP instead of RIP/SAP to exchange routing information with the NLSP routers.As the percentage of NLSP routers on your network increases, the bandwidth use and convergence time improves throughout your network.LABEL="3"PAGENUM=13 ID="BP19"ID="FM47651"Trying Out NLSP on Your IPX NetworkThis chapter provides a quick, easy-to-implement migration solution for those who want to see immediate benefits of NLSPTM software on their IPXTM internetwork. IDXID="w4918"BOOK="_idx" COLLECTION="nw41" TIDREF="i2927"
This approach enables you to "test drive" NLSP before migrating your entire IPX internetwork. Each solution also provides ways to measure server and network performance before and after migration.This chapter includes the following sections:MARK=BULLETIDREF="FM47574""Trying Out NLSP on a Single NetWare LAN"This section explains how to migrate the NetWare® servers on a small LAN in your internetwork.IDREF="FM84891""Examining the Operation of Your NLSP Systems"This section shows how you can take a closer look at the NetWare systems you migrate.IDREF="FM83925""Where to Go from Here"This section shows you where to look for more information about migrating other portions of your IPX internetwork.PAGENUM=13 ID="BP20"PAGENUM=14RENDERAS="SECT1"ID="FM47574"Trying Out NLSP on a Single NetWare LANThis section explains how to see the benefits of NLSP on a small NetWare LAN.RENDERAS="SECT2"Choosing the LANChoose a LAN with the following characteristics:MARK=BULLETSupports no more than 10 servers running NetWare 3.11, NetWare 3.12, NetWare 4.01, or NetWare 4.02 softwareHas no third-party routers connecting the LAN to other networksIDREF="FM92178"Figure 3-1 shows two LANs that satisfy these criteria.LABEL="3-1" FLOAT="0"ID="FM92178"Example NetWare LANsFILEREF="31lan.tif"PAGENUM=15 ID="BP21"RENDERAS="SECT2"ID="FM63101"Measuring LAN and Server Performance (Optional)IDXID="w4919"BOOK="_idx" COLLECTION="nw41" TIDREF="i2360"
Before you migrate the servers, use any of the following NetWare software to examine server and network performance:MARK=BULLETIDXID="w4920"BOOK="_idx" COLLECTION="nw41" TIDREF="i4538"TRACK ON---Use the MOREINFO="NONE"TRACK ON command to display incoming and outgoing RIP and SAP traffic on the server. Note the frequency.IDXID="w4921"BOOK="_idx" COLLECTION="nw41" TIDREF="i2045"LANalyzer® network analyzer---Use the LANalyzer product to examine the percentage of network utilization consumed by broadcast traffic. Record this number.IDXID="w4922"BOOK="_idx" COLLECTION="nw41" TIDREF="i2510"MONITOR---If your IPX network has a large number of NetWare 3.11 servers, load MONITOR on one of the servers on which you intend to install NLSP software. Record the number displayed in the CLASS=MENUITEM MOREINFO="NONE"Utilization counter; this shows the percentage of time the IDXID="w4923"BOOK="_idx" COLLECTION="nw41" TIDREF="i865"
CPU is busy.On a large network of NetWare 3.11 servers, CPU utilization typically exceeds 95 percent during RIP and SAP broadcasts. You should see a marked reduction in IDXID="w4924"BOOK="_idx" COLLECTION="nw41" TIDREF="i865"
CPU utilization after migration.RENDERAS="SECT2"Migrating the ServersTo migrate the servers on the LAN, complete the following steps:PERFORMANCE="REQUIRED"Install and configure IPX Upgrade for NetWare Servers 1.0 on each server in any order.For instructions, see the BOOK="ipxicenu" COLLECTION="ipxrug10"IPX Upgrade for NetWare Servers 1.0 Installation and Configuration Guide.PERFORMANCE="REQUIRED"Reexamine server and network performance with the same software you used in 
IDREF="FM63101""Measuring LAN and Server Performance (Optional)."PERFORMANCE="REQUIRED"Compare these performance statistics with those you observed before migrating the servers.
PAGENUM=16 ID="BP22"RENDERAS="SECT1"ID="FM84891"Examining the Operation of Your NLSP SystemsAfter you migrate a portion of your network to NLSP, you can gain management access to the NLSP systems with the IPX network management console (IDXID="w4925"BOOK="_idx" COLLECTION="nw41" TIDREF="i1964"
IPXCON). IPXCON allows you to monitor the operation of local and remote systems for troubleshooting, checking configuration parameters, and observing general performance and load statistics.You can also use the IDXID="w4926"BOOK="_idx" COLLECTION="nw41" TIDREF="i1969"
IPXPING utility to check the connectivity and latency---response time over the network---of remote NLSP systems.For information about how to use IPXCON and IPXPING, see the BOOK="cfg2_enu" COLLECTION="nw41"NetWare 4.1 Advanced Protocol Configuration and Management Guide.RENDERAS="SECT1"ID="FM83925"Where to Go from HereIf you want to migrate other portions of your IPX internetwork, continue to IDREF="FM89629"Chapter 4, "Developing a Migration Strategy." That chapter helps you develop an organized and comprehensive strategy that suits the size and topology of your network.If you have migrated all the systems you want---or need---to migrate at this time, you are done.LABEL="4"PAGENUM=17 ID="BP23"ID="FM89629"Developing a Migration StrategyThis chapter provides the information you need to develop a comprehensive IDXID="w4927"BOOK="_idx" COLLECTION="nw41" TIDREF="i2459"migration strategy for your IPXTM internetwork.Use this chapter as a point of reference when planning and implementing the migration.This chapter includes the following sections:MARK=BULLETIDREF="FM84057""Step 1: Determine the Size of Your Network" This section explains how to determine how many internal and external network numbers are represented on the network.IDREF="FM40913""Step 2: Characterize Your Network"This section outlines the steps you follow to develop the migration strategy that best suits your network.IDREF="FM13086""Step 3: Migrate Your Network to NLSP"This section gives general guidelines for migrating your network.PAGENUM=17 ID="BP24"PAGENUM=18RENDERAS="SECT1"ID="FM84057"Step 1: Determine the Size of Your NetworkThe migration strategy you adopt depends primarily on the number of networks and servers on your IPX internetwork. To determine this number, type the following NetWare® command at the server prompt:FORMAT="LINESPECIFIC"MOREINFO="NONE"IDXID="w4928"BOOK="_idx" COLLECTION="nw41" TIDREF="i1146"
DISPLAY NETWORKS MOREINFO="NONE"<Enter>The screen displays the IDXID="w4929"BOOK="_idx" COLLECTION="nw41" TIDREF="i1855"
internal network number of each server and the IDXID="w4930"BOOK="_idx" COLLECTION="nw41" TIDREF="i1411"
external network number of each IPX network that can be reached from the server. The total number of network numbers is displayed at the end of the list.RENDERAS="SECT2"If Your Network Has Fewer Than 400 Network NumbersA small network---one having fewer than 400 network numbers---is easy to migrate, especially if it comprises only NetWare servers and includes no third-party routers that do not support NLSPTM software. In this case, you can install NLSP on the servers in any order.RENDERAS="SECT2"If Your Network Has 400 or More Network NumbersA large network---one having 400 or more network numbers---should be partitioned into routing areas.You should also consider reserving a contiguous block of IPX network addresses through the Novell® Network RegistrySM service.For information about partitioning your network and participating in the Novell Network Registry, see IDREF="FM88235"Chapter 5, "Partitioning an Internetwork into Routing Areas."PAGENUM=18 ID="BP25"PAGENUM=19RENDERAS="SECT1"ID="FM40913"Step 2: Characterize Your NetworkHow you migrate your network depends on the following network characteristics:MARK=BULLETSizeNetWare versionsNovell products other than NetWare on the networkThis section provides a set of tasks that helps you determine what you need to do to migrate your network. Each step directs you to complete a task and refers you to a chapter for specific instructions. The number of chapters to which you must refer depends largely on the topological complexity of your network.PERFORMANCE="REQUIRED"If your network comprises 400 or more network numbers, define the routing areas.Routing areas provide a manageable hierarchy and preserve routing efficiency in large IPX networks. For further instructions, see 
IDREF="FM88235"Chapter 5, "Partitioning an Internetwork into Routing Areas."PERFORMANCE="REQUIRED"Determine which versions of NetWare are running on the network.In particular, NetWare 2 servers require special consideration because of their dependence on IPX RIP and SAP broadcasts. For further instructions, see 
IDREF="FM79804"Chapter 6, "Migrating a Network with Different NetWare Versions."PERFORMANCE="REQUIRED"Determine whether any of the following Novell products are running on the network:
MARK=BULLETNetWare MultiProtocol RouterTM 2.0, 2.1, or 2.11 softwareIDXID="w4931"BOOK="_idx" COLLECTION="nw41" TIDREF="i4658"
UnixWareTM softwareIDXID="w4932"BOOK="_idx" COLLECTION="nw41" TIDREF="i3136"
OS/2* Named PipesIDXID="w4933"BOOK="_idx" COLLECTION="nw41" TIDREF="i2832"
NetWare/IPTM softwareLike NetWare 2, these products depend on RIP, SAP, or both. For further instructions, see 
IDREF="FM38483"Chapter 7, "Migrating a Network with Products That Require RIP and SAP."PAGENUM=20 ID="BP26"RENDERAS="SECT1"ID="FM13086"Step 3: Migrate Your Network to NLSPThis section offers guidelines to help your network migration progress smoothly.To maintain connectivity between LANs during migration, do not disable RIP routing on any interface until you have installed NLSP software on every system.RENDERAS="SECT2"If You Need to Define Routing AreasUse the following guidelines if you need to partition your network into routing areas:MARK=BULLETDefine the routing areas first. For information, see IDREF="FM66835""Guidelines to Follow When Defining Routing Areas."Migrate the "core" routers first, then migrate one LAN at a time. Core routers are typically those that form the network backbone or share a high-speed transit LAN. For information, see the examples in IDREF="FM49385""Defining Routing Areas in an Internetwork."RENDERAS="SECT2"If You Do Not Need to Define Routing AreasIf you do not need to partition your network into routing areas, use Chapters 6 and 7, as necessary, to migrate your network.If your network has fewer than 400 network numbers and uses no WAN connections or routers that do not support NLSP, install NLSP software on the NetWare servers or dedicated routers in any order.LABEL="5"PAGENUM=21 ID="BP27"ID="FM88235"Partitioning an Internetwork into Routing AreasIDXID="w4934"BOOK="_idx" COLLECTION="nw41" TIDREF="i3230"
This chapter explains how to IDXID="w4935"BOOK="_idx" COLLECTION="nw41" TIDREF="i3898"
partition a large IPXTM internetwork into routing areas. Because these internetworks are typically linked by one or more WAN connections, the guidelines and examples provided in this chapter are oriented primarily toward WAN connections, which require other Novell® or third-party products in addition to NetWare® 4.1. However, the information in this chapter can still help you partition a purely LAN-based internetwork.You should read this chapter ifMARK=BULLETYour IPX internetwork has 400 or more IDXID="w4936"BOOK="_idx" COLLECTION="nw41" TIDREF="i2872"
network numbersIf you do not know how many network numbers your internetwork has, see IDREF="FM84057""Step 1: Determine the Size of Your Network."You want to use route or service IDXID="w4937"BOOK="_idx" COLLECTION="nw41" TIDREF="i1502"
filtering as a means of establishing security or limiting broadcast traffic on your internetworkTo configure filters after you partition your internetwork, see the BOOK="cfg2_enu" COLLECTION="nw41"NetWare 4.1 Advanced Protocol Configuration and Management Guide.This chapter includes the following sections:MARK=BULLETIDREF="FM69664""Routing Areas"This section explains what routing areas are.IDREF="FM28904""Using the Novell Network Registry"This section introduces the Novell Network RegistrySM service and explains how to use the services it provides.IDREF="FM49385""Defining Routing Areas in an Internetwork"This section presents guidelines to help you determine how you should partition your network.PAGENUM=22 ID="BP28"RENDERAS="SECT1"ID="FM69664"Routing AreasRouting areas establish hierarchy within an IPX internetwork. For growing networks, routing areas allow for better scaling---more LANs, servers, and routers than otherwise possible. Routing areas also separate an internetwork into manageable components, which is desirable for administrative simplicity.RENDERAS="SECT2"ID="FM42135"Area Addresses and MasksTwo 32-bit numbers---a IDXID="w4938"BOOK="_idx" COLLECTION="nw41" TIDREF="i2872"
network number and a mask---identify a routing area. Together, these numbers constitute the area address. Here is an example:IDXID="w4939"BOOK="_idx" COLLECTION="nw41" TIDREF="i286"MOREINFO="NONE"08068500 (network number)MOREINFO="NONE"FFFFFF00 (mask)The default values for the network number and mask are as follows:MARK=BULLETIDXID="w4940"BOOK="_idx" COLLECTION="nw41" TIDREF="i286"
Address=00000000IDXID="w4941"BOOK="_idx" COLLECTION="nw41" TIDREF="i291"
Mask=00000000The address and mask are both set to zero to ensure compatibility with future versions of NLSPTM software. Zero values mean that all NLSP routers operate in a single routing area.Although you are allowed to configure the area address and mask on your NetWare 4.1 server, accept the default values and use RIP to partition your areas as described in the next section.RENDERAS="SECT2"ID="FM69654"Using RIP to Partition Routing AreasIDXID="w4942"BOOK="_idx" COLLECTION="nw41" TIDREF="i3870"
Although the current version of NLSP does not support interarea (level 2) routing, you can create IDXID="w4943"BOOK="_idx" COLLECTION="nw41" TIDREF="i3898"
routing areas by running RIP on the network interfaces that link the areas. IDREF="FM62020"Figure 5-1 shows two routing areas partitioned by RIP.PAGENUM=23 ID="BP29"LABEL="5-1" FLOAT="0"ID="FM62020"Creating Routing Areas Partitioned by RIPFILEREF="51areas.tif"The following steps summarize how to configure the interfaces:PERFORMANCE="REQUIRED"Enable NLSP routing on each router.Complete the following steps:If you need more detailed instructions, see the BOOK="cfg1_enu" COLLECTION="nw41"NetWare 4.1 Basic Protocol Configuration Guide.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Load INETCFG.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Protocols.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"IPX.PERFORMANCE="REQUIRED"Set the 
CLASS=MENUITEM MOREINFO="NONE"Routing Protocol parameter to 
CLASS=MENUITEM MOREINFO="NONE"NLSP with RIP/SAP Compatibility.PERFORMANCE="REQUIRED"Save your changes.PERFORMANCE="REQUIRED"On the network interface that 
links the areas, turn off NLSP and turn on RIP and SAP.Complete the following steps:If you need more detailed instructions, see the BOOK="cfg1_enu" COLLECTION="nw41"NetWare 4.1 Basic Protocol Configuration Guide.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Load INETCFG.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Bindings.PERFORMANCE="REQUIRED"Select the interface.
PAGENUM=24 ID="BP30"PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Expert Bind Options, then select 
CLASS=MENUITEM MOREINFO="NONE"RIP Bind Options; set the 
CLASS=MENUITEM MOREINFO="NONE"RIP State parameter to 
CLASS=MENUITEM MOREINFO="NONE"On.PERFORMANCE="REQUIRED"Return to the 
CLASS=MENUITEM MOREINFO="NONE"Expert Bind Options window, then select 
CLASS=MENUITEM MOREINFO="NONE"SAP Bind Options; set the 
CLASS=MENUITEM MOREINFO="NONE"SAP State parameter to 
CLASS=MENUITEM MOREINFO="NONE"On.PERFORMANCE="REQUIRED"Return to the 
CLASS=MENUITEM MOREINFO="NONE"Expert Bind Options window, then select 
CLASS=MENUITEM MOREINFO="NONE"NLSP Bind Options; set the 
CLASS=MENUITEM MOREINFO="NONE"NLSP State parameter to 
CLASS=MENUITEM MOREINFO="NONE"Off.PERFORMANCE="REQUIRED"Save your changes.Although NLSP is disabled on the interface at the area boundary, each router still imports the routes and services from the connected network into its own routing area.RENDERAS="SECT2"Filtering Routes and Services Between Routing AreasYou can use routing areas to prevent RIP and SAP traffic on one network from flowing to another. For example, suppose you want to prevent some users from gaining access to the accounting services on a particular network. You can use service filters to restrict access to those services.You cannot filter routes or services within a routing area, but you can filter routes and services between areas at the area boundaries. If you want to restrict Network-layer access within a routing area, you can filter IPX packets.If you use route and service filters, you must configure the same inbound and outbound filters on all NLSP routers connected to the same LAN within the same area. With NLSP, all routers in the same area share the same link state information; however, a single system called the IDXID="w4944"BOOK="_idx" COLLECTION="nw41" TIDREF="i1001"Designated Router imports routes and services for the entire network. Therefore, if you configure an inbound route or service filter on one---but not all---NLSP routers, and that router is not the Designated Router, the filter might have no effect. For information about how the Designated Router works, see the BOOK="ipxrtenu" COLLECTION="nw41"NetWare 4.1 IPX Reference.To configure route and service filters after you partition your internetwork, see the BOOK="cfg2_enu" COLLECTION="nw41"NetWare 4.1 Advanced Protocol Configuration and Management Guide.PAGENUM=25 ID="BP31"RENDERAS="SECT1"ID="FM28904"Using the Novell Network RegistryIDXID="w4945"BOOK="_idx" COLLECTION="nw41" TIDREF="i2881"
Business organizations, each with its own enterprise network, sometimes merge or agree to share information. Or, these same organizations might want to connect their networks to a larger IDXID="w4946"BOOK="_idx" COLLECTION="nw41" TIDREF="i3635"
public internetwork to use the services it provides. This means that all network numbers throughout the connected organizations must be unique.For this purpose, Novell offers the Novell Network Registry. The Novell Network Registry service assigns and tracks IPX network addresses and organization names. The Novell Network Registry enables participating organizations to share data between interconnected NetWare networks without name and address conflicts.The Novell Network Registry assigns a contiguous "block" of IPX network addresses that are unique to your organization. The size of your address block depends on the number of NetWare LANs and servers in your IPX internetwork, including any additional LANs or servers you anticipate installing over the next two years.To learn more about the Novell Network Registry, or to reserve a block of IPX IDXID="w4947"BOOK="_idx" COLLECTION="nw41" TIDREF="i2843"
network addresses, call 1-408-577-7506 or send Internet E-mail to IDXID="w4948"BOOK="_idx" COLLECTION="nw41" TIDREF="i3727"registry@novell.com. You can also send E-mail by way of the MHS NHUB system to registry@novell. Ask for the publication The Novell Network Registry.RENDERAS="SECT1"ID="FM49385"Defining Routing Areas in an InternetworkThis section uses examples to show how to define routing areas in an IPX internetwork.There are many ways to partition an internetwork into areas. This section provides only a few examples of how this can be done.PAGENUM=25 ID="BP32"PAGENUM=26RENDERAS="SECT2"ID="FM66835"Guidelines to Follow When Defining Routing AreasApply the following guidelines when defining routing areas in your internetwork:MARK=BULLETMake a sketch of the internetwork. A graphic representation can help you identify area boundaries and key routers more easily.Identify the routers that make up the "core" network infrastructure. These routers typically form the corporate backbone network.A core area that uses backbone routers is shown in IDREF="FM87279""Partitioning an Internetwork That Uses a WAN Backbone."Identify the routers that "feed" one or more LANs. These IDXID="w4949"BOOK="_idx" COLLECTION="nw41" TIDREF="i1443"feeder routers service LANs that typically represent functional groups, such as remote sales offices, an engineering department, and so on.An example of feeder routers is shown in IDREF="FM22946""Partitioning an Internetwork That Uses a Transit LAN."Do not enable NLSP on the interfaces at area boundaries. Two routers running NLSP at an area boundary automatically become neighbors and join their respective areas into a single area. Run only RIP at an area boundary, as shown in IDREF="FM62020"Figure 5-1 on page 23.However, a router in one area can run NLSP on a transit LAN while routers to other areas run RIP. An example of this is shown in IDREF="FM22946""Partitioning an Internetwork That Uses a Transit LAN."Avoid partitioning routing areas across WAN connections. Doing so forces RIP to run over the WAN connection, which, along with SAP, consumes network bandwidth. Wherever it is possible, run only NLSP over the WAN connections in your internetwork.IDREF="FM51606"Figure 5-3 on page 28 and IDREF="FM20313"Figure 5-4 on page 30 show how an internetwork can be partitioned to keep WAN connections within a single area.PAGENUM=26 ID="BP33"PAGENUM=27Avoid having more than one RIP connection between a backbone router and a single routing area. Otherwise, the routers import the same routing and service information through each connection from the backbone into the routing area. This can double the routing traffic flowing into the area.IDREF="FM31556"Figure 5-2 shows the type of area configuration you should avoid.LABEL="5-2" FLOAT="0"ID="FM31556"Why You Should Have Only One RIP Connection Between a Backbone Network and a Routing AreaFILEREF="522rips.tif"PAGENUM=27 ID="BP34"PAGENUM=28RENDERAS="SECT2"ID="FM87279"Partitioning an Internetwork That Uses a WAN BackboneThis section explains how to define areas on an internetwork that uses a central backbone of WAN routers. IDREF="FM51606"Figure 5-3 shows a large IPX internetwork linked by five WAN routers that form the network backbone. Each WAN router is connected to a LAN router that services a small group of NetWare LANs. Without the benefit of NLSP or routing areas, RIP and SAP traffic from all the NetWare LANs traverses the backbone and consumes a large percentage of the available network bandwidth.LABEL="5-3" FLOAT="0"ID="FM51606"Routing Areas in an Internetwork Connected by a WAN BackboneFILEREF="52areas.tif"PAGENUM=28 ID="BP35"PAGENUM=29This internetwork is partitioned as follows:MARK=BULLETArea A. The backbone network of WAN routers forms one area.MARK=BULLETNLSP routing is enabled on the WAN interface between each WAN router.RIP routing is enabled on the interface between each WAN router and the corresponding LAN router that services its respective group of NetWare LANs.Areas B through F. Each group of NetWare LANs forms its own area.NLSP routing is enabled on the interface between each LAN router and its respective group of NetWare LANs.RENDERAS="SECT2"ID="FM22946"Partitioning an Internetwork That Uses a Transit LANThis section explains how to define areas on an internetwork that uses a IDXID="w4950"BOOK="_idx" COLLECTION="nw41" TIDREF="i4559"transit LAN. A transit LAN is typically a high-speed LAN---such as a high-speed IDXID="w4951"BOOK="_idx" COLLECTION="nw41" TIDREF="i4511"
token ring or Fiber Distributed Data Interface (IDXID="w4952"BOOK="_idx" COLLECTION="nw41" TIDREF="i1436"
FDDI) ring---that serves as a "crossroads" for all traffic on the internetwork. A transit LAN can link several routing areas.The internetwork in IDREF="FM20313"Figure 5-4 has six routers connected to an FDDI transit LAN:MARK=BULLETA backbone router links the transit LAN to a corporate backbone network like the one shown in IDREF="FM51606"Figure 5-3.Two LAN routers each connect a large group of NetWare LANs to the transit LAN.Three IDXID="w4953"BOOK="_idx" COLLECTION="nw41" TIDREF="i1443"
feeder routers are each linked through a WAN connection to several IDXID="w4954"BOOK="_idx" COLLECTION="nw41" TIDREF="i509"branch office routers. Each branch office router services a group of LANs at a branch office.PAGENUM=30 ID="BP36"LABEL="5-4" FLOAT="0"ID="FM20313"Routing Areas in an Internetwork Connected by an FDDI Transit LANFILEREF="53areas.tif"PAGENUM=30 ID="BP37"PAGENUM=31This internetwork is partitioned as follows:MARK=BULLETArea A. The backbone router and the backbone network form one area.MARK=BULLETRIP routing is enabled on the network interface between the backbone router and the FDDI transit LAN.NLSP routing is enabled on the network interface between the backbone router and the backbone network.Because the backbone router is running NLSP on the interface to the backbone network, it incorporates the route and service information it receives from the LAN routers into its IDXID="w4955"BOOK="_idx" COLLECTION="nw41" TIDREF="i2111"
Link State Packets (LSPs). The backbone router passes these LSPs to the backbone network.Areas B and C. Each LAN router and its group of NetWare LANs form a separate area.MARK=BULLETRIP routing is enabled on the network interface between each LAN router and the FDDI transit LAN.NLSP routing is enabled on the network interface between each LAN router and its corresponding group of NetWare LANs.Area D. The feeder routers, IDXID="w4956"BOOK="_idx" COLLECTION="nw41" TIDREF="i509"
branch office routers, and branch office LANs form one area.MARK=BULLETNLSP routing is enabled on the network interface between each feeder router and the FDDI transit LAN.NLSP routing is enabled on the WAN interface between each feeder router and branch office router.NLSP routing is enabled on the network interface between each branch office router and its corresponding group of NetWare LANs.To exchange routing information, the feeder routers use NLSP among themselves and RIP with the three other routers on the transit LAN.PAGENUM=31 ID="BP38"PAGENUM=32When you configure the network interfaces, start with the routers on the transit LAN---the backbone router in area A, the LAN routers in areas B and C, and the feeder routers in area D---then work "out" toward the branch office LANs.You can use the IPX network management console (IDXID="w4957"BOOK="_idx" COLLECTION="nw41" TIDREF="i1964"
IPXCON) to make sure you have configured the routers correctly. Using the internetwork shown in IDREF="FM20313"Figure 5-4 as an example, you would load IPXCON on one of the routers and view the neighboring routers on the transit LAN. The three routers running NLSP on the transit LAN should show each other as neighbors. They should not, however, show the backbone router or the two LAN routers as neighbors. The backbone router and the LAN routers should have no neighbors on the transit LAN.For more information about how to use IPXCON, see the BOOK="cfg2_enu" COLLECTION="nw41"NetWare 4.1 Advanced Protocol Configuration and Management Guide.LABEL="6"PAGENUM=33 ID="BP39"ID="FM79804"Migrating a Network with Different NetWare VersionsThis chapter presents upgrade options for servers running different versions of the NetWare® operating system.This chapter includes the following sections:MARK=BULLETIDREF="FM50908""If Your Network Has NetWare 2 Servers"This section outlines the options available for migrating a network with NetWare 2 servers.IDREF="FM30038""If Your Network Has NetWare 3 or NetWare 4.0x Servers"This section outlines the options available for migrating a network that has NetWare 3TM servers, NetWare 4.01 servers, or NetWare 4.02 servers.Because NLSPTM software can receive and broadcast IPXTM RIP and SAP packets, it can interoperate with any NetWare server. However, although the NetWare 3, NetWare 4.01, and NetWare 4.02 operating systems can run NLSP, the NetWare 2 system cannot and must either continue using RIP and SAP or be upgraded to a NetWare version that runs NLSP.PAGENUM=33 ID="BP40"PAGENUM=34RENDERAS="SECT1"ID="FM50908"If Your Network Has NetWare 2 ServersIDXID="w4958"BOOK="_idx" COLLECTION="nw41" TIDREF="i2823"
NetWare 2 servers depend on periodic RIP and SAP broadcasts. On an IPX network, NLSP detects NetWare 2 servers automatically and updates them with RIP and SAP broadcasts. However, unless you put the NetWare 2 servers on a single LAN, you must run both IPX routing protocols---RIP and NLSP---as well as SAP.The following options are available for migrating or interoperating with NetWare 2 servers on an IPX network:MARK=BULLETUpgrade the NetWare 2 servers to NetWare 3, NetWare 4.01, or NetWare 4.02.From this point, you install IPX Upgrade for NetWare Servers 1.0 on each server. To install this product, see the BOOK="ipxicenu" COLLECTION="ipxrug10"IPX Upgrade for NetWare Servers 1.0 Installation and Configuration Guide. This product is also available from the following sources:MARK=BULLETIDXID="w4959"BOOK="_idx" COLLECTION="nw41" TIDREF="i2836"
NetWire® electronic bulletin board. Type MOREINFO="NONE"GO NOVLIB, then download the NOVLIB\08\IPXRTR.EXE file.IDXID="w4960"BOOK="_idx" COLLECTION="nw41" TIDREF="i1581"
ftp.novell.com, by anonymous FTP. Log in, then copy the pub/novlib/08/ipxrtr.exe file.IDXID="w4961"BOOK="_idx" COLLECTION="nw41" TIDREF="i3011"
Novell® Network Support Encyclopedia Professional VolumeSM (NSE ProSM) CD-ROM. Type MOREINFO="NONE"CD DOWNLOAD, then download the IPXRTR.EXE file.From this point, you have two upgrade options:Install IPX Upgrade for NetWare Servers 1.0 on each NetWare 3 server.To install this product, see the BOOK="ipxicenu" COLLECTION="ipxrug10"IPX Upgrade for NetWare Servers 1.0 Installation and Configuration Guide. This product is available from the following sources:---IDXID="w4962"BOOK="_idx" COLLECTION="nw41" TIDREF="i2836"
NetWire® electronic bulletin board. Type MOREINFO="NONE"GO NOVLIB, then download the NOVLIB\08\IPXRTR.EXE file.---ftp.novell.com, by anonymous FTP. Log in, then copy the pub/novlib/08/ipxrtr.exe file.---NSE ProSM, the Novell® Network Support Encyclopedia Professional VolumeSM. Type MOREINFO="NONE"CD DOWNLOAD, then download the IPXRTR.EXE file.PAGENUM=34 ID="BP41"PAGENUM=35Upgrade the NetWare 3 servers to NetWare 4.1.In addition to providing NLSP routing for IPX, this option offers all the features of NetWare 4.1, including TCP/IP and AppleTalk routing.To upgrade a server to NetWare 4.1, see BOOK="instlenu" COLLECTION="nw41"NetWare 4.1 Installation.Put all NetWare 2 servers on the same LAN.This conserves network bandwidth by limiting the RIP/SAP traffic generated by the NetWare 2 servers to a single LAN. Any NetWare server running NLSP on an interface connected to the NetWare 2 LAN can then "import" and forward the routes and services from that LAN.RENDERAS="SECT1"ID="FM30038"If Your Network Has NetWare 3 or NetWare 4.0x ServersEnabling IDXID="w4963"BOOK="_idx" COLLECTION="nw41" TIDREF="i2825"
NetWare 3, NetWare 4.01, and IDXID="w4964"BOOK="_idx" COLLECTION="nw41" TIDREF="i2828"
NetWare 4.02 servers to run NLSP is straightforward and simple. The following options are available:MARK=BULLETInstall IPX Upgrade for NetWare Servers 1.0 on each NetWare 3 and NetWare 4 server.To install this product, see the BOOK="ipxicenu" COLLECTION="ipxrug10"IPX Upgrade for NetWare Servers 1.0 Installation and Configuration Guide. This product is available from the following sources:MARK=BULLETIDXID="w4965"BOOK="_idx" COLLECTION="nw41" TIDREF="i2836"
NetWire electronic bulletin board. Type MOREINFO="NONE"GO NOVLIB, then download the NOVLIB\08\IPXRTR.EXE file.ftp.novell.com, by anonymous FTP. Log in, then copy the pub/novlib/08/ipxrtr.exe file.Novell Network Support Encyclopedia Professional Volume (NSE Pro) CD-ROM. Type MOREINFO="NONE"CD DOWNLOAD, then download the IPXRTR.EXE file.Upgrade the NetWare 3, NetWare 4.01, and NetWare 4.02 servers to NetWare 4.1.In addition to providing NLSP routing for IPX, this option offers all the features of NetWare 4.1, including TCP/IP and AppleTalk routing.To upgrade a server to NetWare 4.1, see BOOK="instlenu" COLLECTION="nw41"NetWare 4.1 Installation.PAGENUM=36 ID="BP42"LABEL="7"PAGENUM=37 ID="BP43"ID="FM38483"Migrating a Network with Products That Require RIP and SAPThis chapter explains how to migrate or interoperate with systems running Novell® products other than the standard NetWare® operating system. Like NetWare 2 software, the products named in this chapter rely on RIP and SAP to advertise their services. These products can be running anywhere on the IPXTM internetwork, from a local server to systems on connected NetWare LANs.This chapter identifies products known to require special configurations to interoperate with NetWare servers or dedicated routers running NLSPTM software. Other Novell products, as well as third-party network interface boards and routing software, might also require special configurations.Note also that some network printers use SAP to advertise their print services on the network.This chapter includes the following sections:MARK=BULLETIDREF="FM74559""Interoperating with NetWare MultiProtocol Router 2.x"This section explains how to migrate or interoperate with NetWare servers or dedicated routers running NetWare MultiProtocol RouterTM 2.0, 2.1, or 2.11 software, NetWare WAN LinksTM 2.0 software, or NetWare MultiProtocol Router PlusTM 2.1 or 2.11 software.IDREF="FM54483""Interoperating with UnixWare"This section explains how to configure an NLSP router to interoperate with systems running UnixWareTM software.IDREF="FM49170""Interoperating with OS/2 Named Pipes"This section explains how to configure an NLSP router to interoperate with systems running OS/2 Named Pipes. Read this section only if you are using OS/2 Named Pipes from version 2.01 or earlier of NetWare ClientTM for OS/2 software.PAGENUM=38 ID="BP44"IDREF="FM80672""Interoperating with NetWare/IP"This section explains how to configure a NetWare server running both NLSP and NetWare/IPTM software.RENDERAS="SECT1"ID="FM74559"Interoperating with NetWare MultiProtocol Router 2.xThe 2.x versions of NetWare MultiProtocol Router---2.0, 2.1, and 2.11---as well as NetWare WAN Links 2.0 and NetWare MultiProtocol Router Plus 2.1x, support RIP-based IPX routing. In this case, the servers or dedicated routers running these products continue to run RIP and SAP. NLSP interoperates with these systems.RENDERAS="SECT1"ID="FM54483"Interoperating with UnixWareIf one or more UnixWare servers or clients are on a LAN connected to one of the network interfaces and the users are running the internal UNIX® NetWare client instead of the DOS NetWare client, you must enable RIP and SAP explicitly on the interface connected to the LAN.IDREF="FM19870"Figure 7-1 shows how you configure this interface.LABEL="7-1" FLOAT="0"ID="FM19870"Configuring an Interface for UnixWareFILEREF="71unxwre.tif"PAGENUM=38 ID="BP45"PAGENUM=39If you are using NetWare 4.1 on the connected system, complete the following steps:PERFORMANCE="REQUIRED"Type the following command at the server prompt:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INETCFG MOREINFO="NONE"<Enter>The 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears.PERFORMANCE="REQUIRED"Complete the following tasks:These tasks are outlined in greater detail in the BOOK="cfg1_enu" COLLECTION="nw41"NetWare 4.1 Basic Protocol Configuration Guide. Refer to this document for detailed instructions if you are unfamiliar with the Internetworking Configuration utility (INETCFG).PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Make sure you have configured all necessary IPX protocol parameters.This includes setting the CLASS=MENUITEM MOREINFO="NONE"Routing Protocol parameter to CLASS=MENUITEM MOREINFO="NONE"NLSP with RIP/SAP Compatibility.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Bindings.PERFORMANCE="REQUIRED"Select the interface.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Expert Bind Options, then select 
CLASS=MENUITEM MOREINFO="NONE"RIP Bind Options; set the 
CLASS=MENUITEM MOREINFO="NONE"RIP State parameter to 
CLASS=MENUITEM MOREINFO="NONE"On.PERFORMANCE="REQUIRED"Return to the 
CLASS=MENUITEM MOREINFO="NONE"Expert Bind Options window, then select 
CLASS=MENUITEM MOREINFO="NONE"SAP Bind Options; set the 
CLASS=MENUITEM MOREINFO="NONE"SAP State parameter to 
CLASS=MENUITEM MOREINFO="NONE"On.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc>, then select 
CLASS=MENUITEM MOREINFO="NONE"Yes to save your changes.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to exit INETCFG, then type the following command at the server prompt:
FORMAT="LINESPECIFIC"MOREINFO="NONE"IDXID="w4966"BOOK="_idx" COLLECTION="nw41" TIDREF="i3728"
REINITIALIZE SYSTEM MOREINFO="NONE"<Enter>If the connected system is running IPX Upgrade for NetWare Servers 1.0, add the following MOREINFO="NONE"BIND command to the server AUTOEXEC.NCF file:FORMAT="LINESPECIFIC"MOREINFO="NONE"IDXID="w4967"BOOK="_idx" COLLECTION="nw41" TIDREF="i427"
BIND IPX boardname NET=network_number 
   RIP=YES SAP=YES
PAGENUM=40 ID="BP46"RENDERAS="SECT1"ID="FM49170"Interoperating with OS/2 Named PipesIf you are using IDXID="w4968"BOOK="_idx" COLLECTION="nw41" TIDREF="i3136"
OS/2 Named Pipes from version 2.01 or earlier of NetWare Client for OS/2 on a LAN connected to one of the network interfaces, you must enable RIP and SAP explicitly on the interface. The OS/2 Named Pipes that is part of version 2.10---the current version---of NetWare Client for OS/2 does not have this requirement.IDREF="FM55339"Figure 7-2 shows how you configure this interface.LABEL="7-2" FLOAT="0"ID="FM55339"Configuring an Interface for OS/2 Named PipesFILEREF="72os2.tif"If you are using NetWare 4.1 on the connected system, complete the following steps:PERFORMANCE="REQUIRED"Type the following command at the server prompt:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INETCFG MOREINFO="NONE"<Enter>The Internetworking Configuration menu appears.
PAGENUM=40 ID="BP47"PAGENUM=41PERFORMANCE="REQUIRED"Complete the following tasks:These tasks are outlined in greater detail in the BOOK="cfg1_enu" COLLECTION="nw41"NetWare 4.1 Basic Protocol Configuration Guide. Refer to this document for detailed instructions if you are unfamiliar with INETCFG.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Make sure you have configured all necessary IPX protocol parameters.This includes setting the CLASS=MENUITEM MOREINFO="NONE"Routing Protocol parameter to CLASS=MENUITEM MOREINFO="NONE"NLSP with RIP/SAP Compatibility.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Bindings.PERFORMANCE="REQUIRED"Select the interface.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Expert Bind Options, then select 
CLASS=MENUITEM MOREINFO="NONE"RIP Bind Options; set the 
CLASS=MENUITEM MOREINFO="NONE"RIP State parameter to 
CLASS=MENUITEM MOREINFO="NONE"On.PERFORMANCE="REQUIRED"Return to the 
CLASS=MENUITEM MOREINFO="NONE"Expert Bind Options window, then select 
CLASS=MENUITEM MOREINFO="NONE"SAP Bind Options; set the 
CLASS=MENUITEM MOREINFO="NONE"SAP State parameter to 
CLASS=MENUITEM MOREINFO="NONE"On.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc>, then select 
CLASS=MENUITEM MOREINFO="NONE"Yes to save your changes.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to exit INETCFG, then type the following command at the server prompt:
FORMAT="LINESPECIFIC"MOREINFO="NONE"REINITIALIZE SYSTEM MOREINFO="NONE"<Enter>If the connected system is running IPX Upgrade for NetWare Servers 1.0, add the following MOREINFO="NONE"BIND command to the server AUTOEXEC.NCF file:FORMAT="LINESPECIFIC"MOREINFO="NONE"BIND IPX boardname NET=network_number 
   RIP=YES SAP=YESThe OS/2 Named Pipes that is part of version 2.10---the current version---of NetWare Client for OS/2 does not require RIP and SAP to be active; in this case, just type the MOREINFO="NONE"BIND command for the interface as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"BIND IPX boardname NET=network_number
PAGENUM=41 ID="BP48"PAGENUM=42RENDERAS="SECT1"ID="FM80672"Interoperating with NetWare/IPIf you install NLSP software on a server that is running IDXID="w4969"BOOK="_idx" COLLECTION="nw41" TIDREF="i2832"
NetWare/IP, you must enable RIP and SAP and disable NLSP on the interface to which IPX is bound.IDREF="FM20360"Figure 7-3 shows how you configure this interface.LABEL="7-3" FLOAT="0"ID="FM20360"Configuring an Interface for NetWare/IPFILEREF="73nwip.tif"If you are using NetWare 4.1 on the connected system, complete the following steps:PERFORMANCE="REQUIRED"Type the following command at the server prompt:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INETCFG MOREINFO="NONE"<Enter>The 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears.
PAGENUM=42 ID="BP49"PAGENUM=43PERFORMANCE="REQUIRED"Complete the following tasks:These tasks are outlined in greater detail in the BOOK="cfg1_enu" COLLECTION="nw41"NetWare 4.1 Basic Protocol Configuration Guide. Refer to this document for detailed instructions if you are unfamiliar with INETCFG.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Make sure you have configured all necessary IPX protocol parameters.This includes setting the CLASS=MENUITEM MOREINFO="NONE"Routing Protocol parameter to CLASS=MENUITEM MOREINFO="NONE"NLSP with RIP/SAP Compatibility.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Bindings.PERFORMANCE="REQUIRED"Select an interface to which IPX is already bound or create a new binding.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Expert Bind Options, then select 
CLASS=MENUITEM MOREINFO="NONE"RIP Bind Options; set the 
CLASS=MENUITEM MOREINFO="NONE"RIP State parameter to 
CLASS=MENUITEM MOREINFO="NONE"On.PERFORMANCE="REQUIRED"Return to the 
CLASS=MENUITEM MOREINFO="NONE"Expert Bind Options window, then select 
CLASS=MENUITEM MOREINFO="NONE"SAP Bind Options; set the 
CLASS=MENUITEM MOREINFO="NONE"SAP State parameter to 
CLASS=MENUITEM MOREINFO="NONE"On.PERFORMANCE="REQUIRED"Return to the 
CLASS=MENUITEM MOREINFO="NONE"Expert Bind Options window, then select 
CLASS=MENUITEM MOREINFO="NONE"NLSP Bind Options; set the 
CLASS=MENUITEM MOREINFO="NONE"NLSP State parameter to 
CLASS=MENUITEM MOREINFO="NONE"Off.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc>, then select 
CLASS=MENUITEM MOREINFO="NONE"Yes to save your changes.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to exit INETCFG, then type the following command at the server prompt:
FORMAT="LINESPECIFIC"MOREINFO="NONE"REINITIALIZE SYSTEM MOREINFO="NONE"<Enter>If the connected system is running IPX Upgrade for NetWare Servers 1.0, add the following MOREINFO="NONE"BIND command to the server AUTOEXEC.NCF file:FORMAT="LINESPECIFIC"MOREINFO="NONE"BIND IPX boardname NET=network_number 
   RIP=YES SAP=YES NLSP=NO