NetWare/IP v1.1 Update (NIP318) NetWare/IP Release Document README.TXT Copyright (c) 1995 Novell, Inc. All Rights Reserved. THIS WORK IS SUBJECT TO U.S. AND INTERNATIONAL COPYRIGHT LAWS AND TREATIES. NO PART OF THIS WORK MAY BE USED, PRACTICED, PERFORMED, COPIED, DISTRIBUTED, REVISED, MODIFIED, TRANSLATED, ABRIDGED, CONDENSED, EXPANDED, COLLECTED, COMPILED, LINKED, RECAST, TRANSFORMED, OR ADAPTED WITHOUT THE PRIOR WRITTEN CONSENT OF NOVELL, INC. ANY USE OR EXPLOITATION OF THIS WORK WITHOUT AUTHORIZATION COULD SUBJECT THE PERPETRATOR TO CRIMINAL AND CIVIL LIABILITY. The NetWare/IP software update contains both bug fixes and enhancements. The enhancements consist of new optional parameters, which can be set using new UNICON utility screens. This patch supersedes previously applied patches to NetWare/IP v1.1, including the special compiled versions. If previous patches have been applied, the NIP318 install will prompt the user to remove them before proceeding. It is not required to apply the updated NetWare/IP client to work with the server components of the NIP318 patch; however, Novell strongly recommends that you do so to ensure the new features included in this patch are supported by the updated NetWare/IP client. The NWIPMAP.EXE included in this patch will not work correctly without the updated NetWare/IP client. The updated NetWare/IP client is available in Netwire compuserve (NWIPWS.ZIP). NOTE: THIS PATCH IS DESIGNED TO RUN ON NETWARE v3.12 AND v4.02 ONLY. This README file includes the following sections: 1. Updating NetWare/IP 1A. Updating NetWare/IP on a Server 1B. Updating NetWare/IP on a Client 1C. Using NetWare/IP with the NetWare Management System 1D. Updating the Domain Name Server 2. Using the New Features 2A. Setting the Retry Time Parameters 2B. Setting the NSQ Broadcast Parameters 2C. Improving Communication Parameters 2D. Optimizing NetWare/IP for WAN Environments 2E. Setting up Forwarding NWIP/IPX gateways NOTE: If you receive network errors when transferring data, configure the Tunable parameters described in Section 2B, "Improving Communication Parameters" of this README file. 3. Registered/Unregistered DSSes 4. Using the /v Switch 5. Known problem Use the search features of your text editor to go directly to the section of this README file that you want to read. NOTE: You should read the entire README file before you install or update the NetWare/IP on a server or client. To enable the new features included in the NetWare/IP software update, you need to configure the parameters described in this document. ============================================================ 1. Updating NetWare/IP ============================================================ This section explains how to install the NetWare/IP software update on a server and on a client. It also includes information about the NetWare Management System (NMS) function included in this update and installing a bug fix to DNS servers. ============================================================ 1A. Updating NetWare/IP on a Server ============================================================ The NetWare/IP software update contains new files that you must install on NetWare/IP servers. CAUTION: When you install the NetWare/IP update on the server, do not delete the original NWIP1.1 software from the server. This update replaces only the following files: Filename Version ----------- ------- NETDB.NLM 2.21 DSS.NLM 2.05t NAMED.NLM 2.25e NWIP.NLM 2.11h NWIPADM.NLM 1.10d NWIPADM.HLP NWIPAGT.NLM 1.02r To update a server that already has NetWare/IP installed, proceed as follows. From your client workstation, perform the following steps: 1. Log in to the server. 2. Rename the existing NetWare/IP files. For example, rename DSS.NLM to DSS.OLD. You must rename each NetWare/IP file listed. 3. Create a new directory named NWIP.PAT on any valid NetWare volume. For example: MD NWIP.PAT 4. Change to the NWIP.PAT directory. For example: CD NWIP.PAT 5. Copy the self extracting file NIP318.exe into the directory NWIP.PAT and then type NIP318 to extract the files. From your NetWare/IP server, perform the following steps: 1. Load the Installation program by typing LOAD INSTALL 2. Select PRODUCT OPTIONS. The Currently Installed Products Menu appears and lists the following product: NWIP 1.1 NetWare/IP NWUPD 1.1B PTF-F191 NetWare/IP Patch The second entry will appear in the list only if you have previously applied the NIP191 patch. 3. Press and then to install the update files. The SPECIFY DIRECTORY PATH dialog box appears. 4. Type in the path to the NWIP1 directory where the NIP318 file was extracted. Example: SYS:\NWIP.PAT\NWIP1 If the NIP191 patch has been previously applied, the NIP318 install will prompt you to remove it. After the Installation program installs the files, the Currently Installed Products menu appears and lists the following: NWIP 1.1 NetWare/IP NWUPD 1.1C PTF-F318 NetWare/IP Patch 5. Exit the Installation program or press +. The system console prompt appears. 6. Type UNISTOP at the system console prompt to unload the NetWare/IP modules from memory. 7. Type UNISTART to start the modules again. This NetWare/IP rev contains optional parameters for network customization purposes. If you want to change these parameter settings, use the UNICON utility as described in Section 2, "Using the New Features" in this README file. If you changed the parameter settings, then at the system console type UNISTOP to unload the NetWare/IP modules from memory. Type UNISTART to start the modules again. ============================================================ 1B. Updating NetWare/IP on a Client ============================================================ Get the updated NetWare/IP client from compuserve (NWIPWS.ZIP). The updated client contains five diskettes; they are WSDOS_1, WSDOS_2, WSDOS_3, WSDOS_4, and WSDOS_5. The label of each diskette is important only if you choose to update the NetWare/IP client from diskettes. You can update the NetWare/IP client software automatically from the server or manually from diskette. This section provides step-by-step instructions for both methods. Updating the software using a diskette requires you to visit each client workstation individually; therefore, we recommend that you update your clients using the server-based installation whenever possible. NOTE: The NetWare/IP client install program does not configure the clients NET.CFG for Ethernet_II frame support. Please update the NET.CFG to support the Ethernet_II frame type for the NetWare/IP client software to work. If NetWare/IP client software is installed on C:, the NET.CFG file is found in the C:\NWCLIENT directory. You must update the NetWare/IP servers before you update the NetWare/IP clients. UPDATING A CLIENT USING A SERVER-BASED INSTALLATION If you want to update all existing NetWare/IP clients without visiting each client workstation individually, perform the following steps: 1. Create a directory NWCLIENT on any valid NetWare Volume. Example: MKDIR NWCLIENT Copy the contents of the 5 client disks that came with NWIPWS.ZIP. Example: XCOPY A: F:\NWCLIENT /s/e Where F: is a drive mapped to a valid NetWare volume and A: is a valid floppy disk drive. The 5 client disks are WSDOS_1, WSDOS_2, WSDOS_3, WSDOS_4 and WSDOS_5. 2. Provide the NetWare/IP client users with the appropriate information needed to install the new software. This information is contained on the Client Worksheet provided in the "NetWare/IP Administrator's Guide." 3. Inform the NetWare/IP client users of the server name and login, and then tell each user to install the new NetWare/IP client software by changing directories to the NWCLIENT dir and typing INSTALL. For more in-depth installation instructions, refer to page 9-3 of the "NetWare/IP Administrator Guide." If you want your client users to configure the Tunable parameters, you should add the parameters to the Client Worksheet. The client users should configure the Tunable parameters during installation as follows: 1. From the NetWare/IP Client Install v1.21 screen, scroll down to Step 5 and press . A new screen appears with additional options. 2. Scroll down to Step 7 and select Tunable Parameters. The NetWare/IP Tunable Parameters screen appears. For example: NetWare/IP Tunable Parameters DSS Preferences (Host/IP Address/Network) Preference #1: boston Preference #2: 127.39.1.0 Preference #3: 129.0.0.0 Preference #4: 19.20.1.1 Preference #5: 120.5.0.0 Nearest Server Preferences (Host/IP Address/Network) Preference #1: boston Preference #2: 127.39.128.0 Preference #3: 150.100.1.1 Preference #4: 127.39.0.0 Preference #5: For complete information on the Tunable parameters, see Section 2B, "Improving Communication Parameters" of this file. UPDATING AN EXISTING CLIENT USING A DISKETTE Using the diskette method requires you to visit each NetWare/IP client workstation individually to update the software. For complete information about installing NetWare/IP on a client, see Chapter 9, "Installing and Configuring the NetWare/IP Client Software" in the "NetWare/IP Administrator's Guide." If you are going to configure the optional Tunable parameters, you should edit the C:\NWCLIENT\NET.CFG file now. For information on configuring the Tunable parameters, see Section 2B, "Improving Communication Parameters" of this file. ============================================================ 1C. Using NetWare/IP with the NetWare Management System ============================================================ The NWIP.NLM in this software update includes the NetWare Management System (NMS) Automatic Discovery function. The new NetWare/IP client file provides better IPX compatibility and support for the NMS NET Explorer Automatic Discovery function. The default value for NWIP1_1 COMPATIBILITY is set to "OFF" to enable the automatic discovery function with NIP318 client installation. NWIP1_1 COMPATIBILITY OFF If you have a mixed NetWare/IP environment in which the servers have either NetWare/IP v1.1 or this update installed, set the value to ON and then no automatic discovery. ============================================================ 1D. Updating the Domain Name Server ============================================================ The DNS server(NAMED.NLM) included in this NetWare/IP update contains a bug fix for servers that use the old DNS server that came with the NFS gateway 1.1/1.2 or NetWare/IP 1.1. The bug fix applies only to the servers that use the NAMED.NLM replica function. The old DNS server did not create an accurate replica database (a local copy of the zone database imported from the master/primary DNS server). This problem causes an invalid response to Start of Authority (SOA) and Name Server (NS) queries. To apply the bug fix, initiate a fresh zone transfer to these servers by doing one of the following: 1. Manually delete the zone database file on the DNS replica servers. To locate the zone database file on the servers, search for the entry that begins with the keyword "secondary" in the SYS:ETC/NAMED.CFG file. After you delete the zone database file, reload the NAMED.NLM. For example, in the entry SECONDARY FOO.COM 1.2.3.SYS:ETC/DNS/ZONE.DB the zone database file is ZONE.DB. Then you would go to the SYS:ETC/DNS/ directory and delete the ZONE.DB file. 2. Manually edit the serial number field in the SOA record for the zone at the master name server to increment the number by one digit. To locate the file to edit, search for the entry that begins with the keyword "primary" in the SYS:ETC/NAMED.CFG file. ============================================================ 2. Using the New Features ============================================================ This NetWare/IP update contains new optional parameters that provide the following features: - Retry Time parameters, which configure the number of times and the interval at which the modules retry contacting a DSS server at startup. - Communication parameters, which when configured, enable NetWare/IP to provide more efficient communication between the NetWare/IP client, NetWare/IP server, and DSS servers. - Optimization parameters, which optimize NetWare/IP running under WAN environments. When you change the parameter settings, type UNISTOP to unload the NetWare/IP modules from memory. To start the modules again, type UNISTART ============================================================ 2A. Setting the Retry Time Parameters ============================================================ You can configure the following optional parameters on the NetWare/IP client and NetWare/IP server to indicate the amount of time between attempts to retry contacting a DSS server at startup. - AUTORETRIES, which specifies the number of times to retry. The default is 1. The range is 1 through 10. - AUTORETRY_SECS, which specifies the number of seconds between retries. The default is 10. The range is 5 through 60. If you specify a value for these parameters that is not in the valid range, the NetWare/IP server uses the default value. CONFIGURING THE NETWARE/IP CLIENT To configure these parameters on a NetWare/IP client, edit the NWIP section of the NET.CFG file in the C:\NWCLIENT directory. For example: AUTORETRIES 3 AUTORETRY_SECS 4 In this example, a NetWare/IP node re-issues DNS queries (such as NS and SOA queries) if it cannot communicate with either the DNS or DSS server. The NetWare/IP node retries three times and waits at four second intervals between each retry before giving up. CONFIGURING THE NETWARE/IP SERVER To configure these parameters on the NetWare/IP server, use the UNICON utility. Start at the UNICON utility's Main Menu and select the following: -> Manage Services -> NetWare/IP -> Configure NetWare/IP The NetWare/IP Server Configuration screen appears, as shown: NetWare/IP Server Configuration NetWare/IP Domain: nwip.novell.com Preferred DSSes: Initial DSS Contact Retries: 3 Retry Interval: 4 seconds Slow Link Customization: Forward IPX Information to DSS? No To configure the AUTORETRIES parameter, edit the Initial DSS Contact Retries field. To configure the AUTORETRY_SECS parameter, edit the Retry Interval field. ============================================================ 2B. Setting the NSQ Broadcast parameter ============================================================ You can configure the NSQ_BROADCAST parameters on the NetWare/IP client to indicate if the client will attempt to contact any of the nearest NWIP servers using broadcast. To configure the parameter on a NetWare/IP client, edit the NWIP section of the NET.CFG in the C:\NWCLIENT directory. For example: NSQ_BROADCAST ON If it is set to ON (default value), the client will not attempt to contact any of the nearest NWIP servers using broadcast until it is invoked by a specific Nearest Server Request (e.g. when VLM loads)or other SAP/RIP requests. If it is set to OFF, the client will attempt to contact each of the nearest NWIP servers at "load" time -- when NWIP.EXE is initialized. In both cases, the client will store the found NWIP servers in its cache for future references. ============================================================ 2C. Improving Communication Parameters ============================================================ You can configure the NetWare/IP client to improve its communication with both the DSS servers and NetWare/IP server. You can also configure the NetWare/IP server to improve its communication with the DSS servers. The preferred DSS parameter specifies the desirable DSS servers for the client and server to locate. When you configure a Preferred DSS parameter on either a client or a server, you must specify a hostname, an IP address, or a partial IP address. The specified IP address can represent a subnetwork address or an IP address matching pattern. You can specify up to five preferences per parameter. For information on specifying a subnetwork or IP address, see the "Physical Addresses and Internet Addresses" section of Appendix B, "TCP/IP Protocol Suite" in the "TCP/IP Transport Supervisor's Guide." CONFIGURING THE NETWARE/IP CLIENT To improve the NetWare/IP client's communication, you can configure the following two optional parameters: - Preferred DSS parameter, which specifies the desirable DSS servers for the client to locate. - Nearest NetWare/IP server, which specifies the NetWare/IP servers with the closest route to the client. Using this parameter, a NetWare/IP client can rely on the closest NetWare/IP server to resolve subsequent queries. This parameter can directly improve the response time for some IPX applications that use the General SAP query (for example, RCONSOLE). Specify this parameter only on the client. If NetWare/IP is already installed on the client, you must edit the C:\NWCLIENT\NET.CFG file and add the parameters under the NWIP section. For example: PREFERRED DSS boston 127.39.1.0 129.0.0.0 19.20.1.1 120.5.0.0 NEAREST NWIP SERVER boston 127.39.128.0 150.100.1.1 127.39.0.0 CONFIGURING THE NETWARE/IP SERVER To configure the Preferred DSS parameter on the NetWare/IP server, use the UNICON utility. At the UNICON utility's Main Menu, select the following: -> Manage Services -> NetWare/IP -> Configure NetWare/IP Server -> Preferred DSSes: The Preferred DSSes (Host/IP Address/Network) screen appears. For example: Preferred DSSes (Host/IP Address/Network) Preferred DSS #1: 20.19.0.0 Preferred DSS #2: 120.5.1.1 Preferred DSS #3: 127.39.1.0 Preferred DSS #4: 128.0.0.0 Preferred DSS #5: sanjose ============================================================ 2D. Optimizing NetWare/IP for WAN Environments ============================================================ New optional parameters are defined on the NetWare/IP server that optimize NetWare/IP under certain conditions. For a NetWare/IP domain configured to span WAN links, you can configure the Tunable parameters for the following conditions: - For a NetWare IPX client that occasionally times out or gets disconnected while accessing remote servers - To control the network traffic between DSS servers and NetWare/IP servers, and between the primary DSS server and secondary DSS servers To optimize a NetWare IPX client that occasionally times out or gets disconnected while accessing remote servers, you can configure the Ticks Between Nodes Tunable parameters. These parameters specify the approximate one-way time for a packet to travel, in ticks, between two NetWare/IP nodes on the same IP subnetwork, same IP network, and different IP networks. A tick equals 1/18th second. To configure these parameters use the UNICON utility. At the UNICON utility's Main Menu, select the following: -> Manage Services -> NetWare/IP -> Configure Primary DDS -> Tunable Parameters The Tunable Parameters screen appears. For example: Tunable Parameters UDP Port Number for NetWare/IP Service: 43981 DSS-NetWare/IP Server Synchronization Interval: 5 Primary-Secondary DSS Synchronization Interval: 5 Maximum UDP Retransmissions: 3 UDP Checksum? No Ticks between Nodes on the Same IP Subnet: 2 Ticks between Nodes on the Same IP Net: 4 Ticks between Nodes on Different IP Nets: 6 Configure the last three parameters on the list: - Ticks between Nodes on the Same IP Subnet: - Ticks between Nodes on the Same IP Net: - Ticks between Nodes on Different IP Nets: The example shows the defaults, which in most cases are sufficient. You can estimate the time for a packet to travel between nodes on the same subnetwork, same network, and different networks, by using the NetWare PING utility. If modifying the Ticks Between Nodes Tunable parameters does not completely solve your timeout problems, you can configure the NetWare/IP servers for host/networks across slow WAN links from which they send and receive packets. You should specifically modify the tick values on those NetWare/IP servers that act as IPX/IP gateways and/or send and receive packets over slow WAN links. You should specify a remote IP network/host address and the approximate one-way time (in ticks) to ping a remote host on the other side of the slow link using the UNICON utility. You can specify up to five network/host-tick pairs. At the UNICON utility's Main Menu, select the following: -> Manage Services -> NetWare/IP -> Configure Primary DDS -> Slow Link Customizations: The Remote Access Via Slow Links screen appears. For example: Remote Access Via Slow Links Network/Host IP Address Tick Value atlanta 2 127.39.0.0 20 Use the NetWare Ping utility to estimate the time for a packet to travel the slow links. To access the Ping utility, enter LOAD PING ip_address at your system prompt. Use the average that the PING utility calculates. To optimize the network traffic between DSS servers and NetWare/IP servers, and between the primary DSS server and secondary DSS servers, you can modify the following Tunable parameters on the primary DSS server. Using the UNICON utility, access the Tunable Parameters screen as previously described and modify the following: - DSS-NetWare/IP Server Synchronization Interval, which specifies how often a NetWare/IP server queries a DSS server for updated information. The default is five minutes. If you want the latency between the servers and their DSS servers to be small at the expense of extra local traffic, then you should specify a smaller value for this parameter (particularly if your configuration gives each site its own DSS server). - Primary-Secondary DSS Synchronization Interval, which specifies how often a secondary DSS server queries the primary DSS server for update information. The default is five minutes. If you reduce the traffic between the primary and the secondary DSS servers at the expense of higher DSS-DSS latency (if your configuration spreads DSS servers across WANs), then you should specify a larger value for this parameter. ============================================================ 2E. Setting up Forwarding NWIP/IPX gateways ============================================================ When a NWIP server is configured as a non-forwarding gateway, it will not send information it learned from the IPX side to the DSS. Note that the default is set as non-forwarding gateway when this patch is applied. Caveat: There are some side-effects associated with using a non-forwarding gateway. A NetWare/IP client, connected to a non-forwarding gateway, may be able to see a server using "slist" and yet not be able to connect to that server. This can also be evidenced by doing "display servers" on the console of the non-forwarding gateway. Therefore, it is not encouraged to have any non-forwarding gateway. One should carefully designate one or two servers as forwarding gateways and avoid having other servers as gateways (forwarding or non-forwarding) on the network. The forwarding feature can be enabled(disabled) either by specifying a command line switch at load time or through UNICON under the configure NetWare/IP server option. To enable (disable) forwarding from the system console, you should type load nwip /forward=[yes|no] CONFIGURING THE NETWARE/IP SERVER To configure the forward IPX to DSS parameter on the NetWare/IP server, use the UNICON utility. Start at the UNICON utility's Main Menu and select the following: -> Manage Services -> NetWare/IP -> Configure NetWare/IP The NetWare/IP Server Configuration screen appears, as shown: NetWare/IP Server Configuration NetWare/IP Domain: nwip.novell.com Preferred DSSes: Initial DSS Contact Retries: 3 Retry Interval: 4 seconds Slow Link Customization: Forward IPX Information to DSS? No Select the Forward IPX Information to DSS field, and specify your selection. Note: a) Forwarding cannot be changed dynamically. The command-line option /forward=yes (/forward=no) can be used only at load time (not at run-time), and b) Forwarding specification on the command line always overrides the forwarding specification in the nwparams file. c) When NWIP is loaded with the option "/forward=no" for the first time, it can be loaded again with the option "forward=yes", and it will dynamically change to a forwarding gateway, but not vise versa. If you want to change the forwarding gateway to a non-forwarding gateway, you have to unload and reload the NWIP again. ============================================================ 3. Registered/Unregistered DSSes ============================================================ Registered DSS Server A registered DSS server is visible to all NetWare/IP nodes through DNS. Each registered DSS server has a corresponding NS records in the DNS database, which identifies it as a name server for the NetWare/IP domain. When a NetWare/IP host queries DNS for the location of the nearest DSS server, DNS will only return a listing of registered DSS servers, because these are the only DSS servers it knows about. Unregistered DSS Server An unregistered DSS server is not registered with DNS. Thus, a NetWare/IP node cannot locate an unregistered DSS server by issuing a DNS query. Instead, the NetWare/IP node must be provided the name or address of the unregistered DSS server as part of its preferred DSS server listing. For example, you may want to designate a DSS server that is isolated from the rest of the NetWare/IP internetwork by a WAN link as an unregistered DSS server to prevent NetWare/IP servers from redirecting their queries to this DSS server when other closer DSS servers are busy or down. Using unregistered DSS servers can help in overcoming a deficiency of most DNS implementations -- a reply to a DNS query cannot exceed ~1.5K bytes. If there are more nameservers than a DNS packet can accomodate, all nameserver entries may not be returned in response to an NS query. This deficiency of DNS implementations can be bypassed by using unregistered DSS servers. An administrator can use an unregistered DSS to designate exactly which DSS server a NetWare/IP node should use. This gives the administrator better control of DSS server utilization and load balancing. ============================================================ 4. Using the /v Switch ============================================================ Use the /v (Verbose) switch when you load the NWIP.EXE file the first time(for example, nwip /v), to display status messages on the screen. These messages indicate the status of the communication between the client and the DNS and DSS servers. For example: C> nwip /v NetWare/IP IPX Far Call Interface Emulator v2.10 (950322) (C) Copyright 1990-1995 Novell, Inc. All Rights Reserved. This is a post NWIP v1.1 client Resolving NWIP domain NWIP1.TEST.NET ************************************ Sending DNS Query to address: 127.74.7.114 Responding DNS address: 127.74.7.114 Resolving NWIP SOA record from DSS ************************************ Sending DNS Query to address: 127.74.7.114 Responding DSS address: 127.74.7.114 Trying to get parameters from DSS: 127.74.7.114 Successfully received parameters from DSS: 127.74.7.114 Configuration: Node address: 127.74.6.79 UDP Port: 43981 43982 Checksum: No When you load the NWIP.EXE file with the /v anytime after that, no status messages appear on the screen. For example: C> nwip /v NetWare/IP IPX Far Call Interface Emulator v2.10 (950322) (C) Copyright 1990-1995 Novell, Inc. All Rights Reserved. This is a post NWIP v.1.1 client TSR. *DSS address: 127.74.7.114 NO_ANS Count: 0 DSS address: 129.23.3.1 NO_ANS Count: 1 DSS address: 19.6.7.1 NO_ANS Count: 2 *NWIP Server address: 127.74.7.114 NO_ANS Count: 0 NWIP-210-13: NetWare/IP has already been loaded. EXPLANATION: * - Indicates the current DSS or NetWare/IP server that the client is communicating with found NWIP servers in its cache for further references. NO_ANS Count - The number of times the node has not answered a query requested by the NetWare/IP client found NWIP servers in its cache for further references. ============================================================ 5. Known problem ============================================================ When NWIPADM.NLM is loaded within the UNICON utility, manually unloading it with unload NWIPADM or unistop at the server console will result displaying the following error message: !!CLIB ERROR!! Screen for process=DA7050, NCS=BFD228 not found in _DestroyThread This will not cause any functionality problem to NetWare/IP, you can ignore that.