#EDIR DATA#
DOCTYPE='BOOK' PUBLICID='' SYSTEMID='/dtd/docbook.dtd'IPX ReferenceIPX ReferenceNovell, 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=11 ID="BP1"About This ReferenceThis reference is written for the network administrator responsible for setting up and maintaining NetWare 4.1 software running the Internetwork Packet ExchangeTM (IPXTM) protocol.As the administrator, you must plan and implement the connection of the router to the physical internetwork. This task involves laying the network cables, installing network interface boards, adding and removing nodes, and placing bridges and routers. In addition, you are responsible for installing and configuring the network software. To perform these tasks, you should have technical knowledge of protocols, network addressing, routing, and operational issues.This reference provides the information you need to understand the IPX protocol for the router, as well as descriptions of configuration parameters. It is not intended to provide software installation information or detailed configuration information.RENDERAS="SECT1"Chapter SummariesThis section briefly summarizes each chapter in this reference. Use these summaries to help you locate specific topics, or to help you decide which portions of this reference contain new information.IDREF="FM70134"Chapter 1, "Introduction to NetWare IPX Router," describes the principal features of NetWare IPX RouterTM software for NetWare 4.1.IDREF="FM12933"Chapter 2, "IPX Routing Concepts," describes the processes and protocols that govern IPX routing in the NetWare environment.IDREF="FM19231"Chapter 3, "NetWare Link Services Protocol Concepts," describes the NetWare Link Services ProtocolTM (NLSPTM) protocol, Novell's link state routing protocol for IPX internetworks.PAGENUM=12 ID="BP2"IDREF="FM64625"Chapter 4, "IPX Configuration Parameters," provides detailed descriptions of the parameters required to configure the different IPX features, including protocol configuration, routing configuration, filter configuration, tunnel configuration, and binding configuration.RENDERAS="SECT1"Conventions Used in This ReferenceThe NetWare 4.1 IPX Reference uses the documentation conventions described in this section. The following sections describe the conventions used:MARK=BULLETIDREF="FM93971""Parameter Paths" IDREF="FM39110""Terminology"IDREF="FM54953""New Terms and Important Information"IDREF="FM20495""System Messages"IDREF="FM28323""User Input"IDREF="FM65826""Special Characters"IDREF="FM10768""Graphic Symbols"RENDERAS="SECT2"ID="FM93971"Parameter PathsThis reference 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)PAGENUM=12 ID="BP3"PAGENUM=13Parameter 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="FM39110"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="FM54953"New Terms and Important InformationHighlighting emphasizes new terms and important information.RENDERAS="SECT2"ID="FM20495"System MessagesRegular (nonboldface, nonitalic) monospaced character strings represent system prompts or responses; for example:FORMAT="LINESPECIFIC"MOREINFO="NONE"message exampleRENDERAS="SECT2"ID="FM28323"User InputThis reference 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>PAGENUM=13 ID="BP4"PAGENUM=14Highlighted 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="FM65826"Special CharactersThis reference 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>Characters 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.PAGENUM=15 ID="BP5"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="FM10768"Graphic SymbolsIn printed documentation, the following symbols appear in the left margin to identify different categories of information: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. 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.PAGENUM=15 ID="BP6"PAGENUM=16RENDERAS="SECT1"Related Novell PublicationsSee the following Novell publications for information about IPX, NLSP, RIP, SAP, and related subjects: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="nlsp_enu" COLLECTION="nw41"NetWare 4.1 NLSP Migration Guide (Novell part number 100-002448-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)RENDERAS="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="BP7"ID="FM70134"Introduction to NetWare IPX RouterThis chapter introduces NetWare® IPX RouterTM software, Novell's IPXTM routing software for NetWare products. It describes the principal features of the product and identifies some of the NetWare Loadable ModuleTM (NLMTM) files that support these features.This chapter contains the following sections:MARK=BULLETIDREF="FM57561""Background"This section explains the need for a more efficient, scalable routing protocol for IPX networks.IDREF="FM15766""NetWare IPX Router Features"This section describes the principal features and capabilities of NetWare IPX Router.RENDERAS="SECT1"ID="FM57561"BackgroundOver the last few years, IPX networks have become larger and more complex. NetWare resources and services that were once LAN-based are now distributed over wide area links and across mixed topologies. Performance, reliability, and efficient use of network bandwidth are now primary considerations, especially for WAN connections.Novell developed NetWare IPX Router to meet the demands of large IPX internetworks. In addition to providing full Routing Information Protocol/Service Advertising Protocol (RIP/SAP) functionality, NetWare IPX Router provides NetWare Link Services ProtocolTM (NLSPTM) protocol, Novell's link state routing protocol for IPX networks. NLSP offers better performance, reliability, and scalability than the IPX RIP routing traditionally employed by NetWare servers.PAGENUM=2 ID="BP8"RENDERAS="SECT1"ID="FM15766"NetWare IPX Router FeaturesIDXID="w3414"BOOK="_idx" COLLECTION="nw41" TIDREF="i2750"IDXID="w3415"BOOK="_idx" COLLECTION="nw41" TIDREF="i1442"
The rest of this chapter summarizes the principal features of NetWare IPX Router.RENDERAS="SECT2"RIP/SAP CompatibilityIDXID="w3416"BOOK="_idx" COLLECTION="nw41" TIDREF="i2750"IDXID="w3417"BOOK="_idx" COLLECTION="nw41" TIDREF="i3872"
NetWare has traditionally used two communication protocols to propagate information throughout an IPX internetwork:MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"RIP---Distance vectorIDXID="w3418"BOOK="_idx" COLLECTION="nw41" TIDREF="i1153"
routing protocol that NetWare uses to exchange routing informationCLASS=MENUITEM MOREINFO="NONE"SAP---NetWare protocol used to advertise network services and the addresses from which these services are availableNetWare IPX Router is compatible with current IPX RIP networks and with service-advertising ("SAPing") devices, such as print and file servers. Such backward compatibility makes it possible for NetWare IPX Router to operate in environments that use RIP- and SAP-based devices from Novell or from third-party manufacturers.Because NLSP and RIP routers can operate simultaneously on the same IPX internetwork, you can migrateIDXID="w3419"BOOK="_idx" COLLECTION="nw41" TIDREF="i2454"
your network from RIP to NLSP without interrupting routing services. To read more about migrating your network to NLSP, see the BOOK="nlsp_enu" COLLECTION="nw41"NetWare 4.1 NLSP Migration Guide.NLSP detects non-NLSP devices on the network. To maintain interoperability in mixed routing environments, NLSP routers periodically broadcast RIP and SAP information, but restrict those broadcasts to the network segments served by the non-NLSP devices. This avoids broadcasting routing information that is relevant only to the non-NLSP devices throughout the entire internetwork. On networks using only NLSP routers, RIP and SAP are disabled automatically.To read more about RIP and SAP, see IDREF="FM12933"Chapter 2, "IPX Routing Concepts."To read more about NLSP, see IDREF="FM19231"Chapter 3, "NetWare Link Services Protocol Concepts."PAGENUM=3 ID="BP9"RENDERAS="SECT2"Link State RoutingIDXID="w3420"BOOK="_idx" COLLECTION="nw41" TIDREF="i2750"IDXID="w3421"BOOK="_idx" COLLECTION="nw41" TIDREF="i2116"
Routers on an IPX internetwork exchange information about themselves and the network segments to which they are attached. Such information can include router node addresses, network numbers, the cost of a path, media types, and so on. Each router uses this information to determine the best path by which to send outbound packets. Depending on various factors, this might be the fastest or least-expensive path---not necessarily the most direct. RIP routers use the distance vector algorithm as the basis for their routing operations and decisions; NLSP routers use the link state algorithm.Routers using the traditional distance vector algorithm periodically exchange information about network services and communication links with their immediate neighbors. Each node on the network consolidates the information it receives and passes it on to other routers, servers, and end nodes.NLSP routers using the link state algorithm broadcast or multicast information about themselves to every node they can reach. Unlike distance vector routers, which periodically broadcast routing and service information, link state routers send routing information only when a change occurs in a route or service.Every NLSP router keeps the same "road map" representing the states of all links and routers on an internetwork. Each router keeps a record of all the routers, the links connecting them, the operational status of the routers and links, and related parameters.NetWare IPX Router implements NLSP link state routing through IPXRTR.NLM, the router protocol stack. IPXRTR gathers and broadcasts link state information, makes routing decisions based on that information, and forwards packets accordingly.Link state routing---as implemented by NLSP---offers the following advantages over traditional distance vector routing:MARK=BULLETAbility to interconnect larger IPX networks and handle more complex topologiesFaster convergence of routing information across the networkLess routing traffic---an important advantage for WAN connectionsPAGENUM=4 ID="BP10"To read more about distance vector and link state routing protocols, see BOOK="cncptenu" COLLECTION="nw41"NetWare 4.1 Concepts.To read more about NLSP, see IDREF="FM19231"Chapter 3, "NetWare Link Services Protocol Concepts."RENDERAS="SECT2"FilteringIDXID="w3422"BOOK="_idx" COLLECTION="nw41" TIDREF="i2750"IDXID="w3423"BOOK="_idx" COLLECTION="nw41" TIDREF="i1500"
You can control the flow of IPX packets, routing and service information, and NetBIOS packets on your internetwork. You use the Filter Configuration utility (IDXID="w3424"BOOK="_idx" COLLECTION="nw41" TIDREF="i1493"
FILTCFG) to configure filters for incoming and outgoing packets, and packets that are routed to processes within the router. Packets can be filtered by source and destination addresses and socket numbers, interface number, and packet type (IPX or NetBIOS, for example).For RIP packets, you can apply routing filters on acceptance or on advertisement of the route. For SAP packets, you can apply service filters on acceptance or on advertisement of the service.You cannot filter routes and services between routers running NLSP. You can, however, filter routes and services between NLSP routers that connect routing areas. For general information about routing areas, see IDREF="FM19231"Chapter 3, "NetWare Link Services Protocol Concepts." For information about implementing routing areas in a network, see the BOOK="nlsp_enu" COLLECTION="nw41"NetWare 4.1 NLSP Migration Guide.To read more about filtering on an IPX internetwork, see the BOOK="cfg2_enu" COLLECTION="nw41"NetWare 4.1 Advanced Protocol Configuration and Management Guide.RENDERAS="SECT2"IPX Network ManagementIDXID="w3425"BOOK="_idx" COLLECTION="nw41" TIDREF="i2321"
You can monitor and IDXID="w3426"BOOK="_idx" COLLECTION="nw41" TIDREF="i4579"
troubleshoot your IPX internetwork with IDXID="w3427"BOOK="_idx" COLLECTION="nw41" TIDREF="i1963"
the IPX network management console (IPXCON). IPXCON uses SNMP over IPX or UDP/IP to monitor remote servers, routers, or network segments on the internetwork, enabling you to view the following information:MARK=BULLETNumber of IPX packets being received, sent, and forwarded by a routerAll possible paths by which IPX packets can reach their destinationPAGENUM=5 ID="BP11"Active links and routers on a remote network segmentActive routing protocols on a routerReachable networksAvailable servicesIPXCON uses the following files to retrieve routing statistics and other network information from a router:MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"IPXRTRNM.NLM---Instrumentation of the IPX, NLSP, and RIP/SAP Management Information Base (MIB) variables. IPXRTRNM gathers IPX routing statistics and provides them to IPXCON through SNMP.NLM.CLASS=MENUITEM MOREINFO="NONE"SNMP.NLM---IDXID="w3428"BOOK="_idx" COLLECTION="nw41" TIDREF="i2807"
NetWare SNMP Agent. SNMP.NLM initiates and responds to requests for management information.You can run IPXCON each time you restart the router by putting the command LOAD IPXCON in the AUTOEXEC.NCF file, or by loading it from the server prompt whenever you need to use it. In either case, load IPXCON after you load IPXRTR.To read more about IPXCON and managing network protocols, see the BOOK="cfg2_enu" COLLECTION="nw41"NetWare 4.1 Advanced Protocol Configuration and Management Guide.RENDERAS="SECT2"Larger Network DiametersOn a RIP-based IPX network, IPX packets with a hop count of 16 are discarded. With NLSP, IPX packets can now traverse up to 127 hops before being discarded. You set this number through the CLASS=MENUITEM MOREINFO="NONE"Hop Count IDXID="w3429"BOOK="_idx" COLLECTION="nw41" TIDREF="i1687"
Limit parameter. This feature makes it possible to IDXID="w3430"BOOK="_idx" COLLECTION="nw41" TIDREF="i553"
build larger IPX internetworks in which IPX packets can be forwarded from one end to the other.Propagation of Type 20 packets, which include NetBIOS, is still limited to eight hops.PAGENUM=5 ID="BP12"PAGENUM=6RENDERAS="SECT2"Load BalancingIDXID="w3431"BOOK="_idx" COLLECTION="nw41" TIDREF="i2927"
NLSP supports IDXID="w3432"BOOK="_idx" COLLECTION="nw41" TIDREF="i2137"load balancing, a method of distributing outbound traffic among equal-cost routes to the same destination.You specify the number of equal-cost routes from the CLASS=MENUITEM MOREINFO="NONE"IDXID="w3433"BOOK="_idx" COLLECTION="nw41" TIDREF="i2355"
Maximum Number of Path Splits parameter. By distributing outbound traffic among the available routes, the router increases its effective throughput.For more information about load balancing and equal-cost routes, see IDREF="FM79930""Balancing Traffic Loads Over Equal-Cost Routes."RENDERAS="SECT2"Multiple Interfaces to the Same LANNLSP routers with two or more network interface boards can bind each interface to the same LAN. This is one method of load balancing that increases the effective throughput of the router.RENDERAS="SECT2"Internetworking Configuration UtilityIDXID="w3434"BOOK="_idx" COLLECTION="nw41" TIDREF="i1791"
The Internetworking Configuration utility (INETCFG) is a menu-driven utility that simplifies the task of configuring LANs  to operate with multiple network and routing protocols. INETCFG supersedes the manual use of most LOAD and BIND commands.INETCFG comprises a hierarchy of menus and windows from which you configure related sets of parameters. You can enter names of new configurations, configure the IPX protocol, bind IPX to a network interface, and override default settings---all without using the command line.All INETCFG parameters are defined in IDREF="FM64625"Chapter 4, "IPX Configuration Parameters."LABEL="2"PAGENUM=7 ID="BP13"ID="FM12933"IPX Routing ConceptsIDXID="w3435"BOOK="_idx" COLLECTION="nw41" TIDREF="i1957"
This chapter IDXID="w3436"BOOK="_idx" COLLECTION="nw41" TIDREF="i3184"IDXID="w3437"BOOK="_idx" COLLECTION="nw41" TIDREF="i3897"
describes the processes and protocols that govern IPXTM routing in the NetWare® environment. In particular, it examines the mechanics of packet routing and the administration of routing and service information on an IPX internetwork.Every NetWare 3TM and NetWare 4TM server has a built-in capability to route IPX packets. Because the focus of this chapter is IPX routing, the term NetWare router is used to denote such a server.This chapter contains the following sections:MARK=BULLETIDREF="FM86817""NetWare Protocols Overview"This section presents a brief overview of the NetWare communication protocols.IDREF="FM88564""NetWare Communication Protocols"This section provides a more in-depth look at each NetWare protocol with particular emphasis on IPX, Routing Information Protocol (RIP), and Service Advertising Protocol (SAP).RENDERAS="SECT1"ID="FM86817"NetWare Protocols OverviewIDXID="w3438"BOOK="_idx" COLLECTION="nw41" TIDREF="i699"
Each of the NetWare communication protocols plays a different role in enabling a NetWare router to perform its tasks. Media Access Control (MAC) protocols and IPX provide the addressing mechanism that delivers packets to their destination. The RIP, SAP, and NLSPTM protocols provide the means by which routers gather routing and service information and share it with other routers.PAGENUM=7 ID="BP14"PAGENUM=8Although the NCPTM protocol does not play a direct role in routing, it does provide session control and packet-level error checking between NetWare workstations and routers. Similarly, the IDXID="w3439"BOOK="_idx" COLLECTION="nw41" TIDREF="i4240"
Sequenced Packet ExchangeTM (SPXTM) protocol neither routes packets nor advertises service information, but guarantees delivery of each packet to its destination.RENDERAS="SECT1"ID="FM88564"NetWare Communication ProtocolsIDXID="w3440"BOOK="_idx" COLLECTION="nw41" TIDREF="i699"
The following protocols govern IDXID="w3441"BOOK="_idx" COLLECTION="nw41" TIDREF="i3609"
communication between NetWare routers and workstations and define the format of the packets these devices use to exchange information: COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="8*"COLNAME=2 COLWIDTH="18*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ProtocolCOLNAME=2 ROTATE="0" MOREROWS="0"For more information, see:VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"MACCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM86919""MAC."COLNAME=1 ROTATE="0" MOREROWS="0"IPXCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM44941""IPX."COLNAME=1 ROTATE="0" MOREROWS="0"RIPCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM87687""RIP."COLNAME=1 ROTATE="0" MOREROWS="0"SAPCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM26446""SAP."COLNAME=1 ROTATE="0" MOREROWS="0"NLSPCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM19231"Chapter 3, "NetWare Link Services Protocol Concepts."COLNAME=1 ROTATE="0" MOREROWS="0"NCPCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM33747""NCP."COLNAME=1 ROTATE="0" MOREROWS="0"SPXCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM11600""SPX."COLNAME=1 ROTATE="0" MOREROWS="0"NetBIOSCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM82047""NetBIOS."Additional protocols can operate in the NetWare environment; however, this chapter describes only those relevant to IPX routing.IDREF="FM43650"Figure 2-1 shows the relative mapping of the NetWare protocols to the Open Systems Interconnection (OSI) Reference Model. Because this model represents only a basic framework for networking functionality, not all NetWare protocols fit neatly into a single functional layer.PAGENUM=9 ID="BP15"LABEL="2-1" FLOAT="0"ID="FM43650"Mapping NetWare Protocols to the OSI Reference Model FILEREF="osinw.tif"The higher-level protocols (NetBIOS, SAP, NCP, IDXID="w3442"BOOK="_idx" COLLECTION="nw41" TIDREF="i4240"
SPX, NLSP, and RIP) rely on the MAC protocols and IPX to handle lower-level communications, such as node addressing. With the exception of NetBIOS, NCP, and SPX, each of these protocols plays a role in the operation of IPX routing.PAGENUM=9 ID="BP16"PAGENUM=10RENDERAS="SECT2"ID="FM86919"MACIDXID="w3443"BOOK="_idx" COLLECTION="nw41" TIDREF="i3609"
MAC IDXID="w3444"BOOK="_idx" COLLECTION="nw41" TIDREF="i2253"
protocols operate at the OSI Data-Link layer. Their primary task is to transport packets from one node to another on a network segment. Several MAC protocols have been defined, many of which can be used with NetWare. Following are three of the most common MAC protocols currently in use:MARK=BULLETIEEE 802.5 (token ring)IEEE 802.3 (Ethernet)ARCNETThe 802.5 and 802.3 protocols were defined by the Institute of Electrical and Electronic Engineers (IEEE). IDXID="w3445"BOOK="_idx" COLLECTION="nw41" TIDREF="i281"
ARCNET was developed by Datapoint, Inc.MAC protocols define the addressing that identifies each node on a network segment. Node addressing is implemented within the hardware of each network interface board. In the case of Ethernet, token ring, and FDDI boards, these physical addresses are assigned at the factory. The IEEE administers physical addresses to ensure that no two manufacturers use the same one.Some physical addresses are assigned by setting jumpers or switches on the board or through configuration software; this is the case with ARCNET boards.MAC protocols also provide bit-level error checking in the form of a cyclic redundancy check (CRC). The CRC is appended at the end of every transmitted packet, also called the MAC trailer. The CRC ensures that every received packet is free of corruption.To get a packet to its destination node, MAC protocols place the node addresses and other information in a MAC header at the front of every outgoing packet, and the CRC in the MAC trailer.PAGENUM=10 ID="BP17"PAGENUM=11RENDERAS="SECT3"MAC HeaderIDXID="w3446"BOOK="_idx" COLLECTION="nw41" TIDREF="i2252"
The MAC header contains source node and destination node address fields. These fields contain the physical addresses that indicate where the packet originated and where it is going. Each interface board attached to the network checks the CLASS=MENUITEM MOREINFO="NONE"Destination Address field in the MAC header of every packet it receives. If the board finds its own address in this field, or if the packet is a broadcast packet (intended for all nodes), the board copies the packet. The packet is then passed to a higher-layer process---such as IPX---for further examination and processing.The destination and source MAC addresses are the same as those in the CLASS=MENUITEM MOREINFO="NONE"Destination Node and CLASS=MENUITEM MOREINFO="NONE"Source Node fields in the IPX header.The MAC header and trailer encapsulate each packet with the node addresses, the upper-layer protocol, the CRC, the message length, and additional information specific to the network medium. This information is specified in a format conforming to a particular frame type.RENDERAS="SECT3"Data-Link Frames and Frame TypesIDXID="w3447"BOOK="_idx" COLLECTION="nw41" TIDREF="i937"
A IDXID="w3448"BOOK="_idx" COLLECTION="nw41" TIDREF="i1568"frame is the IDXID="w3449"BOOK="_idx" COLLECTION="nw41" TIDREF="i1568"
data unit used for communication between two nodes on a network. The frame's MAC header contains information that specifies the sending and receiving nodes, the upper-layer protocol to which the frame is passed, and---for source-routed token ring networks---the exact forwarding path the packet follows to its destination.NetWare supports several frame types for interoperability with many different network protocols on various network media. These frame types are described in the following list:MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"IDXID="w3450"BOOK="_idx" COLLECTION="nw41" TIDREF="i1568"
802.2IDXID="w3451"BOOK="_idx" COLLECTION="nw41" TIDREF="i6" frames are used with IPX and OSI protocols, and include the following frame types:MARK=BULLETTOKEN-RING (for token ring networks)ETHERNET_802.2 (for Ethernet networks)FDDI_802.2 (for Fiber Distributed Data Interface---FDDI---networks)PAGENUM=11 ID="BP18"PAGENUM=12CLASS=MENUITEM MOREINFO="NONE"IDXID="w3452"BOOK="_idx" COLLECTION="nw41" TIDREF="i1568"
SNAPIDXID="w3453"BOOK="_idx" COLLECTION="nw41" TIDREF="i4183" (Sub-Network Access Protocol) frames are used with IPX, IP, and AppleTalk* Phase 2, and include the following frame types:MARK=BULLETTOKEN-RING_SNAP (for token ring networks)ETHERNET_SNAP (for Ethernet networks)FDDI_SNAP (for FDDI networks)CLASS=MENUITEM MOREINFO="NONE"IDXID="w3454"BOOK="_idx" COLLECTION="nw41" TIDREF="i1568"
802.3IDXID="w3455"BOOK="_idx" COLLECTION="nw41" TIDREF="i8" ("raw") frames can be used only with IPX on Ethernet networks.Before the release of NetWare 4, NetWare workstations and drivers were configured with ETHERNET_802.3 as the default frame type. The default frame type for NetWare 4 and later releases is ETHERNET_802.2. Note also that it is not possible to send IPX packets containing checksums encapsulated in ETHERNET_802.3 frames.CLASS=MENUITEM MOREINFO="NONE"IDXID="w3456"BOOK="_idx" COLLECTION="nw41" TIDREF="i1568"
ETHERNET_IIIDXID="w3457"BOOK="_idx" COLLECTION="nw41" TIDREF="i1355" frames can be used with IPX, IP, and AppleTalk Phase 1.You can configure multiple frame types on the same NetWare router or workstation. However, for two nodes on a network to communicate, they must have in common at least one frame type. If one node accepts only ETHERNET_802.3 frames and the other accepts only ETHERNET_802.2 frames, the nodes cannot communicate directly, although they share the same physical network. Also, using more than one frame type on a node does not increase packet throughput.You can also mix frame types and network protocols on the same network. For example, IP can use ETHERNET_II while IPX uses ETHERNET_802.2.RENDERAS="SECT2"ID="FM44941"IPXIDXID="w3458"BOOK="_idx" COLLECTION="nw41" TIDREF="i1949"
Novell adapted IPX from the Xerox* Network System (XNS*) Internet Datagram Protocol (IDP). IPX is a connectionless datagram protocol. ConnectionlessPAGENUM=13 ID="BP19" means that when a process running on a particular node uses IPX to communicate with a process on another node, no connection between the two nodes is established. Thus, IPX packets containing data are addressed and sent to their destinations, but there is no guarantee or verification of successful delivery. Any packet acknowledgment, or connection control, is provided by protocols above IPX, such as SPX. Datagram means that each packet is treated as an individual entity, having no logical or sequential relation to any other packet.IPX operates at the OSI Network layer. As a Network-layer protocol, IPX addresses and routes packets from one location to another on an IPX internetwork. IPX bases its routing decisions on the address fields in its header and on the information it receives from RIP or NLSP. IPX uses this information to forward packets to their destination node or to the next router, providing a path to the destination node.RENDERAS="SECT3"IPX Packet StructureIDXID="w3459"BOOK="_idx" COLLECTION="nw41" TIDREF="i1949"
The IPX IDXID="w3460"BOOK="_idx" COLLECTION="nw41" TIDREF="i3189"
packet is similar to an XNS IDP packet and consists of two IDXID="w3461"BOOK="_idx" COLLECTION="nw41" TIDREF="i1946"
parts:MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"30-byte IPX header---Includes the network, node, and socket addresses for both the destination and the sourceCLASS=MENUITEM MOREINFO="NONE"Data---Often includes the header of a higher-level protocol, such as SPXThe minimum IPX packet size---excluding the MAC header---is 30 bytes (IPX header only). Historically, the maximum size of routed IPX packets has been 576 bytes (IPX header and data). Until recently, all routed IPX packets were between 30 and 576 bytes. However, the IPX protocol has always allowed packet sizes up to 65,535 bytes.Media constraints typically limit the actual maximum packet size allowed to something less than 65,535. Ethernet II packets, for example, are limited to a data size of 1500 bytes, not including the MAC header.TheIDXID="w3462"BOOK="_idx" COLLECTION="nw41" TIDREF="i1934"
 IPX header is placed after the MAC header and before the data. IDREF="FM20860"Figure 2-2 shows the structure of an IPX packet.PAGENUM=14 ID="BP20"LABEL="2-2" FLOAT="0"ID="FM20860"IPX Packet Structure FILEREF="ipxpkt.tif"Following is a description of the IIDXID="w3463"BOOK="_idx" COLLECTION="nw41" TIDREF="i1942"
