NetWare/IP 2.1 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. DISCLAIMER Novell, Inc. makes no representations or warranties with respect to this software, and specifically disclaims any express or implied warranties of merchantability, title, or fitness for a particular purpose. Distribution of this software is forbidden without the express written consent of Novell, Inc. Novell will not be responsible for any data loss that might result from implementing this software. Novell strongly recommends a backup be made before installing this software. *************************************************************************** CAUTION *************************************************************************** Always back up your system before implementing any program/utility revision involving the low-level functions of NetWare, including re-linking of operating system .OBJ files, bindery utilities, and drive and volume operation. *************************************************************************** CONTENTS *************************************************************************** Welcome to the NetWare/IP 2.1 product! This document contains last-minute information that is not included in the documentation. It includes the following sections: Installing the Product Installing the Software and Online Documentation Editing the Local SYS:ETC\HOSTS File Before Installing the Software Setting Up an Installation Directory on a Server Volume Using XCONSOLE to Install Over IP Installing NetWare 4.1 Over an IP Network Installing with the UnixWare NUC Package Installing the UNICON Management Groups Manually NetWare Language Support Configuring the Product Adding the UNISTART Command to the AUTOEXEC.NCF file Configuring Servers with More Than One Network Adapter Card Modifying the DSS Dedicated Mode Parameter Modifying the Maximum Number of UDP Datagrams and TCP Connections Modifying the Slow Link Customizations Parameter Supporting Secondary DSS Servers with Multiple IP Addresses Default Tick Values Disabling DNS Increasing the Maximum Size of the AUDIT.LOG File Setting up SAP/RIP Filtering Stopping a Server Running Both NetWare/IP and DSS Running the Product with Other Software Compatibility With Previous Versions of NetWare/IP Compatibility With NetWare 4.1 Compatibility with NLSP Compatibility with Broadcast Applications SFT III Support Troubleshooting What to do if TCP/IP is Not Available What to do if there is a DSS Database Error Using DynaText Installing the DynaText Online Document Viewer Uninstalling the Online Documentation ====================== Installing the Product ====================== Installing the Software and Online Documentation ================================================ The following lists the number of diskettes and their content: NWIP1-NWIP2 Contain the software NWIP2-NWIP5 Contain the online documentation Editing the Local SYS:ETC\HOSTS File Before Installing the Software =================================================================== The SYS:ETC\HOSTS file that installs with NetWare 4.10 contains several sample host entries that do not belong in the file. Before you install the product software, you should edit the SYS:ETC\HOSTS file to ensure that these entries do not exist. If the following entries exist in your HOSTS file, delete them: 127.0.0.1 loopback lb localhost # normal loopback address 130.57.4.2 ta tahiti ta.novell.com loghost 130.57.6.40 osd-frog frog 130.57.6.144 sj-in5 in5 192.67.172.71 sj-in1 in1 192.67.67.20 sri-nic.arpa nic.ddn.mil nic 26.2.0.74 wsmr-simtel20.army.mil simtel20 If you install the product without deleting these entries and you use local DNS, you can use UNICON to delete the entries. Setting Up an Installation Directory on a Server Volume ======================================================= If you plan to install NetWare/IP using a server-based installation, you must copy each installation diskette to a directory you create on your server. Some of the files required for NetWare/IP have long filenames. Therefore, the directory you create for your server-based installation must have a short name. If you do not use a short directory name, some of the required files may not be installed properly because the path name of the file is too long. For example, consider creating a directory such as the following: SYS:\N For more information on setting up a server-based installation, refer to Chapter 4 of the NetWare/IP Administrator's Guide. Using XCONSOLE to Install Over IP ================================= In order to install a product on a remote NetWare server across an IP network, you must use the following procedure: 1. Copy the NWCCSS.NLM from the NWIP2 diskette to the SYS:SYSTEM directory of the server on which you plan to install NWIP. 2. Copy XCONSOLE.NL2 from the NWIP2 diskette to SYS:SYSTEM\XCONSOLE.NLM 3. Copy XCONSOLE.MS2 from the NWIP2 diskette to SYS:SYSTEM\NLS\4\XCONSOLE.MSG 4. Copy TELNETD.NL2 from the NWIP2 diskette to SYS:SYSTEM\TELNETD.NLM 5. Copy TELNETD.MS2 from the NWIP2 diskette to SYS:SYSTEM\NLS\4\TELNETD.MSG 6. If XCONSOLE is already running on the remote server, you must unload and reload it before proceeding. 7. You can now telnet to the remote server and begin installing the product. 8. When NWIP installation finishes copying the files to your server, it prompts you to log in using the admin user object. If you are unable to log in, you must unload NETDB and then run UNISTART. You must then enter the following command at the server console prompt to create the UNICON management groups: LOAD UNICON /L INITNWIP UNICON will launch and prompt you to log in as admin. After you log in successfully, the installation program will finish the NetWare/IP initialization and unload UNICON. For more information on using XCONSOLE to install over the IP protocol, read XCONSOLE.TXT, which you can find on the NWIP2 diskette or in the server's SYS:SYSTEM directory. Installing NetWare 4.1 Over an IP Network ============================================ If you plan to install the NetWare 4.1 software using a server-to-server install over the IP protocol, you can obtain a software fix from NETWIRE that will enable you to perform this operation. Installing with the UnixWare NUC Package ======================================== If your server runs the NUC.NLM package delivered with UnixWare, you must unload NETDB.NLM before installing this product. To unload this module, type the following at the server console prompt: UNISTOP Installing the UNICON Management Groups Manually ================================================ If you are able to log in as ADMIN when you install the NetWare/IP software, the installation program creates the UNICON management groups described in Chapter 5 of the NetWare/IP Administrator's Guide. These management groups are created in the server's default context. Once the groups are created, you can delegate UNICON management tasks by adding users to the appropriate groups. Because the groups are created in the default context, group members who log in using the group user object can be authenticated at the local partition rather than at the root partition. If you change the server's default context or if NDS is not installed on the server when NetWare/IP is installed, you must create the groups manually by typing the following command at the server console prompt: LOAD UNICON /L INITNWIP NetWare Language Support ======================== NetWare/IP 2.1 only supports the English language. When you install NetWare/IP 2.1 on a NetWare server with the LANGUAGE parameter set to French, Italian, German, or Spanish, the NetWare/IP installation module will automatically load using English. There is no need for you to change the LANGUAGE parameter value. ======================= Configuring the Product ======================= Adding the UNISTART Command to the AUTOEXEC.NCF file ==================================================== Make sure that UNISTART.NCF is the last line in your AUTOEXEC.NCF file. You can modify the AUTOEXEC.NCF file using the INSTALL utility. Configuring Servers with More Than One Network Adapter Card =========================================================== If your server has more than one network adapter card, it also has more than one IP address. During installation, only the first IP address identified by TCP/IP is entered into the SYS:ETC/HOSTS file. After installation you must edit the SYS:ETC/HOSTS file and enter the remaining IP addresses used by the server. For example, suppose your server named sjf-argos has two IP addresses. In this case, you would make the following entries in the SYS:ETC/HOSTS file: 123.47.6.78 sjf-argos 123.48.6.8 sjf-argos Modifying the DSS Dedicated Mode Parameter ========================================== By default, the DSS server runs in dedicated mode. As its name implies, dedicated mode dedicates system resources to DSS activities. If you want to free up some system resources to enable you to run other NLMs on the server along with DSS.NLM, you can edit the DEDICATED_DSS line in the DSS section of the SYS:ETC\NWPARAMS file to disable or enable dedicated mode as follows: ° DEDICATED_DSS 0 (to disable) or ° DEDICATED_DSS 1 (to enable) After changing this parameter value, you must unload and then reload the DSS.NLM in order for the change to take effect. Modifying the Maximum Number of UDP Datagrams and TCP Connections ================================================================= The DSS NLM allows you to manually configure the maximum size of the UDP packet queues and maximum number of simultaneous TCP connections maintained by DSS for storing SAP and RIP packets. To reconfigure these parameters, add the following lines to the DSS section of the server's SYS:ETC\NWPARAMS file: MAX_UDP_PKTS (default: 64) MAX_TCP_CONNS (default: 16) where and are decimal integers greater than the default values. You must modify the NWPARAMS file on each DSS server where you want to change the defaults. After changing this parameter value, you must unload and then reload the DSS.NLM in order for the change to take effect. Modifying the Slow Link Customizations Parameter ================================================ If you modify the Slow Link Customizations parameter value, you must unload and reload the NetWare/IP server module for the change to take effect. Supporting Secondary DSS Servers with Multiple IP Addresses =========================================================== If a secondary DSS server has multiple IP addresses, you must add the following line to the DSS section of the server's SYS:ETC\NWPARAMS file: THIS_DSS_IPADDR Where is the preferred IP address for use by the DSS server component. Default Tick Values =================== The default tick values listed in Chapter 7 of the NetWare/IP Administrator's Guide have been changed. The new default tick values are as follows: ° 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 Disabling DNS ============= If you disable the NetWare DNS service on your server, the DSS service is also disabled. You can enable both services by enabling DNS. Increasing the Maximum Size of the AUDIT.LOG File ================================================= If you increase the maximum size of the AUDIT.LOG file, you must make sure the TCP/IP Physical Receive Packet size is set to a minimum value of 4202. Values less than 4202 may cause TCP/IP transmission errors. By default, the Physical Receive Packet size is set to 4202, however it can be modified using the STARTUP.NCF file. To ensure that the Receive Packet size is set to a minimum of 4202, check the STARTUP.NCF file for the following line: MAXIMUM PHYSICAL RECEIVE PACKET SIZE = This line appears in the file, you must ensure that the value is set to a minimum of 4202 or remove the line so that the system accepts the default value. Setting up SAP/RIP Filtering ============================ NetWare/IP gateways provide a means to connect IP and IPX networks. You can use one of the following methods to implement SAP/RIP filtering between the IP and IPX network segments when using a NetWare/IP gateway: 1. Filter IPX-side information from flowing to the IP segment. To do this, you must set up the server as a non-forwarding gateway as described in Chapter 8 of the NetWare/IP Administrator's Guide. A non-forwarding NetWare/IP gateway does not report SAP/RIP information learned from the IPX network to the DSS server. 2. Filter IP-side information from flowing to the IPX segment. To do this you must use the INETCFG and FLTCFG utilities provided with NetWare 4.1. First, bind IPX to the LAN card using the INETCFG utility. Then use the FLTCFG utility to filter outgoing SAPs/RIPs as required on the LAN card you configured. NOTE: FLTCFG can only control LAN bindings configured through INETCFG. You must bind IPX to the LAN card using INETCFG. In addition, FLTCFG requires that you only use one frame type per board. Therefore, you must use a separate LAN card for each frame type you are supporting. These are the only supported methods for implementing SAP/RIP filtering on a NetWare/IP network. Note the following SAP/RIP filtering limitations: - An IP-only server cannot filter incoming SAPs/RIPs - A NetWare/IP server with one LAN card where IPX is bound to two frame types cannot filter outbound SAP/RIP traffic selectively on one of the two frame types. ================================================= Stopping a Server Running Both NetWare/IP and DSS ================================================= When you stop a NetWare/IP server, the server reports its status to a DSS server. However, if the NetWare/IP server and the DSS server are running on the same machine, the NetWare/IP server would most likely report its status to the DSS server on the local machine. In order for the rest of the network to learn the status of the NetWare/IP server, the DSS would have to report the change to the primary DSS at the next database synchronization. However, if you down the server before the next synchronization, the change would not be reported to the rest of the network. Therefore, when you stop a server that is running both the NetWare/IP and DSS server components, you should use the following procedure: 1. Unload the NetWare/IP server 2. Force the DSS server to synchronize its database with the primary DSS by typing the following command at the server console prompt: LOAD DSS /SYNC 3. Wait a minute and then down the server. ======================================= Running the Product with Other Software ======================================= Compatibility With Previous Versions of NetWare/IP ================================================== NetWare/IP 2.1 is fully compatible with previous versions of NetWare/IP. However, you should upgrade your primary DSS server and all secondary DSS servers to NetWare/IP 2.1 to take full advantage of new features and functionality provided in this release. You do not have to upgrade your NetWare/IP servers and clients immediately. However, you should plan to migrate all your server and client nodes to 2.1 as soon as possible. In the interim, make sure that all of your NetWare/IP 1.1 server nodes have been upgraded to the NIP191 (or later) patch. When running multiple versions of NetWare/IP on the same network, keep in mind that you cannot manage your 1.1 servers using UNICON 2.1. Similarly, you cannot manage your 2.1 servers using UNICON 1.1. Refer to Chapter 4 of the NetWare/IP Administrator's Guide for more information on upgrading your NetWare/IP network. Compatibility With NetWare 4.1 ============================== NetWare 4.1 ships with some NLMs that are also on NetWare/IP diskettes. They are NETDB.NLM (located in the SYSTEM directory on the NWIP1 diskette) and V_NFS.NLM (located in the SYSTEM directory on the NWIP2 diskette). When installing NetWare/IP using the NetWare/IP-NetWare 4.1 integrated install, make sure that you select NO when prompted to overwrite these files. If you inadvertently overwrite these files, you can copy these files from NetWare/IP diskettes to the server after the NetWare 4.1 installation is complete. Compatibility with NLSP ======================= NetWare/IP is compatible with the NetWare Link Services Protocol (NLSP) in SAP/RIP Compatibility mode only. Compatibility with Broadcast Applications ========================================= You can run non-SAP/RIP broadcast applications in multiple NetWare/IP domains on the same subnet. However, to prevent routing loops you must make sure the NetWare/IP domains are using different UDP port numbers for NetWare/IP communications. SFT III SUPPORT =============== This product does not support SFT III. =============== Troubleshooting =============== What to Do if TCP/IP is Unavailable =================================== When using UNICON to log in to a remote server, you may get an error message indicating that TCP/IP is unavailable. This condition is temporary. If you receive this message, retry logging in to the server later. What to Do if there is a DSS Database Error =========================================== If you receive an error message indicating that there is a Btrieve error in the DSS database, you must reset the DSS database on the affected server. To reset the DSS database, type the following command at the server console prompt: load dss /resetdb ============== Using DynaText ============== Installing the DynaText Online Viewer ===================================== If you are installing the online documentation and the installation program detects that you already have the DynaText viewer installed, the installation program prompts you whether to overwrite the existing Dynatext viewer files. If you choose to overwrite the viewer files, you must ensure that there are no users accessing the viewer. If a user is accessing the viewer when the installation program tries to overwrite the files, the installation will fail. Uninstalling the Online Documentation ===================================== The UNINSTALL utility does not delete all NetWare/IP files from your server. After you uninstall the NetWare/IP 2.1 product, you must uninstall all files specified in Chapter 10 of the NetWare/IP Administrator's Guide. In addition, if you installed the online documentation on this server, you must also manually delete NetWare/IP document entries from the DynaText configuration file, SYS:\PUBLIC\SYSDOCS.CFG.