NOVELL TECHNICAL INFORMATION DOCUMENT TITLE: Installation of PTF 41X series on 3.1X server DOCUMENT ID: TID250011 DOCUMENT REVISION: A DATE: 23SEP93 ALERT STATUS: Yellow INFORMATION TYPE: Issue README FOR: NA NOVELL PRODUCT and VERSION: NetWare for SAA 1.3 ABSTRACT: The installation instructions for PTF 410, PTF 411, PTF 414, and PTF 415 if installed in a NetWare 3.11 or 3.12 server. _________________________________________________________________ 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 INSTALLATION INSTRUCTIONS: How to Install the PTF41X Series on a NetWare 3.11 or 3.12 Server: 1. If you have not already ready read PTF41X.TXT, it is very important that you do so. 2. Install Simple Network Management Protocol (SNMP) using the SNMP update diskette included in your NetWare for SAA 1.3 product. If you have already installed SNMP, skip to III. The installation process will check to be certain that SNMP is installed before proceeding. Note that SNMP does NOT support remote installation. SNMP must be installed with the SNMP diskette or from a NetWare partition, it cannot be installed from a DOS partition. To Install SNMP Remotely: You must use RCONSOLE to copy all files to the remote target server. Use RCONSOLE to run Install, specifying the input to be the SNMP-1 directory where you copied the files from the SNMP diskette. From the NetWare console: a. Type LOAD INSTALL . b. Select Product Options . c. Press . d. Enter the full pathname of the 'SNMP-1' diskette or where the files are to be copied (for a NetWare partition only). For example: volume:\SYSTEM\NETWARE\SNMP-1 (See Note below) NOTE: The SNMP diskette for SAA 1.3.14 was SNMP-1, and the diskette for SAA 1.3.A is SNMP_1. Make sure you have the directory and path correct depending upon which SNMP diskette you have. 3. To initiate the installation, perform the following operations at the NetWare console: a. Type LOAD INSTALL . b. Select Product Options . c. Press . d. Enter the full pathname of the CEUPDATE directory. Include \DISK1 at the end of the pathname as shown in the example below: volume:\SAA13\CEUPDATE\DISK1 The installation process checks to see if SNMP is not installed or if it is out of date. If so, the installation terminates with the following message: SNMP has not been installed. Update system with the software from the SNMP diskette packaged with the 1.3 NetWare for SAA Product. Installation will now terminate. Next, the install process checks for the existence of up-to-date operating system and driver files. If it finds that the critical files (CLIB.NLM, STREAMS.NLM, etc.) are out of date, the installation copies all of the system files from DISK3 of the COMMEXEC update directory (CEUPDATE\DISK3). It will give you a chance to abort the installation and backup the files. If out-of-date files are detected, the following message is displayed: NetWare operating system files will be overwritten as specified in the NetWire README file. To preserve files, exit and backup, then reinstall the Communication Executive. NOTE: All of the NetWare 3.11 System files from COMMEXE3.EXE will be copied to the volume:SYSTEM directory during the Communication Executive installation. Files will NOT be down rev'ed. Back up any older versions before installing COMMEXEC. Next, Btrieve will be checked, and if it is outdated, the installation will give you a chance to stop and backup if necessary. If you continue BTRIEVE will be updated. After BTRIEVE is updated the installation exits, and prompts you to bring down the server. This is so the new BTRIEVE gets loaded. Bring down the server, and then restart it. At the server console LOAD INSTALL again and select PRODUCT OPTIONS and press . Insert the full path name to the COMMEXEC files and this time the COMMEXEC install will install the COMMEXEC files. 4. After the COMMEXEC installation is complete, install the NetWare for SAA files as follows: a. Type LOAD INSTALL . b. Select Product Options . c. Press . d. Enter the full pathname of the NWSAAUPD directory. For a NetWare partition installation, include \DISK1 in the path as shown below: volume:\SAA31\NWSAAUPD\DISK1 e. After you have installed the Communication Executive and NetWare for SAA check to ensure that your AUTOEXEC.BAT conforms to the sample shown below. f. Down the server and restart it (with the SERVER command). You must do this to ensure proper operation of the Communications Server after you have installed NetWare for SAA. Sample AUTOEXEC.NCF for NetWare 3.11 ------------------------------------ In this example, the same adapter card is used for both LAN and host access. The lower-case entries indicate items that you must fill in with your own values (for the file server name and the IPX internal network number.) FILE SERVER NAME file_server_name IPX INTERNAL NET internal_network_number LOAD CLIB LOAD LSLENH LOAD SPXFIX2 LOAD BTRIEVE -U=1 -P=4096 -F=20 -H=60 -L=20 -C SET MAXIMUM PACKET RECEIVE BUFFERS=2000 ; LAN CONNECTION: LOAD NE2000 INT=3 PORT=300 FRAME=ETHERNET_802.3 ; HOST CONNECTION: LOAD NE2000 INT=3 PORT=300 FRAME=ETHERNET_802.2 NAME = xxxx ; where xxxx is the Logical Adapter Name from CSCON Sample AUTOEXEC.NCF for NetWare 3.12 ------------------------------------ In this example, the same adapter card is used for both LAN and host access. The lower-case entries indicate items that you must fill in with your own values (for the file server name and the IPX internal network number.) FILE SERVER NAME file_server_name IPX INTERNAL NET internal_network_number LOAD CLIB LOAD BTRIEVE -U=1 -P=4096 -F=20 -H=60 -L=20 -C SET MAXIMUM PACKET RECEIVE BUFFERS=2000 ; LAN CONNECTION: LOAD NE2000 INT=3 PORT=300 FRAME=ETHERNET_802.3 ; HOST CONNECTION: LOAD NE2000 INT=3 PORT=300 FRAME=ETHERNET_802.2 NAME = xxxx ; where xxxx is the Logical Adapter Name from CSCON INSTALLATION NOTES 1. Remote Installation from a local server's diskette drive may cause problems. If you attempt to do a remote installation and use the local server's diskette drives to install NWSAA 1.3 expect the following error message to appear in certain situations: "Error, BuildCDProductsList returned -1 Press Any Key To Continue." At this point NWSAA installation will fail. The problem is due to the fact that the diskette drive access is slow enough that the SPX connection established to the remote server will timeout, in which case the install process can't write to the PRODUCTS.DAT file thus causing this error message and install to fail. This also depends on network traffic. In some situations this remote install procedure from diskette will work with no problems. There are two possible solutions: þDo remote installs from DOS hard drive or NetWare volume if possible. or þIncrease both the remote and local server's "SPX WATCHDOG ABORT TIMEOUT" and "SPX ACK WAIT TIMEOUT" SPX timeout values using SPXCONFG.NLM. NMA for NetView (NetView Ready) experiences the same problems as above for remote installs from diskette drive. 2. Loading and Unloading a. Load the protocol stacks that will be required by Communication Executive prior to loading COMMEXEC.NLM. If you do load COMMEXEC.NLM, and it has been configured to require other protocol stacks (SPXS, Appletalk, or TCP/IP), and the protocol stack has not been loaded, the following error message will display: "CE: unable to build stream driver ..." b. The CSSTATUS statement should not appear immediately after the LOAD COMMEXEC statement in an AUTOEXEC.NCF file. You may either issue the CSSTATUS statement manually, or insert another statement between the CSSTATUS and LOAD COMMEXEC. c. Token Ring Drivers Node Address message With the ODI Token Ring drivers, specifying a node address in the LOAD statement causes the following message to appear on the system console at load time: "WARNING: Token-NU-127: The local bit in the node address override was set" The message is informational, to let you know that a locally administered node address has been specified. d. The LOAD command for EtherNet LAN drivers that are to be bound to IPX must include the following parameter (as shown in the sample AUTOEXEC.NCF above): FRAME=ETHERNET_802.3 This FRAME= statement is necessary to match the workstation configuration (as well as file server configurations). The previous default was ETHERNET_802.3. The new default is ETHERNET_802.2. If your system uses the PU concentrator feature with WEEAS.EXE, IPX is bound to both ETHERNET_802.2 and ETHERNET_802.3. e. Make sure you have the LSLENH and SPXFIX2 load statements before loading any LAN adapters. 3. When using the Newport Board a. Installing NWSAA while CSL.NLM is loaded will cause problems. Problems have been encountered if NWSAA is installed and you are implementing a QLLC connection to a host with the Newport X.25 driver, or SNALinks has been installed while the CSL.NLM is loaded. The symptom is that the Newport X.25 driver will not be able to read its configuration database. b. When using the Newport Driver and X.25 (QLLC), occasionally, calls will not be made from the X.25 driver. The workaround for this is: >CSUNLOAD >UNLOAD >LOAD >CSLOAD 4. X.25 Drivers Novell recommends using the latest X.25 drivers for your X.25 adapter. Both Novell and Newport Systems have new drivers that support NetWare for SAA 1.3. 5. SDLC a. Running SDLC on servers faster than 50 Megahertz can cause problems when loading the R3SDLC.LAN driver. This will cause the following message to display when the SAA profile is loaded: "DLCI ERROR: Adapter requested by NWSAA was not found. To recover, reload R3SDLC.LAN before you load the SAA profile." b. The following message at the console lets you know that the system had to allocate additional ECBs for the SDLC adapter: "R3SDLC: Please increase minimum packet receive buffers in STARTUP.NCF file and increase maximum packet receive buffers in AUTOEXEC.NCF." c. IBM MPA SDLC Adapter -- AutoRegister Memory On any Micro Channel server that uses the IBM MPA SDLC board, add the following command to AUTOEXEC.NCF: SET AUTOREGISTER MEMORY ABOVE 16MB = OFF The IBM MPA SDLC board will not work properly on a machine that addresses memory above 16MB. The message occurs more frequently when the minimum packet receive buffers parameter has been set to less than the recommended number of 500. Operation will continue normally if memory is available for this ECB to be allocated. d. The Eicon SDLC driver takes up to 15 seconds to load and initialize. This means that it may be necessary to insert a command or procedure in AUTOEXEC.NCF to delay the execution of subsequent CSLOAD commands for profiles that use the EICON driver in AUTOEXEC.NCF. The Eicon driver must be loaded after loading the Communication Executive. The public domain NLM called DELAY.NLM is one example of a method you could use to delay execution of the CSLOAD command. Another alternative is to issue the CSLOAD command manually from the NetWare console. 6. NetWare for SAA 1.3 supports only two host connections. You may only install two licensed copies of NetWare for SAA on a single server. If you try to install a third copy on the server, one of the following things will happen: a. If the third copy is a newer version number than the copies already installed, the server will be updated with the new software. b. If the third copy is the same, or a lesser version, the installation will fail. To increase the number of sessions, first remove at least one of the copies of NetWare for SAA from the server and reinstall with the copy containing the number of licenses you want. Note that any profile information will be lost unless you backup the profile using SAACOPY to copy it to another server. 7. On a PS/2 Model 95 server, running two NetWare for SAA Synchronous Adapters causes the following messages to be displayed more than once at the NetWare console: 'Spurious Hardware Interrupt 3 Detected' and 'Spurious Hardware Interrupt 4 Detected.' The following NetWare command will stop these messages from being displayed: SET DISPLAY SPURIOUS INTERRUPT ALERTS = OFF 8. NIC Drivers Novell recommends the use of ODI drivers, for both the host connection and the LAN connection. 9. Disaster Recovery Tips Once you have installed the PTFs, we recommend that you backup CSMASTER.DBA to a diskette. If CSMASTER.DBA should become corrupted because of a server crash, you may then copy CSMASTER.DBA to the SYSTEM subdirectory and restart the system. The following symptoms may indicate corruption of CSMASTER.DBA: * Unable to load a service profile * Unable to attach to a Communication Server through CSCON * Receive an error message after loading the Communication Executive * Cannot access the audit trail or event log 10. Mainframe and AS/400 Concurrent Access To access a 3270 session and a PC Support session concurrently from the same workstation, use RUMBA/400 offered by WallData, Inc. and IBM Corp., or use ATTACHMATE. At the present time, NetWare 3270 LAN Workstation for DOS does not support this configuration. 11. QLLC Support To support PVC links on a VM/CMS 9370, the host must be configured to retry QSM(SNRM) and QXID(XID) indefinitely. 12. Using the RUNCMD Query Server Using the RUNCMD 'Query Server' without any attributes will return the maximum number of connections supported as the number of NetWare OS licenses (max. number of NCP users) plus 100. The additional 100 connections reflect the capability of NetWare modules to use these connections. For an accurate number, subtract 100 from the value returned. The response from 'Query file or directory' may be incomplete if the "Maximum Frame Size to Transmit Inbound" defined in the host connection of the service profile used to send RUNCMDs is less than 521 (that is, 256). The ideal size is 1033, but 521 does work. The user name in RUNCMD does not support a group name. 13. OS/2 Software for NWSAA Access Support This release has modules needed for OS/2 NWSAA Access Support. These files are copied to the volume:SYSTEM\NWSAA subdirectory during installation. WEEAS.EXE WCM.DLL WEEAS.ICO WEEAS.HLP To install OS/2 NetWare for SAA Access Support software, create a subdirectory on the OS/2 machine, and copy these files to it. Then create a new program item with the Presentation Manager. Use WEEAS.EXE as the program filename when creating the new program item. After loading this program, use Connect, Disconnect, etc. to log in, disconnect, etc. 14. When upgrading from NetWare for SAA 1.2 to 1.3, the upgrade automatically creates a default adapter name. Execute CSCON and change the Logical Adapter Name entry so that it matches the NAME = parameter in the AUTOEXEC.NCF. 15. If you are using a NE2-32 LAN adapter, the correct Logical Adapter Name is NE2_32. Modify the Logical Adapter Name entry in CSCON and NAME = parameter in the AUTOEXEC.NCF accordingly. 16. If NetWare for SAA is already installed on a NetWare 3.11 server, and you plan to install the MPR 2.1 product, BE SURE NOT TO COPY OVER THE BTRIEVE.NLM WHICH CAME WITH MPR. It is an older version. OTHER NOTES 1. If NetWare for SAA is unloaded (with CSUNLOAD) and then reloaded immediately (with CSLOAD) while a large number (i.e., approximately 100) of downstream PUs are connected to it, NetWare for SAA may abend with the following error: FSM_XID3_NEG_PROTO. This error occurs only if the downstream PUs are also running NetWare for SAA on a server. To avoid this problem, wait for about two minutes between unloading and reloading NetWare for SAA. 2. Do not unload DLM while NetWare for SAA is loaded. 3. Unexplained host disconnections have occurred when using the NetWare for SAA Synchronous Adapter with a Zilog chip at board location U4. Adapters with an AMD chip at location U4 do not experience this problem. 4. PU 2.1 and PU 2.0 Profile Information NWSAA 1.3 will support any combination of PU 2.0 or PU 2.1 profiles. The maximum amount of profiles is two per server. You can have a server configured for two PU 2.0 profiles, or two PU 2.1 profiles, or one PU 2.1 and one PU 2.0 profile. The variation from this is when PCSUPPORT is one of the PU 2.1 profiles; when this is the case you cannot have the other profile be another PCSUPPORT PU 2.1. You can have a SNALINKS PU 2.1 profile and a PCSUPPORT PU2.1 profile on the same server. Patch History: See PTF410.TXTÿ