PX packet fields:MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"IDXID="w3464"BOOK="_idx" COLLECTION="nw41" TIDREF="i624"
Checksum---Packet integrity check.The checksum is used by the NetWare SFT IIITM (System Fault TolerantTM) software, NetWare 4, and newer versions of the NetWare shell (NETx.COM). Older versions of NetWare did not use the IPX checksum and required that this field be set to 0xFFFF.CLASS=MENUITEM MOREINFO="NONE"IDXID="w3465"BOOK="_idx" COLLECTION="nw41" TIDREF="i1942"
Packet Length---LCLASS=MENUITEM MOREINFO="NONE"IDXID="w3466"BOOK="_idx" COLLECTION="nw41" TIDREF="i3181"ength, in bytes, of the complete packet, which is the length of the IPX header plus the length of the data.The packet length is at least 30 bytes (for the IPX header).PAGENUM=15 ID="BP21"CLASS=MENUITEM MOREINFO="NONE"IDXID="w3467"BOOK="_idx" COLLECTION="nw41" TIDREF="i1942"
Transport ControlIDXID="w3468"BOOK="_idx" COLLECTION="nw41" TIDREF="i4562"
---Number of routers a packet has traversed on the way to its destination.On a traditional, RIP-based IPX router, IPX packets whose CLASS=MENUITEM MOREINFO="NONE"Transport Control field reaches a value of 16 are discarded. With NLSP, an IPX packet can travel up to 127 hops to reach its destination. You make this possible by setting the CLASS=MENUITEM MOREINFO="NONE"Hop Count Limit parameter from the Internetworking Configuration utility (INETCFG). This enables you to limit the number of routers (hops) an IPX packet traverses before it is discarded.Sending nodes always set the CLASS=MENUITEM MOREINFO="NONE"Transport Control field to zero when building an IPX packet. When a router receives a packet that requires further routing, it increments this field by one and forwards the packet.CLASS=MENUITEM MOREINFO="NONE"IDXID="w3469"BOOK="_idx" COLLECTION="nw41" TIDREF="i1942"
Packet TypeIDXID="w3470"BOOK="_idx" COLLECTION="nw41" TIDREF="i3191"
---Type of service offered or required by the packet.Novell currently uses the packet types listed in IDREF="FM19196"Table 2-1. LABEL="2-1" PGWIDE=0 TOCENTRY="1"IDXID="w3471"BOOK="_idx" COLLECTION="nw41" TIDREF="i1947"ID="FM19196"Packet TypesCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="9*"COLNAME=2 COLWIDTH="6*"COLNAME=3 COLWIDTH="9*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Packet TypeCOLNAME=2 ROTATE="0" MOREROWS="0"Field Value (Hex)COLNAME=3 ROTATE="0" MOREROWS="0"PurposeVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"NetWare Link Services ProtocolCOLNAME=2 ROTATE="0" MOREROWS="0"0x00COLNAME=3 ROTATE="0" MOREROWS="0"NLSP packetsCOLNAME=1 ROTATE="0" MOREROWS="0"Routing informationCOLNAME=2 ROTATE="0" MOREROWS="0"0x01COLNAME=3 ROTATE="0" MOREROWS="0"RIP packetsCOLNAME=1 ROTATE="0" MOREROWS="0"Service advertisingCOLNAME=2 ROTATE="0" MOREROWS="0"0x04COLNAME=3 ROTATE="0" MOREROWS="0"SAP packetsCOLNAME=1 ROTATE="0" MOREROWS="0"SequencedCOLNAME=2 ROTATE="0" MOREROWS="0"0x05COLNAME=3 ROTATE="0" MOREROWS="0"SPX packetsCOLNAME=1 ROTATE="0" MOREROWS="0"NetWare Core ProtocolCOLNAME=2 ROTATE="0" MOREROWS="0"0x11COLNAME=3 ROTATE="0" MOREROWS="0"NCP packetsCOLNAME=1 ROTATE="0" MOREROWS="0"PropagatedCOLNAME=2 ROTATE="0" MOREROWS="0"0x14COLNAME=3 ROTATE="0" MOREROWS="0"NetBIOS and other propagated packetsCLASS=MENUITEM MOREINFO="NONE"IDXID="w3472"BOOK="_idx" COLLECTION="nw41" TIDREF="i1942"
Destination Network---NIDXID="w3473"BOOK="_idx" COLLECTION="nw41" TIDREF="i1013"
umber of the network to which the destination node is attached.When a sending node sets this field to zero, the destination node is assumed to be on the same network segment as the sending (or source) node.PAGENUM=15 ID="BP22"PAGENUM=16A special case exists when a workstation sends SAP Get Nearest Server and RIP Get Local Target (or Route Request) broadcast requests at initialization time. Because the workstation does not yet know which network it belongs to, it sets both the CLASS=MENUITEM MOREINFO="NONE"Source Network and CLASS=MENUITEM MOREINFO="NONE"Destination Network fields to 0 for these requests. When a router receives one of these requests, it sends a reply directly to the sending workstation, filling in the CLASS=MENUITEM MOREINFO="NONE"Source Network and CLASS=MENUITEM MOREINFO="NONE"Destination Network fields with the appropriate network numbers.IPX does not have a broadcast network number (such as 0xFFFFFFFF). However, a network number of 0xFFFFFFFF has special meaning in some contexts (involving RIP, primarily). Subsequently, you should not assign this number to any network.CLASS=MENUITEM MOREINFO="NONE"IDXID="w3474"BOOK="_idx" COLLECTION="nw41" TIDREF="i1942"
Destination NodeIDXID="w3475"BOOK="_idx" COLLECTION="nw41" TIDREF="i1014"
---Physical address of the destination node.Not all LAN topologies use the same size address field. A node on an Ethernet network requires all six bytes to specify its address; a node on an Omninet network requires only one byte.A node address of 0xFFFFFFFFFFFF (that is, six bytes of 0xFF) broadcasts the packet to all nodes on the destination network.CLASS=MENUITEM MOREINFO="NONE"IDXID="w3476"BOOK="_idx" COLLECTION="nw41" TIDREF="i1942"
Destination SocketIDXID="w3477"BOOK="_idx" COLLECTION="nw41" TIDREF="i1017"
---Socket address of the packet destination process.Sockets route packets to different processes within a single node. Novell reserves several sockets for use in the NetWare environment.IPX does not have a broadcast socket number (such as 0xFFFF).CLASS=MENUITEM MOREINFO="NONE"IDXID="w3478"BOOK="_idx" COLLECTION="nw41" TIDREF="i1942"
Source NetworkIDXID="w3479"BOOK="_idx" COLLECTION="nw41" TIDREF="i4208"
---Number of the network to which the source node is attached. If a sending node sets this field to zero, the local network to which the source is connected is unknown. For routers, the rules that apply to the CLASS=MENUITEM MOREINFO="NONE"Destination Network field also apply to the CLASS=MENUITEM MOREINFO="NONE"Source Network field, except that routers can propagate packets that were received with this field set to zero.CLASS=MENUITEM MOREINFO="NONE"IDXID="w3480"BOOK="_idx" COLLECTION="nw41" TIDREF="i1942"
Source NodeIDXID="w3481"BOOK="_idx" COLLECTION="nw41" TIDREF="i4209"
---Physical address of the source node.Broadcast addresses are not allowed.PAGENUM=16 ID="BP23"PAGENUM=17CLASS=MENUITEM MOREINFO="NONE"IDXID="w3482"BOOK="_idx" COLLECTION="nw41" TIDREF="i1942"
Source SocketIDXID="w3483"BOOK="_idx" COLLECTION="nw41" TIDREF="i4217"
---Socket address of the process that transmits the packet.Processes communicating in a peer-to-peer fashion do not need to send and receive on the same socket number.In a workstation-server situation, the server usually "listens" on a specific socket for service requests. In such a case, the source socket is not necessarily the same or even significant. All that matters is that the server reply to the source socket. For example, all NetWare file servers have the same socket address, but requests to them can originate from any socket number.Source socket numbers follow the same conventions as those for destination sockets.CLASS=MENUITEM MOREINFO="NONE"IDXID="w3484"BOOK="_idx" COLLECTION="nw41" TIDREF="i1942"
Higher-Level Protocol HeadersIDXID="w3485"BOOK="_idx" COLLECTION="nw41" TIDREF="i1672"---Headers of higher-level NetWare protocols, such as NCP or SPX. These headers occupy the data portion of the IPX packet.RENDERAS="SECT3"IPX AddressingIDXID="w3486"BOOK="_idx" COLLECTION="nw41" TIDREF="i107"IDXID="w3487"BOOK="_idx" COLLECTION="nw41" TIDREF="i107"IDXID="w3488"BOOK="_idx" COLLECTION="nw41" TIDREF="i107"
IPX defines its own IDXID="w3489"BOOK="_idx" COLLECTION="nw41" TIDREF="i1871"
internetwork and IDXID="w3490"BOOK="_idx" COLLECTION="nw41" TIDREF="i1886"
intranode IDXID="w3491"BOOK="_idx" COLLECTION="nw41" TIDREF="i1926"
addressing. For intranetwork (node) addressing, IPX uses the physical address assigned to the network interface board.The IDXID="w3492"BOOK="_idx" COLLECTION="nw41" TIDREF="i1939"IPX network address uniquely identifies an IPX server on an IPX network and individual processes within the server. A complete IPX network address is a 12-byte hexadecimal number comprising the following components:MARK=BULLETA four-byte network number (server)A six-byte node number (server)A two-byte socket number (server process)PAGENUM=17 ID="BP24"PAGENUM=18A complete IPX network address looks something like this:FORMAT="LINESPECIFIC"MOREINFO="NONE"FEDCBA98 1A2B3C5D7E9F 0453Each number is contained in a field in the IPX header and represents a source or destination network, node, or socket. The network number is used only for Network-layer operations, namely routing. The node number is used for local, or same-segment, packet transmission. The socket number directs a packet to a process operating within a node.Each component of the IPX address is described in the following sections.RENDERAS="SECT4"Network NumberThe IDXID="w3493"BOOK="_idx" COLLECTION="nw41" TIDREF="i2870"IDXID="w3494"BOOK="_idx" COLLECTION="nw41" TIDREF="i2870"
network number is the four-byte hexadecimal address that serves as the basis for IPX internetwork routing. Each network segment on an internetwork is assigned a unique network number. NetWare routers use this number to forward packets to their final destination segment.The network number can contain up to eight digits, including zeros. (Leading zeros are usually not displayed.) For example, FEDCBA98, 1234567D, and C7 are all valid network numbers. The numbers 0 and FFFFFFFF are not available for network addressing; IPX reserves these for special purposes.NetWare 3 and NetWare 4 servers have an additional identifier called an IDXID="w3495"BOOK="_idx" COLLECTION="nw41" TIDREF="i1854"IDXID="w3496"BOOK="_idx" COLLECTION="nw41" TIDREF="i2870"internal 
network number. This is a unique hexadecimal number between one and eight digits that is assigned to the server at installation. The internal network is a logical network that NetWare uses to advertise services and route IPX packets to the physical networks attached to the server.The internal network number overcomes some routing and connectivity limitations inherent to NetWare 2. These are summarized in the following paragraphs.A NetWare 2 server selects a primary interface and advertises its services as reachable through that interface. On a network with more than one server, packets might travel an extra hop to reach their destination.PAGENUM=19 ID="BP25"A NetWare 2 server loses network connectivity if its primary network interface board fails, even if the server has Network-layer connectivity through another interface. Consider a NetWare 2 server with connections to two networks. The server advertises its services through the primary interface attached to one of the networks. If that interface fails, workstations attached to the server through the second network might not be able to log in to the server.RENDERAS="SECT4"Node NumberThe IDXID="w3497"BOOK="_idx" COLLECTION="nw41" TIDREF="i2952"
node IDXID="w3498"BOOK="_idx" COLLECTION="nw41" TIDREF="i1941"
number is the six-byte hexadecimal address that identifies a device on an IPX network. This device can be a file server, router, workstation, or printer. The node number is identical to the physical address assigned to the interface board that connects the device to the network.The IPX header contains a CLASS=MENUITEM MOREINFO="NONE"Destination Node field and a CLASS=MENUITEM MOREINFO="NONE"Source Node field. These fields contain the same destination and source node addresses found in the MAC header. A NetWare workstation, for example, uses the destination node address to locate and forward packets to another workstation on the same network segment.IPX requires the node number to be unique only within the same IPX network. For example, a node on network FEDCBA98 can use the number 1A2B3C5D7E9F, and a node on network 1234567D can also use the number 1A2B3C5D7E9F. Because each node has a different network number, IPX recognizes each node as having a legitimate, unique address.RENDERAS="SECT4"Socket NumberThe IDXID="w3499"BOOK="_idx" COLLECTION="nw41" TIDREF="i4196"
socket IDXID="w3500"BOOK="_idx" COLLECTION="nw41" TIDREF="i1959"
number is the two-byte hexadecimal number that identifies the ultimate destination of an IPX packet within the node. This destination is actually a process---such as routing (RIP) or advertising (SAP)---that operates within the node. Because several processes are typically operating at any given time, socket numbers provide a type of "mail slot" by which each process can identify itself to IPX.A process that must communicate on the network requests that a socket number be assigned to it. Any packets that IPX receives that are addressed to that socket are passed on to the process. Socket numbers provide a quick method of routing packets within a node.PAGENUM=20 ID="BP26"IDREF="FM72136"Table 2-2 lists some socket numbers and processes used in the NetWare environment. LABEL="2-2" PGWIDE=0 TOCENTRY="1"ID="FM72136"NetWare Socket Numbers and ProcessesCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="9*"COLNAME=2 COLWIDTH="17*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Socket NumberCOLNAME=2 ROTATE="0" MOREROWS="0"ProcessVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"0x451COLNAME=2 ROTATE="0" MOREROWS="0"NetWare Core Protocol (NCP)COLNAME=1 ROTATE="0" MOREROWS="0"0x452COLNAME=2 ROTATE="0" MOREROWS="0"Service Advertising Protocol (SAP)COLNAME=1 ROTATE="0" MOREROWS="0"0x453COLNAME=2 ROTATE="0" MOREROWS="0"Routing Information Protocol (RIP)COLNAME=1 ROTATE="0" MOREROWS="0"0x455COLNAME=2 ROTATE="0" MOREROWS="0"Novell NetBIOSCOLNAME=1 ROTATE="0" MOREROWS="0"0x456COLNAME=2 ROTATE="0" MOREROWS="0"DiagnosticsCOLNAME=1 ROTATE="0" MOREROWS="0"0x9001COLNAME=2 ROTATE="0" MOREROWS="0"NetWare Link Services Protocol (NLSP)COLNAME=1 ROTATE="0" MOREROWS="0"0x9004COLNAME=2 ROTATE="0" MOREROWS="0"IPXWAN ProtocolSocket numbers between 0x4000 and 0x7FFF are dynamic sockets; these are used by workstations to communicate with file servers and other network devices. Socket numbers between 0x8000 and 0xFFFF are well-known sockets; these are assigned by Novell to specific processes. For example, 0x9001 is the socket number that identifies NLSP. Software developers writing NetWare applications can contact Novell to reserve well-known sockets.RENDERAS="SECT3"IPX RoutingIDXID="w3501"BOOK="_idx" COLLECTION="nw41" TIDREF="i3897"
NetWare routers interconnect different IDXID="w3502"BOOK="_idx" COLLECTION="nw41" TIDREF="i1957"
IPX network segments and receive instructions for addressing and routing packets between these segments from the IPX protocol. IPX accomplishes these and other Network-layer tasks with the help of RIP, SAP, and NLSP.RENDERAS="SECT4"When a Workstation Sends an IPX PacketIDXID="w3503"BOOK="_idx" COLLECTION="nw41" TIDREF="i1948"
Consider a NetWare workstation that wants to IDXID="w3504"BOOK="_idx" COLLECTION="nw41" TIDREF="i4025"PAGENUM=21 ID="BP27"send information to another workstation. If both workstations share the same network number (both are on the same segment), the sending workstation addresses and sends packets directly to the destination workstation's physical address. If the two workstations have different network numbers (each is on a different segment), the sending workstation must first find a router on its own segment that can forward packets to the segment on which the destination workstation resides.To find this router, the sending workstation broadcasts a RIP packet requesting the fastest route to the destination segment. The router on the sending segment with the shortest path to the destination segment responds to the request. In its response, the router includes its own network and node address in the IPX header.If the sending node is a router rather than a workstation, it does not need to broadcast a RIP request to get this information; the router gets it from its internal routing table.When the sending workstation knows the router node address, it addresses and sends packets to the destination workstation as follows:NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"The sending workstation places the destination node IPX network address---network, node, and socket numbers---in the corresponding destination fields of the IPX header.The sending workstation places its own IPX network address---network, node, and socket numbers---in the corresponding source fields of the IPX header. The sending workstation also fills out all other fields in the header.The sending workstation places the node address of the router that responded to the RIP request in the CLASS=MENUITEM MOREINFO="NONE"Destination Address field of the MAC header.The sending workstation places its own node address in the CLASS=MENUITEM MOREINFO="NONE"Source Address field of the MAC header.The sending workstation sends the packet.PAGENUM=21 ID="BP28"PAGENUM=22RENDERAS="SECT4"ID="FM34389"When a Router Receives an IPX PacketIDXID="w3505"BOOK="_idx" COLLECTION="nw41" TIDREF="i1948"
When a router IDXID="w3506"BOOK="_idx" COLLECTION="nw41" TIDREF="i3701"
receives an IPX packet, it does the following tasks:NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"The router checks the CLASS=MENUITEM MOREINFO="NONE"Transport Control field of the IPX packet header.A RIP router discards the packet if the value in this field is greater than 16.An NLSP router discards the packet if the value in this field is greater than the value of the CLASS=MENUITEM MOREINFO="NONE"Hop Count Limit parameter.The router checks the IPX header CLASS=MENUITEM MOREINFO="NONE"Packet Type field.If the Packet Type is 20 (0x14, NetBIOS), the packet is handled as follows:NUMERATION=LOWERALPHA CONTINUATION="RESTARTS" INHERITNUM="IGNORE"The router examines the CLASS=MENUITEM MOREINFO="NONE"Transport Control field of the IPX header. If this value is eight or greater, the router discards the packet. (Propagation of a NetBIOS packet is limited to eight networks.)The router compares each network number entry in the packet to the network number of the segment on which the router received the packet.If the router finds a match, it discards the packet to prevent multiple traversals of the same network segment. If the router finds no match, it performs the next step.The router places the address of the network segment from which the packet arrived in the next available CLASS=MENUITEM MOREINFO="NONE"Network Number field.The router increments the CLASS=MENUITEM MOREINFO="NONE"Transport Control field of the IPX header and broadcasts the packet to all directly connected network segments that are not represented in the CLASS=MENUITEM MOREINFO="NONE"Network Number fields.PAGENUM=22 ID="BP29"PAGENUM=23The router checks the IPX header CLASS=MENUITEM MOREINFO="NONE"Destination Address fields---network, node, and socket numbers---to determine how to route the packet.If the packet is addressed to the router, the appropriate socket process handles it internally; otherwise, the router forwards the packet.Packets that must be handled internally are those addressed directly to the router and those broadcast (Destination Node = 0xFFFFFFFFFFFF) to any network segment to which the router is directly connected. Usually, only RIP, SAP, and diagnostic packets fall into this category.RENDERAS="SECT4"When a Router Forwards an IPX PacketIDXID="w3507"BOOK="_idx" COLLECTION="nw41" TIDREF="i1948"
When IDXID="w3508"BOOK="_idx" COLLECTION="nw41" TIDREF="i1562"
forwarding packets, the router can take one of two possible actions. If the packet is destined for a network number to which the router is directly connected, the router does the following tasks:NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"The router places the destination node address from the IPX header in the CLASS=MENUITEM MOREINFO="NONE"Destination Address field of the MAC header.The router places its own node address in the CLASS=MENUITEM MOREINFO="NONE"Source Address field of the MAC header.The router increments the CLASS=MENUITEM MOREINFO="NONE"Transport Control field of the IPX header and forwards the packet to the destination node segment.If the CLASS=MENUITEM MOREINFO="NONE"Transport Control field equals the maximum allowed hop count before the field is incremented, the router discards the packet. For RIP routers, the hop count limit is 16; for NLSP routers, this limit can be set to any number between eight and 127.Note also that broadcast packets are never rebroadcast onto the network segment from which they are received.PAGENUM=23 ID="BP30"PAGENUM=24If the router is not directly connected to the segment on which the final destination node resides, it sends the packet to the next router in the path to the destination node, as follows:NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"The router places the node address of the next router in the CLASS=MENUITEM MOREINFO="NONE"Destination Address field of the MAC header.The router gets this information from its Routing Information Table.The router places its own node address in the CLASS=MENUITEM MOREINFO="NONE"Source Address field of the MAC header.The router increments the CLASS=MENUITEM MOREINFO="NONE"Transport Control field in the IPX header and forwards the packet to the next router.RENDERAS="SECT2"ID="FM87687"RIPIDXID="w3509"BOOK="_idx" COLLECTION="nw41" TIDREF="i3902"
RIP, like IPX, was derived from XNS. RIP uses IPX and the MAC protocols for its transport.IDXID="w3510"BOOK="_idx" COLLECTION="nw41" TIDREF="i3894"
Routers use RIP to exchange routing information with neighboring routers on an IPX internetwork. As a router becomes aware of changes in the internetwork, it broadcasts this information immediately to neighboring routers.A RIP router periodically broadcasts a packet containing all routing information known to the router. These broadcasts keep all routers on the internetwork synchronized and provide a means of aging networks that have become inaccessible since the last broadcast. A network might be inaccessible because a router went down, or because a router "dropped" a packet containing information that the route to the network is unreachable. Aged networks do not appear in the routing information broadcast.NetWare workstations also use RIP to locate the fastest route to a distant network. A workstation initiates a route request by broadcasting a RIP packet and then "listens" for the RIP response that contains the route information.PAGENUM=25 ID="BP31"RENDERAS="SECT3"RIP Packet StructureThe IDXID="w3511"BOOK="_idx" COLLECTION="nw41" TIDREF="i3867"
RIP IDXID="w3512"BOOK="_idx" COLLECTION="nw41" TIDREF="i3190"
packet structure is shown in IDREF="FM15743"Figure 2-3. As with most of the higher-level protocols, the RIP packet is encapsulated within the data area of the IPX packet. RIP packets are defined in the IPX header as Packet Type 1 and Socket Number 0x453.LABEL="2-3" FLOAT="0"ID="FM15743"RIP Packet Structure FILEREF="ipxrippk.tif"Following is a description of theIDXID="w3513"BOOK="_idx" COLLECTION="nw41" TIDREF="i3866"
 RIP packetIDXID="w3514"BOOK="_idx" COLLECTION="nw41" TIDREF="i3173"
 fields:MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Operation---Flag indicating whether the packet is a request or a response. The value 1 represents a RIP request; the value 2 represents a RIP response.CLASS=MENUITEM MOREINFO="NONE"Network Entry---Subject of the RIP request or response. Each network entry is eight bytes long.PAGENUM=25 ID="BP32"PAGENUM=26A RIP packet can contain up to 50 network entries. Therefore, depending on the amount of network information contained in the packet, the size of a RIP packet can vary from a minimum of 40 bytes (IPX header and one RIP network entry) to a maximum of 432 bytes (IPX header and 50 entries). Each RIP network entry comprises the following fields:MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Network Number---Network number that is the subject of the RIP request or response.For RIP requests, this field can be set to 0xFFFFFFFF to indicate a general request.CLASS=MENUITEM MOREINFO="NONE"Number of Hops---Number of routers that must be traversed to reach the network number associated with this entry.For response packets, the Number of Hops must be at least 1.CLASS=MENUITEM MOREINFO="NONE"Number of Ticks---Time delay, in "ticks," to reach the network number associated with this entry. A tick is about 1/18 of a second. (There are 18.21 ticks in a second.) The number in this field is always at least 1 for RIP responses.The original XNS definition of RIP did not include the CLASS=MENUITEM MOREINFO="NONE"Number of Ticks field.If there are multiple routes to a network number, a router uses the path with the least number of ticks when forwarding packets to that network number. If two paths have equal tick values, the router chooses the one with the fewest hops.With NetWare routers, the network interface board driver is responsible for reporting the time delay on its segment.For RIP operating on a LAN, the time delay is always one tick. As information about the network segment is passed throughout the network by way of periodic broadcasts, routers add any additional delay that they impose to the initial time delay for the segment. This time delay does not include any dynamic queuing delay.PAGENUM=26 ID="BP33"PAGENUM=27RENDERAS="SECT3"Routing Information TableIPX routers use RIP to create and dynamically maintain a database of routing information called the IDXID="w3515"BOOK="_idx" COLLECTION="nw41" TIDREF="i3905"Routing Information Table. This table contains information about all the network segments on the IPX internetwork. The router uses this information to forward packets to their destination by the best possible route.IDREF="FM49740"Table 2-3 shows a sample IDXID="w3516"BOOK="_idx" COLLECTION="nw41" TIDREF="i3905"Routing Information Table. LABEL="2-3" PGWIDE=1 TOCENTRY="1"ID="FM49740"Sample Routing Information TableCOLS=6 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="6*"COLNAME=2 COLWIDTH="4*"COLNAME=3 COLWIDTH="4*"COLNAME=4 COLWIDTH="5*"COLNAME=5 COLWIDTH="7*"COLNAME=6 COLWIDTH="4*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Network NumberCOLNAME=2 ROTATE="0" MOREROWS="0"Hops to NetworkCOLNAME=3 ROTATE="0" MOREROWS="0"Ticks to NetworkCOLNAME=4 ROTATE="0" MOREROWS="0"Network Interface BoardCOLNAME=5 ROTATE="0" MOREROWS="0"Immediate Address of Forwarding RouterCOLNAME=6 ROTATE="0" MOREROWS="0"Aging TimerVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"00000001COLNAME=2 ROTATE="0" MOREROWS="0"1COLNAME=3 ROTATE="0" MOREROWS="0"2COLNAME=4 ROTATE="0" MOREROWS="0"ACOLNAME=5 ROTATE="0" MOREROWS="0"-COLNAME=6 ROTATE="0" MOREROWS="0"0COLNAME=1 ROTATE="0" MOREROWS="0"00000002COLNAME=2 ROTATE="0" MOREROWS="0"1COLNAME=3 ROTATE="0" MOREROWS="0"2COLNAME=4 ROTATE="0" MOREROWS="0"BCOLNAME=5 ROTATE="0" MOREROWS="0"-COLNAME=6 ROTATE="0" MOREROWS="0"0COLNAME=1 ROTATE="0" MOREROWS="0"FEED0038COLNAME=2 ROTATE="0" MOREROWS="0"1COLNAME=3 ROTATE="0" MOREROWS="0"20COLNAME=4 ROTATE="0" MOREROWS="0"CCOLNAME=5 ROTATE="0" MOREROWS="0"-COLNAME=6 ROTATE="0" MOREROWS="0"0COLNAME=1 ROTATE="0" MOREROWS="0"FEED0035COLNAME=2 ROTATE="0" MOREROWS="0"2COLNAME=3 ROTATE="0" MOREROWS="0"3COLNAME=4 ROTATE="0" MOREROWS="0"BCOLNAME=5 ROTATE="0" MOREROWS="0"00001B029927COLNAME=6 ROTATE="0" MOREROWS="0"1COLNAME=1 ROTATE="0" MOREROWS="0"000000FFCOLNAME=2 ROTATE="0" MOREROWS="0"2COLNAME=3 ROTATE="0" MOREROWS="0"3COLNAME=4 ROTATE="0" MOREROWS="0"ACOLNAME=5 ROTATE="0" MOREROWS="0"00001B0349B2COLNAME=6 ROTATE="0" MOREROWS="0"2COLNAME=1 ROTATE="0" MOREROWS="0"FEED0036COLNAME=2 ROTATE="0" MOREROWS="0"3COLNAME=3 ROTATE="0" MOREROWS="0"4COLNAME=4 ROTATE="0" MOREROWS="0"ACOLNAME=5 ROTATE="0" MOREROWS="0"00001B0349B2COLNAME=6 ROTATE="0" MOREROWS="0"2This table can contain additional fields; only those pertinent to this discussion are shown.Following is a description of the fields in the Routing Information Table:MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Network Number---Network number of each network segment of which the router is currently aware. To get its forwarding instructions for a packet, the router matches the destination network number in the IPX header with an entry in this field.CLASS=MENUITEM MOREINFO="NONE"Hops to Network---Number of routers (hops) that must be traversed to reach the destination segment.CLASS=MENUITEM MOREINFO="NONE"Ticks to Network---Estimate of the time necessary to reach the destination segment.PAGENUM=27 ID="BP34"PAGENUM=28CLASS=MENUITEM MOREINFO="NONE"Network Interface Board---Board in the router through which the destination segment can be reached. The letters A, B, and C in IDREF="FM49740"Table 2-3 are symbolic representations of three different interface boards.CLASS=MENUITEM MOREINFO="NONE"Immediate Address of Forwarding Router---Node address of the router that can forward packets to each segment.This field remains empty if the segment is directly connected to the router.CLASS=MENUITEM MOREINFO="NONE"Aging Timer---Timer that makes sure the information about the destination segment is current.Each time the router receives information about the network, it resets the CLASS=MENUITEM MOREINFO="NONE"Aging Timer to zero. If the value reaches three minutes, the router assumes that the route to the network is down and broadcasts that information to its connected segments.RENDERAS="SECT2"ID="FM26446"SAPIDXID="w3517"BOOK="_idx" COLLECTION="nw41" TIDREF="i4072"
