#EDIR DATA#
DOCTYPE='BOOK' PUBLICID='' SYSTEMID='/dtd/docbook.dtd'Advanced Protocol Configuration and Management GuideAdvanced Protocol Configuration and Management GuideNovell, Inc.DisclaimerNovell, Inc. makes no representations or warranties with
respect to the contents or use of this manual, and specifically
disclaims any express or implied warranties of merchantability or
fitness for any particular purpose. Further, Novell, Inc. reserves the
right to revise this publication and to make changes to its content,
at any time, without obligation to notify any person or entity of such
revisions or changes.Further, Novell, Inc. makes no representations or warranties
with respect to any NetWare software, and specifically disclaims any
express or implied warranties of merchantability or fitness for any
particular purpose. Further, Novell, Inc. reserves the right to make
changes to any and all parts of NetWare software, at any time, without
any obligation to notify any person or entity of such changes.TrademarksThe following are registered trademarks of Novell, Inc.: DR DOS, Fastpath, LAN WorkPlace, LANalyzer, NetWare, NetWare Name Service, Novell Press, UnixWare, WordPerfect.UNIX is a registered trademark of Novell, Inc. in the United States and other countries, licensed exclusively through X/Open Company, Ltd.The following are trademarks of Novell, Inc.: Advanced NetWare, Enterprise Certified NetWare Engineer, ECNE, EXOS, FirstMail, Global MHS, HSM, Hardware Specific Module, Hot Fix, IPX, IPX/SPX, IPXWAN, Internetwork Packet Exchange, LSL, Link Support Layer, MLI, MLID, MSL, MSM, MacIPX, MacNCP, MacNDS, Media Support Module, Mirrored Server Link, Multiple Link Interface, Multiple Link Interface Driver, NCP, NDR, NDS, NE/2, NE/2-32, NE1000, NE1500T, NE2000, NE2100, NE3200, NE32HUB, NLM, NLSP, NMS, NSE Pro, NTR2000, NVT, NetSync, NetWare 3, NetWare 4, NetWare 4.01, NetWare 4.1, NetWare Application Notes, NetWare Care, NetWare Client, NetWare Core Protocol, NetWare DOS Requester, NetWare Directory Services, NetWare Express, NetWare IPX Router, NetWare Link Services Protocol, NetWare Link/Frame Relay, NetWare Link/PPP, NetWare Link/X.25, NetWare Loadable Module, NetWare Logotype (teeth logo), NetWare MHS, NetWare Management Agent, NetWare Management System, NetWare Message Handling Service, NetWare MultiProtocol Router, NetWare Navigator, NetWare Peripheral Architecture, NetWare Ready, NetWare Requester, NetWare Runtime, NetWare SFT, NetWare SFT III, NetWare Tools, NetWare UAM, NetWare/IP, Netware Notify, Network Support Encyclopedia Professional Volume, Novell Labs, Novell Research Reports, Novell Virtual Terminal, ODI, Open Data-Link Interface, Packet Burst, Personal NetWare, RX-Net, RXNet/2, Red Box, SFT, SFT III, SMS, SPX, Sequenced Packet Exchange, Storage Management Services, Streams, TSM, Topology Specific Module, Transaction Tracking System, TTS, VLM, Virtual Loadable Module, "Yes, It Runs With NetWare Logo", and the "Yes, NetWare Tested and Approved Logo".The following are registered service marks of Novell, Inc.: Novell Technology Institute, NetWire.The following are service marks of Novell, Inc.: Novell Registry, Certified NetWare Administrator, CNA, Certified NetWare Engineer, CNE, Certified NetWare Instructor, CNI, Novell Authorized Service Center, NASC, Novell Technical Support.The following are collective marks of Novell, Inc.: Novell Authorized Reseller, Technical Support Alliance, TSA.3Com, 3+Share, and TokenLink are registered trademarks of 3Com Corporation.4.3BSD is a trademark of the Regents of University of California, Berkeley.ARCnet is a registered trademark of Datapoint Corporation.AT is a registered trademark of International Business Machines Corporation.AT&T is a registered trademark of American Telephone & Telegraph.Adobe and PostScript are registered trademarks of Adobe Systems Incorporated.Apple, AppleShare, AppleTalk, EtherTalk, ImageWriter, LaserWriter, LocalTalk, Macintosh, and MultiFinder are registered trademarks, and Finder and Mac are trademarks, of Apple Computer, Inc.Btrieve is a registered trademark of Btrieve Technologies, Inc.Canon is a registered trademark of Canon, Inc.COMPAQ is a registered trademark of COMPAQ Computer Corporation.Cisco Systems is a trademark of Cisco Systems, Inc.Citizen is a registered trademark of Tokei Kabushiki Kaisha.Claris is a trademark and MacWrite is a registered trademark of Claris Corporation.CompuServe is a registered trademark of CompuServe, Inc.DEC, DECnet, and Digital are trademarks of Digital Equipment Corporation.DeskJet, DeskWriter, LaserJet, PaintJet, PaintWriter, and PCL are registered trademarks of Hewlett-Packard Company.Diablo is a registered trademark of Xerox Corporation.DynaText is a registered trademark of Electronic Book Technologies, Inc.Epson is a registered trademark of Seiko Epson Corporation.EtherPrint is a trademark of 3Com Corporation.TokenPrint is a registered trademark of Dayna Communications.EtherFlex is a registered trademark of Extended Systems International.GatorBox is a registered trademark of Cayman Systems.Hewlett Packard, HP, HP-GL, LaserJet, and PCL are registered trademarks of Hewlett-Packard Company.Hayes is a registered trademark of Hayes Microcomputer Products, Inc.IBM, OS/2, Micro Channel, ProPrinter, and PS/2 are registered trademarks and AFP, Presentation Manager, and SAA are trademarks of International Business Machines Corporation.Intel is a registered trademark and Pentium is a trademark of Intel Corporation.LaserBridge is a registered trademark of Sonic Systems.Lotus is a registered trademark of Lotus Development Corporation.MS-DOS and Microsoft are registered trademarks and LAN Manager is a trademark of Microsoft Corporation.MacPlot is a registered trademark of Microspot.NEC, Spinwriter, and Pinwriter are registered trademarks of NEC Corporation.NFS is a registered trademark of Sun Microsystems, Inc.Okidata and MicroLine are registered trademarks of Oki Electric Industry Co., Ltd.PageMaker is a registered trademark of Aldus Corporation.Panasonic is a registered trademark of Panasonic Office Automation.PowerPrint is a trademark of GDT Softworks, Inc.SQL Server is a trademark of Sybase, Inc.SprintTalk is a registered trademark of Digital Products.Ultra is a trademark of Hayes Microcomputer Products, Inc.Unicode is a registered trademark of Transoft Ltd.Word is a registered trademark of Microsoft Corporation.XT is a trademark of International Business Machines Corporation.Xerox is a registered trademark and XNS is a trademark of Xerox Corporation.cc:Mail is a trademark of cc:Mail, a Division of Lotus.All other trademarks, service marks, certification marks, and
collective marks --- registered or not --- are the property of their
respective owners.Copyright Notices© Copyright 1983-1994 Novell, Inc. All rights reserved. No
part of this publication may be reproduced, photocopied, stored on a
retrieval system, or transmitted without the express written consent
of the publisher.TYPE="VERT"Novell, Inc.122 East 1700 SouthProvo, UT 84606U.S.A.User Comment FormNovell encourages and welcomes your feedback and suggestions on ways we can improve our manuals. You can help us by sharing your comments and suggestions about how our manuals could be made more useful to you, and about any inaccuracies or information gaps they contain.Submit your comments by printing this User Comment form (click on the icon to display the form, then select "Print" from the "File" menu), filling it in, then faxing or mailing it to us.LABEL="0" FLOAT="0"User Comment FormFILEREF="ucomment.tif"PAGENUM=17 ID="BP1"About This GuideThis guide provides the information you need to perform advanced configuration and management of the NetWare® 4.1 protocol software. This includes modifying the default configuration parameters to meet the specific needs of your LAN connections.This guide is written for network administrators responsible for installing and implementing network topologies.RENDERAS="SECT1"Chapter SummariesThis section briefly summarizes each chapter in this guide. Use these summaries to help you locate specific topics, or to help you decide which portions of this guide contain new information.IDREF="FM91106"Chapter 1, "Introduction to Advanced Configuration," introduces the overall concepts required to configure and manage the NetWare 4.1 protocol software.IDREF="FM71392"Chapter 2, "Configuring IPX," explains the concepts and steps required to configure and customize IPX.IDREF="FM76970"Chapter 3, "Configuring IP," explains the concepts and steps required to configure and customize TCP/IP.IDREF="FM76890"Chapter 4, "Configuring AppleTalk," explains the concepts and steps required to configure and customize AppleTalk.IDREF="FM54089"Chapter 5, "Configuring Filters," explains the concepts and steps required to configure filters for the network-layer protocols.IDREF="FM52280"Chapter 6, "Using Internetworking Utilities," discusses the usage of the internetworking utilities available for the NetWare 4.1 software.PAGENUM=18 ID="BP2"IDREF="FM59500"Chapter 7, "Monitoring LAN Connections," shows how to verify, monitor, and check the configuration and links configured with the NetWare 4.1 software.IDREF="FM70491"Chapter 8, "Configuring Communication Protocols on an SFT III Server," explains the concepts and steps for configuring a NetWare SFT IIITM server.IDREF="FM26050"Chapter 9, "Troubleshooting Overview," contains general troubleshooting information for the NetWare 4.1 software.IDREF="FM83381"Chapter 10, "Troubleshooting Network-Layer Protocols," contains troubleshooting information for each network-layer protocol.RENDERAS="SECT1"Conventions Used in This GuideThe guide uses the documentation conventions described in this section. Specifically, these conventions are used for the following:MARK=BULLETIDREF="FM70798"Parameter Paths IDREF="FM29511"TerminologyIDREF="FM80330"New Terms and Important InformationIDREF="FM58327"System Messages IDREF="FM89310"User InputIDREF="FM71150"Special CharactersIDREF="FM88636"Graphic SymbolsPAGENUM=18 ID="BP3"PAGENUM=19RENDERAS="SECT2"ID="FM70798"Parameter PathsThis guide uses a special format to show the path to a parameter. For example, rather than specifying "Load INETCFG; from the CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu, select CLASS=MENUITEM MOREINFO="NONE"Protocols; from the CLASS=MENUITEM MOREINFO="NONE"Protocol Configuration menu, select CLASS=MENUITEM MOREINFO="NONE"AppleTalk; from the CLASS=MENUITEM MOREINFO="NONE"AppleTalk Configuration menu, select CLASS=MENUITEM MOREINFO="NONE"Static Routes Configuration (the CLASS=MENUITEM MOREINFO="NONE"Configured Static Routes for On-Demand Calls menu appears); then press MOREINFO="NONE"<Insert> (the CLASS=MENUITEM MOREINFO="NONE"Static Route Configuration menu appears)," the following format is used:Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"AppleTalk > Select CLASS=MENUITEM MOREINFO="NONE"Static Routes Configuration (CLASS=MENUITEM MOREINFO="NONE"Configured 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="FM29511"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="FM80330"New Terms and Important InformationHighlighting emphasizes new terms and important information.PAGENUM=19 ID="BP4"PAGENUM=20RENDERAS="SECT2"ID="FM58327"System MessagesRegular (nonboldface, nonitalic) monospaced character strings represent system prompts or responses; for example:FORMAT="LINESPECIFIC"MOREINFO="NONE"message exampleRENDERAS="SECT2"ID="FM89310"User InputThis guide uses the following conventions to denote user input:MARK=BULLETMOREINFO="NONE"Highlighted monospaced character strings represent user input, which must be entered exactly as shown; for example:FORMAT="LINESPECIFIC"MOREINFO="NONE"MOREINFO="NONE"LOAD TCPIP MOREINFO="NONE"<Enter> or
   MOREINFO="NONE"Load tcpip MOREINFO="NONE"<Enter>Highlighted and lowercase character strings show descriptive names for items that you must replace with appropriate values. For example, in the following NetWare console command, you replace driver with the specific name of a driver:FORMAT="LINESPECIFIC"MOREINFO="NONE"UNBIND IP FROM driver MOREINFO="NONE"<Enter>RENDERAS="SECT2"ID="FM71150"Special CharactersThis guide uses special characters to denote the following:MARK=BULLETAsterisks * in text denote third-party trademarks.Angle brackets < >, brackets [ ], braces { }, vertical bar |, parenthesis ( ), and quotation marks " are used as metacharacters and, as such, you must not type these as part of user input.Angle brackets < > enclose a descriptive name for any value that is provided as output by a computer; for example:FORMAT="LINESPECIFIC"MOREINFO="NONE"Error: <IP address> is illegal.
    Must be class A, B, or C.PAGENUM=20 ID="BP5"PAGENUM=21Characters 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 IP TO board_name ADDR=ip_addr
   [MASK=mask_addr] MOREINFO="NONE"<Enter>If a command, such as the preceding one, is too long to fit on one line, it wraps to the next line; such a command must be entered after the console prompt (:) but before the end-of-line (EOL) character.Braces { } enclose multiple items separated by the vertical bar | character. You must specify only one of the items; for example:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD TCPIP [FORWARD={YES|NO}]MOREINFO="NONE"<Enter>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. PAGENUM=21 ID="BP6"PAGENUM=22RENDERAS="SECT2"ID="FM88636"Graphic SymbolsIn printed documentation, the following symbols appear in the left margin to identify different categories of information:PERFORMANCE="REQUIRED"This symbol identifies the first step of a procedure. To accomplish a specific task, follow the steps in the procedure. MARK=BOXThis symbol identifies the first step of a checklist. 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.RENDERAS="SECT1"Related Novell PublicationsSee the following Novell publications for related information:MARK=BULLETBOOK="atrefenu" COLLECTION="nw41"NetWare 4.1 AppleTalk* ReferenceBOOK="cfg1_enu" COLLECTION="nw41"NetWare 4.1 Basic Protocol Configuration GuideBOOK="ipxrtenu" COLLECTION="nw41"NetWare 4.1 IPX ReferenceBOOK="nlsp_enu" COLLECTION="nw41"NetWare 4.1 NLSP Migration GuideBOOK="tcpipenu" COLLECTION="nw41"NetWare 4.1 TCP/IP ReferenceLABEL="1"PAGENUM=1 ID="BP7"ID="FM91106"Introduction to Advanced ConfigurationThe initial configuration of the NetWare® 4.1 network protocol provides the basis for most needs. The configuration is based on the boards configured and the protocols enabled and configured.IDXID="w938"BOOK="_idx" COLLECTION="nw41" TIDREF="i1808"
If you followed the instructions in the BOOK="cfg1_enu" COLLECTION="nw41"NetWare 4.1 Basic Protocol Configuration Guide, most protocol parameters during the initial configuration are set at their default values. This configuration enables a basic server setup useful for most LAN purposes.The NetWare 4.1protocol software offers an extensive set of configurable parameters for all protocols supported. You can use these parameters to modify the default characteristics of the original configuration. You can configure the advanced features and optimize the protocol performance options. This guide presents advanced configuration concepts and procedures, and discusses the management utilities you might find useful in your particular situation. This chapter contains the following sections:MARK=BULLETIDREF="FM77786""Configuration Overview"This section describes the major tasks required to configure the protocols on a server on a LAN.IDREF="FM45501""Understanding Configuration Concepts"This section discusses the concepts to help you make the right decisions when configuring the server.IDREF="FM77585""Understanding Management"This section discusses overall protocol management tasks and explains the types of utilities to help you manage the NetWare 4.1 protocols.PAGENUM=2 ID="BP8"RENDERAS="SECT1"ID="FM77786"Configuration OverviewIDXID="w939"BOOK="_idx" COLLECTION="nw41" TIDREF="i752"
To set up a server to run on a LAN, you need to perform the following tasks using INETCFG:NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"Configure the LAN board.MARK=BULLETFor a LAN board, you only need to configure the board.For information about configuring LAN boards, refer to the BOOK="cfg1_enu" COLLECTION="nw41"NetWare 4.1 Basic Protocol Configuration Guide.Configure the network protocols that will run over the LAN connection.MARK=BULLETFor a LAN, you can configure the routing protocol (for IPXTM and TCP/IP), tunneling (for IPX and AppleTalk*), filtering, static routes (for TCP/IP only), and other expert configurations.For information about configuring the network protocols for a LAN, see IDREF="FM71392"Chapter 2, "Configuring IPX," IDREF="FM76970"Chapter 3, "Configuring IP," and IDREF="FM76890"Chapter 4, "Configuring AppleTalk."Bind the network protocols to the network interfaces through which you want them to connect.For information about binding the protocols, see IDREF="FM71392"Chapter 2, "Configuring IPX," IDREF="FM76970"Chapter 3, "Configuring IP," and IDREF="FM52280"Chapter 6, "Using Internetworking Utilities."RENDERAS="SECT1"ID="FM45501"Understanding Configuration ConceptsConfiguring the server involves some planning and decision-making along the way. You have to know the details of the network where you are placing the server, the type of connectivity you want, and the configuration details of the peers to which you are connecting the server. PAGENUM=3 ID="BP9"Deciding the characteristics of each protocol you are using over a LAN interface is based on the topography and existing characteristics of the network. For every protocol you configure to run over a LAN link you must determine whether to route and which protocol to use, whether to tunnel packets, whether you need or want to configure static routes, and the type of filtering to use.This section discusses the basic concepts you must know to make the right decisions when configuring the network protocols you want to use on NetWare 4.1 software. Each network protocol you want to support must be bound and must run over a configured link. For information about binding configuration concepts and procedures and about configuring protocols, see IDREF="FM71392"Chapter 2, "Configuring IPX," IDREF="FM76970"Chapter 3, "Configuring IP,"and IDREF="FM76890"Chapter 4, "Configuring AppleTalk."RENDERAS="SECT2"Routing ProtocolsIPX and TCP/IP configurations offer options for setting the routing protocols. There are two general types of routing protocols available: IDXID="w940"BOOK="_idx" COLLECTION="nw41" TIDREF="i3906"IDXID="w941"BOOK="_idx" COLLECTION="nw41" TIDREF="i1151"
distance vector and IDXID="w942"BOOK="_idx" COLLECTION="nw41" TIDREF="i3906"IDXID="w943"BOOK="_idx" COLLECTION="nw41" TIDREF="i2113"
link state. Your choice of routing protocols is determined largely by which routing protocols are currently used in your network. For example, in older networks, such as NetWare 2, there might be several routers that can only support distance vector routing. However, if your situation enables you to choose just one type of routing to use, choose link state routing if possible.If your network contains routers that support both link state and distance vector routing, you should configure your router to support both. In networks that have nothing but newer routers, it is best to configure the routers to use only link state routing protocols. Although this is not a very likely scenario, it might be possible to achieve by gradually updating your routers and migrating to the exclusive use of link state routing protocols over a period of time.IDREF="FM54176"Table 1-1 shows the distance vector and link state protocols that are supported by NetWare 4.1.LABEL="1-1" PGWIDE=1 TOCENTRY="1"ID="FM54176"Distance Vector and Link State ProtocolsCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="12*"COLNAME=3 COLWIDTH="11*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Network ProtocolCOLNAME=2 ROTATE="0" MOREROWS="0"Distance Vector Routing ProtocolCOLNAME=3 ROTATE="0" MOREROWS="0"Link State Routing ProtocolVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IPXCOLNAME=2 ROTATE="0" MOREROWS="0"RIPCOLNAME=3 ROTATE="0" MOREROWS="0"NLSPTM with RIP/SAP compatibility (Default)COLNAME=1 ROTATE="0" MOREROWS="0"TCP/IPCOLNAME=2 ROTATE="0" MOREROWS="0"RIP (Default)COLNAME=3 ROTATE="0" MOREROWS="0"OSPFCOLNAME=1 ROTATE="0" MOREROWS="0"AppleTalkCOLNAME=2 ROTATE="0" MOREROWS="0"RTMPCOLNAME=3 ROTATE="0" MOREROWS="0"---PAGENUM=4 ID="BP10"RENDERAS="SECT2"Permanent Links and Static RoutesIDXID="w944"BOOK="_idx" COLLECTION="nw41" TIDREF="i4270"
In TCP/IP, you can use static routes for LAN connections. You use a static route for a LAN connection if you want to eliminate routing protocol traffic over the connection, making more bandwidth available for data, or to have a backup route for dynamic routes. You can also use static routes to limit user access to one portion of the network, or to gain access to isolated areas of the network.RENDERAS="SECT2"TunnelingIDXID="w945"BOOK="_idx" COLLECTION="nw41" TIDREF="i4607"
The NetWare 4.1 software provides the IPTUNNEL driver for tunneling IPX packets through IP internetworks, and the AURP protocol to tunnel AppleTalk packets through IP internetworks. IPTUNNEL is configured as a board driver and uses UDP encapsulation to send IPX packets through an IP internetwork, to a remote IPTUNNEL peer. The remote IPTUNNEL peer then strips the UDP encapsulation and sends the IPX packet through an IPX network to its destination.Similarly, AURP encapsulates AppleTalk packets to send them through an IP internetwork to a remote AURP peer. The remote AURP peer strips the encapsulation and sends the packet through the AppleTalk network to its destination.RENDERAS="SECT2"FilteringIDXID="w946"BOOK="_idx" COLLECTION="nw41" TIDREF="i1499"
The NetWare 4.1 protocols support filtering to control the service and route information that is accepted or advertised by a server. Filters are useful when you want to limit specific types of traffic to certain parts of your network and when you want to provide a certain level of security. The Filter Configuration utility (FILTCFG) enables you to configure the filters for IPX, IP, and AppleTalk to selectively discard packets sent or received by a server. The following types of filters are supported:MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"IDXID="w947"BOOK="_idx" COLLECTION="nw41" TIDREF="i3177"IDXID="w948"BOOK="_idx" COLLECTION="nw41" TIDREF="i1503"
Packet forwarding---To prevent selected data packets from being forwarded by the server. Packet forwarding filtering is available for IPX and TCP/IP.PAGENUM=4 ID="BP11"PAGENUM=5CLASS=MENUITEM MOREINFO="NONE"IDXID="w949"BOOK="_idx" COLLECTION="nw41" TIDREF="i4076"IDXID="w950"BOOK="_idx" COLLECTION="nw41" TIDREF="i1503"
Service information---To prevent packets that advertise services destined for particular parts of the network from being advertised by the server. Service information filtering is available for IPX and AppleTalk.CLASS=MENUITEM MOREINFO="NONE"IDXID="w951"BOOK="_idx" COLLECTION="nw41" TIDREF="i3901"IDXID="w952"BOOK="_idx" COLLECTION="nw41" TIDREF="i1503"
Routing information---To limit the routes added to the routing tables of specified servers. Routing information filtering is available for IPX, AppleTalk and TCP/IP.RENDERAS="SECT1"ID="FM77585"Understanding ManagementIDXID="w953"BOOK="_idx" COLLECTION="nw41" TIDREF="i2313"
The NetWare 4.1 networking software offers multiple utilities to manage the server and its operation on the internetwork. Managing the server after it is configured consists of the following major tasks:MARK=BULLETVerifying the configuration to make sure everything is up and running and has the characteristics you intended.Monitoring the server to find out whether it is performing efficiently, and to detect possible problems.Configuring and managing connectivity equipment.Optimizing the server to make routing more efficient.Testing connectivity and troubleshooting.IDXID="w954"BOOK="_idx" COLLECTION="nw41" TIDREF="i1875"
The utilities available to help you configure and manage your server include:MARK=BULLETManagement and testing utilities, such as INETCFG, FILTCFG, or IPXPING, to configure and optimize the server.Monitoring utilities, such as IPXCON, ATCON, or TCPCON, to help you check how each protocol is behaving, and to help you identify potential problems.Command-line utilities, such as PING, CONLOG, or REINITIALIZE SYSTEM, to help you monitor, test, and implement configuration changes to your server.PAGENUM=5 ID="BP12"PAGENUM=6The advanced configuration features described in this guide include information such as configuration of low-level data-link parameters, including transmit queue limits and protocol error recovery; and optimization techniques for network protocols and LAN links.Although many optimization techniques can be used on a LAN, optimization is less of an issue on a LAN because bandwidth is inexpensive.Monitoring your server, during and after initial configuration, can help you detect potential problems and identify its optimization needs. You can also use the management utilities in conjunction to isolate problems. For information about the utilities, see IDREF="FM52280"Chapter 6, "Using Internetworking Utilities." For information about troubleshooting, refer to IDREF="FM26050"Chapter 9, "Troubleshooting Overview."LABEL="2"PAGENUM=7 ID="BP13"ID="FM71392"Configuring IPXNetWare® 4.1 software provides a set of configurable parameters with which you can modify operational characteristics of the IPXTM network protocol, such as selecting its routing protocol and configuring it to run over a LAN connection.You configure IPX by enabling the protocol, setting its various parameters, and binding it to a network interface. You configure all IPX parameters from the Internetworking Configuration utility (INETCFG).The configuration you specify using INETCFG does not take effect automatically. To activate the new configuration, exit INETCFG, then enter MOREINFO="NONE"REINITIALIZE SYSTEM at the console prompt after you finish all configuration tasks.This chapter contains the following sections:MARK=BULLETIDREF="FM36257""IPX Configuration Decisions"IDREF="FM87451""Turning off IPX Packet Forwarding"IDREF="FM70281""Configuring NLSP"IDREF="FM82769""Configuring RIP and SAP"IDREF="FM98371""Enabling Advanced IPX Parameters"IDREF="FM31348""Enabling Filters"IDREF="FM29310""Controlling the Propagation of Type 20 Packets"IDREF="FM33824""Changing the Hop Count Limit for IPX Packets"IDREF="FM86203""Balancing Traffic Loads Over Equal-Cost Routes"PAGENUM=7 ID="BP14"PAGENUM=8IDREF="FM35697""Configuring SPX Connection Parameters"IDREF="FM18623""Tunneling Through IP Networks"IDREF="FM67153""Configuring the MacIPX Gateway"RENDERAS="SECT1"ID="FM36257"IPX Configuration DecisionsIDXID="w955"BOOK="_idx" COLLECTION="nw41" TIDREF="i741"IDXID="w956"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"
How you configure IPX beyond its most basic configuration depends on the following decisions:MARK=BULLETWhether to turn off IPX packet forwarding or to use the system as an IPX router.NetWare 4.1 allows you to turn off, or disable, IDXID="w957"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"IDXID="w958"BOOK="_idx" COLLECTION="nw41" TIDREF="i3174"
IPX packet forwarding on a NetWare file server. This is useful when you have more than one NetWare system connecting two or more LANs and you want to free one of the systems from the task of forwarding IPX packets between the LANs.To turn off IPX packet forwarding, see IDREF="FM87451""Turning off IPX Packet Forwarding."Whether to use NLSP, RIP/SAP, or both, on your server.IDXID="w959"BOOK="_idx" COLLECTION="nw41" TIDREF="i2927"IDXID="w960"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"IDXID="w961"BOOK="_idx" COLLECTION="nw41" TIDREF="i3859"IDXID="w962"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"IDXID="w963"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"IDXID="w964"BOOK="_idx" COLLECTION="nw41" TIDREF="i3943"
NetWare Link Services ProtocolTM (NLSPTM) is the Novell® link state routing protocol for IPX internetworks; RIP and SAP are the routing and service advertising protocols traditionally used by NetWare.To configure NLSP on your server, see IDREF="FM70281""Configuring NLSP."To configure RIP and SAP on your server, see IDREF="FM82769""Configuring RIP and SAP."Whether to enable the advanced IPX parameters.This is a set of parameters with which you configure NLSP and other advanced features of the IPX protocol.To enable these parameters for configuration, see IDREF="FM98371""Enabling Advanced IPX Parameters."PAGENUM=9 ID="BP15"Whether to activate the route, service, or IPX or NetBIOS packet filters you configure with the Filter Configuration utility (FILTCFG).IDXID="w965"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"IDXID="w966"BOOK="_idx" COLLECTION="nw41" TIDREF="i1503"
Filters enable you to do the following:MARK=BULLETControl user access to any services.Reduce the bandwidth consumed by routing traffic.Restrict the flow of IPX or NetBIOS packets.To configure filters, you must first enable the CLASS=MENUITEM MOREINFO="NONE"Filtering Support parameter from INETCFG and then load the Filter Configuration utility (FILTCFG). For more information, see IDREF="FM54089"Chapter 5, "Configuring Filters."Whether to change how your router propagates type 20 packets.IDXID="w967"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"IDXID="w968"BOOK="_idx" COLLECTION="nw41" TIDREF="i4613"
Type 20 is an IPX packet type that refers to any propagated packet. NetBIOS packets, for example, are type 20 packets. If your router processes a lot of type 20 packets, you can control how it propagates these packets through its interfaces. This can reduce the amount of traffic on a LAN.To change how your router propagates type 20 packets, see IDREF="FM29310""Controlling the Propagation of Type 20 Packets."Whether to change the hop count limit of outbound IPX packets.IDXID="w969"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"IDXID="w970"BOOK="_idx" COLLECTION="nw41" TIDREF="i1686"
This enables you to control the range of outbound IPX packets on your router.To control the range of IPX packets, see IDREF="FM33824""Changing the Hop Count Limit for IPX Packets."Whether to balance traffic loads over equal-cost routes.IDXID="w971"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"IDXID="w972"BOOK="_idx" COLLECTION="nw41" TIDREF="i409"
If your router supports two or more network interfaces that can reach the same destination, it can distribute outbound traffic among those interfaces for an effective increase in throughput.To configure equal-cost routes, see IDREF="FM86203""Balancing Traffic Loads Over Equal-Cost Routes."PAGENUM=9 ID="BP16"PAGENUM=10Whether to configure SPX connection parameters.IDXID="w973"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"IDXID="w974"BOOK="_idx" COLLECTION="nw41" TIDREF="i4237"
You might need to configure certain Sequenced Packet ExchangeTM (SPXTM) parameters if you are running NetWare applications that have specific requirements for connection timeouts, retry counts, and so on.To configure any of these parameters, see IDREF="FM35697""Configuring SPX Connection Parameters."Whether to configure IP tunneling.IDXID="w975"BOOK="_idx" COLLECTION="nw41" TIDREF="i4607"IDXID="w976"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"
You use IP tunneling between peer routers when you want two or more IPX networks to exchange information through an Internet Protocol (IP) network.To configure IP tunneling, see IDREF="FM18623""Tunneling Through IP Networks."Whether to configure the MacIPX gateway.IDXID="w977"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"IDXID="w978"BOOK="_idx" COLLECTION="nw41" TIDREF="i2275"
You use the MacIPXTM gateway when you have Macintosh* clients on an AppleTalk* network that need to use the resources available on a NetWare LAN.To configure the MacIPX gateway, see IDREF="FM67153""Configuring the MacIPX Gateway."RENDERAS="SECT1"ID="FM87451"Turning off IPX Packet ForwardingIDXID="w979"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"IDXID="w980"BOOK="_idx" COLLECTION="nw41" TIDREF="i3174"
As a typical part of its operation, a NetWare file server forwards IPX packets between its network interfaces. By disabling the CLASS=MENUITEM MOREINFO="NONE"Packet Forwarding parameter, you turn off IPX packet forwarding on a NetWare file server. This is useful when you have more than one NetWare system on a network and you want to make more computing resources available on a server for file and print services.A server with IPX packet forwarding disabled still performs its duties as a file server, but broadcasts only its own services and internal network number---not those associated with its network interfaces. A server operating in this way is sometimes called a IDXID="w981"BOOK="_idx" COLLECTION="nw41" TIDREF="i2557"multihomed server. Although the multihomed server does not reply to routing requests from NetWare workstations, it must still accept all incoming RIP and SAP broadcasts to maintain its bindery.PAGENUM=11 ID="BP17"IDREF="FM49762"Figure 2-1 shows how the tasks of routing and file service can be divided between a NetWare file server and a dedicated router. Typically, the task of routing IPX traffic between the two internetworks would be shared by the router and the file server. When you disable IPX packet forwarding on the file server, the router assumes the task of routing all IPX traffic. The file server, now free from the tasks of forwarding IPX packets and answering route requests, can devote its full processing resources to file service.LABEL="2-1" FLOAT="0"ID="FM49762"Turning Off IPX Packet Forwarding on a NetWare File ServerFILEREF="routeoff.tif"You should turn off IPX packet forwarding only for the following reasons:MARK=BULLETYou do not want the server to forward IPX packets between its interfaces.The server is operating in a RIP-only network.Turning off IPX routing in a network that has NLSP routers forces those routers to send RIP/SAP updates to the server.PAGENUM=12 ID="BP18"RENDERAS="SECT2"How to Turn Off IPX Packet ForwardingIDXID="w982"BOOK="_idx" COLLECTION="nw41" TIDREF="i3174"IDXID="w983"BOOK="_idx" COLLECTION="nw41" TIDREF="i1943"
To turn off IPX packet forwarding, load INETCFG and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"IPX (CLASS=MENUITEM MOREINFO="NONE"IPX Protocol Configuration window appears)The CLASS=MENUITEM MOREINFO="NONE"Packet Forwarding parameter is already highlighted; select it, then select CLASS=MENUITEM MOREINFO="NONE"Disabled.Press MOREINFO="NONE"<Esc> to return to the CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu; save your change when prompted.If you want this change to take effect immediately, exit INETCFG, then type the following command:FORMAT="LINESPECIFIC"MOREINFO="NONE"REINITIALIZE SYSTEM MOREINFO="NONE"<Enter>If you want to configure other IPX parameters, do so now, then reinitialize the system when you are finished.RENDERAS="SECT1"ID="FM70281"ID="FM25099"Configuring NLSPIDXID="w984"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"IDXID="w985"BOOK="_idx" COLLECTION="nw41" TIDREF="i2927"
Novell developed NLSP to meet the demands of large IPX internetworks. As a link state routing protocol, NLSP offers better performance, reliability, and scalability than the IPX RIP routing traditionally employed by NetWare servers.Unlike RIP and SAP, which periodically broadcast routing and service information, NLSP transmits routing information only when a change occurs in a route or service somewhere in the network, or every two hours---whichever occurs first. Because NLSP generates fewer routing updates than RIP and SAP, it uses less network bandwidth to maintain its routing database.An NLSP router transmits information about its directly connected routers and the links to those routers in Link State Packets (LSPs). By default, LSPs are 512 bytes, a nominal value that is sufficient for most IPX networks. If you have a large network---on the order of 4,000 routes and 2,000 services or more---you should increase the value of the CLASS=MENUITEM MOREINFO="NONE"LSP Size parameter to 1024. To configure this parameter, see IDREF="FM70524""How to Change the LSP Size."PAGENUM=13 ID="BP19"By default, NLSP broadcasts its packets because some LAN drivers do not properly support multicast, a transmission mode that enables only those devices listening for a specific multicast packet address to accept the packet. You can, however, change the NLSP packet transmission mode to multicast with the CLASS=MENUITEM MOREINFO="NONE"MAC Channel parameter. An advantage of using multicast transmission is that NLSP packets sent by multicast do not "clutter" nonrouting nodes with unnecessary traffic.All NetWare systems on the same LAN must use the same NLSP packet transmission mode.NLSP makes large IPX internetworks more manageable by allowing you to partition them into administrative domains called routing areas. Each routing area can be identified by up to three area addresses, a unique, four-byte hexadecimal number that identifies each NLSP router as being part of a routing area. Although area addresses are not required, they are available chiefly for compatibility with future versions of NLSP and do provide some benefit for large IPX internetworks.Do not configure area addresses unless you must partition a large IPX internetwork. If you make an error in the address assignments, you can partition your network inadvertently and lose connectivity between some routers.For more information about routing areas and partitioning an IPX internetwork, refer to the BOOK="nlsp_enu" COLLECTION="nw41"NetWare 4.1 NLSP Migration Guide.Each NLSP router is identified by a unique, six-byte hexadecimal number called IDXID="w986"BOOK="_idx" COLLECTION="nw41" TIDREF="i2936"
the System ID. The default IDXID="w987"BOOK="_idx" COLLECTION="nw41" TIDREF="i4381"
System ID comprises a two-byte constant, 0x0200, followed by the router's own internal network number. You should not change the System ID unless you have another numbering scheme in place with which you can reliably track and manage the NLSP routers on your network. If you must change a router's System ID, use another unique number, such as the physical address of one of the router's network interface boards.NLSP uses a default cost value based on media throughput to choose the best route by which to forward IPX packets. NetWare 4.1 enables you to override this value on an interface. By overriding the default cost, you can establish preferred routes, balance traffic loads among interfaces, and set up specific traffic flows between routers. For more information, see IDREF="FM86203""Balancing Traffic Loads Over Equal-Cost Routes."PAGENUM=14 ID="BP20"All NLSP routers have a configurable parameter called the Priority. The router with the highest priority becomes the Designated Router, which assumes the responsibility for exchanges of link state information on behalf of all other NLSP routers on the LAN. You do not typically need to change a router's Priority value; the NLSP routers automatically "elect" one from themselves. However, if you want to force a router to become the Designated Router for its LAN, increase its Priority value to at least 85. The router you choose should be typically up and should have enough memory to process NLSP routing information and generate the pseudonode LSP for its LAN. If you want to prevent a particular router from becoming the Designated Router, decrease its Priority value.NetWare 4.1 provides a set of convergence parameters that enable you to control the operation of NLSP on your server/router. The default values for these parameters are sufficient for most IPX networks and should be changed only on the advice of your technical support representative.When configuring NLSP on an interface, you can set the CLASS=MENUITEM MOREINFO="NONE"NLSP State parameter to one of two states: CLASS=MENUITEM MOREINFO="NONE"On and CLASS=MENUITEM MOREINFO="NONE"Off. CLASS=MENUITEM MOREINFO="NONE"On enables the router to exchange NLSP packets freely with other NLSP routers on the attached network. CLASS=MENUITEM MOREINFO="NONE"Off disables NLSP routing on the interface.For additional information about how NLSP works, refer to the BOOK="ipxrtenu" COLLECTION="nw41"NetWare 4.1 IPX Reference.RENDERAS="SECT2"ID="FM52660"How to Configure NLSPIf you are planning to implement NLSP throughout an entire IPX network or even if you need to configure NLSP on just a few server or LANs, refer to the BOOK="nlsp_enu" COLLECTION="nw41"NetWare 4.1 NLSP Migration Guide.IDXID="w988"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"IDXID="w989"BOOK="_idx" COLLECTION="nw41" TIDREF="i2927"
To configure NLSP on the server, load INETCFG and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"IPX (CLASS=MENUITEM MOREINFO="NONE"IPX Protocol Configuration window appears)PAGENUM=14 ID="BP21"PAGENUM=15Complete the following steps:PERFORMANCE="REQUIRED"Select the CLASS=MENUITEM MOREINFO="NONE"Routing Protocol parameter, then select CLASS=MENUITEM MOREINFO="NONE"NLSP with RIP/SAP Compatibility.If the router supports several interfaces and you need to filter routes and services to a remote site through one of those interfaces, select 
CLASS=MENUITEM MOREINFO="NONE"NLSP with RIP/SAP Compatibility, then disable NLSP and enable RIP and SAP on that interface. To enable RIP and SAP, see 
IDREF="FM82769""Configuring RIP and SAP."If you select 
CLASS=MENUITEM MOREINFO="NONE"Expert Configuration Options, you can view the following expert NLSP parameters:
MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"NLSP Local Area AddressesCLASS=MENUITEM MOREINFO="NONE"Override NLSP System IDCLASS=MENUITEM MOREINFO="NONE"NLSP System IdentificationCLASS=MENUITEM MOREINFO="NONE"NLSP Convergence RateCLASS=MENUITEM MOREINFO="NONE"NLSP Convergence Rate ConfigurationMost network configurations do not require changes to these parameters. To learn how they are used, refer to the BOOK="ipxrtenu" COLLECTION="nw41"NetWare 4.1 IPX Reference.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to return to the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu, then select the following path: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 OptionsPERFORMANCE="REQUIRED"Configure the following parameters:
MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"NLSP State---Identifies the state of NLSP on this interface. Select one of the following options:---CLASS=MENUITEM MOREINFO="NONE"On. Enables NLSP routing on the interface.---CLASS=MENUITEM MOREINFO="NONE"Off. Disables NLSP routing on the interface.Select this option if the interface is on an area boundary, or if you need to filter incoming RIP or SAP packets at the interface.PAGENUM=15 ID="BP22"PAGENUM=16CLASS=MENUITEM MOREINFO="NONE"MAC Channel---Determines whether NLSP uses the broadcast or multicast channel to transmit its packets. If you select CLASS=MENUITEM MOREINFO="NONE"Multicast, NLSP automatically determines the multicast address. All systems on a network must be set to CLASS=MENUITEM MOREINFO="NONE"Multicast; otherwise, the systems default to CLASS=MENUITEM MOREINFO="NONE"Broadcast, the default state for this parameter.Make sure the driver you are using supports multicast transmission; drivers that do not support multicast can cause systems to become unaware of each other.The 
CLASS=MENUITEM MOREINFO="NONE"NLSP Bind Options window also includes the following parameters:
MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"MTU Override---Overrides the Maximum Transmission Unit (MTU) of the network medium to which this interface is connected. All outbound packets on this interface use the value you enter. The default value is 0, which means "use the MTU of the network medium." For example, the Ethernet MTU is 1500 bytes.Set this parameter if you have a bridge or other device on your network.CLASS=MENUITEM MOREINFO="NONE"Priority---Sets the priority of the NLSP router on the network segment to which this interface is connected. The default priority is 64; increase this value to at least 85 if you want the router to become the Designated Router for its LAN; decrease it if you want to prevent the router from becoming the Designated Router.CLASS=MENUITEM MOREINFO="NONE"Pace Override---Specifies the maximum number of NLSP packets that can be sent each second through this interface. On a LAN, the default---and maximum---pace for NLSP packets is 30 pps.The default value for this parameter is 0, which means "do not override the current pace."Because the default settings for these parameters are suitable for most NLSP networks, you should change them only for a specific purpose. Misconfiguring these parameters can increase routing traffic or cause loss of connectivity on your network. If you are unfamiliar with these parameters, refer to the BOOK="ipxrtenu" COLLECTION="nw41"NetWare 4.1 IPX Reference.The 
CLASS=MENUITEM MOREINFO="NONE"NLSP Bind Options window also includes the 
CLASS=MENUITEM MOREINFO="NONE"Cost Override parameter, which overrides the default cost of the network medium to which an interface is connected. To configure this parameter, see 
IDREF="FM86203""Balancing Traffic Loads Over Equal-Cost Routes."PAGENUM=17 ID="BP23"PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to return to the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu; save your changes when prompted.PERFORMANCE="REQUIRED"If you want these changes to take effect immediately, exit INETCFG, then type the following command:
FORMAT="LINESPECIFIC"MOREINFO="NONE"REINITIALIZE SYSTEM MOREINFO="NONE"<Enter>If you want to configure other IPX parameters, do so now, then reinitialize the system when you are finished.RENDERAS="SECT2"ID="FM70524"How to Change the LSP SizeIDXID="w990"BOOK="_idx" COLLECTION="nw41" TIDREF="i2927"IDXID="w991"BOOK="_idx" COLLECTION="nw41" TIDREF="i2248"
The larger the packet a network can carry, the fewer LSPs are required to propagate a router's link state information on that network. However, the LSP must be no larger than the largest frame size supported by the network, less 30 bytes for the IPX header. For example, an ARCNET* LAN can transmit no more than 576 bytes at a time. If you set CLASS=MENUITEM MOREINFO="NONE"LSP Size to 1024, the LSP cannot be transmitted across the LAN because it is too large. This prevents the network from converging.To change the size of the LSP that a router transmits, load INETCFG and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"Expert Configuration OptionsSelect the CLASS=MENUITEM MOREINFO="NONE"LSP Size parameter, enter a value between 128 and 4096, then press MOREINFO="NONE"<Enter>.Press MOREINFO="NONE"<Esc> to return to the CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu; save your change when prompted.If you want this change to take effect immediately, exit INETCFG, then type the following command:FORMAT="LINESPECIFIC"MOREINFO="NONE"REINITIALIZE SYSTEM MOREINFO="NONE"<Enter>If you want to configure other IPX parameters, do so now, then reinitialize the system when you are finished.PAGENUM=18 ID="BP24"RENDERAS="SECT1"ID="FM82769"Configuring RIP and SAPIDXID="w992"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"IDXID="w993"BOOK="_idx" COLLECTION="nw41" TIDREF="i3859"IDXID="w994"BOOK="_idx" COLLECTION="nw41" TIDREF="i3943"IDXID="w995"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"
RIP and SAP are the routing and service advertising protocols traditionally used by NetWare systems to exchange route and service information on an IPX network. RIP is currently the most common routing protocol used on IPX networks.RIP and SAP perform well in small networks that have simple architectures and few routers. However, they begin to reveal their limitations in the large, complex internetworks that are becoming increasingly common throughout the large installed base of NetWare systems.By default, RIP and SAP packets are broadcast every 60 seconds, even if no change has occurred anywhere in a route or service. Depending on the size and speed of the network, these periodic broadcasts can consume a significant amount of bandwidth and burden NetWare nodes.NetWare 4.1 provides a configurable parameter, CLASS=MENUITEM MOREINFO="NONE"Periodic Update Interval, that enables you to control how often a router broadcasts its route and service updates. This, along with other configurable parameters, such as CLASS=MENUITEM MOREINFO="NONE"Aging Interval Multiplier, CLASS=MENUITEM MOREINFO="NONE"Pace Override, and CLASS=MENUITEM MOREINFO="NONE"Packet Size Override, enables you to fine-tune the operation of RIP and SAP on your router. However, the default values for these parameters are sufficient for most IPX networks and should be changed only on the advice of your technical support representative. A misconfiguration can cause the router to lose routes and services or even generate more traffic than usual.When configuring RIP on an interface, you can set the CLASS=MENUITEM MOREINFO="NONE"RIP State parameter to one of three states: CLASS=MENUITEM MOREINFO="NONE"Auto, CLASS=MENUITEM MOREINFO="NONE"On, and CLASS=MENUITEM MOREINFO="NONE"Off. CLASS=MENUITEM MOREINFO="NONE"Auto, the default state, enables the router to accept incoming RIP packets and rebroadcast their routes only if RIP-broadcasting devices, such as NetWare 2 servers, are operating on the attached network. If those devices are removed from the attached network, the CLASS=MENUITEM MOREINFO="NONE"Auto-state interface responds by automatically disabling RIP and enabling NLSP. CLASS=MENUITEM MOREINFO="NONE"On enables the router to exchange RIP packets freely with other RIP routers on the network. CLASS=MENUITEM MOREINFO="NONE"Off disables RIP routing on the interface but does not prevent the router from responding to incoming requests for RIP routes from local NetWare workstations.PAGENUM=19 ID="BP25"Similarly, you configure SAP on an interface with the CLASS=MENUITEM MOREINFO="NONE"SAP State parameter, which can also assume one of three states: CLASS=MENUITEM MOREINFO="NONE"Auto, CLASS=MENUITEM MOREINFO="NONE"On, and CLASS=MENUITEM MOREINFO="NONE"Off. CLASS=MENUITEM MOREINFO="NONE"Auto, the default state, enables the router to accept incoming SAP packets and rebroadcast their services only if SAP-broadcasting devices, such as NetWare 2 servers, are operating on the attached network. If those devices are removed from the attached network, the CLASS=MENUITEM MOREINFO="NONE"Auto-state interface responds by automatically disabling SAP and enabling NLSP. CLASS=MENUITEM MOREINFO="NONE"On enables the router to exchange SAP packets freely with other routers on the network. CLASS=MENUITEM MOREINFO="NONE"Off disables SAP advertising on the interface but does not prevent the router from responding to incoming requests for services from local NetWare workstations. Additionally, the CLASS=MENUITEM MOREINFO="NONE"Off state still allows the router to import locally advertised services.If you want to filter routes or services between routers, use RIP and SAP. NLSP routers cannot filter routes or services.For additional information about how RIP and SAP work, refer to the BOOK="ipxrtenu" COLLECTION="nw41"NetWare 4.1 IPX Reference.RENDERAS="SECT2"How to Configure RIPIDXID="w996"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"IDXID="w997"BOOK="_idx" COLLECTION="nw41" TIDREF="i3859"
To configure RIP, load INETCFG and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"IPX (CLASS=MENUITEM MOREINFO="NONE"IPX Protocol Configuration window appears)Complete the following steps:PERFORMANCE="REQUIRED"Select the CLASS=MENUITEM MOREINFO="NONE"Routing Protocol parameter.Select 
CLASS=MENUITEM MOREINFO="NONE"RIP/SAP Only if your network supports RIP/SAP routing and has no NLSP routers.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to return to the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu, then select the following path: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=19 ID="BP26"PAGENUM=20PERFORMANCE="REQUIRED"Configure the following parameters for the interface you selected:
MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"RIP State---Identifies the state of RIP on this interface. Select one of the following options:---CLASS=MENUITEM MOREINFO="NONE"Auto. Accepts and broadcasts RIP packets only if non-NLSP devices, such as NetWare 2 servers, are operating on the attached network. This is the default state.---CLASS=MENUITEM MOREINFO="NONE"Off. Disables RIP routing on the interface. This state disables backward compatibility with older routers and servers that use and depend on RIP.---CLASS=MENUITEM MOREINFO="NONE"On. Enables RIP routing on the interface. This state is necessary for some third-party products that require RIP to operate.The 
CLASS=MENUITEM MOREINFO="NONE"RIP Bind Options window also includes the following parameters:
MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Periodic Update Interval---Measured in 30-second units, determines the interval at which RIP packets are transmitted through this interface. The default value is 2 (60 seconds).Each router on the network segment to which this router is attached must use the same value for the CLASS=MENUITEM MOREINFO="NONE"Periodic Update Interval.CLASS=MENUITEM MOREINFO="NONE"Aging Interval Multiplier---Controls how long the router keeps route information received through this interface. The product of this parameter and the RIP CLASS=MENUITEM MOREINFO="NONE"Periodic Update Interval specifies how long the router keeps route information from periodic RIP updates received through an interface.Increasing the CLASS=MENUITEM MOREINFO="NONE"Aging Interval Multiplier slows the rate at which the router "ages" the routes in its Routing Information Table. This is necessary to keep routes that might otherwise be "aged out" of the routing table because of dropped RIP updates.The default value for the CLASS=MENUITEM MOREINFO="NONE"Aging Interval Multiplier is 4. For example, if RIP packets are sent every 60 seconds (CLASS=MENUITEM MOREINFO="NONE"Periodic Update Interval equals 2), the router keeps the route information for 240 (60 
 4) seconds without refreshing it.Each router on the network segment to which this router is attached must use the same value for the CLASS=MENUITEM MOREINFO="NONE"Aging Interval Multiplier.PAGENUM=21 ID="BP27"CLASS=MENUITEM MOREINFO="NONE"Pace Override---Specifies the maximum number of RIP packets that can be sent each second through this interface. The default---and maximum---pace for RIP packets is 9 pps.The default value for this parameter is 0, which means "do not override the current pace."CLASS=MENUITEM MOREINFO="NONE"Packet Size Override---Specifies the size, in bytes, of RIP packets sent on this interface. The default value is 0, which means "do not override the current value."Each router on the network segment must use the same RIP packet size.Because the default settings for these parameters are suitable for most RIP-based IPX networks, you should change them only for a specific purpose. Misconfiguring these parameters can increase routing traffic or cause loss of connectivity on your network. If you are unfamiliar with these parameters, refer to the BOOK="ipxrtenu" COLLECTION="nw41"NetWare 4.1 IPX Reference.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to return to the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu; save your changes when prompted.PERFORMANCE="REQUIRED"If you want these changes to take effect immediately, exit INETCFG, then type the following command:
FORMAT="LINESPECIFIC"MOREINFO="NONE"REINITIALIZE SYSTEM MOREINFO="NONE"<Enter>If you want to configure other IPX parameters, do so now, then reinitialize the system when you are finished.PAGENUM=21 ID="BP28"PAGENUM=22RENDERAS="SECT2"How to Configure SAPIDXID="w998"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"IDXID="w999"BOOK="_idx" COLLECTION="nw41" TIDREF="i3943"
To configure SAP, load INETCFG and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"IPX (CLASS=MENUITEM MOREINFO="NONE"IPX Protocol Configuration window appears)Complete the following steps:PERFORMANCE="REQUIRED"Select the CLASS=MENUITEM MOREINFO="NONE"Routing Protocol parameter, then select CLASS=MENUITEM MOREINFO="NONE"RIP/SAP Only.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to return to the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu, then select the following path: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 OptionsPERFORMANCE="REQUIRED"Configure the following parameters for the interface you selected:
MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"SAP State---Identifies the state of SAP on this interface. Select one of the following options:---CLASS=MENUITEM MOREINFO="NONE"Auto. Accepts and broadcasts SAP packets only if non-NLSP devices, such as NetWare 2 servers, are operating on the attached network. This is the default state.---CLASS=MENUITEM MOREINFO="NONE"Off. Disables SAP advertising on the interface. This state disables backward compatibility with older routers and servers that use and depend on SAP.The router responds to incoming SAP requests, such as Get Nearest Server, even if SAP is disabled on this interface.---CLASS=MENUITEM MOREINFO="NONE"On. Enables SAP advertising and RIP routing on the interface. This state is necessary for some third-party products that rely on SAP to advertise their services.PAGENUM=22 ID="BP29"PAGENUM=23CLASS=MENUITEM MOREINFO="NONE"Get Nearest Server Requests Override---Determines whether the router accepts or ignores SAP Get Nearest Server requests it receives through this interface. Select one of the following options:---CLASS=MENUITEM MOREINFO="NONE"No Override. Do not override the global setting for the router. This is the default state.---CLASS=MENUITEM MOREINFO="NONE"Ignore. Ignore Get Nearest Server requests received through this interface.---CLASS=MENUITEM MOREINFO="NONE"Accept. Accept Get Nearest Server requests received through this interface.The 
CLASS=MENUITEM MOREINFO="NONE"SAP Bind Options window also includes the following parameters:
MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Periodic Update Interval---Measured in 30-second units, determines the interval at which SAP packets are transmitted through this interface. The default value is 2 (60 seconds).Each router on the network segment to which this router is attached must use the same value for the CLASS=MENUITEM MOREINFO="NONE"Periodic Update Interval.CLASS=MENUITEM MOREINFO="NONE"Aging Interval Multiplier---Controls how long the router keeps service advertisements received through this interface. The product of this parameter and the SAP CLASS=MENUITEM MOREINFO="NONE"Periodic Update Interval specifies how long the router keeps service information from periodic SAP updates received through an interface. This parameter is a holding multiplier for the CLASS=MENUITEM MOREINFO="NONE"SAP Periodic Update Interval.The default value for the CLASS=MENUITEM MOREINFO="NONE"Aging Interval Multiplier is 4. For example, if SAP packets are sent every 60 seconds (CLASS=MENUITEM MOREINFO="NONE"Periodic Update Interval equals 2), the router keeps the service information for 240 (60 
 4) seconds without refreshing it.Each router on the network segment to which this router is attached must use the same value for the CLASS=MENUITEM MOREINFO="NONE"Aging Interval Multiplier.CLASS=MENUITEM MOREINFO="NONE"Pace Override---Specifies the maximum number of SAP packets that can be sent each second through this interface. The default---and maximum---pace for SAP packets is 9 pps.The default value for this parameter is 0, which means "do not override the current pace."PAGENUM=24 ID="BP30"CLASS=MENUITEM MOREINFO="NONE"Packet Size Override---Specifies the size, in bytes, of SAP packets sent on this interface. The default value is 0, which means "do not override."Each router on the network segment must use the same SAP packet sizeBecause the default settings for these parameters are suitable for most RIP-based IPX networks, you should change them only for a specific purpose. Misconfiguring these parameters can increase routing traffic or cause loss of connectivity on your network. If you are unfamiliar with these parameters, refer to the BOOK="ipxrtenu" COLLECTION="nw41"NetWare 4.1 IPX Reference.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to return to the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu; save your changes when prompted.PERFORMANCE="REQUIRED"If you want these changes to take effect immediately, exit INETCFG, then type the following command:
FORMAT="LINESPECIFIC"MOREINFO="NONE"REINITIALIZE SYSTEM MOREINFO="NONE"<Enter>If you want to configure other IPX parameters, do so now, then reinitialize the system when you are finished.RENDERAS="SECT1"ID="FM98371"Enabling Advanced IPX ParametersIDXID="w1000"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"IDXID="w1001"BOOK="_idx" COLLECTION="nw41" TIDREF="i125"
The CLASS=MENUITEM MOREINFO="NONE"Advanced IPX parameter allows you to enable or disable NLSP parameters and other advanced IPX parameters. You should disable this parameter only for the following reasons:MARK=BULLETYou want to evaluate NLSP before using it on your network.You do not plan to use NLSP on your network.PAGENUM=24 ID="BP31"PAGENUM=25RENDERAS="SECT2"How to Enable Advanced IPX ParametersIDXID="w1002"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"IDXID="w1003"BOOK="_idx" COLLECTION="nw41" TIDREF="i125"
To enable the advanced IPX parameters, load INETCFG and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"IPX (CLASS=MENUITEM MOREINFO="NONE"IPX Protocol Configuration window appears)Select CLASS=MENUITEM MOREINFO="NONE"Advanced IPX, then select CLASS=MENUITEM MOREINFO="NONE"Enabled.All NLSP parameters are enabled when you enable this parameter.Press MOREINFO="NONE"<Esc> to return to the CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu; save your change when prompted.If you want this change to take effect immediately, exit INETCFG, then type the following command:FORMAT="LINESPECIFIC"MOREINFO="NONE"REINITIALIZE SYSTEM MOREINFO="NONE"<Enter>If you want to configure other IPX parameters, do so now, then reinitialize the system when you are finished.RENDERAS="SECT1"ID="FM31348"Enabling FiltersIDXID="w1004"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"IDXID="w1005"BOOK="_idx" COLLECTION="nw41" TIDREF="i1499"
The CLASS=MENUITEM MOREINFO="NONE"Filtering Support parameter enables you to restrict the routes or services or the IPX or NetBIOS packets a router sends and receives.To configure specific filters, you must use FILTCFG. For information about configuring filters, see IDREF="FM54089"Chapter 5, "Configuring Filters."PAGENUM=25 ID="BP32"PAGENUM=26RENDERAS="SECT2"How to Enable FiltersIDXID="w1006"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"IDXID="w1007"BOOK="_idx" COLLECTION="nw41" TIDREF="i1499"
To enable filters on your router, load INETCFG and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"IPX (CLASS=MENUITEM MOREINFO="NONE"IPX Protocol Configuration window appears)Select CLASS=MENUITEM MOREINFO="NONE"Filtering Support, then select CLASS=MENUITEM MOREINFO="NONE"Enabled.Press MOREINFO="NONE"<Esc> to return to the CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu; save your change when prompted.If you want this change to take effect immediately, exit INETCFG, then type the following command:FORMAT="LINESPECIFIC"MOREINFO="NONE"REINITIALIZE SYSTEM MOREINFO="NONE"<Enter>If you want to configure other IPX parameters, do so now, then reinitialize the system when you are finished.RENDERAS="SECT1"ID="FM29310"Controlling the Propagation of Type 20 PacketsIDXID="w1008"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"IDXID="w1009"BOOK="_idx" COLLECTION="nw41" TIDREF="i4613"
NetWare 4.1 allows you to control the propagation of IDXID="w1010"BOOK="_idx" COLLECTION="nw41" TIDREF="i4613"
type 20 packets with the CLASS=MENUITEM MOREINFO="NONE"Advanced Packet Type 20 Flooding parameter. Type 20 is an IPX packet type that refers to any propagated packet. IDXID="w1011"BOOK="_idx" COLLECTION="nw41" TIDREF="i2654"
NetBIOS packets, for example, are type 20 packets.If the CLASS=MENUITEM MOREINFO="NONE"Advanced Packet Type 20 Flooding 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 routes to the same source.If the CLASS=MENUITEM MOREINFO="NONE"Advanced Packet Type 20 Flooding 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="w1012"BOOK="_idx" COLLECTION="nw41" TIDREF="i3849"reverse path forwarding.PAGENUM=27 ID="BP33"The router does not propagate type 20 packets through the same interface from which it receives them. This is known as IDXID="w1013"BOOK="_idx" COLLECTION="nw41" TIDREF="i4229"split horizon, a technique used with RIP and other distance vector routing protocols.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
   OPTION [0|1|2|3] MOREINFO="NONE"<Enter>You can type the command by itself to check the current setting, or you can specify one of the following numeric options:MARK=BULLET0---Router discards, rather than propagates, any type 20 packet it receives. This option completely disables type 20 packet propagation.1---Same effect as setting CLASS=MENUITEM MOREINFO="NONE"Advanced Packet Type 20 Flooding to CLASS=MENUITEM MOREINFO="NONE"Disabled.2---Same effect as setting CLASS=MENUITEM MOREINFO="NONE"Advanced Packet Type 20 Flooding to CLASS=MENUITEM MOREINFO="NONE"Enabled.3---Router propagates type 20 packets the same way as option MOREINFO="NONE"2, but does not forward them across WAN connections.PAGENUM=27 ID="BP34"PAGENUM=28RENDERAS="SECT2"How to Control the Propagation of Type 20 PacketsIDXID="w1014"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"IDXID="w1015"BOOK="_idx" COLLECTION="nw41" TIDREF="i4613"
To control the propagation of type 20 packets, load INETCFG and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"Expert Configuration OptionsSelect the CLASS=MENUITEM MOREINFO="NONE"Advanced Type 20 Packet Flooding parameter, then select CLASS=MENUITEM MOREINFO="NONE"Enabled.Press MOREINFO="NONE"<Esc> to return to the CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu; save your change when prompted.If you want this change to take effect immediately, exit INETCFG, then type the following command:FORMAT="LINESPECIFIC"MOREINFO="NONE"REINITIALIZE SYSTEM MOREINFO="NONE"<Enter>If you want to configure other IPX parameters, do so now, then reinitialize the system when you are finished.RENDERAS="SECT1"ID="FM33824"Changing the Hop Count Limit for IPX PacketsIDXID="w1016"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"IDXID="w1017"BOOK="_idx" COLLECTION="nw41" TIDREF="i1686"
NetWare 4.1 enables you to increase the range of outbound IPX packets with the CLASS=MENUITEM MOREINFO="NONE"Hop Count Limit parameter. The hop count limit is the maximum number of routers (hops) an IPX packet can traverse before it is discarded. You can set the CLASS=MENUITEM MOREINFO="NONE"Hop Count Limit parameter to any number between 8 and 127; however, the default value of 64 is sufficient for most IPX networks.The CLASS=MENUITEM MOREINFO="NONE"Hop Count Limit parameter applies only to IPX packets. It does not increase the range of RIP and SAP packets, which are limited to 16 hops, or type 20 (NetBIOS) packets, which are limited to eight hops.Earlier versions of the NetWare operating system limit the hop count of all IPX packets to 16. This also limits the size, or diameter, of IPX networks.If the diameter of your IPX network is approaching the 16-hop limit, you should run NLSP on the routers at the network boundary to ensure continued connectivity across the network as it grows. IDREF="FM94899"Figure 2-2 provides a simple, conceptual view of how this can work.PAGENUM=29 ID="BP35"LABEL="2-2" FLOAT="0"ID="FM94899"Running NLSP at the Boundary of a Large IPX NetworkFILEREF="hopcount.tif"RENDERAS="SECT2"How to Change the Hop Count LimitIDXID="w1018"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"IDXID="w1019"BOOK="_idx" COLLECTION="nw41" TIDREF="i1686"
To change the hop count limit, load INETCFG and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"Expert Configuration OptionsSelect the CLASS=MENUITEM MOREINFO="NONE"Hop Count Limit parameter, enter a value between 8 and 127, then press MOREINFO="NONE"<Enter>.Press MOREINFO="NONE"<Esc> to return to the CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu; save your change when prompted.If you want this change to take effect immediately, exit INETCFG, then type the following command:FORMAT="LINESPECIFIC"MOREINFO="NONE"REINITIALIZE SYSTEM MOREINFO="NONE"<Enter>If you want to configure other IPX parameters, do so now, then reinitialize the system when you are finished.PAGENUM=29 ID="BP36"PAGENUM=30RENDERAS="SECT1"ID="FM86203"Balancing Traffic Loads Over Equal-Cost RoutesIDXID="w1020"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"IDXID="w1021"BOOK="_idx" COLLECTION="nw41" TIDREF="i4541"
If a router has two or more network interfaces with routes to the same destination, it can distribute outbound traffic among those interfaces for an effective increase in throughput. This is called load balancing or load sharing.NLSP uses an assigned path cost to select the best route by which to forward outbound IPX packets. The higher the throughput of the network medium, the lower the cost of the route. IDREF="FM52271"Table 2-1 shows the throughput range, its default cost, and some typical network media. LABEL="2-1" PGWIDE=0 TOCENTRY="1"ID="FM52271"Throughput Range, Default Cost, and 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 ALIGN="CENTER" ROTATE="0" MOREROWS="0"61COLNAME=3 ROTATE="0" MOREROWS="0"9600-Baud LineCOLNAME=1 ROTATE="0" MOREROWS="0"48-64 KbpsCOLNAME=2 ALIGN="CENTER" ROTATE="0" MOREROWS="0"45COLNAME=3 ROTATE="0" MOREROWS="0"ISDN (U.S.)COLNAME=1 ROTATE="0" MOREROWS="0"64-128 KbpsCOLNAME=2 ALIGN="CENTER" ROTATE="0" MOREROWS="0"45COLNAME=3 ROTATE="0" MOREROWS="0"ISDN (Europe)COLNAME=1 ROTATE="0" MOREROWS="0"1-2 MbpsCOLNAME=2 ALIGN="CENTER" 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 ALIGN="CENTER" 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 ALIGN="CENTER" 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 ALIGN="CENTER" ROTATE="0" MOREROWS="0"20COLNAME=3 ROTATE="0" MOREROWS="0"Ethernet (10 Mbps)COLNAME=1 ROTATE="0" MOREROWS="0"16-32 MbpsCOLNAME=2 ALIGN="CENTER" ROTATE="0" MOREROWS="0"19COLNAME=3 ROTATE="0" MOREROWS="0"Token Ring (16 Mbps)COLNAME=1 ROTATE="0" MOREROWS="0"64-128 MbpsCOLNAME=2 ALIGN="CENTER" ROTATE="0" MOREROWS="0"14COLNAME=3 ROTATE="0" MOREROWS="0"FDDI (100 Mbps),CDDI (100 Mbps)You can specify up to eight equal-cost routes to a single destination with the CLASS=MENUITEM MOREINFO="NONE"Maximum Number of Path Splits parameter. Two routes are equal in cost if the cost to the destination is the same for both routes. To equalize the costs of two interfaces, you set their CLASS=MENUITEM MOREINFO="NONE"Cost Override parameter to the same value. By default, CLASS=MENUITEM MOREINFO="NONE"Cost Override is set to 0 for all interfaces, which means that NLSP uses the default cost associated with the connected medium and throughput range listed in IDREF="FM52271"Table 2-1.PAGENUM=31 ID="BP37"If you configure equal-cost routes on two or more interfaces, make sure the associated media throughputs fall within---or near---the same range, as indicated in IDREF="FM52271"Table 2-1. For example, equal-cost routes between a 10 Mbps Ethernet link and a 16 Mbps token ring link are viable; equal-cost routes between a 4 Mbps token ring link and a 16 Mbps token ring link are not.Do not equalize the cost of routes whose throughputs differ greatly; this can interfere with the operation of IPX applications running over the network.To see an example of how load balancing works over equal-cost routes, see the BOOK="ipxrtenu" COLLECTION="nw41"NetWare 4.1 IPX Reference.RENDERAS="SECT2"How to Balance Traffic Loads Over Equal-Cost RoutesTo use equal-cost routes, the router must be running NLSP. To enable NLSP globally on the router or on one or more interfaces, see IDREF="FM52660""How to Configure NLSP."IDXID="w1022"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"IDXID="w1023"BOOK="_idx" COLLECTION="nw41" TIDREF="i4541"
To configure load balancing over equal-cost routes, load INETCFG and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"Expert Configuration OptionsComplete the following steps:PERFORMANCE="REQUIRED"Select the CLASS=MENUITEM MOREINFO="NONE"Maximum Number of Path Splits parameter, enter a value between 2 and 8, then press MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to return to the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu.PERFORMANCE="REQUIRED"Complete the following steps to change the cost of an interface:PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select the network interface > Select CLASS=MENUITEM MOREINFO="NONE"Expert Bind Options > Select CLASS=MENUITEM MOREINFO="NONE"NLSP Bind OptionsPERFORMANCE="REQUIRED"Select the 
CLASS=MENUITEM MOREINFO="NONE"Cost Override parameter, enter a value between 1 and 63, then press 
MOREINFO="NONE"<Enter>.
PAGENUM=32 ID="BP38"PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to return to the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu; save your changes when prompted.PERFORMANCE="REQUIRED"If you want these changes to take effect immediately, exit INETCFG, then type the following command:
FORMAT="LINESPECIFIC"MOREINFO="NONE"REINITIALIZE SYSTEM MOREINFO="NONE"<Enter>If you want to configure other IPX parameters, do so now, then reinitialize the system when you are finished.RENDERAS="SECT1"ID="FM35697"Configuring SPX Connection ParametersIDXID="w1024"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"IDXID="w1025"BOOK="_idx" COLLECTION="nw41" TIDREF="i4237"
Because some Novell and third-party NetWare applications place unique demands on the SPX transport protocol, INETCFG gives you control over the following parameters:MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Maximum IPX Socket Table Size---IDXID="w1026"BOOK="_idx" COLLECTION="nw41" TIDREF="i2932"
Maximum number of concurrent IPX sockets that can be opened by an application.CLASS=MENUITEM MOREINFO="NONE"SPX Watchdog Abort Timeout---IDXID="w1027"BOOK="_idx" COLLECTION="nw41" TIDREF="i2932"
Time, in ticks (about 1/18 of a second), SPX waits without receiving a packet from the other end of a connection before concluding that the connection is no longer valid.CLASS=MENUITEM MOREINFO="NONE"SPX Watchdog Verify Timeout---IDXID="w1028"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.CLASS=MENUITEM MOREINFO="NONE"SPX Ack Wait Timeout---IDXID="w1029"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.CLASS=MENUITEM MOREINFO="NONE"SPX Default Retry Count---IDXID="w1030"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.PAGENUM=32 ID="BP39"PAGENUM=33CLASS=MENUITEM MOREINFO="NONE"Maximum Concurrent SPX Sessions---IDXID="w1031"BOOK="_idx" COLLECTION="nw41" TIDREF="i2932"
Maximum number of concurrent SPX sessions that can be opened by an application program.The default values for these parameters are sufficient for most NetWare applications. Any application that requires a change to one or more of these parameters typically tells you so.RENDERAS="SECT2"How to Configure SPX Connection ParametersIDXID="w1032"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"IDXID="w1033"BOOK="_idx" COLLECTION="nw41" TIDREF="i4237"
To configure the SPX connection parameters, load INETCFG and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"Expert Configuration OptionsSelect CLASS=MENUITEM MOREINFO="NONE"IPX/SPX Parameters. Enter a value for each of the parameters you need to change.Press MOREINFO="NONE"<Esc> to return to the CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu; save your change when prompted.If you want these changes to take effect immediately, exit INETCFG, then restart the system.If you want to configure other IPX parameters, do so now, then restart the system when you are finished.RENDERAS="SECT1"ID="FM18623"Tunneling Through IP NetworksIDXID="w1034"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"IDXID="w1035"BOOK="_idx" COLLECTION="nw41" TIDREF="i4607"
This section describes IP tunneling, the method by which two or more IPX networks exchange packets through an IP network.IPX uses the IDXID="w1036"BOOK="_idx" COLLECTION="nw41" TIDREF="i3082"
Open Data-Link InterfaceTM (ODITM) interface to pass packets through the IP tunnel. The IP tunnel sends each IPX packet across the TCP/IP network by encapsulating it in a IDXID="w1037"BOOK="_idx" COLLECTION="nw41" TIDREF="i4704"
User Datagram Protocol (UDP) packet. The tunnel driver at the destination router removes the UDP header from each incoming packet and passes it through ODI to IPX.Encapsulating IPX packets in IP packets enables them to go through any TCP/IP supported media, such as Ethernet or token ring.PAGENUM=34 ID="BP40"The TCP/IP network is the medium. The IP address is the immediate address, which performs the same function in the TCP/IP medium as the Media Access Control (MAC) address performs in the Ethernet medium.NetWare 4.1 provides the IPTUNNEL LAN driver that models the IP internetwork as a single IPX LAN to tunnel IPX packets. To configure your server to use an IP tunnel, IP must be loaded and bound to the interfaces you plan to use. The IP tunnel requires local IP addressing information and can fail if IP is not connected to the network. For basic IP configuration procedures, see the BOOK="cfg1_enu" COLLECTION="nw41"NetWare 4.1 Basic Protocol Configuration Guide.RENDERAS="SECT2"ID="FM34843"IDXID="w1038"BOOK="_idx" COLLECTION="nw41" TIDREF="i1923"The IPTUNNEL DriverIDXID="w1039"BOOK="_idx" COLLECTION="nw41" TIDREF="i4607"IDXID="w1040"BOOK="_idx" COLLECTION="nw41" TIDREF="i1923"
You can use the IPTUNNEL driver to enable IPX to use a TCP/IP network to communicate with other IPX nodes. You configure IPTUNNEL from INETCFG or from the command line.The IPTUNNEL driver enables IPX to use a TCP/IP network to communicate with other IPX nodes.The IPTUNNEL driver models the IP internetwork as a single IPX LAN. To IPX, IPTUNNEL performs the same functions as a typical NetWare LAN driver. The TCP/IP network operates as if it were a hardware network, passing packets among the IPX nodes connected to it.IPTUNNEL is compatible with the Schneider & Koch SK-IPX/IP Gateway, which provides NetWare 2 compatibility. IPTUNNEL also serves workstations using either the Novell® IP tunnel workstation driver, a component of the LAN WorkPlace® for DOS software, or the Schneider & Koch end node product for DOS.When configuring the IP tunnel, you supply the IP addresses of other IPX routers that you plan to include in the tunnel. These other IPX routers are known as peers. Whenever IPX broadcasts a packet, the IP tunnel duplicates the packet and sends a copy to each peer.IDXID="w1041"BOOK="_idx" COLLECTION="nw41" TIDREF="i1957"
To exchange routing and service information between IPX routers, IPX depends on broadcasting messages to every other NetWare server connected to the medium. However, because broadcast facilities are limited in TCP/IP networks, IPTUNNEL must handle broadcast traffic by duplicating the packet and sending a copy to each peer router.PAGENUM=35 ID="BP41"IPTUNNEL presents a standard ODI driver interface to the NetWare system and handles IPX traffic like any other driver. You load the driver like any other, and then bind IPX to it to instruct IPX to receive and route packets over the TCP/IP network.You should configure any connected group of peers so that all servers in the group have the IP addresses of all other servers in the group. Other configurations are possible, but not recommended; they frequently create confusing---and often surprising---IPX routing topologies.RENDERAS="SECT2"ID="FM74163"How to Configure IPTUNNEL from INETCFGMake sure TCP/IP is enabled and bound to the interface before you configure IPTUNNEL.IDXID="w1042"BOOK="_idx" COLLECTION="nw41" TIDREF="i4607"IDXID="w1043"BOOK="_idx" COLLECTION="nw41" TIDREF="i1923"
To configure the IPTUNNEL driver, load INETCFG and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Boards > Press MOREINFO="NONE"<Ins> (CLASS=MENUITEM MOREINFO="NONE"Available Drivers window appears)Complete the following steps:PERFORMANCE="REQUIRED"Select CLASS=MENUITEM MOREINFO="NONE"IPTUNNEL from the list.The 
CLASS=MENUITEM MOREINFO="NONE"Board Configuration window appears.PERFORMANCE="REQUIRED"Configure the following parameters:
MARK=BULLETIDXID="w1044"BOOK="_idx" COLLECTION="nw41" TIDREF="i1922"IDXID="w1045"BOOK="_idx" COLLECTION="nw41" TIDREF="i484"CLASS=MENUITEM MOREINFO="NONE"Board Name---Identifies the interface board. This parameter is available only from INETCFG.IDXID="w1046"BOOK="_idx" COLLECTION="nw41" TIDREF="i1922"IDXID="w1047"BOOK="_idx" COLLECTION="nw41" TIDREF="i3285"CLASS=MENUITEM MOREINFO="NONE"Peer IP Address---Adds an IP address to the peer list. If this parameter is not present, no peer is added. This is the most important parameter.The equivalent command-based parameter is CLASS=MENUITEM MOREINFO="NONE"PEER.IDXID="w1048"BOOK="_idx" COLLECTION="nw41" TIDREF="i1922"IDXID="w1049"BOOK="_idx" COLLECTION="nw41" TIDREF="i2167"CLASS=MENUITEM MOREINFO="NONE"Local IP Address---Specifies a single local IP address for the IP tunnel.For IPX routing to work correctly, the IP tunnel must use a single local IP address consistently. The default value is the IP address of the first interface to which TCP/IP was bound.PAGENUM=36 ID="BP42"The equivalent command-based parameter is CLASS=MENUITEM MOREINFO="NONE"LOCAL. If you configure IPTUNNEL from the command line, use the CLASS=MENUITEM MOREINFO="NONE"LOCAL parameter only with the first MOREINFO="NONE"LOAD IPTUNNEL command.IDXID="w1050"BOOK="_idx" COLLECTION="nw41" TIDREF="i1922"IDXID="w1051"BOOK="_idx" COLLECTION="nw41" TIDREF="i4625"CLASS=MENUITEM MOREINFO="NONE"UDP Checksum---Enables or disables UDP checksums on transmitted packets. The default option is CLASS=MENUITEM MOREINFO="NONE"Yes. The UDP checksum improves data reliability; you should leave this parameter enabled.The equivalent command-based parameter is CLASS=MENUITEM MOREINFO="NONE"CHKSUM.IDXID="w1052"BOOK="_idx" COLLECTION="nw41" TIDREF="i1922"IDXID="w1053"BOOK="_idx" COLLECTION="nw41" TIDREF="i4626"CLASS=MENUITEM MOREINFO="NONE"UDP Port---Sets the UDP port the IP tunnel uses. The default value is 213, the officially assigned UDP port for IPX packets. Enter a value between 1 and 65535.If you must communicate with nodes using products prior to Schneider & Koch SK-IPX/IP version 1.3, you can use port=59139.The equivalent command-based parameter is CLASS=MENUITEM MOREINFO="NONE"PORT. If you configure IPTUNNEL from the command line, use the CLASS=MENUITEM MOREINFO="NONE"PORT parameter only with the first MOREINFO="NONE"LOAD IPTUNNEL command.Comment---Optional description of the tunnel configuration.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc>.The new board appears at the end of the 
CLASS=MENUITEM MOREINFO="NONE"Configured Boards list.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to return to the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu.PERFORMANCE="REQUIRED"Bind IPX to IPTUNNEL.For binding procedures, see the 
BOOK="cfg1_enu" COLLECTION="nw41"NetWare 4.1 Basic Protocol Configuration Guide.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to return to the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu; save your changes when prompted.PERFORMANCE="REQUIRED"If you want these changes to take effect immediately, exit INETCFG, then type the following command:
FORMAT="LINESPECIFIC"MOREINFO="NONE"REINITIALIZE SYSTEM MOREINFO="NONE"<Enter>If you want to configure other IPX parameters, do so now, then reinitialize the system when you are finished.PAGENUM=37 ID="BP43"RENDERAS="SECT2"How to Configure IPTUNNEL from the Command LineIDXID="w1054"BOOK="_idx" COLLECTION="nw41" TIDREF="i4607"IDXID="w1055"BOOK="_idx" COLLECTION="nw41" TIDREF="i1923"
You can also configure IPTUNNEL from the command line with the IDXID="w1056"BOOK="_idx" COLLECTION="nw41" TIDREF="i2141"MOREINFO="NONE"LOAD IPTUNNEL command using the following format:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD IPTUNNEL [PEER=remote IP address] 
   [LOCAL=local IP address] [CHKSUM={YES|NO}]
   [PORT=UDP port number] [SHOW={YES|NO}]
   MOREINFO="NONE"<Enter>If you use INETCFG to configure IPTUNNEL, you cannot add more than one peer router to a peer group. If you configure IPTUNNEL from the command line, just repeat the MOREINFO="NONE"LOAD IPTUNNEL command for each peer router you want to add. IDREF="FM23804""Configuring IPTUNNEL for Multiple Peers" explains how to do this.The CLASS=MENUITEM MOREINFO="NONE"PEER, CLASS=MENUITEM MOREINFO="NONE"LOCAL, CLASS=MENUITEM MOREINFO="NONE"CHKSUM, and CLASS=MENUITEM MOREINFO="NONE"PORT parameters are explained in IDREF="FM74163""How to Configure IPTUNNEL from INETCFG."If you configure IPTUNNEL for multiple peer routers, use the CLASS=MENUITEM MOREINFO="NONE"LOCAL and CLASS=MENUITEM MOREINFO="NONE"PORT parameters only with the first MOREINFO="NONE"LOAD IPTUNNEL command.The CLASS=MENUITEM MOREINFO="NONE"IDXID="w1057"BOOK="_idx" COLLECTION="nw41" TIDREF="i1922"IDXID="w1058"BOOK="_idx" COLLECTION="nw41" TIDREF="i4145"
SHOW parameter, available only with the command-based configuration, displays an IPTUNNEL configuration summary. If you load IPTUNNEL with CLASS=MENUITEM MOREINFO="NONE"SHOW set to CLASS=MENUITEM MOREINFO="NONE"YES (the default), the command displays the local IP address, the UDP port used, the peer list, and whether UDP checksums are enabled.To configure IPTUNNEL with the MOREINFO="NONE"LOAD IPTUNNEL command, complete the following tasks in order:NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"From INETCFG, enable TCP/IP and bind IP to each network interface you plan to use with IPTUNNEL.Return to the console prompt and typeFORMAT="LINESPECIFIC"MOREINFO="NONE"REINITIALIZE SYSTEM MOREINFO="NONE"<Enter>Alternately, bring down and restart the router.Enter the necessary MOREINFO="NONE"LOAD IPTUNNEL commands.PAGENUM=38 ID="BP44"RENDERAS="SECT2"ID="FM23804"Configuring IPTUNNEL for Multiple PeersIPTUNNEL duplicates and transmits every IPX packet in a UDP packet to each remote peer in a peer group. Because this can create a large amount of traffic on the network, you should have no more than 10 peers for any one node.IDXID="w1059"BOOK="_idx" COLLECTION="nw41" TIDREF="i1923"IDXID="w1060"BOOK="_idx" COLLECTION="nw41" TIDREF="i4607"IDREF="FM77537"Figure 2-3 shows how IPTUNNEL enables three NetWare servers---A, B, and C---to communicate over IPX network 95 as an IP tunnel through an IP internetwork.LABEL="2-3" FLOAT="0"ID="FM77537"IPTUNNEL Configuration for Three PeersFILEREF="acm52.tif"To configure IPTUNNEL on Server A, you enter the following commands at the Server A console:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD IPTUNNEL PEER=129.1.0.7 MOREINFO="NONE"<Enter>
LOAD IPTUNNEL PEER=192.1.1.96 MOREINFO="NONE"<Enter>
BIND IPX to IPTUNNEL NET=95 MOREINFO="NONE"<Enter>The first two commands load IPTUNNEL and add entries on Server A for peer IP addresses 129.1.0.7 (Server B) and 192.1.1.96 (Server C). The third command binds IPX to IPTUNNEL.PAGENUM=39 ID="BP45"To configure IPTUNNEL on Server B, you enter the following commands at the Server B console:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD IPTUNNEL PEER=1.0.0.3 MOREINFO="NONE"<Enter>
LOAD IPTUNNEL PEER=192.1.1.96 MOREINFO="NONE" <Enter>
BIND IPX to IPTUNNEL NET=95 MOREINFO="NONE"<Enter>The preceding commands are almost identical to those in the Server A configuration. These commands add entries for peer IP addresses 1.0.0.3 (Server A) and 192.1.1.96 (Server C) and bind IPX to IPTUNNEL.To configure IPTUNNEL on Server C, you enter the following commands at the Server C console:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD IPTUNNEL PEER=1.0.0.3MOREINFO="NONE" <Enter>
LOAD IPTUNNEL PEER=129.1.0.7 MOREINFO="NONE"<Enter>
BIND IPX TO IPTUNNEL NET=95 MOREINFO="NONE" <Enter>The preceding commands are almost identical to those in the Server B configuration. These commands add entries for peer IP addresses 1.0.0.3 (Server A) and 129.1.0.7 (Server B) and bind IPX to IPTUNNEL.RENDERAS="SECT1"ID="FM67153"Configuring the MacIPX GatewayIDXID="w1061"BOOK="_idx" COLLECTION="nw41" TIDREF="i2275"IDXID="w1062"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"
The MacIPX gateway enables IPX networks to exchange data with Macintosh clients running MacIPX applications on AppleTalk networks. Because IPX is the native network protocol for NetWare LANs, the MacIPX gateway enables Macintosh clients to use the resources on a NetWare LAN.MacIPX software provides support for IPX transport protocols. It does not enable Macintosh users connected to the IPX network to log in to a NetWare server or to print documents on NetWare printers. Users and developers must rely on NetWare for Macintosh software to support NetWare file and print services.The MacIPX gateway converts packets traveling in both directions between the AppleTalk and the IPX networks. IPX packets generated on a Macintosh and destined for the IPX network are sent out with AppleTalk encapsulation. When the packets reach the MacIPX gateway, the gateway strips the AppleTalk encapsulation and forwards them to the IPX network.PAGENUM=40 ID="BP46"Similarly, when IPX packets from the IPX network reach the MacIPX gateway, the gateway adds AppleTalk encapsulation and delivers them to the MacIPX clients on the AppleTalk network.IDREF="FM99166"Figure 2-4 shows a MacIPX gateway between an AppleTalk network and an IPX network that has both PCs and Macintosh computers. The MacIPX gateway allows Macintosh computers running MacIPX applications on the AppleTalk network to communicate with the IPX network.LABEL="2-4" FLOAT="0"ID="FM99166"Networks Connected by a MacIPX GatewayFILEREF="macipx6.tif"PAGENUM=40 ID="BP47"PAGENUM=41RENDERAS="SECT2"Understanding the MacIPX GatewayIDXID="w1063"BOOK="_idx" COLLECTION="nw41" TIDREF="i2275"
You can load the MacIPX gateway if your networks have the following characteristics:MARK=BULLETYou have IPX and AppleTalk networks that you want to connect and these networks are part of a LAN running NetWare 3.11 or later, or NetWare 4.1. You need to load the MacIPX gateway on one of these networks.The AppleTalk networks have MacIPX clients on them. These are Macintosh clients with IDXID="w1064"BOOK="_idx" COLLECTION="nw41" TIDREF="i2275"
applications based on MacIPX.One or more of the networks use only the AppleTalk protocol family to connect Macintosh clients to the network. APPLETLK.NLM must be installed and configured before you load and configure the MacIPX gateway. The MacIPX gateway requires 65 KB of memory.From a user perspective, the MacIPX gateway is required only for Macintosh users who select the IDXID="w1065"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"
AppleTalk icon in the IDXID="w1066"BOOK="_idx" COLLECTION="nw41" TIDREF="i2275"
MacIPX Control Panel. If all Macintosh users select either the IDXID="w1067"BOOK="_idx" COLLECTION="nw41" TIDREF="i1352"
Ethernet or IDXID="w1068"BOOK="_idx" COLLECTION="nw41" TIDREF="i4512"
Token Ring icon, and if you permit IPX traffic on those networks, then you do not need the MacIPX gateway.You cannot use the IDXID="w1069"BOOK="_idx" COLLECTION="nw41" TIDREF="i2275"
MacIPX gateway to route IPX packets across an AppleTalk network. The MacIPX gateway's encapsulation capabilities cannot connect IPX networks across an AppleTalk cloud. This is because MacIPX is not an extension to AppleTalk networking. Rather, it allows Macintosh computers to participate in IPX networks and encourages multiplatform peer-to-peer connectivity.MacIPX applications automatically select an IPX gateway only when the gateway is in the same zone that contains the Macintosh client running MacIPX. If this is not the case, use the IDXID="w1070"BOOK="_idx" COLLECTION="nw41" TIDREF="i2275"
MacIPX Control Panel to configure MacIPX to look for IPX gateways in specific zones.Plan the location of your MacIPX gateways to minimize the amount of configuration required by MacIPX. For example, if you have an AppleTalk network for dial-in users that is providing service for AppleTalk Remote Access IDXID="w1071"BOOK="_idx" COLLECTION="nw41" TIDREF="i236"
(ARA), you might want to ensure that a MacIPX gateway is serving the AppleTalk zone that includes the ARA network, so that Macintosh clients using ARA do not require MacIPX configuration.PAGENUM=42 ID="BP48"EachIDXID="w1072"BOOK="_idx" COLLECTION="nw41" TIDREF="i2275"
 MacIPX gateway must have a unique IPX network number. All the MacIPX clients using the MacIPX gateway are on that IPX network. However, you can restrict the set of AppleTalk networks that the MacIPX gateway serves. For more information, see IDREF="FM53927""Configuring the MacIPX Gateway to Serve Specific AppleTalk Networks."The IPX address of a IDXID="w1073"BOOK="_idx" COLLECTION="nw41" TIDREF="i2272"
MacIPX client using a MacIPX gateway consists of a network number and a node number. These are determined in the following way:MARK=BULLETThe network number is the one that was bound to the gateway itself.The node ID, except for MacIPX 1.1 or earlier, consists of the bytes 0x7A, 0x00, and 0x00 followed by the MacIPX client's two-byte AppleTalk network number, and the client's one-byte AppleTalk node ID.For example, if the MacIPX client on AppleTalk network 0x1234 with node ID 0xAA is using a gateway whose IPX network is 0x4321, the IPX address of the client is 4321:7A00001234AA.For MacIPX 1.1 and earlier, the node ID consists of three bytes of 0x00, followed by the two-byte AppleTalk network number and one-byte node ID.Loading the IDXID="w1074"BOOK="_idx" COLLECTION="nw41" TIDREF="i2275"
MacIPX gateway comprises three steps: configuring it, binding IPX to it, and reinitializing the server. The following sections explain these procedures.RENDERAS="SECT3"ID="FM87423"How to Configure the MacIPX GatewayIDXID="w1075"BOOK="_idx" COLLECTION="nw41" TIDREF="i2275"
The MacIPX gateway driver, IDXID="w1076"BOOK="_idx" COLLECTION="nw41" TIDREF="i2281"
MACIPXGW.LAN, is copied to the server as a part of the NetWare installation. However, before you can use it, you must configure it and bind IPX to it.To configure the MacIPX gateway, load INETCFG and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Boards > Press MOREINFO="NONE"<Insert> (CLASS=MENUITEM MOREINFO="NONE"Available List window appears) > Select CLASS=MENUITEM MOREINFO="NONE"MACIPXGW (CLASS=MENUITEM MOREINFO="NONE"Board Configuration window appears)PAGENUM=42 ID="BP49"PAGENUM=43Configure the following parameters:MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Board Name---Name you give the gateway driver.CLASS=MENUITEM MOREINFO="NONE"Gateway Name---Name you give the MacIPX gateway. IDXID="w1077"BOOK="_idx" COLLECTION="nw41" TIDREF="i2275"
This name is used to advertise the IDXID="w1078"BOOK="_idx" COLLECTION="nw41" TIDREF="i2275"
MacIPX gateway on the AppleTalk network. It appears in the IDXID="w1079"BOOK="_idx" COLLECTION="nw41" TIDREF="i2275"
MacIPX Control Panel and, therefore, should be a name that users recognize easily.If you do not specify a name, the MacIPX gateway uses the name of the NetWare 4.1 server on which the MacIPX gateway is installed.CLASS=MENUITEM MOREINFO="NONE"Unicast Threshold---Controls how IPX broadcast traffic is sent by the MacIPX gateway to AppleTalk networks. You can specify a value from 1 to 4294967295 (unsigned four-byte integer). The default value is 1. Enter a number lower than the number of MacIPX clients served by the MacIPX gateway (such as 1) to send IPX broadcast packets to all AppleTalk networks with MacIPX clients. Macintosh systems not running MacIPX applications do not understand the broadcast packets and drop them. Using this option means that unnecessary packets are distributed on the network.Enter a number equal to or higher than the number of MacIPX clients served by the MacIPX gateway to send CLASS=MENUITEM MOREINFO="NONE"IPX broadcast packets to each MacIPX client. If the number of clients exceeds this threshold number, the MacIPX gateway starts sending broadcast packets. Using this option can increase network traffic, because a single IPX broadcast packet could become many AppleTalk unicast packets, depending on the number of MacIPX clients.CLASS=MENUITEM MOREINFO="NONE"Comment---Information to help you administer the board. Press the MOREINFO="NONE"<Up> or MOREINFO="NONE"<Down> arrow key if you need to move between fields.Press MOREINFO="NONE"<Esc> to return to the CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu; save your changes when prompted.If you want these changes to take effect immediately, exit INETCFG, then bring down and restart the server. If you want to configure other parameters, do so now and restart the server when you are finished.The next step is to bind IPX to the gateway. To do so, see the next section, IDREF="FM44821""How to Bind IPX to the MacIPX Gateway."PAGENUM=44 ID="BP50"RENDERAS="SECT3"ID="FM44821"How to Bind IPX to the MacIPX GatewayFor the IDXID="w1080"BOOK="_idx" COLLECTION="nw41" TIDREF="i2275"
MacIPX gateway to appear in the list in the IDXID="w1081"BOOK="_idx" COLLECTION="nw41" TIDREF="i2275"
MacIPX Control Panel, you must bind IPX to the MacIPX gateway. To bind IPX to the MacIPX gateway, load INETCFG and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Press MOREINFO="NONE"<Insert> (CLASS=MENUITEM MOREINFO="NONE"Select from the list of configured protocols window appears) > Select CLASS=MENUITEM MOREINFO="NONE"IPX (CLASS=MENUITEM MOREINFO="NONE"Select from the list of configured network interfaces window appears) > Select the MacIPX driver (CLASS=MENUITEM MOREINFO="NONE"Binding IPX to a LAN Interface window appears)Configure the following parameters:MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"IPX Network Number---Network number of the IPX network to which the interface is attached.CLASS=MENUITEM MOREINFO="NONE"Expert Options---Entry point to configure IPX settings for RIP and SAP. These settings default to standard IPX values; you should not need to change the existing values.Press MOREINFO="NONE"<Esc> to return to the CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu; save your changes when prompted.If you want these changes to take effect immediately, exit INETCFG, then bring down and restart the server. If you want to configure other parameters, do so now and restart the server when you are finished.RENDERAS="SECT2"ID="FM93482"Administering the MacIPX GatewayIDXID="w1082"BOOK="_idx" COLLECTION="nw41" TIDREF="i2275"
After the IDXID="w1083"BOOK="_idx" COLLECTION="nw41" TIDREF="i2275"
MacIPX gateway is configured and bound, you need to administer it. The following sections explain how to configure the MacIPX gateway to serve specific AppleTalk networks, and how to display information and statistics about the MacIPX gateway.PAGENUM=44 ID="BP51"PAGENUM=45RENDERAS="SECT3"ID="FM53927"Configuring the MacIPX Gateway to Serve Specific AppleTalk NetworksThe IDXID="w1084"BOOK="_idx" COLLECTION="nw41" TIDREF="i2275"
MacIPX gateway, by default, serves all AppleTalk networks that make up the AppleTalk cloud. However, you can also configure the MacIPX gateway to restrict its service to selected AppleTalk networks.To restrict service, create a configuration file called IDXID="w1085"BOOK="_idx" COLLECTION="nw41" TIDREF="i2280"
MACIPXGW.DAT in the SYS:SYSTEM directory on the server. Place commands in the file using the following syntax:FORMAT="LINESPECIFIC"MOREINFO="NONE"[exclude | include]
<net_number>[-net_number]
[. . .]The first line is a keyword that specifies the following modes of inclusion:MARK=BULLETexclude---Directs the MacIPX gateway to serve all AppleTalk networks except those whose numbers are listed on the following lines.include---Directs the MacIPX gateway to serve only networks whose numbers are listed on the following lines; this is the default mode if no keyword appears.The networks listed can appear as a number or range. You can also specify additional network numbers or ranges by placing each network on its own line. For example, a MACIPXGW.DAT file can contain the following command:FORMAT="LINESPECIFIC"MOREINFO="NONE"exclude
10-20
100This instructs the MacIPX gateway to serve all AppleTalk networks except 10-20 and 100. Alternatively, a MACIPXGW.DAT file can contain the following command:FORMAT="LINESPECIFIC"MOREINFO="NONE"include
10-20
100
PAGENUM=46 ID="BP52"This instructs the MacIPX gateway to serve only AppleTalk networks 10-20 and 100, excluding all others.If no MACIPXGW.DAT file is found in SYS:SYSTEM, the MacIPX gateway serves all AppleTalk networks.The network numbers in these examples are AppleTalk network numbers, not IPX network numbers.After you have created the MACIPXGW.DAT file, you must unload the MacIPX gateway and reinitialize the system.RENDERAS="SECT3"ID="FM22040"Viewing MacIPX Gateway Configuration and Operation InformationTo view information about the configuration and operation of a IDXID="w1086"BOOK="_idx" COLLECTION="nw41" TIDREF="i2275"
loaded MacIPX gateway, type the following command at the NetWare server prompt:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD MACIPXGW SHOW=YES MOREINFO="NONE"<Enter>This command does not reload the MacIPX gateway, but instead displays information about the MacIPX gateway and the AppleTalk networks that it serves, as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"MACIPXGW:
Unicast threshold set at 1.
AppleTalk nets this gateway is configured
   to serve:
10-20    111    2222-2223    3333-3335FORMAT="LINESPECIFIC"MOREINFO="NONE"AppleTalk nodes registered for IPX broadcasts:
IPX node: 0xffffffffffff
  Socket: 0x452      10.238    1501.138    1502.168
  Socket: 0x453      10.128PAGENUM=46 ID="BP53"PAGENUM=47This information includes the following items:MARK=BULLETThe value for the unicast thresholdThe network numbers of all AppleTalk networks served by this gatewayAll AppleTalk nodes currently registered with the MacIPX gateway for broadcasts and identified by the IPX socketRENDERAS="SECT3"Viewing MacIPX Gateway StatisticsIDXID="w1087"BOOK="_idx" COLLECTION="nw41" TIDREF="i2275"
To view statistics pertaining to the IDXID="w1088"BOOK="_idx" COLLECTION="nw41" TIDREF="i2275"
MacIPX gateway, load MONITOR and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"LAN/WAN Information > Select CLASS=MENUITEM MOREINFO="NONE"MACIPXGWThe CLASS=MENUITEM MOREINFO="NONE"MACIPXGW window displays the statistics explained in IDREF="FM90556"Table 2-2.LABEL="2-2" PGWIDE=1 TOCENTRY="1"ID="FM90556"MacIPX Gateway Custom StatisticsCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="25*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"StatisticCOLNAME=2 ROTATE="0" MOREROWS="0"ExplanationVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Received Tickle PacketsCOLNAME=2 ROTATE="0" MOREROWS="0"Number of "tickle" packets sent by MacIPX clients served by the gateway. MacIPX clients send tickle packets to the MacIPX gateway; the gateway sends IPX broadcast packets back to that client.COLNAME=1 ROTATE="0" MOREROWS="0"IPX Broadcast Requests from IPX StackCOLNAME=2 ROTATE="0" MOREROWS="0"Number of IPX broadcast packets sent to the MacIPX gateway by the IPX stack in the NetWare server or router.COLNAME=1 ROTATE="0" MOREROWS="0"IPX Broadcast Requests from MacIPX ClientsCOLNAME=2 ROTATE="0" MOREROWS="0"Number of IPX broadcast packets sent to the MacIPX gateway by the MacIPX clients that the MacIPX gateway is servicing.COLNAME=1 ROTATE="0" MOREROWS="0"DDP Packets Broadcasted for IPX BroadcastsCOLNAME=2 ROTATE="0" MOREROWS="0"Number of AppleTalk packets sent out as broadcast packets carrying IPX broadcast packets.COLNAME=1 ROTATE="0" MOREROWS="0"DDP Packets Unicasted for IPX BroadcastsCOLNAME=2 ROTATE="0" MOREROWS="0"Number of AppleTalk packets sent out as unicast packets carrying IPX broadcast packets.COLNAME=1 ROTATE="0" MOREROWS="0"Received DDP Packets with Unknown OptionsCOLNAME=2 ROTATE="0" MOREROWS="0"Number of AppleTalk packets received by the MacIPX gateway that include unrecognized encapsulation demultiplexing options. This indicates corrupted packets or incompatible client software. Ensure that your network cabling is functioning correctly and that software on the Macintosh clients is compatible with this version of the MacIPX gateway.COLNAME=1 ROTATE="0" MOREROWS="0"Received DDP Packets with Wrong TypeCOLNAME=2 ROTATE="0" MOREROWS="0"Number of AppleTalk packets received by the gateway that include an incorrect AppleTalk packet type. This indicates the presence of corrupted packets or incompatible client software. Ensure that your network cabling is functioning correctly and that software on the Macintosh clients is compatible with this version of the MacIPX gateway.COLNAME=1 ROTATE="0" MOREROWS="0"Received Service RequestsCOLNAME=2 ROTATE="0" MOREROWS="0"Number of requests received by the MacIPX gateway to provide service to MacIPX clients.COLNAME=1 ROTATE="0" MOREROWS="0"Transmitted Service GrantsCOLNAME=2 ROTATE="0" MOREROWS="0"Number of times the MacIPX gateway granted service to the MacIPX clients.COLNAME=1 ROTATE="0" MOREROWS="0"Transmitted Service RefusalsCOLNAME=2 ROTATE="0" MOREROWS="0"Number of times the MacIPX gateway refused service to the MacIPX clients.COLNAME=1 ROTATE="0" MOREROWS="0"Memory Allocation FailureCOLNAME=2 ROTATE="0" MOREROWS="0"Number of times the MacIPX gateway could not allocate memory. You might need to add memory to the NetWare server to fix this problem.PAGENUM=48 ID="BP54"LABEL="3"PAGENUM=49 ID="BP55"ID="FM76970"Configuring IPNetWare® 4.1 software provides a set of configurable parameters with which you can modify operational characteristics of the Internet Protocol (IP), such as selecting its protocol and configuring it to run over a LAN connection.You configure IP for NetWare 4.1 by enabling the protocol, setting its various parameters, and binding it to a network interface. You configure all IP parameters from the Internetworking Configuration utility (INETCFG).The configuration you specify using INETCFG does not take effect automatically. To activate the configuration, exit INETCFG, then bring down and restart the server after you finish all configuration steps.This chapter covers advanced IP concepts and configuration procedures in the following sections:MARK=BULLETIDREF="FM26527""IP Configuration Decisions"This section presents a list of decisions you need to consider before configuring IP on the server. Each decision refers you to a section in this chapter---or another chapter in this guide---for configuration instructions and additional conceptual information.IDREF="FM33739""Configuring RIP"This section explains how to configure the server to use Routing Information Protocol (RIP) as its IP routing protocol.IDREF="FM12152""Configuring OSPF"This section explains how to configure the server to use Open Shortest Path First (OSPF) as its IP routing protocol.PAGENUM=49 ID="BP56"PAGENUM=50IDREF="FM30088""Configuring Static Routes on LAN Routers"This section describes static routes and explains how to configure them on the router or end node's IP LAN connections.IDREF="FM26096""Configuring Router Discovery"This section describes router discovery and explains how to configure it on an IP router or end node.IDREF="FM21545""Enabling ARP and Proxy ARP"This section describes Address Resolution Protocol (ARP) and Proxy ARP and explains how to enable them on an IP router.IDREF="FM35538""Enabling Directed Broadcast Forwarding"This section describes directed broadcast forwarding and explains how to configure it on an IP router.IDREF="FM21342""Configuring BootP Forwarding"This section describes BootP forwarding and explains how to configure it on an IP router or end node.IDREF="FM64935""Configuring Multiple Logical Interfaces"This section describes multiple logical interfaces and explains how to configure them on an IP router or end node.NetWare 4.1 uses IP to encapsulate Internetwork Packet ExchangeTM (IPXTM) packets and AppleTalk* packets. This is called IP tunneling and is covered in IDREF="FM71392"Chapter 2, "Configuring IPX," and IDREF="FM76890"Chapter 4, "Configuring AppleTalk."PAGENUM=50 ID="BP57"PAGENUM=51RENDERAS="SECT1"ID="FM26527"IP Configuration DecisionsIDXID="w1089"BOOK="_idx" COLLECTION="nw41" TIDREF="i1868"IDXID="w1090"BOOK="_idx" COLLECTION="nw41" TIDREF="i741"
How you configure IP beyond the most basic configuration depends on the following decisions:MARK=BULLETWhether to use the computer as a router or an end node (that is, host).IDXID="w1091"BOOK="_idx" COLLECTION="nw41" TIDREF="i1868"IDXID="w1092"BOOK="_idx" COLLECTION="nw41" TIDREF="i1912"
The CLASS=MENUITEM MOREINFO="NONE"IP Packet Forwarding parameter, which controls IP packet routing, is disabled by default. Enable this parameter if you want your computer to operate as an IP router; disable it if you want it to operate as an end node.Whether to use RIP, OSPF, or a mixed RIP-OSPF environment.IDXID="w1093"BOOK="_idx" COLLECTION="nw41" TIDREF="i1868"IDXID="w1094"BOOK="_idx" COLLECTION="nw41" TIDREF="i1868"IDXID="w1095"BOOK="_idx" COLLECTION="nw41" TIDREF="i3859"IDXID="w1096"BOOK="_idx" COLLECTION="nw41" TIDREF="i3128"
RIP and OSPF are IP routing protocols. If you already have IP routers in your network environment, use the same routing protocol they use. If your network currently has no other routers, use OSPF.To configure your server as a RIP router, see IDREF="FM33739""Configuring RIP."To configure your server as an OSPF router, see IDREF="FM12152""Configuring OSPF."Whether to use static routes on a LAN router.IDXID="w1097"BOOK="_idx" COLLECTION="nw41" TIDREF="i1868"IDXID="w1098"BOOK="_idx" COLLECTION="nw41" TIDREF="i4270"
Static routes are useful for reducing routing traffic, providing security, accessing isolated networks, and operating as backup routes on LANs. To configure static routes on a LAN router, see IDREF="FM30088""Configuring Static Routes on LAN Routers."Whether to filter routes or various TCP/IP packets.IDXID="w1099"BOOK="_idx" COLLECTION="nw41" TIDREF="i1868"IDXID="w1100"BOOK="_idx" COLLECTION="nw41" TIDREF="i1499"
Enable filters if you want to do any of the following:MARK=BULLETControl access to any services, such as File Transfer Protocol (FTP), on your network.Reduce the bandwidth consumed by routing traffic.PAGENUM=51 ID="BP58"PAGENUM=52To configure TCP/IP filters, you must enable the CLASS=MENUITEM MOREINFO="NONE"Filtering Support parameter from INETCFG and then load the Filter Configuration utility (FILTCFG). For more information, see IDREF="FM54089"Chapter 5, "Configuring Filters."Whether to configure router discovery.IDXID="w1101"BOOK="_idx" COLLECTION="nw41" TIDREF="i1868"IDXID="w1102"BOOK="_idx" COLLECTION="nw41" TIDREF="i3887"
Router discovery allows end nodes to find an IP router on their network. If your computer is operating as a router, it can advertise itself periodically as a router; if your computer is operating as an end node, it can send queries to locate a router.To configure router discovery, see IDREF="FM26096""Configuring Router Discovery."Whether to enable ARP or Proxy ARP.IDXID="w1103"BOOK="_idx" COLLECTION="nw41" TIDREF="i1868"IDXID="w1104"BOOK="_idx" COLLECTION="nw41" TIDREF="i1868"IDXID="w1105"BOOK="_idx" COLLECTION="nw41" TIDREF="i3616"
ARP is a LAN protocol that maps Internet addresses to physical addresses. IP routers and end nodes use ARP to determine a destination node's physical address.An IP router using Proxy ARP replies to ARP requests it receives through an interface on behalf of an end node on a network attached to another interface.To enable ARP or to configure Proxy ARP on your router, see IDREF="FM21545""Enabling ARP and Proxy ARP."Whether to enable the router to forward directed broadcasts.IDXID="w1106"BOOK="_idx" COLLECTION="nw41" TIDREF="i1868"IDXID="w1107"BOOK="_idx" COLLECTION="nw41" TIDREF="i1038"
A directed broadcast is a broadcast intended only for a specific group of nodes rather than all nodes on the network.To enable directed broadcast forwarding, see IDREF="FM35538""Enabling Directed Broadcast Forwarding."Whether to configure the router or end node as a BootP forwarder.IDXID="w1108"BOOK="_idx" COLLECTION="nw41" TIDREF="i1868"IDXID="w1109"BOOK="_idx" COLLECTION="nw41" TIDREF="i504"
The BootP protocol enables end nodes to get an IP address at startup time. As a BootP forwarder, the router or end node accepts and forwards BootP requests to a BootP server, which assigns the IP address.To configure BootP forwarding, see IDREF="FM21342""Configuring BootP Forwarding."Whether to configure multiple logical interfaces on a single board.PAGENUM=53 ID="BP59"IDXID="w1110"BOOK="_idx" COLLECTION="nw41" TIDREF="i1868"IDXID="w1111"BOOK="_idx" COLLECTION="nw41" TIDREF="i2564"
This enables you to bind more than one IP network to a LAN board to operate as separate logical interfaces.To configure multiple logical interfaces on a board, see IDREF="FM64935""Configuring Multiple Logical Interfaces."RENDERAS="SECT1"ID="FM33739"Configuring RIPIDXID="w1112"BOOK="_idx" COLLECTION="nw41" TIDREF="i1868"IDXID="w1113"BOOK="_idx" COLLECTION="nw41" TIDREF="i3859"
RIP is probably the most common IP routing protocol in use. As such, it is widely available and presents few obstacles to interoperability with other IP internetworks, most notably the Internet.RIP performs sufficiently well in small IP internetworks that have simple architectures and few routers. However, RIP reveals its limitations in the large, complex internetworks that have become common in government and private-sector organizations throughout the world. Its most apparent limitations are as follows:MARK=BULLETAll subnetworks must be contiguous.The entire network must use the same subnetwork mask.You cannot use subnet zero.RIP routes are limited to 15 hops.To overcome or ease some of these limitations, the internetworking community developed various enhancements to RIP. IDXID="w1114"BOOK="_idx" COLLECTION="nw41" TIDREF="i3859"IDXID="w1115"BOOK="_idx" COLLECTION="nw41" TIDREF="i1868"RIP II, for example, is an enhanced version of RIP that supports variable-length subnetwork masks by carrying a field that contains the subnetwork mask of the destination network. RIP also supports the use of subnet zero, whose addresses were reserved under the original IP specification. When configuring RIP, you can run RIP, RIP II, or both on a single interface.Not all third-party routers support RIP II.PAGENUM=53 ID="BP60"PAGENUM=54You can also enable IDXID="w1116"BOOK="_idx" COLLECTION="nw41" TIDREF="i3332"poison reverse on an interface. This is a mechanism that causes RIP to advertise a route back through the same path from which it learned the route, but with a hop count of 16---that is, unreachable. Although poison reverse prevents routing loops, the unreachable routes carried in each RIP packet increase the bandwidth consumed by RIP traffic. This increase becomes significant in large internetworks.RIP allows you to assign a cost value between 1 and 15 to each network interface you configure. This enables you to establish a preferred route according to the type of network media connected to the interface. For example, you might want to increase the cost of an interface that uses a slow link so that, given the choice, RIP uses the interface to a faster, less costly link. The default cost for each interface is 1; you should not increase this value on an interface unless you want to discourage its use as an eligible routing path.When choosing an IP routing protocol, consider the following "IDXID="w1117"BOOK="_idx" COLLECTION="nw41" TIDREF="i3906"
rules of thumb":MARK=BULLETIf the IP internetwork is small and uses no routing protocol besides RIP, continue using RIP.To configure RIP, see IDREF="FM57022""How to Configure RIP."However, if the network will continue to grow and perhaps become part of a larger IP internetwork, you should consider migrating the network from RIP to OSPF. For information about RIP-to-OSPF migration, see the BOOK="tcpipenu" COLLECTION="nw41"NetWare 4.1 TCP/IP Reference.If the internetwork uses variable-length subnetworks or has third-party routers that support RIP II, use RIP II or OSPF.To configure RIP II, see IDREF="FM57022""How to Configure RIP."To configure OSPF, see IDREF="FM37028""How to Configure OSPF."If the internetwork has some third-party routers that support RIP II and others that do not, use RIP and RIP II.For this purpose, you can enable RIP and RIP II simultaneously on a network interface. For instructions, see IDREF="FM57022""How to Configure RIP."PAGENUM=54 ID="BP61"PAGENUM=55If you are currently building a large IP internetwork, use OSPF.You can also run RIP and OSPF concurrently; for more information, see IDREF="FM12152""Configuring OSPF."For additional information about RIP and related topics, see the BOOK="tcpipenu" COLLECTION="nw41"NetWare 4.1 TCP/IP Reference.RENDERAS="SECT2"ID="FM57022"How to Configure RIPIDXID="w1118"BOOK="_idx" COLLECTION="nw41" TIDREF="i1868"IDXID="w1119"BOOK="_idx" COLLECTION="nw41" TIDREF="i3859"
To enable RIP routing and to configure RIP on a network interface, load INETCFG and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > (CLASS=MENUITEM MOREINFO="NONE"TCP/IP Protocol Configuration window appears)Complete the following steps:PERFORMANCE="REQUIRED"Make sure RIP routing is enabled globally: the CLASS=MENUITEM MOREINFO="NONE"RIP field should be set to CLASS=MENUITEM MOREINFO="NONE"Enabled.This is the default setting.If you want to disable RIP routing on a single interface, set the 
CLASS=MENUITEM MOREINFO="NONE"Status parameter to 
CLASS=MENUITEM MOREINFO="NONE"Disabled as described in 
IDREF="FM30552"Step 2.PERFORMANCE="REQUIRED"ID="FM30552"Press 
MOREINFO="NONE"<Esc> to return to the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu, then select the following path:Parameter Path: Select 
CLASS=MENUITEM MOREINFO="NONE"Bindings > Select a network interface > Select 
CLASS=MENUITEM MOREINFO="NONE"RIP Bind Options (
CLASS=MENUITEM MOREINFO="NONE"RIP Bind Options window appears)Configure the following parameters:
MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Status---Status of RIP routing on this interface. RIP routing is enabled by default; to disable RIP routing only on this interface, select this parameter, then select CLASS=MENUITEM MOREINFO="NONE"Disabled.CLASS=MENUITEM MOREINFO="NONE"RIP Mode---Version of RIP to use on this interface. Select one of the following options:---CLASS=MENUITEM MOREINFO="NONE"RIPI. Standard version of RIP used by most IP routers and end nodes. This is the default option.---CLASS=MENUITEM MOREINFO="NONE"RIPII. Enhanced version of RIP that supports variable-length subnetwork masks.PAGENUM=56 ID="BP62"---CLASS=MENUITEM MOREINFO="NONE"RIPI & RIPII. Both versions of RIP. Select this option if your internetwork has nodes that support only RIPI and subnetworks that have variable-length masks.---CLASS=MENUITEM MOREINFO="NONE"Send Only. Causes the router only to broadcast, in RIPI packets, the entries in its own routing table.Some end nodes learn routes only by listening to RIP, even if portions of the internetwork run OSPF. Select this option if you want the router to broadcast the OSPF routes in its RIPI packets so that every end node can learn all available routes.The 
CLASS=MENUITEM MOREINFO="NONE"RIP Bind Options window also includes the following parameters:
MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Cost of InterfaceCLASS=MENUITEM MOREINFO="NONE"Originate Default RouteIDXID="w1120"BOOK="_idx" COLLECTION="nw41" TIDREF="i3332"CLASS=MENUITEM MOREINFO="NONE"Poison ReverseBecause the default settings for these parameters are suitable for most IP networks, you should change them only for a specific purpose. Misconfiguring these parameters can increase routing traffic or cause loss of connectivity on your network. If you are unfamiliar with these parameters, refer to the BOOK="tcpipenu" COLLECTION="nw41"NetWare 4.1 TCP/IP Reference.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to return to the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu; save your changes when prompted.If you want these changes to take effect immediately, exit INETCFG, then bring down and restart the server. If you want to configure other IP parameters, do so now and restart the server when you are finished.RENDERAS="SECT1"ID="FM12152"Configuring OSPFIDXID="w1121"BOOK="_idx" COLLECTION="nw41" TIDREF="i1868"IDXID="w1122"BOOK="_idx" COLLECTION="nw41" TIDREF="i3128"
OSPF was developed to satisfy the need for a scalable, open-standards routing protocol for large IP internetworks. As a link state protocol, OSPF provides highly efficient routing and fast convergence.OSPF makes large internetworks more manageable by allowing you to partition them into administrative domains called areas. Areas impose a hierarchy to the internetwork. All OSPF areas are connected to a central backbone area by an Area Border Router (ABR). The ABR shares OSPF routing information between the area and the backbone.PAGENUM=57 ID="BP63"When configuring an OSPF area, you assign to it a four-byte decimal number called the Area ID. You also indicate which of the router's network interfaces belong to the area, and whether the area is a stub area.NetWare 4.1 supports the use of virtual links between OSPF routers. A virtual link "patches together" a partitioned backbone by creating a direct point-to-point link between the ABRs that connect the partitioned backbone areas through the transit area.Because of the complexity and high probability of misconfiguring virtual links, Novell recommends against using them on your network.Most IP internetworks in use today are not "pure" OSPF networks; that is, portions of these internetworks still employ other routing protocols, such as RIP. OSPF uses an IDXID="w1123"BOOK="_idx" COLLECTION="nw41" TIDREF="i3128"Autonomous System Boundary Router (ASBR) to import and propagate routing information from these protocols. When configuring OSPF, you can enable your router to operate as an ASBR. For an ASBR to import RIP routes learned through an interface, RIP must be enabled on that interface.Each OSPF router has its own IDXID="w1124"BOOK="_idx" COLLECTION="nw41" TIDREF="i3128"Router ID, a four-byte number that uniquely identifies the router and allows it to participate in informational exchanges with neighboring routers. The default Router ID is the IP address of the first interface bound to IP on the router. Although INETCFG allows you to change the Router ID, you should use the default unless you need a simpler numbering scheme for administrating several hundred routers on an internetwork.IDXID="w1125"BOOK="_idx" COLLECTION="nw41" TIDREF="i3128"IDXID="w1126"BOOK="_idx" COLLECTION="nw41" TIDREF="i351"
OSPF authenticates its packets by providing an authentication key---an eight-byte, alphanumeric password---in each OSPF packet header. OSPF authentication gives you administrative control over which routers participate in link state exchanges on the internetwork. A router without proper authentication is excluded from these exchanges and, essentially, from performing any OSPF routing whatsoever. NetWare 4.1 allows you to enable authentication for an area and to provide an authentication key for each network to which the router is connected.Unlike RIP, whose only criterion for choosing the best route is the hop count, OSPF allows you to assign a cost value to each network interface you configure. This enables you to establish a preferred route according to the type of network media connected to the interface. For example, you might want to increase the cost of an interface that uses a slow link so that, given the choice, OSPF uses the interface to a faster, less costly link.PAGENUM=58 ID="BP64"NetWare 4.1 allows you to run OSPF and RIP on the same router. You can run them separately on different interfaces or concurrently on a single interface. Although an ASBR must run both protocols so that it can import RIP routes and propagate them to other OSPF routers, you should not run both on too many other routers in your OSPF domain. Doing so consumes additional network bandwidth and router memory and might even create routing loops.For additional information about OSPF and related topics, see the BOOK="tcpipenu" COLLECTION="nw41"NetWare 4.1 TCP/IP Reference.RENDERAS="SECT2"ID="FM37028"How to Configure OSPFIDXID="w1127"BOOK="_idx" COLLECTION="nw41" TIDREF="i3128"
The extent to which you need to configure OSPF depends on the characteristics of your network, such as its size and topology, and whether it uses other IP routing protocols besides OSPF. To help you configure only what is necessary, this section provides the following procedures:MARK=BULLETIDREF="FM53035""Basic OSPF Configuration" This is the minimum configuration required to enable---or disable---OSPF routing on the entire router or on a single interface, and to enable the router to operate as an 
Autonomous System Boundary Router (ASBR).
MARK=BULLETIDREF="FM77088""OSPF Area Configuration"This is an optional configuration that explains how to set up OSPF routing areas and authentication.RENDERAS="SECT3"ID="FM53035"Basic OSPF ConfigurationIDXID="w1128"BOOK="_idx" COLLECTION="nw41" TIDREF="i3128"
To enable OSPF routing and to configure OSPF on a network interface, load INETCFG and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > (CLASS=MENUITEM MOREINFO="NONE"TCP/IP Protocol Configuration window appears)PAGENUM=58 ID="BP65"PAGENUM=59Complete the following steps:PERFORMANCE="REQUIRED"Select the CLASS=MENUITEM MOREINFO="NONE"OSPF field, then select CLASS=MENUITEM MOREINFO="NONE"Enabled.This enables OSPF routing globally on the router. If you want to disable OSPF routing on a single interface, set the 
CLASS=MENUITEM MOREINFO="NONE"Status parameter to 
CLASS=MENUITEM MOREINFO="NONE"Disabled as described in 
IDREF="FM83892"Step 4.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"OSPF Configuration.The 
CLASS=MENUITEM MOREINFO="NONE"OSPF Configuration window appears.PERFORMANCE="REQUIRED"Select the 
CLASS=MENUITEM MOREINFO="NONE"Autonomous System Boundary Router field, then select 
CLASS=MENUITEM MOREINFO="NONE"Enabled.Enabling this parameter allows the router to operate as an ASBR. In this capacity, the router advertises non-OSPF routes, such as those generated by RIP and EGP, as well as static routes and direct routes to the OSPF domain. This is necessary for preserving connectivity throughout an internetwork that uses other routing protocols besides OSPF.You do not need to enable this parameter on an internetwork that uses only OSPF.The 
CLASS=MENUITEM MOREINFO="NONE"OSPF Configuration window also includes the following parameters:
MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Router IDCLASS=MENUITEM MOREINFO="NONE"Virtual Link ConfigurationMost network configurations do not require you to change these parameters. To learn how they are used, refer to the BOOK="tcpipenu" COLLECTION="nw41"NetWare 4.1 TCP/IP Reference.PERFORMANCE="REQUIRED"ID="FM83892"Press 
MOREINFO="NONE"<Esc> to return to the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu, then select the following path:Parameter Path: Select 
CLASS=MENUITEM MOREINFO="NONE"Bindings > Select a network interface > Select 
CLASS=MENUITEM MOREINFO="NONE"OSPF Bind Options (
CLASS=MENUITEM MOREINFO="NONE"OSPF Bind Options window appears)The 
CLASS=MENUITEM MOREINFO="NONE"Status field indicates whether OSPF routing is active on this interface. OSPF routing is enabled by default; to disable OSPF routing only on this interface, select 
CLASS=MENUITEM MOREINFO="NONE"Status, then select 
CLASS=MENUITEM MOREINFO="NONE"Disabled.
PAGENUM=59 ID="BP66"PAGENUM=60The 
CLASS=MENUITEM MOREINFO="NONE"OSPF Bind Options window also includes the following parameters:
MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Cost of InterfaceCLASS=MENUITEM MOREINFO="NONE"PriorityCLASS=MENUITEM MOREINFO="NONE"Hello IntervalCLASS=MENUITEM MOREINFO="NONE"Router Dead IntervalBecause the default settings for these parameters are suitable for most IP networks, you should change them only for a specific purpose. Misconfiguring these parameters can increase routing traffic or cause loss of connectivity on your network. If you are unfamiliar with these parameters, refer to the BOOK="tcpipenu" COLLECTION="nw41"NetWare 4.1 TCP/IP Reference.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to return to the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu; save your changes when prompted.If you want these changes to take effect immediately, exit INETCFG, then bring down and restart the router. If you want to configure other IP parameters, do so now and restart the router when you are finished.RENDERAS="SECT4"ID="FM77088"OSPF Area ConfigurationIDXID="w1129"BOOK="_idx" COLLECTION="nw41" TIDREF="i3128"
To configure OSPF areas, load INETCFG and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > (CLASS=MENUITEM MOREINFO="NONE"TCP/IP Protocol Configuration window appears)Complete the following steps:PERFORMANCE="REQUIRED"Select CLASS=MENUITEM MOREINFO="NONE"OSPF Configuration.The 
CLASS=MENUITEM MOREINFO="NONE"OSPF Configuration window appears.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Area Configuration.The 
CLASS=MENUITEM MOREINFO="NONE"OSPF Areas 
window appears.This window lists the IDs of all areas to which the router belongs. If you have not configured an OSPF area on this router, the only area listed is 0.0.0.0, the 
backbone area.
PAGENUM=60 ID="BP67"PAGENUM=61PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Ins>.The 
CLASS=MENUITEM MOREINFO="NONE"OSPF Area Configuration window appears.PERFORMANCE="REQUIRED"Configure the following area parameters:
MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Area ID---Four-byte decimal number that identifies the area. For example, a valid Area ID is 85.8.0.11. If you enter a hexadecimal number, INETCFG converts it to decimal.For the router to belong to an area, the Area ID that identifies that area must be assigned to at least one of the router's interfaces. You assign an Area ID to an interface in IDREF="FM78191"Step 5.CLASS=MENUITEM MOREINFO="NONE"Authentication---Switch that enables or disables authentication for the area.If you enable authentication on this router, you must enable authentication on all other routers in the area. Also, all interfaces belonging to that area must have an authentication key. You provide the authentication key in IDREF="FM78191"Step 5.CLASS=MENUITEM MOREINFO="NONE"Area Type---Type of OSPF area, which can be CLASS=MENUITEM MOREINFO="NONE"Normal or CLASS=MENUITEM MOREINFO="NONE"Stub. All routers in the same area must agree on the area type.The backbone area (0.0.0.0) cannot be a stub area.CLASS=MENUITEM MOREINFO="NONE"Stub Cost---Cost of the default route advertised to the stub area.PERFORMANCE="REQUIRED"ID="FM78191"Press 
MOREINFO="NONE"<Esc> to return to the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu, then select the following path:Parameter Path: Select 
CLASS=MENUITEM MOREINFO="NONE"Bindings > Select a network interface > Select 
CLASS=MENUITEM MOREINFO="NONE"OSPF Bind Options (
CLASS=MENUITEM MOREINFO="NONE"OSPF Bind Options window appears)
MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Area ID---ID of the area to which this interface belongs. Press MOREINFO="NONE"<Enter> to see the list of available areas. Use the MOREINFO="NONE"<Up>- and MOREINFO="NONE"<Down>-arrow keys to highlight an area, then press MOREINFO="NONE"<Enter> to select it.CLASS=MENUITEM MOREINFO="NONE"Authentication Key---Eight-byte password that authenticates the router's OSPF packets to the area to which this interface belongs. Valid characters are 0-9, A-Z, a-z, underscore, and dash.All interfaces within the same area are not required to have the same authentication key; however, all interfaces connected to the same network must have the same authentication key.The CLASS=MENUITEM MOREINFO="NONE"Authentication parameter must be enabled for the area you select.PAGENUM=62 ID="BP68"PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to return to the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu; save your changes when prompted.If you want these changes to take effect immediately, exit INETCFG, then bring down and restart the router. If you want to configure other IP parameters, do so now and restart the router when you are finished.RENDERAS="SECT1"ID="FM30088"Configuring Static Routes on LAN RoutersIDXID="w1130"BOOK="_idx" COLLECTION="nw41" TIDREF="i4270"IDXID="w1131"BOOK="_idx" COLLECTION="nw41" TIDREF="i1868"
NetWare 4.1 allows you to configure remote routes manually on a LAN router as static routes.Static routes are useful if you want to do any of the following on your network:MARK=BULLETEliminate routing traffic, which makes more bandwidth available for data.Limit user access to one portion of the network. (If a single static route for a network is configured on a router, users on the same network as the router can gain access only to those systems on the destination network specified by the static route.)Gain access to isolated areas of the network, which is useful if dealing with legacy network topologies.Gain access to a network more than 15 hops away.Use a static route as a backup route to dynamic routes.RENDERAS="SECT2"How to Configure a Static Route Between Two LAN RoutersIDXID="w1132"BOOK="_idx" COLLECTION="nw41" TIDREF="i4270"IDXID="w1133"BOOK="_idx" COLLECTION="nw41" TIDREF="i1868"
To configure a static route on a LAN router, load INETCFG and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > (CLASS=MENUITEM MOREINFO="NONE"TCP/IP Protocol Configuration window appears)PAGENUM=62 ID="BP69"PAGENUM=63Complete the following steps:PERFORMANCE="REQUIRED"Configure the following static route parameters:MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Static Routing---Enables static routing on the router.Select this field, then select CLASS=MENUITEM MOREINFO="NONE"Enabled.CLASS=MENUITEM MOREINFO="NONE"Static Routing Table---Entry point to the static route configuration parameters.Press MOREINFO="NONE"<Ins> and configure the following parameters:---CLASS=MENUITEM MOREINFO="NONE"Route to Network or Host. Destination at the other end of the static route, which can be a single IP host or an IP network (that is, a group of hosts).You can also select CLASS=MENUITEM MOREINFO="NONE"Default Route. If the router must forward a packet for which it can find no destination in its routing table, it sends it to the next hop, which could be a default router. If the router has no other place to send the packet, it sends it to this address instead of discarding it. This type of "blind forwarding" keeps a packet on the network until a router can forward it to its final destination.---CLASS=MENUITEM MOREINFO="NONE"IP Address of Network/Host. Address of the destination network or host. To select from a list of symbolic network names and addresses, press MOREINFO="NONE"<Ins>.---CLASS=MENUITEM MOREINFO="NONE"Subnetwork Mask. If the destination is an IP network, the subnetwork mask of that network.---CLASS=MENUITEM MOREINFO="NONE"Next Hop Type. Indicates whether the next hop on the static route is an IP address or a WAN Call Destination.Select CLASS=MENUITEM MOREINFO="NONE"Gateway IP Address if you are configuring a static route on a LAN router.---CLASS=MENUITEM MOREINFO="NONE"Next Hop Router on Route. Explicit destination of the next hop.---CLASS=MENUITEM MOREINFO="NONE"Metric for this route. Number of hops to the destination. This metric is directly proportional to the cost of the route. Given two routes to the same destination, the router chooses the lower-cost route.PAGENUM=63 ID="BP70"PAGENUM=64If you want to use the static route as a backup route to a dynamic route, select a value that is higher than the cost associated with the dynamic route to ensure that the dynamic route remains the preferred route under normal conditions.Do not set this metric value to 16 unless you want to disable the route.---CLASS=MENUITEM MOREINFO="NONE"Type of route. Specifies whether the static route is active or passive.If the static route is active, and the router discovers a lower-cost dynamic route to the same destination, it uses the lower-cost route instead of the active static route. If the lower-cost route becomes unavailable, the router returns to using the active static route.A passive static route is always used, regardless of whether the router discovers a lower-cost route to the same destination.If you want to use the static route as a backup route, select CLASS=MENUITEM MOREINFO="NONE"Active.PERFORMANCE="REQUIRED"Complete the following steps to disable the routing protocol at the interface:PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Select the following parameter path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select the network interface > Select CLASS=MENUITEM MOREINFO="NONE"Expert TCP/IP Bind Options (CLASS=MENUITEM MOREINFO="NONE"Expert TCP/IP WAN Options window appears)PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"RIP Bind Options.Select the CLASS=MENUITEM MOREINFO="NONE"Status field, then select CLASS=MENUITEM MOREINFO="NONE"Disabled.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"OSPF Bind Options.Select the CLASS=MENUITEM MOREINFO="NONE"Status field, then select CLASS=MENUITEM MOREINFO="NONE"Disabled.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to return to the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu; save your changes when prompted.If you want these changes to take effect immediately, exit INETCFG, then bring down and restart the router. If you want to configure other IP parameters, do so now and restart the router when you are finished.
PAGENUM=65 ID="BP71"RENDERAS="SECT1"ID="FM26096"Configuring Router DiscoveryIDXID="w1134"BOOK="_idx" COLLECTION="nw41" TIDREF="i3887"IDXID="w1135"BOOK="_idx" COLLECTION="nw41" TIDREF="i1868"
IP routers and end nodes can both use the ICMP Router Discovery Protocol. Routers use it to advertise themselves as an IP router and to answer queries from end nodes; end nodes use it to locate an IP router on their network.For an end node to locate an IP router by this method, it must also support the ICMP Router Discovery Protocol.RENDERAS="SECT2"How to Configure Router DiscoveryIDXID="w1136"BOOK="_idx" COLLECTION="nw41" TIDREF="i1868"IDXID="w1137"BOOK="_idx" COLLECTION="nw41" TIDREF="i3887"
To configure router discovery on an interface, load INETCFG and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select the network interface > Select CLASS=MENUITEM MOREINFO="NONE"Expert TCP/IP Bind Options > Select CLASS=MENUITEM MOREINFO="NONE"Router Discovery Options (CLASS=MENUITEM MOREINFO="NONE"Router Discovery window appears)Configure the following parameters:MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Status---Select this field, then select CLASS=MENUITEM MOREINFO="NONE"Enabled.CLASS=MENUITEM MOREINFO="NONE"Destination Address---Method by which the IP router or end node sends router discovery packets.Select one of the following options:MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Broadcast---Sends the packets to all nodes on the network.CLASS=MENUITEM MOREINFO="NONE"Router Discovery Multicast---Sends the packets to an IP multicast address used specifically for router discovery exchanges. The packets are received only by nodes that understand this multicast address.Press MOREINFO="NONE"<Esc> to return to the CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu; save your changes when prompted.If you want these changes to take effect immediately, exit INETCFG, then bring down and restart the router. If you want to configure other IP parameters, do so now and restart the router when you are finished.PAGENUM=66 ID="BP72"RENDERAS="SECT1"ID="FM21545"Enabling ARP and Proxy ARPIDXID="w1138"BOOK="_idx" COLLECTION="nw41" TIDREF="i1868"IDXID="w1139"BOOK="_idx" COLLECTION="nw41" TIDREF="i1868"IDXID="w1140"BOOK="_idx" COLLECTION="nw41" TIDREF="i101"IDXID="w1141"BOOK="_idx" COLLECTION="nw41" TIDREF="i3616"
IP routers and end nodes use ARP to determine the physical address of a node to which they want to send a packet. For one node to send a packet to another, the sending node must know the physical address of the destination node. The sending node, knowing only the destination IP address, first checks its ARP table for an entry that maps the destination IP address to the destination physical address. If the sending node finds the entry, it inserts the physical address into the packet and sends it. If the sending node does not find the entry in its ARP table, it broadcasts an ARP address request to the network. The destination node replies to the request with its own physical address, which the sending node uses to send the packet, and adds to its ARP table for future use.ARP is enabled by default.An IP router uses Proxy ARP when devices attached to one of its interfaces do not support IP subnetworking and are unaware that they must go through the router to reach devices on other subnetworks of the same IP network. A router using Proxy ARP replies to ARP requests intended for devices on other subnetworks but does so only if the device is reachable through the router. The router determines whether the device is reachable by examining its own routing table.Proxy ARP is required on ARP subnetwork routers, which support routing within a subnetworked IP network having hosts that do not recognize subnetworking.Proxy ARP is also required on the parent network of a stub subnetwork. The parent network has an IP address range that includes the IP address range of the stub subnetwork. The router responds to ARP requests sent on the parent network on behalf of devices on the stub subnetwork.When both the parent and stub subnetwork are bound to IP interfaces, the router can detect the parent/stub subnetwork and automatically enable Proxy ARP for the appropriate interfaces. Even if Proxy ARP is not required, and not automatically enabled, you can still force it to be enabled with the CLASS=MENUITEM MOREINFO="NONE"Force Proxy ARP parameter.You must enable CLASS=MENUITEM MOREINFO="NONE"Force Proxy ARP on each interface on which the router must reply to ARP requests for destinations it can reach.CLASS=MENUITEM MOREINFO="NONE"Force Proxy ARP is disabled on each interface by default.PAGENUM=67 ID="BP73"RENDERAS="SECT2"How to Enable ARPIDXID="w1142"BOOK="_idx" COLLECTION="nw41" TIDREF="i1868"IDXID="w1143"BOOK="_idx" COLLECTION="nw41" TIDREF="i101"
To enable ARP on a network interface, load INETCFG and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select the network interface > Select CLASS=MENUITEM MOREINFO="NONE"Expert TCP/IP Bind Options (CLASS=MENUITEM MOREINFO="NONE"Expert TCP/IP LAN/WAN Options window appears)Select the CLASS=MENUITEM MOREINFO="NONE"Use of ARP field, then select CLASS=MENUITEM MOREINFO="NONE"Enabled.Press MOREINFO="NONE"<Esc> to return to the CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu; save your change when prompted.If you want this change to take effect immediately, exit INETCFG, then bring down and restart the router. If you want to configure other IP parameters, do so now and restart the router when you are finished.RENDERAS="SECT2"How to Enable Proxy ARPIDXID="w1144"BOOK="_idx" COLLECTION="nw41" TIDREF="i1868"IDXID="w1145"BOOK="_idx" COLLECTION="nw41" TIDREF="i3616"
To enable Proxy ARP on a network interface, load INETCFG and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select the network interface > Select CLASS=MENUITEM MOREINFO="NONE"Expert TCP/IP Bind Options (CLASS=MENUITEM MOREINFO="NONE"Expert TCP/IP LAN/WAN Options window appears)Select the CLASS=MENUITEM MOREINFO="NONE"Force Proxy ARP field, then select CLASS=MENUITEM MOREINFO="NONE"Enabled.Press MOREINFO="NONE"<Esc> to return to the CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu; save your change when prompted.If you want this change to take effect immediately, exit INETCFG, then bring down and restart the router. If you want to configure other IP parameters, do so now and restart the router when you are finished.PAGENUM=67 ID="BP74"PAGENUM=68RENDERAS="SECT1"ID="FM35538"Enabling Directed Broadcast ForwardingIDXID="w1146"BOOK="_idx" COLLECTION="nw41" TIDREF="i1868"IDXID="w1147"BOOK="_idx" COLLECTION="nw41" TIDREF="i1038"
A directed broadcast is a broadcast intended only for a specific group of nodes rather than all nodes on the network. For example, the broadcast address 255.255.255.255 reaches all nodes on a network; the directed broadcast address 128.1.255.255 is intended only for nodes whose network address is 128.1. A router not directly attached to 128.1 simply forwards the directed broadcast packet to the next hop. A router on network 128.1---if it has directed broadcast forwarding enabled---accepts and forwards the packet to all nodes whose network address is 128.1. Routers connecting subnetworks of 128.1 also accept and forward the packet to the nodes on their respective subnetworks.For all nodes on 128.1 to receive the directed broadcast, each router attached to network 128.1 must have directed broadcast forwarding enabled.RENDERAS="SECT2"How to Enable Directed Broadcast ForwardingIDXID="w1148"BOOK="_idx" COLLECTION="nw41" TIDREF="i1038"IDXID="w1149"BOOK="_idx" COLLECTION="nw41" TIDREF="i1868"
To enable the router to forward directed broadcasts for its network, load INETCFG and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Expert Configuration Options (CLASS=MENUITEM MOREINFO="NONE"TCP/IP Expert Configuration window appears)Select the CLASS=MENUITEM MOREINFO="NONE"Directed Broadcast Forwarding field, then select CLASS=MENUITEM MOREINFO="NONE"Enabled.Press MOREINFO="NONE"<Esc> to return to the CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu; save your change when prompted.If you want this change to take effect immediately, exit INETCFG, then bring down and restart the router. If you want to configure other IP parameters, do so now and restart the router when you are finished.RENDERAS="SECT1"ID="FM21342"Configuring BootP ForwardingIDXID="w1150"BOOK="_idx" COLLECTION="nw41" TIDREF="i1868"IDXID="w1151"BOOK="_idx" COLLECTION="nw41" TIDREF="i504"
BootP is a protocol that enables end nodes to get its IP address from a BootP server at startup time. If there is a BootP server on your internetwork, you can configure your IP router to accept and forward BootP requests to the BootP server.PAGENUM=69 ID="BP75"RENDERAS="SECT2"How to Configure the Router as a BootP ForwarderIDXID="w1152"BOOK="_idx" COLLECTION="nw41" TIDREF="i1868"IDXID="w1153"BOOK="_idx" COLLECTION="nw41" TIDREF="i504"
To configure the router as a BootP forwarder, load INETCFG and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Expert Configuration Options > Select CLASS=MENUITEM MOREINFO="NONE"BootP Forwarding Configuration (CLASS=MENUITEM MOREINFO="NONE"BootP Configuration Options window appears)Complete the following steps:PERFORMANCE="REQUIRED"Select the CLASS=MENUITEM MOREINFO="NONE"BootP Packet Forwarding field, then select CLASS=MENUITEM MOREINFO="NONE"Enabled.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"BootP Server List.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Ins>.PERFORMANCE="REQUIRED"Type the IP address of the BootP server at the prompt, then press 
MOREINFO="NONE"<Enter>.The server address appears in the 
CLASS=MENUITEM MOREINFO="NONE"BootP Servers window.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc>.PERFORMANCE="REQUIRED"If you want to record the activity of the BootP forwarder, select 
CLASS=MENUITEM MOREINFO="NONE"Log Operation, then select one of the following options:
MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Log to BootP Screen---Logs BootP activity to the BootP screen. This is a separate screen that you can select and monitor from the NetWare console. The information logged to this screen is not saved to a file.CLASS=MENUITEM MOREINFO="NONE"Log to File---Logs BootP activity to the SYS:\ETC\BOOTP.LOG file by default.To use a different file, type its full pathname in the CLASS=MENUITEM MOREINFO="NONE"Log File field.PERFORMANCE="REQUIRED"If you do not want to record the activity of the BootP forwarder, select the 
CLASS=MENUITEM MOREINFO="NONE"Do Not Log option.
PAGENUM=69 ID="BP76"PAGENUM=70PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to return to the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu; save your changes when prompted.If you want these changes to take effect immediately, exit INETCFG, then bring down and restart the router. If you want to configure other IP parameters, do so now and restart the router when you are finished.RENDERAS="SECT1"ID="FM64935"Configuring Multiple Logical InterfacesIDXID="w1154"BOOK="_idx" COLLECTION="nw41" TIDREF="i1868"IDXID="w1155"BOOK="_idx" COLLECTION="nw41" TIDREF="i2564"
NetWare 4.1 allows you to bind more than one IP network to a LAN board---board using multiaccess mode---to operate as separate logical interfaces. The ability to configure multiple logical interfaces simplifies the task of managing a growing network in the following ways:MARK=BULLETYou can merge two separate networks that were previously joined by a router.The section IDREF="FM51310""Merging Two Networks When the Connecting Router Fails" describes how to do this.You can move hosts from one IP network to another without losing connectivity.The section IDREF="FM95977""Reassigning IP Addresses" describes how to do this.You can add new nodes to a nearly full subnetwork.The section IDREF="FM99932""Adding New Nodes to a Full Subnetwork" describes how to do this.To attach more than one IP network to LAN board, bind IP to the board as many times as necessary, supplying a different IP address for each network.IDXID="w1156"BOOK="_idx" COLLECTION="nw41" TIDREF="i748"PAGENUM=70 ID="BP77"PAGENUM=71RENDERAS="SECT2"ID="FM51310"Merging Two Networks When the Connecting Router FailsIDXID="w1157"BOOK="_idx" COLLECTION="nw41" TIDREF="i1868"IDXID="w1158"BOOK="_idx" COLLECTION="nw41" TIDREF="i2405"IDXID="w1159"BOOK="_idx" COLLECTION="nw41" TIDREF="i748"IDXID="w1160"BOOK="_idx" COLLECTION="nw41" TIDREF="i3889"
Suppose a router that connects IP networks 130.81.0.0 and 167.10.0.0 fails. For simplicity, both use Ethernet as the physical medium. If the router cannot be repaired quickly, you can implement a temporary fix as follows:PERFORMANCE="REQUIRED"Join the two networks into a single network segment, using a barrel connector, a repeater, or other appropriate means.PERFORMANCE="REQUIRED"Find two working NetWare 
4.1 systems connected to the joined network.PERFORMANCE="REQUIRED"Load INETCFG on each system and select the following path:Parameter Path: Select 
CLASS=MENUITEM MOREINFO="NONE"Protocols > Select 
CLASS=MENUITEM MOREINFO="NONE"TCP/IPPERFORMANCE="REQUIRED"Set 
CLASS=MENUITEM MOREINFO="NONE"IP Packet Forwarding to 
CLASS=MENUITEM MOREINFO="NONE"Enabled ("Router").PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> until you return to the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu; save your change when prompted.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Bindings, then bind IP to the joined network 
twice as follows:PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Select one of the interfaces connected to the joined network.PERFORMANCE="REQUIRED"Set 
CLASS=MENUITEM MOREINFO="NONE"Local IP Address to 130.81.23.44.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc>, then save your change when prompted.PERFORMANCE="REQUIRED"Select the 
second interface connected to the joined network.PERFORMANCE="REQUIRED"Set 
CLASS=MENUITEM MOREINFO="NONE"Local IP Address to 167.10.17.52.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc>, then save your change when prompted.PERFORMANCE="REQUIRED"Exit INETCFG.PERFORMANCE="REQUIRED"Bring down and restart each system.
PAGENUM=72 ID="BP78"RENDERAS="SECT2"ID="FM95977"Reassigning IP AddressesIDXID="w1161"BOOK="_idx" COLLECTION="nw41" TIDREF="i1868"IDXID="w1162"BOOK="_idx" COLLECTION="nw41" TIDREF="i1909"IDXID="w1163"BOOK="_idx" COLLECTION="nw41" TIDREF="i748"IDXID="w1164"BOOK="_idx" COLLECTION="nw41" TIDREF="i107"
Suppose you need to change network number 89 to 130.57. Without multiple logical interfaces, you must change all IP addresses on network 89 at the same time to avoid losing connectivity to any hosts. With multiple logical interfaces, you can assign the new IP addresses gradually. Networks 89 and 130.57 can coexist on the same network segment until the transition is complete. The router interfaces, attached to both logical networks, forward packets for each network and route packets between the two.RENDERAS="SECT2"ID="FM99932"Adding New Nodes to a Full SubnetworkIDXID="w1165"BOOK="_idx" COLLECTION="nw41" TIDREF="i748"IDXID="w1166"BOOK="_idx" COLLECTION="nw41" TIDREF="i1379"
Suppose you want to add several new nodes to a subnetwork that has no more available IP addresses. Assume that the network has enough free connectors available.First, you assign a new subnetwork number to the cable so that both subnetworks share the cable. You then add new nodes by binding their IP address to the new logical subnetwork. The router whose interface is bound to both subnetwork addresses provides connectivity between the two subnetworks and to the rest of the internetwork.LABEL="4"PAGENUM=73 ID="BP79"ID="FM76890"Configuring AppleTalkThe AppleTalk for NetWare® protocol offers a set of configurable parameters you can use to modify the default characteristics of the protocol or to configure AppleTalk to run over an IP tunnel.You can configure AppleTalk for NetWare 4.1 by enabling the protocol, setting its various options, and binding the protocol to a network interface. All AppleTalk options can be configured or changed by running the Internetworking Configuration utility (INETCFG). This chapter covers advanced configuration concepts and procedures for AppleTalk and includes the following sections:MARK=BULLETIDREF="FM18710""Understanding General AppleTalk Concepts"This section discusses concepts you need to understand for all AppleTalk configurations. In addition to this information, you can find the concepts for specific configurations of AppleTalk explained with the configuration information.IDREF="FM19247""AppleTalk Configuration Decisions"This section lists the decisions you need to make before configuring AppleTalk.IDREF="FM39539""Configuring Basic AppleTalk Parameters"This section describes how to configure parameters that are used for all AppleTalk configurations.IDREF="FM38831""Configuring AppleTalk as an End Node"This section describes how to configure AppleTalk to behave as an end node rather than a server.PAGENUM=73 ID="BP80"PAGENUM=74IDREF="FM42920""Configuring AppleTalk for LAN Connections"This section describes how to configure and bind AppleTalk to run over a LAN. IDREF="FM69353""Configuring AppleTalk to Use the IP Tunnel (AURP)"This section describes how to enable AppleTalk to use the IP tunnel to route AppleTalk packets through an IP internetwork.This chapter helps you configure advanced options for AppleTalk for the NetWare 4.1 software. During NetWare 4.1 basic protocol configuration, default protocol parameters were set, and the network protocols were bound to network interface boards. You can configure the options explained in this chapter if your needs extend beyond the basic configuration.RENDERAS="SECT1"ID="FM18710"Understanding General AppleTalk ConceptsIDXID="w1167"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"
AppleTalk can be routed over a LAN by using the NetWare 4.1 software. You can configure AppleTalk to provide application support through the internal network or to a bound interface, and to tunnel AppleTalk through IP. This section discusses the following AppleTalk for NetWare concepts that impact AppleTalk configuration to run over a LAN:MARK=BULLETIDREF="FM22412""AppleTalk Addressing"IDREF="FM33459""Seeding"IDREF="FM80889""Internal Networks"IDREF="FM68332""Filtering"PAGENUM=74 ID="BP81"PAGENUM=75RENDERAS="SECT2"ID="FM22412"AppleTalk AddressingIDXID="w1168"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"IDXID="w1169"BOOK="_idx" COLLECTION="nw41" TIDREF="i107"
AppleTalk addressing consists of a network number and a node number. Each node acquires a unique 8-bit node number dynamically when it connects to the network. The node tries to use the same address when it connects to the network again. If the address is not available, then it tries other numbers until it finds a unique address.The network portion of the address, as well as the zone assignments, can be of two forms, depending on whether the network is an extended or a nonextended network.IDXID="w1170"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"IDXID="w1171"BOOK="_idx" COLLECTION="nw41" TIDREF="i252"IDXID="w1172"BOOK="_idx" COLLECTION="nw41" TIDREF="i4875"
An AppleTalk zone is a logical grouping of devices that enables users to locate and access network services, such as printing. A zone name is a logical name associated with some or all the services on a network or set of networks.IDXID="w1173"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"IDXID="w1174"BOOK="_idx" COLLECTION="nw41" TIDREF="i2962"
A nonextended network supports Phase 1 network addressing. On a phase 1 network, you assign a single network number and a single zone to each network. This limits the total number of nodes per network to 254. A Phase 1 network does not support extended Phase 2 addressing, and can only communicate with a Phase 2 network if the networks are connected by a router.IDXID="w1175"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"IDXID="w1176"BOOK="_idx" COLLECTION="nw41" TIDREF="i1395"
An extended network supports Phase 2 network addressing. On a Phase 2 network, you assign a range of network numbers, rather than a single network number, to each network, and can assign up to 255 zone names. Each network number supports up to 253 nodes. This scheme increases the number of nodes per network to the size of the range by 253.On nonextended networks, each node acquires the assigned network number, and finds an unused node number on the network. On extended networks, each node acquires a startup network number by choosing a number from a reserved "startup range" (65,280 through 65,534), and then acquiring a node number that is unused on the network. With these startup numbers, the node can communicate with the router and acquire a valid network number from the configured range for the network.PAGENUM=76 ID="BP82"RENDERAS="SECT2"ID="FM33459"SeedingThe network and zone configuration is propagated throughIDXID="w1177"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"IDXID="w1178"BOOK="_idx" COLLECTION="nw41" TIDREF="i4005"seed routers. A seed router can teach other routers on a network about the network and zone configuration. A IDXID="w1179"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"IDXID="w1180"BOOK="_idx" COLLECTION="nw41" TIDREF="i2974"non-seed router (or learning router) learns its configuration information from the seed router. For a nonextended network, the seed router is configured with the network number and zone name for the network. For an extended network, the seed router is configured with a network range and a zones list for the network. At least one router on the network must be a seed router. The seeding state is configured for each interface individually.RENDERAS="SECT2"ID="FM80889"Internal NetworksIDXID="w1181"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"IDXID="w1182"BOOK="_idx" COLLECTION="nw41" TIDREF="i1853"
An internal network is a virtual network contained within the AppleTalk module; it has no physical components, and it appears to the server as if it were just one of a number of networks to which the server is connected. The internal network supports two nodes, the AppleTalk stack (node 1 on the internal network), and the AppleTalk router (node 2 on the internal network).Packets must be routed from an external network interface to the internal network. Because the internal network requires an address, it takes up a network number. If you configure AppleTalk without configuring an internal network, you must configure one of the bound interfaces to allow application support.You configure the internal network to enable AppleTalk application support. The internal network is an extended network, and it allows you to configure multiple zones. If you choose to configure only one zone for the internal network, you must advertise all of a server's print queues and other services in a single zone. With an internal network, you can advertise services on any internal network zone. You configure the internal network following the same rules as when you configure an external, physical network, with these conditions:MARK=BULLETA range of one is required.You cannot specify multiple zones for the internal network of a router that uses transition routing.AFP file services are always advertised in the default zone.PAGENUM=77 ID="BP83"If you have many NetWare AppleTalk servers, the number of internal networks might create a large amount of periodic routing update traffic.The following are the advantages of using an internal network:MARK=BULLETThe internal network is of equal distance from every bound interface. This ensures the use of the most optimal route all the time.If the hardware for a bound interface becomes nonoperational, the end stations on that network can still communicate with the applications if there is another path.The following are the advantages of using a bound interface for application support instead of the internal network:MARK=BULLETFor every router, you do not need to maintain an extra network only for application support.Packets received at the selected interface do not require the additional hop required to reach the internal network.RENDERAS="SECT2"ID="FM68332"FilteringIDXID="w1183"BOOK="_idx" COLLECTION="nw41" TIDREF="i1499"IDXID="w1184"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"
AppleTalk provides two types of filtering: device hiding filtering and routing information filtering.Device hiding filters restrict service access by filtering out the packets that advertise services. Routing filters restrict the exchange of routing information between routers. Routing filters are of two types: route advertisement filters and route acceptance filters.AppleTalk routing information filters are applicable to zones and networks, but they cannot be used for specific nodes.Enable filtering support when you want to restrict the packets that a router sends and receives. If you enable this option, you must use FILTCFG to configure the filtering options. PAGENUM=78 ID="BP84"RENDERAS="SECT1"ID="FM19247"AppleTalk Configuration DecisionsIDXID="w1185"BOOK="_idx" COLLECTION="nw41" TIDREF="i741"IDXID="w1186"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"
This section provides you with information to decide if a feature is useful in your environment and on how a feature should be configured to fit your needs. How you configure AppleTalk beyond the most basic configuration depends on the following decisions:MARK=BULLETWhether to use the computer as a router or as an end nodeCLASS=OPTION MOREINFO="NONE".IDXID="w1187"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"IDXID="w1188"BOOK="_idx" COLLECTION="nw41" TIDREF="i3174"
The CLASS=MENUITEM MOREINFO="NONE"Packet Forwarding parameter controls AppleTalk routing. Enable this parameter if you want your computer to operate as an AppleTalk router; disable it if you want your computer to operate as an end node.Select an end node configuration if you are only using NetWare for AppleTalk to support applications, and you already have an AppleTalk router that provides connectivity to other networks.For more information, see IDREF="FM38831""Configuring AppleTalk as an End Node."Whether your network supports Phase 1 or Phase 2 addressingCLASS=OPTION MOREINFO="NONE".IDXID="w1189"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"IDXID="w1190"BOOK="_idx" COLLECTION="nw41" TIDREF="i3174"
The CLASS=MENUITEM MOREINFO="NONE"Type of Packet Forwarding option you select depends on the type of AppleTalk addressing your network supports. The default is CLASS=MENUITEM MOREINFO="NONE"Phase 2. Select CLASS=MENUITEM MOREINFO="NONE"Transition (Phase 1 and Phase 2) if you need to connect to Phase 1 routers. For more information, see IDREF="FM22412""AppleTalk Addressing."Whether to use an internal network.IDXID="w1191"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"IDXID="w1192"BOOK="_idx" COLLECTION="nw41" TIDREF="i1853"
The CLASS=MENUITEM MOREINFO="NONE"Internal Network, CLASS=MENUITEM MOREINFO="NONE"Network Number, and CLASS=MENUITEM MOREINFO="NONE"Network Zone(s) List parameters let you configure an internal network to enable application support on the internal network. For more information, see IDREF="FM80889""Internal Networks."Whether to filter routes or services.IDXID="w1193"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"IDXID="w1194"BOOK="_idx" COLLECTION="nw41" TIDREF="i1499"
Enable CLASS=MENUITEM MOREINFO="NONE"Filtering Support if you want to control access to services on your network. This also reduces the bandwidth consumed by routing traffic. Once you enable the CLASS=MENUITEM MOREINFO="NONE"Filtering Support parameter, you must use the Filter Configuration utility (FILTCFG) to configure the filters. For more information, see IDREF="FM68332""Filtering," and IDREF="FM54089"Chapter 5, "Configuring Filters."PAGENUM=79 ID="BP85"Whether you need AURP.IDXID="w1195"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"IDXID="w1196"BOOK="_idx" COLLECTION="nw41" TIDREF="i349"
AURP enables AppleTalk packets to be routed through an IP tunnel. Also, unlike RTMP, routing information is exchanged only when there is a change in network topologies. AURP is a more economical way to provide AppleTalk connectivity between two sites because less bandwidth is used to exchange routing information.To configure AURP, use the CLASS=MENUITEM MOREINFO="NONE"Tunnel AppleTalk Through IP (AURP) and AURP configuration parameters. For more information, see IDREF="FM69353""Configuring AppleTalk to Use the IP Tunnel (AURP)."Whether your router will be a seed router.IDXID="w1197"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"IDXID="w1198"BOOK="_idx" COLLECTION="nw41" TIDREF="i4005"
A CLASS=MENUITEM MOREINFO="NONE"seed router propagates network and zone configuration information to other routers in the network. A CLASS=MENUITEM MOREINFO="NONE"non-seed router learns its configuration information from the seed router. At least one router on an AppleTalk network must be a seed router. the seeding state is configured for each interface individually. Not all seed routers learn the network number and zone name from active routers on the network. Therefore, if you need to reconfigure the addressing of the network, you only need to change the configuration on the seed router and restart all the routers, rather than reconfiguring all the routers.For more information, see IDREF="FM33459""Seeding."RENDERAS="SECT1"ID="FM39539"Configuring Basic AppleTalk ParametersIDXID="w1199"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"
The basic AppleTalk configuration parameters modify the default behavior of the protocol and how it is used for LAN connections. To access the basic AppleTalk configuration parameters, load INETCFG and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"AppleTalkPAGENUM=80 ID="BP86"The basic AppleTalk parameters are explained in IDREF="FM66642"Table 4-1.LABEL="4-1" PGWIDE=1 TOCENTRY="1"ID="FM66642"AppleTalk Configuration ParametersCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="9*"COLNAME=2 COLWIDTH="26*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ParameterCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"AppleTalk StatusCOLNAME=2 ROTATE="0" MOREROWS="0"Enables the protocol. If this parameter is disabled, the configuration of the protocol is saved, but AppleTalk is not active.COLNAME=1 ROTATE="0" MOREROWS="0"Packet ForwardingCOLNAME=2 ROTATE="0" MOREROWS="0"Forwards AppleTalk packets, operating the system as a router. When this parameter is disabled, the system behaves like an end node and does not forward AppleTalk packets from one network to another.COLNAME=1 ROTATE="0" MOREROWS="0"Type of Packet ForwardingCOLNAME=2 ROTATE="0" MOREROWS="0"Specifies the type of routing. AppleTalk for NetWare is a Phase 2 router. Select CLASS=MENUITEM MOREINFO="NONE"Transition (Phase1 and Phase 2) if you need to connect to Phase 1 routers. A Phase 1 router cannot read Phase 2 packets.If you select CLASS=MENUITEM MOREINFO="NONE"Transition, each extended network number must be a range of on, and can have only one associated zone nameIf you have to support Phase 1 AppleTalk routers, choose the CLASS=MENUITEM MOREINFO="NONE"Transition mode. Otherwise, leave the default, CLASS=MENUITEM MOREINFO="NONE"Phase 2, selected.For more information, see IDREF="FM22412""AppleTalk Addressing."COLNAME=1 ROTATE="0" MOREROWS="0"DDP ChecksumCOLNAME=2 ROTATE="0" MOREROWS="0"Specifies whether to use DDP checksum to detect errors in packets for the router. Enabling checksum will affect routing performance.COLNAME=1 ROTATE="0" MOREROWS="0"Tunnel AppleTalk Through IP (AURP)COLNAME=2 ROTATE="0" MOREROWS="0"Enables the use of AURP for an IP tunnel when you want to route packets through an IP internetwork.For more information, see IDREF="FM69353""Configuring AppleTalk to Use the IP Tunnel (AURP)."COLNAME=1 ROTATE="0" MOREROWS="0"AURP ConfigurationCOLNAME=2 ROTATE="0" MOREROWS="0"Lets you configure AURP for the IP tunnel.COLNAME=1 ROTATE="0" MOREROWS="0"Filtering SupportCOLNAME=2 ROTATE="0" MOREROWS="0"Lets you enable filtering support when you want to restrict the packets that a router sends and receives. If you enable this option, you must use FILTCFG to configure the filtering options. You must enable Filtering for any AppleTalk filters configured using the FILTCFG utility to work.For more information, see IDREF="FM68332""Filtering."COLNAME=1 ROTATE="0" MOREROWS="0"Internal NetworkCOLNAME=2 ROTATE="0" MOREROWS="0"Lets you enable application support on the internal network, such as AFP and ATPS, on the network interface. AppleTalk can operate with or without the internal network. When the internal network is disabled, you should select a network interface for AppleTalk to provide application support.For more information, see IDREF="FM80889""Internal Networks."COLNAME=1 ROTATE="0" MOREROWS="0"Network NumberCOLNAME=2 ROTATE="0" MOREROWS="0"Lets you assign a unique number to your internal network.COLNAME=1 ROTATE="0" MOREROWS="0"Network Zone(s) ListCOLNAME=2 ROTATE="0" MOREROWS="0"Lets you set up your internal network with up to 255 zone names. A router using transitional routing is allowed to use only one zone name.PAGENUM=81 ID="BP87"RENDERAS="SECT1"ID="FM38831"Configuring AppleTalk as an End NodeIDXID="w1200"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"IDXID="w1201"BOOK="_idx" COLLECTION="nw41" TIDREF="i1326"
NetWare 4.1 allows you to turn off, or disable, AppleTalk routing on a dedicated router or NetWare file server. This is especially useful when you have more than one AppleTalk router on your network and you want to make more computing resources available for NetWare file and print services. A NetWare system with AppleTalk routing disabled operates as an AppleTalk end node.An AppleTalk router allows end nodes on one AppleTalk network to communicate with end nodes on other AppleTalk networks. If you are only using NetWare for AppleTalk to support applications such as AFP and ATPS on a LAN, and you already have an AppleTalk router that provides connectivity to other networks, and end node configuration will have the following advantages:MARK=BULLETAn end node does not periodically broadcast routing table maintenance packets. More network bandwidth can be used for data rather than routing traffic.An end node does not require any network number or zone configuration.Features such as filtering, internal network support, and AURP are available only if NetWare for AppleTalk is configured as a router.PAGENUM=82 ID="BP88"RENDERAS="SECT2"How to Configure AppleTalk as an End NodeIDXID="w1202"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"IDXID="w1203"BOOK="_idx" COLLECTION="nw41" TIDREF="i1326"
To turn off AppleTalk routing and configure AppleTalk as an end node, load INETCFG and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"AppleTalk > Select CLASS=MENUITEM MOREINFO="NONE"Packet Forwarding > Select CLASS=MENUITEM MOREINFO="NONE"DisableWith packet forwarding disabled, the system does not route AppleTalk packets from one network to another. Press MOREINFO="NONE"<Esc> to return to the CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu; save your changes when prompted.Make sure AppleTalk is bound to a single interface. The router will not come up as an end node unless AppleTalk is bound. When you configure AppleTalk as an end node, you can bind AppleTalk only to one interface.If you want these changes to take effect immediately, exit INETCFG, then bring down and restart the router. If you want to configure other parameters, do so now and restart the router when you are finished.RENDERAS="SECT1"ID="FM42920"Configuring AppleTalk for LAN ConnectionsIDXID="w1204"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"IDXID="w1205"BOOK="_idx" COLLECTION="nw41" TIDREF="i2029"
To configure AppleTalk to run over a LAN, you must complete the following tasks:NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"Configure the LAN board.For information about configuring boards, see the BOOK="cfg1_enu" COLLECTION="nw41"NetWare 4.1 Basic Protocol Configuration Guide.Configure basic AppleTalk options, including CLASS=MENUITEM MOREINFO="NONE"Type of Packet Forwarding, CLASS=MENUITEM MOREINFO="NONE"Filtering Support, and CLASS=MENUITEM MOREINFO="NONE"Internal Network, if necessary.For information about these AppleTalk options, see IDREF="FM39539""Configuring Basic AppleTalk Parameters."Bind AppleTalk to a LAN interface, including the following options:NUMERATION=LOWERALPHA CONTINUATION="RESTARTS" INHERITNUM="IGNORE"CLASS=MENUITEM MOREINFO="NONE"Network Range and Zone configuration, to establish whether this is a seed or non-seed router.For more information, see IDREF="FM33459""Seeding."PAGENUM=83 ID="BP89"CLASS=MENUITEM MOREINFO="NONE"Network Range/Number and CLASS=MENUITEM MOREINFO="NONE"Zone(s) List, if it is a seed router.CLASS=MENUITEM MOREINFO="NONE"Provide Application through this Interface and CLASS=MENUITEM MOREINFO="NONE"Applications Zone Name, if you want application support through the interface rather than the internal network.For more information, see IDREF="FM80889""Internal Networks."RENDERAS="SECT2"Configuring AppleTalk for a LANIDXID="w1206"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"IDXID="w1207"BOOK="_idx" COLLECTION="nw41" TIDREF="i2029"
To configure AppleTalk for a LAN connection, load INETCFG and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"AppleTalk CLASS=MENUITEM MOREINFO="NONE"Complete the following steps: PERFORMANCE="REQUIRED"Configure the basic AppleTalk options. For information about the basic AppleTalk configuration options, see 
IDREF="FM39539""Configuring Basic AppleTalk Parameters." PERFORMANCE="REQUIRED"Bind AppleTalk to a LAN interface. For information about binding AppleTalk for a LAN connection, see 
IDREF="FM21214""Binding AppleTalk to a LAN Interface."PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to return to the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu; save your changes when prompted.If you want these changes to take effect immediately, exit INETCFG, then bring down and restart the router. If you want to configure other parameters, do so now and restart the router when you are finished.RENDERAS="SECT2"ID="FM21214"Binding AppleTalk to a LAN InterfaceIDXID="w1208"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"IDXID="w1209"BOOK="_idx" COLLECTION="nw41" TIDREF="i2029"IDXID="w1210"BOOK="_idx" COLLECTION="nw41" TIDREF="i463"
To bind AppleTalk to a LAN interface, load INETCFG and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Press <Insert> (CLASS=MENUITEM MOREINFO="NONE"Select from the list of configured protocols window appears) > Select CLASS=MENUITEM MOREINFO="NONE"AppleTalk (CLASS=MENUITEM MOREINFO="NONE"Select from the list of configured network interfaces window appears) > Select the LAN interface (CLASS=MENUITEM MOREINFO="NONE"Types of AppleTalk Networks window appears)PAGENUM=84 ID="BP90"Complete the following steps:PERFORMANCE="REQUIRED"Choose the CLASS=MENUITEM MOREINFO="NONE"Type of AppleTalk Networks.An 
CLASS=MENUITEM MOREINFO="NONE"Extended Network supports Phase 2 addressing, a 
CLASS=MENUITEM MOREINFO="NONE"Non-Extended Network supports only one network number and one zone.The 
CLASS=MENUITEM MOREINFO="NONE"Binding NetWare AppleTalk to a LAN Interface window is displayed. For more information, see 
IDREF="FM22412""AppleTalk Addressing."PERFORMANCE="REQUIRED"Choose whether this is a seed interface.You can choose between a seed interface (
CLASS=MENUITEM MOREINFO="NONE"Define Here) or a non-seed interface (
CLASS=MENUITEM MOREINFO="NONE"Learn from Network). If this is a seed interface, enter the 
CLASS=MENUITEM MOREINFO="NONE"Network Range/Number of the network to which this router belongs, and the 
CLASS=MENUITEM MOREINFO="NONE"Zone(s) List available in the network.PERFORMANCE="REQUIRED"To provide application support through this interface, enable 
CLASS=MENUITEM MOREINFO="NONE"Provide Application through this Interface, and enter the 
CLASS=MENUITEM MOREINFO="NONE"Applications Zone Name.You can provide application support through the internal network or the interface. Configure application support through the interface only when the internal network is not enabled.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to return to the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu; save your changes when prompted.If you want these changes to take effect immediately, exit INETCFG, then bring down and restart the router. If you want to configure other parameters, do so now and restart the router when you are finished.RENDERAS="SECT1"IDXID="w1211"BOOK="_idx" COLLECTION="nw41" TIDREF="i4607"ID="FM69353"Configuring AppleTalk to Use the IP Tunnel (AURP)AURP provides two features:IDXID="w1212"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"IDXID="w1213"BOOK="_idx" COLLECTION="nw41" TIDREF="i349"MARK=BULLETIP tunnelingUnlike RTMP, routing information is exchanged only when a change occurs in network topologies.PAGENUM=85 ID="BP91"If you need to connect two sites using a low bandwidth, AURP is the more economical way to provide AppleTalk connectivity between the two sites. Because less bandwidth is used to exchange routing information, more bandwidth can be used to carry user data.To configure AppleTalk to use the IP tunnel, AppleTalk and TCP/IP must be enabled. Refer to the BOOK="atrefenu" COLLECTION="nw41"NetWare 4.1 AppleTalk* Reference for AppleTalk configuration procedures, and see IDREF="FM76970"Chapter 3, "Configuring IP," for TCP/IP configuration procedures.RENDERAS="SECT2"ID="FM60465"Tunneling AppleTalk PacketsIDXID="w1214"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"IDXID="w1215"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"IDXID="w1216"BOOK="_idx" COLLECTION="nw41" TIDREF="i4607"IDXID="w1217"BOOK="_idx" COLLECTION="nw41" TIDREF="i349"
AppleTalk for NetWare uses AURP to encapsulate AppleTalk packets in IP packets. The forwarding AURP router encapsulates and forwards each AppleTalk packet through the TCP/IP network to the next AURP router. The receiving AURP router removes the IP headers from the packet, then forwards it, like any other AppleTalk packet, to the destination AppleTalk network. For information about AURP, refer to the BOOK="atrefenu" COLLECTION="nw41"NetWare 4.1 AppleTalk* Reference.IDREF="FM57210"Figure 4-1 shows two isolated AppleTalk networks connected by an IP tunnel.LABEL="4-1" FLOAT="0"ID="FM57210"IP Tunnel Connecting Two AppleTalk Networks FILEREF="aurp1.tif"PAGENUM=86 ID="BP92"When configuring the IP tunnel for AURP, you supply the IP addresses of the AURP routers with which you plan to communicate. Generally, all AURP routers on an IP tunnel can communicate with one another. Each AURP router on a tunnel sends routing information about its local AppleTalk network to each of its peers on the tunnel. Because each AURP router is responsible for distributing its local network routing information, the receiving AURP routers on the tunnel do not need to forward the information to any of their AURP peer routers. IDXID="w1218"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"IDXID="w1219"BOOK="_idx" COLLECTION="nw41" TIDREF="i4607"IDXID="w1220"BOOK="_idx" COLLECTION="nw41" TIDREF="i1585"
A fully connected tunnel is one in which all AURP routers on the tunnel are aware of and can communicate with one another. On a fully connected tunnel, the same number of routes should be reachable from each AURP router. IDXID="w1221"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"IDXID="w1222"BOOK="_idx" COLLECTION="nw41" TIDREF="i4607"IDXID="w1223"BOOK="_idx" COLLECTION="nw41" TIDREF="i3224"
A partially connected tunnel is one in which not all AURP routers are aware of and can communicate with one another. A partially connected tunnel can provide network-level security. In a partially connected tunnel configuration, the routing tables on the different AURP routers can have different numbers of entries, and not all networks connected to these AURP routers are reachable by one another. Partially connected tunnels can also be created accidentally if the router is not configured properly. For example, a network manager might create a partially connected tunnel accidentally by making an error when entering the list of peers with which the router should communicate.RENDERAS="SECT2"Configuring AURPIDXID="w1224"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"IDXID="w1225"BOOK="_idx" COLLECTION="nw41" TIDREF="i349"IDXID="w1226"BOOK="_idx" COLLECTION="nw41" TIDREF="i4607"
When you enable AppleTalk, you can use the CLASS=MENUITEM MOREINFO="NONE"AppleTalk Configuration window in INETCFG to configure AURP to use the IP tunnel. To configure AURP to use the IP tunnel, load INETCFG and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"AppleTalk CLASS=MENUITEM MOREINFO="NONE"Complete the following steps: PERFORMANCE="REQUIRED"Enable CLASS=MENUITEM MOREINFO="NONE"Tunnel AppleTalk Through IP (AURP).PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"AURP Configuration.The 
CLASS=MENUITEM MOREINFO="NONE"AURP Configuration screen is displayed.The
CLASS=MENUITEM MOREINFO="NONE" UDP Port is always set to 387, and the 
CLASS=MENUITEM MOREINFO="NONE"UDP Checksum is always enabled.
PAGENUM=87 ID="BP93"PERFORMANCE="REQUIRED"Configure the following options:
MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Local IP Address, to select the address of the local peer for the IP tunnel. This gives the router a unique address with which other routers can establish connections.CLASS=MENUITEM MOREINFO="NONE"Remote Peers List, to add the remote peers to which the router can tunnel AppleTalk packets. Press MOREINFO="NONE"<Insert> to add a peer. You can then fill in the CLASS=MENUITEM MOREINFO="NONE"Remote IP Address and configure the following parameters for the remote peer, by selecting CLASS=MENUITEM MOREINFO="NONE"Expert Options:CLASS=MENUITEM MOREINFO="NONE"Transmit Timeout, to set the time between retries if there is no response to a communications request. The default is 10 seconds.CLASS=MENUITEM MOREINFO="NONE"Maximum Transmit Retries, to set the maximum number of retries to establish communication. The default is three tries.CLASS=MENUITEM MOREINFO="NONE"Last Heard from Timeout Interval, to set the time between keep-alive requests. The default is 90 seconds.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> until you get back to the 
CLASS=MENUITEM MOREINFO="NONE"AURP Configuration screen.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Expert Options to configure the following parameters:
MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Connections from Unconfigured Peers, to specify whether connect requests from peers not in the peer list are accepted. The default is CLASS=MENUITEM MOREINFO="NONE"Deny.CLASS=MENUITEM MOREINFO="NONE"Last Heard from Timeout Interval, to set the time between keep-alive requests sent to unconfigured peers. The default is 90 seconds.CLASS=MENUITEM MOREINFO="NONE"Routing Update Interval, to set the minimum amount of time between routing updates. The default is 60 seconds.The default values are appropriate for most configurations.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to return to the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu; save your changes when prompted.If you want these changes to take effect immediately, exit INETCFG, then bring down and restart the router. If you want to configure other parameters, do so now and restart the router when you are finished.
PAGENUM=88 ID="BP94"LABEL="5"PAGENUM=89 ID="BP95"ID="FM54089"Configuring FiltersThe IDXID="w1227"BOOK="_idx" COLLECTION="nw41" TIDREF="i761"IDXID="w1228"BOOK="_idx" COLLECTION="nw41" TIDREF="i1503"
Filter Configuration utility IDXID="w1229"BOOK="_idx" COLLECTION="nw41" TIDREF="i1496"
(FILTCFG) allows you to configure filters that selectively discard packets to be sent or received by a server or router. Filters let you control the service and route information that is accepted or advertised by a server or router. Filters can be useful when you want to limit specific kinds of traffic to certain parts of your network topology, or when you want to provide a certain level of security. This chapter describes the different types of filters and describes how to configure them. This chapter contains the following sections:MARK=BULLETIDREF="FM17729""Filtering Overview" This section describes the general concepts of filtering and the protocol suites and filter types that can be configured for each.IDREF="FM11582""AppleTalk Filtering" This section describes AppleTalk filtering, includes procedures for configuring AppleTalk filtering, and provides examples.IDREF="FM38444""IPX Filtering" This section describes IPXTM filtering, includes procedures for configuring IPX filtering, and provides examples.IDREF="FM96491""TCP/IP Filtering" This section describes TCP/IP filtering, includes procedures for configuring TCP/IP filtering, and provides examples.PAGENUM=90 ID="BP96"RENDERAS="SECT1"ID="FM17729"Filtering OverviewIDXID="w1230"BOOK="_idx" COLLECTION="nw41" TIDREF="i1499"The NetWare® 4.1 FILTCFG utility provides the following filter types, categorized according to the type of information being filtered: MARK=BULLETIDREF="FM73009"Packet Forwarding Filters IDREF="FM26556"Service Information Filters IDREF="FM83216"Routing Information Filters IDREF="FM85303"Table 5-1 lists the protocol suites and the filter types that you can configure for each using FILTCFG.LABEL="5-1" PGWIDE=1 TOCENTRY="1"ID="FM85303"Filter Types and Protocol SuitesCOLS=4 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="7*"COLNAME=2 COLWIDTH="7*"COLNAME=3 COLWIDTH="7*"COLNAME=4 COLWIDTH="7*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Protocol SuiteCOLNAME=2 ROTATE="0" MOREROWS="0"Packet Forwarding FiltersCOLNAME=3 ROTATE="0" MOREROWS="0"Service FiltersCOLNAME=4 ROTATE="0" MOREROWS="0"Route FiltersVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IPXCOLNAME=2 ALIGN="CENTER" ROTATE="0" MOREROWS="0"XCOLNAME=3 ALIGN="CENTER" ROTATE="0" MOREROWS="0"XCOLNAME=4 ALIGN="CENTER" ROTATE="0" MOREROWS="0"XCOLNAME=1 ROTATE="0" MOREROWS="0"AppleTalkCOLNAME=2 ALIGN="CENTER" ROTATE="0" MOREROWS="0"COLNAME=3 ALIGN="CENTER" ROTATE="0" MOREROWS="0"XCOLNAME=4 ALIGN="CENTER" ROTATE="0" MOREROWS="0"XCOLNAME=1 ROTATE="0" MOREROWS="0"TCP/IPCOLNAME=2 ALIGN="CENTER" ROTATE="0" MOREROWS="0"XCOLNAME=3 ALIGN="CENTER" ROTATE="0" MOREROWS="0"COLNAME=4 ALIGN="CENTER" ROTATE="0" MOREROWS="0"XRENDERAS="SECT2"ID="FM73009"Packet Forwarding FiltersPacket forwarding filters limit access to specific services by preventing selected data packets from being forwarded by the server or router. These filters provide the highest level of security because they examine each data packet forwarded by the server or router. Packets are filtered based on the following:MARK=BULLETSource of the packetDestination of the packetPacket typePacket forwarding filters do not restrict service advertisement packets sent by servers. Hence, restricted users might see advertisements of services even when they cannot access the service. PAGENUM=91 ID="BP97"Although packet forwarding filters provide the highest level of security, they might affect the performance of the server or router because the filters are applied to each data packet received by the server or router.Packet forwarding filters are not applied to packets that originate from or are destined to a router. They are applied only to packets that are forwarded. This includes packets forwarded to the internal IPX network.Packet forwarding filters are available for IPX and TCP/IP protocols.RENDERAS="SECT2"ID="FM26556"Service Information FiltersIDXID="w1231"BOOK="_idx" COLLECTION="nw41" TIDREF="i1503"IDXID="w1232"BOOK="_idx" COLLECTION="nw41" TIDREF="i4076"Service information IDXID="w1233"BOOK="_idx" COLLECTION="nw41" TIDREF="i4076"
filters restrict the advertisement or acceptance of specified services by filtering out information in the data packets that advertise the services destined for particular parts of the network. These filters increase security by limiting the visibility of selected services. However, service information filters provide a lower level of network security than packet forwarding filters because they look only at service information packets. They also reduce the network traffic caused by periodic service information messages sent by servers.Service information filters are available for IPX (as outgoing and incoming SAP filters) and AppleTalk (as device hiding filters).RENDERAS="SECT2"ID="FM83216"Routing Information FiltersIDXID="w1234"BOOK="_idx" COLLECTION="nw41" TIDREF="i1503"IDXID="w1235"BOOK="_idx" COLLECTION="nw41" TIDREF="i3901"Routing information filters restrict the exchange of routing information between routers by limiting the routes added to the routing tables of specified routers. These filters increase network security by limiting the visibility of specified networks. However, like service information filters, routing information filters provide a low level of network security because they look only at routing information packets. They also reduce the network traffic caused by the periodic exchange of routing information messages between routers.Routing information filters are available for IPX, AppleTalk, and TCP/IP.There are two types of routing information filters:MARK=BULLETOutgoing routing information filters limit the route advertisements sent out by a router to a specified set of routers.PAGENUM=92 ID="BP98"Incoming routing information filters limit the acceptance of route advertisements received by the router from its neighboring routers.RENDERAS="SECT3"Outgoing Routing Information FiltersIDXID="w1236"BOOK="_idx" COLLECTION="nw41" TIDREF="i3901"IDXID="w1237"BOOK="_idx" COLLECTION="nw41" TIDREF="i3155"Outgoing routing information filters limit routing information advertised by a router to its neighboring routers. When these filters are enabled on a router, only the allowed routes are advertised to each neighboring router. This hides specified routes from some routers and from certain parts of the network.A typical outgoing routing information filter consists of the route to the destination network, and the interface through which filtered advertisements of the route are sent. The filters affect all routers on the network to which this interface connects. Outgoing routing information filters may not affect whether the end stations that are on the same LAN segment as the filtering router can access the filtered routes. Because these filters only keep from advertising filtered routes to other routers, but do not affect the filtering router's routing table, the filtering router delivers all packets that it receives as destined for filtered routes. End stations at least one router away usually cannot access networks with routes that are filtered out. IDREF="FM19905"IDREF="FM26540"Figure 5-1 shows two networks; the route for one network has been filtered. LABEL="5-1" FLOAT="0"ID="FM26540"Outgoing RIP FiltersID="FM19905"FILEREF="endroute.tif"PAGENUM=93 ID="BP99"The route to Network 1 is filtered out in Router R1's advertisement to Network 3. If End Station E2 sends a packet to Network 1, Router R2 will drop that packet because it does not have a route. If End Station E1 sends a packet to Network 1, Router R1 will forward it because it does have a route. End Station E1 can only send a packet to Network 1 if it has a route to that network. End station E2 can only "see" Networks 2, 3, and 4. End station E1 can see both Networks 1 and 2.For IPX, route information filters affect both clients and routes. A client will make a route request which passes through the same filters as for the routinely transmitted route information. However, if a client is locally attached to a router that is performing outbound route information filtering and the client is using software that can use static routing, the client can send packets to Network 1 through Router R1 because R1 knows about Network 1 in its routing tables. If only standard IPX route lookups are done (true for a majority of sites), a path is not possible to the filtered networks.RENDERAS="SECT3"Incoming Routing Information FiltersIDXID="w1238"BOOK="_idx" COLLECTION="nw41" TIDREF="i3901"IDXID="w1239"BOOK="_idx" COLLECTION="nw41" TIDREF="i1779"IDXID="w1240"BOOK="_idx" COLLECTION="nw41" TIDREF="i1496"Incoming routing information filters limit the routing information accepted by a router from its neighboring routers. When incoming routing information filters are enabled on a router, the router accepts only the allowed routes from each neighboring router, thereby hiding specified routes from some routers and from certain parts of the network. However, incoming routing information filters cannot be used to filter out directly connected networks. A typical incoming routing information filter consists of the destination network of the route and the interface through which advertisements of the route are expected to be received. Incoming routing information filters keep the filtering router from adding certain routes to its routing table when it receives the information from its neighbors. The filtering router cannot forward a packet to a filtered route even if it receives a packet destined for it. In this way, incoming routing information filters provide a higher level of security than outgoing routing information filters.PAGENUM=94 ID="BP100"RENDERAS="SECT2"Running FILTCFGIDXID="w1241"BOOK="_idx" COLLECTION="nw41" TIDREF="i3930"IDXID="w1242"BOOK="_idx" COLLECTION="nw41" TIDREF="i1496"Filtering support must be enabled for each protocol that needs filtering in the Internetworking Configuration utility (INETCFG) for filtering to work.To set up and modify filtering, complete the following steps:PERFORMANCE="REQUIRED"Load FILTCFG by typing 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.PERFORMANCE="REQUIRED"Select the protocol for which you want to configure filters.PERFORMANCE="REQUIRED"Select to define the filter.The main menu for the protocol you selected appears.PERFORMANCE="REQUIRED"Select the option you want.The corresponding option menu appears.PERFORMANCE="REQUIRED"For each option you select, you can configure the following general parameters:
MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Status---Select CLASS=MENUITEM MOREINFO="NONE"Enabled or CLASS=MENUITEM MOREINFO="NONE"Disabled to specify the status of the selected filters.Disabling a filter category means that the protocol will operate as if the filter module is not loaded for that filter category, and no filtering will occur. You can configure filtering when it is disabled, but your changes will have no effect.CLASS=MENUITEM MOREINFO="NONE"Action---Toggle the displayed choice to permit or deny the entries listed in the filter list. This specifies the action taken when a packet, route, or service matches an entry in the filter list.If the action is permitted, one of the following occurs:---Packets matching the entries in the Packet Forwarding List are allowed through.---Services/routes matching the entries in the Outgoing Service/Routing Information Filter Lists are advertised.PAGENUM=95 ID="BP101"---Services/routes matching the entries in the Incoming Service/Routing Information Filter Lists are not accepted.If a device or route is denied, the packets are discarded.CLASS=MENUITEM MOREINFO="NONE"Filters---Press MOREINFO="NONE"<Enter> to display a list of filters that are accepted (permitted) or filtered (denied) on an interface.You can modify the list by pressing MOREINFO="NONE"<Insert> to add a new filter; or you can select a filter from the list and press MOREINFO="NONE"<Enter> to modify the filter, or MOREINFO="NONE"<Delete> to remove it. Refer to the corresponding section later in this chapter for the steps to define a filter if you are modifying or adding a filter.CLASS=MENUITEM MOREINFO="NONE"Exceptions---Press MOREINFO="NONE"<Enter> to display a list of exceptions to which the above action---permit or deny---does not apply. These are the exceptions to the filter list. When filtering, the exception list is examined before the filter list. If there is a conflict between the two lists, the exception list is used. The action taken on the exception list is always opposite the action taken on the filter list.You can modify the list by pressing MOREINFO="NONE"<Insert> to add a new filter; or you can select a filter from the list and press MOREINFO="NONE"<Enter> to modify the filter, or MOREINFO="NONE"<Delete> to remove it. For example, you could use a filter to hide all Marketing file servers from Engineering, except the server named "MKTG-DEMO."PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to exit.RENDERAS="SECT1"ID="FM11582"AppleTalk FilteringIDXID="w1243"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"IDXID="w1244"BOOK="_idx" COLLECTION="nw41" TIDREF="i1499"AppleTalk supports the following types of filters:MARK=BULLETIDREF="FM84822"AppleTalk Device Hiding Filters IDREF="FM29451"AppleTalk Routing Information Filters RENDERAS="SECT2"ID="FM84822"AppleTalk Device Hiding FiltersIDXID="w1245"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"IDXID="w1246"BOOK="_idx" COLLECTION="nw41" TIDREF="i1503"IDXID="w1247"BOOK="_idx" COLLECTION="nw41" TIDREF="i1024"PAGENUM=96 ID="BP102"AppleTalk device hiding filters restrict the advertisement of services on a internetwork by filtering out packets that advertise those services. These filters prevent users from finding the network addresses of services, and provide a level of network security. In AppleTalk, theIDXID="w1248"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"IDXID="w1249"BOOK="_idx" COLLECTION="nw41" TIDREF="i2573"
 Name Binding Protocol (NBP) lets users access services such as file servers and printers. Specifically, it allows a user or application to specify search parameters such as the network entity name and service type, and a zone in which the search should be done. The search is represented in an NBP lookup request sent to the appropriate zone where the service might be. Services matching the search parameters reply directly to the requesting user or application with the AppleTalk address of the service. Once the user or application has received the NBP reply, the user or application can communicate with the service using the AppleTalk address. When AppleTalk device hiding filters are enabled on a server or router, the server or router drops the NBP replies for specified services (that is, it does not deliver the replies to the client machine or application that requested them). Thus, the services are hidden from that part of the network. A common use of NBP is the Macintosh* Chooser application. The user or application issues an NBP lookup, specifying a zone and service type of interest. The lookup is sent to the appropriate zone. All devices or services of the specified type in the zone respond with an NBP reply. The Chooser displays the list of available devices, depending on the NBP replies it receives. Using the AppleTalk address supplied in each NBP reply, the user or application can then communicate with the device or service.PAGENUM=96 ID="BP103"PAGENUM=97If filtering for that device or service location is enabled, the router drops the NBP reply to keep a user or application from getting the network address of these services. Without the NBP reply, the application cannot know about the existence of the device. Device hiding filters provide a low-level of security, but they do have limitations. Because filtering is enabled on a router, if the client machine requesting the address is on the same network as the service, the NBP reply goes directly to the client and the router has no opportunity to filter it out. Additionally, if a client machine knows the address of a specific service, it does not need the NBP reply to access the service. You can configure AURP routers to filter service information traveling through an IP tunnel. If a filter is enabled on the tunnel, all networks accessible through the tunnel are affected by service information filters configured for the AURP router. Refer to IDREF="FM76890"Chapter 4, "Configuring AppleTalk," for more information about configuring AURP.RENDERAS="SECT3"How to Configure AppleTalk Device Hiding FilteringIDXID="w1250"BOOK="_idx" COLLECTION="nw41" TIDREF="i761"IDXID="w1251"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"IDXID="w1252"BOOK="_idx" COLLECTION="nw41" TIDREF="i1024"Filtering support must be enabled for AppleTalk in INETCFG for filtering to work.To configure AppleTalk device hiding filtering, load FILTCFG and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"AppleTalk > Select CLASS=MENUITEM MOREINFO="NONE"Device Hiding FiltersMOREINFO="NONE" (CLASS=MENUITEM MOREINFO="NONE"Device Hiding Filters menu appears)Complete the following steps:PERFORMANCE="REQUIRED"Select CLASS=MENUITEM MOREINFO="NONE"Action and toggle the choice to show or hide the devices listed in the filter list.This specifies the action taken when an NBP reply packet matches a filter in the filter list. If you specify to show the devices, the AppleTalk router will forward only the NBP replies that match the description of any filter in the filter list and will discard all other AppleTalk device replies. If you specify to hide the devices, the AppleTalk router will discard all NBP replies that match the description of any filters in the filter list, and will forward all others.
PAGENUM=97 ID="BP104"PAGENUM=98PERFORMANCE="REQUIRED"ID="FM11183"Select 
CLASS=MENUITEM MOREINFO="NONE"Filters to display a list of device filters.Displays the list of filters that either hide or show devices, depending on the setting of the 
CLASS=MENUITEM MOREINFO="NONE"Action parameter. The name, type, device location, and user location are listed for each device filter.PERFORMANCE="REQUIRED"Modify the filter list.Press 
MOREINFO="NONE"<Insert> to add a new filter; or select a filter from the list and press 
MOREINFO="NONE"<Enter> to modify the filter, or 
MOREINFO="NONE"<Delete> to remove it. If you are modifying or adding a filter, perform the following substeps at the 
CLASS=MENUITEM MOREINFO="NONE"Define Filter menu:PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"ID="FM42356"Select 
CLASS=MENUITEM MOREINFO="NONE"Device 
CLASS=MENUITEM MOREINFO="NONE"Name and enter an NBP name of up to 32 characters. Keep the default (the = sign) to select all NBP names. An AppleTalk device advertises itself on the network based on the CLASS=MENUITEM MOREINFO="NONE"Device Name and CLASS=MENUITEM MOREINFO="NONE"Device Type values.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Device Type.PressMOREINFO="NONE" <Enter> to select from the list of defined AppleTalk NBP device types, or press MOREINFO="NONE"<Insert> to add a new NBP type with the following information: MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Device Type---Enter a text string of up to 32 characters.CLASS=MENUITEM MOREINFO="NONE"Comment---Enter an optional short description.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Device Location Type and specify where the filtered device is located. Your choices are CLASS=MENUITEM MOREINFO="NONE"<Any> (the default), CLASS=MENUITEM MOREINFO="NONE"Interface, CLASS=MENUITEM MOREINFO="NONE"Non-extended Network, CLASS=MENUITEM MOREINFO="NONE"Extended Network, Zone, or CLASS=MENUITEM MOREINFO="NONE"AURP Tunnel. Select <Any> if you do not know the location of the device, or if the network location does not matter.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Device Location and perform one of the following, based on what you selected in Step 3c:
MARK=BULLET<CLASS=MENUITEM MOREINFO="NONE"Any> or CLASS=MENUITEM MOREINFO="NONE"AURP Tunnel--- This field cannot be edited.CLASS=MENUITEM MOREINFO="NONE"Interface---Press MOREINFO="NONE"<Enter>, then select a network interface from the list.CLASS=MENUITEM MOREINFO="NONE"Non-extended Network---Press MOREINFO="NONE"<Enter>, then type a network number to identify the non-extended network where the filtered device is located.PAGENUM=99 ID="BP105"CLASS=MENUITEM MOREINFO="NONE"Extended Network---Press MOREINFO="NONE"<Enter>, then type the start and end network numbers for extended network where the filtered device is located. The start number must be greater than zero, and the end number must be greater than or equal to the start value.CLASS=MENUITEM MOREINFO="NONE"Zone---Press MOREINFO="NONE"<Enter>, then type the name of the AppleTalk zone where the filtered device is located.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"User 
CLASS=MENUITEM MOREINFO="NONE"Location Type and select a location type. Your choices are: <CLASS=MENUITEM MOREINFO="NONE"Any> (the default), CLASS=MENUITEM MOREINFO="NONE"Interface, CLASS=MENUITEM MOREINFO="NONE"Non-extended Network, CLASS=MENUITEM MOREINFO="NONE"Extended Network, CLASS=MENUITEM MOREINFO="NONE"Zone, or CLASS=MENUITEM MOREINFO="NONE"AURP Tunnel. Select <Any> if you do not know the location of the device, or if the network location does not matter.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"User Location and specify the locations of the users whose access to the devices must be controlled. Perform one of the following, based on what you selected in Step 3e:
MARK=BULLET<CLASS=MENUITEM MOREINFO="NONE"Any> or CLASS=MENUITEM MOREINFO="NONE"AURP Tunnel--- This field cannot be edited.CLASS=MENUITEM MOREINFO="NONE"Interface---PressMOREINFO="NONE" <Enter>, then select a network interface from the list.CLASS=MENUITEM MOREINFO="NONE"Non-extended Network---Press MOREINFO="NONE"<Enter>, then type a network number to identify the non-extended network where the filtered device is located.CLASS=MENUITEM MOREINFO="NONE"Extended Network---Press MOREINFO="NONE"<Enter>, then type the start and end numbers for the extended network where the filtered device is located. The start number must be greater than zero, and the end number must be greater than or equal to the start value.CLASS=MENUITEM MOREINFO="NONE"Zone---Press MOREINFO="NONE"<Enter>, then type the name of the AppleTalk zone where the filtered device is located.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Comment and enter an optional short description.PERFORMANCE="REQUIRED"ID="FM75859"Press 
MOREINFO="NONE"<Esc> and save the filter information.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Exceptions to display a list of exceptions to the hidden devices.Setting this option lets you define a set of exceptions (overrides) to the filter list. Note that the devices are hidden only if the action in 
IDREF="FM11183"Step 2 is 
CLASS=MENUITEM MOREINFO="NONE"Hide Devices. 
PAGENUM=100 ID="BP106"PERFORMANCE="REQUIRED"Modify the exception list.Press 
MOREINFO="NONE"<Insert> to add a new filter; or select a filter from the list and press 
MOREINFO="NONE"<Enter> to modify the filter, or 
MOREINFO="NONE"<Delete> to remove it. Refer to 
IDREF="FM42356"Step 3a through 
IDREF="FM75859"Step 3h to modify or add a filter on the exception list.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Status and
 toggle the choice to read 
CLASS=MENUITEM MOREINFO="NONE"Enabled or 
Disabled. This specifies the status of the device hiding or AppleTalk service filters and takes effect immediately.RENDERAS="SECT3"Example AppleTalk Device Hiding FilterIDREF="FM21340"Figure 5-2 showsIDXID="w1253"BOOK="_idx" COLLECTION="nw41" TIDREF="i761"IDXID="w1254"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"IDXID="w1255"BOOK="_idx" COLLECTION="nw41" TIDREF="i1506"IDXID="w1256"BOOK="_idx" COLLECTION="nw41" TIDREF="i1024"
 the internetwork topology for an organization with an FDDI backbone connecting several departments within the organization and a link to external networks. Routers A and C connect the departmental networks to the backbone. In general, users can communicate freely across the internetwork. However, access to printers within the Accounting department is restricted. PAGENUM=101 ID="BP107"LABEL="5-2" FLOAT="0"ID="FM21340"AppleTalk Device Hiding Filter ExampleFILEREF="atsvinfo.tif"All networks within the Accounting department are in Zone Accounting. A device hiding filter on Router C stops access from specific areas to the LaserWriter* printers within the Accounting zone.PAGENUM=101 ID="BP108"PAGENUM=102When configuring this example, set the following parameters, as shown in IDREF="FM14851"Table 5-2.LABEL="5-2" PGWIDE=0 TOCENTRY="1"ID="FM14851"AppleTalk Device Hiding Filter Example ParametersCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ParameterCOLNAME=2 ROTATE="0" MOREROWS="0"Example EntryVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"ActionCOLNAME=2 ROTATE="0" MOREROWS="0"DenyCOLNAME=1 ROTATE="0" MOREROWS="0"Device NameCOLNAME=2 ROTATE="0" MOREROWS="0"= (for all NBP names)COLNAME=1 ROTATE="0" MOREROWS="0"Device TypeCOLNAME=2 ROTATE="0" MOREROWS="0"LaserWriterCOLNAME=1 ROTATE="0" MOREROWS="0"Device Location TypeCOLNAME=2 ROTATE="0" MOREROWS="0"ZoneCOLNAME=1 ROTATE="0" MOREROWS="0"Device LocationCOLNAME=2 ROTATE="0" MOREROWS="0"AccountingCOLNAME=1 ROTATE="0" MOREROWS="0"User Location TypeCOLNAME=2 ROTATE="0" MOREROWS="0"InterfaceCOLNAME=1 ROTATE="0" MOREROWS="0"User LocationCOLNAME=2 ROTATE="0" MOREROWS="0"FDDI BackboneRENDERAS="SECT2"ID="FM29451"AppleTalk Routing Information FiltersIDXID="w1257"BOOK="_idx" COLLECTION="nw41" TIDREF="i1503"IDXID="w1258"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"IDXID="w1259"BOOK="_idx" COLLECTION="nw41" TIDREF="i3901"
IDXID="w1260"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"AppleTalk routing information filters restrict the exchange of routing information between routers by limiting the routes added to the routing tables of specified routers. These filters increase security by limiting the visibility of selected networks or zones and reduce the network bandwidth consumed by the periodic exchange of routing information between routers. There are two types of AppleTalk routing information filters:MARK=BULLETIDREF="FM43243"AppleTalk Outgoing Route Filters IDREF="FM29217"AppleTalk Incoming Route Filters AppleTalk uses RTMP as its primary routing protocol. This protocol is similar to the Routing Information Protocol (RIP) used by TCP/IP and IPX. The routing tables maintained by RTMP contain an entry for every known route. These routing tables acquire routing information in two ways: MARK=BULLETFor directly connected networks, through AppleTalk configuration.For networks not directly connected, through the routing updates from each of a router's neighboring routers.PAGENUM=103 ID="BP109"When all routing information filters are not enabled, an AppleTalk router learns all the routes known by its neighboring routers through periodic routing table updates (sent by RTMP). In this way, every router on the internetwork acquires the routing information from all other routers on the internetwork. Routing information filters are also available over AURP. In this case, a neighboring router can be either a network interface (all neighbors directly connected to the cable) or all peers on the AURP tunnel. AppleTalk outgoing route information filters can be used for networks and zones. Incoming route filtering can only be used for a network.RENDERAS="SECT3"ID="FM43243"AppleTalk Outgoing Route FiltersIDXID="w1261"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"IDXID="w1262"BOOK="_idx" COLLECTION="nw41" TIDREF="i1503"IDXID="w1263"BOOK="_idx" COLLECTION="nw41" TIDREF="i3901"IDXID="w1264"BOOK="_idx" COLLECTION="nw41" TIDREF="i3901"AppleTalk IDXID="w1265"BOOK="_idx" COLLECTION="nw41" TIDREF="i1503"IDXID="w1266"BOOK="_idx" COLLECTION="nw41" TIDREF="i1503"IDXID="w1267"BOOK="_idx" COLLECTION="nw41" TIDREF="i1503"IDXID="w1268"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"IDXID="w1269"BOOK="_idx" COLLECTION="nw41" TIDREF="i3155"
outgoing route filters limit the routing information advertised by a router to its neighbors. A typical outgoing route filter consists of a network or zone (the route) and the interface through which filtered advertisements are sent. The filters affect all routers on the network to which the interface connects.An AppleTalk router learns only about networks that are not directly connected through its neighbors. Because of this, neighboring routers with enabled outgoing route filtering can limit the routing information that the AppleTalk router receives. This effectively cuts off access from one part of the network to another.If you hide a route from a neighbor, none of the routers on the neighbor's side of the network has any information about this route.If the action is to deny routes in the filter list, the router ignores all the route information specified in the filters going to the specified neighbors, but sends all other routing information. If the action is to permit routes in the filter list, the router uses only routes specified in the filter list to the specific neighbors and ignores everything else.NetWare 4.1 AppleTalk supports zone-based and network number-based outgoing route filters, as discussed in the following sections.PAGENUM=103 ID="BP110"PAGENUM=104RENDERAS="SECT4"Zone-Based Outgoing Route FiltersIDXID="w1270"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"IDXID="w1271"BOOK="_idx" COLLECTION="nw41" TIDREF="i4879"IDXID="w1272"BOOK="_idx" COLLECTION="nw41" TIDREF="i1503"Zone-based outgoing route filters limit the advertisement of all routes associated with a particular zone. A zone is an abstraction of networks into which many physical networks, including noncontiguous networks, can be grouped. The chief advantage of using zone names in filters is that the filter does not need to be modified when new networks are added to the zone. For example, when filters are configured for the Marketing zone, the zone is made up of only one physical network. As the department grows, more physical networks are added, but they are still grouped under the Marketing zone. All filters configured for the Marketing zone are enforced automatically for all new physical networks added to the zone. This greatly simplifies network management.When you select a zone from a network that has multiple zones, all set filters will affect the entire network, not just the selected zone. RENDERAS="SECT3"Network Number-Based Outgoing Route FiltersIDXID="w1273"BOOK="_idx" COLLECTION="nw41" TIDREF="i1503"IDXID="w1274"BOOK="_idx" COLLECTION="nw41" TIDREF="i2875"Network number-based outgoing route filters limit the advertisement of the routes to specific networks. This kind of filtering gives very explicit control to the user about which physical network should or should not be advertised to different neighbors. You must reconfigure network number-based outgoing route filters when changes occur in the network topology.RENDERAS="SECT3"ID="FM29217"AppleTalk Incoming Route FiltersIDXID="w1275"BOOK="_idx" COLLECTION="nw41" TIDREF="i1503"IDXID="w1276"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"IDXID="w1277"BOOK="_idx" COLLECTION="nw41" TIDREF="i1503"IDXID="w1278"BOOK="_idx" COLLECTION="nw41" TIDREF="i1503"IDXID="w1279"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"IDXID="w1280"BOOK="_idx" COLLECTION="nw41" TIDREF="i1779"IDXID="w1281"BOOK="_idx" COLLECTION="nw41" TIDREF="i3880"IDXID="w1282"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"IDXID="w1283"BOOK="_idx" COLLECTION="nw41" TIDREF="i1503"AppleTalk incoming route filters limit the routing information that a router accepts and adds to its routing tables. When these filters are enabled on a router, the router accepts only the allowed routes from each of its neighboring routers, thus hiding specified routes from some routers and from certain parts of the network. NetWare 4.1 AppleTalk supports only network number-based incoming route filters.An incoming route filter consists of a route and the interface through which the route advertisements are expected to come. The specified route can be to a nonextended network or to an extended network. PAGENUM=105 ID="BP111"Directly connected networks cannot be filtered by incoming route filters. If the action is to deny routes in the filter list, the router ignores all the route information specified in the filters received from the specified neighbors, but accepts and records all other routing information. If the action is to permit routes in the filter list, the router accepts only routes specified in the filter list from the specific neighbors and ignores everything else.RENDERAS="SECT2"AppleTalk Routing Information Filters Over AURPIDXID="w1284"BOOK="_idx" COLLECTION="nw41" TIDREF="i3901"IDXID="w1285"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"Route information filters configured for AURP routers affect all AURP routers on the tunnel in the same way. AppleTalk routers running AURP cannot filter routes on a per-router basis. You should not change AURP route filters dynamically unless it is absolutely required. Because AURP routers exchange complete route information only during connection setup and only send updates to the information thereafter, changing route filters can cause large volumes of AURP routing information to be exchanged as the routers adapt to the new filter configuration. During this information exchange, connectivity over the tunnel can be affected.RENDERAS="SECT3"How to Configure AppleTalk Incoming Route FilteringIDXID="w1286"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"IDXID="w1287"BOOK="_idx" COLLECTION="nw41" TIDREF="i761"IDXID="w1288"BOOK="_idx" COLLECTION="nw41" TIDREF="i3901"Filtering support must be enabled for AppleTalk in INETCFG for filtering to work.To configure AppleTalk routing information filtering for incoming route filters, load FILTCFG and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"AppleTalk > Select CLASS=MENUITEM MOREINFO="NONE"Incoming Route Filters (CLASS=MENUITEM MOREINFO="NONE"Incoming Route Filters menu appears)Complete the following steps:PERFORMANCE="REQUIRED"Select CLASS=MENUITEM MOREINFO="NONE"Action and toggle the choice to permit or deny the routes listed in the filter list.This specifies the action taken with a route that appears in the filter list. If you select to permit routes, the AppleTalk router will accept only the routes to the networks in the filter list. If you select to deny routes, the AppleTalk router will not accept specific routes to specific networks in the filter list, but will accept all other entries in the routing table.
PAGENUM=105 ID="BP112"PAGENUM=106PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Filters to display a list of permitted or denied filters.The route and interface names are listed for each filter.PERFORMANCE="REQUIRED"ID="FM94882"Modify the filter list.Press 
MOREINFO="NONE"<Insert> to add a new filter; or select a filter from the list and press 
MOREINFO="NONE"<Enter> to modify the filter, or 
MOREINFO="NONE"<Delete> to remove it. If you are modifying or adding a filter, modify the following parameters at the 
CLASS=MENUITEM MOREINFO="NONE"Define Filter menu:
MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Route to Extended/Non-extended Network---Select the type of route or network to be filtered.Your choices are CLASS=MENUITEM MOREINFO="NONE"All Routes, CLASS=MENUITEM MOREINFO="NONE"Non-Extended Network, or CLASS=MENUITEM MOREINFO="NONE"Extended CLASS=MENUITEM MOREINFO="NONE"Network. CLASS=MENUITEM MOREINFO="NONE"Network CLASS=MENUITEM MOREINFO="NONE"Number/Range---Enter a network number or a network range, depending on if you selected a nonextended or an extended network. CLASS=MENUITEM MOREINFO="NONE"Interface---Select the network interface that the filter affects. CLASS=MENUITEM MOREINFO="NONE"Comment---Enter an optional short description.PERFORMANCE="REQUIRED"ID="FM42683"Press 
MOREINFO="NONE"<Esc> and save the filter information.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Exceptions to display a list of exceptions to the filtered routes.PERFORMANCE="REQUIRED"Modify the exceptions list.Press 
MOREINFO="NONE"<Insert> to add a new filter; or select a filter from the list and press 
MOREINFO="NONE"<Enter> to modify the filter, or 
MOREINFO="NONE"<Delete> to remove it. Refer to 
IDREF="FM94882"Step 3 and 
IDREF="FM42683"Step 4 to modify or add a filter.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Status and toggle the choice to read 
CLASS=MENUITEM MOREINFO="NONE"Enabled or 
CLASS=MENUITEM MOREINFO="NONE"Disabled. This specifies the status of the filters, and takes effect immediately.
PAGENUM=106 ID="BP113"PAGENUM=107RENDERAS="SECT3"How to Configure AppleTalk Outgoing Route FilteringIDXID="w1289"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"IDXID="w1290"BOOK="_idx" COLLECTION="nw41" TIDREF="i761"IDXID="w1291"BOOK="_idx" COLLECTION="nw41" TIDREF="i3901"Filtering support must be enabled for AppleTalk in INETCFG for filtering to work.To configure AppleTalk routing information filtering for outgoing route filters, load FILTCFG and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"AppleTalk > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing Route Filters (CLASS=MENUITEM MOREINFO="NONE"Outgoing Route Filters menu appears)Complete the following steps:PERFORMANCE="REQUIRED"Select CLASS=MENUITEM MOREINFO="NONE"Action and toggle the choice to permit or deny the routes listed in the filter list.This specifies the action taken with a route that appears in the filter list. If you select to permit routes, the AppleTalk router will advertise only the routes to the networks in the filter list. If you select to deny routes, the AppleTalk router will not advertise specific routes to specific networks in the filter list, but will advertise all other entries in the routing table.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Filters to display a list of permitted or denied filters.The route and interface name are listed for each filter.PERFORMANCE="REQUIRED"ID="FM42720"Modify the filter list.Press 
MOREINFO="NONE"<Insert> to add a new filter; or select a filter from the list and press 
MOREINFO="NONE"<Enter> to modify the filter, or 
MOREINFO="NONE"<Delete> to remove it. If you are modifying or adding a filter, modify the following parameters at the 
CLASS=MENUITEM MOREINFO="NONE"Define Filter menu:
MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Route CLASS=MENUITEM MOREINFO="NONE"to Network or Zone---Select the type of route or network to be filtered.Your choices are CLASS=MENUITEM MOREINFO="NONE"All Routes, CLASS=MENUITEM MOREINFO="NONE"Non-extended Network, Extended CLASS=MENUITEM MOREINFO="NONE"Network, or CLASS=MENUITEM MOREINFO="NONE"Zone. CLASS=MENUITEM MOREINFO="NONE"Network CLASS=MENUITEM MOREINFO="NONE"Number/Range---Enter a network number or a network range, depending on if you selected a nonextended or an extended network. PAGENUM=107 ID="BP114"PAGENUM=108CLASS=MENUITEM MOREINFO="NONE"Zone Name---Enter the zone name of the AppleTalk zone to be filtered.CLASS=MENUITEM MOREINFO="NONE"Interface---Press MOREINFO="NONE"<Enter> and select the network interface that the filter affects. CLASS=MENUITEM MOREINFO="NONE"Comment---Enter an optional short description.PERFORMANCE="REQUIRED"ID="FM89193"Press 
MOREINFO="NONE"<Esc> and save the filter information.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Exceptions to display a list of exceptions to the filtered routes.PERFORMANCE="REQUIRED"Modify the exceptions list.Press 
MOREINFO="NONE"<Insert> to add a new filter; or select a filter from the list and press 
MOREINFO="NONE"<Enter> to modify the filter, or 
MOREINFO="NONE"<Delete> to remove it. Refer to 
IDREF="FM42720"Step 3 and 
IDREF="FM89193"Step 4 to modify or add a filter.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Status and toggle the choice to read 
CLASS=MENUITEM MOREINFO="NONE"Enabled or 
CLASS=MENUITEM MOREINFO="NONE"Disabled. This specifies the status of the filters, and takes effect immediately.RENDERAS="SECT2"AppleTalk Outgoing Routing Information Filter ExampleIn the following exampleIDXID="w1292"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"IDXID="w1293"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"IDXID="w1294"BOOK="_idx" COLLECTION="nw41" TIDREF="i1506"
, the Accounting department is connected to the FDDI backbone by Router C. One of the AppleTalk networks within Accounting is 165-170. Access to this network from outside the Accounting department is not required. The administrator has chosen not to propagate a route to this network outside the Accounting department. IDREF="FM32519"Figure 5-3 shows the internetwork topology.PAGENUM=109 ID="BP115"LABEL="5-3" FLOAT="0"ID="FM32519"AppleTalk Routing Information Filter ExampleFILEREF="atrtinfo.tif"Extended network 165-170 can be hidden from the rest of the organization by configuring an outgoing route filter on Router C. The route being hidden from the rest of the network is extended network 165-170. Router C's connection to the departments outside Accounting is through the FDDI backbone. The destination from which to hide the Accounting network is most easily defined as the interface to the backbone. Note that no node in the Accounting network will be able to see the rest of the internetwork.When configuring this example, set the following parameters, as shown in IDREF="FM31226"Table 5-3. LABEL="5-3" PGWIDE=0 TOCENTRY="1"ID="FM31226"AppleTalk Routing Information Filter Example ParametersCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="12*"COLNAME=2 COLWIDTH="14*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ParameterCOLNAME=2 ROTATE="0" MOREROWS="0"Example EntryVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"ActionCOLNAME=2 ROTATE="0" MOREROWS="0"DenyCOLNAME=1 ROTATE="0" MOREROWS="0"Filtered Route:Route to Network or ZoneCOLNAME=2 ROTATE="0" MOREROWS="0"Extended NetworkCOLNAME=1 ROTATE="0" MOREROWS="0"Network Number/RangeCOLNAME=2 ROTATE="0" MOREROWS="0"165-170COLNAME=1 ROTATE="0" MOREROWS="0"Do Not Send Route To:InterfaceCOLNAME=2 ROTATE="0" MOREROWS="0"FDDIPAGENUM=110 ID="BP116"RENDERAS="SECT1"ID="FM38444"IPX FilteringIDXID="w1295"BOOK="_idx" COLLECTION="nw41" TIDREF="i1932"IDXID="w1296"BOOK="_idx" COLLECTION="nw41" TIDREF="i1499"IPX supports the following filters:MARK=BULLETIDREF="FM26030"IPX SAP Filters  (service information filters)IDREF="FM33977"IPX RIP Filters  (routing information filters)IDREF="FM29536"IPX NetBIOS and Packet Forwarding Filters RENDERAS="SECT2"ID="FM26030"IPX SAP FiltersIDXID="w1297"BOOK="_idx" COLLECTION="nw41" TIDREF="i1958"IDXID="w1298"BOOK="_idx" COLLECTION="nw41" TIDREF="i1503"Servers and routers on an IPX network exchange information about the name, type, and location of the various service providers on the internetwork by way of SAP packets. This information is distributed to users through SAP packets. SAP filters limit the propagation of this information, providing limited security at the servers and reducing the bandwidth required by the SAP exchanges.There are two types of service information filters:MARK=BULLETIDREF="FM18872"IPX Outgoing SAP Filters  (service advertisement filters)IDREF="FM84667"IPX Incoming SAP Filters  (service acceptance filters)SAP filters work only on servers running the RIP and SAP protocols. They do not work on servers running the NLSPTM protocol. For filtering to work, make sure that either IPXRTR is configured for RIP/SAP only; or that the bind options on selected interfaces are set up to read RIP=Yes, SAP=Yes, and NLSP=No.RENDERAS="SECT3"ID="FM18872"IPX Outgoing SAP FiltersIDXID="w1299"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"IDXID="w1300"BOOK="_idx" COLLECTION="nw41" TIDREF="i3157"IDXID="w1301"BOOK="_idx" COLLECTION="nw41" TIDREF="i3951"IDXID="w1302"BOOK="_idx" COLLECTION="nw41" TIDREF="i4071"IDXID="w1303"BOOK="_idx" COLLECTION="nw41" TIDREF="i1503"Outgoing SAP filters restrict the propagation of the SAP information that is known to the server. An outgoing SAP filter specifies the service provider and the potential recipient of the information. The service provider is defined by a service name and service type. The recipient is defined as an outbound interface. The filter is applied to all servers, users, and routers that would receive the SAP information through the interface. PAGENUM=111 ID="BP117"RENDERAS="SECT3"ID="FM84667"IPX Incoming SAP FiltersIDXID="w1304"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"IDXID="w1305"BOOK="_idx" COLLECTION="nw41" TIDREF="i1780"IDXID="w1306"BOOK="_idx" COLLECTION="nw41" TIDREF="i3951"IDXID="w1307"BOOK="_idx" COLLECTION="nw41" TIDREF="i4071"IDXID="w1308"BOOK="_idx" COLLECTION="nw41" TIDREF="i1503"Incoming SAP filters let the server discard information about a particular service provider. The filtered SAP information is not recorded in the local SAP information table or propagated to other routers or servers. The SAP filter includes the service name and service type. An incoming SAP filter may also specify the source of the SAP information to be filtered. The source identifies the interface from which the SAP information was received.RENDERAS="SECT3"How to Configure IPX Incoming SAP FilteringIDXID="w1309"BOOK="_idx" COLLECTION="nw41" TIDREF="i1499"IDXID="w1310"BOOK="_idx" COLLECTION="nw41" TIDREF="i761"Filtering support must be enabled for IPX in INETCFG for filtering to work.To configure IPX incoming SAP filtering, load FILTCFG and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"Incoming SAP Filters (CLASS=MENUITEM MOREINFO="NONE"Incoming SAP Filters menu appears)Complete the following steps:PERFORMANCE="REQUIRED"Select CLASS=MENUITEM MOREINFO="NONE"Status and toggle the choice to read CLASS=MENUITEM MOREINFO="NONE"Enabled or CLASS=MENUITEM MOREINFO="NONE"Disabled to specify the status of the filters.Disabling the filter status means that nothing will be filtered.It may be easier to configure filters while they are disabled. Otherwise you may experience temporary service loss while you are adding and setting up wildcard filters.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Action and
 toggle the choice to permit or deny the services on the filter list. This specifies the action taken with an incoming service (SAP packet) in the filter list. If you select to permit the services, the SAP information will be received from the local networks. If you select to deny the services, the SAP information will not be received from the local networks.Changing a filter to permit the services on the filter list when no filters are specified will deny all services.PAGENUM=111 ID="BP118"PAGENUM=112PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Filters option to display a list of permitted or denied services.This specifies which incoming services are accepted (permitted) or filtered (denied) on an interface.PERFORMANCE="REQUIRED"ID="FM55788"Modify the service list.Press 
MOREINFO="NONE"<Insert> to add a new service; or select a service from the list and press 
MOREINFO="NONE"<Enter> to modify the service, or 
MOREINFO="NONE"<Delete> to remove it. If you are modifying or adding a new filter, modify the following parameters from the 
CLASS=MENUITEM MOREINFO="NONE"Define Filter menu:
MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Service Name---Press MOREINFO="NONE"<Insert>, and select from a list of unfiltered NetWare services known to the router, or enter a service name.You can use the asterisk (*) and question mark (?) wildcards. The * wildcard is equal to zero or more character matches. The ? wildcard is equal to precisely one character match. For example, SJF-IPD matches SJF-IPD, SJF-IPD2, and SJF-IPD-MKTG; while SJF-IPD? matches only SJF-IPD2. You can enter several wildcard characters in a string. It is recommended that you enter exceptions to wildcards first when working with an enabled filter list.CLASS=MENUITEM MOREINFO="NONE"Service Type---Enter a hexadecimal SAP number, or press MOREINFO="NONE"<Insert>, then select from a list of defined IPX service types. You can use FFF as a wildcard for any or all types.CLASS=MENUITEM MOREINFO="NONE"Interface---Press MOREINFO="NONE"<Enter>, and select an interface on which you want to filter the service.CLASS=MENUITEM MOREINFO="NONE"Comment---Enter an optional short description.PERFORMANCE="REQUIRED"ID="FM77387"Press 
MOREINFO="NONE"<Esc> and save the information.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Exceptions to display a list of exceptions to the permitted or denied services.Lists the incoming services to which the action---permit or deny---does not apply. These are the exceptions to the filter list. You can specify a wildcard filter from the filter list.
PAGENUM=112 ID="BP119"PAGENUM=113PERFORMANCE="REQUIRED"Modify the exceptions list.Press 
MOREINFO="NONE"<Insert> to add a new service; or select a service from the list and press 
MOREINFO="NONE"<Enter> to modify the service, or 
MOREINFO="NONE"<Delete> to remove it. Refer to 
IDREF="FM55788"Step 4 and 
IDREF="FM77387"Step 5 to modify or add a filter.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to return to the 
CLASS=MENUITEM MOREINFO="NONE"IPX menu.RENDERAS="SECT3"How to Configure IPX SAP Outgoing FilteringIDXID="w1311"BOOK="_idx" COLLECTION="nw41" TIDREF="i1499"IDXID="w1312"BOOK="_idx" COLLECTION="nw41" TIDREF="i761"Filtering support must be enabled for IPX in INETCFG for filtering to work.To configure IPX outgoing SAP filtering, load FILTCFG and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing SAP Filters (CLASS=MENUITEM MOREINFO="NONE"Outgoing SAP Filters menu appears)Complete the following steps:PERFORMANCE="REQUIRED"Select CLASS=MENUITEM MOREINFO="NONE"Status and toggle the choice to read CLASS=MENUITEM MOREINFO="NONE"Enabled or CLASS=MENUITEM MOREINFO="NONE"Disabled to specify the status of the filters.Disabling the filter status means that nothing will be filtered.It may be easier to configure filters while they are disabled. Otherwise you may experience temporary service loss while you are adding and setting up wildcard filters.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Action and
 toggle the choice to permit or deny the services on the filter list. This specifies the action taken with an outgoing service (SAP packet) in the filter list. If you select to permit the services, the SAP information will be broadcast to the local networks. If you select to deny the services, the SAP information will not be broadcast to the local networks.Changing a filter to permit the services on the filter list when no filters are specified will deny all services.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Filters to display a list of permitted or denied services.This specifies which outgoing services are accepted (permitted) or filtered (denied) on an interface.
PAGENUM=114 ID="BP120"PERFORMANCE="REQUIRED"ID="FM73751"Modify the service list.Press 
MOREINFO="NONE"<Insert> to add a new service; or select a service from the list and press 
MOREINFO="NONE"<Enter> to modify the service, or 
MOREINFO="NONE"<Delete> to remove it. If you are modifying or adding a new filter, modify the following parameters from the 
CLASS=MENUITEM MOREINFO="NONE"Define Filter menu:
MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Service Name---Press MOREINFO="NONE"<Insert>, and select from a list of unfiltered NetWare services known to the router, or enter a service name.You can use the asterisk (*) and question mark (?) wildcards. The * wildcard is equal to zero or more character matches. The ? wildcard is equal to precisely one character match. For example, SJF-IPD matches SJF-IPD, SJF-IPD2, and SJF-IPD-MKTG; while SJF-IPD? matches only SJF-IPD2. You can enter several wildcard characters in a string. It is recommended that you enter exceptions to wildcards first when working with an enabled filter list.CLASS=MENUITEM MOREINFO="NONE"Service Type---Enter a hexadecimal SAP number, or press MOREINFO="NONE"<Insert> then select from a list of defined IPX service types. You can use FFF as a wildcard for any or all types.CLASS=MENUITEM MOREINFO="NONE"Interface---Press MOREINFO="NONE"<Enter>, and select an interface to be filtered from the list.CLASS=MENUITEM MOREINFO="NONE"Comment---Enter an optional short description.PERFORMANCE="REQUIRED"ID="FM79256"Press 
MOREINFO="NONE"<Esc> and save the information.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Exceptions to display a list of exceptions to the permitted or denied services.Lists the incoming services to which the action---permit or deny--- does not apply. These are the exceptions to the filter list. You can specify a wildcard filter from the filter list.PERFORMANCE="REQUIRED"Modify the exceptions list.Press 
MOREINFO="NONE"<Insert> to add a new service; or select a service from the list and press 
MOREINFO="NONE"<Enter> to modify the service, or 
MOREINFO="NONE"<Delete> to remove it. Refer to 
IDREF="FM73751"Step 4 and 
IDREF="FM79256"Step 5 to add or modify a filter.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to return to the 
CLASS=MENUITEM MOREINFO="NONE"IPX menu.
PAGENUM=115 ID="BP121"RENDERAS="SECT2"IPX SAP Filter ExampleIDXID="w1313"BOOK="_idx" COLLECTION="nw41" TIDREF="i1499"IDXID="w1314"BOOK="_idx" COLLECTION="nw41" TIDREF="i1506"In this example, two departmental networks are connected to a corporate network through a WAN link between Router 1 and Router 2. The two routers communicate with each other using the RIP and SAP routing protocol. RIP enables routers to send out periodic updates of service and routing information. The internetwork topology is shown in IDREF="FM23621"Figure 5-4.Either Router 1 or Router 2 can be set up to do the following. RIP/SAP can be run over the WAN link with outbound SAP filter, and with NLSP on the LAN. RIP/SAP can be run on the LAN with inbound filter, and with NLSP on the WAN. RIP can be run on the LAN and WAN links, and both inbound and outbound filtering is enabled.LABEL="5-4" FLOAT="0"ID="FM23621"IPX SAP Filter ExampleFILEREF="ipxserv.tif"PAGENUM=115 ID="BP122"PAGENUM=116To minimize the load on the WAN link, an IPX SAP filter is configured on Router 1 and Router 2. This filter cuts down the periodic service information updates across the WAN link by advertising only a few selected servers. The clients across the WAN link can access the servers on the other network by first attaching to these selected servers.When configuring this example, set the following parameters, as shown in IDREF="FM25428"Table 5-4LABEL="5-4" PGWIDE=0 TOCENTRY="1"ID="FM25428"IPX SAP Filter Example ParametersCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"NAMEST=1 NAMEEND=2 SPANNAME=SPAN1T2 ALIGN=LEFTVALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ParameterCOLNAME=2 ROTATE="0" MOREROWS="0"Example EntryVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Router 1 ActionCOLNAME=2 ROTATE="0" MOREROWS="0"Permit ServicesSPANNAME=SPAN1T2 ROTATE="0" MOREROWS="0"Router 1 FiltersCOLNAME=1 ROTATE="0" MOREROWS="0"Filter 1:Service NameService TypeInterfaceFilter 2:Service NameService TypeInterfaceCOLNAME=2 ROTATE="0" MOREROWS="0"SJF-DEPT1FFFF (All Types)WAN-1SJF-DEPT2FFFF (All Types)WAN-1COLNAME=1 ROTATE="0" MOREROWS="0"Router 2 ActionCOLNAME=2 ROTATE="0" MOREROWS="0"Permit ServicesSPANNAME=SPAN1T2 ROTATE="0" MOREROWS="0"Router 2 Filters:COLNAME=1 ROTATE="0" MOREROWS="0"Service NameService TypeInterfaceCOLNAME=2 ROTATE="0" MOREROWS="0"CORP-MAILFFFF (All Types)WAN-1RENDERAS="SECT2"ID="FM33977"IPX RIP FiltersIDXID="w1315"BOOK="_idx" COLLECTION="nw41" TIDREF="i1955"IDXID="w1316"BOOK="_idx" COLLECTION="nw41" TIDREF="i1503"Routers and servers on an IPX network exchange routing information through RIP packets. RIP filters limit the propagation of this information, providing limited security to IPX networks, reducing the bandwidth required for RIP updates and reducing the memory requirements for routing tables. PAGENUM=116 ID="BP123"PAGENUM=117There are two types of IPX RIP filters:MARK=BULLETIDREF="FM62671"IPX Outgoing RIP Filters IDREF="FM11689"IPX Incoming RIP Filters  RIP filters work only on servers running the RIP protocol. They do not work for servers running the NLSP protocol. Use RIP filters with care since they can partition a physical network into two or more pieces.RENDERAS="SECT3"ID="FM62671"IPX Outgoing RIP FiltersIDXID="w1317"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"IDXID="w1318"BOOK="_idx" COLLECTION="nw41" TIDREF="i3151"Outgoing RIP filters restrict the propagation of information by the router. An outgoing RIP filter specifies the network and the potential recipient of the information. The recipient is an outbound interface. The filter is applied to all servers, users, and routers that receive the RIP information through that interface.RENDERAS="SECT3"ID="FM11689"IPX Incoming RIP FiltersIDXID="w1319"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"IDXID="w1320"BOOK="_idx" COLLECTION="nw41" TIDREF="i1775"Incoming RIP filters let the router discard information about a particular network. The filtered network is not recorded in the local forwarding table and cannot be propagated to other routers, servers, or users. The filter includes the network and the source of the route. The source identifies the interface from which the routing information was received. This is the most effective route filter for improving security.RENDERAS="SECT3"How to Configure IPX Incoming RIP FilteringIDXID="w1321"BOOK="_idx" COLLECTION="nw41" TIDREF="i1499"IDXID="w1322"BOOK="_idx" COLLECTION="nw41" TIDREF="i761"Filtering support must be enabled for IPX in INETCFG for filtering to work.To configure IPX incoming RIP filtering, load FILTCFG and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"Incoming RIP Filters (CLASS=MENUITEM MOREINFO="NONE"Incoming RIP Filters menu appears)PAGENUM=117 ID="BP124"PAGENUM=118Complete the following steps:PERFORMANCE="REQUIRED"Select CLASS=MENUITEM MOREINFO="NONE"Status and toggle the choice to read CLASS=MENUITEM MOREINFO="NONE"Enabled or CLASS=MENUITEM MOREINFO="NONE"Disabled to specify the status of the filters.Disabling the filter status means that nothing will be filtered.It may be easier to configure filters while they are disabled. Otherwise you may experience temporary service loss while you are adding and setting up wildcard filters.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Action and toggle the choice to permit or deny the networks on the filter list. This specifies the action taken on an incoming network (RIP packet) in the filter list. If you select to permit networks, the RIP information will be received from local networks. If you select to deny networks, the RIP information will not be received from local networks.Changing a filter to permit the services on the filter list when no filters are specified will deny all services.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Filters to display a list of permitted or denied networks.Specifies which incoming network numbers are sent (permitted) or filtered (denied) on an interface.PERFORMANCE="REQUIRED"ID="FM55940"Modify the network list.Press 
MOREINFO="NONE"<Insert> to add a new network filter to the list; or select a filter from the list and press 
MOREINFO="NONE"<Enter> to modify the filter, or 
MOREINFO="NONE"<Delete> to remove it. If you are modifying or adding a new filter, modify the following parameters from the 
CLASS=MENUITEM MOREINFO="NONE"Define Filter menu:Whenever the internal network number of a server is filtered, the SAPs from the server are also filtered automatically.MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Network CLASS=MENUITEM MOREINFO="NONE"Number---Enter a four-byte hexadecimal number that identifies the IPX network.CLASS=MENUITEM MOREINFO="NONE"Network CLASS=MENUITEM MOREINFO="NONE"Mask---Enter a 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. One bit in the network mask means it must match that bit. For example, C9000000/FFFFFF00 will match C90000XX network numbers.PAGENUM=119 ID="BP125"Bit masks do not need to be contiguous for filters.CLASS=MENUITEM MOREINFO="NONE"Interface---Select the interface to be filtered from the list.CLASS=MENUITEM MOREINFO="NONE"Comment---Enter an optional short description.PERFORMANCE="REQUIRED"ID="FM23451"Press 
MOREINFO="NONE"<Esc> and save the information.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Exceptions to display a list of exceptions to the permitted or denied networks.Lists the incoming network numbers to which the action---permit or deny---does not apply. These are the exceptions to the filter list.PERFORMANCE="REQUIRED"Modify the exceptions list.Press 
MOREINFO="NONE"<Insert> to add a new network filter; or select a filter from the list and press 
MOREINFO="NONE"<Enter> to modify the filter, or 
MOREINFO="NONE"<Delete> to remove it. Refer to 
IDREF="FM55940"Step 4 and 
IDREF="FM23451"Step 5 to add or modify a filter.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to return to the 
CLASS=MENUITEM MOREINFO="NONE"IPX menu.RENDERAS="SECT3"How to Configure IPX Outgoing RIP FilteringIDXID="w1323"BOOK="_idx" COLLECTION="nw41" TIDREF="i1499"IDXID="w1324"BOOK="_idx" COLLECTION="nw41" TIDREF="i761"Filtering support must be enabled for IPX in INETCFG for filtering to work.To configure IPX outgoing RIP filtering, load FILTCFG and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing RIP Filters (CLASS=MENUITEM MOREINFO="NONE"Outgoing RIP Filters menu appears)Complete the following steps:PERFORMANCE="REQUIRED"Select CLASS=MENUITEM MOREINFO="NONE"Status and toggle the choice to read CLASS=MENUITEM MOREINFO="NONE"Enabled or CLASS=MENUITEM MOREINFO="NONE"Disabled to specify the status of the filters.Disabling the filter status means that nothing will be filtered.It may be easier to configure filters while they are disabled. Otherwise you may experience temporary service loss while you are adding and setting up wildcard filters.PAGENUM=119 ID="BP126"PAGENUM=120PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Action and toggle the choice to permit or deny the networks on the filter list. This specifies the action taken on an outgoing network (RIP packet) in the filter list. If you select to permit networks, the RIP information will be broadcast to local networks. If you select to deny networks, the RIP information will not be broadcast to local networks.Changing a filter to permit the services on the filter list when no filters are specified will deny all services.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Filters to display a list of permitted or denied networks.Specifies which outgoing network numbers are sent (permitted) or filtered (denied) on an interface.PERFORMANCE="REQUIRED"ID="FM57473"Modify the network list.Press 
MOREINFO="NONE"<Insert> to add a new network filter; or select a filter from the list and press 
MOREINFO="NONE"<Enter> to modify the filter, or 
MOREINFO="NONE"<Delete> to remove it. If you are modifying or adding a new filter, modify the following parameters from the 
CLASS=MENUITEM MOREINFO="NONE"Define Filter menu:Whenever the internal network number of a server is filtered, the SAPs from the server are also filtered automatically.MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Network CLASS=MENUITEM MOREINFO="NONE"Number---Enter a four-byte hexadecimal number that identifies the IPX network.CLASS=MENUITEM MOREINFO="NONE"Network CLASS=MENUITEM MOREINFO="NONE"Mask---Enter a 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. One bit in the mask means that bit must be matched. For example, C9000000/FFFFFF00 will match C90000XX network numbers.Bit masks do not need to be contiguous for filters.CLASS=MENUITEM MOREINFO="NONE"Interface---Select the network interface on which you want to filter the network number.CLASS=MENUITEM MOREINFO="NONE"Comment---Enter an optional short description.PERFORMANCE="REQUIRED"ID="FM20323"Press 
MOREINFO="NONE"<Esc> and save the information.
PAGENUM=121 ID="BP127"PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Exceptions to display a list of exceptions to the permitted or denied networks.Lists the outgoing network numbers to which the action---permit or deny---does not apply. These are the exceptions to the filter list.PERFORMANCE="REQUIRED"Modify the exceptions list.Press 
MOREINFO="NONE"<Insert> to add a new network filter; or select a filter from the list and press 
MOREINFO="NONE"<Enter> to modify the filter, or 
MOREINFO="NONE"<Delete> to remove it. Refer to 
IDREF="FM57473"Step 4 and 
IDREF="FM20323"Step 5 to add or modify a filter.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to return to the 
CLASS=MENUITEM MOREINFO="NONE"IPX menu.RENDERAS="SECT3"IPX RIP Filter ExampleIDXID="w1325"BOOK="_idx" COLLECTION="nw41" TIDREF="i1499"IDXID="w1326"BOOK="_idx" COLLECTION="nw41" TIDREF="i1504"In this example, a corporate network is connected to a global internetwork through a WAN link. Users on the corporate network can access all of the servers on the network and on the global internetwork. However, only two designated servers, DEMO_SRVR and TRANSFER_SRVR, can be accessed from outside the corporate network. To do this, an inbound RIP filter is configured on Router 1. This filter only accepts and advertises the internal network numbers of the two servers to the global internetwork. The filter also suppresses the advertisement of all services on the corporate network (except the two designated servers). Outbound filters are not always effective. In this case, static routes could be configured to still access the filtered networks from the global internetwork. Any packets that reach Router 1 will be forwarded. With inbound filters, Router 1 does not have a route and will drop the packets.The topology is shown in IDREF="FM79425"Figure 5-5.PAGENUM=122 ID="BP128"LABEL="5-5" FLOAT="0"ID="FM79425"IPX Routing Information Filter ExampleFILEREF="ipxroute.tif"When configuring this example, set the following parameters, as shown in IDREF="FM79903"Table 5-5.LABEL="5-5" PGWIDE=0 TOCENTRY="1"ID="FM79903"IPX Incoming Filter Example ParametersCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"NAMEST=1 NAMEEND=2 SPANNAME=SPAN1T2 ALIGN=LEFTVALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ParameterCOLNAME=2 ROTATE="0" MOREROWS="0"Example EntryVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"ActionCOLNAME=2 ROTATE="0" MOREROWS="0"Permit NetworksSPANNAME=SPAN1T2 ROTATE="0" MOREROWS="0"Filters:COLNAME=1 ROTATE="0" MOREROWS="0"Filter 1NetworkMaskInterfaceFilter 2NetworkMaskInterfaceCOLNAME=2 ROTATE="0" MOREROWS="0"00000023FFFFFFFFBackbone00000089FFFFFFFFBackbonePAGENUM=122 ID="BP129"PAGENUM=123RENDERAS="SECT2"ID="FM29536"IPX NetBIOS and Packet Forwarding FiltersIDXID="w1327"BOOK="_idx" COLLECTION="nw41" TIDREF="i1503"IDXID="w1328"BOOK="_idx" COLLECTION="nw41" TIDREF="i1503"IDXID="w1329"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"IDXID="w1330"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"IPX packet forwarding filters allow the router to filter a packet based on the source and destination address fields and the packet type. The source and destination may be specified in the filter as an interface, a network number, or a node address. Some services can be identified by the presence of expected values in one or more of the following packet fields:MARK=BULLETPacket typeDestination socketNetBIOS filters allow the router to forward NetBIOS broadcast packets only on selected interfaces.IPX NetBIOS and packet forwarding filters will work while using either NLSP or RIP/SAP routing modes.RENDERAS="SECT2"Configuring IPX Packet ForwardingIDXID="w1331"BOOK="_idx" COLLECTION="nw41" TIDREF="i1499"IDXID="w1332"BOOK="_idx" COLLECTION="nw41" TIDREF="i761"Filtering support must be enabled for IPX in INETCFG for filtering to work.To configure IPX packet forwarding filters, load FILTCFG and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX > Select CLASS=MENUITEM MOREINFO="NONE"NetBIOS and Packet Forwarding Filters (CLASS=MENUITEM MOREINFO="NONE"NetBIOS and Packet Forwarding Filters menu appears)Complete the following steps:PERFORMANCE="REQUIRED"Select CLASS=MENUITEM MOREINFO="NONE"Status and toggle the choice to read CLASS=MENUITEM MOREINFO="NONE"Enabled or CLASS=MENUITEM MOREINFO="NONE"Disabled to specify the status of the filters.It may be easier to configure filters while they are disabled. Otherwise you may experience temporary service loss while you are adding and setting up wildcard filters.PAGENUM=123 ID="BP130"PAGENUM=124PERFORMANCE="REQUIRED"Perform the following steps to configure IPX NetBIOS broadcast filters:PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"NetBIOS Broadcast Filters Action and
 toggle the choice to permit or deny the IPX NetBIOS packets on the listed interfaces.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"NetBIOS Broadcast Filters Interfaces to display a list of permitted or denied interfaces.PERFORMANCE="REQUIRED"Modify the list.Press MOREINFO="NONE"<Insert> to add a new interface to the list; or select an interface from the list and press MOREINFO="NONE"<Enter> to modify the interface, or MOREINFO="NONE"<Delete> to remove it. PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Packet Forwarding Filters 
CLASS=MENUITEM MOREINFO="NONE"Action and toggle the choice to permit or deny the packet forwarding filters on the filter list. Specifies whether to forward (permit) or filter (deny) IPX packets in the filter list.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Filters to display a list of permitted or denied packet filters.PERFORMANCE="REQUIRED"Modify the filter list.Press 
MOREINFO="NONE"<Insert> to add a new network filter; or select a filter from the list and press 
MOREINFO="NONE"<Enter> to modify the filter, or 
MOREINFO="NONE"<Delete> to remove it. If you are modifying or adding a new filter, perform the following substeps from the 
CLASS=MENUITEM MOREINFO="NONE"Define Filter menu:PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"ID="FM60920"Select 
CLASS=MENUITEM MOREINFO="NONE"Source Type to select where the incoming IPX packet originated. Your choices are CLASS=MENUITEM MOREINFO="NONE"Interface, CLASS=MENUITEM MOREINFO="NONE"Network, or CLASS=MENUITEM MOREINFO="NONE"Node. PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Source and press
MOREINFO="NONE" <Enter> to specify the source. Select one of the following, based on what you selected in IDREF="FM60920"Step 5a:MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Interface---Select a network interface from the list, then press MOREINFO="NONE"<Enter>.To stop access to or from this RTR/server, select the CLASS=MENUITEM MOREINFO="NONE"Interface option and select CLASS=MENUITEM MOREINFO="NONE"Internal Network as the interface.PAGENUM=125 ID="BP131"CLASS=MENUITEM MOREINFO="NONE"Network---Enter the network number and network mask of an IPX segment or internal network address. The network number is used with the network mask to allow a range of networks to be specified with one filter.CLASS=MENUITEM MOREINFO="NONE"Node---Enter the network number and node number of an IPX node (host).PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Packet Description and press 
MOREINFO="NONE"<Enter> to select from a list of defined packet types, or press 
MOREINFO="NONE"<Insert> to define a packet type. Enter the following information to define the type of IPX packet you can filter:MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Packet Name---Enter a name for the packet.CLASS=MENUITEM MOREINFO="NONE"Packet Type---Enter a one-byte packet type number in hexadecimal. The FF wildcard matches all packet numbers.CLASS=MENUITEM MOREINFO="NONE"Destination Socket---Enter a 2-byte socket number in hexadecimal. The wildcard FFFF matches all socket numbers.CLASS=MENUITEM MOREINFO="NONE"Comment---Enter an optional short description.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Destination Type to select where an outgoing IPX packet is going. Your choices are CLASS=MENUITEM MOREINFO="NONE"Interface, CLASS=MENUITEM MOREINFO="NONE"Network, or CLASS=MENUITEM MOREINFO="NONE"Node.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Destination and select from a list of network interfaces.
MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Interface---Select a network interface from the list, then press MOREINFO="NONE"<Enter>.CLASS=MENUITEM MOREINFO="NONE"Network---Type the hexadecimal network number and network mask of an IPX segment or internal network address.CLASS=MENUITEM MOREINFO="NONE"Node---Type the network number and node number of an IPX node (host).PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Comment and enter an optional short description.PERFORMANCE="REQUIRED"ID="FM38765"Press 
MOREINFO="NONE"<Esc> and save the filter information.
PAGENUM=126 ID="BP132"PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Exceptions to display a list of exceptions to the filters in the Filters List. Lists the IPX packet types to which the action---permit or deny---does not apply. These are the exceptions to the filter list. You can specify to block all packets between two interfaces, except those from a specified network.PERFORMANCE="REQUIRED"Modify the exceptions list.Press 
MOREINFO="NONE"<Insert> to add a new filter; or select a filter from the list and press 
MOREINFO="NONE"<Enter> to modify the filter, or 
MOREINFO="NONE"<Delete> to remove it. Refer to 
IDREF="FM60920"Step 5a through 
IDREF="FM38765"Step 5g to modify or add a filter.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> and exit the 
CLASS=MENUITEM MOREINFO="NONE"NetBIOS and Packet Forwarding Filters menu.RENDERAS="SECT3"IPX Packet Forwarding Filter ExampleIDXID="w1333"BOOK="_idx" COLLECTION="nw41" TIDREF="i1499"IDXID="w1334"BOOK="_idx" COLLECTION="nw41" TIDREF="i1506"In this example, an FDDI backbone connects several departments in an organization. Routers A, B, and C connect the departmental networks to the backbone. Within the organization, users can access all servers. However, the Human Resources (HR) servers can be accessed only by HR employees. To make the HR servers secure, packet forwarding filters are used in addition to the normal NetWare password security. Note that some of the HR employees are connected to different networks than the one HR servers are connected to. IDREF="FM22756"Figure 5-6 shows the internetwork topology.PAGENUM=127 ID="BP133"LABEL="5-6" FLOAT="0"ID="FM22756"IPX Packet Forwarding Filter Example FILEREF="ipxforwd.tif"Routers B and C do not require filters because users can access all corporate servers (except for the HR server). Packet forwarding filters are installed on Router A to block packets from the FDDI interface to the HR servers, except when the packets are from the nodes 59:00001B2700F3 and 55:00001B2700F0.PAGENUM=127 ID="BP134"PAGENUM=128When configuring this example, set the following parameters, as shown in IDREF="FM12472"Table 5-6.LABEL="5-6" PGWIDE=0 TOCENTRY="1"ID="FM12472"IPX Packet Forwarding Filter Example ParametersCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"NAMEST=1 NAMEEND=2 SPANNAME=SPAN1T2 ALIGN=LEFTVALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ParameterCOLNAME=2 ROTATE="0" MOREROWS="0"Example EntryVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"ActionCOLNAME=2 ROTATE="0" MOREROWS="0"Deny PacketsSPANNAME=SPAN1T2 ROTATE="0" MOREROWS="0"Filter List:COLNAME=1 ROTATE="0" MOREROWS="0"Source PacketDestinationSourcePacketDestinationCOLNAME=2 ROTATE="0" MOREROWS="0"Interface, FDDI<Any>Network, 10/FFFFFFFFInterface, FDDI<Any>Network, 12/FFFFFFFFSPANNAME=SPAN1T2 ROTATE="0" MOREROWS="0"Exceptions:COLNAME=1 ROTATE="0" MOREROWS="0"SourcePacketDestinationSourcePacketDestinationSourcePacketDestinationSourcePacketDestinationCOLNAME=2 ROTATE="0" MOREROWS="0"Node, 59:00001B2700F3<Any>Network, 10/FFFFFFFFNode, 55:00001B2700F0<Any>Network, 10/FFFFFFFFNode 59:00001B2700F3AnyNetwork, 12/FFFFFFFFNode 55:00001B2700F0AnyNetwork, 12/FFFFFFFFPAGENUM=128 ID="BP135"PAGENUM=129RENDERAS="SECT1"ID="FM96491"TCP/IP FilteringIDXID="w1335"BOOK="_idx" COLLECTION="nw41" TIDREF="i4450"IDXID="w1336"BOOK="_idx" COLLECTION="nw41" TIDREF="i1499"TCP/IP supports the following filters:MARK=BULLETIDREF="FM77090"IP Routing Information Filters IDREF="FM70119"IP Packet Forwarding Filters RENDERAS="SECT2"ID="FM77090"IP Routing Information FiltersIDXID="w1337"BOOK="_idx" COLLECTION="nw41" TIDREF="i1503"IDXID="w1338"BOOK="_idx" COLLECTION="nw41" TIDREF="i1910"IP routing information filters let the router restrict the routes that it accepts from neighbors (incoming filters) and limit the advertised routes (outgoing filters). The router can use RIP, OSPF, or EGP to exchange routing information with other neighboring routers. MARK=BULLETRIP filters control the propagation of routing information and hide the existence of specific IP networks from other routers.OSPF filters control the propagation of routing information from non-OSPF domains (RIP, EGP and so on) to the OSPF domain. EGP filters define the routes a router can share with other EGP peers.RENDERAS="SECT3"IP Incoming FiltersIDXID="w1339"BOOK="_idx" COLLECTION="nw41" TIDREF="i1503"IDXID="w1340"BOOK="_idx" COLLECTION="nw41" TIDREF="i1910"IP incoming filters let the router discard information about a particular route. The filtered route is not recorded in the local forwarding table and cannot be propagated to other routers or hosts. The filter includes the destination network and the source of the route. The source identifies the interface from which the route information was received or the address of the router that provided the information. The destination network is an IP address mask pair.You can apply IP incoming filters only to RIP and EGP routes. You cannot filter routes to directly connected networks.MARK=BULLETRIP incoming filters restrict the acceptance of routing information from other RIP routers.EGP incoming filters restrict the routes accepted from the EGP peers.PAGENUM=130 ID="BP136"RENDERAS="SECT3"IP Outgoing Filters IDXID="w1341"BOOK="_idx" COLLECTION="nw41" TIDREF="i1503"IDXID="w1342"BOOK="_idx" COLLECTION="nw41" TIDREF="i1910"IP outgoing filters restrict the propagation of route information from the router. You can also use them to control the flow of routes between the routing protocols. An outgoing filter specifies a route and a potential recipient of the information. The recipient is either an outbound interface or the IP address of another router.You can apply IP outgoing filters to RIP, EGP, and OSPF routes. You cannot filter directly-connected networks.MARK=BULLETRIP outgoing filters restrict the advertising of routing information by the router using RIP. These routes may be learned from RIP, OSPF, EGP, or static routes.OSPF external route filters define the routes learned from RIP, EGP, or static routes that will be propagated into the OSPF domain.EGP outgoing filters restrict the routes that are propagated to the EGP peers. These routes may be learned from the RIP, OSPF, or static routes.RENDERAS="SECT3"How to Configure IP Incoming Routing Information FiltersIDXID="w1343"BOOK="_idx" COLLECTION="nw41" TIDREF="i1499"IDXID="w1344"BOOK="_idx" COLLECTION="nw41" TIDREF="i761"Filtering support must be enabled for IP in INETCFG for filtering to work.To configure IP incoming RIP filters, load FILTCFG and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Incoming RIP Filters (CLASS=MENUITEM MOREINFO="NONE"Incoming RIP Filters menu appears)Complete the following steps:PERFORMANCE="REQUIRED"Select CLASS=MENUITEM MOREINFO="NONE"Status and toggle the choice to read CLASS=MENUITEM MOREINFO="NONE"Enabled or CLASS=MENUITEM MOREINFO="NONE"Disabled to specify the status of the selected filters.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Action and
 toggle the choice to permit or deny the routes in the filter list. Specifies whether to accept (permit) or ignore (deny) all route information packets in the filter list.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Filters to display a list of permitted or denied routes.
PAGENUM=131 ID="BP137"PERFORMANCE="REQUIRED"ID="FM71822"Modify the route list.Press 
MOREINFO="NONE"<Insert> to add a new route filter; or select a filter from the list and press 
MOREINFO="NONE"<Enter> to modify the filter, or 
MOREINFO="NONE"<Delete> to remove it. If you are modifying or adding a new filter, modify the following parameters from the 
CLASS=MENUITEM MOREINFO="NONE"Define Filter menu:
MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Route CLASS=MENUITEM MOREINFO="NONE"to Network or Host---Specify the type of route to be filtered. Your choices are CLASS=MENUITEM MOREINFO="NONE"All Routes, CLASS=MENUITEM MOREINFO="NONE"Host, or CLASS=MENUITEM MOREINFO="NONE"Network.CLASS=MENUITEM MOREINFO="NONE"IP Address of Network/Host---Enter a 4-byte IP address in dotted decimal notation. You do not need to enter this if you selected CLASS=MENUITEM MOREINFO="NONE"All Routes for the CLASS=MENUITEM MOREINFO="NONE"Route to Network/Hosts.CLASS=MENUITEM MOREINFO="NONE"Subnetwork Mask---Enter a 4-byte mask address in dotted decimal or hexadecimal notation. Do this only if you selected CLASS=MENUITEM MOREINFO="NONE"Network for the CLASS=MENUITEM MOREINFO="NONE"Route to Network/Hosts parameter.CLASS=MENUITEM MOREINFO="NONE"Source Type---Select the destination type that the route will be advertised to or blocked from. Your choices are CLASS=MENUITEM MOREINFO="NONE"Interface, CLASS=MENUITEM MOREINFO="NONE"Network, or CLASS=MENUITEM MOREINFO="NONE"Host.CLASS=MENUITEM MOREINFO="NONE"Source---If you selected CLASS=MENUITEM MOREINFO="NONE"Interface or CLASS=MENUITEM MOREINFO="NONE"Host for the CLASS=MENUITEM MOREINFO="NONE"Source Type parameter, press MOREINFO="NONE"<Insert> to display and select from a list of interfaces. If you selected CLASS=MENUITEM MOREINFO="NONE"Network for the CLASS=MENUITEM MOREINFO="NONE"Source Type parameter, press MOREINFO="NONE"<Enter>, then type the TCP/IP address and the subnetwork mask.CLASS=MENUITEM MOREINFO="NONE"Advertised Hop Count---Enter a number from 1 to 16.This option is enabled if the filter is configured to permit or advertise the route. If you leave this option blank, the TCP/IP routing table is automatically consulted for the required information. CLASS=MENUITEM MOREINFO="NONE"Comment---Enter an optional short description.PERFORMANCE="REQUIRED"ID="FM74943"Press 
MOREINFO="NONE"<Esc> and save the filter information.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Exceptions to display a list of exceptions to the configured filters.Lists the routes to which the action---accept or ignore---does not apply.
PAGENUM=131 ID="BP138"PAGENUM=132PERFORMANCE="REQUIRED"Modify the exceptions list.Press 
MOREINFO="NONE"<Insert> to add a new filter; or select a filter from the list and press 
MOREINFO="NONE"<Enter> to modify the filter, or 
MOREINFO="NONE"<Delete> to remove it. Refer to 
IDREF="FM71822"Step 4 and
IDREF="FM74943"Step 5 if you are adding or modifying a filter.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to return to the 
CLASS=MENUITEM MOREINFO="NONE"TCP/IP menu.RENDERAS="SECT3"How to Configure IP Outgoing Routing Information FiltersIDXID="w1345"BOOK="_idx" COLLECTION="nw41" TIDREF="i1499"IDXID="w1346"BOOK="_idx" COLLECTION="nw41" TIDREF="i761"Filtering support must be enabled for IP in INETCFG for filtering to work.To configure IP outgoing RIP filters, load FILTCFG and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing RIP Filters (CLASS=MENUITEM MOREINFO="NONE"Outgoing RIP Filters menu appears)Complete the following steps:PERFORMANCE="REQUIRED"Select CLASS=MENUITEM MOREINFO="NONE"Status option and toggle the choice to read CLASS=MENUITEM MOREINFO="NONE"Enabled or CLASS=MENUITEM MOREINFO="NONE"Disabled to specify the status of the selected filters.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Action and
 toggle the choice to permit or deny the routes in the filter list. This specifies whether to forward (permit) or block (deny) all route advertisement packets defined in the filter list.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Filters to display a list of permitted or denied routes.PERFORMANCE="REQUIRED"ID="FM64247"Modify the route list.Press 
MOREINFO="NONE"<Insert> to add a new route filter; or select a filter from the list and press 
MOREINFO="NONE"<Enter> to modify the filter, or 
MOREINFO="NONE"<Delete> to remove it. If you are modifying or adding a new filter, modify the following parameters from the 
CLASS=MENUITEM MOREINFO="NONE"Define Filter menu:
MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Route CLASS=MENUITEM MOREINFO="NONE"to Network or Host---Specify the type of route to be filtered. Your choices are CLASS=MENUITEM MOREINFO="NONE"All Routes, CLASS=MENUITEM MOREINFO="NONE"Host, or CLASS=MENUITEM MOREINFO="NONE"Network.CLASS=MENUITEM MOREINFO="NONE"IP Address of Network/Host---Enter a 4-byte IP address in dotted decimal notation. You do not need to enter this if you selected CLASS=MENUITEM MOREINFO="NONE"All Routes for the CLASS=MENUITEM MOREINFO="NONE"Route to Network or Host parameter.PAGENUM=133 ID="BP139"CLASS=MENUITEM MOREINFO="NONE"Subnetwork Mask---Enter a 4-byte mask address in dotted decimal or hexadecimal notation. You need to do this only if you selected CLASS=MENUITEM MOREINFO="NONE"Network for the CLASS=MENUITEM MOREINFO="NONE"Route to Network or Host parameter.CLASS=MENUITEM MOREINFO="NONE"Destination Type---Select the destination type that the route will be advertised to. Your choices are CLASS=MENUITEM MOREINFO="NONE"Interface, CLASS=MENUITEM MOREINFO="NONE"Network, or CLASS=MENUITEM MOREINFO="NONE"Host.CLASS=MENUITEM MOREINFO="NONE"Destination---If you selected CLASS=MENUITEM MOREINFO="NONE"Interface or CLASS=MENUITEM MOREINFO="NONE"Host for the CLASS=MENUITEM MOREINFO="NONE"Destination Type, press MOREINFO="NONE"<Insert> to display and select from a list of interfaces. If you selected CLASS=MENUITEM MOREINFO="NONE"Network for the CLASS=MENUITEM MOREINFO="NONE"Destination Type, press MOREINFO="NONE"<Enter>, then type the TCP/IP address and the subnetwork mask.CLASS=MENUITEM MOREINFO="NONE"Advertised Hop Count---Enter a number from 1 to 16.This option is enabled if the filter is configured to permit or advertise the route. If you leave this option blank, the TCP/IP routing table is automatically consulted for the required information. CLASS=MENUITEM MOREINFO="NONE"Comment---Enter an optional short description.PERFORMANCE="REQUIRED"ID="FM80433"Press 
MOREINFO="NONE"<Esc> and save the filter information.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Exceptions to display a list of exceptions to the configured filters.Lists the routes to which the action---advertise or hide---does not apply.PERFORMANCE="REQUIRED"Modify the exceptions list.Press 
MOREINFO="NONE"<Insert> to add a new filter; or select a filter from the list and press 
MOREINFO="NONE"<Enter> to modify the filter, or 
MOREINFO="NONE"<Delete> to remove it. Refer to 
IDREF="FM64247"Step 4 and 
IDREF="FM80433"Step 5 if you are adding or modifying a filter.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to return to the 
CLASS=MENUITEM MOREINFO="NONE"TCP/IP menu.RENDERAS="SECT3"How to Configure Incoming EGP FiltersIDXID="w1347"BOOK="_idx" COLLECTION="nw41" TIDREF="i1499"IDXID="w1348"BOOK="_idx" COLLECTION="nw41" TIDREF="i761"IDXID="w1349"BOOK="_idx" COLLECTION="nw41" TIDREF="i1503"IDXID="w1350"BOOK="_idx" COLLECTION="nw41" TIDREF="i1296"No routes are accepted by EGP unless EGP filters are configured.To configure IP incoming EGP filters, load FILTCFG and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Incoming EGP Filters (CLASS=MENUITEM MOREINFO="NONE"Incoming EGP Filters menu appears)PAGENUM=134 ID="BP140"Complete the following steps:PERFORMANCE="REQUIRED"Select CLASS=MENUITEM MOREINFO="NONE"Status and toggle the choice to read CLASS=MENUITEM MOREINFO="NONE"Enabled or CLASS=MENUITEM MOREINFO="NONE"Disabled to specify the status of the selected filters.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Action and toggle the choice to permit or deny the routes in the filter list. This specifies whether to accept (permit) or ignore (deny) all packet information in the filter list.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Filters to display a list of permitted or denied routes.PERFORMANCE="REQUIRED"Modify the filter list.Press 
MOREINFO="NONE"<Insert> to add a new network filter; or select a filter from the list and press 
MOREINFO="NONE"<Enter> to modify the filter, or 
MOREINFO="NONE"<Delete> to remove it. If you are modifying or adding a new filter, perform the following substeps from the 
CLASS=MENUITEM MOREINFO="NONE"Define Filter menu:PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"ID="FM99960"Select 
CLASS=MENUITEM MOREINFO="NONE"Route to Network or Host, then press 
MOREINFO="NONE"<Enter> to specify the type of route to be filtered. Your choices are CLASS=MENUITEM MOREINFO="NONE"All Routes or CLASS=MENUITEM MOREINFO="NONE"Network.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"IP Address of Network/Host and enter an IP address in dotted decimal notation.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Subnetwork Mask and enter the subnetwork mask number.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Source Type to select the source from which the packets originate. Your choices are CLASS=MENUITEM MOREINFO="NONE"Autonomous System, CLASS=MENUITEM MOREINFO="NONE"Host, CLASS=MENUITEM MOREINFO="NONE"Interface, or CLASS=MENUITEM MOREINFO="NONE"Network.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Source and perform one of the following steps, based on what you selected in step 4d for the source type:
MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Interface---Press MOREINFO="NONE"<Insert>, then select a network interface from the list.CLASS=MENUITEM MOREINFO="NONE"Network---PressMOREINFO="NONE" <Enter>, then type the TCP/IP Address and Subnetwork Mask numbers in dotted decimal notation.PAGENUM=135 ID="BP141"CLASS=MENUITEM MOREINFO="NONE"Host---Press MOREINFO="NONE"<Enter>, then type the TCP/IP Address in dotted decimal notation.CLASS=MENUITEM MOREINFO="NONE"Autonomous System---Press MOREINFO="NONE"<Enter> and type the Autonomous System number (from 0 to 65535) from which the route is learned (source).PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Metric Value and enter a number to be associated with the route. This option is only enabled if the filter is configured to permit or advertise the route. If you leave this option blank, the TCP/IP routing table is automatically consulted for the required information. PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Comment and enter an optional short description.PERFORMANCE="REQUIRED"ID="FM60124"Press 
MOREINFO="NONE"<Esc> and save the filter information.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Exceptions to display a list of exceptions to the permitted or denied routes.Lists the routes to which the action---permit or deny---does not apply.PERFORMANCE="REQUIRED"Modify the exceptions list.Press 
MOREINFO="NONE"<Insert> to add a new filter; or select a filter from the list and press 
MOREINFO="NONE"<Enter> to modify the filter, or 
MOREINFO="NONE"<Delete> to remove it. Refer to 
IDREF="FM99960"Step 4a through 
IDREF="FM60124"Step 4h if you are adding or modifying a filter.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to return to the
CLASS=MENUITEM MOREINFO="NONE" TCP/IP menu.RENDERAS="SECT3"How to Configure Outgoing EGP FiltersIDXID="w1351"BOOK="_idx" COLLECTION="nw41" TIDREF="i1499"IDXID="w1352"BOOK="_idx" COLLECTION="nw41" TIDREF="i761"IDXID="w1353"BOOK="_idx" COLLECTION="nw41" TIDREF="i1503"IDXID="w1354"BOOK="_idx" COLLECTION="nw41" TIDREF="i1296"No routes are advertised to EGP unless EGP filters are configured.To configure IP outgoing EGP filters, load FILTCFG and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing EGP Filters (CLASS=MENUITEM MOREINFO="NONE"Outgoing EGP Filters menu appears)PAGENUM=135 ID="BP142"PAGENUM=136Complete the following steps:PERFORMANCE="REQUIRED"Select CLASS=MENUITEM MOREINFO="NONE"Status and toggle the choice to read CLASS=MENUITEM MOREINFO="NONE"Enabled or CLASS=MENUITEM MOREINFO="NONE"Disabled to reflect the status of the filter.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Action and toggle the choice to permit or deny the routes in the filter list. This specifies whether to advertise (permit) or block (deny) all packet information in the filter list.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Filters to display a list of permitted or denied routes.PERFORMANCE="REQUIRED"Modify the filter list.Press 
MOREINFO="NONE"<Insert> to add a new route; or select a filter from the list and press 
MOREINFO="NONE"<Enter> to modify the filter, or 
MOREINFO="NONE"<Delete> to remove it. If you are modifying or adding a new filter, perform the following steps from the 
CLASS=MENUITEM MOREINFO="NONE"Define Filter menu:PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"ID="FM94483"Select 
CLASS=MENUITEM MOREINFO="NONE"Route to Network or Host, then press 
MOREINFO="NONE"<Enter> to specify the type of route to be filtered. Your choices are CLASS=MENUITEM MOREINFO="NONE"All Routes or CLASS=MENUITEM MOREINFO="NONE"Network.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"IP Address of Network/Host and enter an IP address in dotted decimal notation.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Subnetwork Mask and enter the subnetwork mask number.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Destination Type and select the destination type. Your choices are CLASS=MENUITEM MOREINFO="NONE"Autonomous System, CLASS=MENUITEM MOREINFO="NONE"Host, CLASS=MENUITEM MOREINFO="NONE"Interface, or CLASS=MENUITEM MOREINFO="NONE"Network.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Destination and perform one of the following steps, based on what you selected in Step 4d for the destination type:
MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Interface---Press MOREINFO="NONE"<Insert>, then select a network interface from the list.CLASS=MENUITEM MOREINFO="NONE"Network---PressMOREINFO="NONE" <Enter>, then type the TCP/IP Address and Subnetwork Mask numbers in dotted decimal notation.PAGENUM=137 ID="BP143"CLASS=MENUITEM MOREINFO="NONE"Host---Press MOREINFO="NONE"<Enter>, then type the TCP/IP Address in dotted decimal notation.CLASS=MENUITEM MOREINFO="NONE"Autonomous System---Press MOREINFO="NONE"<Enter>, then type the Autonomous System number (from 0 to 65535) into which the route is advertised (destination).PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Metric Value and enter a number to be associated with the route. This option is enabled only if the filter is configured to permit or advertise the route. If you leave this option blank, the TCP/IP routing table is automatically consulted for the required information. PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Comment and enter an optional short description.PERFORMANCE="REQUIRED"ID="FM83082"Press 
MOREINFO="NONE"<Esc> and save the filter information.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Exceptions to display a list of exceptions to the permitted or denied routes.This lists the routes to which the action---advertise or hide---does not apply.PERFORMANCE="REQUIRED"Modify the exceptions list.Press 
MOREINFO="NONE"<Insert> to add a new filter; or select a filter from the list and press 
MOREINFO="NONE"<Enter> to modify the filter, or 
MOREINFO="NONE"<Delete> to remove it. Refer to 
IDREF="FM94483"Step 4a through 
IDREF="FM83082"Step 4h if you are adding or modifying a filter.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to return to the
CLASS=MENUITEM MOREINFO="NONE" TCP/IP menu.RENDERAS="SECT3"How to Configure OSPF External Route FiltersIDXID="w1355"BOOK="_idx" COLLECTION="nw41" TIDREF="i1499"IDXID="w1356"BOOK="_idx" COLLECTION="nw41" TIDREF="i761"IDXID="w1357"BOOK="_idx" COLLECTION="nw41" TIDREF="i1503"IDXID="w1358"BOOK="_idx" COLLECTION="nw41" TIDREF="i3128"OSPF outgoing route filters apply only to routes learned from RIP, EGP, or static routes.To configure OSPF external route filters, load FILTCFG and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"OSPF External Route Filters (CLASS=MENUITEM MOREINFO="NONE"OSPF External Route Filter menu appears)PAGENUM=137 ID="BP144"PAGENUM=138Complete the following steps:PERFORMANCE="REQUIRED"Select CLASS=MENUITEM MOREINFO="NONE"Status and toggle the choice to read CLASS=MENUITEM MOREINFO="NONE"Enabled or CLASS=MENUITEM MOREINFO="NONE"Disabled to specify the status of the filters.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Action and toggle the choice to permit or deny the routes in the filter list. Specifies whether to permit or deny the routes in the filter list.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Filters to display a list of permitted or denied routes.PERFORMANCE="REQUIRED"ID="FM92358"Modify the route list.Press 
MOREINFO="NONE"<Insert> to add a new route filter; or select a filter from the list and press 
MOREINFO="NONE"<Enter> to modify the filter, or 
MOREINFO="NONE"<Delete> to remove it. If you are modifying or adding a new filter, modify the following parameters from the 
CLASS=MENUITEM MOREINFO="NONE"Define Filter menu:
MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Route to Network or Host---Press MOREINFO="NONE"<Enter> to specify the type of route to be filtered. Your choices are CLASS=MENUITEM MOREINFO="NONE"All Routes, CLASS=MENUITEM MOREINFO="NONE"Host, orCLASS=MENUITEM MOREINFO="NONE" Network.CLASS=MENUITEM MOREINFO="NONE"IP Address---Enter a 4-byte IP address in dotted decimal notation if you specified CLASS=MENUITEM MOREINFO="NONE"Network or CLASS=MENUITEM MOREINFO="NONE"Host for the CLASS=MENUITEM MOREINFO="NONE"Route to Network or Host parameter.CLASS=MENUITEM MOREINFO="NONE"Subnetwork Mask---Enter a 4-byte mask address in dotted decimal or hexadecimal notation if you specified CLASS=MENUITEM MOREINFO="NONE"Network for the CLASS=MENUITEM MOREINFO="NONE"Route to Network or Host parameter.CLASS=MENUITEM MOREINFO="NONE"Metric Value---Enter a metric or cost associated with the route. This option is only available for outgoing filters, and is enabled if the filter is configured to permit or advertise the route. If you leave this option blank, the TCP/IP routing table is automatically consulted for the required information. CLASS=MENUITEM MOREINFO="NONE"Comment---Enter an optional short description.PERFORMANCE="REQUIRED"ID="FM51794"Press 
MOREINFO="NONE"<Esc> and save the filter information.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Exceptions to display a list of exceptions to the permitted or denied route filters.This lists the routes to which the action---permit or deny---does not apply.
PAGENUM=139 ID="BP145"PERFORMANCE="REQUIRED"Modify the exceptions list.Press 
MOREINFO="NONE"<Insert> to add a new filter; or select a filter from the list and press 
MOREINFO="NONE"<Enter> to modify the filter, or 
MOREINFO="NONE"<Delete> to remove it. Refer to 
IDREF="FM92358"Step 4 and 
IDREF="FM51794"Step 5 if you are adding or modifying a filter.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to return to the 
CLASS=MENUITEM MOREINFO="NONE"TCP/IP menu.RENDERAS="SECT3"IP Routing Information Filter ExampleIDXID="w1359"BOOK="_idx" COLLECTION="nw41" TIDREF="i1499"IDXID="w1360"BOOK="_idx" COLLECTION="nw41" TIDREF="i1506"In this example, the Accounting department is connected to the FDDI backbone by Router C. One of the networks within Accounting is 151.1.0.0 (subnetwork mask of 255.255.255.0). Access to this network from outside the Accounting department is not required. The administrator has selected to not propagate a route to this network outside the Accounting department. Network 151.1.0.0 can be hidden from the rest of the organization by configuring an outgoing RIP filter on Router C. Because IP supports RIP, OSPF, and EGP, routing filters must always specify the routing protocol for which the filter will apply. In this case, RIP is used by all routers in the organization, and a RIP routing information filter is configured. The route being hidden from the rest of the network is defined by the accounting network with IP network address 151.1.0.0. Router C's connection to the departments outside Accounting is through the FDDI backbone. The destination from which to hide network 151.1.0.0 is most easily defined as the FDDI interface to the backbone. IDREF="FM14386"Figure 5-7 shows an example topology.Note that Router C will have the route to network 151.1.0.0 in its routing table. If Router C receives a packet from the FDDI backbone that is destined for network 151.1.0.0, it will forward the packet.PAGENUM=140 ID="BP146"LABEL="5-7" FLOAT="0"ID="FM14386"IP Routing Information Filter ExampleFILEREF="ipktinfo.tif"When configuring this example, set the following parameters, as shown in IDREF="FM21806"Table 5-7.LABEL="5-7" PGWIDE=0 TOCENTRY="1"ID="FM21806"IP Routing Information Filter Example ParametersCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"NAMEST=1 NAMEEND=2 SPANNAME=SPAN1T2 ALIGN=LEFTVALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ParameterCOLNAME=2 ROTATE="0" MOREROWS="0"Example EntryVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"ActionCOLNAME=2 ROTATE="0" MOREROWS="0"Deny ServicesSPANNAME=SPAN1T2 ROTATE="0" MOREROWS="0"Filters:COLNAME=1 ROTATE="0" MOREROWS="0"Route to Network or HostIP AddressSubnetwork MaskDestination TypeDestinationCOLNAME=2 ROTATE="0" MOREROWS="0"Network151.1.0.0255.255.255.0InterfaceFDDI InterfacePAGENUM=140 ID="BP147"PAGENUM=141RENDERAS="SECT2"ID="FM70119"IP Packet Forwarding FiltersIDXID="w1361"BOOK="_idx" COLLECTION="nw41" TIDREF="i1503"IDXID="w1362"BOOK="_idx" COLLECTION="nw41" TIDREF="i1910"IP packet forwarding filters let the router filter packets selectively, based on their type, source, and destination. The source is specified as an IP address or the inbound interface. The destination is specified as an IP address or the outbound interface. The packet type is identified by the presence of expected values in the protocol type field of the IP header and in a protocol-specific operator. Packet forwarding filters recognize the following protocol types:MARK=BULLETICMPTCPUDPThe packet type may be further identified by the TCP/UDP port. You can filter only TCP packets that initiate a connection. This lets you restrict access to TCP services in a location while allowing clients in that location to access outside TCP services.RENDERAS="SECT2"Configuring IP Packet Forwarding FilteringIDXID="w1363"BOOK="_idx" COLLECTION="nw41" TIDREF="i1499"IDXID="w1364"BOOK="_idx" COLLECTION="nw41" TIDREF="i761"Filtering support must be enabled for IP in INETCFG for filtering to work.To configure IP packet forwarding filtering, load FILTCFG and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Packet CLASS=MENUITEM MOREINFO="NONE"Forwarding Filters (CLASS=MENUITEM MOREINFO="NONE"Packet Forwarding Filters menu appears)Complete the following steps:PERFORMANCE="REQUIRED"Select CLASS=MENUITEM MOREINFO="NONE"Status and toggle the choice to read CLASS=MENUITEM MOREINFO="NONE"Enabled or CLASS=MENUITEM MOREINFO="NONE"Disabled to specify the status of the selected filters.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Action and toggle the choice to permit or deny the packets in the filter list.Specifies whether to forward (permit) or block (deny) all packets defined in the filter list.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Filters to display a list of permitted or denied packets.
PAGENUM=142 ID="BP148"PERFORMANCE="REQUIRED"Modify the packet list.Press 
MOREINFO="NONE"<Insert> to add a new packet filter; or select a filter from the list and press 
MOREINFO="NONE"<Enter> to modify the filter, or 
MOREINFO="NONE"<Delete> to remove it. If you are modifying or adding a new filter, perform the following steps from the 
CLASS=MENUITEM MOREINFO="NONE"Define Filter menu:You cannot modify a predefined packet type.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"ID="FM70459"Select 
CLASS=MENUITEM MOREINFO="NONE"Source Type to select the source type. Your choices are CLASS=MENUITEM MOREINFO="NONE"Network, CLASS=MENUITEM MOREINFO="NONE"Host, or CLASS=MENUITEM MOREINFO="NONE"Interface.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Source and perform one of the following steps, based on what you selected in IDREF="FM70459"Step 4a:
MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Interface---Press MOREINFO="NONE"<Enter>, then select a network interface from the list.CLASS=MENUITEM MOREINFO="NONE"Network---Press MOREINFO="NONE"<Enter>, then type the TCP/IP Address and Subnetwork Mask numbers in dotted decimal notation.CLASS=MENUITEM MOREINFO="NONE"Host---Press MOREINFO="NONE"<Enter>, then type the TCP/IP Address in dotted decimal notation.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Packet Type, press 
MOREINFO="NONE"<Enter> and select a packet type from the list.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Destination Type to select the destination type. Your choices are CLASS=MENUITEM MOREINFO="NONE"Network, CLASS=MENUITEM MOREINFO="NONE"Host, or CLASS=MENUITEM MOREINFO="NONE"Interface.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Destination and perform one of the following steps, based on what you selected in Step 4d:
MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Interface---Press MOREINFO="NONE"<Enter>, then select a network interface from the list.CLASS=MENUITEM MOREINFO="NONE"Network---Press MOREINFO="NONE"<Enter>, then type the TCP/IP Address and Subnetwork Mask numbers in dotted decimal notation.CLASS=MENUITEM MOREINFO="NONE"Host---Press MOREINFO="NONE"<Enter>, then type the TCP/IP Address in dotted decimal notation.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Comment and enter an optional short description.PERFORMANCE="REQUIRED"ID="FM21326"Press 
MOREINFO="NONE"<Esc> and save the filter information.
PAGENUM=143 ID="BP149"PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Exceptions to display a list of exceptions to the permitted or denied packets.Lists the packets to which the action---forward or block---does not apply.PERFORMANCE="REQUIRED"Modify the exceptions list.Press 
MOREINFO="NONE"<Insert> to add a new filter; or select a filter from the list and press 
MOREINFO="NONE"<Enter> to modify the filter, or 
MOREINFO="NONE"<Delete> to remove it. Refer to 
IDREF="FM70459"Step 4a through 
IDREF="FM21326"Step 4g if you are adding or modifying a filter.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to return to the
CLASS=MENUITEM MOREINFO="NONE" TCP/IP menu.RENDERAS="SECT3"IP Packet Forwarding Filter ExampleIDXID="w1365"BOOK="_idx" COLLECTION="nw41" TIDREF="i1499"IDXID="w1366"BOOK="_idx" COLLECTION="nw41" TIDREF="i1506"In this example, an organization has an FDDI backbone connecting several departments within the organization and a link to external networks. Routers A and C connect the departmental networks to the backbone. Router B connects the external networks to the backbone. Within the organization, users can communicate freely across the internetwork. External access is limited to electronic mail. The internetwork topology is shown in IDREF="FM38536"Figure 5-8.PAGENUM=144 ID="BP150"LABEL="5-8" FLOAT="0"ID="FM38536"IP Packet Forwarding Filter ExampleFILEREF="ippktfwd.tif"Because internal communication is not restricted, packet forwarding filters are not required on Routers A or C. Two packet forwarding filters are required on Router B. The first filter ensures that any packet originating within the organization's internal networks will be forwarded by Router B. The second filter allows external users to send and receive electronic mail to and from internal users by providing access to the corporate mail server.To configure the first filter, the source identifies the packets that originate in the internal networks. The simplest way to do this on Router B is to identify all packets received from the FDDI backbone interface. Because internal users are allowed to use any service at any location, the remaining fields in the filter may be specified as "ANY."The source of the second filter is all packets originating from external networks. Because the interface NE2000_B is the only connection that B has to the external networks, this may be used to specify the source field for this filter. SMTP (Simple Mail Transfer Protocol) is selected from the predefined services list. The allowable destinations are limited to the corporate mail servers. Host 153.5.3.1 is the only mail server defined. PAGENUM=145 ID="BP151"When configuring this example, set the following parameters, as shown in IDREF="FM51835"Table 5-8.LABEL="5-8" PGWIDE=0 TOCENTRY="1"ID="FM51835"IP Packet Forwarding Filter Example ParametersCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"NAMEST=1 NAMEEND=2 SPANNAME=SPAN1T2 ALIGN=LEFTVALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ParameterCOLNAME=2 ROTATE="0" MOREROWS="0"Example EntryVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"ActionCOLNAME=2 ROTATE="0" MOREROWS="0"DenySPANNAME=SPAN1T2 ROTATE="0" MOREROWS="0"Filters ListCOLNAME=1 ROTATE="0" MOREROWS="0"Filter 1:Source TypeSourcePacket TypeDestination TypeDestinationFilter 2:Source TypeSourcePacket TypeDestination TypeDestinationCOLNAME=2 ROTATE="0" MOREROWS="0"InterfaceFDDI backboneAnyInterfaceAnyInterfaceNE2000_BSMTPHost153.5.3.1LABEL="6"PAGENUM=147 ID="BP152"ID="FM52280"Using Internetworking UtilitiesIDXID="w1367"BOOK="_idx" COLLECTION="nw41" TIDREF="i1875"
This chapter includes descriptions of the NetWare® 4.1 internetworking utilities, which consist of console commands and NetWare Loadable ModuleTM (NLMTM) files. It gives general information about these utilities and what you can do with them. Console commands and NLM files can be used at either the server console or through RCONSOLE, XCONSOLE, or ACONSOLE from a remote workstation.These utilities and consoles enable you to monitor and troubleshoot problems on your network, configure SNMP information, and configure remote access for your node.This chapter describes how to use the utilities and consoles to monitor and troubleshoot problems on your network. The utilities and consoles let you perform the following tasks:MARK=BULLETView statistical information for the protocol stackView runtime configuration information for the protocol stackView the network interface attachments for each protocol Verify connectivity to a particular deviceProvide access to remote hosts through SNMPProvide remote access to the current nodePAGENUM=147 ID="BP153"PAGENUM=148This chapter contains the following sections:MARK=BULLETIDREF="FM64930""Using Monitoring Utilities"This section describes the utilities you can use to monitor the behavior of specific protocols.IDREF="FM23907""Using Management Utilities"This section describes the utilities you can use to configure, manage, and optimize the server and its connections.IDREF="FM79722""Using Command-Line Utilities"This section describes the command line utilities available to complement the existing monitoring and management utilities.RENDERAS="SECT1"ID="FM64930"Using Monitoring UtilitiesIDXID="w1368"BOOK="_idx" COLLECTION="nw41" TIDREF="i2511"IDXID="w1369"BOOK="_idx" COLLECTION="nw41" TIDREF="i4736"
The NetWare 4.1 protocol software includes utilities to help you monitor the performance and behavior of a local or remote server and network protocols. This section discusses the following topics:MARK=BULLETIDREF="FM82138""Selecting a Server or Router to Monitor"IDREF="FM88790""Using the IPX Console"IDREF="FM84377""Using the AppleTalk Console"IDREF="FM32608""Using the TCP/IP Console"IDREF="FM40777""Using the NetWare MONITOR Utility"RENDERAS="SECT2"ID="FM82138"Selecting a Server or Router to MonitorIDXID="w1370"BOOK="_idx" COLLECTION="nw41" TIDREF="i2511"IDXID="w1371"BOOK="_idx" COLLECTION="nw41" TIDREF="i4222"
IPXCON and TCPCON give you management access to remote servers or dedicated routers on the network. IPXCON gives you access only to servers or routers that are running NetWare 4.1 IPXTM software. In this section, the term local system refers to the server or router from which you load the console utility; remote system refers to any other server or router on the network.PAGENUM=149 ID="BP154"RENDERAS="SECT3"Accessing the Local SystemIDXID="w1372"BOOK="_idx" COLLECTION="nw41" TIDREF="i2511"IDXID="w1373"BOOK="_idx" COLLECTION="nw41" TIDREF="i2169"
To gain IPX, TCP/IP, or AppleTalk management access to the local system, load IPXCON TCPCON or ATCON, respectively.The consoles access the local system by default.RENDERAS="SECT3"Accessing a Remote SystemIDXID="w1374"BOOK="_idx" COLLECTION="nw41" TIDREF="i2511"IDXID="w1375"BOOK="_idx" COLLECTION="nw41" TIDREF="i3766"
To gain management access to a remote server or router, go to a local server or router, load the appropriate console, and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"SNMP Access Configuration (CLASS=MENUITEM MOREINFO="NONE"SNMP Access Configuration window appears) > Select CLASS=MENUITEM MOREINFO="NONE"Transport Protocol (CLASS=MENUITEM MOREINFO="NONE"Transport Protocol window appears) > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP or CLASS=MENUITEM MOREINFO="NONE"IPX (SNMP Access Configuration window reappears) > Select CLASS=MENUITEM MOREINFO="NONE"Host Address > Press MOREINFO="NONE"<Ins> to see a list of available host names and addresses.Scroll through the list to find and select the system. In a few moments, the console begins recording statistics for the system you selected.RENDERAS="SECT2"ID="FM88790"Using the IPX ConsoleIDXID="w1376"BOOK="_idx" COLLECTION="nw41" TIDREF="i4736"IDXID="w1377"BOOK="_idx" COLLECTION="nw41" TIDREF="i1929"
The IPX Console (IPXCON) is a diagnostic console utility that provides access to statistics and information about the status of various components of the IPX protocol. IPXCON uses SNMP to access this information from any local or remote system on the network. IPXCON operates over both IPX and TCP/IP networks and uses UDP to run over either IPX or TCP/IP networks. This section describes the interface for IPXCON. You can use IPXCON to perform the following tasks:MARK=BULLETMonitor and troubleshoot IPX routers and network segments throughout your IPX internetwork.Display the status of any IPX router or network segment on your internetworkDisplay all paths through which IPX packets can flowLocate all active IPX routers on your internetworkPAGENUM=150 ID="BP155"Display operational circuits for IPXMonitor remote routers running NetWare IPX RouterTM softwareGenerally, the local NetWare IPX node is the target of IPXCON. However, you can access any other IPX router node that supports SNMP by changing the host address. This includes IPX protocol stacks provided by other vendors.To start IPXCON, enter the following command at the server prompt:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD IPXCONIf you want to start IPXCON automatically each time you start the server, add the MOREINFO="NONE"LOAD IPXCON command after the INITSYS.NCF line in your AUTOEXEC.NCF file. The system displays the IPXCON main menu screen shown in IDREF="FM37507"Figure 6-1.LABEL="6-1" FLOAT="0"ID="FM37507"IPXCON Main ScreenFILEREF="ipxconh.tif"PAGENUM=151 ID="BP156"The top of the screen displays the name of the router being monitored and a summary of routing statistics for the selected router. The center of the screen displays the CLASS=MENUITEM MOREINFO="NONE"Available Options menu that allows access to additional features of IPXCON.IDREF="FM38582"Table 6-1 explains the fields in the summary display at the top of the screen. Because IPXCON is a real-time monitor, these fields are always active and some of the values in the fields change as IPX packets are processed.LABEL="6-1" PGWIDE=1 TOCENTRY="1"ID="FM38582"IPXCON Routing Statistics Summary FieldsCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="9*"COLNAME=2 COLWIDTH="26*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Field COLNAME=2 ROTATE="0" MOREROWS="0"Explanation VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SNMP Transport Address COLNAME=2 ROTATE="0" MOREROWS="0"Name of the router being monitored or the transport address if no name can be determined.COLNAME=1 ROTATE="0" MOREROWS="0"Packets Received COLNAME=2 ROTATE="0" MOREROWS="0"Number of IPX packets received by the selected router. COLNAME=1 ROTATE="0" MOREROWS="0"Packets Sent COLNAME=2 ROTATE="0" MOREROWS="0"Number of IPX packets sent by the selected router. COLNAME=1 ROTATE="0" MOREROWS="0"Packets Forwarded COLNAME=2 ROTATE="0" MOREROWS="0"Number of IPX packets forwarded by the selected router. COLNAME=1 ROTATE="0" MOREROWS="0"Circuits COLNAME=2 ROTATE="0" MOREROWS="0"Number of circuits currently in use on the router.A circuit is a logical attachment to a network segment through which a router can reach other systems. A circuit can be a local or wide area connection. COLNAME=1 ROTATE="0" MOREROWS="0"Networks COLNAME=2 ROTATE="0" MOREROWS="0"Number of networks currently reachable from the selected router. COLNAME=1 ROTATE="0" MOREROWS="0"Services COLNAME=2 ROTATE="0" MOREROWS="0"Number of services currently reachable from the selected router. IDXID="w1378"BOOK="_idx" COLLECTION="nw41" TIDREF="i1929"PAGENUM=151 ID="BP157"PAGENUM=152The CLASS=MENUITEM MOREINFO="NONE"Available Options menu allows access to additional features of IPXCON. These features are described in IDREF="FM41612"Table 6-2. LABEL="6-2" PGWIDE=1 TOCENTRY="1"ID="FM41612"IPXCON Available Options MenuCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="9*"COLNAME=2 COLWIDTH="26*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Option COLNAME=2 ROTATE="0" MOREROWS="0"Explanation VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SNMP Access ConfigurationCOLNAME=2 ROTATE="0" MOREROWS="0"Lets you select the router you want to monitor. You can monitor the local system, which is the default, or a remote system. You can monitor the remote system via IPX or TCP/IP. You can also set the poll interval to specify how often the information will be retrieved through SNMP. COLNAME=1 ROTATE="0" MOREROWS="0"IPX Information COLNAME=2 ROTATE="0" MOREROWS="0"Displays statistics for the selected router's IPX packet routing. To display additional packet routing statistics, select CLASS=MENUITEM MOREINFO="NONE"Detailed IPX Information from the bottom of the IPX Information window.COLNAME=1 ROTATE="0" MOREROWS="0"IPX Router Information COLNAME=2 ROTATE="0" MOREROWS="0"Displays general information about the selected IPX router, including information about the operation of NLSP, RIP, and SAP.COLNAME=1 ROTATE="0" MOREROWS="0"NLSP Information COLNAME=2 ROTATE="0" MOREROWS="0"Displays the following NLSP (NetWare Link Services ProtocolTM) information about the selected router:MARK=BULLETSystem informationArea addressesNeighborsRoutersLANsCOLNAME=1 ROTATE="0" MOREROWS="0"CircuitsCOLNAME=2 ROTATE="0" MOREROWS="0"Displays circuit information.COLNAME=1 ROTATE="0" MOREROWS="0"ForwardingCOLNAME=2 ROTATE="0" MOREROWS="0"Displays all destinations networks known to this router.COLNAME=1 ROTATE="0" MOREROWS="0"ServicesCOLNAME=2 ROTATE="0" MOREROWS="0"Displays information for services available to this router.RENDERAS="SECT2"IDXID="w1379"BOOK="_idx" COLLECTION="nw41" TIDREF="i1929"PAGENUM=152 ID="BP158"PAGENUM=153ID="FM84377"Using the AppleTalk ConsoleIDXID="w1380"BOOK="_idx" COLLECTION="nw41" TIDREF="i4736"IDXID="w1381"BOOK="_idx" COLLECTION="nw41" TIDREF="i194"
The AppleTalk Console (ATCON) is a diagnostic console utility that provides access to statistics and information about the status of various components of the AppleTalk protocol. ATCON uses SNMP to access this information from the local system. This section describes the interface for ATCON. You can use ATCON to perform the following tasks:MARK=BULLETMonitor activity in the AppleTalk portions of your networkDiagnose operational problems in network segments that support AppleTalkVerify the configuration of the local AppleTalk routerVerify the connectivity of an AppleTalk router to the rest of the AppleTalk internetworkMonitor the status of AppleTalk Update-based Routing Protocol (AURP)To start ATCON, enter the following command at the server prompt:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD ATCONThe system displays the ATCON main menu screen shown in IDREF="FM96606"Figure 6-2.LABEL="6-2" FLOAT="0"ID="FM96606"ATCON Available Actions MenuFILEREF="atcon.tif"PAGENUM=154 ID="BP159"The CLASS=MENUITEM MOREINFO="NONE"Available Actions menu allows access to the features of ATCON. These features are described in IDREF="FM41379"Table 6-3. LABEL="6-3" PGWIDE=1 TOCENTRY="1"ID="FM41379"ATCON Available Actions MenuCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="9*"COLNAME=2 COLWIDTH="26*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Option COLNAME=2 ROTATE="0" MOREROWS="0"Explanation VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"AURP Information COLNAME=2 ROTATE="0" MOREROWS="0"Displays the current status of each one-way connection to each AURP peer router. This option is available only if AURP is enabled. COLNAME=1 ROTATE="0" MOREROWS="0"InterfacesCOLNAME=2 ROTATE="0" MOREROWS="0"Displays configuration status information about the interfaces directly connected to the AppleTalk router.COLNAME=1 ROTATE="0" MOREROWS="0"Log FilesCOLNAME=2 ROTATE="0" MOREROWS="0"Sets logging levels for AppleTalk messages. Also displays system log and Volume log files.COLNAME=1 ROTATE="0" MOREROWS="0"Lookup Network EntitiesCOLNAME=2 ROTATE="0" MOREROWS="0"Lets you query for services available on the AppleTalk network and send echo packets to services found.COLNAME=1 ROTATE="0" MOREROWS="0"Packet StatisticsCOLNAME=2 ROTATE="0" MOREROWS="0"Displays a variety of statistics maintained by the AppleTalk router.COLNAME=1 ROTATE="0" MOREROWS="0"Protocol ConfigurationCOLNAME=2 ROTATE="0" MOREROWS="0"Displays the current configuration of the AppleTalk protocol stack and router.COLNAME=1 ROTATE="0" MOREROWS="0"Routing TableCOLNAME=2 ROTATE="0" MOREROWS="0"Displays the AppleTalk Routing table. This table lists all the destinations that can be reached by the AppleTalk router.COLNAME=1 ROTATE="0" MOREROWS="0"Zones ListCOLNAME=2 ROTATE="0" MOREROWS="0"Displays the list of zones known to this AppleTalk router. This list of zones should look exactly the same as the one displayed on the Macintosh Chooser. RENDERAS="SECT2"IDXID="w1382"BOOK="_idx" COLLECTION="nw41" TIDREF="i194"ID="FM32608"Using the TCP/IP ConsoleIDXID="w1383"BOOK="_idx" COLLECTION="nw41" TIDREF="i4444"IDXID="w1384"BOOK="_idx" COLLECTION="nw41" TIDREF="i4736"IDXID="w1385"BOOK="_idx" COLLECTION="nw41" TIDREF="i4444"
The TCP/IP Console (TCPCON) is a diagnostic console utility that provides access to statistics and information about the status of various components of the TCP/IP protocol. TCPCON uses SNMP to access this information from any local or remote system on the network. This section describes the interface for TCPCON. You can use TCPCON to perform the following tasks:MARK=BULLETMonitor activity in the TCP/IP network segments of your internetworkDisplay configuration and statistics information about the following TCP/IP protocols---IP, ICMP, UDP, TCP, OSPF, and EGPPAGENUM=155 ID="BP160"Display the IP routes currently known to a TCP/IP nodeDisplay the network interfaces supported by a TCP/IP nodeAccess the trap log maintained by SNMPLOG (for local systems only)Use SNMP over TCP/IP or IPX to access TCP/IP information in any remote protocol stack supporting the TCP/IP Management Information Base (MIB)Generally, the local NetWare TCP/IP node is the target of TCPCON. However, you can access any other TCP/IP node that supports SNMP by changing the host address. This includes TCP/IP protocol stacks provided by other vendors.To start TCPCON, enter the following command at the system prompt:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD TCPCONThe system displays the TCPCON CLASS=MENUITEM MOREINFO="NONE"Available Options menu shown in IDREF="FM23200"Figure 6-3.PAGENUM=156 ID="BP161"LABEL="6-3" FLOAT="0"ID="FM23200"TCPCON Available Options MenuFILEREF="tcpconh.tif"The top of the screen displays the name of the router being monitored and a summary of statistics for the selected router. The center of the screen displays the CLASS=MENUITEM MOREINFO="NONE"Available Options menu that allows access to additional features of TCPCON.PAGENUM=156 ID="BP162"PAGENUM=157IDREF="FM15232"Table 6-4 explains the fields in the summary display at the top of the screen. LABEL="6-4" PGWIDE=1 TOCENTRY="1"ID="FM15232"TCPCON Summary Display Fields COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="9*"COLNAME=2 COLWIDTH="26*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Field COLNAME=2 ROTATE="0" MOREROWS="0"Explanation VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"HostCOLNAME=2 ROTATE="0" MOREROWS="0"Symbolic hostname or IP address of the selected TCP/IP host (or server name if accessing a remote node using IPX) being queried. This is the host specified in the SNMP Access Configuration option in the CLASS=MENUITEM MOREINFO="NONE"Available Options menu. COLNAME=1 ROTATE="0" MOREROWS="0"Uptime COLNAME=2 ROTATE="0" MOREROWS="0"Amount of time that has elapsed since the selected host was last initialized. COLNAME=1 ROTATE="0" MOREROWS="0"System COLNAME=2 ROTATE="0" MOREROWS="0"Brief description of the selected host. COLNAME=1 ROTATE="0" MOREROWS="0"IP Received COLNAME=2 ROTATE="0" MOREROWS="0"Number of input IP datagrams received from all interfaces, including those received in error. COLNAME=1 ROTATE="0" MOREROWS="0"IP Sent COLNAME=2 ROTATE="0" MOREROWS="0"Number of datagrams sent to IP for transmission. This number does not include datagrams forwarded by this host. COLNAME=1 ROTATE="0" MOREROWS="0"IP Forwarded COLNAME=2 ROTATE="0" MOREROWS="0"Number of IP packets forwarded from one node to another. This field displays the value Disabled if this host is not configured to be an IP gateway. COLNAME=1 ROTATE="0" MOREROWS="0"TCP Received COLNAME=2 ROTATE="0" MOREROWS="0"Number of TCP segments received, including those received in error. COLNAME=1 ROTATE="0" MOREROWS="0"TCP Sent COLNAME=2 ROTATE="0" MOREROWS="0"Number of TCP segments sent, excluding those containing retransmitted data. COLNAME=1 ROTATE="0" MOREROWS="0"TCP Connections COLNAME=2 ROTATE="0" MOREROWS="0"Number of currently established TCP connections. IDXID="w1386"BOOK="_idx" COLLECTION="nw41" TIDREF="i4444"PAGENUM=157 ID="BP163"PAGENUM=158The CLASS=MENUITEM MOREINFO="NONE"Available Options menu allows access to additional features of TCPCON. These features are described in IDREF="FM42870"Table 6-5. LABEL="6-5" PGWIDE=1 TOCENTRY="1"ID="FM42870"TCPCON Available Options MenuCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="9*"COLNAME=2 COLWIDTH="26*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Option COLNAME=2 ROTATE="0" MOREROWS="0"Explanation VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SNMP Access Configuration COLNAME=2 ROTATE="0" MOREROWS="0"Lets you select the TCP/IP host you want to monitor. You can monitor the local system, which is the default, or a remote system. You can monitor the remote system using IPX or TCP/IP protocols. You can also set the poll interval. COLNAME=1 ROTATE="0" MOREROWS="0"Protocol Information COLNAME=2 ROTATE="0" MOREROWS="0"Displays protocol information for the selected host. COLNAME=1 ROTATE="0" MOREROWS="0"IP Routing Table COLNAME=2 ROTATE="0" MOREROWS="0"Displays the IP routes currently known to the selected host. COLNAME=1 ROTATE="0" MOREROWS="0"Statistics COLNAME=2 ROTATE="0" MOREROWS="0"Displays TCP/IP statistics. These statistics provide detailed information about the operation of the major protocols within the TCP/IP protocol stack. COLNAME=1 ROTATE="0" MOREROWS="0"Interfaces COLNAME=2 ROTATE="0" MOREROWS="0"Displays all network interfaces supported by the selected host. COLNAME=1 ROTATE="0" MOREROWS="0"Display Traps COLNAME=2 ROTATE="0" MOREROWS="0"Displays the local SNMP trap log created by SNMPLOG.NLM. RENDERAS="SECT2"IDXID="w1387"BOOK="_idx" COLLECTION="nw41" TIDREF="i4444"ID="FM40777"ID="FM24245"Using the NetWare MONITOR UtilityIDXID="w1388"BOOK="_idx" COLLECTION="nw41" TIDREF="i2509"IDXID="w1389"BOOK="_idx" COLLECTION="nw41" TIDREF="i4736"
The NetWare MONITOR utility is a diagnostic console utility that provides access to statistics and information about the status of various components of the router. It enables you to monitor interface statistics, data link states, and serial interface signals. You can use this collection of dynamic data to help determine what is happening on LAN connection.You can use MONITOR with the local system only, whereas the other consoles can be used to query a remote system. However, MONITOR gives you access to a larger set of dynamic data than the other consoles do. To use MONITOR, type MOREINFO="NONE"LOAD MONITOR MOREINFO="NONE"<Enter>, then select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"LAN/WAN Information (CLASS=MENUITEM MOREINFO="NONE"LAN/WAN Driver Information appears) > Select the interface for which you want to check statisticsPAGENUM=159 ID="BP164"RENDERAS="SECT1"ID="FM23907"Using Management UtilitiesIDXID="w1390"BOOK="_idx" COLLECTION="nw41" TIDREF="i2313"IDXID="w1391"BOOK="_idx" COLLECTION="nw41" TIDREF="i4736"
The utilities you use to manage the NetWare 4.1 protocols work in conjunction with the monitoring utilities to configure, monitor, and optimize the server and the server's connections. Unlike most of the monitoring utilities, you can use these utilities to configure and test the server and its connections. This section discusses the following topics:MARK=BULLETIDREF="FM60738""Using the Internetworking Configuration Utility"IDREF="FM76526""Using the Filter Configuration Utility"IDREF="FM44838""Using the IPXPING Utility"IDREF="FM90829""Using the PING Utility"RENDERAS="SECT2"ID="FM60738"Using the Internetworking Configuration UtilityIDXID="w1392"BOOK="_idx" COLLECTION="nw41" TIDREF="i1874"IDXID="w1393"BOOK="_idx" COLLECTION="nw41" TIDREF="i4736"IDXID="w1394"BOOK="_idx" COLLECTION="nw41" TIDREF="i1874"
The Internetworking Configuration utility (INETCFG) enables you to configure your NetWare 4.1 internetworking. You can set up and customize your internetworking configuration for IPX, IP, and AppleTalk by performing the following tasks:MARK=BULLETSelect and configure a boardSelect and configure a network interfaceSelect and configure a network protocolBind a network protocol to an interfaceManage the configurationView the configurationINETCFG simplifies the process of configuring servers to work with the network and protocols supported by NetWare.PAGENUM=159 ID="BP165"PAGENUM=160INETCFG records information in various configuration (*.CFG) files located in SYS:\ETC. Some of these files are present at system startup; others are created by INETCFG, depending on what you configure. Here is a partial list of these files:MARK=BULLETAURP.CFGTCPIP.CFGIPXSPX.CFGNLSP.CFGNETINFO.CFGINETCFG creates these files strictly for its own use; do not delete them or change their contents.To start INETCFG, type the following command at the server prompt:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INETCFG MOREINFO="NONE"<Enter>The system displays the INETCFG main menu screen shown in IDREF="FM28388"Figure 6-4. LABEL="6-4" FLOAT="0"ID="FM28388"INETCFG Internetworking Configuration MenuFILEREF="inetcfg.tif"PAGENUM=161 ID="BP166"The CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu allows access to the features of INETCFG. These features are described in IDREF="FM31631"Table 6-6. LABEL="6-6" PGWIDE=1 TOCENTRY="1"ID="FM31631"INETCFG Internetworking Configuration Menu OptionsCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="9*"COLNAME=2 COLWIDTH="26*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Option COLNAME=2 ROTATE="0" MOREROWS="0"Explanation VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"BoardsCOLNAME=2 ROTATE="0" MOREROWS="0"Lets you select and configure boards. To configure a board, choose a driver, assign a name to the board, and specify values to the board parameters.Each driver that is compatible with NetWare has a driver description file that defines the parameters necessary for the driver to operate with the board you select. This file---sometimes called the LDI file---also specifies the valid range of values for each parameter. If a driver has an LDI file, the parameters are presented in the CLASS=MENUITEM MOREINFO="NONE"Board Configuration window; you simply choose a value for each parameter. If a driver has no LDI file, you must enter the values yourself in the CLASS=MENUITEM MOREINFO="NONE"Board Parameters field.COLNAME=1 ROTATE="0" MOREROWS="0"Network InterfacesCOLNAME=2 ROTATE="0" MOREROWS="0"Lets you configure WAN network interfaces for multiple interface WAN boards. This option does not apply to NetWare 4.1.COLNAME=1 ROTATE="0" MOREROWS="0"WAN Call DirectoryCOLNAME=2 ROTATE="0" MOREROWS="0"Lets you configure WAN call destinations. This option does not apply to NetWare 4.1.COLNAME=1 ROTATE="0" MOREROWS="0"ProtocolsCOLNAME=2 ROTATE="0" MOREROWS="0"Lets you select and configure network protocols. To configure a protocol, select the protocol, such as IPX or IP, and configure the protocol-specific parameters that pertain to routing, packet forwarding, and so on.COLNAME=1 ROTATE="0" MOREROWS="0"BindingsCOLNAME=2 ROTATE="0" MOREROWS="0"Lets you bind a network protocol to an interface; configure protocol and interface-specific parameters, such as frame type, network number (for IPX), local IP address (for IP), and zone information (for AppleTalk); and delete a bound interface from the configuration.COLNAME=1 ROTATE="0" MOREROWS="0"Manage ConfigurationCOLNAME=2 ROTATE="0" MOREROWS="0"Lets you specify SNMP information, such as the SNMP device name, hardware description, physical location, and human contact for the server or router.COLNAME=1 ROTATE="0" MOREROWS="0"View ConfigurationCOLNAME=2 ROTATE="0" MOREROWS="0"Lets you display the INETCFG configuration information file and the console messages captured during system initialization, and import or export configuration information to or from a diskette. It also lets you modify the AUTOEXEC.NCF file.RENDERAS="SECT2"IDXID="w1395"BOOK="_idx" COLLECTION="nw41" TIDREF="i1874"PAGENUM=162 ID="BP167"ID="FM76526"Using the Filter Configuration UtilityIDXID="w1396"BOOK="_idx" COLLECTION="nw41" TIDREF="i1496"IDXID="w1397"BOOK="_idx" COLLECTION="nw41" TIDREF="i4736"
The Filter Configuration utility (FILTCFG) enables you to set up and configure filters for the IPX, TCP/IP, and AppleTalk protocols. This section describes the interface for FILTCFG. Filters provide a way to control the kind of information that is sent and received by a router by selectively discarding packets of specified types. Filters are useful when you want to limit specific kinds of traffic to a certain part of your network topology, or when you want to provide a level of security.To start FILTCFG, type the following command at the server prompt: FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD FILTCFG MOREINFO="NONE"<Enter>The system displays the FILTCFG main menu screen shown in IDREF="FM29548"Figure 6-5.LABEL="6-5" FLOAT="0"ID="FM29548"FILTCFG Main MenuFILEREF="filtcfg.tif"NetWare 4.1 software provides the following filter types for network layer protocols, categorized according to the type of information being filtered:MARK=BULLETIDXID="w1398"BOOK="_idx" COLLECTION="nw41" TIDREF="i1503"IDXID="w1399"BOOK="_idx" COLLECTION="nw41" TIDREF="i3177"Packet Forwarding Filters---To restrict access to services by filtering data packets sent by the restricted location to the service location. Because these filters do not restrict service advertisement packets (SAPs) sent by servers, restricted users might see advertisements of services even when they cannot access the service.Packet forwarding filters are available for IPX and TCP/IP routers.Although these filters provide the highest level of security of all the filters, they might affect the performance of the router because the filters are applied to each data packet the router receives.PAGENUM=163 ID="BP168"IDXID="w1400"BOOK="_idx" COLLECTION="nw41" TIDREF="i1503"IDXID="w1401"BOOK="_idx" COLLECTION="nw41" TIDREF="i4076"Service Information Filters---To restrict service advertisement on a router's internetwork. This type of filtering provides low-level security by preventing users from finding the network addresses of servers advertising those services. It also reduces the network bandwidth consumed by periodic service broadcasts.Service information filters are available for IPX and AppleTalk routers.IDXID="w1402"BOOK="_idx" COLLECTION="nw41" TIDREF="i1503"IDXID="w1403"BOOK="_idx" COLLECTION="nw41" TIDREF="i3901"Routing Information Filters---To restrict the exchange of routing information between routers by limiting the routes added to the routing tables of specified routers. These filters increase network security by limiting the visibility of specified networks and reduce the bandwidth used by the periodic exchange of routing information between routers.Routing information filters are available for IPX, IP, and AppleTalk routers. When you add a routing information filter, an implicit service filter is also added for all services residing on the filtered networks.IDREF="FM17597"Table 6-7 shows which types of filtering are supported for which protocol suite. For more information, refer to IDREF="FM54089"Chapter 5, "Configuring Filters." LABEL="6-7" PGWIDE=0 TOCENTRY="1"ID="FM17597"Filter Types Provided by Protocol SuiteCOLS=4 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="7*"COLNAME=2 COLWIDTH="10*"COLNAME=3 COLWIDTH="9*"COLNAME=4 COLWIDTH="8*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ProtocolCOLNAME=2 ROTATE="0" MOREROWS="0"Packet Forwarding FiltersCOLNAME=3 ROTATE="0" MOREROWS="0"Service Information FiltersCOLNAME=4 ROTATE="0" MOREROWS="0"Routing Information FiltersVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IPXCOLNAME=2 ALIGN="CENTER" ROTATE="0" MOREROWS="0"XCOLNAME=3 ALIGN="CENTER" ROTATE="0" MOREROWS="0"XCOLNAME=4 ALIGN="CENTER" ROTATE="0" MOREROWS="0"XCOLNAME=1 ROTATE="0" MOREROWS="0"AppleTalkCOLNAME=2 ALIGN="CENTER" ROTATE="0" MOREROWS="0"COLNAME=3 ALIGN="CENTER" ROTATE="0" MOREROWS="0"XCOLNAME=4 ALIGN="CENTER" ROTATE="0" MOREROWS="0"XCOLNAME=1 ROTATE="0" MOREROWS="0"TCP/IPCOLNAME=2 ALIGN="CENTER" ROTATE="0" MOREROWS="0"XCOLNAME=3 ALIGN="CENTER" ROTATE="0" MOREROWS="0"COLNAME=4 ALIGN="CENTER" ROTATE="0" MOREROWS="0"XRENDERAS="SECT2"IDXID="w1404"BOOK="_idx" COLLECTION="nw41" TIDREF="i1503"PAGENUM=163 ID="BP169"PAGENUM=164ID="FM44838"ID="FM99313"Using the IPXPING UtilityIDXID="w1405"BOOK="_idx" COLLECTION="nw41" TIDREF="i1969"IDXID="w1406"BOOK="_idx" COLLECTION="nw41" TIDREF="i4736"
The IPXPING utility enables you to check connectivity to an IPX server on your internetwork.IPXPING determines the reachability of the IPX server or workstation---the "target" node---to which it sends the request packet. After the node receives the packet, it sends an IPXPING reply packet to the system that sent the request packet.This section describes the interface for IPXPING. IPXPING determines the reachability of an IPX "target" node on your internetwork, to which it sends a request packet. If the target node receives the request packet, it sends back a reply packet.To use IPXPING, type the following command at the server prompt:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD IPXPING MOREINFO="NONE"<Enter>The system displays the CLASS=MENUITEM MOREINFO="NONE"New Target window shown in IDREF="FM14821"Figure 6-6.LABEL="6-6" FLOAT="0"ID="FM14821"IPXPING New Target WindowFILEREF="ipxping.tif"To select a target IPX server, enter its IPX address in the CLASS=MENUITEM MOREINFO="NONE"Network field and the node number in the CLASS=MENUITEM MOREINFO="NONE"Node field. You can also specify the number of seconds between each packet transmission and the size of the packet, in bytes.To start sending request packets, press MOREINFO="NONE"<Esc>. The sending node continues to send request packets and collect response time statistics until you press MOREINFO="NONE"<Esc> again and exit IPXPING.Request and reply packets use the same format; each packet contains the standard IPX header.To select additional IPX servers, press MOREINFO="NONE"<Ins>. Enter the IPX address of the server in the CLASS=MENUITEM MOREINFO="NONE"Address field. Press MOREINFO="NONE"<Esc> to start sending packets.PAGENUM=165 ID="BP170"RENDERAS="SECT2"ID="FM90829"Using the PING UtilityIDXID="w1407"BOOK="_idx" COLLECTION="nw41" TIDREF="i3312"IDXID="w1408"BOOK="_idx" COLLECTION="nw41" TIDREF="i4736"
The PING utility enables you to send an ICMP echo request packet to an IP node on your internetwork.This section describes the interface for PING. PING determines the reachability of an IP "target" node on your internetwork, to which it sends a request packet. If the target node receives the request packet, it sends back a reply packet.To start PING, type the following command at the server prompt:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD PING MOREINFO="NONE"<Enter>The system displays the CLASS=MENUITEM MOREINFO="NONE"New Target window shown in IDREF="FM49103"Figure 6-7.LABEL="6-7" FLOAT="0"ID="FM49103"PING New Target WindowFILEREF="ping.tif"To select an IP node, enter its hostname or Internet address in the CLASS=MENUITEM MOREINFO="NONE"Host Name field. You can also specify the number of seconds between each packet transmission and the size of the packet, in bytes.To start sending packets, press MOREINFO="NONE"<Esc>. The sending node continues to send request packets and collect response time statistics until you press MOREINFO="NONE"<Esc> again and exit PING.To select additional IP nodes, press MOREINFO="NONE"<Ins>. Enter the IP address of the node in the CLASS=MENUITEM MOREINFO="NONE"Host Name field. Press MOREINFO="NONE"<Esc> to start sending packets.PAGENUM=165 ID="BP171"PAGENUM=166RENDERAS="SECT1"ID="FM79722"Using Command-Line UtilitiesIDXID="w1409"BOOK="_idx" COLLECTION="nw41" TIDREF="i690"IDXID="w1410"BOOK="_idx" COLLECTION="nw41" TIDREF="i4736"
The NetWare 4.1 software also includes the commands described in this section to complement the monitoring and management utilities. This section describes the following topics:MARK=BULLETIDREF="FM50357""Using the CONLOG Utility"IDREF="FM88998""Using the TPING Utility"IDREF="FM68723""Using the INITIALIZE SYSTEM Command"IDREF="FM98340""Using the REINITIALIZE SYSTEM Command"RENDERAS="SECT2"ID="FM50357"Using the CONLOG UtilityIDXID="w1411"BOOK="_idx" COLLECTION="nw41" TIDREF="i777"IDXID="w1412"BOOK="_idx" COLLECTION="nw41" TIDREF="i4736"
The CONLOG utility enables you to capture all console messages generated at the server while CONLOG is loaded, and write the messages to the default file SYS:/ETC/CONSOLE.LOG or to another file of your choice.To use CONLOG, type the following command at the server prompt and press MOREINFO="NONE"<Enter>:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD CONLOG [FILE=log filename]
   [SAVE=backup filename]
   [MAXIMUM=max file size]
   [ENTIRE=YES] | HELPWhere,MOREINFO="NONE"FILE=log filename is the name of the file you want to use as the log file. CONLOG writes console messages to this file instead of CONSOLE.LOG. The log filename parameter must be used with SFT IIITM servers, whose three engines must each write to a different log file.MOREINFO="NONE"SAVE=backup filename is the name of the file in which you want to save the preexisting console log. This enables the AUTOEXEC.NCF file to load CONLOG without overwriting the previous console log. Use this parameter if you want to examine the old console log for troubleshooting purposes.PAGENUM=167 ID="BP172"MOREINFO="NONE"MAXIMUM=max file size is the maximum size, in kilobytes, of the log file. If the log file exceeds max file size, it is deleted---or renamed if backup filename was specified. In either case, logging starts over with an empty log file.MOREINFO="NONE"ENTIRE=YES captures the lines already on the screen at the time CONLOG is loaded. Without this parameter, CONLOG starts logging with the next output to the console after it is loaded.MOREINFO="NONE"HELP displays a description of each CONLOG command parameter.The command LOAD CONLOG is typically added to the AUTOEXEC.NCF file, as shown in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"FILE SERVER NAME NETW41_SVR
IPX INTERNAL NET C92556E
LOAD CONLOG
LOAD REMOTE
LOAD RSPXYou can view the console log from INETCFG or with any text editor. Console messages can reveal errors that occur during system initialization.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="12*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ToCOLNAME=2 ROTATE="0" MOREROWS="0"TypeVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Start capturing console messages during system initializationCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"LOAD CONLOGCOLNAME=1 ROTATE="0" MOREROWS="0"Load CONLOG, but save the current log file as CLOG.BAK and limit the size of CONSOLE.LOG to 100 KBCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"LOAD CONLOG SAVE=CLOG.BAK MAXIMUM=100COLNAME=1 ROTATE="0" MOREROWS="0"Stop capturing console messagesCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"UNLOAD CONLOGPAGENUM=167 ID="BP173"PAGENUM=168RENDERAS="SECT2"ID="FM88998"Using the TPING UtilityIDXID="w1413"BOOK="_idx" COLLECTION="nw41" TIDREF="i4534"IDXID="w1414"BOOK="_idx" COLLECTION="nw41" TIDREF="i4736"
The TPING utility enables you to send an ICMP echo request packet to an IP node on your internetwork.TPING determines the reachability of an IP "target" node on your internetwork, to which it sends a request packet. If the target node receives the request packet, it sends back a reply packet.To use TPING, type the following command at the server prompt and press MOREINFO="NONE"<Enter>:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD TPING host [packet size [retry count]]Where, Host is the symbolic host name or IP address of a TCP/IP system on the network.Packet size is the size, in bytes, of the ICMP packet.Retry count is the number of times you want to send an ICMP packet to the host system until a reply is received.TPING sends a maximum of five ICMP echo request packets to the target node by default. If it receives a response, TPING stops sending requests and displays a message indicating that the target node is reachable. If it does not receive a response, TPING displays a message indicating that the target node did not respond.RENDERAS="SECT2"ID="FM68723"Using the INITIALIZE SYSTEM CommandIDXID="w1415"BOOK="_idx" COLLECTION="nw41" TIDREF="i1809"IDXID="w1416"BOOK="_idx" COLLECTION="nw41" TIDREF="i688"
The MOREINFO="NONE"INITIALIZE SYSTEM command lets you enable the NetWare 4.1 internetworking configuration by executing all commands in the system NETINFO.CFG file.To use MOREINFO="NONE"INITIALIZE SYSTEM, type the following command at the server prompt:FORMAT="LINESPECIFIC"MOREINFO="NONE"INITIALIZE SYSTEM MOREINFO="NONE"<Enter>
PAGENUM=168 ID="BP174"PAGENUM=169This command is typically executed from the INITSYS.NCF file during server startup.Executing MOREINFO="NONE"INITIALIZE SYSTEM on a system that has already been initialized can generate errors as the system discovers that the commands in the NETINFO.CFG file have already been executed.RENDERAS="SECT2"ID="FM98340"Using the REINITIALIZE SYSTEM CommandIDXID="w1417"BOOK="_idx" COLLECTION="nw41" TIDREF="i3728"IDXID="w1418"BOOK="_idx" COLLECTION="nw41" TIDREF="i688"
The MOREINFO="NONE"REINITIALIZE SYSTEM command lets you enable configuration changes made since the commands in the NETINFO.CFG file were executed.To use MOREINFO="NONE"REINITIALIZE SYSTEM, type the following command at the server prompt:FORMAT="LINESPECIFIC"MOREINFO="NONE"REINITIALIZE SYSTEM MOREINFO="NONE"<Enter>MOREINFO="NONE"REINITIALIZE SYSTEM compares the current NETINFO.CFG file with the previous one, which became effective with the execution of the MOREINFO="NONE"INITIALIZE SYSTEM command. If MOREINFO="NONE"REINITIALIZE SYSTEM finds any new or changed commands in the current NETINFO.CFG file, it executes them.MOREINFO="NONE"REINITIALIZE SYSTEM also informs any SNMP-registered NLM file that it is executing. This is a "call-back" mechanism that enables NLM files that store configuration information outside the NETINFO.CFG file to know that changes to the configuration have taken place.Not all NLM files register with SNMP for notification of MOREINFO="NONE"REINITIALIZE SYSTEM. If the configuration changes of an NLM involve more than loading, unloading, binding, or unbinding protocol stacks, unload the NLM, then type MOREINFO="NONE"REINITIALIZE SYSTEM.LABEL="7"PAGENUM=171 ID="BP175"ID="FM59500"Monitoring LAN ConnectionsIDXID="w1419"BOOK="_idx" COLLECTION="nw41" TIDREF="i2511"IDXID="w1420"BOOK="_idx" COLLECTION="nw41" TIDREF="i795"
This chapter describes how to monitor LAN connections using the available NetWare 4.1 management consoles and utilities. This chapter contains the following sections:MARK=BULLETIDREF="FM49610""Verifying the Configuration"This section describes how to verify specific aspects of your router configuration, including hardware, binding, and protocol configuration.IDREF="FM89369""Monitoring Performance"This section describes performance monitoring techniques to help you identify potential problems or areas for optimization.IDREF="FM15389""Checking the Connection Between Servers"This section describes a variety of ways to check connectivity and the link's behavior for your router, including how to monitor and manage communications equipment.IDREF="FM53135""Monitoring IPX Information"This section describes how to monitor IPXTM information to help give you a clear view of what your IPX network is doing, and to help identify potential problems in the router.IDREF="FM12512""Monitoring TCP/IP Information"This section describes how to monitor TCP/IP information to help give you a clear view of what your TCP/IP network is doing, and to help identify potential problems in the router.IDREF="FM53474""Monitoring AppleTalk Information"This section describes how to monitor AppleTalk information to help give you a clear view of what your AppleTalk network is doing, and to help identify potential problems in the router.PAGENUM=172 ID="BP176"RENDERAS="SECT1"ID="FM49610"Verifying the ConfigurationIDXID="w1421"BOOK="_idx" COLLECTION="nw41" TIDREF="i3886"
Once you configure the NetWare 4.1 software, you should verify if everything is configured in the way you intended. You use the monitoring and management tools available to view if everything is working correctly according to your configuration. This section discusses the following topics:MARK=BULLETIDREF="FM88440""Viewing Binding Configuration for a LAN Interface"IDREF="FM23467""Viewing NetWare IPX Configuration Information"IDREF="FM97535""Viewing AppleTalk Configuration Information"IDREF="FM62219""Viewing TCP/IP Configuration Information"RENDERAS="SECT2"ID="FM42787"Viewing the Hardware Configuration of a LAN InterfaceTo find out the hardware configuration information for a LAN interface, load MONITOR and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"LAN/WAN Information > Look at the interface for which you want to see informationYou can see the following information:MARK=BULLETInterface NameNode AddressPortInterruptFrame TypeIf more than one framing type is used on an interface, MONITOR shows a separate entry for each framing type used on the same interface. You should view each entry for that interface to find out all the frame types. PAGENUM=173 ID="BP177"RENDERAS="SECT2"ID="FM88440"Viewing Binding Configuration for a LAN InterfaceYou can find out which network protocols are bound to an interface, and which of them are currently operational, load MONITOR and select the following path: Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"LAN/WAN Information > Select the interface for which you want to see informationLook at CLASS=MENUITEM MOREINFO="NONE"Protocols to see the network protocols that are bound to that interface.If more than one framing type is used on an interface, MONITOR shows a separate entry for each framing type used on the same interface. You should view each entry for that interface to find all the protocols bound to the interface. RENDERAS="SECT2"ID="FM23467"ID="FM90893"Viewing NetWare IPX Configuration InformationTo find out how IPX is configured, load IPXCON, and select the following options:MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"IPX Router Information---To view whether RIP, SAP, and NLSPTM protocols are configured for this router.CLASS=MENUITEM MOREINFO="NONE"NLSP Information---To view NLSP configuration for the system and the NLSP network.CLASS=MENUITEM MOREINFO="NONE"Circuits---To view the IPX circuits configured for the router.RENDERAS="SECT2"ID="FM97535"Viewing AppleTalk Configuration InformationTo find out how AppleTalk is configured, load ATCON and select the following options:MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Protocol Configuration---To view the current configuration for AppleTalk.CLASS=MENUITEM MOREINFO="NONE"Zones List---To view the list of zones to which the router belongs.CLASS=MENUITEM MOREINFO="NONE"Interfaces---To view the interfaces in the router to which AppleTalk is bound.PAGENUM=174 ID="BP178"RENDERAS="SECT2"ID="FM62219"Viewing TCP/IP Configuration InformationTo find out how TCP/IP is configured, load TCPCON, and select CLASS=MENUITEM MOREINFO="NONE"Protocol Information. You can then select to view configuration information and statistics for EGP, ICMP, IP, OSPF, TCP, and UDP.RENDERAS="SECT1"ID="FM89369"Monitoring PerformanceIDXID="w1422"BOOK="_idx" COLLECTION="nw41" TIDREF="i2511"IDXID="w1423"BOOK="_idx" COLLECTION="nw41" TIDREF="i3295"
Monitoring the performance of the router and connections is an important management task. If the router or links are not performing efficiently, this could cause problems for users or could signal a larger problem in your network. This section discusses the following topics:MARK=BULLETIDREF="FM71284""Determining Processing Time and Memory Usage"IDREF="FM80809""Monitoring Overall Link Performance"RENDERAS="SECT2"ID="FM71284"Determining Processing Time and Memory UsageIDXID="w1424"BOOK="_idx" COLLECTION="nw41" TIDREF="i2511"IDXID="w1425"BOOK="_idx" COLLECTION="nw41" TIDREF="i2511"IDXID="w1426"BOOK="_idx" COLLECTION="nw41" TIDREF="i3560"IDXID="w1427"BOOK="_idx" COLLECTION="nw41" TIDREF="i2375"
To determine the processing time and memory usage of a router, you use the MONITOR utility. When you load MONITOR, the screen shows two windows. The upper window displays information for the router, including utilization, and cache and packet buffer information. The lower window displays the CLASS=MENUITEM MOREINFO="NONE"Available Options menu. RENDERAS="SECT2"ID="FM80809"Monitoring Overall Link PerformanceIDXID="w1428"BOOK="_idx" COLLECTION="nw41" TIDREF="i2511"IDXID="w1429"BOOK="_idx" COLLECTION="nw41" TIDREF="i2109"
You can monitor the performance of a particular interface by looking at the following fields in the MONITOR utility:MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Send Line UtilizationCLASS=MENUITEM MOREINFO="NONE"Receive Line UtilizationCLASS=MENUITEM MOREINFO="NONE"Receive OverrunsCLASS=MENUITEM MOREINFO="NONE"Data Q Backup in 1/1000 second High values in these fields indicate that performance has degraded. In this case, consider a higher line speed. Note that some spikes are normal in all networks.PAGENUM=175 ID="BP179"RENDERAS="SECT1"ID="FM15389"ID="FM34681"ID="FM56187"Checking the Connection Between ServersIDXID="w1430"BOOK="_idx" COLLECTION="nw41" TIDREF="i3894"IDXID="w1431"BOOK="_idx" COLLECTION="nw41" TIDREF="i781"
You can check that the connection between servers is active by performing the following tasks:MARK=BULLETDetermine whether a link is active by using MONITOR.Determine if a remote server or services are reachable by running an echo or ping test.Monitor the Error Counters by using NetWare MONITOR and the consoles.This section discusses the following topics:MARK=BULLETIDREF="FM35782""Determining Whether a LAN Link is Active"IDREF="FM13503""Determining Whether a Remote IPX Server is Reachable"IDREF="FM88332""Determining Which IPX Services are Reachable"IDREF="FM95867""Determining Whether a Remote TCP/IP Server is Reachable"IDREF="FM57607""Determining Whether a Remote AppleTalk Server is Reachable"IDREF="FM98624""Determining Which AppleTalk Services are Reachable"IDREF="FM41660""Monitoring Error Counters"PAGENUM=175 ID="BP180"PAGENUM=176RENDERAS="SECT2"ID="FM35782"Determining Whether a LAN Link is ActiveIDXID="w1432"BOOK="_idx" COLLECTION="nw41" TIDREF="i2125"IDXID="w1433"BOOK="_idx" COLLECTION="nw41" TIDREF="i2511"
To determine if a link is active, load MONITOR and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"LAN/WAN Information (CLASS=MENUITEM MOREINFO="NONE"LAN/WAN Driver Information window appears) > Select the interface for which you want to see information Under CLASS=MENUITEM MOREINFO="NONE"Generic Statistics, look at the CLASS=MENUITEM MOREINFO="NONE"Total Packets Sent and CLASS=MENUITEM MOREINFO="NONE"Total Packets Received counters. The link is active if these counters are increasing.RENDERAS="SECT2"ID="FM13503"Determining Whether a Remote IPX Server is ReachableIDXID="w1434"BOOK="_idx" COLLECTION="nw41" TIDREF="i3894"IDXID="w1435"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"IDXID="w1436"BOOK="_idx" COLLECTION="nw41" TIDREF="i3761"
To determine if a remote server is reachable, you can run an IPX echo test. To run an echo test, load IPXPING and perform the following steps:PERFORMANCE="REQUIRED"Specify the target router address in the CLASS=MENUITEM MOREINFO="NONE"Network field.PERFORMANCE="REQUIRED"Specify the target router node number in the 
CLASS=MENUITEM MOREINFO="NONE"Node field.PERFORMANCE="REQUIRED"Specify the number of seconds between each transmission in the 
CLASS=MENUITEM MOREINFO="NONE"Seconds to pause between pings field.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to begin transmitting.To run the IPX echo test from a NetWare server, the server must be running IPXRTR and the router must use the NetWare® 4.1 software. Otherwise, you can run the IPX echo test from another server using the NetWare® 4.1 software.RENDERAS="SECT2"ID="FM88332"Determining Which IPX Services are ReachableIDXID="w1437"BOOK="_idx" COLLECTION="nw41" TIDREF="i4081"IDXID="w1438"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"
If you want to know whether a specific IPX service is available, you need to find out which IPX services are reachable. To determine the services available to a server, load IPXCON and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Services (CLASS=MENUITEM MOREINFO="NONE"Known Services window appears) > Select the service you want to reach to get information about it > Press MOREINFO="NONE"<Enter> (CLASS=MENUITEM MOREINFO="NONE"Service Information window appears)PAGENUM=177 ID="BP181"If a service is visible, then it is reachable. If you want to see information about the service, the Service Information window displays CLASS=MENUITEM MOREINFO="NONE"Name, CLASS=MENUITEM MOREINFO="NONE"Type, CLASS=MENUITEM MOREINFO="NONE"Network Number, CLASS=MENUITEM MOREINFO="NONE"Node, CLASS=MENUITEM MOREINFO="NONE"Socket, and additional path information for NLSP systems by selecting CLASS=MENUITEM MOREINFO="NONE"Destination Information.RENDERAS="SECT2"ID="FM95867"Determining Whether a Remote TCP/IP Server is ReachableIDXID="w1439"BOOK="_idx" COLLECTION="nw41" TIDREF="i3894"IDXID="w1440"BOOK="_idx" COLLECTION="nw41" TIDREF="i4450"IDXID="w1441"BOOK="_idx" COLLECTION="nw41" TIDREF="i3761"
To determine if a remote server is reachable, you can run an echo test. To run an echo test, load PING and perform the following steps:PERFORMANCE="REQUIRED"Specify the target server address in the CLASS=MENUITEM MOREINFO="NONE"Host Name field.PERFORMANCE="REQUIRED"Specify the number of seconds between each transmission in the 
CLASS=MENUITEM MOREINFO="NONE"Seconds to pause between pings field.PERFORMANCE="REQUIRED"Specify the packet size to transmit in the 
CLASS=MENUITEM MOREINFO="NONE"IP packet size to send in bytes field.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to begin transmitting.RENDERAS="SECT2"ID="FM57607"Determining Whether a Remote AppleTalk Server is ReachableIDXID="w1442"BOOK="_idx" COLLECTION="nw41" TIDREF="i3894"IDXID="w1443"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"IDXID="w1444"BOOK="_idx" COLLECTION="nw41" TIDREF="i3761"
To determine if a remote server is reachable, you can run an echo test. To run an echo test, load ATCON and perform the following steps:PERFORMANCE="REQUIRED"From the CLASS=MENUITEM MOREINFO="NONE"Available Actions menu, select CLASS=MENUITEM MOREINFO="NONE"Lookup Network Entities.PERFORMANCE="REQUIRED"In the 
CLASS=MENUITEM MOREINFO="NONE"Name field, type the name of the server you want to reach.PERFORMANCE="REQUIRED"In the 
CLASS=MENUITEM MOREINFO="NONE"Type field, enter the NBP type of the server you want to reach.Press 
MOREINFO="NONE"<Enter> to get a list of NBP types from which you can select.PERFORMANCE="REQUIRED"In the 
CLASS=MENUITEM MOREINFO="NONE"Zone field, enter the name of the zone in which the remote server resides.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Perform Lookup and press 
MOREINFO="NONE"<Enter>.The 
CLASS=MENUITEM MOREINFO="NONE"Network Entities Found window appears.
PAGENUM=178 ID="BP182"PERFORMANCE="REQUIRED"Select the server you want to reach.The 
CLASS=MENUITEM MOREINFO="NONE"Edit Echo Parameters and Execute Test window appears.PERFORMANCE="REQUIRED"Edit the echo parameters.You can edit the following parameters:
MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Mode---Choose CLASS=MENUITEM MOREINFO="NONE"Send Specified Number of Packets to send only the number of packets specified in the CLASS=MENUITEM MOREINFO="NONE"Number of Packets to Send field. Choose CLASS=MENUITEM MOREINFO="NONE"Send Continuously if you want to send packets until you decide to stop the echo test by pressing MOREINFO="NONE"<Esc>.CLASS=MENUITEM MOREINFO="NONE"Number of Packets to Send---Determines the number of echo requests to send to the remote server.CLASS=MENUITEM MOREINFO="NONE"Timeout---Determines the amount of time to wait for an echo reply from the remote server. If the reply returns before the timeout is over, the next echo request is sent. If the reply does not come back, an echo request is sent after the timeout is over.CLASS=MENUITEM MOREINFO="NONE"Number of Data Bytes---Specifies the size of the echo request packet.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Perform Echo and press 
MOREINFO="NONE"<Enter>.The 
CLASS=MENUITEM MOREINFO="NONE"Sending Echo Packets window appears. The window shows the progress of the echo test.RENDERAS="SECT2"ID="FM98624"Determining Which AppleTalk Services are ReachableIDXID="w1445"BOOK="_idx" COLLECTION="nw41" TIDREF="i4081"IDXID="w1446"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"
If you want to know whether a specific AppleTalk service is available, you need to find out which AppleTalk services are reachable. To determine the services available to a router, load ATCON and perform a lookup for network entities.To perform a lookup, complete the following steps:PERFORMANCE="REQUIRED"From the CLASS=MENUITEM MOREINFO="NONE"Available Actions menu, select CLASS=MENUITEM MOREINFO="NONE"Lookup Network Entities.PERFORMANCE="REQUIRED"In the 
CLASS=MENUITEM MOREINFO="NONE"Name field, type the name of the service for which you are looking.You can leave the default (=) to find all types of services.
PAGENUM=179 ID="BP183"PERFORMANCE="REQUIRED"In the 
CLASS=MENUITEM MOREINFO="NONE"Type field, enter the NBP type of the router you want to reach.Press 
MOREINFO="NONE"<Enter> to get a list of NBP types from which you can select.PERFORMANCE="REQUIRED"In the 
CLASS=MENUITEM MOREINFO="NONE"Zone field, enter the name of the zone in which the remote server resides.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Perform Lookup and press 
MOREINFO="NONE"<Enter>.The 
CLASS=MENUITEM MOREINFO="NONE"Network Entities Found window appears.RENDERAS="SECT2"ID="FM41660"Monitoring Error CountersIDXID="w1447"BOOK="_idx" COLLECTION="nw41" TIDREF="i2511"IDXID="w1448"BOOK="_idx" COLLECTION="nw41" TIDREF="i1338"
You monitor error counters to make sure they are not increasing rapidly. When an error counter is increasing, it indicates a problem. You can monitor error counters in one of the following ways:MARK=BULLETBy using NetWare MONITOR, to view counters such as CLASS=MENUITEM MOREINFO="NONE"Checksum Errors, CLASS=MENUITEM MOREINFO="NONE"Send and Receive Packet Errors, and interface-specific errors. To view these counters, load MONITOR and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"LAN/WAN Information (CLASS=MENUITEM MOREINFO="NONE"LAN/WAN Driver Information window appears) > Select the interface for which you want to see error countersBy using IPXCON, to view the following IPX counters:MARK=BULLETToo Many HopsHeader ErrorsUnknown SocketsDecompression ErrorsMalformed RequestsCompression ErrorsOpen Socket FailuresTo view these counters, load IPXCON and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IPX Information > Select CLASS=MENUITEM MOREINFO="NONE"Detailed IPX Information PAGENUM=180 ID="BP184"By using TCPCON, to view the following TCP/IP counters:MARK=BULLETIP ErrorsIP address errorsUnknown protocol errorsLocal errorsReassembly failures detectedFragmentation Failures DetectedTo view these counters, load TCPCON and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Statistics > Select CLASS=MENUITEM MOREINFO="NONE"IP > Select CLASS=MENUITEM MOREINFO="NONE"More IP StatisticsBy using ATCON, to view the following AppleTalk counters:MARK=BULLETBad DDP LengthBad DDP ChecksumNo Route FoundToo Many HopsTo view these counters, load ATCON and select CLASS=MENUITEM MOREINFO="NONE"Packet Statistics.RENDERAS="SECT1"ID="FM53135"Monitoring IPX InformationIDXID="w1449"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"IDXID="w1450"BOOK="_idx" COLLECTION="nw41" TIDREF="i2511"
Monitoring IPX information can give you a clear view of what your IPX network is doing, and whether the server is configured properly to run efficiently in the context of the network. This information can also be helpful in general troubleshooting and optimization of the network. This section discusses the following topics:MARK=BULLETIDREF="FM20213""Checking the IPX Routing Table"IDREF="FM27747""Checking an IPX Network for Duplicate Network Numbers"IDREF="FM96919""Determining Where NLSP is Running in Your Network"IDREF="FM83798""Finding NLSP Routers with Insufficient Memory"PAGENUM=181 ID="BP185"IDREF="FM85164""Finding the Designated Router on a LAN"RENDERAS="SECT2"ID="FM20213"Checking the IPX Routing TableIDXID="w1451"BOOK="_idx" COLLECTION="nw41" TIDREF="i2511"IDXID="w1452"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"
You can check the IPX routing table and information associated with each route by loading IPXCON and selecting the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Forwarding (CLASS=MENUITEM MOREINFO="NONE"Forwarding Table window appears) > Select the entry for which you want information (CLASS=MENUITEM MOREINFO="NONE"Destination Information window appears)The CLASS=MENUITEM MOREINFO="NONE"Forwarding Table shows you all known IPX destination networks. The list shows the following information about each item:MARK=BULLETThe network number of the destinationThe routing protocol through which the destination was learnedThe first hop circuit to the destinationThe name of the destinationThe CLASS=MENUITEM MOREINFO="NONE"Destination Information window expands on this information by showing information about the CLASS=MENUITEM MOREINFO="NONE"Next Hop (CLASS=MENUITEM MOREINFO="NONE"Name, CLASS=MENUITEM MOREINFO="NONE"Circuit, CLASS=MENUITEM MOREINFO="NONE"NIC Address), and by giving access to the services on the destination router that are available to the current router. If the destination is an NLSP destination, you may determine potential paths to the destination by selecting CLASS=MENUITEM MOREINFO="NONE"Potential Paths.PAGENUM=181 ID="BP186"PAGENUM=182RENDERAS="SECT2"Checking an IPX Network for Inactive RoutersIDXID="w1453"BOOK="_idx" COLLECTION="nw41" TIDREF="i2511"IDXID="w1454"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"IDXID="w1455"BOOK="_idx" COLLECTION="nw41" TIDREF="i3894"IDXID="w1456"BOOK="_idx" COLLECTION="nw41" TIDREF="i1771"
You can use IPXCON to identify routers on your network that are inactive---that is, not routing---for some reason. This information can often help you locate a defective network interface. To check your network for inactive routers, load IPXCON, select a system as described in IDREF="FM52280"Chapter 6, "Using Internetworking Utilities," and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"NLSP Information (CLASS=MENUITEM MOREINFO="NONE"NLSP Information window appears) > Select CLASS=MENUITEM MOREINFO="NONE"RoutersIPXCON lists the NLSP routers known to the system you are monitoring.Any router labeled CLASS=MENUITEM MOREINFO="NONE"Unreachable may either be down or have a defective network interface. It may also indicate that some other router in the path has one of these problems.Any router labeled CLASS=MENUITEM MOREINFO="NONE"Overloaded has run out of memory and can no longer process NLSP routing information.Routers not labeled CLASS=MENUITEM MOREINFO="NONE"Unreachable or CLASS=MENUITEM MOREINFO="NONE"Overloaded are operating properly.RENDERAS="SECT2"ID="FM27747"Checking an IPX Network for Duplicate Network NumbersIDXID="w1457"BOOK="_idx" COLLECTION="nw41" TIDREF="i2511"IDXID="w1458"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"IDXID="w1459"BOOK="_idx" COLLECTION="nw41" TIDREF="i3894"IDXID="w1460"BOOK="_idx" COLLECTION="nw41" TIDREF="i1271"
Each external network number that identifies a LAN on your IPX network must be unique. Incorrect configurations and other problems can cause two LANs to have the same external network number.One way in which this can occur is when a bridge connecting two LAN segments fails---a condition known as a split LAN. When the bridge fails, each segment becomes a separate LAN but retains the same network number. As a result, routers forwarding packets to that network number see two destinations and simply choose the nearest one.PAGENUM=182 ID="BP187"PAGENUM=183To check your network for duplicate network numbers, load IPXCON, select a system as described in IDREF="FM52280"Chapter 6, "Using Internetworking Utilities," and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"NLSP Information (CLASS=MENUITEM MOREINFO="NONE"NLSP Information window appears) > Select CLASS=MENUITEM MOREINFO="NONE"LANs (CLASS=MENUITEM MOREINFO="NONE"Known LANs window appears) The LANs are listed in numeric order by network number. Scroll through the list of LANs to look for duplicate network numbers.RENDERAS="SECT2"Checking an IPX Network for Duplicate System IDsIDXID="w1461"BOOK="_idx" COLLECTION="nw41" TIDREF="i2511"IDXID="w1462"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"IDXID="w1463"BOOK="_idx" COLLECTION="nw41" TIDREF="i3894"IDXID="w1464"BOOK="_idx" COLLECTION="nw41" TIDREF="i1274"
To check your network for duplicate System IDs, load IPXCON, select a system as described in IDREF="FM52280"Chapter 6, "Using Internetworking Utilities," and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"NLSP Information (CLASS=MENUITEM MOREINFO="NONE"NLSP Information window appears) > Select CLASS=MENUITEM MOREINFO="NONE"System Information MOREINFO="NONE"> Select the field associated with CLASS=MENUITEM MOREINFO="NONE"Detailed NLSP System Information Check the numbers associated with the CLASS=MENUITEM MOREINFO="NONE"Sequence Number Skips, if the number is increasing, there are two or more NLSP routers on your network with the same system ID.RENDERAS="SECT2"ID="FM96919"Determining Where NLSP is Running in Your NetworkIDXID="w1465"BOOK="_idx" COLLECTION="nw41" TIDREF="i2511"IDXID="w1466"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"IDXID="w1467"BOOK="_idx" COLLECTION="nw41" TIDREF="i2927"
After migrating your network, you can identify which LANs on your IPX network are using NLSP or RIP---or both---as the routing protocol.If you partitioned your IPX network into routing areas, note the following points:MARK=BULLETThe procedure in this section shows only the LANs and NLSP routers that are within the same routing area as the system you are currently monitoring.RIP should be running only on the servers at area boundaries.For an explanation of routing areas, see the BOOK="nlsp_enu" COLLECTION="nw41"NetWare 4.1 NLSP Migration Guide.PAGENUM=184 ID="BP188"To find LANs on which NLSP or RIP is running, load IPXCON, select a system as described in IDREF="FM52280"Chapter 6, "Using Internetworking Utilities," and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"NLSP Information (CLASS=MENUITEM MOREINFO="NONE"NLSP Information window appears) > Select CLASS=MENUITEM MOREINFO="NONE"LANsThe CLASS=MENUITEM MOREINFO="NONE"Known LANs window displays the following information about each NetWare LAN of which the local system is aware:MARK=BULLETNetwork Number---External network number of the LAN.CLASS=MENUITEM MOREINFO="NONE"Throughput---Number of Mbps reported by the LAN board.CLASS=MENUITEM MOREINFO="NONE"Delay---Time, in microseconds, for packets to reach the LAN.If NLSP is importing RIP routes to a LAN, the entry is labeled CLASS=MENUITEM MOREINFO="NONE"RIP Active. If the entry is labeled CLASS=MENUITEM MOREINFO="NONE"Unreachable, the LAN is no longer accessible from the local system. No label means that NLSP is the only routing protocol running on the LAN and that the LAN is reachable.You can select one of the LANs to see which NLSP routers are on it.RENDERAS="SECT2"ID="FM83798"Finding NLSP Routers with Insufficient MemoryIDXID="w1468"BOOK="_idx" COLLECTION="nw41" TIDREF="i2511"IDXID="w1469"BOOK="_idx" COLLECTION="nw41" TIDREF="i1840"IDXID="w1470"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"IDXID="w1471"BOOK="_idx" COLLECTION="nw41" TIDREF="i3894"IDXID="w1472"BOOK="_idx" COLLECTION="nw41" TIDREF="i2375"
To check your network for routers that have run out of memory, load IPXCON, select a system as described in IDREF="FM52280"Chapter 6, "Using Internetworking Utilities," and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"NLSP Information (CLASS=MENUITEM MOREINFO="NONE"NLSP Information window appears) > Select CLASS=MENUITEM MOREINFO="NONE"RoutersIf a router does not have enough memory to process routing information, the entry is labeled CLASS=MENUITEM MOREINFO="NONE"Overloaded.You can also select CLASS=MENUITEM MOREINFO="NONE"System Information and check the following information:MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Level 1 Overloaded---It should read CLASS=MENUITEM MOREINFO="NONE"No. If it reads CLASS=MENUITEM MOREINFO="NONE"Yes, the router does not have enough memory to process routing information.CLASS=MENUITEM MOREINFO="NONE"Detailed NLSP System Information---The CLASS=MENUITEM MOREINFO="NONE"Level 1 Database Overloads field indicates how many times the router has run out of memory.PAGENUM=185 ID="BP189"RENDERAS="SECT2"ID="FM85164"Finding the Designated Router on a LANIDXID="w1473"BOOK="_idx" COLLECTION="nw41" TIDREF="i2511"IDXID="w1474"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"IDXID="w1475"BOOK="_idx" COLLECTION="nw41" TIDREF="i1000"IDXID="w1476"BOOK="_idx" COLLECTION="nw41" TIDREF="i2927"
The Designated Router is an NLSP router elected by its peers to represent and keep track of the connectivity of its LAN. The Designated Router handles exchanges of link state information on behalf of all other NLSP routers on the LAN.To find the Designated Router on a LAN, load IPXCON, select a system as described in IDREF="FM52280"Chapter 6, "Using Internetworking Utilities," and select the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Circuits (CLASS=MENUITEM MOREINFO="NONE"Circuit window appears) > Select a broadcast circuit (CLASS=MENUITEM MOREINFO="NONE"Circuit Information window appears)The CLASS=MENUITEM MOREINFO="NONE"Circuits window displays the name, type, and state of each circuit. Only broadcast (LAN) circuits have Designated Routers.The CLASS=MENUITEM MOREINFO="NONE"Circuit Information window displays, among other information, the name of the Designated Router and the external network number of the LAN it represents.To see more information about the Designated Router, complete the following steps:PERFORMANCE="REQUIRED"Record the name of the Designated Router.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> until you return to the 
CLASS=MENUITEM MOREINFO="NONE"Available Options menu.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"SNMP Access Configuration.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"IPX as the transport protocol.PERFORMANCE="REQUIRED"Type the name of the Designated Router in the 
CLASS=MENUITEM MOREINFO="NONE"Host Address field, then press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to return to the 
CLASS=MENUITEM MOREINFO="NONE"Available Options menu.In a few moments, IPXCON begins displaying statistics for the Designated Router.PAGENUM=186 ID="BP190"RENDERAS="SECT1"ID="FM12512"Monitoring TCP/IP InformationIDXID="w1477"BOOK="_idx" COLLECTION="nw41" TIDREF="i2511"IDXID="w1478"BOOK="_idx" COLLECTION="nw41" TIDREF="i4450"
Monitoring TCP/IP information can give you a clear view of what your TCP/IP network is doing, and whether the server is configured properly to run efficiently in the context of the network. This information can also be helpful in general troubleshooting and optimization of the network. This section discusses the following topics:MARK=BULLETIDREF="FM52477""Checking the TCP/IP Routing Table"IDREF="FM73265""Monitoring the TCP/IP Protocols Configured"RENDERAS="SECT2"ID="FM52477"Checking the TCP/IP Routing TableIDXID="w1479"BOOK="_idx" COLLECTION="nw41" TIDREF="i2511"IDXID="w1480"BOOK="_idx" COLLECTION="nw41" TIDREF="i4450"IDXID="w1481"BOOK="_idx" COLLECTION="nw41" TIDREF="i3910"
You can check the TCP/IP routing table and information associated with each route by loading TCPCON and selecting the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"IP Routing Table > Select the entry for which you want information (CLASS=MENUITEM MOREINFO="NONE"IP Route Information window appears)The CLASS=MENUITEM MOREINFO="NONE"IP Routing Table shows you all known TCP/IP destination networks. The list has the following information about each item:MARK=BULLETThe IP address of the destinationThe IP address of the next hop for the routeThe type of the route (Direct, Remote)The primary cost for the routeThe interface used to reach a routeThe CLASS=MENUITEM MOREINFO="NONE"IP Route Information window expands on this information by showing information about the mask used and the routing protocol through which the destination was learned.PAGENUM=186 ID="BP191"PAGENUM=187RENDERAS="SECT2"ID="FM73265"Monitoring the TCP/IP Protocols ConfiguredIDXID="w1482"BOOK="_idx" COLLECTION="nw41" TIDREF="i2511"IDXID="w1483"BOOK="_idx" COLLECTION="nw41" TIDREF="i4450"IDXID="w1484"BOOK="_idx" COLLECTION="nw41" TIDREF="i3609"
You can view, and sometimes change, the configuration of TCP/IP protocols configured for use in your server. You can reach this information by loading TCPCON and selecting CLASS=MENUITEM MOREINFO="NONE"Protocol Information. You can configure and view statistics and other information for the following protocols:MARK=BULLETEGPICMPIPOSPFTCPUDPRENDERAS="SECT1"ID="FM53474"Monitoring AppleTalk InformationIDXID="w1485"BOOK="_idx" COLLECTION="nw41" TIDREF="i2511"IDXID="w1486"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"
Monitoring AppleTalk information can give you a clear view of what your AppleTalk network is doing, and whether the server is configured properly to run efficiently in the context of the network. This information can also be helpful in general troubleshooting and optimization of the network. This section discusses the following topics:MARK=BULLETIDREF="FM64721""Checking the AppleTalk Routing Table"IDREF="FM77944""Monitoring AURP"PAGENUM=187 ID="BP192"PAGENUM=188RENDERAS="SECT2"ID="FM64721"Checking the AppleTalk Routing TableIDXID="w1487"BOOK="_idx" COLLECTION="nw41" TIDREF="i2511"IDXID="w1488"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"IDXID="w1489"BOOK="_idx" COLLECTION="nw41" TIDREF="i3910"
You can check the AppleTalk routing table and information associated with each route by loading ATCON and selecting the following path:Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Routing Table (CLASS=MENUITEM MOREINFO="NONE"Sort Routes By window appears) > Select CLASS=MENUITEM MOREINFO="NONE"Network or CLASS=MENUITEM MOREINFO="NONE"Zone Name to sort the list of routes (CLASS=MENUITEM MOREINFO="NONE"Routing Table window appears) The CLASS=MENUITEM MOREINFO="NONE"Routing Table shows you all known AppleTalk destination networks. The list shows the following information about each item:MARK=BULLETThe network number or rangeThe zone or zones assigned to the associated networkThe status of the destinationThe number of hops between the router and destinationsThe DDP address of the next hopThe port number of the interface used to reach a routeRENDERAS="SECT2"ID="FM77944"Monitoring AURPIDXID="w1490"BOOK="_idx" COLLECTION="nw41" TIDREF="i2511"IDXID="w1491"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"IDXID="w1492"BOOK="_idx" COLLECTION="nw41" TIDREF="i349"
If you have AURP configured, you can monitor the AURP connections to check on their connection state by loading ATCON and selecting CLASS=MENUITEM MOREINFO="NONE"AURP Information.The list shows the following information about each AURP connection:MARK=BULLETThe address of the peer to which the router is connectedThe state of the receiver peerThe state of the sender peerThe time between keep-alive packets sent between two peersLABEL="8"PAGENUM=189 ID="BP193"ID="FM70491"Configuring Communication Protocols on an SFT III ServerIDXID="w1493"BOOK="_idx" COLLECTION="nw41" TIDREF="i759"IDXID="w1494"BOOK="_idx" COLLECTION="nw41" TIDREF="i4126"IDXID="w1495"BOOK="_idx" COLLECTION="nw41" TIDREF="i1794"IDXID="w1496"BOOK="_idx" COLLECTION="nw41" TIDREF="i4736"
This chapter describes how to use INETCFG to configure the AppleTalk, IP, and IPXTM communications protocols for a IDXID="w1497"BOOK="_idx" COLLECTION="nw41" TIDREF="i2804"
NetWare® SFT IIITM server. To perform this configuration, INETCFG utility must be run in the MS Engine and the IO Engines of both the primary and secondary servers. The IO Engine of the primary server uses the communications protocols configured with INETCFG to perform all the network routing functions for its SFT III server. In addition, it routes packets over a separate virtual network that connects the IO Engines to the MS Engine. This virtual network is referred to as the "SFT III Network." The communications protocols of the IO Engine of the secondary server are configured so that it can perform network routing functions to the SFT III network if the IO Engine in the primary server fails. IDREF="FM68887"Figure 8-1 demonstrates the general routing configuration for SFT III servers. LABEL="8-1" FLOAT="0"IDXID="w1498"BOOK="_idx" COLLECTION="nw41" TIDREF="i4116"ID="FM68887"SFT III Server Routing ConfigurationFILEREF="sft1.tif"The IO Engine in the secondary server only routes to the MS Engine until it becomes the primary server. At that time, the bind to the network takes effect and the secondary server routes on the main network.PAGENUM=189 ID="BP194"PAGENUM=190Although the communications protocol software that is installed on the SFT III server is identical to that of standard protocol software, the configuration can be somewhat different. This is because of the need to configure the communications protocol software in each of the engines of the SFT III server. Depending on the protocol being routed, there are different configuration parameters.This chapter contains the following sections:MARK=BULLETIDREF="FM36123"IDREF="FM36123""Creating an SFT III Network for AppleTalk"This section describes creating an SFT III network for the AppleTalk protocol.IDREF="FM30056""Creating an SFT III Network for IPX"This section describes creating an SFT III network for the IPX protocol.IDREF="FM12367""Creating an SFT III Network for IP"This section describes creating an SFT III network for the IP protocol.IDREF="FM37077""Configuring Communications Protocols on SFT III Server Engines"This section describes configuring the internal networks in each of the three protocols, and contains the procedures you use to do this.RENDERAS="SECT1"ID="FM36123"Creating an SFT III Network for AppleTalkIDXID="w1499"BOOK="_idx" COLLECTION="nw41" TIDREF="i884"IDXID="w1500"BOOK="_idx" COLLECTION="nw41" TIDREF="i4120"IDXID="w1501"BOOK="_idx" COLLECTION="nw41" TIDREF="i2891"
Configuring AppleTalk in the MS Engine and IO Engines of an SFT III server requires that an SFT III virtual AppleTalk network be established. This means that AppleTalk in each of the three SFT III server engines must be connected to that SFT III virtual AppleTalk network and that a separate AppleTalk network number must be assigned to the virtual network, as shown in IDREF="FM69946"Figure 8-2. AppleTalk in the IO Engines must be configured as routers, with packet forwarding CLASS=MENUITEM MOREINFO="NONE"On. AppleTalk in the MS Engine must be configured as an end system, with packet forwarding CLASS=MENUITEM MOREINFO="NONE"Off.IDXID="w1502"BOOK="_idx" COLLECTION="nw41" TIDREF="i4116"PAGENUM=191 ID="BP195"LABEL="8-2" FLOAT="0"ID="FM69946"SFT III Internal AppleTalk Network ConfigurationFILEREF="sft2.tif"Also, the AppleTalk network that connects the IO Engines to the MS Engine must be assigned to one or more AppleTalk zones.IDXID="w1503"BOOK="_idx" COLLECTION="nw41" TIDREF="i252"IDXID="w1504"BOOK="_idx" COLLECTION="nw41" TIDREF="i4875"IDXID="w1505"BOOK="_idx" COLLECTION="nw41" TIDREF="i427"
 The zone list can contain existing zones or unique zones that contain only the SFT III network. One consequence of this configuration is that a bind is generated in each of the engines to the SFT III virtual board. A line is generated in each of theIDXID="w1506"BOOK="_idx" COLLECTION="nw41" TIDREF="i2671"IDXID="w1507"BOOK="_idx" COLLECTION="nw41" TIDREF="i1484"
 NETINFO.CFG files to indicate this bind. In the MS Engine, the following command is created:FORMAT="LINESPECIFIC"MOREINFO="NONE"BIND AppleTlk MSENGINEIn the IO Engine, the MOREINFO="NONE"BIND command includes the AppleTalk network number. For example, if you configure an IO Engine of an SFT III server with the AppleTalk network number 1234, its MOREINFO="NONE"BIND command appears as shown:FORMAT="LINESPECIFIC"MOREINFO="NONE"BIND AppleTlk MSENGINE net=1234-1234RENDERAS="SECT1"ID="FM30056"Creating an SFT III Network for IPXIDXID="w1508"BOOK="_idx" COLLECTION="nw41" TIDREF="i884"IDXID="w1509"BOOK="_idx" COLLECTION="nw41" TIDREF="i4120"IDXID="w1510"BOOK="_idx" COLLECTION="nw41" TIDREF="i2891"
For the IPX protocol, there is no need to create an internal network because one already exists. Each NetWare server has its own internal IPX network. In an SFT III server, both MS Engines share one internal network and each of the IO Engines has its own internal IPX network. The IO Engine of the primary SFT III server is bound automatically to the internal IPX network of the MS Engine. For this reason, an additional internal network is not required to connect the two engines of the SFT III server.PAGENUM=192 ID="BP196"RENDERAS="SECT1"ID="FM12367"Creating an SFT III Network for IPIDXID="w1511"BOOK="_idx" COLLECTION="nw41" TIDREF="i884"IDXID="w1512"BOOK="_idx" COLLECTION="nw41" TIDREF="i4120"IDXID="w1513"BOOK="_idx" COLLECTION="nw41" TIDREF="i2891"
Configuring IP routing in the MS Engine and IO Engines of an SFT III server requires that an SFT III network be established. This virtual network connects the MS Engine to the IO Engines. This means that a separate subnetwork must be created with two separate host addresses, as shown in IDREF="FM64745"Figure 8-3. LABEL="8-3" FLOAT="0"IDXID="w1514"BOOK="_idx" COLLECTION="nw41" TIDREF="i4116"ID="FM64745"SFT III Internal IP Network ConfigurationFILEREF="sft3.tif"Because the MS Engines are mirrored, they can share the same host address. Similarly, it is best to configure each IO Engine with the same host address. This can be done without causing a conflict, because only one of the IO Engines operates on the SFT III virtual network at any one time.This subnetwork is like any other subnetwork on your IP network. It must be assigned an IP address from the IP network addresses assigned to you. One consequence of this configuration is that a bind is generated in each of the engines to a virtual board. A line is generated in each of the IDXID="w1515"BOOK="_idx" COLLECTION="nw41" TIDREF="i2671"IDXID="w1516"BOOK="_idx" COLLECTION="nw41" TIDREF="i1484"
NETINFO.CFG files to indicate this bind. For example, if you configure a server engine's SFT III network host address to be 144.1.1.2 and its mask with the value FF.FF.0.0, its MOREINFO="NONE"BIND command appears as shown:FORMAT="LINESPECIFIC"MOREINFO="NONE"BIND IP MSENGINE Address=144.1.1.2
   Mask=FF.FF.0.0
PAGENUM=193 ID="BP197"RENDERAS="SECT1"ID="FM37077"Configuring Communications Protocols on SFT III Server EnginesIDXID="w1517"BOOK="_idx" COLLECTION="nw41" TIDREF="i759"IDXID="w1518"BOOK="_idx" COLLECTION="nw41" TIDREF="i4123"IDXID="w1519"BOOK="_idx" COLLECTION="nw41" TIDREF="i1874"IDXID="w1520"BOOK="_idx" COLLECTION="nw41" TIDREF="i4736"IDXID="w1521"BOOK="_idx" COLLECTION="nw41" TIDREF="i1903"IDXID="w1522"BOOK="_idx" COLLECTION="nw41" TIDREF="i1484"IDXID="w1523"BOOK="_idx" COLLECTION="nw41" TIDREF="i2377"IDXID="w1524"BOOK="_idx" COLLECTION="nw41" TIDREF="i1898"IDXID="w1525"BOOK="_idx" COLLECTION="nw41" TIDREF="i1484"
Configuring the communications protocols on SFT III servers involves running INETCFG to set individual protocol parameters. If the allocation of memory between the MS Engine and the IO Engine is not set to an adequate value, INETCFG does not run. If your SFT III servers have 16 MB of memory or less, there is not enough memory allocated to the IO Engine to run INETCFG. To set the memory allocation between the IO Engine and MS Engine to a level adequate to run INETCFG, insert the following commands into the IOSTART.NCF file:FORMAT="LINESPECIFIC"MOREINFO="NONE"SET NEW START ADDRESS FOR UNCLAIMED MEMORY
   BLOCK=8000000
SET MAXIMUM PHYSICAL RECEIVE PACKET SIZE=1518In the IO Engine, 1518 is adequate for Ethernet; 4202 is better for token ring.You must then bring down the server and restart it for the changes to memory allocation to take effect.Once you have adequate memory allocation between the MS Engine and IO Engine, you can run INETCFG as described.The communications protocol parameters are then configured separately in each of the following SFT III server engines:MARK=BULLETThe MS Engine The IO Engine of the primary serverThe IO Engine of the secondary serverPAGENUM=194 ID="BP198"Depending on the engine being configured, many of the same parameters required for normal configuration are required along with a set of parameters specific to SFT III. This chapter describes the procedures for configuring the parameters that are specific to SFT III servers. The common parameters differ, depending on the protocol and are described in detail in the protocol references listed in IDREF="FM13670"Table 8-1. IDXID="w1526"BOOK="_idx" COLLECTION="nw41" TIDREF="i3598"IDXID="w1527"BOOK="_idx" COLLECTION="nw41" TIDREF="i3598"IDXID="w1528"BOOK="_idx" COLLECTION="nw41" TIDREF="i3598"IDXID="w1529"BOOK="_idx" COLLECTION="nw41" TIDREF="i1915"IDXID="w1530"BOOK="_idx" COLLECTION="nw41" TIDREF="i1952"IDXID="w1531"BOOK="_idx" COLLECTION="nw41" TIDREF="i232"IDXID="w1532"BOOK="_idx" COLLECTION="nw41" TIDREF="i759"IDXID="w1533"BOOK="_idx" COLLECTION="nw41" TIDREF="i2531"LABEL="8-1" PGWIDE=1 TOCENTRY="1"ID="FM13670"Protocol ReferencesCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="9*"COLNAME=2 COLWIDTH="17*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Router ProtocolCOLNAME=2 ROTATE="0" MOREROWS="0"ReferencesVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"AppleTalk COLNAME=2 ROTATE="0" MOREROWS="0"BOOK="atrefenu" COLLECTION="nw41"NetWare 4.1 AppleTalk* ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"IPCOLNAME=2 ROTATE="0" MOREROWS="0"BOOK="tcpipenu" COLLECTION="nw41"NetWare 4.1 TCP/IP ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"IPXCOLNAME=2 ROTATE="0" MOREROWS="0"BOOK="ipxrtenu" COLLECTION="nw41"NetWare 4.1 IPX ReferenceTo support file access, the secondary IO Engine requires an IPX connection to the primary IO Engine. If this connection fails, the IO Engine's inability to support file access might result in either of the following error messages: MOREINFO="NONE"CONLOG-1.02-7: Cannot open SYS:ETC\IO2\CONSOLE.LOGMOREINFO="NONE"INETCFG-3.10-49: Unable to determine valid configuration directory for this IO Engine. The directory should be either SYS:ETC\IO1 or SYS:ETC\IO2 and should be specified on the snmp load line (ex: load snmp config=SYS:ETC\IO2). Program execution cannot continue normally. If either of these messages appears, make sure that the IPX connection between the IO Engines is working and that Directory Services is functioning normally. RENDERAS="SECT2"ID="FM24450"Configuring AppleTalk Parameters for the MS EngineIDXID="w1534"BOOK="_idx" COLLECTION="nw41" TIDREF="i759"IDXID="w1535"BOOK="_idx" COLLECTION="nw41" TIDREF="i231"IDXID="w1536"BOOK="_idx" COLLECTION="nw41" TIDREF="i2531"
To configure the AppleTalk protocol parameters for the MS Engine, complete the following steps:PERFORMANCE="REQUIRED"If INETCFGIDXID="w1537"BOOK="_idx" COLLECTION="nw41" TIDREF="i1874"IDXID="w1538"BOOK="_idx" COLLECTION="nw41" TIDREF="i4736"
 is not already running, type the following command at the server prompt:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INETCFG MOREINFO="NONE"<Enter>The 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Protocols from the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu.The 
CLASS=MENUITEM MOREINFO="NONE"Protocols Supported window appears.
PAGENUM=195 ID="BP199"PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"AppleTalk from the 
CLASS=MENUITEM MOREINFO="NONE"Protocols Supported menu.The 
CLASS=MENUITEM MOREINFO="NONE"AppleTalk Protocol Configuration window appears.PERFORMANCE="REQUIRED"Configure the SFT III-specific parameter described in 
IDREF="FM63031"Table 8-2. 
IDXID="w1539"BOOK="_idx" COLLECTION="nw41" TIDREF="i231"IDXID="w1540"BOOK="_idx" COLLECTION="nw41" TIDREF="i4119"LABEL="8-2" PGWIDE=1 TOCENTRY="1"ID="FM63031"AppleTalk Protocol Parameters for SFT III MS EngineCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="9*"COLNAME=2 COLWIDTH="13*"COLNAME=3 COLWIDTH="12*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ParameterIDXID="w1541"BOOK="_idx" COLLECTION="nw41" TIDREF="i3596"IDXID="w1542"BOOK="_idx" COLLECTION="nw41" TIDREF="i3179"COLNAME=2 ROTATE="0" MOREROWS="0"DescriptionCOLNAME=3 ROTATE="0" MOREROWS="0"Range/Options and DefaultVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Packet ForwardingCOLNAME=2 ROTATE="0" MOREROWS="0"Because the MS Engine is connected only to the IO Engine of its server, it is always configured as an end node.COLNAME=3 ROTATE="0" MOREROWS="0"Disabled ("end node") is the only allowed setting.PERFORMANCE="REQUIRED"Configure the other parameters as described in the BOOK="atrefenu" COLLECTION="nw41"NetWare 4.1 AppleTalk* Reference.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> until the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears.RENDERAS="SECT2"Configuring IPX Parameters for the MS EngineIDXID="w1543"BOOK="_idx" COLLECTION="nw41" TIDREF="i759"IDXID="w1544"BOOK="_idx" COLLECTION="nw41" TIDREF="i1951"IDXID="w1545"BOOK="_idx" COLLECTION="nw41" TIDREF="i2531"To configure the IPX protocol parameters in the MS Engine, complete the following steps:PERFORMANCE="REQUIRED"If INETCFG is not already running, type the following command at the server prompt:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INETCFG MOREINFO="NONE"<Enter>The 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Protocols from the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu.The 
CLASS=MENUITEM MOREINFO="NONE"Protocols Supported window appears.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"IPX from the 
CLASS=MENUITEM MOREINFO="NONE"Protocols Supported menu.The 
CLASS=MENUITEM MOREINFO="NONE"IPX Protocol Configuration window appears.
PAGENUM=196 ID="BP200"PERFORMANCE="REQUIRED"ID="FM69465"Configure the parameters described in 
IDREF="FM27431"Table 8-3. 
IDXID="w1546"BOOK="_idx" COLLECTION="nw41" TIDREF="i1951"IDXID="w1547"BOOK="_idx" COLLECTION="nw41" TIDREF="i4119"LABEL="8-3" PGWIDE=1 TOCENTRY="1"ID="FM27431"IPX Protocol Parameters for SFT III MS EngineCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="9*"COLNAME=2 COLWIDTH="13*"COLNAME=3 COLWIDTH="12*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ParameterIDXID="w1548"BOOK="_idx" COLLECTION="nw41" TIDREF="i3596"IDXID="w1549"BOOK="_idx" COLLECTION="nw41" TIDREF="i2774"COLNAME=2 ROTATE="0" MOREROWS="0"DescriptionCOLNAME=3 ROTATE="0" MOREROWS="0"Range/Options and DefaultVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"NetWare Operating Systems IPXCOLNAME=2 ROTATE="0" MOREROWS="0"Enables or disables the IPX implementation of the core NetWare Operating System. Novell recommends that this setting be kept enabled to ensure superior performance.Selecting CLASS=MENUITEM MOREINFO="NONE"Disabled for this parameter enables the router IPX implementation and allows the setting of several other routing parameters for routing customization. COLNAME=3 ROTATE="0" MOREROWS="0"Options: Enabled, DisabledDefault: EnabledPERFORMANCE="REQUIRED"If you selected 
CLASS=MENUITEM MOREINFO="NONE"Disabled in the 
IDREF="FM69465"Step 4, configure the other parameters as described in the BOOK="ipxrtenu" COLLECTION="nw41"NetWare 4.1 IPX Reference.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> until the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears.RENDERAS="SECT2"Configuring IP Parameters for the MS EngineIDXID="w1550"BOOK="_idx" COLLECTION="nw41" TIDREF="i759"IDXID="w1551"BOOK="_idx" COLLECTION="nw41" TIDREF="i1914"IDXID="w1552"BOOK="_idx" COLLECTION="nw41" TIDREF="i2531"To configure the IP protocol parameters in the MS Engine of the primary server, complete the following steps:PERFORMANCE="REQUIRED"If INETCFG is notIDXID="w1553"BOOK="_idx" COLLECTION="nw41" TIDREF="i1874"IDXID="w1554"BOOK="_idx" COLLECTION="nw41" TIDREF="i4736"
 already running, type the following command at the server prompt:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INETCFG MOREINFO="NONE"<Enter>The 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Protocols from the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu.The 
CLASS=MENUITEM MOREINFO="NONE"Protocols Supported window appears.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"TCP/IP from the 
CLASS=MENUITEM MOREINFO="NONE"Protocols Supported menu.The 
CLASS=MENUITEM MOREINFO="NONE"TCP/IP Protocol Configuration window appears.
PAGENUM=197 ID="BP201"PERFORMANCE="REQUIRED"Configure the parameters described in 
IDREF="FM31296"Table 8-4IDXID="w1555"BOOK="_idx" COLLECTION="nw41" TIDREF="i1914"IDXID="w1556"BOOK="_idx" COLLECTION="nw41" TIDREF="i4119"LABEL="8-4" PGWIDE=1 TOCENTRY="1"ID="FM31296"IP Protocol Parameters for SFT III MS Engine COLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="9*"COLNAME=2 COLWIDTH="13*"COLNAME=3 COLWIDTH="12*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ParameterIDXID="w1557"BOOK="_idx" COLLECTION="nw41" TIDREF="i3596"IDXID="w1558"BOOK="_idx" COLLECTION="nw41" TIDREF="i3596"IDXID="w1559"BOOK="_idx" COLLECTION="nw41" TIDREF="i3596"COLNAME=2 ROTATE="0" MOREROWS="0"DescriptionCOLNAME=3 ROTATE="0" MOREROWS="0"Range/Options and DefaultVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IP Packet Forwarding IDXID="w1560"BOOK="_idx" COLLECTION="nw41" TIDREF="i1913"IDXID="w1561"BOOK="_idx" COLLECTION="nw41" TIDREF="i1908"IDXID="w1562"BOOK="_idx" COLLECTION="nw41" TIDREF="i4320"COLNAME=2 ROTATE="0" MOREROWS="0"Because the MS Engine is connected only to the IO Engine of its server, it is always configured as an end node.COLNAME=3 ROTATE="0" MOREROWS="0"Disabled ("end node").COLNAME=1 ROTATE="0" MOREROWS="0"IP Address of SFT III NetworkCOLNAME=2 ROTATE="0" MOREROWS="0"The MS Engine and the IO Engines must each be configured with unique IP host addresses on the SFT III virtual network.COLNAME=3 ROTATE="0" MOREROWS="0"Any IP host address allowed on the SFT III server's virtual network.COLNAME=1 ROTATE="0" MOREROWS="0"Subnetwork Mask of SFT III NetworkCOLNAME=2 ROTATE="0" MOREROWS="0"A subnetwork mask is required to designate a separate internal IP network for the SFT III server.COLNAME=3 ROTATE="0" MOREROWS="0"The subnetwork mask required to designate the separate IP subnetwork being used for the SFT III server's internal networkPERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> until you the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears.RENDERAS="SECT2"Configuring AppleTalk Parameters for the IO EngineIDXID="w1563"BOOK="_idx" COLLECTION="nw41" TIDREF="i759"IDXID="w1564"BOOK="_idx" COLLECTION="nw41" TIDREF="i231"IDXID="w1565"BOOK="_idx" COLLECTION="nw41" TIDREF="i1897"IDXID="w1566"BOOK="_idx" COLLECTION="nw41" TIDREF="i4117"
To configure the AppleTalk protocol parameters in both the primary server and the secondary server IO Engines, complete the following steps:PERFORMANCE="REQUIRED"If INETCFG is not IDXID="w1567"BOOK="_idx" COLLECTION="nw41" TIDREF="i1874"IDXID="w1568"BOOK="_idx" COLLECTION="nw41" TIDREF="i4736"
already running, type the following command at the server prompt:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INETCFG MOREINFO="NONE"<Enter>The 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Protocols from the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu.The 
CLASS=MENUITEM MOREINFO="NONE"Protocols Supported window appears.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"AppleTalk from the 
CLASS=MENUITEM MOREINFO="NONE"Protocols Supported menu.The 
CLASS=MENUITEM MOREINFO="NONE"AppleTalk Protocol Configuration window appears.
PAGENUM=198 ID="BP202"PERFORMANCE="REQUIRED"Configure the parameters described in 
IDREF="FM21943"Table 8-5. LABEL="8-5" PGWIDE=1 TOCENTRY="1"ID="FM21943"AppleTalk Protocol Parameters for SFT III IO EngineCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="9*"COLNAME=2 COLWIDTH="13*"COLNAME=3 COLWIDTH="12*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ParameterCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionCOLNAME=3 ROTATE="0" MOREROWS="0"Range/Options and DefaultVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Packet ForwardingCOLNAME=2 ROTATE="0" MOREROWS="0"Because the MS Engine of the SFT III server requires that packets be forwarded from the IO Engine, forwarding is always enabled.COLNAME=3 ROTATE="0" MOREROWS="0"Enabled ("router") is the only allowed setting.COLNAME=1 ROTATE="0" MOREROWS="0"Network Number for SFT III NetworkCOLNAME=2 ROTATE="0" MOREROWS="0"A separate internal network must be assigned for the SFT III server. This network is a standard AppleTalk network and its number must be unique on the internetwork that the server is connected to. Enter the same network number for both IO Engines.COLNAME=3 ROTATE="0" MOREROWS="0"A unique decimal number between 1 and 65279.COLNAME=1 ROTATE="0" MOREROWS="0"Network Zone for SFT III NetworkCOLNAME=2 ROTATE="0" MOREROWS="0"The SFT III network must be assigned to one or more AppleTalk zones. The zone list can be unique or the same one currently being used. Enter the same zone list on both IO Engines.COLNAME=3 ROTATE="0" MOREROWS="0"One or more names of up to 32 characters.PERFORMANCE="REQUIRED"Configure the other AppleTalk parameters as described in the 
BOOK="atrefenu" COLLECTION="nw41"NetWare 4.1 AppleTalk* Reference.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> until the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears.RENDERAS="SECT2"Configuring IPX Protocol Parameters for the IO EngineIDXID="w1569"BOOK="_idx" COLLECTION="nw41" TIDREF="i4117"IDXID="w1570"BOOK="_idx" COLLECTION="nw41" TIDREF="i759"IDXID="w1571"BOOK="_idx" COLLECTION="nw41" TIDREF="i1951"IDXID="w1572"BOOK="_idx" COLLECTION="nw41" TIDREF="i1897"IDXID="w1573"BOOK="_idx" COLLECTION="nw41" TIDREF="i1951"
To configure the IPX protocol parameters in both the primary server and the secondary server IO Engines, complete the following stepsIDXID="w1574"BOOK="_idx" COLLECTION="nw41" TIDREF="i4117"
:PERFORMANCE="REQUIRED"If INETCFG is not already IDXID="w1575"BOOK="_idx" COLLECTION="nw41" TIDREF="i1874"IDXID="w1576"BOOK="_idx" COLLECTION="nw41" TIDREF="i4736"
running, type the following command at the server prompt:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INETCFG MOREINFO="NONE"<Enter>The 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears.
PAGENUM=199 ID="BP203"PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Protocols from the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu.The 
CLASS=MENUITEM MOREINFO="NONE"Protocols Supported window appears.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"IPX from the 
CLASS=MENUITEM MOREINFO="NONE"Protocols Supported menu.The 
CLASS=MENUITEM MOREINFO="NONE"IPX Protocol Configuration window appears.PERFORMANCE="REQUIRED"Configure the parameters as described in the 
BOOK="ipxrtenu" COLLECTION="nw41"NetWare 4.1 IPX Reference.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> until the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears.RENDERAS="SECT2"Configuring IP Protocol Parameters for the IO EngineIDXID="w1577"BOOK="_idx" COLLECTION="nw41" TIDREF="i759"IDXID="w1578"BOOK="_idx" COLLECTION="nw41" TIDREF="i1914"IDXID="w1579"BOOK="_idx" COLLECTION="nw41" TIDREF="i1897"IDXID="w1580"BOOK="_idx" COLLECTION="nw41" TIDREF="i3596"
To configure the IP protocol parameters in both the primary server and secondary server IO Engines, complete the following steps:PERFORMANCE="REQUIRED"If INETCFG is not already IDXID="w1581"BOOK="_idx" COLLECTION="nw41" TIDREF="i1874"IDXID="w1582"BOOK="_idx" COLLECTION="nw41" TIDREF="i4736"
running, type the following command at the server prompt:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INETCFG MOREINFO="NONE"<Enter>The 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Protocols from the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu.The 
CLASS=MENUITEM MOREINFO="NONE"Protocols Supported window appears.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"TCP/IP from the 
CLASS=MENUITEM MOREINFO="NONE"Protocols Supported menu.The 
CLASS=MENUITEM MOREINFO="NONE"TCP/IP Protocol Configuration window appears.
PAGENUM=200 ID="BP204"PERFORMANCE="REQUIRED"Configure the parameters described in 
IDREF="FM99462"Table 8-6. 
IDXID="w1583"BOOK="_idx" COLLECTION="nw41" TIDREF="i1914"IDXID="w1584"BOOK="_idx" COLLECTION="nw41" TIDREF="i4117"LABEL="8-6" PGWIDE=1 TOCENTRY="1"ID="FM99462"IP Protocol Parameters for SFT III IO EngineCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="9*"COLNAME=2 COLWIDTH="13*"COLNAME=3 COLWIDTH="12*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ParameterIDXID="w1585"BOOK="_idx" COLLECTION="nw41" TIDREF="i3596"IDXID="w1586"BOOK="_idx" COLLECTION="nw41" TIDREF="i3596"IDXID="w1587"BOOK="_idx" COLLECTION="nw41" TIDREF="i3596"COLNAME=2 ROTATE="0" MOREROWS="0"DescriptionCOLNAME=3 ROTATE="0" MOREROWS="0"Range/Options and DefaultVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IP Packet ForwardingCOLNAME=2 ROTATE="0" MOREROWS="0"Because the MS Engine of the SFT III server requires the IO Engine to forward its packets, forwarding is always enabled.COLNAME=3 ROTATE="0" MOREROWS="0"Enabled ("router") is the only allowed setting.COLNAME=1 ROTATE="0" MOREROWS="0"IP Address of SFT III NetworkCOLNAME=2 ROTATE="0" MOREROWS="0"Each of the IO Engines configured for IP routing in the SFT III server should have the same host address on the SFT III server's virtual network.COLNAME=3 ROTATE="0" MOREROWS="0"Any IP host address allowed on the SFT III server's virtual network.COLNAME=1 ROTATE="0" MOREROWS="0"Subnetwork Mask of SFT III NetworkCOLNAME=2 ROTATE="0" MOREROWS="0"A subnetwork mask is required to designate a separate virtual IP network for the SFT III server.COLNAME=3 ROTATE="0" MOREROWS="0"The subnetwork mask required to designate the separate IP subnetwork being used for the SFT III server's virtual network.PERFORMANCE="REQUIRED"Configure the other parameters as described in the 
BOOK="tcpipenu" COLLECTION="nw41"NetWare 4.1 TCP/IP Reference.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> until the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears.RENDERAS="SECT2"Example ConfigurationIDXID="w1588"BOOK="_idx" COLLECTION="nw41" TIDREF="i743"For IP, a typical SFT III subnetwork can be a two-node subnetwork. The primary IO Engine can be bound to both the child subnetwork and the parent network. The following example configuration is for the primary IO Engine:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD TCPIP FORWARD=NO
BIND IP MSENGINE ADDR=144.11.241 
   MASK=ff.ff.ff.fcThe following example configuration is for the MS Engine:FORMAT="LINESPECIFIC"MOREINFO="NONE"BIND IP MSENGINE ADDR=144.1.1.242 
   MASK=ff.ff.ff.fc
BIND IP NE2000 ADDR=144.1.1.1 
   MASK=ff.ff.ff.0LABEL="9"PAGENUM=201 ID="BP205"ID="FM26050"Troubleshooting OverviewThis chapter contains general troubleshooting information for NetWare® 4.1 internetworking. Before you proceed to the protocol-specific troubleshooting information in subsequent chapters, read the general suggestions and troubleshooting tips described in the first two sections of this chapter. The troubleshooting tips section will help you to identify any problems resulting from product limitations.RENDERAS="SECT1"Before Calling IDXID="w1589"BOOK="_idx" COLLECTION="nw41" TIDREF="i4461"
Technical SupportBefore you call technical support, complete the following steps:NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"Check the NetWire® section of CompuServe* for the latest patches, drivers, and application notes for the NetWare 4.1 series of products. These continually updated files are located in either Novlib section 1, 8, or 9.Read the README files and Release Notes for information about known product limitations and bugs. The README files can be viewed from the SETUP menu of the installation (they can also be printed from the INSTALL diskette).Make hard copies of these configuration/log files:STARTUP.NCF AUTOEXEC.NCFSYS:ETC\CONSOLE.LOGSYS:ETC\NETINFO.CFG           (DO NOT EDIT THIS FILE!)SYS:SYSTEM\INSTALL.LOGPAGENUM=201 ID="BP206"PAGENUM=202Examining these files should help you spot a network configuration error. Also, if you later need to call technical support, having these files printed, as well as having a network map or drawing, helps the technical support staff examine the entire configuration and the surrounding environment (most of the calls technical support receives are about configuration issues involving more than just the servers).Print the contents of the MOREINFO="NONE"CONFIG command by performing the following actions:MARK=BULLETLog in to the router from a workstation using RCONSOLE. Refer to the NetWare documentation for more information about RCONSOLE.Type MOREINFO="NONE"CONFIG, then press MOREINFO="NONE"<Enter> at the console prompt.Redirect the output to a printer by pressing MOREINFO="NONE"<Shift>+MOREINFO="NONE"<PrintScrn>.RENDERAS="SECT1"IDXID="w1590"BOOK="_idx" COLLECTION="nw41" TIDREF="i4584"
Troubleshooting TipsYou should check the following general areas to ensure that they are not the source of the problem. RENDERAS="SECT2"IDXID="w1591"BOOK="_idx" COLLECTION="nw41" TIDREF="i1848"
Interface BoardsThe following items concern problems with interface boards:MARK=BULLETUse boards that are certified by the Novell® LabsTM group.If you are using IBM* token ring boards, a shared RAM size of 16 KB is recommended. In most cases, the LAN boards can be installed with the Video Memory Addressing set to the factory default settings. However, the default settings for some boards might conflict with already installed VGA/EGA boards. To eliminate the conflict, either the VGA/EGA board or the network interface board must be reconfigured.PAGENUM=202 ID="BP207"PAGENUM=203You cannot route the IPXTM software on two different interface boards that are attached to the same routed IPX network. In the case of token ring networks, source route bridging can be used (instead of routing) to connect two or more IPX networks.If you are routing on an Ethernet board, set the maximum physical receive packet size to at least 1524 in the STARTUP.NCF file. If you are routing on a token ring board, set the value to at least 4510.Before you install a LAN board, make sure that you check all the available interrupts, I/O base address, and memory map address for all boards. To avoid conflicts with board parameter settings, verify that the same values are not being used by multiple boards. For reference, the values typically used by a PC are listed below:TYPE="VERT"COM1 uses IRQ-4, port=3F8-3FFCOM2 uses IRQ-3, port=2F8-2FFLPT1 uses IRQ-7, port=378-37FLPT2 uses IRQ-5, port=278- 27FRefer to the hardware manual for each device to determine valid settings for IRQ, I/O base, and memory locations. As you configure the links, record this information on a worksheet to avoid any conflicts. When a command is issued to unload a board driver, all instances of that driver are unloaded. For example, if two Synchronous/+ boards are loaded, an MOREINFO="NONE"UNLOAD SYNCLPUS command unloads both boards, and all calls on these boards are terminated.RENDERAS="SECT2"IDXID="w1592"BOOK="_idx" COLLECTION="nw41" TIDREF="i1820"
InstallationThe following items concern problems with product installation:PAGENUM=204 ID="BP208"MARK=BULLETFor new installations of the NetWare 4.1 product, Novell highly recommends that you choose to convert the commands in your AUTOEXEC.NCF file to INETCFG commands automatically when you are prompted to do so within INETCFG. However, if you choose to convert the AUTOEXEC.NCF file commands manually, all LOAD commands for LAN drivers and all BIND commands must be commented out within (or removed from) the AUTOEXEC.NCF file. IDREF="FM14609"Table 9-1 shows the protocol LOAD and BIND commands that must be commented out of the file.LABEL="9-1" PGWIDE=0 TOCENTRY="1"IDXID="w1593"BOOK="_idx" COLLECTION="nw41" TIDREF="i2136"ID="FM14609" LOAD and BIND Command RemovalCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ProtocolCOLNAME=2 ROTATE="0" MOREROWS="0"LOAD/BIND Commands to Comment OutVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IPXCOLNAME=2 ROTATE="0" MOREROWS="0"IPX (BIND commands only)COLNAME=1 ROTATE="0" MOREROWS="0"AppleTalkCOLNAME=2 ROTATE="0" MOREROWS="0"APPLETLKATLKSNMPCOLNAME=1 ROTATE="0" MOREROWS="0"TCP/IPCOLNAME=2 ROTATE="0" MOREROWS="0"TCPIPTCONFIGIPCONFIGCOLNAME=1 ROTATE="0" MOREROWS="0"OtherCOLNAME=2 ROTATE="0" MOREROWS="0"ROUTE (LOAD commands only)Do not remove other services from the AUTOEXEC.NCF file if they are present; for example:MARK=BULLETIDXID="w1594"BOOK="_idx" COLLECTION="nw41" TIDREF="i2860"
NFS*IDXID="w1595"BOOK="_idx" COLLECTION="nw41" TIDREF="i203"
AFP*IDXID="w1596"BOOK="_idx" COLLECTION="nw41" TIDREF="i226"
ATPSIf you plan to use the NetWare 4.1 software in combination with another Novell product, see the README file of that product for any special installation instructions required for your version of the product. The order of installation is especially important if you are using NetWare for Macintosh, IDXID="w1597"BOOK="_idx" COLLECTION="nw41" TIDREF="i2744"
NetWare for SAA*, or NetWare for NFS with the NetWare 4.1 software.RENDERAS="SECT2"IDXID="w1598"BOOK="_idx" COLLECTION="nw41" TIDREF="i3740"
Remote Access and ControlYou can configure your server to restart automatically by creating a .NCF file (located in SYS: SYSTEM) that contains these commands:FORMAT="LINESPECIFIC"MOREINFO="NONE"REMOVE DOS
DOWN
EXIT
PAGENUM=205 ID="BP209"The .NCF file is created with any text editor, and can be created remotely using RCONSOLE. To restart the server, use RCONSOLE to attach to that server and run the appropriate .NCF file. Make sure that you have the SERVER command in the AUTOEXEC.BAT file of the server.RENDERAS="SECT2"IDXID="w1599"BOOK="_idx" COLLECTION="nw41" TIDREF="i753"
Configuration The following items concern problems with product configuration:MARK=BULLETObtain the latest .LAN files and .LDI files from NetWire or your network interface board vendor. Always use INETCFG to configure the NetWare 4.1 internetworking product. INETCFG provides a series of easy-to-use menus for configuration. INETCFG automates the LOAD and BIND commands used with NetWare 3.12, NetWare 4.1, and earlier servers. INETCFG also allows you to view and, in some cases, edit (for troubleshooting purposes) the configuration information file (IDXID="w1600"BOOK="_idx" COLLECTION="nw41" TIDREF="i2669"
NETINFO.CFG), the AUTOEXEC.NCF file, and the messages generated during a system restart. Finally, INETCFG provides several layers of context-sensitive help to make the configuration process quicker and easier.Do not modify the IDXID="w1601"BOOK="_idx" COLLECTION="nw41" TIDREF="i2669"
NETINFO.CFG file found in the SYS:ETC subdirectory. Your NETINFO.CFG file contains the LOAD and BIND commands you configured with INETCFG. If you use the INSTALL utility to create an AUTOEXEC.NCF file after using INETCFG, the LOAD and BIND commands in your system memory are written to your AUTOEXEC.NCF file. Novell does not recommend this procedure because it can create duplicate entries of the LOAD and BIND commands already in your NETINFO.CFG file.If the NETINFO.CFG file is flagged READ ONLY, and if you change a field in INETCFG (for example, CLASS=MENUITEM MOREINFO="NONE"IPX Network Number under CLASS=MENUITEM MOREINFO="NONE"Bindings), INETCFG reflects the change but NETINFO.CFG does not. There can be no change to the NETINFO.CFG file because it is flagged READ ONLY. However, INETCFG gives you a warning when this occurs, reflecting the fact that the NETINFO.CFG file could not be changed. To save the change, flag INETINFO.CFG as READ/WRITE, return to INETCFG, and reenter the change.PAGENUM=206 ID="BP210"Make sure you configure the proper frame types when binding IP, IPX, and AppleTalk to a LAN interface. Note that the default frame type for IPX has been changed to Ethernet_802.2.Do not load and bind the bridge from the command line.RENDERAS="SECT1"IDXID="w1602"BOOK="_idx" COLLECTION="nw41" TIDREF="i4585"Troubleshooting ToolsFollowing are several utilities you can use to troubleshoot any problems you might have with your router. In addition to these general tools, there are also LAN protocol-specific utilities. See the "Troubleshooting Tools" section under each protocol later in this chapter for more information.RENDERAS="SECT2"IDXID="w1603"BOOK="_idx" COLLECTION="nw41" TIDREF="i775"
CONLOGCONLOG is an NLMTM utility that logs console messages in an ASCII file called CONSOLE.LOG in the SYS:ETC subdirectory on the server on which CONLOG has been loaded. You can use the CONSOLE.LOG file to check that during startup of the server, all modules have been loaded without any errors. It can be viewed from INETCFG (parameter path: Select CLASS=MENUITEM MOREINFO="NONE"View Configuration > Select CLASS=MENUITEM MOREINFO="NONE"Console Messages). RENDERAS="SECT2"IDXID="w1604"BOOK="_idx" COLLECTION="nw41" TIDREF="i2509"
MONITORMONITOR is an NLM utility that allows you to monitor various system statistics, including the following:MARK=BULLETUtilization and overall activityCache memory statusConnections and their statusLAN board driversLoaded modulesMemory usagePAGENUM=207 ID="BP211"In addition, under the CLASS=MENUITEM MOREINFO="NONE"LAN Information option of the main menu, you can find a list of all the configured network boards in the machine. If a board does not appear on that list, it indicates that it has not been initialized, probably because the settings for the board don't match the hardware settings or there is a conflict with other boards in the machine. Refer to the BOOK="sysmsenu" COLLECTION="nw41"NetWare 4.1 System Messages manual for more details about MONITOR.RENDERAS="SECT2"IDXID="w1605"BOOK="_idx" COLLECTION="nw41" TIDREF="i3739"
Remote AccessThe following tools are useful for remote troubleshooting.RENDERAS="SECT3"IDXID="w1606"BOOK="_idx" COLLECTION="nw41" TIDREF="i3674"
RCONSOLERCONSOLE allows access to a NetWare 4.1 console from an IPX workstation and turns the workstation into a virtual console.RENDERAS="SECT3"IDXID="w1607"BOOK="_idx" COLLECTION="nw41" TIDREF="i4863"
XCONSOLEXCONSOLE allows access to a NetWare 4.1 console from an IP workstation (for example, a LAN WorkPlace® for DOS workstation) and turns the workstation into a virtual console. RENDERAS="SECT2"IDXID="w1608"BOOK="_idx" COLLECTION="nw41" TIDREF="i4192"
SNMPLOGWhen loaded, SNMPLOG is an NLM utility that creates SNMP log files for trap capture. These log files can be viewed under the CLASS=MENUITEM MOREINFO="NONE"Trap Log option in the protocol console utilities (such as IDXID="w1609"BOOK="_idx" COLLECTION="nw41" TIDREF="i194"
ATCON, IDXID="w1610"BOOK="_idx" COLLECTION="nw41" TIDREF="i1929"
IPXCON, and IDXID="w1611"BOOK="_idx" COLLECTION="nw41" TIDREF="i4444"
TCPCON).RENDERAS="SECT2"IDXID="w1612"BOOK="_idx" COLLECTION="nw41" TIDREF="i2762"
NMS NetWare Management SystemTM (NMSTM) software provides a Microsoft* Windows-based SNMP management station. Its Management Information Base (MIB) Browser allows remote access of the NetWare Link/Frame Relay MIB, as well as other NetWare 4.1 MIBs.LABEL="10"PAGENUM=209 ID="BP212"ID="FM83381"Troubleshooting Network-Layer ProtocolsThis chapter contains troubleshooting information organized by Network-layer protocol. Each protocol-specific section contains information about troubleshooting tools, troubleshooting checkpoints, and common problems. Some sections also have information about troubleshooting tips.RENDERAS="SECT1"Troubleshooting AppleTalkThis section contains AppleTalk troubleshooting information that is divided into four categories: MARK=BULLETIDREF="FM49890"Troubleshooting ToolsIDREF="FM47561"Troubleshooting TipsIDREF="FM46280"Troubleshooting CheckpointsIDREF="FM56014"Common ProblemsIf the problem is general in nature, perform the procedure described under "Troubleshooting Checkpoints" to isolate and resolve the problem. When a problem with a specific symptom occurs, refer to the information listed under "Common Problems."RENDERAS="SECT2"ID="FM49890"IDXID="w1613"BOOK="_idx" COLLECTION="nw41" TIDREF="i4585"IDXID="w1614"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"Troubleshooting ToolsIDXID="w1615"BOOK="_idx" COLLECTION="nw41" TIDREF="i194"
ATCON is an NLMTM console utility for diagnosing AppleTalk network conditions and verifying connectivity. ATCON provides information about the server's AppleTalk stack and any attached AppleTalk networks. Enter MOREINFO="NONE"LOAD ATCON at the system console prompt. You can select CLASS=MENUITEM MOREINFO="NONE"View RTMP Table to display the RTMP responses the router has received from the AppleTalk network. You can also use the CLASS=MENUITEM MOREINFO="NONE"Lookup and Echo Services option to verify AppleTalk device connectivity. PAGENUM=210 ID="BP213"RENDERAS="SECT2"ID="FM47561"Troubleshooting TipsThis section lists recommendations for configuring AppleTalk:MARK=BULLETIncrease the CLASS=MENUITEM MOREINFO="NONE"Routing Update Timer period in INETCFG from the default of 10 seconds to anywhere between 60 and 300 seconds when using links below 19.2 Kbps (parameter path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings> Select a specific binding). This maximizes data throughput by minimizing the routing information packets sent through the link. By maximizing the CLASS=MENUITEM MOREINFO="NONE"Router Update Timer period, you adversely affect the amount of time a network takes to converge after a change of topology.If an internal network is configured on a NetWare for AppleTalk server, the server's Name Binding Protocol (NBP) name resides on the default zone of the internal network. If the internal network is not configured, the NetWare for AppleTalk server name resides on the default zone of the selected LAN interface bound to AppleTalk.When configuring the AppleTalk seed state in INETCFG (parameter path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select a specific binding > Select CLASS=MENUITEM MOREINFO="NONE"Network Range and Zone configuration), you must verify that there is at least one seed router on each AppleTalk network. If there are other seed routers directly connected to the same network, all the network numbers and zone names must be configured the same.RENDERAS="SECT2"ID="FM46280"IDXID="w1616"BOOK="_idx" COLLECTION="nw41" TIDREF="i4578"IDXID="w1617"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"Troubleshooting CheckpointsTo isolate and resolve AppleTalk problems, complete the following steps:PERFORMANCE="REQUIRED"ID="FM33250"Use an Echo test to determine whether the router can communicate with a particular node on one of its networks.When you execute an Echo test, the router sends a specified number of packets across the network to a specified node; the node then returns the same number of packets. If the 
CLASS=MENUITEM MOREINFO="NONE"Number of Packets Received field does not increment, the specified node might be switched off, or a cable connection might have become loose.
PAGENUM=210 ID="BP214"PAGENUM=211If an Echo test executes successfully, the number of packets received is equal, or nearly equal to the number of packets sent. If the communication is successful, AppleTalk is working on that interface, and the specified node is up and running. To execute an Echo test:PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Lookup Network Entities from the main menu of ATCON.PERFORMANCE="REQUIRED"Enter a zone name in the 
CLASS=MENUITEM MOREINFO="NONE"Name option.PERFORMANCE="REQUIRED"Select the 
CLASS=MENUITEM MOREINFO="NONE"Proceed option.PERFORMANCE="REQUIRED"Select an entity from the displayed list.PERFORMANCE="REQUIRED"Edit the following test parameters as required: 
CLASS=MENUITEM MOREINFO="NONE"Mode, Number of Packets to Send, 
CLASS=MENUITEM MOREINFO="NONE"Timeout, and 
CLASS=MENUITEM MOREINFO="NONE"Number of Data Bytes. PERFORMANCE="REQUIRED"Use an Echo test to determine whether the router can communicate with a node on a remote AppleTalk network. Use the same procedure described in 
IDREF="FM33250"Step 1.If the test is successful, the router can reach another AppleTalk network and all AppleTalk routers in between are routing correctly.If the test is not successful, execute an echo test to the closest router on the path to the remote node. Continue echo testing each router along the path until you find the closest point at which the test fails. Perform correct action on the router that fails the echo test.PERFORMANCE="REQUIRED"Check the routing table in ATCON.The 
CLASS=MENUITEM MOREINFO="NONE"Routing Table option contains entries for all networks and zones to which the router can send packets.PERFORMANCE="REQUIRED"Check the Zones list in ATCON.The 
CLASS=MENUITEM MOREINFO="NONE"Zones List option displays a global list of all AppleTalk zones in the internetwork. This list should be identical to the zones list that appears in the Macintosh Chooser. PERFORMANCE="REQUIRED"Verify that AppleTalk is bound to the interface.PERFORMANCE="REQUIRED"Check the system log file using ATCON.
PAGENUM=212 ID="BP215"PERFORMANCE="REQUIRED"Verify that the AppleTalk configuration options in INETCFG are set to the proper values.PERFORMANCE="REQUIRED"Check AppleTalk Packet Statistics using ATCON.RENDERAS="SECT2"ID="FM56014"IDXID="w1618"BOOK="_idx" COLLECTION="nw41" TIDREF="i696"IDXID="w1619"BOOK="_idx" COLLECTION="nw41" TIDREF="i187"
Common ProblemsThis section lists various symptoms of common problems and their potential solutions. The problems are categorized by the NLM files that produce them.RENDERAS="SECT3"IDXID="w1620"BOOK="_idx" COLLECTION="nw41" TIDREF="i2282"
MACIPXGW.NLMMARK=BULLETMACIPXGW fails to load and the error message MOREINFO="NONE"Failed to find zone for gateway is displayed.MARK=BULLETTry to load MACIPXGW manually from the console. If it loads, MACIPXGW was loaded before the AppleTalk stack could resolve the default zone. Delay loading MACIPXGW in your AUTOEXEC.NCF file as long as possible. You should load and bind AppleTalk first, followed by other protocols, and finally MACIPXGW.    If MACIPXGW still fails to load when you load it manually, the AppleTalk stack might be homing on an external nonseed interface, and there is no router on the network to which the interface is attached. Reconfigure AppleTalk to be a seed router on that interface, or enable the AppleTalk internal network.MACIPXGW fails to load because of an incorrect AppleTalk API version.You have incompatible APPLETLK.NLM and MACIPXGW.LAN files on your machine. Update both to the latest version.The message MOREINFO="NONE"Gateway name truncated to 32 characters is displayed.   The gateway name that you configured is more than 32 bytes long. This is not a fatal error, but you should change the gateway name to less than 32 bytes to avoid the warning message in the future.PAGENUM=213 ID="BP216"There are too many IPXTM broadcast packets encapsulated in unicast AppleTalk packets on the wire and you want to reduce the traffic. Change the CLASS=MENUITEM MOREINFO="NONE"Unicast Threshold parameter for MACIPXGW to a smaller number to force the broadcast IPX packets to be encapsulated in AppleTalk broadcast packets. RENDERAS="SECT3"IDXID="w1621"BOOK="_idx" COLLECTION="nw41" TIDREF="i4876"
Zones and Zone NamesMARK=BULLETReconfigured zones are still visible in the client's Chooser or in the router's zone tables.This problem results from the way in which AppleTalk maintains routing tables and zone information on the internetwork. Routers are not informed automatically about changes in zone configuration.MARK=BULLETIf this problem is occurring at your site and the reconfigured router is the only router directly connected to the network supporting new zones, bring down the router and let it stay off the network for at least 20 minutes (or until the changed routes are aged out from the internetwork). When you bring up the router again, the new zones will be in effect.If more than one router is connected to the network supporting new zones, all of them must be reconfigured to support the same zones. Bring down all the routers, reconfigure the zones, and leave them down for at least 20 minutes (or until the changed routes are aged out from the internetwork). When you bring up the routers, the new zones will be in effect. If the zones are supporting more than one network and you want to change the zones for all or some of those networks, you must bring down the routers connected to each of the network on which you want to change the zones. Reconfigure the zones and leave them down for at least 20 minutes (or until the changed routes are aged out from the internetwork).PAGENUM=213 ID="BP217"PAGENUM=214Zone names do not match configured zone names.MARK=BULLETIf additional zone names show up in the Chooser or ATCON after you have brought up a router on an AppleTalk network, verify that you typed the same zone names in different configuration files using the same case. Zone names are case-sensitive and variations in case in the same words result in different zone names.  Verify that there are no trailing blanks in zone names. A network number or network range has a different zone list on different routers after the zone list of the network was changed on the seed router.    The seed router was brought before the network was aged out from all the routers. Bring down the seed router and the directly connected routers, and wait for the network to age out all the routers. Ten to 20 minutes is recommended, depending on the size of your AppleTalk internetwork. Allow one minute per hop. If the farthest router is 11 hops away from the seed router where you changed the network, you should wait at least 11 minutes before restarting the seed router and directly connected routers.RENDERAS="SECT3"IDXID="w1622"BOOK="_idx" COLLECTION="nw41" TIDREF="i802"
Console MessagesMARK=BULLETThe console displays messages about mismatched network numbers or mismatched zones.RENDERAS="SECT4"General SolutionsMARK=BULLETVerify that the network number or range is unique on the internetwork.Verify that all routers on the cable agree about the network number or range.Verify that the network's Zones list has the same names, and that all routers agree about that name.PAGENUM=214 ID="BP218"PAGENUM=215RENDERAS="SECT4"Solutions for Extended NetworksMARK=BULLETVerify that the extended network range of the router in Transition Mode has a network range of one (such as 21-21).Verify that the extended network range is unique on the internetwork.Verify that all routers on the cable agree about the network range.Verify that all routers on the cable agree about the zone names.RENDERAS="SECT3"IDXID="w1623"BOOK="_idx" COLLECTION="nw41" TIDREF="i467"
Binding ProblemsMARK=BULLETAppleTalk does not successfully bind to a seed interface.Because the NetWare 4.1® AppleTalk software does soft seeding, AppleTalk verifies the configured seeding information with the current network configuration from the other routers on that network. If the seeding information is inconsistent with the current configuration of the network, it indicates that there is a misconfiguration, and AppleTalk does not allow the interface to come up. Check the interface's configuration to verify that the network number/range and zone names are configured exactly the same as all other seed routers connected to the same network.AppleTalk fails to bind to an interface and the message MOREINFO="NONE"Error binding APPLETALK to board board_name is displayed. This occurs when the driver was not initialized fully when AppleTalk was bound to it the first time. This can happen when the MOREINFO="NONE"LOAD driver command is right above the command for binding AppleTalk to the driver in a batch file such as AUTOEXEC.NCF. To fix this problem, use INETCFG to configure the board and AppleTalk, or manually move the MOREINFO="NONE"LOAD driver line to above the MOREINFO="NONE"LOAD MOREINFO="NONE"APPLETLK line to give more time to the board to complete initialization.PAGENUM=215 ID="BP219"PAGENUM=216RENDERAS="SECT3"IDXID="w1624"BOOK="_idx" COLLECTION="nw41" TIDREF="i3539"
Printing and Services ProblemsMARK=BULLETAppleTalk clients cannot see the services provided on the NetWare server from the Chooser, and the server does not respond to ARP requests. The LAN driver does not support multicast correctly. Use a different LAN driver.AppleTalk clients cannot see the services provided on the NetWare server from the Chooser. Load ATCON from the NetWare server console, then select CLASS=MENUITEM MOREINFO="NONE"Protocol Configuration. If the status of the stack is CLASS=MENUITEM MOREINFO="NONE"Disabled and the    AppleTalk router has no internal network configured, you might have forgotten to select a LAN interface to provide application support when you bound AppleTalk to the LAN interface.There are differences in the routing tables between routers.Routing tables between AppleTalk routers can be different. Check CLASS=MENUITEM MOREINFO="NONE"Static Routes for On-demand Calls in INETCFG (parameter path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols), routing filters among the routers, and the AURP peer list.RENDERAS="SECT1"IDXID="w1625"BOOK="_idx" COLLECTION="nw41" TIDREF="i4577"IDXID="w1626"BOOK="_idx" COLLECTION="nw41" TIDREF="i1906"
Troubleshooting IPThis section contains IP troubleshooting information that is divided into three categories: MARK=BULLETIDREF="FM22073"Troubleshooting Tools IDREF="FM13708"Troubleshooting CheckpointsIDREF="FM78960"Common ProblemsIf the problem is general in nature, perform the procedure described under "Troubleshooting Checkpoints" to isolate and resolve the problem. When a problem with a specific symptom occurs, refer to the information listed under "Common Problems."PAGENUM=217 ID="BP220"RENDERAS="SECT2"ID="FM22073"IDXID="w1627"BOOK="_idx" COLLECTION="nw41" TIDREF="i4585"IDXID="w1628"BOOK="_idx" COLLECTION="nw41" TIDREF="i1906"Troubleshooting ToolsIDXID="w1629"BOOK="_idx" COLLECTION="nw41" TIDREF="i4444"
TCPCON is an NLM utility that provides access to statistics and information about the status of various components if the TCP/IP protocol suite. TCPCON uses SNMP to access this information from any local or remote system on the network. TCPCON operates over TCP/IP and IPX networks. Enter MOREINFO="NONE"LOAD TCPCON at the system console prompt. To monitor a remote system, select the CLASS=MENUITEM MOREINFO="NONE"Change Host option and input the IP address of the remote host you want to test. If details from that remote host are displayed, the remote host is alive and functioning. You can use IPXCON to perform the following tasks:MARK=BULLETMonitor activity in the TCP/IP network segments of your internetworkDisplay configuration information and statistics about the following TCP/IP protocols---IP, ICMP, UDP, TCP, OSPF, and EGPDisplay the IP routes currently known to a TCP/IP nodeDisplay the network interfaces supported by a TCP/IP nodeAccess the trap log maintained by SNMPLOG (for local systems only)Access TCP/IP information in any remote protocol stack supporting the TCP/IP Management Information Base (MIB)TCPCON requires SNMP to be loaded on the remote host; otherwise, you receive an error message that the host is unavailable. Another cause of the MOREINFO="NONE"Host unavailable message might be a routing error. You can check the routing table of the by accepting the default value of 127.0.0.1 in the CLASS=MENUITEM MOREINFO="NONE"Change Host option. Select CLASS=MENUITEM MOREINFO="NONE"Routing Table to view the routing information table that the NetWare 4.1 software has received from routing protocols (RIP and OSPF) or Static routes. Compare this to the address topology of the network. See the BOOK="tcpipenu" COLLECTION="nw41"NetWare 4.1 TCP/IP Reference for more information.PAGENUM=217 ID="BP221"PAGENUM=218RENDERAS="SECT2"ID="FM13708"IDXID="w1630"BOOK="_idx" COLLECTION="nw41" TIDREF="i4578"IDXID="w1631"BOOK="_idx" COLLECTION="nw41" TIDREF="i1906"Troubleshooting CheckpointsTo isolate and resolve TCP/IP problems, complete the following steps:PERFORMANCE="REQUIRED"Use TCPCON to verify that IP packets are being sent and received.PERFORMANCE="REQUIRED"Verify that IP 
CLASS=MENUITEM MOREINFO="NONE"Status is set to 
CLASS=MENUITEM MOREINFO="NONE"Packet Forwarding.PERFORMANCE="REQUIRED"Use PING or TPING to test connectivity.PERFORMANCE="REQUIRED"Verify that static routing is configured if other third-party routers that do not use RIP or OSPF are connected on the network.PERFORMANCE="REQUIRED"Use TCPCON to verify that the IP address and subnetwork mask you choose while configuring the router matches the configuration of your internetwork.PERFORMANCE="REQUIRED"Verify that all client software has the 
CLASS=MENUITEM MOREINFO="NONE"Default Router option configured to match the IP address of the network board inside the router that is connected to the local segment. If you are using the Novell® LAN WorkPlace® for DOS product, the 
CLASS=MENUITEM MOREINFO="NONE"IP_ROUTER option in the NET.CFG file sets this parameter.PERFORMANCE="REQUIRED"Check TCPCON for the following 
IDXID="w1632"BOOK="_idx" COLLECTION="nw41" TIDREF="i1917"
IP statistics:
MARK=BULLETLocal errors (memory error)IP errors (unexpected protocol errors)  IP address errors (misdirected packets) Unknown protocol errors (unsupported IP clients) No route found (router failure)PERFORMANCE="REQUIRED"Check TCPCON for the following 
IDXID="w1633"BOOK="_idx" COLLECTION="nw41" TIDREF="i1748"
ICMP statistics: 
MARK=BULLETDestination unreachable (network failure) Time exceeded (network failure)  Redirects (router failure)PERFORMANCE="REQUIRED"Use INETCFG to view all configuration commands and configuration options
PAGENUM=219 ID="BP222"RENDERAS="SECT2"ID="FM78960"Common ProblemsIDXID="w1634"BOOK="_idx" COLLECTION="nw41" TIDREF="i696"IDXID="w1635"BOOK="_idx" COLLECTION="nw41" TIDREF="i1906"This section lists various symptoms of common problems and their potential solutions:RENDERAS="SECT3"Problems with IDXID="w1636"BOOK="_idx" COLLECTION="nw41" TIDREF="i1911"IDXID="w1637"BOOK="_idx" COLLECTION="nw41" TIDREF="i2030"
LAN ConnectivityMARK=BULLETThe router does not forward IP packets. Verify that the CLASS=MENUITEM MOREINFO="NONE"IP Packet Forwarding statistic is set to CLASS=MENUITEM MOREINFO="NONE"Router in TCPCON (parameter path: Select CLASS=MENUITEM MOREINFO="NONE"Protocol Information > SelectCLASS=MENUITEM MOREINFO="NONE" IP). If it is not enabled, unload TCPIP.NLM and reload it with the CLASS=MENUITEM MOREINFO="NONE"forward=yes parameter from the command line. Forwarding can also be enabled in INETCFG under CLASS=MENUITEM MOREINFO="NONE"Protocols; then unload TCPIP.NLM and issue the MOREINFO="NONE"REINITIALIZE SYSTEM command.A TCP/IP host cannot reach the server on the local network.MARK=BULLETVerify that the server and host use the same frame type.Verify that the network portion of the IP address and the subnet mask are the same on the server and the host.PING the TCP/IP host from the server and verify that the Address Translation table has an entry for the host. If there is no entry, use MONITOR to check the status of the LAN driver.PING the TCP/IP host from the server and check for CLASS=MENUITEM MOREINFO="NONE"Echo Requests in TCPCON (parameter path: Select CLASS=MENUITEM MOREINFO="NONE"Statistics > Select CLASS=MENUITEM MOREINFO="NONE"ICMP). If it is not incrementing, check the IP statistics for errors.PING the TCP/IP host from the server and check for CLASS=MENUITEM MOREINFO="NONE"Echo Replies in TCPCON (parameter path: Select CLASS=MENUITEM MOREINFO="NONE"Statistics > Select CLASS=MENUITEM MOREINFO="NONE"ICMP). If it is not incrementing, check the IP statistics for errors.A TCP/IP host cannot reach a remote host. MARK=BULLETVerify that the local TCP/IP host has the local router listed as the default router.Using PING, verify that the local TCP/IP host can reach each router on the path to the remote host.Verify that each router has a routing protocol enabled, and that it has not been disabled on the interface.PAGENUM=220 ID="BP223"Starting at the local router, verify that each router has a route to the remote host's network.Verify that there are no filters configured on any routers along the path that would block IP traffic.Verify that the remote host has a route to the local host's network.Using PING, verify that the remote host can reach each router on the path to the local TCP/IP host.Starting at the router closest to the remote host, verify that each router has a route to the local TCP/IP host's network.The server cannot initiate IP traffic to a remote router through a LAN interface.MARK=BULLETVerify that IP is bound to the right interface with the right address and mask. Check whether the interface driver is loaded with the right frame type. Check whether a route exists to the network on which the destination router resides. This can be done through the CLASS=MENUITEM MOREINFO="NONE"IP Routing Table menu of TCPCON. If the destination router is accessible, also verify that it has a route to the source router's network.RENDERAS="SECT3"Problems with IDXID="w1638"BOOK="_idx" COLLECTION="nw41" TIDREF="i1916"IDXID="w1639"BOOK="_idx" COLLECTION="nw41" TIDREF="i3914"
Routing Table MaintenanceMARK=BULLETRoutes are not exchanged on a LAN. MARK=BULLETVerify that the IP CLASS=MENUITEM MOREINFO="NONE"Status is set to CLASS=MENUITEM MOREINFO="NONE"Packet Forwarding.Verify that a routing protocol has been enabled.Verify that the routing protocol has not been disabled on an interface.Verify that the broadcast address is correct.Use TCPCON to examine the routing table to determine which routes are missing.Check TCPCON for IP errors.PAGENUM=221 ID="BP224"Check TCPCON for ICMP errors.If you are using RIP, verify that the CLASS=MENUITEM MOREINFO="NONE"RIP Mode option is not set to CLASS=MENUITEM MOREINFO="NONE"Send Only.If the CLASS=MENUITEM MOREINFO="NONE"RIP Mode option is set to CLASS=MENUITEM MOREINFO="NONE"RIP II, verify that the other routers also support RIP II.Verify that no route filters are configured that would block route information packets for that interface.If you are using OSPF, verify the following: Routers in the area have the same CLASS=MENUITEM MOREINFO="NONE"Authentication Type configured. All routers on the same network have the same CLASS=MENUITEM MOREINFO="NONE"Authentication Password configured for the interface to the network.All routers on the same network have the same CLASS=MENUITEM MOREINFO="NONE"Hello Intervals configured for the interface to the network.The state of each neighbor is either two-way or full in TCPCON (parameter path: Select CLASS=MENUITEM MOREINFO="NONE"Protocol Information > Select CLASS=MENUITEM MOREINFO="NONE"OSPF > Select CLASS=MENUITEM MOREINFO="NONE"Neighbors). In TCOCON, there is a router link state advertisement for each router in your area. (parameter path: Select CLASS=MENUITEM MOREINFO="NONE"Protocol Information > Select CLASS=MENUITEM MOREINFO="NONE"OSPF > Select CLASS=MENUITEM MOREINFO="NONE"Link State Advertisements).In TCPCON, the number of link state advertisements, Area Boundary Routers, and Autonomous System Boundary Routers are the same for each router in your area (parameter path: Select CLASS=MENUITEM MOREINFO="NONE"Protocol Information > Select CLASS=MENUITEM MOREINFO="NONE"OSPF > Select CLASS=MENUITEM MOREINFO="NONE"Areas).Specific link state advertisements received by each router in your area have the same checksum.RIP routes are not accessible to hosts on OSPF networks. MARK=BULLETCheck the status of the Autonomous System Boundary Router statistic in TCPCON (parameter path: Select CLASS=MENUITEM MOREINFO="NONE"Protocol Information > Select CLASS=MENUITEM MOREINFO="NONE"OSPF).Verify that no filters are configured that would block access to the network.PAGENUM=222 ID="BP225"RENDERAS="SECT1"IDXID="w1640"BOOK="_idx" COLLECTION="nw41" TIDREF="i4577"IDXID="w1641"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"
Troubleshooting IPXThis section contains IPX troubleshooting information that is divided into three categories: MARK=BULLETIDREF="FM23801"Troubleshooting ToolsIDREF="FM91078"Troubleshooting CheckpointsIDREF="FM86394"Common Problems If the problem is general in nature, perform the procedure described under "Troubleshooting Checkpoints" to isolate and resolve the problem. When a problem with a specific symptom occurs, refer to the information listed under "Common Problems."RENDERAS="SECT2"ID="FM23801"Troubleshooting ToolsIDXID="w1642"BOOK="_idx" COLLECTION="nw41" TIDREF="i4585"IDXID="w1643"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"The two IPX-specific troubleshooting tools are explained below.RENDERAS="SECT3"IDXID="w1644"BOOK="_idx" COLLECTION="nw41" TIDREF="i1929"
IPXCONIPXCON is an NLM utility that provides access to statistics and information about the status of various components of the IPX protocol. IPXCON uses SNMP to access this information from any local or remote system on the network. IPXCON operates over both IPX and TCP/IP networks and uses UDP to run over either IPX or TCP/IP networks. Enter MOREINFO="NONE"LOAD IPXCON at the system console prompt. You can use IPXCON to perform the following tasks:MARK=BULLETMonitor and troubleshoot IPX routes and network segments throughout your IPX internetworkDisplay the status of any IPX router or network segment on your internetworkDisplay all paths through which IPX packets can flowLocate all active IPX routers on your internetworkDisplay operational circuits for IPXMonitor remote routers running NetWare IPX RouterTM softwarePAGENUM=223 ID="BP226"RENDERAS="SECT2"ID="FM91078"Troubleshooting CheckpointsObserve the following procedures when configuring IPX for NetWare 4.1.RENDERAS="SECT3"IDXID="w1645"BOOK="_idx" COLLECTION="nw41" TIDREF="i4578"IDXID="w1646"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"
IPX CheckpointsTo isolate and resolve problems with IPX, complete the following steps:PERFORMANCE="REQUIRED"Verify that workstations can connect to all desired servers.If there is a problem with LAN connectivity, see 
IDREF="FM36382""Problems with LAN Connectivity."PERFORMANCE="REQUIRED"Verify that all servers and routers on the same LAN segment have unique internal network numbers. In addition, servers and routers on the same network segment must have the same IPX network number.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Look at the routing table in IPXCON on any NetWare Link Services ProtocolTM (NLSPTM) system in the suspected area (parameter path: 
CLASS=MENUITEM MOREINFO="NONE"NLSP Information > 
CLASS=MENUITEM MOREINFO="NONE"Routers). Determine whether there are routers that are listed and then not listed (these routers might become unreachable for brief periods of time, too). You should then make a remote connection with RCONSOLE, and check whether the message described above is occurring.PERFORMANCE="REQUIRED"Enable SAP on one of the interfaces in a router in the NLSP area. Between SAP periodic updates you should see two routers (or more if more than one router shares the internal network number) being listed as unreachable and then reachable. This should occur every 5 to 10 seconds. PERFORMANCE="REQUIRED"Once you have identified the NLSP systems with the problem, use IPXCON to determine which networks the servers or routers are connected to, should the names of the routers or servers not suffice. To do this, enter IPXCON, select 
CLASS=MENUITEM MOREINFO="NONE"NLSP information, and then select 
CLASS=MENUITEM MOREINFO="NONE"RoutersPAGENUM=224 ID="BP227". Find the offending router (you might need to enter the screen several times), and then quickly select the router. You might need to select the router several times, because its connectivity is intermittent.If the router is a NetWare router, then the internal network number is probably a duplicate. You should change one of the router's internal network numbers and restart the system.RENDERAS="SECT4"ID="FM36382"Problems with LAN ConnectivityTo isolate and resolve problems with LAN connectivity, complete the following steps:PERFORMANCE="REQUIRED"Find the server or router that is connecting the workstation to the network. If there are more than one, then you need to look at each system to determine if it has proper connectivity. If the system with which you are communicating is a server, then use that system.You should identify at least two servers or routers. PERFORMANCE="REQUIRED"Check the forwarding table on both systems:PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"If you are on the server/router representing network A, then find network B in the forwarding table. PERFORMANCE="REQUIRED"If the network does not exist, then exit and enter the forwarding table several times, until it does show up. PERFORMANCE="REQUIRED"If it doesn't show up, then it is likely that a router in the path is either malfunctioning or has a duplicate system ID. PERFORMANCE="REQUIRED"If the route shows up intermittently, then there is probably a duplicate system ID. PERFORMANCE="REQUIRED"If the route shows up consistently, then take a look at the route, and select potential paths.PERFORMANCE="REQUIRED"Make sure that the potential path leads to the correct network by looking at the intermediate routers.If there is a duplicate network number, you can determine the location of the duplicate from this window:PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"If everything still seems OK, then write down all the LANs and routers in the path. 
PAGENUM=225 ID="BP228"PERFORMANCE="REQUIRED"Use IPX PING to check all routers/servers in the end-to-end path (you need to do this from one side only). Also, check the end points. That is, if connectivity is occurring from a workstation, make sure that the workstation can log in to the first server or router in the path, or that it can get through the router in question. If your connectivity loss is temporary only (for example, you occasionally get abort retries on the workstation), then let the IPX PING run for a period of time. Check for packet loss during this time, then examine the router at which packet loss occurred.It is also possible that you have a malfunctioning router in the end-to-end path. Usually, IPX PING can help you to determine where the fault is occurring. PERFORMANCE="REQUIRED"Once you have found the router that has the problem, check its potential paths. All downstream routes from the first router to it should also be potential paths on this router. If this is not the case and the router does not quickly acquire the downstream routes, then the system probably has a software error in it. Contact the router manufacturer's technical support for further assistance. To help minimize problems like this, you should purchase only NLSP-certified routers.PERFORMANCE="REQUIRED"If you have connectivity loss outside of an NLSP area, check each router in the end-to-end path for an external RIP route.RIP is used between NLSP areas. Because of this, it is necessary to check the end-to-end path in a more tedious way:PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Find the next hop router from each of the servers. PERFORMANCE="REQUIRED"Look at that system's forwarding database. PERFORMANCE="REQUIRED"Find the next hop router from that system, and so on, until you have found where the route leads. Do the same from the other side as well.
PAGENUM=226 ID="BP229"This is difficult with the current implementation of RIP and SNMP for Novell implementations, because RIP just shows the next hop LAN and NIC address (over LANs) instead of the internal network number of the system. SNMP cannot receive packets that are addressed to a NIC; they must be addressed to the internal network number. You need to work backward, first finding all routers attached to the LAN, and then finding the receiving LAN card on that router. This should be the next hop router. Repeat these steps until you find the destination network number. If you do not find a duplicate network number in either direction, then check each link in the path for errors.RENDERAS="SECT3"IDXID="w1647"BOOK="_idx" COLLECTION="nw41" TIDREF="i4578"IDXID="w1648"BOOK="_idx" COLLECTION="nw41" TIDREF="i2927"
NLSP CheckpointsTo isolate and resolve problems with NLSP, complete the following steps:PERFORMANCE="REQUIRED"Determine connectivity.MARK=BULLETVerify that all neighbors are displayed under the NLSP CLASS=MENUITEM MOREINFO="NONE"Neighbors option in IPXCON to determine whether there is local connectivity.Verify that there are sufficient potential paths within each area.Verify that all LANs are present in the NLSP CLASS=MENUITEM MOREINFO="NONE"LANs table in IPXCON.Verify that all NLSP routers are in the NLSP CLASS=MENUITEM MOREINFO="NONE"Routers table in IPXCON.PERFORMANCE="REQUIRED"Determine whether RIP is active.
MARK=BULLETVerify that the NLSPCLASS=MENUITEM MOREINFO="NONE" LANs screen indicates whether RIP packets are being absorbed.Verify that the CLASS=MENUITEM MOREINFO="NONE"Circuits table indicates the state of any particular system.PAGENUM=226 ID="BP230"PAGENUM=227RENDERAS="SECT2"ID="FM86394"Common ProblemsIDXID="w1649"BOOK="_idx" COLLECTION="nw41" TIDREF="i696"IDXID="w1650"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"IDXID="w1651"BOOK="_idx" COLLECTION="nw41" TIDREF="i2927"This section lists various symptoms of common problems and their potential solutions.RENDERAS="SECT3"IPXCON Counters Are IncreasingMARK=BULLETThe CLASS=MENUITEM MOREINFO="NONE"LSPs Received counter in IPXCON is increasing (parameter path: Select CLASS=MENUITEM MOREINFO="NONE"NLSP Information > Select CLASS=MENUITEM MOREINFO="NONE"System Information > Select CLASS=MENUITEM MOREINFO="NONE"Detailed NLSP System Information).A NetWare server or router has a conflicting internal network number and both systems are in the same NLSP area, resulting in a duplicate NLSP system ID. A number of activities occur when this happens. If router A and router B have the same system ID, both routers attempt to assert that they own the system ID in question. First, router A issues Link State Packets (LSPs) that supersede router B's LSPs and purge any LSPs of router B`s that it does not have. Then, router B does the same to router A. It is possible that this increases the amount of LSP traffic in the network considerably, particularly if either router A or router B has many LSPs; for example, if one is importing many routes and services. Change the internal network of one of the conflicting systems, or remove one of the systems from the network immediately. For information about how to find the offending node, see IDREF="FM36382""Problems with LAN Connectivity."The CLASS=MENUITEM MOREINFO="NONE"Sequence Number Skips counter in IPXCON is increasing on both routers (parameter path: Select CLASS=MENUITEM MOREINFO="NONE"NLSP Information > Select CLASS=MENUITEM MOREINFO="NONE"System Information > Select CLASS=MENUITEM MOREINFO="NONE"Detailed NLSP System Information). It is normal for a system to have some sequence number skips, but the number of CLASS=MENUITEM MOREINFO="NONE"Sequence Number Skips should not increase after the first five minutes of a router's operation unless there is a duplicate NLSP system ID. Change the internal network of one of the conflicting systems, or remove one of the systems from the network immediately. For information about how to find the offending node, see IDREF="FM36382""Problems with LAN Connectivity."PAGENUM=227 ID="BP231"PAGENUM=228The CLASS=MENUITEM MOREINFO="NONE"Own LSP Purges counter in IPXCON (parameter path: Select CLASS=MENUITEM MOREINFO="NONE"NLSP Information > Select CLASS=MENUITEM MOREINFO="NONE"System Information > Select CLASS=MENUITEM MOREINFO="NONE"Detailed NLSP System Information) is increasing on both routers. There is a duplicate NLSP system ID, and many systems have fluctuating counts of routes and services, because those services available through one or the other router become unreachable. If one of the systems in question can route, then all systems in the network are running the NLSP decision process frequently. Change the internal network of one of the conflicting systems, or remove one of the systems from the network immediately. For information about how to find the offending node, see IDREF="FM36382""Problems with LAN Connectivity."RENDERAS="SECT3"Error Messages Are DisplayedMARK=BULLETThe console displays the message MOREINFO="NONE"System server_nameMOREINFO="NONE" with internal network number numberMOREINFO="NONE" has my system ID in it.A duplicate internal network number has resulted in a duplicate system ID. Change the internal network of one of the conflicting systems, or remove one of the systems from the network immediately. For information about how to find the offending node, see IDREF="FM36382""Problems with LAN Connectivity."The console displays the messageMOREINFO="NONE" LSP graph/link state database inconsistency, NLSP will be reset.Cause 1---Errant application is corrupting the NLSP graph or LSP database.Contact technical support.Cause 2---NLSP has a software error that is either corrupting the graph or causing the graph to be represented incorrectly.Contact technical support.PAGENUM=228 ID="BP232"PAGENUM=229RENDERAS="SECT3"NLSP Decision Process Is Running FrequentlyMARK=BULLETThe NLSP decision process is running frequently. To observe this symptom, obtain access to a NetWare server or router running NLSP in the network and enter the MOREINFO="NONE"SET ISUL DEBUG=256 command at the system console. Every time the decision process runs, an entry is displayed at the system console. If the decision process runs at least every 30 seconds, there might be a duplicate system ID.Change the internal network of one of the conflicting systems, or remove one of the systems from the network immediately. For information about how to find the offending node, see IDREF="FM36382""Problems with LAN Connectivity."RENDERAS="SECT3"System Frequently Appears and Disappears on the LANMARK=BULLETA system frequently appears and disappears on the LAN.Cause 1---System is not transmitting its packets to the Designated Router properly.MARK=BULLETAt the Designated Router, check the CLASS=MENUITEM MOREINFO="NONE"Neighbor State Changes option in IPXCON (parameter path: Select CLASS=MENUITEM MOREINFO="NONE"Circuits > Select a specific circuit > Select CLASS=MENUITEM MOREINFO="NONE"Detailed Circuit Information) and monitor it for the circuit (LAN). If the number is increasing but there are no new systems on the network and systems are not being bound and unbound or restarted, then it is likely that there is a local connectivity problem.Once you have determined that there is a local connectivity problem, check whether there are any systems in the CLASS=MENUITEM MOREINFO="NONE"Initializing state (parameter path: Select CLASS=MENUITEM MOREINFO="NONE"NLSP Information > Select CLASS=MENUITEM MOREINFO="NONE"Neighbors). You might need to exit and enter the CLASS=MENUITEM MOREINFO="NONE"Neighbors menu several times over several minutes. Also check for any systems that do not have a name associated with them. Any system without a name has not transmitted its LSP to the Designated Router.PAGENUM=229 ID="BP233"PAGENUM=230If you find any systems that enter the CLASS=MENUITEM MOREINFO="NONE"Initializing state, then you have identified a connectivity problem between that system and the Designated Router. If you have not identified any such systems, then it is still possible for a router to lose connectivity occasionally. Select the entry in the NLSP CLASS=MENUITEM MOREINFO="NONE"Neighbor table of the router that does not have connectivity (parameter path: Select CLASS=MENUITEM MOREINFO="NONE"NLSP Information > Select CLASS=MENUITEM MOREINFO="NONE"Neighbors). There is a holding timer for the system. By default, every system sends a Hello packet on a LAN every 15 to 20 seconds. You can see whether the Designated Router is getting all the Hello packets from the system.If you still cannot determine the problem with the system, then load IPX PING. Set the PING send rate to zero and check to determine whether packets are being dropped. A packet dropped every once in a while is not bad, but dropping over one percent of packets indicates a problem with the router or server.Also check connectivity between the Designated Router and another system. It might be that the Designated Router is dropping packets or has the problem.Cause 2---Problem with the underlying media. Look at the interface in MONITOR and check for errors. Errors are specific to the media, so you need to understand what different errors mean. It might be a problem with the server's or router's network interface board. This could be a software or hardware error.Cause 3---System misconfiguration. By default, NLSP timers are set so that it takes three dropped packets before a system becomes unreachable. Look at the system's configuration to ensure that this is the case.Cause 4---One or both of the systems are dropping packets. Check the interface boards to determine whether packets are being dropped due to insufficient Event Control Blocks (ECBs). Increasing the maximum number of physical receive packets might help stop the system from dropping packets. However, it might be that the system is incapable of handling the system load. In this case, you should increase the processor power of the system that is dropping packets, or reduce the load on the server by removing NLM files or by decreasing the number of users on the system. You can determine whether the system is using too much CPU by looking at MONITOR.PAGENUM=231 ID="BP234"Cause 5---NLM on the server is not relinquishing control of the CPU frequently enough. This is a rare occurrence, but you can determine whether this is the case by selecting CLASS=MENUITEM MOREINFO="NONE"Performance in MONITOR (in NetWare 3.11 you need to load MONITOR with the CLASS=MENUITEM MOREINFO="NONE"/p option) and seeking processes that exceed many millions of cycles per iteration. You can also determine that an NLM is malfunctioning by removing the NLM from the server and determining whether the problem goes away.Cause 6---Internal error in NLSP. If you have exhausted all other possibilities, you should write down your system configuration, number of users, and error frequency, and send a copy of the system configuration, including the NLSP configuration file (usually located in /ETC/NLSP.CFG), to technical support.RENDERAS="SECT3"ID="FM81062"Multiple Systems on a LAN Become Unreachable IntermittentlyMARK=BULLETIf multiple systems become unreachable intermittently on a LAN, there might be a problem with the Designated Router. Cause 1---Designated Router does not have enough system memory to represent the LAN. You can determine whether this is the case by checking whether the Designated Router is overloaded when the problem occurs or whether it has been overloaded in the past. Check the CLASS=MENUITEM MOREINFO="NONE"Level 1 Data Base Overloads statistic in IPXCON (parameter path: Select CLASS=MENUITEM MOREINFO="NONE"NLSP Information > Select CLASS=MENUITEM MOREINFO="NONE"System Information > Select CLASS=MENUITEM MOREINFO="NONE"Detailed NLSP System Information). If the Designated Router does not have sufficient memory to represent the LAN, then the LAN loses connectivity as new systems are added. You should select another system on the network to become the Designated Router by increasing its priority in INETCFG and entering MOREINFO="NONE"REINITIALIZE SYSTEM at the command line. In addition, you should add memory to the system that was overloaded. You might also want to check whether other systems in the network are overloaded. See IDREF="FM30910""Many Systems Are Entering an Overloaded State."Cause 2---Designated Router or some other system on the LAN is causing the network outage. Another system can cause this problem by electing itself as the Designated Router on the LAN. PAGENUM=232 ID="BP235"A single malfunctioning system on a LAN might be causing all systems on the LAN to become reachable and unreachable. Using IPXCON, check the CLASS=MENUITEM MOREINFO="NONE"Designated Router Changes counter for all systems on the LAN (parameter path: Select CLASS=MENUITEM MOREINFO="NONE"Circuits > Select a specific circuit > Select CLASS=MENUITEM MOREINFO="NONE"Detailed Circuit Information). If a single system has many CLASS=MENUITEM MOREINFO="NONE"Designated Router Changes, it is very likely that the system has connectivity problems with other systems on the LAN. Check whether the counter increases over time. If the Designated Router is not being restarted or unbound from a LAN, the counter should not increase. If all systems on the LAN are having their CLASS=MENUITEM MOREINFO="NONE"Designated Router Changes counter increasing, it is likely that the system that should be Designated Router has a connectivity problem. Remove the system from the LAN or decrease its Designated Router priority to determine whether it is a problem particular to the system or to the network itself. Cause 3---Two systems are contending to be Designated Router for the LAN. If this is the case, the CLASS=MENUITEM MOREINFO="NONE"Own LSP Purges counter increases (parameter path: Select CLASS=MENUITEM MOREINFO="NONE"NLSP Information > Select CLASS=MENUITEM MOREINFO="NONE"System Information > Select CLASS=MENUITEM MOREINFO="NONE"Detailed NLSP System Information). However, unless you are using ARCNET* or some other media that does not have IEEE addresses, only one system has the highest priority on the LAN (the MAC address is used as a tie breaker and IEEE addresses are unique).Cause 4---Each system might have one of the problems described above.See the solutions described previously.RENDERAS="SECT3"Cannot Access a Server on a LANMARK=BULLETYou cannot access a server on the LAN.Cause 1---Area address is set to the wrong value.In this case, the number of destinations (known networks) implies local connectivity only. This is also true of the number of services. Also, the CLASS=MENUITEM MOREINFO="NONE"Initialization Failures statistic in IPXCON increases (parameter path: Select CLASS=MENUITEM MOREINFO="NONE"Circuits > Select CLASS=MENUITEM MOREINFO="NONE"Detailed Circuit Information). If you have configured area addresses, make sure that all systems that should be in communications have the same area addresses. It is acceptable for them to have different addresses, if that is the desired configuration. PAGENUM=233 ID="BP236"Cause 2---RIP is not enabled.If you are running multiple areas on a LAN and you are using RIP to interconnect the systems, verify that RIP is enabled. If the CLASS=MENUITEM MOREINFO="NONE"RIP State is set to CLASS=MENUITEM MOREINFO="NONE"Auto in INETCFG, there is a small chance that RIP will fail.Cause 3---LAN is partitioned due to a failed hub or bridge. Check whether there is data-link connectivity by using IPX PING.Cause 4---LAN board has failed. This system does not see other systems on a LAN, or it does not have any adjacencies in the CLASS=MENUITEM MOREINFO="NONE"Up state. However, it declares itself as being attached to the LAN. In IPXCON, look for a system that is in the CLASS=MENUITEM MOREINFO="NONE"Initializing state. If a system on the LAN appears in the CLASS=MENUITEM MOREINFO="NONE"Initializing state on all other systems but has no neighbors itself, then the system can send but not receive. Check that system, particularly if it is the Designated Router. Use IPX PING to help determine the actual source of the problem. A interface board with a conflicting interrupt is a common source of this problem.Cause 5---System is declaring itself owner of the LAN even though it is not the owner. Reinitialize the system.Cause 6---LAN has become partitioned temporarily during normal NLSP operation. This should occur only during an NLSP system's startup, and the error should be corrected within a few minutes.Verify that the condition does not persist. If it does, check for a hardware problem or an NLSP software incompatibility with other systems.Clients running UnixWareTM, OS/2® Named Pipes, and NetWare/IPTM software have problems with connectivity.Systems are not properly configured. Refer to the BOOK="nlsp_enu" COLLECTION="nw41"NetWare 4.1 NLSP Migration Guide for information about the solution.PAGENUM=233 ID="BP237"PAGENUM=234RENDERAS="SECT3"LAN is IDXID="w1652"BOOK="_idx" COLLECTION="nw41" TIDREF="i3229"
PartitionedMARK=BULLETA LAN is partitioned. The LAN is partitioned when there are duplicate LANs or one of the LANs is declared unreachable in IPXCON (parameter path: Select CLASS=MENUITEM MOREINFO="NONE"NLSP Information > Select CLASS=MENUITEM MOREINFO="NONE"LANs).Cause 1---LAN is partitioned due to a failed hub or bridge. Check whether there is data-link connectivity by using IPX PING.Cause 2---LAN board has failed. This system does not see other systems on a LAN, or it does not have any adjacencies in the CLASS=MENUITEM MOREINFO="NONE"Up state. However, it declares itself as being attached to the LAN. In IPXCON, look for a system that is in the CLASS=MENUITEM MOREINFO="NONE"Initializing state (parameter path: Select CLASS=MENUITEM MOREINFO="NONE"NLSP Information > Select CLASS=MENUITEM MOREINFO="NONE"Neighbors). If a system on the LAN appears in the CLASS=MENUITEM MOREINFO="NONE"Initializing state on all other systems but has no neighbors itself, then the system can send but not receive. Check that system, particularly if it is the Designated Router. Use IPX PING to help determine the actual source of the problem.Cause 3---System is declaring itself owner of the LAN even though it is not the owner. Reinitialize the system.Cause 4---LAN has become partitioned temporarily during normal NLSP operation. This should occur only during an NLSP system's startup, and the error should be corrected within a few of minutes.Verify that the condition does not persist. If it does, check for a hardware problem or an NLSP software incompatibility with other systems.RENDERAS="SECT3"ID="FM63916"No Communication Occurs Between Two NetworksMARK=BULLETConnectivity is lost because a router is missing needed routes.This router's table is not consistent with the routing tables of other routers.The router has not converged because it is configured for multicast and the driver does not support multicast (even though the documentation claims that it does). Set the CLASS=MENUITEM MOREINFO="NONE"MAC Channel option to CLASS=MENUITEM MOREINFO="NONE"Broadcast (parameter path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select a specific binding > Select CLASS=MENUITEM MOREINFO="NONE"Expert Bind Options > Select CLASS=MENUITEM MOREINFO="NONE"NLSP Bind Options).PAGENUM=235 ID="BP238"A workstation cannot communicate with a server on a different connecting LAN, but other systems on the LAN can communicate.Cause 1---Physical problem on the workstation (for example, a broken LAN card).Replace the malfunctioning hardware.Cause 2---Packet filter has been implemented somewhere in the network that is discarding the system's packets.Check each intervening router and correct the filter configurations.A server cannot communicate with another server on a different connecting LAN, but other systems on the LAN can communicate.Cause 1---Server is misconfigured.Correct the server's configuration, and make sure that it has connectivity by verifying that it has the routes and services typical for your network.Cause 2---Connectivity exists, but it is so poor that the transports above IPX cannot maintain connectivity.Set up an IPX PING between the two systems. If you are getting a high rate of dropped packets, your connectivity problem is probably due to a malfunctioning link between the two networks. See IDREF="FM19789""Applications Perform Poorly" to determine which link is the problem.Cause 3---There is a duplicate network number. This can cause a duplicate system ID, provided that both systems are in the same area and the duplicate network numbers are two internal network numbers on two NetWare implementations of NLSP. The console probably displays the message:FORMAT="LINESPECIFIC"MOREINFO="NONE"System server_name with internal network
    number number has my system ID in it.Change the internal network of one of the conflicting systems, or remove one of the systems from the network immediately. For information about how to find the offending node, see IDREF="FM36382""Problems with LAN Connectivity."PAGENUM=235 ID="BP239"PAGENUM=236Cause 4---Packet filtering has been implemented on a router. This can cause similar symptoms to duplicate network numbers (for example, network A might be visible from network B, but network B is not visible from network A, or the reverse). If you do not have communications within an NLSP area, it is usually easy to find the network fault. Although the NLSPCLASS=MENUITEM MOREINFO="NONE" LANs screen shows you duplicate LAN network numbers, it does not show you whether a router or server has a duplicate network number.RENDERAS="SECT3"Services Are Inaccessible in the AreaMARK=BULLETServices are inaccessible in the area.Cause 1---Services are being blocked by filters.Examine the IPXCON CLASS=MENUITEM MOREINFO="NONE"Services option of each router in the path to isolate the router that is doing the filtering.Cause 2---Network connectivity problems.Check that the network to which the service is attached exists. If it does not, you should look for link connectivity in the path between the spot in the network that is missing the network number and the spot that is generating the service.Cause 3---Service name conflict. This occurs when you have the same service name and the same type (for example, file server). If the service is a file service, then the user logging in might not have appropriate rights and the login is rejected. MARK=BULLETCheck that the service has the appropriate network number through the CLASS=MENUITEM MOREINFO="NONE"Services option in IPXCON. If the service and network numbers are both visible, see IDREF="FM63916""No Communication Occurs Between Two Networks."Cause 4---Under very rare circumstances, the server from which you are doing the login has insufficient space to store the service in the bindery. Increase the disk space on the file server.PAGENUM=236 ID="BP240"PAGENUM=237Cause 5---If there are many services, a third-party router might be unable to transmit the entire SAP table before the next periodic update. A third-party router can cause it to start transmitting the services again from the beginning of the table, rather than completing the current update. Contact technical support.RENDERAS="SECT3"Number of Routes and Services on a System Shows Local Connectivity OnlyMARK=BULLETThe number of routes and services on a system shows local connectivity only.Cause 1---If the network to which the system is attached is an NLSP only network, and if it is not configured for RIP mode only, then the system might not receive RIP updates. If the message MOREINFO="NONE"Router server_nameMOREINFO="NONE" claims network numberMOREINFO="NONE" is really number is displayed at the system console, there is a RIP mode misconfiguration, and the two routers cannot communicate.MARK=BULLETTurn on the tracking windows, and check to determine whether there are any RIP and SAP updates coming into the server. If there are, it is possible that you need RIP on the network but that you have set the CLASS=MENUITEM MOREINFO="NONE"RIP State to CLASS=MENUITEM MOREINFO="NONE"Off. You can check this in IPXCON under CLASS=MENUITEM MOREINFO="NONE"Circuits. Check the interfaces and see whether you have accidentally set the CLASS=MENUITEM MOREINFO="NONE"RIP State to CLASS=MENUITEM MOREINFO="NONE"Off.If you are supposed to be receiving RIP on the network but are not, it is possible that the other routers on the network have been configured with RIP CLASS=MENUITEM MOREINFO="NONE"Off. If this is the case, and if you want to run RIP between the servers, then set the CLASS=MENUITEM MOREINFO="NONE"RIP State to CLASS=MENUITEM MOREINFO="NONE"On.Cause 2---Two NLSP systems are configured with different area addresses. In this case, the CLASS=MENUITEM MOREINFO="NONE"Initialization Failures counter in IPXCON should be increasing (parameter path: Select CLASS=MENUITEM MOREINFO="NONE"Circuits > Select CLASS=MENUITEM MOREINFO="NONE"Detailed Circuit Information). If you are on an area boundary and you are using RIP as the interarea protocol, configure RIP on both systems on the interface through which they are communicating.Cause 3---One of the routers has the CLASS=MENUITEM MOREINFO="NONE"RIP State option set to CLASS=MENUITEM MOREINFO="NONE"AutoPAGENUM=238 ID="BP241". If you intended to use RIP for interarea routing on the network, this is potentially dangerous. If the two NLSP routers are in communications with each other, they continue to run RIP. However, if they are connected together with a bridge or hub and that hardware fails and is brought back up again sometime later, NLSP does not detect the condition and RIP does not turn on again.If you are running RIP and SAP on the network and the networks and services fluctuate, see the next section.RENDERAS="SECT3"Services or Routes are Fluctuating ExcessivelyMARK=BULLETThe number of routes and services are fluctuating excessively. Some fluctuation is normal in a large network. Change is occurring constantly as systems are brought down for maintenance and other reasons. However, hundreds of routes and services coming and going indicate a network error. Each of the following problems are solved using the same procedure:Cause 1---Misconfiguration with RIP and SAP. Cause 2---Problem with a link.Cause 3---Error in NLSP. Cause 4---Two systems are competing for a system ID.Cause 5---LAN is generating errors.MARK=BULLETFirst try to determine which systems are affected. It might be helpful to determine which services are appearing and disappearing, and trace the paths backward to their location. If many services are appearing and disappearing, it might work better to find the set of affected systems. In either case, you should be able to determine the boundary routers.In NLSP it is easy to do. Simply look at an affected system's neighbors to see whether they have the problem, too. Examine each system as you move outward. If it is just a single NLSP system that is experiencing the problem, it is probably due to a local connectivity problem. Check the system for neighbor state changes, and so on.If you find that there is a boundary to the problem, or that there is a spot in which in one set of routers a group of services is disappearing but in another set of routers a different set of services is disappearing, you have probably found the boundary. Check to determine whether any of these systems are having a problem with its neighbors, fluctuating links, or a duplicate system ID.PAGENUM=239 ID="BP242"If you find that the problem is isolated to a LAN, then follow the same procedures described under IDREF="FM81062""Multiple Systems on a LAN Become Unreachable Intermittently." You might find that one system that is feeding the network is losing its neighbors, particularly the Designated Router. This system is probably the source of the problem.If you find that the problem is due to some interaction with RIP and SAP, you should check all systems for consistency on the LAN in regards to the following configurable RIP and SAP parameters in INETCFGCLASS=MENUITEM MOREINFO="NONE": Packet Size Override,CLASS=MENUITEM MOREINFO="NONE" Periodic Update Interval, andCLASS=MENUITEM MOREINFO="NONE" Aging Interval Multiplier (parameter path: SelectCLASS=MENUITEM MOREINFO="NONE" Bindings > Select a specific interface > Select CLASS=MENUITEM MOREINFO="NONE"Expert Bind Options > SelectCLASS=MENUITEM MOREINFO="NONE" RIP (orCLASS=MENUITEM MOREINFO="NONE" SAP) CLASS=MENUITEM MOREINFO="NONE"Bind Options).You should never let a periodic multiplier be less than 4. Due to timer skew, this means that after three dropped packets containing the same route, the system loses those routes. If any of the above RIP and SAP parameters are different, you need to reconfigure the values. Better still, just use the default, especially on LANs. Using different values for the timers is too risky to justify the savings on a LAN.RENDERAS="SECT3"ID="FM19789"Applications Perform PoorlyMARK=BULLETYou are experiencing poor application performance on systems in your network. Cause 1---Suboptimal path has been picked by NLSP. MARK=BULLETCheck the end-to-end path of the connection and make sure that the links that you thought would be chosen are being used for forwarding data. In an NLSP area this is easy; simply look at the CLASS=MENUITEM MOREINFO="NONE"Potential Paths screen (parameter path: Select CLASS=MENUITEM MOREINFO="NONE"Forwarding > Select a specific destination). Outside of an NLSP area, perform the procedure described in IDREF="FM36382""Problems with LAN Connectivity."If you find an incorrect path caused by RIP, then you can increase the RIP cost by decreasing the cost of the RIP link manually. Cause 2---Application relies on ticks to retransmit its packets. This should not happen through NetWare 4.1, but it is possible that some other manufacturer's router does not obey the ticks value.PAGENUM=240 ID="BP243"If this is the case, increase the cost of NetWare 4.1 to match the value of the router in question. It should not affect other paths very much, but it should help the application stop retransmitting packets.Cause 3---Router is in an NLSP area and you have routers with load sharing enabled. This causes the application to retransmit packets needlessly.If this is the case, turn off load sharing to see whether the situation improves.Cause 4---Link speed is too slow. You might be choosing the optimal path but you are still not getting very good throughput.MARK=BULLETIf you have a NetWare router and the protocol is windowed, you might want to enable the CLASS=MENUITEM MOREINFO="NONE"IPX Header Compression option. However, it might be that the application requires more bandwidth than you have available. Make sure that the problem is not due to latency. Compression adds latency, which can slow down protocols such as the Sequential Packet ExchangeTM (SPXTM) protocol that do not have windowing. Also, older versions of the NetWare shells do not have windowing. Experiment with the Packet BurstTM protocol.Cause 5---Malfunctioning routers in the end-to-end path, or there is a link that is causing problems in the end-to-end path.Determine the routers in the end-to-end path and check each router and link for abnormal behavior.Cause 6---Load sharing is enabled between dissimilar paths.Verify that the two paths have comparable media and data rates.RENDERAS="SECT3"Single System is Entering an Overloaded StateMARK=BULLETA single system is in an overloaded state.Cause 1---System is running out of memory.If the system is running NetWare 3.12, use MONITOR to check whether the CLASS=MENUITEM MOREINFO="NONE"Alloc Memory Pool is set too low. If it is too low, increase the value set for the CLASS=MENUITEM MOREINFO="NONE"Alloc Memory Pool or remove some applications.PAGENUM=241 ID="BP244"Cause 2---Another system is experiencing database overload. It is possible that another system in overload is causing your system to go into the overloaded state.On each suspect system, use MONITOR to check whether the CLASS=MENUITEM MOREINFO="NONE"Alloc Memory Pool is set too low. If it is too low, increase the value set for the CLASS=MENUITEM MOREINFO="NONE"Alloc Memory Pool or remove some applications.Cause 3---Transient condition on that router. If the problem persists, the system is running out of memory. If the system is running NetWare 3.12, use MONITOR to check whether the CLASS=MENUITEM MOREINFO="NONE"Alloc Memory Pool is set too low. If it is too low, increase the value set for the CLASS=MENUITEM MOREINFO="NONE"Alloc Memory Pool or remove some applications.RENDERAS="SECT3"ID="FM30910"Many Systems Are Entering an Overloaded StateMARK=BULLETMany systems are entering an overloaded state.Cause 1---Systems are being overrun with routing information. It might be that the number of systems in the NLSP area has increased beyond what you originally intended.Using IPXCON, look at the number of routers in the area (parameter path: Select CLASS=MENUITEM MOREINFO="NONE"NLSP Information > Select CLASS=MENUITEM MOREINFO="NONE"Routers). Add this number to the number of LANs in the area. This is a good indicator of the amount of memory that your NLSP area requires on each area. Novell recommends that you do not exceed about 400 LANs and routers (total) in an NLSP area. It is also possible that two areas have merged when they should not have. Determine whether there are some routers in the area that should not be there. Read the BOOK="nlsp_enu" COLLECTION="nw41"NetWare 4.1 NLSP Migration Guide for how to prevent the areas from merging, or use area addresses.Cause 2---You have imported your backbone multiple times into the NLSP area. NLSP is careful about the way that it imports external routes and services into the NLSP network. For example, only the Designated Router on a LAN imports information. Usually, if there are two NLSP systems connected to the same RIP backbone, but they are on different LANs, there is no problem. Only the best RIP information is imported into the NLSP network. However, it might be that most of the backbone is imported more than once. This can occur if there is more than one equal cost path from the NLSP network to the RIP network. You need to look carefully at all routers that are importing RIP to determine whether this has happened.PAGENUM=242 ID="BP245"Using IPXCON, find the systems that are importing RIP into the NLSP area by determining whether CLASS=MENUITEM MOREINFO="NONE"RIP Active is displayed on the LAN (parameter path: Select CLASS=MENUITEM MOREINFO="NONE"NLSP Information > Select CLASS=MENUITEM MOREINFO="NONE"LANs). Find the Designated Router on each LAN. Look at the CLASS=MENUITEM MOREINFO="NONE"Forwarding table of each Designated Router. You might have more than one Designated Router on the LAN. This is probably because you have turned off NLSP on the routers. In this case, you need to run NLSP between each of the routers to cut down on the amount of imported information on each LAN. This is discussed in the BOOK="nlsp_enu" COLLECTION="nw41"NetWare 4.1 NLSP Migration Guide.RENDERAS="SECT3"Connectivity Is Lost on Only One LANMARK=BULLETConnectivity is not possible on a single LAN, but it is possible on other LANs.This almost certainly indicates a duplicate network number. See IDREF="FM63916""No Communication Occurs Between Two Networks" for the solution. Usually, the network number that is the duplicate is the one that does not have the connectivity.PAGENUM=243 ID="BP246"Glossaryaccess rateSee IDREF="FM38450"AR (access rate).ACK (acknowledgment)An ASCII or EBCDIC code indicating that a message has been received correctly.adapter A piece of hardware, typically an interface card, installed in a computer, that connects the computer to other hardware or devices.addressAn identifier assigned to networks, stations, and other devices so that each device can be separately designed to receive and reply to messages.ID="FM29747"address resolution cacheAn area of the software that contains entries that map the IP address to the physical address.ID="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="FM18367"neighbor.administratorThe person who sets up a server, creates user login accounts and passwords, creates groups, sets security, and maintains the server. 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.Annex D An implementation standard (ANSI T1.617) that addresses signaling and other network management functions.ANSI (American National Standards Institute)A nonprofit organization in the U.S. that defines standards in many industries. It is supported by over one thousand trade organizations, professional societies, and companies. ANSI is affiliated with the Consultative Committee for International Telegraphy and Telephony (CCITT) and the International Organization for Standardization (ISO).ID="FM38450"AR (access rate)The physical rate of access of the user channel in bits per second (bps). The offered load to the Frame Relay network is bounded by this parameter.AppleTalkThe Apple Computer suite of protocols that enables the hardware and software on an AppleTalk network to interact and to route data.AppleTalk NLM(APPLETLK.NLM) The AppleTalk protocol stack and router, which is included as a NetWare Loadable Module (NLM) file in the NetWare MultiProtocol Router software.AppleTalk networkA collection of connected, individually controlled computers, printers, and other devices, together with the hardware and AppleTalk software used to link them.areaSee IDREF="FM90443"routing area.ID="FM40289"area addressThe area network number and mask that together define an NLSP routing area. See also IDREF="FM23208"area mask.area boundary routerA type of router that attaches an OSPF area to the backbone area. It has at least one interface in an area and one interface in the backbone area.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. See also IDREF="FM40289"area address.ID="FM40112"ARPAnetThe internetwork created by the Defense Advanced Research Projects Agency (DARPA) that later evolved into the Internet.ASCII (American Standard Code for Information Interchange)An 8-bit code for data transfer that was adopted by ANSI to ensure compatibility among data devices.ATCON utilityA diagnostic tool for use at the server. ATCON provides information about the server's AppleTalk stack and router, and about other AppleTalk networks on the internetwork.backbone networkThe primary connectivity mechanism of a hierarchical distributed system. It ensures that all systems that have connectivity to an intermediate system on the backbone have connectivity to one another.BootPA protocol used by a host to obtain IP addresses. bridgeA device that connects two or more physical networks, forwarding frames between networks based on information in the data-link header. Because a bridge operates at the Data-Link layer, it is transparent to the Network-layer protocols.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.bus topologyThe linear LAN used by Ethernet networks.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="FM10080"DARPA (Defense Advanced Research Projects Agency).ID="FM20010"circuitAny path that can carry an electrical current. In the context of NLSP, an internal logical representation of network connectivity between two NLSP routers.clientA node or workstation on a network that requires services from a server.client/server modelA configuration that uses distributed intelligence to treat both the server and the individual workstations as intelligent, programmable devices.coaxialA type of cable that uses two conductors: a central, solid wire core surrounded by insulation and, surrounding that, a braided-wire conductor sheath. A coaxial cable is well-suited for networking because it can accommodate high bandwidth but is relatively resistant to interference.communications controllerA machine directly attached to a host computer that processes communications to a host. The communications controller is also known as a front-end processor.congestionThe existence of excessive traffic on the network.ID="FM37606"configured routerA router configured explicitly on a network. (As opposed to a router that gets its configuration from a seed router.) Compare IDREF="FM41081"learning router. consoleThe monitor and keyboard from which the server or host activity can be viewed and controlled.convergenceThe synchronization process that a network goes through immediately after a route change happens on the network.convergence timeThe time required for routing information to propagate throughout the network.costA metric assigned to a circuit that determines the likelihood of traffic being routed over that circuit.ID="FM10080"DARPA (Defense Advanced Research Projects Agency)The U.S. government agency that funded ARPAnet. See also IDREF="FM40112"ARPAnet.datagramOne packet of information and associated delivery information that is routed through a packet-switching network.data rateThe speed at which data bits are transmitted and received. The data rate is usually measured in bits per second (bps). ID="FM37918"default zoneThe zone name in a zones list that has been specifically defined as the default zone. In the Novell implementation, if no default zone is defined, the first zone name in the zone list is the default zone. See also IDREF="FM23964"zone; IDREF="FM31006"zones list.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.destination addressThe address in a packet identifying which station is to receive it.destination nodeIn the Open Systems Interconnection (OSI) model, the nodes that represent the host computers at each end of a connection. In a packet-switching network, the node attached to the DTE that is receiving the data.device driverThe software or firmware that translates operating system requests into a format that is recognizable by specific hardware, such as adapters.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.EGP (Exterior Gateway Protocol)The routing protocol used by gateways in an internetwork to connect autonomous networks. It is used in the Internet core system.end nodeThe machine or unit (node) that serves as an originator and final destination of network traffic, but does not relay traffic originated by other nodes. See IDREF="FM29508"node.end systemThe computer of the Open Systems Interconnection (OSI) model containing application processes that can communicate through all seven layers of the OSI model. Equivalent to an end node.enterprise networkAn internetwork that connects a corporation's local and remote sites.ID="FM32459"EthernetA system of high-performance coaxial cables widely used in the communications industry. Ethernet cables can be part of an AppleTalk network or a TCP/IP network, for example. See also IDREF="FM10980"EtherTalk.ID="FM10980"EtherTalkAn AppleTalk network on Ethernet. An EtherTalk network can be either nonextended (EtherTalk 1.0) or extended (EtherTalk 2.0). See also IDREF="FM32459"Ethernet.extended networkAn AppleTalk Phase 2 network on high-speed media, such as Ethernet or token ring. An extended network is capable of supporting the Phase 2 addressing extensions of a network range and zones list. See also IDREF="FM24859"network range; IDREF="FM31006"zones list.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="FM34185"service information filter; IDREF="FM34609"routing information filter.filtering rateThe speed at which packets are checked and discarded.fragmentOne piece of a packet that has been divided by fragmentation.fragmentationThe process in which a packet is broken into smaller pieces to fit the size requirements of the physical network it is transmitted across.gatewayAn internetworking device that operates from the network to application layers of the Open Systems Interconnection (OSI) model. Sometimes used as a synonym for router. 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="FM40922"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.ICMP error message (Internet Control Message Protocol)A packet that contains information about failures on the network.ID="FM37209"IGP (Interior Gateway Protocol)A type of protocol used to exchange routing table information between collaborating routers in the Internet. The Routing Information Protocol (RIP) and the Open Shortest Path First (OSPF) protocol are examples of IGPs.ID="FM39468"INETCFG (Internetworking Configuration utility)A menu-based NetWare Loadable Module (NLM) 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.ID="FM17639"internal networkA virtual network that consists of two software nodes: the AppleTalk protocol stack and the AppleTalk router. See also IDREF="FM25948"network.InternetThe collection of networks and gateways that use the TCP/IP suite of protocols. Written in lowercase, it is an abbreviation for internetwork.Internet addressA 32-bit address assigned to hosts using TCP/IP.ID="FM30635"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="FM25948"network.Internetworking Configuration (INETCFG) utilitySee IDREF="FM39468"INETCFG (Internetworking Configuration utility).IP addressA 32-bit address assigned to hosts using TCP/IP.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 distinguished processes within the same computer. ISO (International Organization for Standardization)An international organization that establishes global standards for communication and information exchange, as well as for many other fields of commercial activity.keep-alive packet A type of packet sent as an Echo Request to a remote peer; typically, an Echo Response is sent back to the peer sending the request. A keep-alive packet serves as a continuous link-confidence test at the access interface, sent at a specified time period.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.LAN driverA device driver that renders the different types of packet frames used by each specific network type into a form that AppleTalk can process.ID="FM30919"ID="FM41081"learning routerOn a router, an interface configured to learn its configuration from a configured router on the same network. Compare IDREF="FM37606"configured router. ID="FM14424"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.linkA channel or line; usually refers to a point-to-point line. In the context of NLSP running on a LAN, a pointer to a Designated Router pseudonode. See also IDREF="FM85927"Designated Router; IDREF="FM92617"pseudonode.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.Link Support Layer (LSL)An implementation of the IDXID="w1653"BOOK="_idx" COLLECTION="nw41" TIDREF="i3079"
Open Data-Link Interface (ODI) specification, LSL serves as an intermediary between the server or router LAN drivers and the communications protocols, such as IPX, TCP/IP, and AppleTalk. LMI (Local Management Interface)An implementation agreement that addresses signaling and other network management functions. load balancingA scheme for distributing network traffic among parallel paths. It provides redundancy while using the available bandwidth efficiently.LocalTalk networkA system of cables, cable extenders, and connector boxes that connect computers and network devices as part of the AppleTalk network system. LocalTalk kits are manufactured by Apple Computer. Generally, where this reference refers to a LocalTalk connection, you can use any system of cables and connectors that supports AppleTalk protocols at 230.4 Kbps to interconnect Macintosh computers and other AppleTalk devices.loopbackA diagnostic test in which a signal is transmitted across a medium while the sending device waits for its return.loopback plugA special connector used to perform echo testing.ID="FM42184"LSP (Link State Packet)A packet generated by an NLSP router that lists the router's neighbors and attached IPX networks.ID="FM23365"MAC (media access control)The Data-Link layer protocol that governs access to transmission media.managed objectA device that is connected to a network and that can be managed by network management software or a protocol such as SNMP.management information baseSee IDREF="FM22835"MIB (Management Information Base).MbpsA data rate equal to 10 to the sixth power bps; often called megabits per second (1,000,000 bps).media access controlSee IDREF="FM23365"MAC (media access control).ID="FM22835"MIB (Management Information Base)A database of network management information used by the Common Management Information Protocol (CMIP) and the Simple Network Management Protocol (SNMP).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.multiprotocol encapsulation A method used by Network-layer protocols in which a layer adds control information to the protocol data unit (PDU) from the preceding layer. Also used in enveloping one protocol inside another for transmission (for example, IP inside IPX).name resolutionThe ability to associate a name that the network administrator has assigned with its network location.ID="FM18367"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.neighboring routersIn the Open Shortest Path First (OSPF) protocol, two routers that share a route to the same network.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="FM26432"NLM (NetWare Loadable Module).ID="FM25948"networkA collection of interconnected, individually controlled computers, together with the hardware and software used to connect them. See also IDREF="FM17639"internal network; IDREF="FM30635"internetwork.network addressA unique Network-layer number that refers to a logical network device. Also known as a protocol address. See also IDREF="FM35470"network number; IDREF="FM34134"node address.network administrationThe task of managing the software and hardware that connects computers in a network. This task includes assigning addresses to devices, maintaining network data files across the network, and setting up internetwork routing. Network administration can also include system tasks on a server, such as starting up and shutting down the system, adding and removing user accounts, and backing up and restoring data.network architectureA framework of principles to facilitate the operation, maintenance, and growth of a communications network by isolating the user and application programs from network details. Protocols and software are packaged together into a usable network architecture system that organizes functions, data formats, and procedures.network managementThe process of ensuring consistent reliability and availability of a network, as well as timely transmission of data. It can be performed by dedicated devices or programmed general-purpose devices.network monitoringA network management function that constantly checks the network and reports any problems. ID="FM35470"network numberIn an AppleTalk network, a decimal integer between 1 and 65,279. You assign a network number to each nonextended network supporting AppleTalk. See also IDREF="FM24859"network range.In a TCP/IP network, the number of the network. Hexadecimal numbers must start with the character pair 0x or 0X. It can be specified with or without trailing zeros. For example, the addresses 130.57 and 130.57.0.0 denote the same IP network. ID="FM24859"network rangeOn an AppleTalk network, a contiguous range of decimal integers between 1 and 65,279, such as 1-10. You assign a network range to each extended network supporting AppleTalk. See also IDREF="FM35470"network number.network topologyThe arrangement of nodes on a network; usually a star, ring, tree, or bus organization.NFS (Network File System)A distributed file system developed by Sun Microsystems that allows a set of computers to access one another's files cooperatively in a transparent manner.ID="FM26432"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.ID="FM37450"ID="FM29508"nodeAn addressable entity on a network. This term sometimes refers to a device itself. Some examples of nodes are Macintosh computers, printers, and file servers. The node acquires a unique 8-bit node number dynamically when it connects to the network. It tries to use that address and node number again when it connects to the network the next time. If the node finds that its previous number is already in use, it tries again until it finds a unique node address. See also IDREF="FM34134"node address.ID="FM34134"node addressA number acquired dynamically by each node when it comes up on a network. You cannot assign an AppleTalk node address explicitly. A device's node address is combined with the network number to form its unique network address. See also IDREF="FM29508"node.nonextended networkAn AppleTalk network that does not support AppleTalk Phase 2 extensions, such as zone lists and network ranges.octetA group of eight binary digits operated on as a unit; also called a byte or character.OSI (Open Systems Interconnection) model A seven-layer model for data communication.OSPF (Open Shortest Path First) protocolA hierarchical Interior Gateway Protocol (IGP) routing algorithm for IP that is a proposed standard for the Internet. Incorporates least-cost routing, equal-cost routing, and load balancing.physical addressThe Data-Link layer address of a network device.PING (Packet Internet Grouper)A program used to test the reachability of destinations by sending them an Internet Control Message Protocol (ICMP) echo request and waiting for a reply.pollingAny procedure that sequentially and periodically contacts terminals in a network.port(1) The logical point of contact between a LAN driver and a protocol that you bind to it. (2) The hardware that enables a component to communicate with a peripheral, such as a parallel port. (3) A unique server input/output address assigned to a LAN driver in NetWare software.ID="FM26161"protocolA set of rules for transmitting data within a network or internetwork. A protocol specifies the format, timing, and sequence in which the network transmits data. Common protocols include AFP, ALAP, RTMP, NCP, and IPX. See also IDREF="FM32333"protocol stack.protocol dependentA term that refers to routing based on a Network-layer or software address. It is specific to the type of Network-layer protocol, such as IP, IPX, or DDP.ID="FM39887"ID="FM32333"protocol stackA complete suite of protocols that includes all layers required to handle transmission and receipt of packets. See also IDREF="FM26161"protocol.protocol suiteA hierarchical set of related protocols.proxy ARPThe technique in which one machine, usually a router, answers ARP requests intended for another machine. By faking its identity, the router accepts responsibility for routing packets to the real destination. It allows a site to use a single IP network address for two physical networks.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="FM40922"RIP (Routing Information Protocol)A distance vector protocol that provides a measure of distance, or hops, from a transmitting system to a receiving system.route metricThe measure that determines the preference between two different routes generated by the same protocol to the same destination. In TCP/IP, an OSPF route entry has two metrics: an internal metric and an external metric.routerThe software that connects multiple networks so that all the nodes on each network can access services and nodes on any other network. It operates at the Network layer (Layer 3) of the OSI model for forwarding decisions. An AppleTalk router connects AppleTalk networks into an internetwork so that all the nodes on each network can access services and nodes on any other connected network. It receives and forwards AppleTalk packets on the networks to which it is directly connected. Router Discovery ProtocolA type of protocol that allows hosts to find routers on the locally attached networks. It is a feature of TCP/IP that alleviates the need to configure hosts with a routing table or a default router.routingThe transmission of a datagram from one node to another on the same or a different network. It also refers to the paths that are chosen to transmit an IP datagram from its origin to its destination, based on the IP addresses contained in the datagram.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; IDREF="FM31406"routing domain.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="FM34609"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 type of protocol that enables routing through the implementation of a specific routing algorithm. Examples of routing protocols include RIP, OSPF, NLSP, and IS-IS.routing tableA database in a router that keeps track of routes (and in some cases, metrics associated with those routes) to a particular network destination.routing updateA message sent from a router to indicate network reachability and associated cost information; it is typically sent at regular intervals and after a change in network topology.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.serverA combination of controller software and mass-storage devices that allows computer users to share common files and applications on a network. A server on an AppleTalk network might be a Macintosh computer running AppleShare software or an IBM PC (or a compatible computer) running the NetWare software.Service Advertising ProtocolSee IDREF="FM14203"SAP (Service Advertising Protocol).ID="FM34185"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 type of 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.standardA set of rules or procedures that has been agreed upon by industry participants.stub networkAn IP network that uses a subset of an existing IP network address and is serviced by a proxy router.subnet address maskA bit mask used to select bits from an Internet address to create a subnet.subnetworkThe portion of the backbone that is partitioned by repeaters, bridges, or routers.subnetwork addressingThe process of using a single Internet ID to identify a number of subnetworks within an organization.System IDA unique, six-byte hexadecimal number that identifies an NLSP router.ID="FM41934"TCP (Transmission Control Protocol)The major transport protocol in the Internet suite of protocols, providing reliable, connection-oriented, full-duplex streams; it uses IP for delivery.ID="FM12010"TCP/IP (Transmission Control Protocol/Internet Protocol)The protocol suite developed by the Advanced Research Projects Agency (ARPA). It includes TCP as the primary transport protocol and IP as the Network-layer protocol.TCPCONA diagnostic tool from Novell that provides information about a NetWare server or router TCP/IP stack and about other TCP/IP networks on the internetwork.TelnetA protocol in the TCP/IP suite that governs character-oriented terminal traffic.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="FM40922"RIP (Routing Information Protocol).ID="FM25053"TokenTalkAn AppleTalk network on token ring. topologyThe physical layer of network components (cables, stations, gateways, and hubs). Three basic interconnection topologies are star, ring, and bus networks.Transmission Control ProtocolSee IDREF="FM41934"TCP (Transmission Control Protocol); IDREF="FM12010"TCP/IP (Transmission Control Protocol/Internet Protocol).transparentA description of a function that operates without being evident to the user.tunnelingThe process of encapsulating and de-encapsulating one protocol in another. In AppleTalk, the process by which a router supporting AURP encapsulates AppleTalk packets in IP packets and sends them across the TCP/IP internetwork to the router supporting AURP. The router then removes the IP and AURP headers of the packets and forwards them, like other AppleTalk packets, to their destination AppleTalk network.workstationA node through which a user can access a server or other nodes. ID="FM23964"zoneA logical grouping of devices physically located on one or more networks. Each nonextended network must have exactly one zone name assigned to it. Each extended network must have at least one zone name, and can have up to 255 zone names, assigned to it. See also IDREF="FM37918"default zone; IDREF="FM31006"zones list.ID="FM31006"zones listA list of up to 255 unique zone names. See also IDREF="FM37918"default zone; IDREF="FM23964"zone.