NOVELL TECHNICAL INFORMATION DOCUMENT TITLE: IPXRTR.EXE; IPX Upgrade for NetWare Servers DOCUMENT ID: DOCUMENT REVISION: A DATE: 03MAY95 ALERT STATUS: Yellow INFORMATION TYPE: Issue README FOR: IPXRT3.EXE NOVELL PRODUCT and VERSION: IPX Upgrade for NetWare Servers 1.0 NetWare 3.11 NetWare 3.12 NetWare 4.02 ABSTRACT: Release 1.0c is an update to the 1.0 release that upgrades NetWare 3.1x and NetWare 4.02 servers with the latest IPX router software. NOTE: This release does not support servers running NetWare MultiProtocol Router(TM), NetWare WAN Links(TM), or NetWare 3.x SFT III(TM). ----------------------------------------------------------------- DISCLAIMER THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL. NOVELL MAKES EVERY EFFORT WITHIN ITS MEANS TO VERIFY THIS INFORMATION. HOWEVER, THE INFORMATION PROVIDED IN THIS DOCUMENT IS FOR YOUR INFORMATION ONLY. NOVELL MAKES NO EXPLICIT OR IMPLIED CLAIMS TO THE VALIDITY OF THIS INFORMATION. ----------------------------------------------------------------- ISSUE This release provides IPXRTR.EXE, which enhances IPX routing capabilities on NetWare 3.1x and NetWare 4.02 servers. This release also corrects problems that occur when installing from a NetWare volume and provides both RIP/SAP and NetWare Link Services(TM) (NLSP(TM)) support. You can run NLSP on any IPX network: NetWare clients, servers, and third-party IPX routers all interoperate with Novell NLSP routers. Also note that IPXRTR is no longer supported on NetWare 4.01. For this reason, you should ignore any references to NetWare 4.01 in the documentation. This file contains the following topics: - Installation Instructions - Patch History - Solution Specifics - New Product Features - Load Balancing - Problems Corrected in this Release - Product Interoperability - Product Restrictions - Incompatibility with Other Products - Product Configuration - Loading SNMP - Product MIBs - Content of DISK1 INSTALLATION INSTRUCTIONS: To install IPX Upgrade for NetWare Servers 1.0c, complete the following steps: 1. Read this document thoroughly. 2. If you have a PostScript* printer, complete the following steps to print the documentation; otherwise, skip to Step 3. a. Download IPXDOC.EXE. b. Run IPXDOC.EXE to extract the files it contains. IPXDOC contains the following guides: - IPX Upgrade for NetWare Servers 1.0 Installation and Configuration Guide - IPX Upgrade for NetWare Servers 1.0 NLSP Migration Guide NOTE: Although these guides refer only to version 1.0 of the software, they are also accurate for version 1.0c. In addition the INSTALL utility will indicate version 1.0. The modules listing for IPXRTR will indicate version 1.0c. c. Print these guides using the following commands, then skip to step 4: COPY BOOKINC.PS LPT1 (or LPT2) COPY BOOKMIG.PS LPT1 (or LPT2) If the LPTx port is being redirected to a Novell print queue by the use of CAPTURE, be sure to use PRINTCON to create a PostScript "job" and issue the CAPTURE command with the JOB= parameter. 3. If you do not have a PostScript printer, you can still print an ASCII version of the IPX Upgrade for NetWare Servers 1.0 Installation and Configuration Guide by printing the INSTALL.TXT file. 4. Read the IPX Upgrade for NetWare Servers 1.0 Installation and Configuration Guide. This guide provides instructions for installing and configuring the software. 5. To create your own installation diskettes, complete the following steps: a. When IPXRTR.EXE is unzipped, it creates a batch file (MAKE_IPX.BAT) and the following three directories: - IPXSERV1 - IPXSERV2 - DISK1 If you want to install the software from your hard drive, skip to Step d. b. If you want to install the software from diskettes, use the DOS FORMAT command to format two high-density diskettes (3.5-inch or 5.25-inch). The FORMAT command asks you for the label to give the diskette (not the label you paste on the diskette). Because the MAKE_IPX.BAT file relabels the diskettes, the labels used when formatting the diskettes are unimportant. c. If you want to install the software from diskettes, use the following command to run the batch file and create diskettes on the A: drive: MAKE_IPX A: d. Follow the instructions in the PostScript guides you printed in Step 2. If you want to install the software directory from the server's hard drive, change the path to :\IPXSERV1 in place of the step that instructs you to insert the IPX Upgrade for NetWare Servers Disk 1 into the disk drive. NOTE: If the system console displays the message "IPXRTR: IPX link state router down", verify that you completed Step d correctly. SOLUTION SPECIFICS: This file contains key information about IPX Upgrade for NetWare Servers 1.0c software that is not available elsewhere. Because this product contains fixes for IPX Upgrade for NetWare Servers 1.0, this file does not contain the installation instructions for this software. These instructions are provided in the IPX Upgrade for NetWare Servers 1.0 Installation and Configuration Guide, which is included with this update. NEW PRODUCT FEATURES The routing capabilities of IPX have been enhanced to meet a number of customer requirements. Features new to IPX Upgrade for NetWare Servers 1.0c include the following: - Ability to bind multiple NICs to a single network number. - Load sharing, which is useful when connecting two or more interfaces on a file server to an Ethernet* switch. - SNMP instrumentation for IPX, RIP/SAP, and NLSP, along with an IPX console (IPXCON.NLM). In addition, ASN.1 copies of the MIBs are included for integration into SNMP management consoles. - NLSP, a new link state routing protocol for IPX that greatly reduces routing overhead and provides more diagnostics on the operation of IPX and IPX routing. - IPXPING.NLM, a utility that tests connectivity between systems running IPXRTR. - Use of the NetWare 3.12 and NetWare 4(TM) hashing algorithm for RIP/SAP processing, which greatly reduces CPU utilization on NetWare 3.11 in large IPX RIP networks. - Ability to turn off IPX routing on servers with multiple NICs. - Filtering of NetBIOS packets, which is enabled by a SET command. - Ability for NLSP to switch automatically from broadcast to multicast when all NLSP nodes on a LAN support multicast. LOAD BALANCING When a NetWare client loads VLMs, it makes an NCP GetLocalTaget(GLT) RIP request. This request is a broadcast and is therefore received by the server on all NICs (or interfaces) bound to the LAN. In previous versions of IPXRTR, the server responded to the request from each NIC on the LAN. The client always caches the first reply it gets and uses the MAC address to communicate with the server from that point on. In version 1.0a and later, the server that supports load balancing does two things: First, the server responds to requests only from one NIC and sends the GLT responses in a "round-robin" fashion out all other NICs attached to the LAN. For example, suppose GLT requests from all clients are processed on NIC 1. If the GLT from Client A is received, only the request seen on NIC 1 is processed and the response is sent from NIC 1. From that point on, client A sends data to the server at NIC 1. If a GLT from Client B arrives, only the GLT received on NIC 1 is processed; this time, however, the response is sent on NIC 2, Client B sends data to NIC 2, and so on. Second, load balancing allows the server to send NLSP packets to an IPX network through just one of the cards attached to a LAN and all other IPX packets to alternating cards. To ensure that load balancing is working, use MONITOR to compare the packets sent between the interfaces doing load balancing. The load should be equally distributed on all interfaces. However, the interface sending the NLSP packets should have a slightly higher packet count. Load balancing is available only for NLSP and IPXRTR 1.0a or later. How to Configure Load Balancing This release of IPXRTR corrects a problem with load balancing. If you want to configure load balancing, you must set the Maximum Number of Path Splits parameter to a value greater than 1 and less than 9. A sample NLSP.CFG file containing the MaxPaths command is provided on DISK1. Copy that file to SYS:\ETC. If you already have a NLSP.CFG file then the following line must be added to the GLOBAL section of the SYS:\ETC\NLSP.CFG file: MaxPaths = ; A new SET command has been added for configuration of load balancing when a server has multiple binds to the same LAN without going through a router. The syntax of this command is: SET LOAD BALANCE LOCAL LAN = The default state is OFF. You should use this SET command in the following instances: - Turn on load balancing if a server is connected to a LAN through multiple interfaces and the interfaces are either on the same media or attached to different ports of a switch. - Turn off load balancing if a server has multiple interfaces to two segments of the same LAN that is also bridged. NOTE: The values 0, -1, and -2 are reserved and should never be assigned as IPX network numbers. PROBLEMS CORRECTED IN THIS RELEASE This release corrects the following problems: - The SAP from a print server was not aged out if RIP and SAP were operating in AUTO mode. - An abend that occurs if an SPX application sends a packet to the internal network and load balancing for the local LAN is turned on using the SET command described above. - Wildcard filters that were inappropriately applied to the source of the packet to all interfaces. - Improper handling of Get Nearest Server requests. The server no longer responds with the nearest Directory Server if the SET REPLY TO GET NEAREST SERVER option is off. NOTE: IPXRTR does not allow static routes or services to be added to a link that is not using static routing. - An IPXRTRNM abend that occurs on NetWare for Windows. - Failure of IPXCON to display a level 2 neighbor. PRODUCT INTEROPERABILITY Every effort has been made to identify Novell and third-party products that require RIP or SAP to operate. Other Novell or third-party products that have not yet been identified might also require RIP or SAP. If you have a product that loses connectivity through a Novell NLSP server, complete the following steps: 1. Unload IPXRTRNM and IPXRTR by entering the following commands at the server prompt: UNLOAD IPXRTRNM UNLOAD IPXRTR 2. Reload IPXRTR and IPXRTRNM by entering the following commands at the server prompt: LOAD IPXRTR LOAD IPXRTRNM This returns the IPX router to the default RIP/SAP-only mode. 3. Check whether connectivity returns to the product. If connectivity returns, the product requires RIP or SAP to function. Contact Novell Technical Support at 1-800-NETWARE (1-800-638-9273) if you discover any such products. PRODUCT RESTRICTIONS IPX Upgrade for NetWare Servers 1.0c is provided with the following restrictions: - It does not support NetWare MultiProtocol Router 2.x software. Do not install IPX Upgrade for NetWare Servers 1.0c on a server or router running NetWare MultiProtocol Router 2.x, NetWare WAN Links 2.0, or NetWare MultiProtocol Router Plus 2.x. - It does not provide support for systems running NetWare 3(TM) SFT III systems. A revision to SFT III supporting NLSP is available with NetWare 4.1. - SERVMAN configurations for IPX RIP/SAP and SAP filtering do not take effect with this product. - IPXRTR.NLM fails to load if IRWASM.NLM is already loaded. If you want to run IPXRTR.NLM on the same system as NetWare SNA Links(TM) 1.0 software, ensure that the LOAD IPXRTR command line precedes the LOAD IRWASM command line in your AUTOEXEC.NCF file. INCOMPATIBILITY WITH OTHER PRODUCTS In certain configurations, the Intel* EtherExpress* TPE ISA hub driver 1.12 incorrectly identifies its MAC address to the NetWare server. Other NLSP systems on the LAN notice the error and display the following message: A mismatched source node/data-link address *address*/ *address* in hello packet on circuit from . This error causes connectivity loss and occurs when you have loaded two master hub boards on a single NetWare server. To prevent the problem, load only one master hub board per NetWare server. Simply unbinding IPX from the board is not sufficient. If more than one hub driver is loaded, the problem persists. Old-style QMS printers do not interoperate in NLSP-only networks. They require RIP and SAP for the NetWare servers on which the print queues reside. Use the following information to determine whether a QMS printer can interoperate with NLSP: The "classic" NetWare daughter boards listen for RIP and SAP information and age this information to keep it current. The newerboards, known as "CrownNet-style" boards, query the bindery of their file server to extract the information they need. You can determine which type of board you have in one of three ways: - The "classic" board supports only NetWare. The CrownNet board supports TCP/IP, AppleTalk and LAN Manager/LAN Server. These protocols are visible in the keypad options. - When QMS printers start up, they generate a startup page. The system displays the communications options on that page. The identification of the daughter board is displayed under the Serial and Parallel options. CrownNet boards are identified by the words "CrownNet xxx". - Some QMS printers support two optional daughter boards. For those printers, look for "CrownNet" under the interface information column on the startup page. Do not use only NLSP on your IPX network if you have "classic" daughter boards in your printer. These boards require RIP and SAP. PRODUCT CONFIGURATION To simplify adding the LOAD commands to your AUTOEXEC.NCF file, the installation process inserts the appropriate lines into the file and comments them out. To cause the commands to be executed each time the system is restarted, select the commented lines you want to run and remove the comment characters. The LOAD line options are documented in the IPX Upgrade for NetWare Servers 1.0 Installation and Configuration Guide. LOADING SNMP When you load SNMP provided with the IPX Upgrade for NetWare Servers 1.0c software on a NetWare 3.11 server, the following messages are displayed on the console: SNMP: Could not register the SNMP NCP extension ID. SNMP: Agent will not be able to handle SNMP over NCP traffic. Ignore these messages. PRODUCT MIBs IPX Upgrade for NetWare Servers 1.0c includes three new product MIBs that you can integrate with Novell and third-party network management software. These ASN.1 text files are included on Disk 1 in the REFMIBS directory if you have made floppy disks; otherwise, they are located in the DISK1\REFMIBS directory. Refer to the documentation for these products for information about installing additional MIBs. CONTENT of DISK1 Disk1 contains several NetWare patches that you should apply to your server. Please review DISK1 and install the patches that are appropriate to the NetWare version on your server. PATCH HISTORY: Patch IPXRTR2.EXE was formerly on NetWire; this IPXRTR3 patch supersedes it. Self-Extracting File Name: IPXRT3.EXE Revision: A Files Included Size Date Time \ IPXRT3.TXT (This File) INSTALL.TXT 37224 05-15-95 6:10p MAKE_IPX.BAT 1743 02-10-95 3:41p \DISK1\ NLSP.CFG 257 05-24-95 3:15p \DISK1\REFMIBS\ IPXMIB.TXT 44641 04-21-94 9:49a RIPMIB.TXT 13421 04-05-94 9:08a NLSPMIB.TXT 61075 01-11-94 2:58p \DISK1\SERVER.3X\ SPXS.NLM 24238 05-17-94 9:58a \DISK1\SERVER.4X\ SPXS.NLM 36102 10-20-94 2:14p \DISK1\SERVER.311\ SPXFIX2.NLM 1727 11-23-93 9:26a PATCHMAN.NLM 9632 02-04-93 10:38a SPXDDFIX.NLM 1151 03-10-94 9:44a SPXNSFIX.NLM 1047 05-26-94 8:56a \DISK1\SERVER.312\ PM312.NLM 9221 03-24-94 11:06a SPXFIX2.NLM 1035 11-23-93 9:13a SPXDDFIX.NLM 1148 03-10-94 9:48a SPXNSFIX.NLM 1044 05-26-94 8:45a \IPXSERV1\ RSPAWN.NLM 22866 11-22-94 2:54p PSCRIPT.DAT 4384 11-22-94 4:28p MPRDINST.NLM 6614 11-22-94 2:54p PINSTALL.HLP 3753 10-13-94 1:58p PINSTALL.NLM 119868 12-09-94 9:56a \IPXSERV1\ETC\SAMPLES\ HOSTS 441 09-11-92 2:31p GATEWAYS 500 05-24-93 4:59p NETWORKS 288 09-11-92 2:31p PROTOCOL 370 09-11-92 2:31p SERVICES 1570 09-11-92 2:31p \IPXSERV1\IPX\ IPXCON.HLP 132679 09-02-94 10:42a IPXCON.MSG 35382 02-01-95 4:35p IPXCON.NLM 345530 05-10-95 11:21a IPXCON.NL_ 95761 05-10-95 11:21a IPXRTR.MSG 11198 02-01-95 3:47p IPXRTR.NLM 317499 05-10-95 11:09a IPXPING.HLP 6511 09-02-94 11:16a IPXPING.MSG 1263 02-01-95 4:44p IPXPING.NLM 34846 02-01-95 4:44p IPXRTRNM.MSG 309 02-01-95 4:23p IPXRTRNM.NLM 50658 05-10-95 11:15a IPXSTACK.MSG 1431 02-01-95 4:23p IPXSTACK.NLM 27704 02-01-95 4:25p \IPXSERV1\UTILS\ TUI.MSG 2304 11-22-94 12:18a TUI.NLM 43415 11-22-94 12:18a SNMP.MSG 3698 11-22-94 8:58a SNMP.NLM 85942 11-22-94 8:59a RSPAWN.MSG 1598 11-22-94 2:54p MPRDINST.MSG 863 11-22-94 2:54p \IPXSERV2\ NLSPAUTO.NLM 7020 11-22-94 3:00p \IPXSERV2\3X\ CLIB.NLM 344458 10-27-94 1:29p IPXS.NLM 8149 08-10-93 7:53a A3112.NLM 12425 03-29-94 1:49p STREAMS.NLM 53566 07-20-93 4:19p AFTER311.NLM 14651 03-29-94 1:48p \IPXSERV2\40X\ CLIB.MSG 11238 04-20-94 10:13a CLIB.NLM 207535 05-25-94 11:37a IPXS.MSG 1182 08-13-93 1:55p IPXS.NLM 10363 08-23-93 8:13a PM401.NLM 8113 02-03-94 1:09a STREAMS.MSG 4775 08-13-93 2:11p STREAMS.NLM 63201 09-14-93 10:12a NCPIDFIX.NLM 1837 04-05-94 5:17p \IPXSERV2\ALL\ TCPIP.MSG 11126 09-09-94 2:50p TCPIP.NLM 194163 09-09-94 2:50p NWSNUT.MSG 2984 10-17-94 2:11p NWSNUT.NLM 175546 10-17-94 2:14p IPCONFIG.MSG 1965 02-22-93 12:35p IPCONFIG.NLM 8439 02-22-93 12:35p ----------------------------------------------------------------- Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information. ----------------------------------------------------------------- ÿ