SAP is conceptually similar to RIP. Although routers use RIP to exchange routing information, SAP provides a means for routers and servers to advertise and exchange service information. Unlike RIP, SAP was not part of the XNS protocol specification.NetWare file servers, print servers, gateway servers, and PCs running NetWare MultiProtocol RouterTM software use SAP to advertise their services and network addresses. Routers gather this information and share it with other routers. Workstations on the network determine which services are available on the network and obtain the IPX address of the services. Workstations use this information to initiate a session with a service.SAP makes the process of adding and removing services on an internetwork dynamic. As servers start up, they use SAP to advertise their services; as they are brought down, they use SAP to indicate that their services are no longer available.PAGENUM=28 ID="BP35"PAGENUM=29As a router becomes aware of any change in the internetwork server layout, this information is immediately broadcast to all neighboring routers. SAP broadcast packets containing all server information known to the router are sent periodically---every 60 seconds, by default. These broadcasts keep all routers on the internetwork synchronized and provide a means of aging servers that become inaccessible because a router---or server---has gone down since the last broadcast. A server might be inaccessible because a router went down, or because a router "dropped" a packet containing information that the route to the server is unreachable. Aged servers do not appear in the SAP broadcast.Like RIP, SAP uses IPX and the MAC protocols for its transport.RENDERAS="SECT3"SAP Packet StructureIDXID="w3518"BOOK="_idx" COLLECTION="nw41" TIDREF="i3948"IDXID="w3519"BOOK="_idx" COLLECTION="nw41" TIDREF="i3190"
The SAP packet structure is shown in IDREF="FM80618"Figure 2-4. As with most of the higher-level protocols, the SAP packet is encapsulated within the data area of IPX. SAP packets are defined in the IPX header as Packet Type 4 and Socket Number 0x452.LABEL="2-4" FLOAT="0"ID="FM80618"SAP Packet Structure FILEREF="sappkt.tif"PAGENUM=29 ID="BP36"PAGENUM=30Following is a description of the SAP IDXID="w3520"BOOK="_idx" COLLECTION="nw41" TIDREF="i3947"IDXID="w3521"BOOK="_idx" COLLECTION="nw41" TIDREF="i3173"
packet fields:MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Operation---Type of operation the SAP packet performs. This field can be set to one of the following values:MARK=BULLET1 (Request)2 (Response)3 (Get Nearest Server Request)4 (Get Nearest Server Response)Depending on the type of operation, the CLASS=MENUITEM MOREINFO="NONE"Operation field is followed by either a single field or one or more sets of fields. For all SAP requests (operations 1 and 3), the packet includes only the first CLASS=MENUITEM MOREINFO="NONE"Service Type field. This means that all SAP requests are 34 bytes long, not including media header (IPX header plus SAP CLASS=MENUITEM MOREINFO="NONE"Operation and CLASS=MENUITEM MOREINFO="NONE"Service Type fields = 30 + 2 + 2 = 34 bytes). All other fields apply only to SAP responses (operations 2 and 4).CLASS=MENUITEM MOREINFO="NONE"Server Entry---Information about the server advertising the service.A SAP response can include from one to seven server entries. Therefore, SAP response packets can vary from 96 bytes (IPX header and one server entry) to 480 bytes (IPX header and 7 entries). Each entry includes information about a particular server and comprises the following fields:MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Service Type---Type of service provided by the server.Novell assigns each type of server a unique service type. For example, a Novell file server advertises itself as Type 4. This value becomes the object type for this server as it is found in IDXID="w3522"BOOK="_idx" COLLECTION="nw41" TIDREF="i3949"
the NetWare bindery. IDREF="FM38630"Table 2-4 lists some well-known service types.LABEL="2-4" PGWIDE=0 TOCENTRY="1"ID="FM38630"Service TypesCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="12*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Service TypeCOLNAME=2 ROTATE="0" MOREROWS="0"Field Value (Hex)VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"UnknownCOLNAME=2 ROTATE="0" MOREROWS="0"0x0000COLNAME=1 ROTATE="0" MOREROWS="0"Print QueueCOLNAME=2 ROTATE="0" MOREROWS="0"0x0003COLNAME=1 ROTATE="0" MOREROWS="0"File ServerCOLNAME=2 ROTATE="0" MOREROWS="0"0x0004COLNAME=1 ROTATE="0" MOREROWS="0"Job ServerCOLNAME=2 ROTATE="0" MOREROWS="0"0x0005COLNAME=1 ROTATE="0" MOREROWS="0"Print ServerCOLNAME=2 ROTATE="0" MOREROWS="0"0x0007COLNAME=1 ROTATE="0" MOREROWS="0"Archive ServerCOLNAME=2 ROTATE="0" MOREROWS="0"0x0009COLNAME=1 ROTATE="0" MOREROWS="0"Remote Bridge ServerCOLNAME=2 ROTATE="0" MOREROWS="0"0x0024COLNAME=1 ROTATE="0" MOREROWS="0"Advertising Print ServerCOLNAME=2 ROTATE="0" MOREROWS="0"0x0047COLNAME=1 ROTATE="0" MOREROWS="0"Reserved Up ToCOLNAME=2 ROTATE="0" MOREROWS="0"0x8000COLNAME=1 ROTATE="0" MOREROWS="0"WildcardCOLNAME=2 ROTATE="0" MOREROWS="0"0xFFFF (-1)PAGENUM=31 ID="BP37"CLASS=MENUITEM MOREINFO="NONE"Server Name---48-byte character string name assigned to a server.The server name, along with the service type, uniquely identifies a server on an internetwork. Although SAP response packets always include the full 48 bytes for this field, server names are typically fewer than 48 characters.CLASS=MENUITEM MOREINFO="NONE"Network Address---Address of the network on which the server resides.CLASS=MENUITEM MOREINFO="NONE"Node Address---Address of the node on which the server resides.CLASS=MENUITEM MOREINFO="NONE"Socket Address---Socket number on which the server receives service requests.CLASS=MENUITEM MOREINFO="NONE"Hops to Server---Number of intermediate networks that must be traversed to reach the server associated with this entry.Each time the packet passes through an intermediate network, the field is incremented by one.PAGENUM=32 ID="BP38"RENDERAS="SECT3"Bindery-Based ServicesIDXID="w3523"BOOK="_idx" COLLECTION="nw41" TIDREF="i461"
With NetWare 3, commands such as LOGIN, MAP, and ATTACH take a server name and look it up in the bindery, Novell's equivalent of a telephone book. The IDXID="w3524"BOOK="_idx" COLLECTION="nw41" TIDREF="i4081"
service is then mapped to an IPX address.A service name identifies a recipient on a node on the network. Rather than sending the entire service name in each IPX message, the service is mapped to a socket number. The socket number allows for up to 65,000 recipients on each IPX node. Each service on a NetWare server has its own socket number and a service name and type that are unique on the IPX network. Some of these service types and their corresponding socket numbers are listed in IDREF="FM38630"Table 2-4.When you log in to a NetWare server, the LOGIN command reads the list of services on the attached server. From there, it obtains the IPX address and the socket number of the file server with the name you supply. This address and socket number are put into messages that reach the designated recipient. This means that each server must have a copy of all services on your IPX network.RENDERAS="SECT3"NetWare Directory ServicesNetWare 4 provides IDXID="w3525"BOOK="_idx" COLLECTION="nw41" TIDREF="i4081"
NetWare IDXID="w3526"BOOK="_idx" COLLECTION="nw41" TIDREF="i2720"
Directory ServicesTM (NDSTM) software, a method of storing and retrieving service information in a distributed database. The directory database organizes this information in a hierarchical tree structure, independent of its physical location. Rather than keeping all service information in the same location, each directory server contains some portion of it. However, each directory server has access to any service information in the database. The directory database replaces the bindery in NetWare 4 servers.With NDS, the use of SAP is considerably reduced. NetWare workstations locate services by consulting an NDS server. The server disseminates the NDS-resident service information by direct, unicast-based protocols, not by broadcast-based SAP. However, even in a network of all NetWare 4 nodes, some uses of SAP remain. For example, SAP locates the nearest NDS server at initialization time.PAGENUM=33 ID="BP39"RENDERAS="SECT2"ID="FM33747"NCPIDXID="w3527"BOOK="_idx" COLLECTION="nw41" TIDREF="i2713"
NCP IDXID="w3528"BOOK="_idx" COLLECTION="nw41" TIDREF="i2619"
enables NetWare workstations and file servers to communicate by defining two aspects of their interaction: connection control and service request encoding.NCP maintains its own connection control and packet-level error checking instead of relying on other protocols for those functions. Connections are established and terminated by IDXID="w3529"BOOK="_idx" COLLECTION="nw41" TIDREF="i2619"NCP Requests, which are issued by NetWare workstations, and IDXID="w3530"BOOK="_idx" COLLECTION="nw41" TIDREF="i2619"NCP Replies, which are issued by NetWare servers.A workstation sends an CLASS=MENUITEM MOREINFO="NONE"NCP Request to a server to retrieve the following types of information:MARK=BULLETFile access and transfers (with the NCOPY command)Virtual drive mappings (with the MAP command)Directory searches (with the FILER utility)Print queue status (with the PCONSOLE utility)Servers respond to these requests with CLASS=MENUITEM MOREINFO="NONE"NCP Replies. When the server has processed and complied with the request, the workstation terminates the connection by sending a CLASS=MENUITEM MOREINFO="NONE"Destroy Service Connection request to the server.RENDERAS="SECT2"ID="FM11600"SPXIDXID="w3531"BOOK="_idx" COLLECTION="nw41" TIDREF="i4031"
SPXIDXID="w3532"BOOK="_idx" COLLECTION="nw41" TIDREF="i4240"
 is a connection-oriented protocol that operates at the OSI Transport layer. Connection-oriented means that when a node uses SPX to communicate with another node, a dedicated connection is established between the two nodes. This connection must be established before the nodes can exchange packets.SPX guarantees delivery of packets to their destination and delivers them in their proper sequence. IPX gives only its "best effort" to deliver packets and delivers them in any order.PAGENUM=33 ID="BP40"PAGENUM=34Although SPX guarantees delivery of every packet it sends, it is slower than IPX. The SPX header includes the IPX header---30 bytes---but adds an additional 12 bytes of sequencing, flow control, connection, and acknowledgment information.RENDERAS="SECT2"ID="FM82047"NetBIOSIDXID="w3533"BOOK="_idx" COLLECTION="nw41" TIDREF="i2656"
NetBIOS was written for IBM* by Sytek in 1984 and has since become an industry standard. NetBIOS provides Session-layer services, such as named addressing and packet assembly/disassembly. Like SPX, NetBIOS also provides Transport-layer services, such as guaranteed packet delivery and packet sequencing.For NetBIOS to operate in the NetWare environment, IPX routers must be able to propagate NetBIOS packets across an internetwork. NetWare accomplishes this by defining a special IPX packet type of 20 (0x14) to designate a propagated packet. Packet type 20 and socket number 0x455 together identify the NetBIOS packet. Additionally, the CLASS=MENUITEM MOREINFO="NONE"Destination Node field in the IPX header is set to 0xFFFFFFFFFFFF. This instructs each router receiving the packet to broadcast it to all nodes on the destination network.NetBIOS packets require unique handling on the part of a router. For a step-by-step description of this process, refer to IDREF="FM34389""When a Router Receives an IPX Packet."Because each router that receives a NetBIOS packet simply broadcasts (forwards) it to directly connected segments, the IPX header CLASS=MENUITEM MOREINFO="NONE"Destination Network field is irrelevant.NetWare IPX Router allows you to control the propagation of type 20 packets on your network. For more information, see IDREF="FM55885""Advanced Packet Type 20 Flooding."LABEL="3"PAGENUM=35 ID="BP41"ID="FM19231"NetWare Link Services Protocol ConceptsThis chapter describes IDXID="w3534"BOOK="_idx" COLLECTION="nw41" TIDREF="i2752"
NetWare® Link Services ProtocolTM (NLSPTM) software, Novell's link state routing protocol for IPXTM internetworks.This chapter contains the following sections:MARK=BULLETIDREF="FM84792""Overview: How NLSP Operates"This section gives a step-by-step summary of how NLSP operates on an IPX network. Each step refers to a section later in this chapter that provides a more thorough explanation of a particular NLSP function.IDREF="FM66399""How Neighboring Routers Form Adjacencies"This section describes the process by which NLSP routers discover each other on the network.IDREF="FM20976""How the Designated Router is Elected"This section describes the process by which NLSP routers elect a router to represent the LAN for exchanges of routing information.IDREF="FM26944""How NLSP Routers Develop Their View of the Network"This section describes the process by which each NLSP router develops the same view of the network.IDREF="FM55207""How NLSP Routers Forward Packets"This section describes the forwarding database and how NLSP routers use it to route packets to their destination.PAGENUM=35 ID="BP42"PAGENUM=36IDREF="FM43362""NLSP System ID"This section describes the purpose and structure of the NLSP System ID.IDREF="FM16677""Routing Areas"This section introduces NLSP routing areas and their purpose in hierarchical routing. It also describes the structure of area addresses and introduces the Novell® Network RegistrySM service.IDXID="w3535"BOOK="_idx" COLLECTION="nw41" TIDREF="i2927"
NLSP is derived from IDXID="w3536"BOOK="_idx" COLLECTION="nw41" TIDREF="i1991"
IS-IS (Intermediate System-to-Intermediate System), the link state routing protocol developed by the International Standards Organization (ISO). Like IDXID="w3537"BOOK="_idx" COLLECTION="nw41" TIDREF="i2927"
IS-IS, NLSP exchanges routing information between routers and makes routing decisions based on that information. For workstation-to-router communication, NLSP routers use the Routing Information Protocol (RIP). To read about RIP, see IDREF="FM87687""RIP."NLSP routers exchange information such as connectivity states, path costs, external network numbers, Maximum Transmission Unit (MTU) size, throughput, and media types. By exchanging this information with its peer routers, each NLSP router builds and maintains a logical map of the entire network.Unlike RIP and the Service Advertising Protocol (SAP), which periodically broadcast routing and service information, NLSP transmits routing information only when a change occurs in a route or service somewhere in the network, or every two hours---whichever occurs first.All NLSP packets are carried in the data portion of IPX packets, immediately following the IPX header. The IPX packets, in turn, are carried in the data portion of data-link frames, following the MAC header.This chapter does not provide diagrams and descriptions of each NLSP packet. For this information, see the NetWare Link Services Protocol Specification (Novell part number 100-001708-002).PAGENUM=36 ID="BP43"PAGENUM=37RENDERAS="SECT1"ID="FM84792"Overview: How NLSP OperatesIDXID="w3538"BOOK="_idx" COLLECTION="nw41" TIDREF="i2927"
The following steps summarize how NLSP discovers information about routers and links on an IPX network and uses the information to build a map by which it can make routing decisions:NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"Each NLSP router "gets acquainted" with the routers to which it is directly connected.This process is explained in IDREF="FM66399""How Neighboring Routers Form Adjacencies."NLSP routers on the same LAN elect a single router from among themselves to represent the group.This process is explained in IDREF="FM20976""How the Designated Router is Elected."Each router creates a packet with information about its directly connected routers and the links to those routers, such as node and network addresses, MTU size, throughput, and path cost.This process is explained in IDREF="FM26944""How NLSP Routers Develop Their View of the Network."Each router floods the network with this information in a Link State Packet (LSP).This process is explained in IDREF="FM24293""Building the Link State Database" and IDREF="FM93938""Synchronizing the Link State Database."Given this information, each router determines the "best" (shortest or least-expensive) path to every other router on the network. This is called the decision process.This process is explained in IDREF="FM55207""How NLSP Routers Forward Packets."IDREF="FM30132"Figure 3-1 summarizes the packet exchanges that occur among NLSP routers, the databases each router uses, and the processing necessary to perform routing operations. The numbers in the figure correspond roughly to the preceding steps.PAGENUM=38 ID="BP44"LABEL="3-1" FLOAT="0"ID="FM30132"Overview of NLSP OperationsFILEREF="db.tif"The sections throughout the rest of this chapter explain the elements of NLSP and how it works on an IPX internetwork.PAGENUM=38 ID="BP45"PAGENUM=39RENDERAS="SECT1"ID="FM66399"How Neighboring Routers Form AdjacenciesIDXID="w3539"BOOK="_idx" COLLECTION="nw41" TIDREF="i114"
Before an IDXID="w3540"BOOK="_idx" COLLECTION="nw41" TIDREF="i2927"
NLSP router floods the network with its link state information, it determines the reachability of its neighboring routers, or neighbors. Two routers are considered neighbors when they can communicate directly---that is, without the aid of an intermediate router.RENDERAS="SECT2"Adjacencies and Hello PacketsIDXID="w3541"BOOK="_idx" COLLECTION="nw41" TIDREF="i114"
An IDXID="w3542"BOOK="_idx" COLLECTION="nw41" TIDREF="i114"adjacency is the record that a router keeps about the state of its connection with a neighbor, and about the attributes of that neighbor. The adjacencies database keeps track of a router's neighbors and the state of the links to those neighbors.When a link comes up, an NLSP router begins a periodic transmission of Hello packets and waits for replies from its neighbors. When a neighbor replies with a Hello packet, the router adds a record of the neighbor to its adjacencies database. Transmission of Hello packets is governed by the CLASS=MENUITEM MOREINFO="NONE"Hello Interval, an NLSP convergence parameter that you can set from the Internetworking Configuration utility (INETCFG).NLSP, by default, broadcasts its Hello packets and LSPs to NLSP routers across the network. You can, however, configure NLSP to multicast these packets. NLSP uses broadcast transmission as a default because some LAN drivers do not properly support packet multicast.A Hello packet can be no larger than the MTU of the network medium and no smaller than the minimum size that any system on the LAN can receive. This limits the number of neighbors a router can have on a single interface. For example, the Ethernet MTU of 1500 bytes corresponds to about 235 neighbors.Each adjacency can assume one of three states:MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"IDXID="w3543"BOOK="_idx" COLLECTION="nw41" TIDREF="i116"
Down---The adjacency state is down when the neighbor is in a different routing area.CLASS=MENUITEM MOREINFO="NONE"Initializing---The adjacency state is initializing when a one-way connection between a router and one of its neighbors is established.CLASS=MENUITEM MOREINFO="NONE"Up---The adjacency state is up when a two-way connection is established between the routers---that is, when they have exchanged Hello packets.PAGENUM=40 ID="BP46"IDREF="FM25979"Figure 3-2 shows how two neighboring NLSP routers---A and B---form an adjacency over a LAN. Router B is already running; the packet exchange begins when Router A starts up.LABEL="3-2" FLOAT="0"ID="FM25979"Two Routers Forming an Adjacency on a LANFILEREF="adjstate.tif"IDXID="w3544"BOOK="_idx" COLLECTION="nw41" TIDREF="i1679"
If a router goes offline and stops sending Hello packets, each of its neighbors keeps the adjacency to that router in the Up state for the number of seconds specified by the holding time. The holding time is the product of the router's CLASS=MENUITEM MOREINFO="NONE"Hello Interval and CLASS=MENUITEM MOREINFO="NONE"IDXID="w3545"BOOK="_idx" COLLECTION="nw41" TIDREF="i1678"
Holding Timer Multiplier and is carried in the Hello packet that a router transmits to its neighbors. The holding time tells the neighbors how long to keep the adjacency to the router in the Up state. For example, a neighbor receiving a Hello packet from a router whose CLASS=MENUITEM MOREINFO="NONE"IDXID="w3546"BOOK="_idx" COLLECTION="nw41" TIDREF="i1652"
Hello Interval is 20 seconds and whose CLASS=MENUITEM MOREINFO="NONE"Holding Timer Multiplier is four, keeps the adjacency in the Up state for 80 seconds before changing the state to Down and finally purging the adjacency from its adjacencies database.PAGENUM=40 ID="BP47"PAGENUM=41RENDERAS="SECT2"CircuitsIDXID="w3547"BOOK="_idx" COLLECTION="nw41" TIDREF="i634"
NLSP IDXID="w3548"BOOK="_idx" COLLECTION="nw41" TIDREF="i2927"
uses the concept of a circuit for LANs and WANs. In general, a circuit is an internal logical representation of network connectivity.For LANs, a circuit is a single interface to a network segment, through which the router can reach other systems and WANs. Two points of attachment to the same network segment are treated as two circuits.In a NetWare environment, enabling a LAN circuit is equivalent to binding a network protocol to a LAN interface. In fact, the name of the LAN circuit is the name you assign to the LAN board in INETCFG.For a dedicated or dial-up point-to-point WAN medium, each interface is treated as a circuit. For multipoint WAN media, such as X.25 and Frame Relay, a single interface can provide access to many other systems using a connection-oriented data-link protocol. NLSP treats each X.25 or Frame Relay virtual circuit---switched or permanent---as a separate circuit because virtual circuits can share the same network interface.In a NetWare environment, enabling a WAN circuit is equivalent to bringing up a WAN Call Destination. In fact, the name of the circuit is the name you assign to the WAN Call Destination in INETCFG.IDREF="FM94390"Figure 3-3 shows an example of circuits and neighbors on a simple internetwork. Router B has one WAN circuit and one LAN circuit. On the WAN circuit, Router B has one neighbor: Router A. On the LAN circuit, Router B has two neighbors: Routers C and D.PAGENUM=42 ID="BP48"LABEL="3-3" FLOAT="0"ID="FM94390"Circuits in an Internetwork FILEREF="circuit.tif"RENDERAS="SECT2"Forming Adjacencies over LAN CircuitsIDXID="w3549"BOOK="_idx" COLLECTION="nw41" TIDREF="i114"
The following events summarize what occurs between neighbors forming an adjacency over a IDXID="w3550"BOOK="_idx" COLLECTION="nw41" TIDREF="i2028"
LAN circuit:MARK=BULLETThe neighbors exchange Hello packets and build their adjacencies databases.The routers elect a single router from among themselves to represent the group. This process is explained in IDREF="FM20976""How the Designated Router is Elected."PAGENUM=42 ID="BP49"PAGENUM=43RENDERAS="SECT2"Forming Adjacencies over WAN CircuitsThe following events summarize what occurs between two neighbors forming an IDXID="w3551"BOOK="_idx" COLLECTION="nw41" TIDREF="i114"
adjacency over a IDXID="w3552"BOOK="_idx" COLLECTION="nw41" TIDREF="i4809"
WAN circuit:MARK=BULLETA data-link connection between the two neighbors is established. The details of how the connection is established depend on the WAN medium (X.25, for example).The two neighbors use the Novell® IPXWANTM protocol to exchange identities and determine certain operational characteristics of the connection.The two neighbors exchange WAN Hello packets and build their adjacencies databases.RENDERAS="SECT1"ID="FM20976"How the Designated Router is ElectedIDXID="w3553"BOOK="_idx" COLLECTION="nw41" TIDREF="i1301"
Each Hello packet contains a field with the priority of the router. CLASS=MENUITEM MOREINFO="NONE"Priority is an NLSP parameter that you can set, using INETCFG, for each LAN interface on a router.IDXID="w3554"BOOK="_idx" COLLECTION="nw41" TIDREF="i1001"
After each router forms adjacencies with its neighbors, NLSP examines the priority of each router. The router with the highest priority is elected the Designated Router. The Designated Router is responsible for exchanges of link state information on behalf of all other NLSP routers on a LAN. If two or more routers have the same priority, NLSP compares the routers' MAC addresses; the router with the numerically higher address becomes the IDXID="w3555"BOOK="_idx" COLLECTION="nw41" TIDREF="i1001"
Designated Router.The Designated Router has its own CLASS=MENUITEM MOREINFO="NONE"Broadcast Hello Interval which, by default, broadcasts a Hello packet every 10 seconds---twice the rate of the standard Hello Interval. Therefore, if the Designated Router goes down, its neighbors notice sooner and can elect a new Designated Router quickly.PAGENUM=44 ID="BP50"While a new Designated Router is being elected, a portion of the network might lose connectivity for a moment. When a system becomes the Designated Router, it immediately increases its priority by 20 to prevent frequent, unnecessary reelections. You can further minimize such reelections by choosing a "stable" router---one that is up most of the time---and setting its priority high enough so that it retains its status as Designated Router. Novell recommends a priority value of 100 for the Designated Router.The Designated Router must also have enough memory to process and maintain all the link state information for its LAN. If the Designated Router runs out of memory, it can no longer process this information and its link state database---the collection of LSPs that represent the entire network---becomes overloaded.A router attached to several LANs might be the Designated Router for some LANs but not for others; the Designated Router election is independent on different LANs.In "mixed" networks---those on which both NLSP and RIP/SAP operate---only the Designated Router propagates RIP and SAP information in its LSPs. To avoid inefficient routing, all NLSP routers broadcast RIP and SAP onto a network on which RIP is active but use the IDXID="w3556"BOOK="_idx" COLLECTION="nw41" TIDREF="i4229"split horizon technique to reduce these broadcasts.RENDERAS="SECT2"Why the Designated Router is NecessaryOn LANs, NLSP takes special measures to keep the size of the link state database manageable. Consider how LAN adjacencies are modeled in the internetwork shown in IDREF="FM26856"Figure 3-4.PAGENUM=45 ID="BP51"LABEL="3-4" FLOAT="0"ID="FM26856"Modeling LAN Adjacencies FILEREF="adjmod.tif"PAGENUM=46 ID="BP52"In (a), each router connects the LAN and a particular WAN. In terms of physical connectivity, each router can reach all others in one hop. This means there is full mesh connectivity, as shown in (b). (The WAN links are not shown.) To avoid propagating large amounts of adjacency information into the NLSP network, NLSP models the LAN adjacencies as shown in (c).RENDERAS="SECT2"PseudonodeA IDXID="w3557"BOOK="_idx" COLLECTION="nw41" TIDREF="i3626"
fictitious pseudonode represents an entire LAN in the link state database. Each router represents itself as directly connected to the pseudonode, but because the pseudonode is a fictitious router, the Designated Router represents it for LSP exchanges.End nodes are also directly connected to the pseudonode, although they are not represented in the LSPs. Representing end nodes is not necessary---they are located by having the same network number as the pseudonode.The Designated Router sends LSPs on behalf of the pseudonode. If the Designated Router resigns because a new router with a higher priority comes online, the Designated Router floods the network with a null LSP indicating that the old pseudonode is no longer valid. At this point, the new router becomes the Designated Router and represents the pseudonode.RENDERAS="SECT1"ID="FM26944"How NLSP Routers Develop Their View of the NetworkThe LSP comprises two parts: a 27-byte header that contains length, identification, and administrative fields; and a variable-length portion that contains the link state information.IDXID="w3558"BOOK="_idx" COLLECTION="nw41" TIDREF="i2112"
When an NLSP router IDXID="w3559"BOOK="_idx" COLLECTION="nw41" TIDREF="i879"
createsIDXID="w3560"BOOK="_idx" COLLECTION="nw41" TIDREF="i1368"
 its own LSP, it puts the following information into the variable-length portion:MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Area addresses---Set of area address/mask pairs configured on the NLSP router. Area addresses are explained in IDREF="FM42135""Area Addresses and Masks."CLASS=MENUITEM MOREINFO="NONE"Management information---Information about the router creating the LSP. It includes the router's network and node numbers and the router's name.PAGENUM=47 ID="BP53"CLASS=MENUITEM MOREINFO="NONE"Link information---Adjacency information collected from each neighbor: path cost, neighbor ID, MTU, delay, throughput, and media type.CLASS=MENUITEM MOREINFO="NONE"Service information---Information about services advertised by SAP, which includes the number of hops to the server offering the service, the network, node, and socket numbers, the type of service, and the service name.IDXID="w3561"BOOK="_idx" COLLECTION="nw41" TIDREF="i1414"
The pseudonode LSP contains an additional set of information called external routes. These are the RIP routes that are available on---or through---the LAN represented by the Designated Router. External route information includes the number of hops, the network number, and the number of ticks from the NLSP router to the RIP network.Each LSP also contains a unique eight-byte ID number. NLSP routers use this number to keep track of each LSP and the router it came from. Each LSP also contains a four-byte IDXID="w3562"BOOK="_idx" COLLECTION="nw41" TIDREF="i4029"
sequence number that distinguishes between older and newer LSPs. An LSP with a higher sequence number is newer.The minimum---and default---LSP size is 512 bytes. You can use INETCFG to set the LSP size to any value up to 4096 bytes, depending on the smallest MTU of any network segment in your NLSP internetwork. The larger the LSP size, the fewer LSPs are necessary to propagate a router's link state information. This, however, is not a clear advantage to most networks; for this reason, Novell recommends that you use the default LSP size for all NLSP routers.RENDERAS="SECT2"ID="FM24293"Building the Link State DatabaseIDXID="w3563"BOOK="_idx" COLLECTION="nw41" TIDREF="i2110"
Each NLSP router compiles the LSPs it receives from all other NLSP routers into the link state database. The IDXID="w3564"BOOK="_idx" COLLECTION="nw41" TIDREF="i553"
link state database represents the connectivity of an entire network.All NLSP routers maintain a copy of the link state database and synchronize their views of the database. To a great extent, the work of NLSP is keeping all copies of the link state database consistent among the routers. When a topology change occurs, there is a short transitional period during which the copies differ before NLSP makes them converge again.PAGENUM=48 ID="BP54"The link state database represents only routers, network numbers, and services. It does not represent NetWare workstations or personal computers.When all copies of the link state database are identical and represent the actual connectivity of the network, forwarding decisions made by successive NLSP routers in a packet's path are consistent with each other. The packet progresses from its source to its destination successfully and efficiently.For each point-to-point WAN link, the link state database records information about the end point routers and the state of the link. For each LAN, the link state database records information about the routers connected to the LAN.RENDERAS="SECT2"ID="FM93938"Synchronizing the Link State DatabaseIDXID="w3565"BOOK="_idx" COLLECTION="nw41" TIDREF="i2110"
When a link comes up or goes down, it takes time for that event to become known throughout the network. In the meantime, there is a temporary inconsistency among the link state databases. Such a disruption to the network must be minimized by making the link state databases IDXID="w3566"BOOK="_idx" COLLECTION="nw41" TIDREF="i4359"
converge to a consistent view as fast as possible.IDXID="w3567"BOOK="_idx" COLLECTION="nw41" TIDREF="i1524"Flooding is the means used to synchronize the link state databases. Each router sends information, in the form of an LSP, that is derived from its adjacencies database to its neighbors. Each LSP is numbered so that a router can detect when it receives the same LSP more than once. When a new LSP arrives, two things happen:MARK=BULLETThe router retransmits the LSP on all links except those from which the LSP was received.Each router receiving the LSP merges it into its own link state database.Therefore, the link state database is the collection of LSPs derived from the router's own adjacencies database and LSPs received from other routers through flooding.If an adjacency is lost, each router detecting the event sends an LSP indicating that the link is down. Routers receiving this LSP tag the link as down.PAGENUM=49 ID="BP55"RENDERAS="SECT2"ID="FM37436"Disseminating Link State Updates Among NLSP RoutersIDXID="w3568"BOOK="_idx" COLLECTION="nw41" TIDREF="i2117"
Each NLSP router sends LSPs to its IDXID="w3569"BOOK="_idx" COLLECTION="nw41" TIDREF="i2936"
neighbors. Some LSPs describe the contents of the sending router's adjacencies database; some are forwarded from other neighbors.LAN and WAN links often do not guarantee packet delivery. NLSP uses two methods to ensure that all copies of the link state database are synchronized throughout the network: one for broadcast (LAN) circuits, and the other for point-to-point (WAN) circuits.RENDERAS="SECT3"Broadcast (LAN) CircuitsIDXID="w3570"BOOK="_idx" COLLECTION="nw41" TIDREF="i634"
On a LAN circuit, IDXID="w3571"BOOK="_idx" COLLECTION="nw41" TIDREF="i2028"
each NLSP router broadcasts its LSP only once. IDXID="w3572"BOOK="_idx" COLLECTION="nw41" TIDREF="i519"
None of the routers receiving the LSP sends an acknowledgment to confirm that it received the LSP.To ensure that all NLSP routers receive the complete set of LSPs, the Designated Router broadcasts a IDXID="w3573"BOOK="_idx" COLLECTION="nw41" TIDREF="i720"Complete Sequence Number Packet (CSNP) periodically. The CSNP does not contain the entire link state database; it contains just enough information about each LSP in the database so that the other routers can determine whether they have the same set of LSPs as the Designated Router.The CSNP identifies the Designated Router and contains the ID, sequence number, and remaining lifetime of each LSP in its link state database. A router receiving the CSNP compares this information to that which is in its own link state database. If the information is identical, the router discards the CSNP.How often the Designated Router broadcasts CSNPs is controlled by the CLASS=MENUITEM MOREINFO="NONE"Complete SNP Interval, a convergence parameter that you can set from INETCFG.If the router receiving the CSNP determines that the Designated Router has out-of-date LSPs, it sends the newer LSPs. If the router receiving the CSNP has out-of-date LSPs, it multicasts a IDXID="w3574"BOOK="_idx" COLLECTION="nw41" TIDREF="i3223"Partial Sequence Number Packet (PSNP) identifying---by sequence number---the LSPs it needs. The Designated Router then sends the missing or new LSPs to the router.PAGENUM=50 ID="BP56"RENDERAS="SECT3"Nonbroadcast (WAN) CircuitsIDXID="w3575"BOOK="_idx" COLLECTION="nw41" TIDREF="i4810"
An NLSP router on one end of a IDXID="w3576"BOOK="_idx" COLLECTION="nw41" TIDREF="i634"
point-to-point WAN connection sends each LSP repeatedly until it receives a PSNP as an acknowledgment.IDXID="w3577"BOOK="_idx" COLLECTION="nw41" TIDREF="i2959"
For example, suppose Router A sends an LSP over a WAN link to Router B. This LSP is typically newer than, or the same as, the one that Router B already has. In either case, Router B acknowledges with a PSNP.If the LSP that Router B receives is older than the one already in its link state database, Router B sends the newer LSP to Router A.RENDERAS="SECT1"ID="FM55207"How NLSP Routers Forward PacketsIDXID="w3578"BOOK="_idx" COLLECTION="nw41" TIDREF="i553"
A synchronized link state IDXID="w3579"BOOK="_idx" COLLECTION="nw41" TIDREF="i1560"
database gives all NLSP routers a consistent view of the network. However, the routers cannot decide where to forward outgoing packets from link state information alone. To determine the next hop for a packet, routers run the IDXID="w3580"BOOK="_idx" COLLECTION="nw41" TIDREF="i954"decision process, a IDXID="w3581"BOOK="_idx" COLLECTION="nw41" TIDREF="i2927"
computation that operates on the link state information and presents it in a new form, called the forwarding database.RENDERAS="SECT2"Forwarding DatabaseThe forwarding database consists of a set of pairs comprising the next hop and its external network number. Although all routers have the same link state database, each router has a unique version of the forwarding database, expressed from its own vantage point. The forwarding database is like a table that maps a destination network number to the next hop.In a network with both NLSP and RIP routers, the decision process always chooses a direct NLSP route over any RIP route to the same destination.The IPX internetwork in IDREF="FM70819"Figure 3-5 serves as an example of how an NLSP router builds its forwarding database.PAGENUM=51 ID="BP57"LABEL="3-5" FLOAT="0"ID="FM70819"Building a Forwarding Database FILEREF="fwddb.tif"IDREF="FM70723"Table 3-1 shows a IDXID="w3582"BOOK="_idx" COLLECTION="nw41" TIDREF="i1560"
forwarding database from the vantage point of Router V. The first column lists all the destinations in the routing area. For each destination, the "next hop" indicates which outgoing link---and destination on that link---to use for packets destined for that network. When the router needs to transmit a packet, its forwarding database determines where to forward it. LABEL="3-1" PGWIDE=0 TOCENTRY="1"IDXID="w3583"BOOK="_idx" COLLECTION="nw41" TIDREF="i1561"ID="FM70723"Sample Forwarding Database for Router VCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="14*"COLNAME=2 COLWIDTH="12*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"DestinationCOLNAME=2 ROTATE="0" MOREROWS="0"Next Hop from Router VVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"LAN A (0xCCC47689)COLNAME=2 ROTATE="0" MOREROWS="0"Router SCOLNAME=1 ROTATE="0" MOREROWS="0"Server (0xE3539677)COLNAME=2 ROTATE="0" MOREROWS="0"Router SCOLNAME=1 ROTATE="0" MOREROWS="0"LAN C (0xCCC47666)COLNAME=2 ROTATE="0" MOREROWS="0"LAN CCOLNAME=1 ROTATE="0" MOREROWS="0"LAN B (0xCCC47600)COLNAME=2 ROTATE="0" MOREROWS="0"Router UCOLNAME=1 ROTATE="0" MOREROWS="0"Router U (0x0082392C)COLNAME=2 ROTATE="0" MOREROWS="0"Router UCOLNAME=1 ROTATE="0" MOREROWS="0"Router T (0x00084765)COLNAME=2 ROTATE="0" MOREROWS="0"Router UCOLNAME=1 ROTATE="0" MOREROWS="0"Router S (0x845FAC11)COLNAME=2 ROTATE="0" MOREROWS="0"Router SCOLNAME=1 ROTATE="0" MOREROWS="0"Router R (0x00086594)COLNAME=2 ROTATE="0" MOREROWS="0"Router SCOLNAME=1 ROTATE="0" MOREROWS="0"Router V (0xC3141592)COLNAME=2 ROTATE="0" MOREROWS="0"Router VPAGENUM=52 ID="BP58"For example, CCC47666 is the network number for LAN C; nodes on C are reached through that address. The network number for router V, the "owner" of the forwarding database, is C3141592. Because this database belongs to Router V, packets addressed to network C3141592 are not forwarded by V.When a router detects a change in the link state database, it runs the decision process to rebuild its forwarding database. However, because several topology changes can sometimes occur within a brief period of time, the CLASS=MENUITEM MOREINFO="NONE"IDXID="w3584"BOOK="_idx" COLLECTION="nw41" TIDREF="i4227"
SPF Hold-Down Interval imposes a minimum waiting period between runs of the decision process. This enables the router to incorporate topology changes into its link state database before running the decision process. Without the CLASS=MENUITEM MOREINFO="NONE"SPF Hold-Down Interval, the router would run the decision process for every topology change and waste its own processing resources. You can change the value of the CLASS=MENUITEM MOREINFO="NONE"SPF Hold-Down Interval from INETCFG.PAGENUM=52 ID="BP59"PAGENUM=53RENDERAS="SECT2"Path Cost and Packet ForwardingTo a large extent, IDXID="w3585"BOOK="_idx" COLLECTION="nw41" TIDREF="i2927"
NLSP uses an assigned path cost to choose the best route by which to forward IPX packets. The higher the throughput of the network medium, the lower the cost of the route. IDREF="FM52271"Table 3-2 shows the throughput range, its default IDXID="w3586"BOOK="_idx" COLLECTION="nw41" TIDREF="i2362"
cost, and some typical network media.LABEL="3-2" PGWIDE=0 TOCENTRY="1"ID="FM52271"Throughput Range and Default Cost for Typical Network MediaCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="8*"COLNAME=2 COLWIDTH="6*"COLNAME=3 COLWIDTH="10*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Throughput RangeCOLNAME=2 ROTATE="0" MOREROWS="0"Default CostCOLNAME=3 ROTATE="0" MOREROWS="0"Typical Network MediaVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"0-16 KbpsCOLNAME=2 ROTATE="0" MOREROWS="0"61COLNAME=3 ROTATE="0" MOREROWS="0"9600-Baud LineCOLNAME=1 ROTATE="0" MOREROWS="0"48-64 KbpsCOLNAME=2 ROTATE="0" MOREROWS="0"45COLNAME=3 ROTATE="0" MOREROWS="0"ISDN (U.S.)COLNAME=1 ROTATE="0" MOREROWS="0"64-128 KbpsCOLNAME=2 ROTATE="0" MOREROWS="0"45COLNAME=3 ROTATE="0" MOREROWS="0"ISDN (Europe)COLNAME=1 ROTATE="0" MOREROWS="0"1-2 MbpsCOLNAME=2 ROTATE="0" MOREROWS="0"27COLNAME=3 ROTATE="0" MOREROWS="0"Corvus Omninet (1 Mbps),T1 (1.5 Mbps)COLNAME=1 ROTATE="0" MOREROWS="0"2-4 MbpsCOLNAME=2 ROTATE="0" MOREROWS="0"26COLNAME=3 ROTATE="0" MOREROWS="0"E1 (2 Mbps),ARCNET (2.5 Mbps)COLNAME=1 ROTATE="0" MOREROWS="0"4-8 MbpsCOLNAME=2 ROTATE="0" MOREROWS="0"25COLNAME=3 ROTATE="0" MOREROWS="0"Token Ring (4 Mbps),Corvus Omninet (4 Mbps)COLNAME=1 ROTATE="0" MOREROWS="0"10-16 MbpsCOLNAME=2 ROTATE="0" MOREROWS="0"20COLNAME=3 ROTATE="0" MOREROWS="0"Ethernet (10 Mbps)COLNAME=1 ROTATE="0" MOREROWS="0"16-32 MbpsCOLNAME=2 ROTATE="0" MOREROWS="0"19COLNAME=3 ROTATE="0" MOREROWS="0"Token Ring (16 Mbps)COLNAME=1 ROTATE="0" MOREROWS="0"64-128 MbpsCOLNAME=2 ROTATE="0" MOREROWS="0"14COLNAME=3 ROTATE="0" MOREROWS="0"FDDI (100 Mbps),CDDI (100 Mbps)You can influence how an NLSP router forwards packets through its interfaces. By changing the cost associated with a particular interface, you can establish preferred routes or create equal-cost routes over which the router can distribute traffic bound for the same destination network.If you change the cost associated with a route on one router, make sure you change it on all other routers attached to the same network.PAGENUM=54 ID="BP60"RENDERAS="SECT2"ID="FM79930"Balancing Traffic Loads Over Equal-Cost RoutesNetWare IPX Router supports load balancing, a method by which an NLSP router distributes traffic bound for a single destination over as many as eight equal-cost routes to that destination.Load sharing is another name for load balancing.Consider the four routers on the network in IDREF="FM89382"Figure 3-6. Interfaces 1 through 6 represent individual paths between Router A and its first-hop routers, B and C. The purpose of load balancing is for Router A to use each of these paths equally to carry traffic destined for Router D.LABEL="3-6" FLOAT="0"ID="FM89382"Distributing Network Traffic over Equal-Cost RoutesFILEREF="loadbal.tif"Router A's forwarding database indicates that the next hop to Router D is either Router B or Router C, each of which has an equal-cost route to Router D. As it forwards each oubound packet, Router A alternates between Router B and Router C.Because there are multiple interfaces---and therefore, multiple paths---between Router A and the next-hop routers (B and C), Router A must also distribute the traffic evenly along each path. From the information in its link state database, Router A knows the MAC addresses and board numbers associated with each interface. Router A uses this information to compute a path to Router D for each outbound packet.PAGENUM=54 ID="BP61"PAGENUM=55With two paths to each next-hop router and two next-hop routers, Router A completes one "load-sharing cycle" every four packets. The following table traces the path of four packets---one cycle---from Router A to Router D: COLS=4 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="6*"COLNAME=3 COLWIDTH="4*"COLNAME=4 COLWIDTH="10*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Packet Number:COLNAME=2 ROTATE="0" MOREROWS="0"Passes Through Interfaces:COLNAME=3 ROTATE="0" MOREROWS="0"To Router:COLNAME=4 ROTATE="0" MOREROWS="0"Which Forwards it to Router:VALIGN="TOP"COLNAME=1 ALIGN="CENTER" ROTATE="0" MOREROWS="0"1COLNAME=2 ROTATE="0" MOREROWS="0"1 and 6COLNAME=3 ALIGN="CENTER" ROTATE="0" MOREROWS="0"BCOLNAME=4 ALIGN="CENTER" ROTATE="0" MOREROWS="0"DCOLNAME=1 ALIGN="CENTER" ROTATE="0" MOREROWS="0"2COLNAME=2 ROTATE="0" MOREROWS="0"3 and 5COLNAME=3 ALIGN="CENTER" ROTATE="0" MOREROWS="0"CCOLNAME=4 ALIGN="CENTER" ROTATE="0" MOREROWS="0"DCOLNAME=1 ALIGN="CENTER" ROTATE="0" MOREROWS="0"3COLNAME=2 ROTATE="0" MOREROWS="0"2 and 6COLNAME=3 ALIGN="CENTER" ROTATE="0" MOREROWS="0"BCOLNAME=4 ALIGN="CENTER" ROTATE="0" MOREROWS="0"DCOLNAME=1 ALIGN="CENTER" ROTATE="0" MOREROWS="0"4COLNAME=2 ROTATE="0" MOREROWS="0"3 and 4COLNAME=3 ALIGN="CENTER" ROTATE="0" MOREROWS="0"CCOLNAME=4 ALIGN="CENTER" ROTATE="0" MOREROWS="0"DRENDERAS="SECT1"ID="FM43362"NLSP System IDEach NLSP router is represented by a unique, six-byte hexadecimal number called IDXID="w3587"BOOK="_idx" COLLECTION="nw41" TIDREF="i2936"
the System ID. The default IDXID="w3588"BOOK="_idx" COLLECTION="nw41" TIDREF="i4381"
System ID comprises a two-byte constant, 0x0200, followed by the router's own internal network number. A typical NLSP System ID looks like this:FORMAT="LINESPECIFIC"MOREINFO="NONE"0200AA112482The System ID is contained in the LSPs that each router floods throughout the network.Each System ID must be unique throughout the network. Duplicate System IDs create serious problems and can, in fact, disable a network. Two routers using the same System ID exchange and update their LSPs indefinitely and, therefore, prevent the network from converging.PAGENUM=55 ID="BP62"PAGENUM=56RENDERAS="SECT1"ID="FM16677"Routing AreasIDXID="w3589"BOOK="_idx" COLLECTION="nw41" TIDREF="i3897"
The current version of the NLSP software specifies link state routing within a single routing area; this is called level 1 routing. A IDXID="w3590"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 versions of IDXID="w3591"BOOK="_idx" COLLECTION="nw41" TIDREF="i2927"
NLSP will link routing areas into routing domains (level 2 routing), and routing domains into a IDXID="w3592"BOOK="_idx" COLLECTION="nw41" TIDREF="i1605"global IPX internetwork (level 3 routing). A IDXID="w3593"BOOK="_idx" COLLECTION="nw41" TIDREF="i3899"
routing IDXID="w3594"BOOK="_idx" COLLECTION="nw41" TIDREF="i2936"
domain IDXID="w3595"BOOK="_idx" COLLECTION="nw41" TIDREF="i3897"
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.IDREF="FM25305"Figure 3-7 shows the hierarchy of routing areas and domains.LABEL="3-7" FLOAT="0"ID="FM25305"Routing Areas and Domains FILEREF="areas.tif"PAGENUM=57 ID="BP63"Routing areas establish hierarchy within a network. 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.Routing areas can prevent 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. If you assign addressing hierarchically, then a single filter can identify all systems within an area.Whenever a change occurs in an area---such as a link going down---all routers within the area run the decision process and eventually converge on the same view of the network.RENDERAS="SECT2"ID="FM42135"Area Addresses and MasksIDXID="w3596"BOOK="_idx" COLLECTION="nw41" TIDREF="i2936"
Basic IPX addressing is explained in IDREF="FM12933"Chapter 2, "IPX Routing Concepts." This section explains IPX addressing in the context of NLSP routing areas.IDXID="w3597"BOOK="_idx" COLLECTION="nw41" TIDREF="i2870"
Two 32-bit numbers---an area network number and a mask---identify a routing area. Together, these numbers constitute the IDXID="w3598"BOOK="_idx" COLLECTION="nw41" TIDREF="i111"area 
address. IDXID="w3599"BOOK="_idx" COLLECTION="nw41" TIDREF="i287"
Here is an example:IDXID="w3600"BOOK="_idx" COLLECTION="nw41" TIDREF="i286"MOREINFO="NONE"08068500 (area network number)MOREINFO="NONE"FFFFFF00 (mask)The default values for the area network number and mask are as follows:MARK=BULLETArea network number=00000000IDXID="w3601"BOOK="_idx" COLLECTION="nw41" TIDREF="i291"
Mask=00000000PAGENUM=57 ID="BP64"PAGENUM=58The area network number and IDXID="w3602"BOOK="_idx" COLLECTION="nw41" TIDREF="i2341"
mask are both set to zero to ensure compatibility with future versions of NLSP. Zero values mean that all NLSP routers operate in a single routing area.For more information about routing areas, see the BOOK="nlsp_enu" COLLECTION="nw41"NetWare 4.1 NLSP Migration Guide.Future releases of NLSP will support interarea (level 2) routing. Until then, it is unnecessary to configure area addresses on your IPX router.RENDERAS="SECT2"Novell Network RegistryIDXID="w3603"BOOK="_idx" COLLECTION="nw41" TIDREF="i2992"
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="w3604"BOOK="_idx" COLLECTION="nw41" TIDREF="i3636"
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 is a service that 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="w3605"BOOK="_idx" COLLECTION="nw41" TIDREF="i2843"
network addresses, call 1-408-577-7506 or send Internet E-mail to IDXID="w3606"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.LABEL="4"PAGENUM=59 ID="BP65"ID="FM64625"IPX Configuration ParametersThis chapter describes the IPXTM parameters you configure forIDXID="w3607"BOOK="_idx" COLLECTION="nw41" TIDREF="i1928"
 NetWare 4.1.This chapter contains the following sections:MARK=BULLETIDREF="FM60804""General IPX Protocol Parameters"This section describes general parameters that control the operation of both RIP and NetWare Link Services ProtocolTM (NLSPTM) routing protocols.IDREF="FM10731""RIP/SAP Parameters"This section describes the parameters that control the operation of RIP and SAP.IDREF="FM75766""NLSP Parameters"This section describes the parameters that control the operation of NLSP.IDREF="FM73876""Filter Parameters"This section describes the parameters that control route, service, and packet filtering.You configure the RIP/SAP and NLSPTM parameters from the Internetworking Configuration utility (INETCFG). To loadIDXID="w3608"BOOK="_idx" COLLECTION="nw41" TIDREF="i2156"
 INETCFG, type the following command at the server prompt:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INETCFG MOREINFO="NONE"<Enter>
PAGENUM=59 ID="BP66"PAGENUM=60You configure route, service, and packet filterIDXID="w3609"BOOK="_idx" COLLECTION="nw41" TIDREF="i759"
s from the Filter Configuration utility (FILTCFG). To load FILTCFG, type the following command at the server prompt:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD FILTCFG MOREINFO="NONE"<Enter>The INETCFG and IDXID="w3610"BOOK="_idx" COLLECTION="nw41" TIDREF="i2154"
FILTCFG interfaces consist of multiple levels of menus. This chapter provides information organized according to the menu hierarchy. Looking at the actual interface while reading the documentation will help you to understand its organization.Additionally, help information is available for each menu and parameter. To get help about a parameter or menu, highlight the item and press MOREINFO="NONE"<F1>.RENDERAS="SECT1"ID="FM60804"General IPX Protocol ParametersIDXID="w3611"BOOK="_idx" COLLECTION="nw41" TIDREF="i1951"
This section describes IPX protocol parameters that pertain to both RIP and NLSP. You use the IPX protocol parameters to set the routing protocol, enable or disable packet forwarding, and specify general routing characteristics, such as hop count limit.IPX protocol parameters are divided into novice and expert parameters. You use the novice parameters to control packet forwarding on the router, select the routing protocol---RIP or NLSP---and activate the core NetWare protocol stack. You use the expert parameters to customize the router software to suit your network. For example, the expert parameters enable you to set the hop count limit and various IPX/SPXTM parameters.PAGENUM=60 ID="BP67"PAGENUM=61RENDERAS="SECT2"Novice IPX ParametersThis section describes the novice IPX protocol parameters.RENDERAS="SECT3"Packet ForwardingIDXID="w3612"BOOK="_idx" COLLECTION="nw41" TIDREF="i2934"
Enables or disables IDXID="w3613"BOOK="_idx" COLLECTION="nw41" TIDREF="i3178"
forwarding of incoming IPX packets.Use this parameter carefully; disabling packet forwarding disables all IPX routing on the router.Options: Enabled, DisabledDefault: EnabledUtility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"IPXRENDERAS="SECT3"Routing ProtocolIDXID="w3614"BOOK="_idx" COLLECTION="nw41" TIDREF="i3897"
Specifies NLSP or RIP/SAP as the IDXID="w3615"BOOK="_idx" COLLECTION="nw41" TIDREF="i2934"
routing protocol.Options: RIP/SAP Only, NLSP with RIP/SAP CompatibilityDefault: RIP/SAP OnlyUtility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"IPXRENDERAS="SECT3"Advanced IPXIDXID="w3616"BOOK="_idx" COLLECTION="nw41" TIDREF="i2931"
Allows you to configure NLSP and other advanced IPX protocol parameters. Disable this parameter if you want to use the traditional NetWare IPX protocol stack; enable it if you want to use NLSP.Options: Enabled, DisabledDefault: DisabledUtility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"IPXPAGENUM=62 ID="BP68"RENDERAS="SECT2"Expert IPX ParametersThis section describes the expert IPX protocol parameters.RENDERAS="SECT3"Get Nearest Server RequestsIDXID="w3617"BOOK="_idx" COLLECTION="nw41" TIDREF="i1600"
Specifies whether the router ignores, or accepts and replies to, SAP Get Nearest Server Requests.Options: Accept, IgnoreDefault: AcceptUtility: 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"Expert Configuration OptionsRENDERAS="SECT3"ID="FM55885"Advanced Packet Type 20 FloodingIDXID="w3618"BOOK="_idx" COLLECTION="nw41" TIDREF="i126"IDXID="w3619"BOOK="_idx" COLLECTION="nw41" TIDREF="i2931"
Controls the propagation of type 20 packets through the router's interfaces. Type 20 is an IPX packet type that refers to any propagated packet. NetBIOS packets, for example, are type 20 packets. For more information, see IDREF="FM82047""NetBIOS."If this parameter is disabled, the router receives and propagates type 20 packets through all its interfaces, regardless of whether some of those interfaces are equal-cost paths to the same source.If this parameter is enabled, the router handles type 20 packets in the following ways:MARK=BULLETThe router does not "repropagate" type 20 packets originating from the same source but received through different interfaces. For example, if Router A receives a type 20 packet from Router B, it forwards the packet through its other interfaces. If Router A then receives the same packet from Router C, it discards it. This is a packet forwarding mechanism known as IDXID="w3620"BOOK="_idx" COLLECTION="nw41" TIDREF="i3849"reverse path forwarding.The router does not propagate type 20 packets through the same interface from which it receives them. This is known as IDXID="w3621"BOOK="_idx" COLLECTION="nw41" TIDREF="i4229"split horizon, a technique used with RIP and other distance vector routing protocols.PAGENUM=63 ID="BP69"If you use FILTCFG to configure NetBIOS packet filters, be aware of the following interactions between these filters and the CLASS=MENUITEM MOREINFO="NONE"Advanced Packet Type 20 Flooding parameter:MARK=BULLETSetting CLASS=MENUITEM MOREINFO="NONE"Advanced Packet Type 20 Flooding to CLASS=MENUITEM MOREINFO="NONE"Disabled overrides the effect of NetBIOS packet filters operating on any network interface.Conversely, the action of NetBIOS packet filters on any network interface overrides the effect of enabling the CLASS=MENUITEM MOREINFO="NONE"Advanced Packet Type 20 Flooding parameter.You can also use the following console command to set this parameter:FORMAT="LINESPECIFIC"MOREINFO="NONE"SET IPX NETBIOS REPLICATION OPTIONOptions: Enabled, DisabledDefault: DisabledUtility: 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"Expert Configuration OptionsRENDERAS="SECT3"Hop Count LimitIDXID="w3622"BOOK="_idx" COLLECTION="nw41" TIDREF="i1685"IDXID="w3623"BOOK="_idx" COLLECTION="nw41" TIDREF="i2931"
Limit on the maximum number of routers (hops) a packet can pass through before being discarded.Range: 8-127Default: 64Utility: 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"Expert Configuration OptionsPAGENUM=63 ID="BP70"PAGENUM=64RENDERAS="SECT3"IPX/SPX ParametersIDXID="w3624"BOOK="_idx" COLLECTION="nw41" TIDREF="i1387"
Entry point to the IPX/SPX parameters, which control operational characteristics of the IPX and Sequenced Packet ExchangeTM (SPXTM) protocols. IDXID="w3625"BOOK="_idx" COLLECTION="nw41" TIDREF="i2932"
Select this parameter to view or change the IPX/SPX parameters.Each parameter is set to a default value that is sufficient for most NetWare environments.Novell recommends against changing these default values.RENDERAS="SECT4"Maximum IPX Socket Table SizeIDXID="w3626"BOOK="_idx" COLLECTION="nw41" TIDREF="i2932"
Maximum number of concurrent IPX sockets that can be opened by an application program.Range: 60-65,520 (in increments of 60)Default: 1200Utility: 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"Expert Configuration Options > Select CLASS=MENUITEM MOREINFO="NONE"IPX/SPX ParametersRENDERAS="SECT4"SPX Watchdog Abort TimeoutIDXID="w3627"BOOK="_idx" COLLECTION="nw41" TIDREF="i2932"
Time, in ticks, SPX waits without receiving a packet from the other end of a connection before concluding that the connection is no longer valid. A tick is about 1/18 of a second.Range: 540-5,400Default: 540 (about 30 seconds)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"Expert Configuration Options > Select CLASS=MENUITEM MOREINFO="NONE"IPX/SPX ParametersPAGENUM=65 ID="BP71"RENDERAS="SECT4"SPX Watchdog Verify TimeoutIDXID="w3628"BOOK="_idx" COLLECTION="nw41" TIDREF="i2932"
Time, in ticks, SPX waits without receiving a packet from the other end of a connection before requesting a watchdog or keep-alive packet. A tick is about 1/18 of a second.Range: 10-255Default: 108 (about six seconds)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"Expert Configuration Options > Select CLASS=MENUITEM MOREINFO="NONE"IPX/SPX ParametersRENDERAS="SECT4"SPX Ack Wait TimeoutIDXID="w3629"BOOK="_idx" COLLECTION="nw41" TIDREF="i2932"
Time, in ticks, SPX waits without receiving an acknowledgment for a data packet it sent, before resending the packet. A tick is about 1/18 of a second.Range: 10-3,240Default: 54 (about three seconds)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"Expert Configuration Options > Select CLASS=MENUITEM MOREINFO="NONE"IPX/SPX ParametersPAGENUM=65 ID="BP72"PAGENUM=66RENDERAS="SECT4"SPX Default Retry CountIDXID="w3630"BOOK="_idx" COLLECTION="nw41" TIDREF="i2932"
Number of times SPX resends a data packet if it does not receive an acknowledgment.The product of this parameter and the CLASS=MENUITEM MOREINFO="NONE"SPX Ack Wait Timeout is about how long it takes for SPX to conclude that the connection is no longer valid.Range: 1-255Default: 10Utility: 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"Expert Configuration Options > Select CLASS=MENUITEM MOREINFO="NONE"IPX/SPX ParametersRENDERAS="SECT4"Maximum Concurrent SPX SessionsIDXID="w3631"BOOK="_idx" COLLECTION="nw41" TIDREF="i2932"
Maximum number of concurrent IPX sessions that can be opened by an application program.Range: 100-2,000Default: 1,000Utility: 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"Expert Configuration Options > Select CLASS=MENUITEM MOREINFO="NONE"IPX/SPX ParametersPAGENUM=66 ID="BP73"PAGENUM=67RENDERAS="SECT1"ID="FM10731"RIP/SAP ParametersIDXID="w3632"BOOK="_idx" COLLECTION="nw41" TIDREF="i759"
This section describes Routing Information Protocol (RIP) and Service Advertising Protocol (SAP) parameters. When configuring the software, you specify values or states for most parameters with INETCFG. The configuration settings you specify from INETCFG are written to an internal configuration file.RENDERAS="SECT2"RIP/SAP Setup for IPX RoutingIDXID="w3633"BOOK="_idx" COLLECTION="nw41" TIDREF="i1956"
To IDXID="w3634"BOOK="_idx" COLLECTION="nw41" TIDREF="i3873"
set up RIP/SAP on your IPX router, complete the following tasks from INETCFG:NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"Define a network interface board with the following information:Name (up to 17 alphanumeric characters, including underscore)Driver (the NE2000TM driver, for example)Status (enabled or disabled)Parameters (port number and interrupt, for example)You provide this information under CLASS=MENUITEM MOREINFO="NONE"Boards in the CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu.Make sure RIP routing is enabled through the CLASS=MENUITEM MOREINFO="NONE"Routing Protocol parameter.When you first load the software, RIP is already enabled as the routing protocol. If the active routing protocol is NLSP, change it to RIP before you configure the RIP and SAP parameters for your network interfaces.Enabling RIP routing automatically sets RIP as the routing protocol on all network interfaces in your IPX router. If you want to change the routing protocol or customize any related parameters on one of the interfaces, complete IDREF="FM73898"Step 4.PAGENUM=67 ID="BP74"PAGENUM=68Enable RIP/SAP filtering if you plan to configure any routing or service filters.RIP/SAP filtering operates only in the following configurations: (1) when RIP routing is enabled on all interfaces through the CLASS=MENUITEM MOREINFO="NONE"Routing Protocol parameter, and (2) when RIP routing is enabled on a particular network interface through the CLASS=MENUITEM MOREINFO="NONE"RIP State expert bind parameter.Note that packet forwarding filters operate when either RIP or NLSP routing is enabled.Routing and service filter parameters are described in IDREF="FM73876""Filter Parameters."ID="FM73898"Configure the RIP and SAP bind parameters for each network interface board.These parameters are described in IDREF="FM21591""RIP/SAP Bind Parameters."RENDERAS="SECT2"ID="FM21591"RIP/SAP Bind ParametersIDXID="w3635"BOOK="_idx" COLLECTION="nw41" TIDREF="i430"
This section describes the IDXID="w3636"BOOK="_idx" COLLECTION="nw41" TIDREF="i3871"
RIP and SAP parameters you configure for each LAN  interface to which you bind IPX. All RIP and SAP bind parameters are considered expert parameters.The software allows you to specify override values for certain RIP and SAP parameters. You use the override parameters to change default values that are based on the network medium. (The software determines these values and uses them as defaults.) You can use the IPX network management console (IPXCON) to discover these values before overriding them.PAGENUM=68 ID="BP75"PAGENUM=69When you select a LAN board, a new window displays the following fields:MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Network Interface---Name of the network interface board to which you bind IPX. This is a display-only field that appears in all RIP and SAP configuration windows.Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select a network interface (CLASS=MENUITEM MOREINFO="NONE"Binding IPX to a LAN Interface window appears)CLASS=MENUITEM MOREINFO="NONE"IPX Network Number---Four-byte network number assigned to the board.Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select a network interface (CLASS=MENUITEM MOREINFO="NONE"Binding IPX to a LAN Interface window appears)CLASS=MENUITEM MOREINFO="NONE"Frame Type---IDXID="w3637"BOOK="_idx" COLLECTION="nw41" TIDREF="i1568"
Frame type assigned to the board (ETHERNET_II, for example).Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select a network interface (CLASS=MENUITEM MOREINFO="NONE"Binding IPX to a LAN Interface window appears)CLASS=MENUITEM MOREINFO="NONE"Expert Bind Options---Entry point to the expert bind parameters. When you select CLASS=MENUITEM MOREINFO="NONE"Expert Bind Options, a new window displays the following fields:MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Network Interface---Name of the network interface board.Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select a network interface > Select CLASS=MENUITEM MOREINFO="NONE"Expert Bind OptionsPAGENUM=69 ID="BP76"PAGENUM=70IDXID="w3638"BOOK="_idx" COLLECTION="nw41" TIDREF="i2930"CLASS=MENUITEM MOREINFO="NONE"Delay Override---Value that overrides the default delay, in microseconds, for this interface.Range: 1-5,000,000Default: 0 (Do not override)Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select a network interface > Select CLASS=MENUITEM MOREINFO="NONE"Expert Bind OptionsIDXID="w3639"BOOK="_idx" COLLECTION="nw41" TIDREF="i2930"CLASS=MENUITEM MOREINFO="NONE"Throughput Override---Value that overrides the default throughput, in bits per second (bps), for this interface.Range: 300-4,294,967,295Default: 0 (Automatically determined)Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select a network interface > Select CLASS=MENUITEM MOREINFO="NONE"Expert Bind OptionsCLASS=MENUITEM MOREINFO="NONE"RIP Bind Options---Entry point to the RIP bind parameters. These are described in IDREF="FM69640""RIP Bind Parameters."CLASS=MENUITEM MOREINFO="NONE"SAP Bind Options---Entry point to the SAP bind parameters. These are described in IDREF="FM46622""SAP Bind Parameters."CLASS=MENUITEM MOREINFO="NONE"NLSP Bind Options---Entry point to the NLSP bind parameters. These are described in IDREF="FM35129""NLSP Bind Parameters."PAGENUM=70 ID="BP77"PAGENUM=71RENDERAS="SECT3"ID="FM69640"RIP Bind ParametersThis section describes the RIP parameters you configure for each bound LAN  interface.RENDERAS="SECT4"RIP StateIDXID="w3640"BOOK="_idx" COLLECTION="nw41" TIDREF="i3861"
Determines IDXID="w3641"BOOK="_idx" COLLECTION="nw41" TIDREF="i3861"
whether the router sends or receives RIP information over this IDXID="w3642"BOOK="_idx" COLLECTION="nw41" TIDREF="i3868"
interface.Options: Auto, Off, OnDefault: AutoUtility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select a network interface > Select CLASS=MENUITEM MOREINFO="NONE"Expert Bind Options > Select CLASS=MENUITEM MOREINFO="NONE"RIP Bind OptionsWhen CLASS=MENUITEM MOREINFO="NONE"RIP State is set to CLASS=MENUITEM MOREINFO="NONE"Auto, the router sends RIP packets only if other routers on the network send periodic RIP updates.Set CLASS=MENUITEM MOREINFO="NONE"RIP State to CLASS=MENUITEM MOREINFO="NONE"On if any servers or workstations on the network are running IDXID="w3643"BOOK="_idx" COLLECTION="nw41" TIDREF="i4658"
UnixWareTM software.RENDERAS="SECT4"Periodic Update IntervalIDXID="w3644"BOOK="_idx" COLLECTION="nw41" TIDREF="i3296"
Interval, in seconds, at which the router transmits RIP information. IDXID="w3645"BOOK="_idx" COLLECTION="nw41" TIDREF="i3861"
The interval is specified in 30-second units.Range: 1-1,000Default: 2 (60 seconds)Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select a network interface > Select CLASS=MENUITEM MOREINFO="NONE"Expert Bind Options > Select CLASS=MENUITEM MOREINFO="NONE"RIP Bind OptionsPAGENUM=71 ID="BP78"PAGENUM=72RENDERAS="SECT4"Aging Interval MultiplierIDXID="w3646"BOOK="_idx" COLLECTION="nw41" TIDREF="i142"
Multiplier that specifies how long the router keeps information received from periodic RIP updates.IDXID="w3647"BOOK="_idx" COLLECTION="nw41" TIDREF="i3861"
Multiplying the default values of the CLASS=MENUITEM MOREINFO="NONE"Periodic Update Interval and the CLASS=MENUITEM MOREINFO="NONE"Aging Interval Multiplier gives four minutes as the length of time RIP information is kept.Range: 1-10Default: 4Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select a network interface > Select CLASS=MENUITEM MOREINFO="NONE"Expert Bind Options > Select CLASS=MENUITEM MOREINFO="NONE"RIP Bind OptionsRENDERAS="SECT4"Pace OverrideIDXID="w3648"BOOK="_idx" COLLECTION="nw41" TIDREF="i3167"
Maximum IDXID="w3649"BOOK="_idx" COLLECTION="nw41" TIDREF="i3861"
pace, in packets per second (pps), at which the router can send RIP packets through an interface.The default---and maximum---pace for RIP packets is nine pps.Range: 1-9Default: 0 (Do not override the current pace)Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select a network interface > Select CLASS=MENUITEM MOREINFO="NONE"Expert Bind Options > Select CLASS=MENUITEM MOREINFO="NONE"RIP Bind OptionsPAGENUM=72 ID="BP79"PAGENUM=73RENDERAS="SECT4"Packet Size OverrideIDXID="w3650"BOOK="_idx" COLLECTION="nw41" TIDREF="i3187"
Value, in bytes, that IDXID="w3651"BOOK="_idx" COLLECTION="nw41" TIDREF="i3861"
overrides the default RIP packet size.Range: 40-65,535Default: 0 (Do not override)Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select a network interface > Select CLASS=MENUITEM MOREINFO="NONE"Expert Bind Options > Select CLASS=MENUITEM MOREINFO="NONE"RIP Bind OptionsRENDERAS="SECT3"ID="FM46622"SAP Bind ParametersThis section describes the SAP parameters you configure for each bound LAN  interface. RENDERAS="SECT4"SAP StateIDXID="w3652"BOOK="_idx" COLLECTION="nw41" TIDREF="i3950"
Parameter indicating whether the router sends or receives IDXID="w3653"BOOK="_idx" COLLECTION="nw41" TIDREF="i3944"
SAP information over this interface.Options: Auto, Off, OnDefault: AutoUtility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select a network interface > Select CLASS=MENUITEM MOREINFO="NONE"Expert Bind Options > Select CLASS=MENUITEM MOREINFO="NONE"SAP Bind OptionsIn the CLASS=MENUITEM MOREINFO="NONE"Auto state, the router sends SAP packets only if non-NLSP peer devices on the network send periodic SAP updates.Set CLASS=MENUITEM MOREINFO="NONE"SAP State to CLASS=MENUITEM MOREINFO="NONE"On if any servers or workstations on the network are running IDXID="w3654"BOOK="_idx" COLLECTION="nw41" TIDREF="i4658"
UnixWare or OS/2* Named Pipes.PAGENUM=73 ID="BP80"PAGENUM=74RENDERAS="SECT4"Get Nearest Server Requests OverrideIDXID="w3655"BOOK="_idx" COLLECTION="nw41" TIDREF="i1601"
Parameter specifying whether the router ignores or replies to IDXID="w3656"BOOK="_idx" COLLECTION="nw41" TIDREF="i3944"
Get Nearest Server SAP requests.If you accept the default option (CLASS=MENUITEM MOREINFO="NONE"No Override), the router uses the setting of the expert protocol parameter CLASS=MENUITEM MOREINFO="NONE"Get Nearest Server Requests. See IDREF="FM13455""General Expert Protocol Parameters" for a description of this parameter.Options: Accept, Ignore, No OverrideDefault: No OverrideUtility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select a network interface > Select CLASS=MENUITEM MOREINFO="NONE"Expert Bind Options > Select CLASS=MENUITEM MOREINFO="NONE"SAP Bind OptionsRENDERAS="SECT4"Periodic Update IntervalIDXID="w3657"BOOK="_idx" COLLECTION="nw41" TIDREF="i3297"
Interval at which the router transmits SAP information. The IDXID="w3658"BOOK="_idx" COLLECTION="nw41" TIDREF="i3944"
interval is specified in 30-second units.Range: 1-1,000Default: 2 (60 seconds)Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select a network interface > Select CLASS=MENUITEM MOREINFO="NONE"Expert Bind Options > Select CLASS=MENUITEM MOREINFO="NONE"SAP Bind OptionsPAGENUM=74 ID="BP81"PAGENUM=75RENDERAS="SECT4"Aging Interval MultiplierIDXID="w3659"BOOK="_idx" COLLECTION="nw41" TIDREF="i143"
Multiplier that specifies how long the router keeps information received from IDXID="w3660"BOOK="_idx" COLLECTION="nw41" TIDREF="i3944"
SAP periodic updates.Multiplying the default values of the CLASS=MENUITEM MOREINFO="NONE"Periodic Update Interval and the CLASS=MENUITEM MOREINFO="NONE"Aging Interval Multiplier gives four minutes as the length of time SAP information is kept.Range: 1-10Default: 4Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select a network interface > Select CLASS=MENUITEM MOREINFO="NONE"Expert Bind Options > Select CLASS=MENUITEM MOREINFO="NONE"SAP Bind OptionsRENDERAS="SECT4"Pace OverrideIDXID="w3661"BOOK="_idx" COLLECTION="nw41" TIDREF="i3168"
Maximum IDXID="w3662"BOOK="_idx" COLLECTION="nw41" TIDREF="i3944"
pace, in pps, at which the router can send SAP packets through an interface.The default---and maximum---pace for SAP packets is nine pps.Range: 1-9Default: 0 (Do not override the current pace)Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select a network interface > Select CLASS=MENUITEM MOREINFO="NONE"Expert Bind Options > Select CLASS=MENUITEM MOREINFO="NONE"SAP Bind OptionsPAGENUM=75 ID="BP82"PAGENUM=76RENDERAS="SECT4"Packet Size OverrideIDXID="w3663"BOOK="_idx" COLLECTION="nw41" TIDREF="i3188"
Value, in bytes, that IDXID="w3664"BOOK="_idx" COLLECTION="nw41" TIDREF="i3944"
overrides the default SAP packet size.Range: 96-65,535Default: 0 (Do not override)Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select a network interface > Select CLASS=MENUITEM MOREINFO="NONE"Expert Bind Options > Select CLASS=MENUITEM MOREINFO="NONE"SAP Bind OptionsRENDERAS="SECT1"ID="FM75766"NLSP ParametersIDXID="w3665"BOOK="_idx" COLLECTION="nw41" TIDREF="i2935"
This section describes NLSP parameters. When configuring the software, you specify values or states for most options with INETCFG. The configuration settings you specify from INETCFG are written to a private configuration file.The NLSP configuration parameters are divided into two categories:MARK=BULLETProtocol parameters, which control the operation and performance of NLSP on the networkBind parameters, which control the operation of NLSP on each network interface to which IPX is boundPAGENUM=76 ID="BP83"PAGENUM=77RENDERAS="SECT2"NLSP Setup for IPX RoutingIDXID="w3666"BOOK="_idx" COLLECTION="nw41" TIDREF="i4107"
To use the IDXID="w3667"BOOK="_idx" COLLECTION="nw41" TIDREF="i1957"
NLSP routing protocol on your IPX router, complete the following tasks from INETCFG:NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"Define a network interface board with the following information:Name (up to 17 alphanumeric characters, including underscore)Driver (NE2000, for example)Status (enabled or disabled)Parameters (port number and interrupt, for example)You provide this information under CLASS=MENUITEM MOREINFO="NONE"Boards in the CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu.Make sure NLSP routing is enabled.When you first load the software, RIP is enabled as the routing protocol. Change the active routing protocol to NLSP before you configure the NLSP protocol and bind parameters.Configure the NLSP protocol parameters.These parameters are described in IDREF="FM76860""NLSP Expert Protocol Parameters."Configure the NLSP bind parameters for each interface.These parameters are described in IDREF="FM35129""NLSP Bind Parameters."RENDERAS="SECT2"ID="FM76860"NLSP Expert Protocol ParametersIDXID="w3668"BOOK="_idx" COLLECTION="nw41" TIDREF="i2931"
The NLSP expert protocol parameters comprise two categories: general parameters, which are described in IDREF="FM13455""General Expert Protocol Parameters," and convergence parameters, which are described in IDREF="FM65880""Convergence Parameters."PAGENUM=77 ID="BP84"PAGENUM=78RENDERAS="SECT3"ID="FM13455"General Expert Protocol ParametersThe parameters described in this section enable you to control general NLSP routing characteristics.RENDERAS="SECT4"Maximum Number of Path SplitsIDXID="w3669"BOOK="_idx" COLLECTION="nw41" TIDREF="i2355"IDXID="w3670"BOOK="_idx" COLLECTION="nw41" TIDREF="i2931"
Maximum number of paths a packet can take to reach the same destination. If there are several paths to a destination, the router can distribute the traffic across those paths. This is called load balancing or load sharing.Range: 1-8Default: 1Utility: 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"Expert Configuration OptionsRENDERAS="SECT4"LSP SizeIDXID="w3671"BOOK="_idx" COLLECTION="nw41" TIDREF="i2247"IDXID="w3672"BOOK="_idx" COLLECTION="nw41" TIDREF="i2931"
Size, in bytes, of the Link State Packet (LSP). The larger the packet your network can handle, the fewer LSPs are necessary to propagate link state information.Range: 128-4096Default: 512Utility: 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"Expert Configuration OptionsPAGENUM=78 ID="BP85"PAGENUM=79RENDERAS="SECT4"NLSP Local Area AddressesIDXID="w3673"BOOK="_idx" COLLECTION="nw41" TIDREF="i2933"
Specifies up to three local IDXID="w3674"BOOK="_idx" COLLECTION="nw41" TIDREF="i2931"
area addresses (IPX network number and mask). Any IPX router can have up to three area addresses.Use the default value.Range: 0-FFFFFFFFDefault: 0Utility: 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"Expert Configuration OptionsRENDERAS="SECT4"Override NLSP System IDIDXID="w3675"BOOK="_idx" COLLECTION="nw41" TIDREF="i2931"
Parameter that allows you to override the default NLSP System ID assigned by your copy of the software. Enabling this parameter lets you assign your own NLSP System ID to the router.You might want to override the default ID if you have purchased multiple copies of the software but are installing the software from a single copy.Options: Enabled, DisabledDefault: DisabledUtility: 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"Expert Configuration OptionsPAGENUM=79 ID="BP86"PAGENUM=80RENDERAS="SECT4"NLSP System IdentificationIDXID="w3676"BOOK="_idx" COLLECTION="nw41" TIDREF="i2931"
Six-byte hexadecimal number that uniquely identifies the router on the network.To enter your own NLSP System ID, you must first enable the CLASS=MENUITEM MOREINFO="NONE"Override NLSP System ID parameter.Separate each byte with a hyphen when you enter the NLSP System ID.Range: 0-FF-FF-FF-FF-FF-FFUtility: 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"Expert Configuration OptionsRENDERAS="SECT4"NLSP Convergence RateIDXID="w3677"BOOK="_idx" COLLECTION="nw41" TIDREF="i2931"
General control over the parameters that determine the rate at which NLSP routing information converges on a network.CLASS=MENUITEM MOREINFO="NONE"Manual allows you to set the values of individual convergence parameters.Options: Default, Fast, ManualDefault: DefaultUtility: 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"Expert Configuration OptionsThese parameters are described in IDREF="FM65880""Convergence Parameters."PAGENUM=80 ID="BP87"PAGENUM=81RENDERAS="SECT4"NLSP Convergence Rate ConfigurationIDXID="w3678"BOOK="_idx" COLLECTION="nw41" TIDREF="i2931"
Entry point to the NLSP convergence parameters.Select this parameter to view or change convergence parameters. These parameters are described in IDREF="FM65880""Convergence Parameters."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"Expert Configuration OptionsRENDERAS="SECT3"ID="FM65880"Convergence ParametersIDXID="w3679"BOOK="_idx" COLLECTION="nw41" TIDREF="i2929"Convergence rate refers to the rate at which NLSP routing information converges on all NLSP routers across your IPX internetwork. You can specify the convergence rate by setting the CLASS=MENUITEM MOREINFO="NONE"NLSP Rate of Convergence parameter to one of the following choices:MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Default---Nominal set of values that are suitable for stable networks, whose topology remains largely the same from day to day.CLASS=MENUITEM MOREINFO="NONE"Fast---Causes the routing information to converge faster than does the Default setting.CLASS=MENUITEM MOREINFO="NONE"Fast is suitable for small, volatile networks, whose topology tends to change frequently. A faster rate of conversion results in more traffic on the network.CLASS=MENUITEM MOREINFO="NONE"Manual---Allows you to choose values for individual convergence parameters.Following are descriptions of the convergence parameters. All parameters---except for the CLASS=MENUITEM MOREINFO="NONE"Holding Timer Multiplier, which is dimensionless---are measured in seconds.Modify the convergence parameters only if you understand the effect your changes will have on the operation of your router. Arbitrary or uninformed changes to these parameters can waste network bandwidth and slow the convergence of your network.PAGENUM=81 ID="BP88"PAGENUM=82RENDERAS="SECT4"SPF Hold-Down IntervalIDXID="w3680"BOOK="_idx" COLLECTION="nw41" TIDREF="i2929"
Time interval between runs of the decision process.Range: 1-100Fast = 2Default = 5Utility: 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"Expert Configuration Options > Select CLASS=MENUITEM MOREINFO="NONE"NLSP Convergence Rate ConfigurationRENDERAS="SECT4"Minimum LSP Generation IntervalIDXID="w3681"BOOK="_idx" COLLECTION="nw41" TIDREF="i2929"
Minimum time interval at which the router generates a local LSP.Range: 1-30Fast = 2Default = 5Utility: 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"Expert Configuration Options > Select CLASS=MENUITEM MOREINFO="NONE"NLSP Convergence Rate ConfigurationRENDERAS="SECT4"Maximum LSP Generation IntervalIDXID="w3682"BOOK="_idx" COLLECTION="nw41" TIDREF="i2929"
Maximum time interval at which the router generates a local LSP.Range: 500-65,000Fast = 7,200Default = 7,200Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)PAGENUM=83 ID="BP89"Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"Expert Configuration Options > Select CLASS=MENUITEM MOREINFO="NONE"NLSP Convergence Rate ConfigurationRENDERAS="SECT4"Maximum LSP AgeIDXID="w3683"BOOK="_idx" COLLECTION="nw41" TIDREF="i2929"
Maximum number of seconds the router keeps an LSP.Range: 800-65,535Fast = 7,500Default = 7,500Utility: 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"Expert Configuration Options > Select CLASS=MENUITEM MOREINFO="NONE"NLSP Convergence Rate ConfigurationRENDERAS="SECT4"Minimum Broadcast LSP Transmission IntervalIDXID="w3684"BOOK="_idx" COLLECTION="nw41" TIDREF="i2929"
Minimum time interval at which the router broadcasts an LSP over a LAN.Range: 1-60Fast = 5Default = 5Utility: 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"Expert Configuration Options > Select CLASS=MENUITEM MOREINFO="NONE"NLSP Convergence Rate ConfigurationPAGENUM=83 ID="BP90"PAGENUM=84RENDERAS="SECT4"Minimum Non-Broadcast LSP Transmission IntervalIDXID="w3685"BOOK="_idx" COLLECTION="nw41" TIDREF="i2929"
Minimum time interval at which the router transmits an LSP over a nonbroadcast link.Range: 2-60Fast = 5Default = 5Utility: 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"Expert Configuration Options > Select CLASS=MENUITEM MOREINFO="NONE"NLSP Convergence Rate ConfigurationRENDERAS="SECT4"Complete SNP IntervalIDXID="w3686"BOOK="_idx" COLLECTION="nw41" TIDREF="i2929"
Time interval at which the router sends Complete Sequence Number Packets (CSNPs) over a LAN.For information about CSNPs, see IDREF="FM37436""Disseminating Link State Updates Among NLSP Routers."Range: 1-240Fast = 10Default = 30Utility: 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"Expert Configuration Options > Select CLASS=MENUITEM MOREINFO="NONE"NLSP Convergence Rate ConfigurationPAGENUM=84 ID="BP91"PAGENUM=85RENDERAS="SECT4"Partial SNP IntervalIDXID="w3687"BOOK="_idx" COLLECTION="nw41" TIDREF="i2929"
Time interval at which the router sends Partial Sequence Number Packets (PSNPs).For information about PSNPs, see IDREF="FM37436""Disseminating Link State Updates Among NLSP Routers."Range: 1-60Fast = 1Default = 1Utility: 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"Expert Configuration Options > Select CLASS=MENUITEM MOREINFO="NONE"NLSP Convergence Rate ConfigurationRENDERAS="SECT4"Broadcast Hello IntervalIDXID="w3688"BOOK="_idx" COLLECTION="nw41" TIDREF="i2929"
Time IDXID="w3689"BOOK="_idx" COLLECTION="nw41" TIDREF="i1652"
interval at which NLSP Hello packets are sent on a broadcast circuit.Range: 1-100Fast = 10Default = 20Utility: 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"Expert Configuration Options > Select CLASS=MENUITEM MOREINFO="NONE"NLSP Convergence Rate ConfigurationPAGENUM=85 ID="BP92"PAGENUM=86RENDERAS="SECT4"Non-Broadcast Hello IntervalIDXID="w3690"BOOK="_idx" COLLECTION="nw41" TIDREF="i2929"
Time IDXID="w3691"BOOK="_idx" COLLECTION="nw41" TIDREF="i1652"
interval at which NLSP Hello packets are sent on a nonbroadcast circuit.Range: 1-100Fast = 10Default = 20Utility: 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"Expert Configuration Options > Select CLASS=MENUITEM MOREINFO="NONE"NLSP Convergence Rate ConfigurationRENDERAS="SECT4"Holding Timer MultiplierIDXID="w3692"BOOK="_idx" COLLECTION="nw41" TIDREF="i2929"
Time IDXID="w3693"BOOK="_idx" COLLECTION="nw41" TIDREF="i1678"
multiplier for adjacencies as a function of the CLASS=MENUITEM MOREINFO="NONE"Hello Interval.Range: 2-20Fast = 3Default = 3Utility: 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"Expert Configuration Options > Select CLASS=MENUITEM MOREINFO="NONE"NLSP Convergence Rate ConfigurationRENDERAS="SECT4"Designated Router Broadcast Hello IntervalIDXID="w3694"BOOK="_idx" COLLECTION="nw41" TIDREF="i2929"
Time interval at which the Designated Router sends NLSP Hello packets.For information about the Designated Router, see IDREF="FM20976""How the Designated Router is Elected."Range: 1-100Fast = 5PAGENUM=87 ID="BP93"Default = 10Utility: 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"Expert Configuration Options > Select CLASS=MENUITEM MOREINFO="NONE"NLSP Convergence Rate ConfigurationRENDERAS="SECT2"ID="FM35129"NLSP Bind ParametersYou configure the IDXID="w3695"BOOK="_idx" COLLECTION="nw41" TIDREF="i2928"
NLSP bind parameters for each network interface to which you bind IPX. All NLSP bind parameters are considered expert parameters.You use the override parameters to change default values that are based on the network medium. (The software determines these values and uses them as defaults.) You can use IPXCON to discover these values before overriding them.When you select a board, a new window displays the following fields:MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Network Interface---Name of the network interface board to which you bind IPX. This is a display-only field that appears in all NLSP configuration windows.Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select a network interface (CLASS=MENUITEM MOREINFO="NONE"Binding IPX to a LAN Interface window appears)CLASS=MENUITEM MOREINFO="NONE"IPX Network Number---Four-byte network number assigned to the board.Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select a network interface (CLASS=MENUITEM MOREINFO="NONE"Binding IPX to a LAN Interface window appears)PAGENUM=87 ID="BP94"PAGENUM=88CLASS=MENUITEM MOREINFO="NONE"Frame Type---IDXID="w3696"BOOK="_idx" COLLECTION="nw41" TIDREF="i1568"
Frame type assigned to the board (ETHERNET_II, for example).Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select a network interface (CLASS=MENUITEM MOREINFO="NONE"Binding IPX to a LAN Interface window appears)CLASS=MENUITEM MOREINFO="NONE"Expert Bind Options---Entry point to the expert bind parameters. When you select CLASS=MENUITEM MOREINFO="NONE"Expert Bind Options, a new window displays the following fields:MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Network Interface---Name of the network interface board.Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select a network interface > Select CLASS=MENUITEM MOREINFO="NONE"Expert Bind OptionsIDXID="w3697"BOOK="_idx" COLLECTION="nw41" TIDREF="i2930"CLASS=MENUITEM MOREINFO="NONE"Delay Override---Value that overrides the default delay, in microseconds, for this interface.Range: 1-5,000,000Default: 0 (Do not override)Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select a network interface > Select CLASS=MENUITEM MOREINFO="NONE"Expert Bind OptionsIDXID="w3698"BOOK="_idx" COLLECTION="nw41" TIDREF="i2930"CLASS=MENUITEM MOREINFO="NONE"Throughput Override---Value that overrides the default throughput, in bps, for this interface.Range: 300-4,294,967,295Default: 0 (Automatically determined)Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select a network interface > Select CLASS=MENUITEM MOREINFO="NONE"Expert Bind OptionsPAGENUM=88 ID="BP95"PAGENUM=89CLASS=MENUITEM MOREINFO="NONE"RIP Bind Options---Entry point to the RIP bind parameters. These are described in IDREF="FM69640""RIP Bind Parameters."CLASS=MENUITEM MOREINFO="NONE"SAP Bind Options---Entry point to the SAP bind parameters. These are described in IDREF="FM46622""SAP Bind Parameters."IDXID="w3699"BOOK="_idx" COLLECTION="nw41" TIDREF="i2930"CLASS=MENUITEM MOREINFO="NONE"NLSP Bind Options---Entry point to the NLSP bind parameters. These are described in the pages that follow.RENDERAS="SECT3"NLSP StateIDXID="w3700"BOOK="_idx" COLLECTION="nw41" TIDREF="i2930"
Indicates whether the router sends or receives NLSP information over this interface.Options: On, OffDefault: OnUtility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select a network interface > Select CLASS=MENUITEM MOREINFO="NONE"Expert Bind Options > Select CLASS=MENUITEM MOREINFO="NONE"NLSP Bind OptionsRENDERAS="SECT4"MAC ChannelIDXID="w3701"BOOK="_idx" COLLECTION="nw41" TIDREF="i2930"
Transmission mode for NLSP packets.By default, NLSP broadcasts its packets because some LAN drivers do not properly support multicast, a transmission mode that directs only those devices listening for a specified multicast packet address to accept the packet.All NetWare systems on the same LAN must use the same NLSP packet transmission mode.Options: Broadcast, MulticastDefault: BroadcastUtility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select a network interface > Select CLASS=MENUITEM MOREINFO="NONE"Expert Bind Options > Select CLASS=MENUITEM MOREINFO="NONE"NLSP Bind OptionsPAGENUM=90 ID="BP96"RENDERAS="SECT4"MTU OverrideIDXID="w3702"BOOK="_idx" COLLECTION="nw41" TIDREF="i2930"
Maximum packet size, in bytes, allowed on this interface.Range: 576-65,535Default: 0 (Do not override)Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select a network interface > Select CLASS=MENUITEM MOREINFO="NONE"Expert Bind Options > Select CLASS=MENUITEM MOREINFO="NONE"NLSP Bind OptionsRENDERAS="SECT4"PriorityIDXID="w3703"BOOK="_idx" COLLECTION="nw41" TIDREF="i2930"
Priority for becoming the Designated Router.For information about the Designated Router, see IDREF="FM20976""How the Designated Router is Elected."Range: 0-127Default: 64Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select a network interface > Select CLASS=MENUITEM MOREINFO="NONE"Expert Bind Options > Select CLASS=MENUITEM MOREINFO="NONE"NLSP Bind OptionsRENDERAS="SECT4"Cost OverrideIDXID="w3704"BOOK="_idx" COLLECTION="nw41" TIDREF="i2930"
Overrides the default cost of using this interface.NLSP uses the cost when determining the best path to the destination.To see a list of the default costs associated with various network media, see IDREF="FM52271"Table 3-2.Range: 1-63Default: 0 (Do not override)PAGENUM=90 ID="BP97"PAGENUM=91Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select a network interface > Select CLASS=MENUITEM MOREINFO="NONE"Expert Bind Options > Select CLASS=MENUITEM MOREINFO="NONE"NLSP Bind OptionsRENDERAS="SECT4"Pace OverrideIDXID="w3705"BOOK="_idx" COLLECTION="nw41" TIDREF="i2930"
Maximum pace, in pps, at which NLSP packets can be sent through an interface.On a LAN, the default---and maximum---pace for NLSP packets is 30 pps.Range: 1-1,000Default: 0 (Do not override the current pace)Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select a network interface > Select CLASS=MENUITEM MOREINFO="NONE"Expert Bind Options > Select CLASS=MENUITEM MOREINFO="NONE"NLSP Bind OptionsRENDERAS="SECT1"ID="FM73876"Filter ParametersThis section describes the filter configuration parameters that pertain to IPX, RIP, and SAP. These parameters fall into the following categories:MARK=BULLETIDXID="w3706"BOOK="_idx" COLLECTION="nw41" TIDREF="i3945"
Incoming and outgoing SAP filtersIDXID="w3707"BOOK="_idx" COLLECTION="nw41" TIDREF="i3862"
Incoming and outgoing RIP filtersIDXID="w3708"BOOK="_idx" COLLECTION="nw41" TIDREF="i2647"
NetBIOS broadcast filtersIDXID="w3709"BOOK="_idx" COLLECTION="nw41" TIDREF="i1944"
Packet forwarding filtersPAGENUM=91 ID="BP98"PAGENUM=92RENDERAS="SECT2"Enabling Filtering SupportBefore you configure any filters, you must enable filtering support from INETCFG as follows:NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"Select CLASS=MENUITEM MOREINFO="NONE"Protocols from the CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu.Select CLASS=MENUITEM MOREINFO="NONE"IPX.The CLASS=MENUITEM MOREINFO="NONE"IPX Protocol Configuration window appears.Select CLASS=MENUITEM MOREINFO="NONE"Filtering Support.Select CLASS=MENUITEM MOREINFO="NONE"Enabled, then press MOREINFO="NONE"<Enter>.INETCFG writes the following line to the NETINFO.CFG configuration file:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD IPXFLTPress MOREINFO="NONE"<Esc> until you exit INETCFG, then type the following command at the server prompt:FORMAT="LINESPECIFIC"MOREINFO="NONE"REINITIALIZE SYSTEM MOREINFO="NONE"<Enter>This executes the MOREINFO="NONE"LOAD IPXFLT command and activates any filters you have already configured.To configure more filters, type the following command at the server prompt:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD FILTCFG MOREINFO="NONE"<Enter>The CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears.RENDERAS="SECT2"SAP Filter ParametersIDXID="w3710"BOOK="_idx" COLLECTION="nw41" TIDREF="i3945"SAP filters restrict the propagation of SAP broadcasts throughout an IPX internetwork.IDXID="w3711"BOOK="_idx" COLLECTION="nw41" TIDREF="i1497"
SAP filters have two purposes: they reduce the network bandwidth consumed by the periodic SAP broadcasts by filtering out unnecessary service advertisements, and they increase security by restricting the visibility of services at selected locations.PAGENUM=93 ID="BP99"FILTCFG allows you to configure two types of SAP filters:MARK=BULLETOutgoing SAP Filters, which limit the propagation of service advertisements by the router to a selected set of services at a selected set of networksIncoming SAP Filters, which limit the acceptance of service advertisements received by the router to a selected set of services at a selected set of networksRENDERAS="SECT3"Outgoing SAP Filter ParametersTo display the IDXID="w3712"BOOK="_idx" COLLECTION="nw41" TIDREF="i3156"
outgoing SAP filter parameters, complete the following steps:NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"Select CLASS=MENUITEM MOREINFO="NONE"IPX from the CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu.The CLASS=MENUITEM MOREINFO="NONE"IPX window appears.Select CLASS=MENUITEM MOREINFO="NONE"Outgoing SAP Filters.The CLASS=MENUITEM MOREINFO="NONE"Outgoing SAP Filters window appears. The outgoing SAP filter parameters are described in the sections that follow.RENDERAS="SECT4"StatusEnables or disables outgoing SAP filters.Options: Enabled, DisabledDefault: DisabledUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing SAP FiltersPAGENUM=93 ID="BP100"PAGENUM=94RENDERAS="SECT4"ActionSpecifies what to do with an outgoing service (SAP packet) that appears in the CLASS=MENUITEM MOREINFO="NONE"Filter list.Options: Permit Services in Filter List, Deny Services in Filter ListDefault: Permit Services in Filter ListUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing SAP FiltersRENDERAS="SECT4"FiltersSpecifies which outgoing services are sent (permitted) or filtered (denied) on an interface.Select this parameter to see the list of service filters.MARK=BULLETTo delete a service filter from the list, select it, then press MOREINFO="NONE"<Delete>.To modify a service filter already in the list, select it, then press MOREINFO="NONE"<Enter>.To add a service filter to the list, press MOREINFO="NONE"<Ins>.A new window displays the following parameters:MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Service Name---Name of the service. Press MOREINFO="NONE"<Ins> to choose one of the services from the router's bindery.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing SAP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Filters > Press MOREINFO="NONE"<Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Filter window appears)CLASS=MENUITEM MOREINFO="NONE"Service Type---Type of service. Press MOREINFO="NONE"<Ins> to choose one of the service types from the router's bindery.If you want to define your own service type, press MOREINFO="NONE"<Ins> again, then enter the service type name and a unique, two-byte hexadecimal value. You can also delete any service type you define; just select the service type, then press MOREINFO="NONE"<Del>.PAGENUM=94 ID="BP101"PAGENUM=95Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing SAP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Filters > Press MOREINFO="NONE"<Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Filter window appears)CLASS=MENUITEM MOREINFO="NONE"Interface---Network interface on which you want to filter the service. Press MOREINFO="NONE"<Ins> to choose one of the router's interfaces.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing SAP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Filters > Press MOREINFO="NONE"<Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Filter window appears)CLASS=MENUITEM MOREINFO="NONE"Comment---Short description of the filter. You can use up to 49 characters.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing SAP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Filters > Press MOREINFO="NONE"<Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Filter window appears)RENDERAS="SECT4"ExceptionsLists outgoing services to which the action---permit or deny---does not apply. These are the exceptions to the CLASS=MENUITEM MOREINFO="NONE"Filter list.Select this parameter to see the list of service filters.MARK=BULLETTo delete a service filter from the list, select it, then press MOREINFO="NONE"<Delete>.To modify a service filter already in the list, select it, then press MOREINFO="NONE"<Enter>.To add a service filter to the list, press MOREINFO="NONE"<Ins>.A new window displays the following parameters:MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Service Name---Name of the service. Press MOREINFO="NONE"<Ins> to choose one of the services from the router's bindery.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing SAP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions > Press MOREINFO="NONE"<Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Exception window appears)PAGENUM=95 ID="BP102"PAGENUM=96CLASS=MENUITEM MOREINFO="NONE"Service Type---Type of service. Press MOREINFO="NONE"<Ins> to choose one of the service types from the router's bindery.If you want to define your own service type, press MOREINFO="NONE"<Ins> again, then enter the service type name and a unique, two-byte hexadecimal value. You can also delete any service type you define; just select the service type, then press MOREINFO="NONE"<Del>.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing SAP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions > Press MOREINFO="NONE"<Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Exception window appears)CLASS=MENUITEM MOREINFO="NONE"Interface---Network interface on which you want to filter the service. Press MOREINFO="NONE"<Ins> to choose one of the router's interfaces.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing SAP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions > Press MOREINFO="NONE"<Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Exception window appears)CLASS=MENUITEM MOREINFO="NONE"Comment---Short description of the filter. You can use up to 49 characters.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing SAP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions > Press MOREINFO="NONE"<Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Exception window appears)RENDERAS="SECT3"Incoming SAP Filter ParametersTo display the incoming SAP filter parameters, complete the following steps:NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"Select CLASS=MENUITEM MOREINFO="NONE"IPX from the CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu.The CLASS=MENUITEM MOREINFO="NONE"IPX window appears.Select CLASS=MENUITEM MOREINFO="NONE"Incoming SAP Filters.The CLASS=MENUITEM MOREINFO="NONE"Incoming SAP Filters window appears. The incoming SAP filter parameters are described in the sections that follow.PAGENUM=96 ID="BP103"PAGENUM=97RENDERAS="SECT4"StatusEnables or disables incoming SAP filters.Options: Enabled, DisabledDefault: DisabledUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"Incoming SAP FiltersRENDERAS="SECT4"ActionSpecifies what to do with an incoming service (SAP packet) that appears in the CLASS=MENUITEM MOREINFO="NONE"Filter list.Options: Permit Services in Filter List, Deny Services in Filter ListDefault: Permit Services in Filter ListUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"Incoming SAP FiltersRENDERAS="SECT4"FiltersSpecifies which incoming services are accepted (permitted) or filtered (denied) on an interface.Select this parameter to see the list of service filters.MARK=BULLETTo delete a service filter from the list, select it, then press MOREINFO="NONE"<Delete>.To modify a service filter already in the list, select it, then press MOREINFO="NONE"<Enter>.PAGENUM=97 ID="BP104"PAGENUM=98To add a service filter to the list, press MOREINFO="NONE"<Ins>.A new window displays the following parameters:MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Service Name---Name of the service. Press MOREINFO="NONE"<Ins> to choose one of the services from the router's bindery.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"Incoming SAP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Filters > Press MOREINFO="NONE"<Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Filter window appears)CLASS=MENUITEM MOREINFO="NONE"Service Type---Type of service. Press MOREINFO="NONE"<Ins> to choose one of the service types from the router's bindery.If you want to define your own service type, press MOREINFO="NONE"<Ins> again, then enter the service type name and a unique, two-byte hexadecimal value. You can also delete any service type you define; just select the service type, then press MOREINFO="NONE"<Del>.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"Incoming SAP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Filters > Press MOREINFO="NONE"<Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Filter window appears)CLASS=MENUITEM MOREINFO="NONE"Interface---Network interface on which you want to filter the service. Press MOREINFO="NONE"<Ins> to choose one of the router's interfaces.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"Incoming SAP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Filters > Press MOREINFO="NONE"<Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Filter window appears)CLASS=MENUITEM MOREINFO="NONE"Comment---Short description of the filter. You can use up to 49 characters.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"Incoming SAP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Filters > Press MOREINFO="NONE"<Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Filter window appears)PAGENUM=98 ID="BP105"PAGENUM=99RENDERAS="SECT4"ExceptionsLists incoming services to which the action---permit or deny---does not apply. These are the exceptions to the CLASS=MENUITEM MOREINFO="NONE"Filter list.Select this parameter to see the list of service filters.MARK=BULLETTo delete a service filter from the list, select it, then press MOREINFO="NONE"<Delete>.To modify a service filter in the list, select it, then press MOREINFO="NONE"<Enter>.To add a service filter to the list, press MOREINFO="NONE"<Ins>.A new window displays the following parameters:MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Service Name---Name of the service. Press MOREINFO="NONE"<Ins> to choose one of the services from the router's bindery.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"Incoming SAP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions > Press MOREINFO="NONE"<Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Exception window appears)CLASS=MENUITEM MOREINFO="NONE"Service Type---Type of service. Press MOREINFO="NONE"<Ins> to choose one of the service types from the router's bindery.If you want to define your own service type, press MOREINFO="NONE"<Ins> again, then enter the service type name and a unique, two-byte hexadecimal value. You can also delete any service type you define; just select the service type, then press MOREINFO="NONE"<Del>.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"Incoming SAP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions > Press MOREINFO="NONE"<Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Exception window appears)CLASS=MENUITEM MOREINFO="NONE"Interface---Network interface on which you want to filter the service. Press MOREINFO="NONE"<Ins> to choose one of the router's interfaces.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"Incoming SAP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions > Press MOREINFO="NONE"<Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Exception window appears)PAGENUM=99 ID="BP106"PAGENUM=100CLASS=MENUITEM MOREINFO="NONE"Comment---Short description of the filter. You can use up to 49 characters.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"Incoming SAP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions > Press MOREINFO="NONE"<Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Exception window appears)RENDERAS="SECT2"RIP Filter ParametersIDXID="w3713"BOOK="_idx" COLLECTION="nw41" TIDREF="i3862"RIP filters restrict the exchange of RIP-based routing information between IDXID="w3714"BOOK="_idx" COLLECTION="nw41" TIDREF="i1497"
routers.RENDERAS="SECT3"Outgoing RIP Filter ParametersTo display the IDXID="w3715"BOOK="_idx" COLLECTION="nw41" TIDREF="i3152"
outgoing RIP filter parameters, complete the following steps:NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"Select CLASS=MENUITEM MOREINFO="NONE"IPX from the CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu.The CLASS=MENUITEM MOREINFO="NONE"IPX window appears.Select CLASS=MENUITEM MOREINFO="NONE"Outgoing RIP Filters.The CLASS=MENUITEM MOREINFO="NONE"Outgoing RIP Filters window appears. The outgoing RIP filter parameters are described in the sections that follow.RENDERAS="SECT4"StatusEnables or disables outgoing RIP filters.Options: Enabled, DisabledDefault: DisabledUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing RIP FiltersPAGENUM=100 ID="BP107"PAGENUM=101RENDERAS="SECT4"ActionSpecifies what to do with an outgoing network (RIP packet) that appears in the CLASS=MENUITEM MOREINFO="NONE"Filter list.Options: Permit Networks in Filter List, Deny Networks in Filter ListDefault: Permit Networks in Filter ListUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing RIP FiltersRENDERAS="SECT4"FiltersSpecifies which outgoing network numbers are sent (permitted) or filtered (denied) on an interface.Select this parameter to see the list of network numbers.MARK=BULLETTo delete a network number from the list, select it, then press MOREINFO="NONE"<Delete>.To change a network number in the list, select it, then press MOREINFO="NONE"<Enter>.To add a network number to the list, press MOREINFO="NONE"<Ins>.A new window displays the following parameters:MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Network Number---Four-byte hexadecimal number that identifies the IPX network.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing RIP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Filters > Press MOREINFO="NONE"<Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Filter window appears)CLASS=MENUITEM MOREINFO="NONE"Network Mask---Four-byte hexadecimal number that defines the range of network numbers you want to filter.A network number/mask pair of 0/0 matches all IPX networks.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing RIP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Filters > Press MOREINFO="NONE"<Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Filter window appears)PAGENUM=102 ID="BP108"CLASS=MENUITEM MOREINFO="NONE"Interface---Network interface on which you want to filter the network number. Press MOREINFO="NONE"<Ins> to choose one of the router's interfaces.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing RIP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Filters > Press MOREINFO="NONE"<Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Filter window appears)CLASS=MENUITEM MOREINFO="NONE"Comment---Short description of the filter. You can use up to 49 characters.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing RIP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Filters > Press MOREINFO="NONE"<Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Filter window appears)RENDERAS="SECT4"ExceptionsLists outgoing network numbers to which the action---permit or deny---does not apply. These are the exceptions to the CLASS=MENUITEM MOREINFO="NONE"Filter list.Select this parameter to see the list of network filters.MARK=BULLETTo delete a network filter from the list, select it, then press MOREINFO="NONE"<Delete>.To modify a network filter already in the list, select it, then press MOREINFO="NONE"<Enter>.To add a network filter to the list, press MOREINFO="NONE"<Ins>.A new window displays the following parameters:MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Network Number---Four-byte hexadecimal number that identifies the IPX network.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing RIP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions > Press MOREINFO="NONE"<Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Exception window appears)CLASS=MENUITEM MOREINFO="NONE"Network Mask---Four-byte hexadecimal number that defines the range of network numbers you want to filter.A network number/mask pair of 0/0 matches all IPX networks.PAGENUM=102 ID="BP109"PAGENUM=103Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing RIP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions > Press MOREINFO="NONE"<Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Exception window appears)CLASS=MENUITEM MOREINFO="NONE"Interface---Network interface on which you want to filter the network number. Press MOREINFO="NONE"<Ins> to choose one of the router's interfaces.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing RIP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions > Press MOREINFO="NONE"<Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Exception window appears)CLASS=MENUITEM MOREINFO="NONE"Comment---Short description of the filter. You can use up to 49 characters.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing RIP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions > Press MOREINFO="NONE"<Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Exception window appears)RENDERAS="SECT3"Incoming RIP Filter ParametersTo display the IDXID="w3716"BOOK="_idx" COLLECTION="nw41" TIDREF="i1776"
incoming RIP filter parameters, complete the following steps:NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"Select CLASS=MENUITEM MOREINFO="NONE"IPX from the CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu.The CLASS=MENUITEM MOREINFO="NONE"IPX window appears.Select CLASS=MENUITEM MOREINFO="NONE"Incoming RIP Filters.The CLASS=MENUITEM MOREINFO="NONE"Incoming RIP Filters window appears. The incoming RIP filter parameters are described in the sections that follow.RENDERAS="SECT4"StatusEnables or disables incoming RIP filters.Options: Enabled, DisabledDefault: DisabledUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"Incoming RIP FiltersPAGENUM=104 ID="BP110"RENDERAS="SECT4"ActionSpecifies what to do with an incoming network (RIP packet) that appears in the CLASS=MENUITEM MOREINFO="NONE"Filter list.Options: Permit Networks in Filter List, Deny Networks in Filter ListDefault: Permit Networks in Filter ListUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"Incoming RIP FiltersRENDERAS="SECT4"FiltersSpecifies which incoming network numbers are sent (permitted) or filtered (denied) on an interface.Select this parameter to see the list of network filters.MARK=BULLETTo delete a network filter from the list, select it, then press MOREINFO="NONE"<Delete>.To modify a network filter in the list, select it, then press MOREINFO="NONE"<Enter>.To add a network filter to the list, press MOREINFO="NONE"<Ins>.A new window displays the following parameters:MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Network Number---Four-byte hexadecimal number that identifies the IPX network.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"Incoming RIP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Filters > Press MOREINFO="NONE"<Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Filter window appears)CLASS=MENUITEM MOREINFO="NONE"Network Mask---Four-byte hexadecimal number that defines the range of network numbers you want to filter.A network number/mask pair of 0/0 matches all IPX networks.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"Incoming RIP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Filters > Press MOREINFO="NONE"<Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Filter window appears)PAGENUM=105 ID="BP111"CLASS=MENUITEM MOREINFO="NONE"Interface---Network interface on which you want to filter the network number. Press MOREINFO="NONE"<Ins> to choose one of the router's interfaces.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"Incoming RIP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Filters > Press MOREINFO="NONE"<Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Filter window appears)CLASS=MENUITEM MOREINFO="NONE"Comment---Short description of the filter. You can use up to 49 characters.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"Incoming RIP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Filters > Press MOREINFO="NONE"<Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Filter window appears)RENDERAS="SECT4"ExceptionsLists incoming network numbers to which the action---permit or deny---does not apply. These are the exceptions to the CLASS=MENUITEM MOREINFO="NONE"Filter list.Select this parameter to see the list of network filters.MARK=BULLETTo delete a network filter from the list, select it, then press MOREINFO="NONE"<Delete>.To modify a network filter in the list, select it, then press MOREINFO="NONE"<Enter>.To add a network filter to the list, press MOREINFO="NONE"<Ins>.A new window displays the following parameters:MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Network Number---Four-byte hexadecimal number that identifies the IPX network.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"Incoming RIP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions > Press MOREINFO="NONE"<Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Exception window appears)CLASS=MENUITEM MOREINFO="NONE"Network Mask---Four-byte hexadecimal number that defines the range of network numbers you want to filter.A network number/mask pair of 0/0 matches all IPX networks.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"Incoming RIP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions > Press MOREINFO="NONE"<Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Exception window appears)PAGENUM=106 ID="BP112"CLASS=MENUITEM MOREINFO="NONE"Interface---Network interface on which you want to filter the network number. Press MOREINFO="NONE"<Ins> to choose one of the router's interfaces.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"Incoming RIP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions > Press MOREINFO="NONE"<Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Exception window appears)CLASS=MENUITEM MOREINFO="NONE"Comment---Short description of the filter. You can use up to 49 characters.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"Incoming RIP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions > Press MOREINFO="NONE"<Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Exception window appears)RENDERAS="SECT2"NetBIOS Broadcast Filter ParametersIDXID="w3717"BOOK="_idx" COLLECTION="nw41" TIDREF="i2647"NetBIOS broadcast filters restrict the propagation of NetBIOS packets through the router's interfaces. To display the NetBIOS broadcast filter parameters, complete the following steps:NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"IDXID="w3718"BOOK="_idx" COLLECTION="nw41" TIDREF="i1497"
Select CLASS=MENUITEM MOREINFO="NONE"IPX from the CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu.The CLASS=MENUITEM MOREINFO="NONE"IPX window appears.Select CLASS=MENUITEM MOREINFO="NONE"NetBIOS and Packet Forwarding Filters.The CLASS=MENUITEM MOREINFO="NONE"NetBIOS and Packet Forwarding Filters window appears.The NetBIOS broadcast filter parameters are described in the sections that follow.If you configure NetBIOS packet filters, be aware of the following interactions between these filters and the CLASS=MENUITEM MOREINFO="NONE"Advanced Packet Type 20 Flooding parameter:MARK=BULLETSetting CLASS=MENUITEM MOREINFO="NONE"Advanced Packet Type 20 Flooding to CLASS=MENUITEM MOREINFO="NONE"Disabled overrides the effect of NetBIOS packet filters operating on any network interface.Conversely, the action of NetBIOS packet filters on any network interface overrides the effect of enabling the CLASS=MENUITEM MOREINFO="NONE"Advanced Packet Type 20 Flooding parameter.For more information about this parameter, see IDREF="FM55885""Advanced Packet Type 20 Flooding."PAGENUM=107 ID="BP113"RENDERAS="SECT3"StatusEnables or disables NetBIOS broadcast filtering.Options: Enabled, DisabledDefault: DisabledUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"NetBIOS and Packet Forwarding FiltersRENDERAS="SECT3"ActionSpecifies whether to propagate (permit) or filter (deny) NetBIOS packets on any of the router's interfaces in the CLASS=MENUITEM MOREINFO="NONE"Interfaces list.Options: Deny NetBIOS Packets on Listed Interfaces, Permit NetBIOS Packets on Listed InterfacesDefault: Deny NetBIOS Packets on Listed InterfacesUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"NetBIOS and Packet Forwarding FiltersRENDERAS="SECT3"InterfacesSpecifies the interfaces on which NetBIOS packets are permitted or denied.Select this parameter to see the list of interfaces.MARK=BULLETTo delete an interface from the list, select it, then press MOREINFO="NONE"<Delete>.To modify an interface already in the list, select it, then press MOREINFO="NONE"<Enter>.To add an interface to the list, press MOREINFO="NONE"<Ins>.PAGENUM=107 ID="BP114"PAGENUM=108Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"NetBIOS and Packet Forwarding FiltersRENDERAS="SECT2"Packet Forwarding Filter ParametersIDXID="w3719"BOOK="_idx" COLLECTION="nw41" TIDREF="i3175"Packet forwarding filters restrict the propagation of IPX packets passing through the router. To display the CLASS=MENUITEM MOREINFO="NONE"Packet Forwarding Filter parameters, complete the following steps:NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"IDXID="w3720"BOOK="_idx" COLLECTION="nw41" TIDREF="i1497"
Select CLASS=MENUITEM MOREINFO="NONE"IPX from the CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu.The CLASS=MENUITEM MOREINFO="NONE"IPX window appears.Select CLASS=MENUITEM MOREINFO="NONE"NetBIOS and Packet Forwarding Filters.The CLASS=MENUITEM MOREINFO="NONE"NetBIOS and Packet Forwarding Filters window appears.The CLASS=MENUITEM MOREINFO="NONE"Packet Forwarding Filter parameters are described in the sections that follow.RENDERAS="SECT3"StatusEnables or disables IPX packet filtering.Options: Enabled, DisabledDefault: DisabledUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"NetBIOS and Packet Forwarding FiltersPAGENUM=108 ID="BP115"PAGENUM=109RENDERAS="SECT3"ActionSpecifies whether to forward (permit) or filter (deny) IPX packets named in the CLASS=MENUITEM MOREINFO="NONE"Filter list.Options: Deny Packets in Filter List, Permit Packets in Filter ListDefault: Deny Packets in Filter ListUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"NetBIOS and Packet Forwarding FiltersRENDERAS="SECT3"FiltersSpecifies which IPX packet types are forwarded (permitted) or filtered (denied) on an interface, a network, or an individual node.Select this parameter to see the list of IPX packet types.MARK=BULLETTo delete an entry from the list, select it, then press MOREINFO="NONE"<Delete>.To modify an entry in the list, select it, then press MOREINFO="NONE"<Enter>.To add an entry to the list, press MOREINFO="NONE"<Ins>.A new window displays the following parameters:MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Source Type---Where an (incoming) IPX packet originated, which can be from one of the router's interfaces, an IPX network, or a node.Options: Interface, Network, NodeDefault: InterfaceUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"NetBIOS and Packet Forwarding Filters > Select CLASS=MENUITEM MOREINFO="NONE"Filters > Press MOREINFO="NONE"<Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Filter window appears)PAGENUM=109 ID="BP116"PAGENUM=110CLASS=MENUITEM MOREINFO="NONE"Source---Interface, network, or node. Press MOREINFO="NONE"<Ins> to specify the source.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"NetBIOS and Packet Forwarding Filters > Select CLASS=MENUITEM MOREINFO="NONE"Filters > Press MOREINFO="NONE"<Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Filter window appears)CLASS=MENUITEM MOREINFO="NONE"Packet Description---Type of IPX packet you can filter, such as diagnostic packets (0x0456) or file service packets (0x0451). Press MOREINFO="NONE"<Ins> to see the list of available packet types; press MOREINFO="NONE"<Enter> to select one.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"NetBIOS and Packet Forwarding Filters > Select CLASS=MENUITEM MOREINFO="NONE"Filters > Press MOREINFO="NONE"<Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Filter window appears)CLASS=MENUITEM MOREINFO="NONE"Destination Type---Where an (outgoing) IPX packet is destined, which can be through one of the router's interfaces or to an IPX network or node.Options: Interface, Network, NodeDefault: InterfaceUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"NetBIOS and Packet Forwarding Filters > Select CLASS=MENUITEM MOREINFO="NONE"Filters > Press MOREINFO="NONE"<Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Filter window appears)CLASS=MENUITEM MOREINFO="NONE"Destination---Interface, network, or node. Press MOREINFO="NONE"<Ins> to specify the destination.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"NetBIOS and Packet Forwarding Filters > Select CLASS=MENUITEM MOREINFO="NONE"Filters > Press MOREINFO="NONE"<Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Filter window appears)CLASS=MENUITEM MOREINFO="NONE"Comment---Short description of the packet filter. You can use up to 49 characters.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"NetBIOS and Packet Forwarding Filters > Select CLASS=MENUITEM MOREINFO="NONE"Filters > Press MOREINFO="NONE"<Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Filter window appears)PAGENUM=111 ID="BP117"RENDERAS="SECT3"ExceptionsLists IPX packet types to which the action---permit or deny---does not apply. These are the exceptions to the CLASS=MENUITEM MOREINFO="NONE"Filter list.Select this parameter to see the list of IPX packet types.MARK=BULLETTo delete an entry from the list, select it, then press MOREINFO="NONE"<Delete>.To modify an entry in the list, select it, then press MOREINFO="NONE"<Enter>.To add an entry to the list, press MOREINFO="NONE"<Ins>.A new window displays the following parameters:MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Source Type---Where an (incoming) IPX packet originated, which can be from one of the router's interfaces, an IPX network, or a node.Options: Interface, Network, NodeDefault: InterfaceUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"NetBIOS and Packet Forwarding Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions > Press MOREINFO="NONE"<Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Exception window appears)CLASS=MENUITEM MOREINFO="NONE"Source---Interface, network, or node. Press MOREINFO="NONE"<Ins> to specify the source.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"NetBIOS and Packet Forwarding Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions > Press MOREINFO="NONE"<Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Exception window appears)CLASS=MENUITEM MOREINFO="NONE"Packet Description---Type of IPX packet you can filter, such as diagnostic packets (0x0456) or file service packets (0x0451). Press MOREINFO="NONE"<Ins> to see the list of available packet types; press MOREINFO="NONE"<Enter> to select one.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"NetBIOS and Packet Forwarding Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions > Press MOREINFO="NONE"<Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Exception window appears)PAGENUM=112 ID="BP118"CLASS=MENUITEM MOREINFO="NONE"Destination Type---Where an (outgoing) IPX packet is destined, which can be through one of the router's interfaces or to an IPX network or node.Options: Interface, Network, NodeDefault: InterfaceUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"NetBIOS and Packet Forwarding Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions > Press MOREINFO="NONE"<Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Exception window appears)CLASS=MENUITEM MOREINFO="NONE"Destination---Interface, network, or node. Press MOREINFO="NONE"<Ins> to specify the destination.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"NetBIOS and Packet Forwarding Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions > Press MOREINFO="NONE"<Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Exception window appears)CLASS=MENUITEM MOREINFO="NONE"Comment---Short description of the packet filter. You can use up to 49 characters.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"NetBIOS and Packet Forwarding Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions > Press MOREINFO="NONE"<Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Exception window appears)PAGENUM=113 ID="BP119"GlossaryID="FM45325"adjacencyThe record that an NLSP router keeps about the state of its connection with a neighbor, and about the attributes of that neighbor. See also IDREF="FM66415"neighbor.advertisingThe process by which devices on a network inform other devices on the network of their existence. NetWare uses the Service Advertising Protocol (SAP) to do this.areaSee IDREF="FM90443"routing area.area addressThe area network number and mask that together define an NLSP routing area. See also IDREF="FM23208"area mask.ID="FM23208"area maskA 32-bit hexadecimal number that indicates how much of an area network number identifies a routing area, and how much identifies a network within the routing area. A typical area mask is FFFFFF00.ID="FM12042"broadcast(Noun) A transmission method by which all hosts on a network receive a copy of any frame that is designated for broadcast. (Verb) The act of sending a message to all nodes. Contrast with IDREF="FM78289"multicast.checksumThe numeric computation that combines the bits of a transmitted message; also, the resulting value. The value is transmitted with the message; the receiver recalculates the checksum and compares it to the received value to detect transmission errors. See also IDREF="FM81640"CRC (Cyclic Redundancy Check).circuitIn the context of NLSP, an internal logical representation of network connectivity between two NLSP routers.costA metric assigned to a circuit that determines the likelihood of traffic being routed over that circuit.ID="FM81640"CRC (Cyclic Redundancy Check)A sophisticated checksum algorithm that detects errors. It uses a complex mathematical formula that employs division and addition.ID="FM27735"Data-Link layerThe second of seven layers of the Open Systems Interconnection (OSI) Reference Model. It is involved in both packaging and addressing information and controlling the flow of separate transmissions over communication lines.delayThe time, in microseconds, to send a byte of data from one system to another.ID="FM85927"Designated RouterThe NLSP router responsible for exchanges of link state information on behalf of all other NLSP routers on the same LAN. See also IDREF="FM92617"pseudonode.distance vector algorithmThe class of routing algorithms that periodically broadcast routing information rather than sending information only when a change occurs in a route. Routers using the distance vector algorithm periodically exchange information about accessible networks with their immediate neighbors. Each node on the network consolidates the information it receives and passes it on to other routers, servers, and end nodes.distance vector protocolA protocol that derives best-path information from the best-path information present in adjacent nodes. IP RIP, IPX RIP, and Routing Table Maintenance Protocol (RTMP---an AppleTalk routing protocol) are examples of distance vector protocols.domainSee IDREF="FM31406"routing domain.FDDI (Fiber Distributed Data Interface)The ANSI standard for high-speed (100 Mbps) fiber-optic connections.filterThe process on a router that selectively discards packets of a certain type, or packets originating from or destined for a certain location. See IDREF="FM39857"service information filter; IDREF="FM15429"routing information filter.frameThe data unit used for Data Link-level communication between two nodes on a network.hierarchical addressingAn addressing scheme whereby a network is partitioned into sections, with the section identifier forming one part of each destination address, and the destination identifier forming another. This allows destination identifiers---such as server names---to be reused in different sections, because the section identifier distinguishes them. There can be more than one level of section.ID="FM74381"hopA measure of distance, in routers, on a network. The number of hops to a destination network is the number of routers that must be traversed to reach the network. The number of hops is part of each network entry in a RIP packet. See also IDREF="FM98226"RIP (Routing Information Protocol); IDREF="FM66278"tick.hop countThe routing metric used to measure the distance between a source and a destination; each hop equals the transmission of a packet across one router.ID="FM78795"internetworkAny interconnected group of networks, such as an interconnected group of AppleTalk networks. Network users in an internetwork can share information and network devices. See also IDREF="FM66879"network.Internetworking Configuration (INETCFG) utilitySee IDREF="FM39468"INETCFG (Internetworking Configuration utility).ID="FM39468"INETCFG (Internetworking Configuration utility)A menu-based NetWare Loadable ModuleTM (NLMTM) file that simplifies the installation of Novell internetworking products by allowing a network administrator to configure interface boards and network protocols. INETCFG enables network administrators to bind protocols to different LAN and WAN boards, and also to view the entire or selected portions of the configuration.IP (Internet Protocol)A TCP/IP protocol that provides datagram delivery of messages.IPX (Internetwork Packet Exchange)A NetWare protocol similar to the Xerox Network Systems (XNS) protocol, providing datagram delivery of messages.IPX addressAn address comprising a four-byte network number, a six-byte node number, and a two-byte socket number. The network number is assigned to each LAN segment, server, or router. The node number identifies a specific system, and is typically the number assigned by the manufacturer or the network interface device. The socket number distinguishes processes within the same computer. IS-IS (Intermediate System-to-Intermediate System)The Open Systems Interconnection (OSI) routing protocol by which intermediate systems exchange routing information. IS-IS is a link state routing protocol.LAN (local area network)A group of computers and other devices connected by a communications link that allows any device to interact with any other device on the network.ID="FM78713"level 1 routingThe interaction of routers within the same routing area. See also IDREF="FM90443"routing area.ID="FM93519"level 2 routingRouting between areas to form a routing domain controlled by a single administrative unit (for example, communications) within an organization. See also IDREF="FM31406"routing domain.level 3 routingRouting between routing domains controlled by different administrative units---for example, communications between different companies or academic organizations.linkIn the context of NLSP running on a LAN, a pointer to a Designated Router pseudonode. See also IDREF="FM85927"Designated Router; IDREF="FM92617"pseudonode.load balancingA scheme for distributing network traffic among parallel paths. It provides redundancy while using the available bandwidth efficiently.ID="FM42184"LSP (Link State Packet)A packet generated by an NLSP router that lists the router's neighbors and attached IPX networks.link state protocolA type of routing protocol in which each router floods information on the state of its links (network attachments) to all nodes in the internetwork. This approach reduces routing loops and network traffic but has greater memory requirements than the distance vector algorithm. NLSP, OSPF, and IS-IS are examples of link state protocols.ID="FM24127"MAC (media access control)The Data-Link layer protocol that governs access to transmission media.Maximum Transmission Unit (MTU)See IDREF="FM75572"MTU (Maximum Transmission Unit).media access controlSee IDREF="FM24127"MAC (media access control).ID="FM75572"MTU (Maximum Transmission Unit)The largest packet size, in bytes, that can be sent on a given physical network medium. For example, the MTU for Ethernet is 1500 bytes.ID="FM78289"multicastA transmission method where only those devices listening for a specified multicast packet address accept the routing information packet. Contrast with IDREF="FM12042"broadcast.ID="FM66415"neighborAn NLSP router that can form an adjacency with another NLSP router. Two NLSP routers are considered neighbors when they can communicate directly---that is, without the aid of an intermediate router. See also IDREF="FM45325"adjacency.NetBIOS (Network Basic Input/Output System)An application program interface typically used on LANs comprising IBM and compatible microcomputers. NetBIOS separates application programs from the networking subsystem, so that application program implementers can support multiple network designs, and a network system can support independently developed applications.NetWareThe Novell network operating system that provides the ability to share services across dissimilar platforms. It uses the NetWare Core Protocol (NCP), Internetwork Packet Exchange (IPX), and Sequenced Packet Exchange (SPX) protocols transparently.NetWare Loadable ModuleSee IDREF="FM16224"NLM (NetWare Loadable Module).ID="FM66879"networkA collection of interconnected, individually controlled computers, together with the hardware and software used to connect them. See also IDREF="FM78795"internetwork.network addressA Network-layer address that refers to a logical network device. Also known as a protocol address.Network layerThe third layer of the OSI Reference Model. Network-layer protocols send information over several hops to its intended destination and manage the differences between network media so that higher-layer protocols need not account for the distinctions.ID="FM16224"NLM (NetWare Loadable Module)An application or driver that resides on a NetWare server; it provides additional resource management capabilities.NLSP (NetWare Link Services Protocol)The link state protocol used by IPX routers and servers to share information about their routes with other devices on the network. NLSP enables network managers to interconnect small or large IPX networks without routing inefficiencies.OSI (Open Systems Interconnection) model A seven-layer model for data communication.packetA group of bits transmitted as a unit of information on a network. These bits include data and control elements. The control elements include the addresses of the packet's source and destination and, in some cases, error-control information. packet forwardingThe act of copying a packet from one interface to another through an intermediate system.ID="FM92617"pseudonodeA fictitious NLSP router that represents an entire LAN in the link state database. The Designated Router represents the pseudonode for Link State Packet (LSP) exchanges. See also IDREF="FM85927"Designated Router; IDREF="FM42184"LSP (Link State Packet).ID="FM98226"RIP (Routing Information Protocol)A distance vector protocol that provides a measure of distance, or hops, from a transmitting system to a receiving system.ID="FM90443"routing areaAn administrative domain of connected IPX networks all having the same area address. Users in a routing area have Network-layer access to the same services. See also IDREF="FM78713"level 1 routing.ID="FM31406"routing domainA collection of routing areas joined by level 2 routers. A 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. See also IDREF="FM93519"level 2 routing; IDREF="FM90443"routing area.ID="FM15429"routing information filterA type of filter that restricts the exchange of routing information between routers. These filters increase security by limiting the visibility of selected networks and reduce the network bandwidth consumed by the periodic exchange of routing information between routers.Routing Information TableIn the context of RIP, a table stored in an IPX RIP router that contains network numbers, routes to a particular destination network, and metrics---such as hops and ticks---associated with those routes. The router uses this information to forward packets to their destination by the best possible route. See also IDREF="FM74381"hop; IDREF="FM66278"tick.routing protocolA protocol that enables routing through the implementation of a specific routing algorithm. Examples of routing protocols include RIP, OSPF, NLSP, and IS-IS.ID="FM14203"SAP (Service Advertising Protocol)A Novell protocol that disseminates information about network services and their addresses to all nodes in an IPX network.segmentA LAN with no routers or bridges.Service Advertising ProtocolSee IDREF="FM14203"SAP (Service Advertising Protocol).ID="FM39857"service information filterA type of filter that restricts service access by filtering out the packets that advertise the services. These filters keep applications from discovering the location of services, but do not restrict access to services if applications know the locations of the services.SNMP (Simple Network Management Protocol)A network management protocol used with various network protocols, such as IPX and IP.split horizon (split-horizon routing)A routing technique by which a router does not advertise routes it learns from an interface out through the same interface, because neighboring routers reachable through that interface know the information already. Distance vector routing protocols typically use split horizon to reduce routing traffic on the network.static routingA method of updating entries in a routing table manually.System IDA unique, six-byte hexadecimal number that identifies an NLSP router.throughputThe total amount of useful information processed or communicated during a specific time period.ID="FM66278"tickThe time delay to reach a network. The number of ticks is part of each network entry in a RIP packet. A tick is about 1/18 of a second. (There are 18.21 ticks in a second.) See also IDREF="FM98226"RIP (Routing Information Protocol).tunneling The process of encapsulating and de-encapsulating one protocol in another. In IPX, the process by which a router running the IPTUNNEL or IPRELAY driver encapsulates IPX packets in UDP/IP packets and sends them across a TCP/IP internetwork to another router running IPTUNNEL or IPRELAY. The router then removes the IP and UDP headers from the packets and forwards them, like other IPX packets, to their destination IPX network.WAN (Wide Area Network)A network that transmits over large geographic areas using lines provided by a common carrier of private telecommunications facilities.workstationA node through which a user can access a server or other nodes. 