NOVELL TECHNICAL INFORMATION DOCUMENT TITLE: Installation of PTF 41X series on a 4.0X server DOCUMENT ID: TID250012 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 in a NetWare 4.0 or 4.01 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 To Install on a NetWare 4.0 or 4.01 server. 1. If you have not yet read PTF41X.TXT it is very importand that you do so. 2. Bindery Emulation must be enabled on the NetWare 4.0x server on which NetWare for SAA 1.3 installed. The SET BINDERY CONTEXT command in AUTOEXEC.NCF or STARTUP.NCF enables bindery emulation. In addition, the NetWare 4.0x server must have a READ/WRITE, or master replica of its partition, in order for bindery emulation to be enabled. Please refer to the NetWare 4 System Administration Guide. CAUTION: Do not change the Bindery Context (Bindery Emulation) once NetWare for SAA 1.3 is installed. Doing so will require you to reinstall NetWare for SAA 1.3 again. 3. Do not install SNMP on a NetWare 4.X server since it is already present on the system. 4. To install the Communication Executive update, issue the following commands at the NetWare console: a. Type LOAD INSTALL . b. Select Maintenance/Selective Install . c. Select Product Options . d. Press . e. 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 5. Perform a similar operation to install NetWare for SAA: a. Type LOAD INSTALL . b. Select Maintenance/Selective Install . c. Select Product Options . d. Press . e. Enter the full pathname of the NWSAAUPD directory. Include \DISK1 at the end of the pathname, as shown in the example below: volume:\SAA13\NWSAAUPD\DISK1 6. After you have installed the Communication Executive and NetWare for SAA, check to make certain that your AUTOEXEC.NCF conforms to sample AUTOEXEC.NCF below. 7. 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 4.0 ----------------------------------- In this sample file, 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 bindery context and the file server name and the IPX internal network number.) SET BINDERY CONTEXT = bindery_context 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 installation of NWSAA 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. a. Remote installs should be done from DOS hard drive or NetWare volume if possible. OR b. Increase both the remote and local server's SPX timeout values, "SPX WATCHDOG ABORT TIMEOUT" and "SPX ACK WAIT TIMEOUT", using SPXCONFG.NLM. NMA for NetView (NetView Ready) experiences the same problems as above for remote installs from diskette drive. 2. CSADMIN User for CSCON A user called CSADMIN is created automatically during the SAA installation. This user has supervisor equivalent in the NW 3.11 sense, to the SAA server and may be used to configure the SAA server and run CSCON. The password for CSADMIN is "NWSAA", you should use NWADMIN and change the password after the SAA installation to maintain security. Creating a User Other than CSADMIN for CSCON In order for a user to be able to log in to CSCON and configure the CS under NetWare 4.0, you must create a user under the Organizational Unit (context) where SAA has been installed. The user must then be given 'Supervisor-Equivalent' rights (in the NetWare 3.11 sense). This can be accomplished by making the user's security equivalent to the File Server object. The procedure below outlines how to do this, using the NWADMIN utility running on a workstation: a. Log in as NetWork Administrator (Admin) to the NetWare 4.0 server. b. Load NWADMIN from Windows. c. Select the Organizational Unit (context) where SAA is installed. d. Click on OBJECT from the NetWare Administrator screen. e. Click on CREATE. f. Select USER from the NEW OBJECT LIST, and click OK. G. Fill in the user information, login name, and last name; then select the ADDITIONAL PROPERTIES box and click OK. h. Click on the PASSWORD RESTRICTIONS box on the right of the screen; check the REQUIRE PASSWORD box and click on the CHANGE PASSWORD bar. Type the password in both boxes, and click OK. i. From the same screen, click on the SECURITY EQUIVALENCIES box in the right lower corner of the screen. j. Click on the ADD box, and select the FILE SERVER OBJECT where SAA is installed from the OBJECTS LIST. Click OK. The file server object will now be shown in the SECURITY EQUAL TO window. Click OK to exit. k. The user just generated will now be able to log in to the server and run CSCON to configure SAA service profiles. 3. Load Information a. OS Ring Protection NetWare for SAA 1.3 can only be loaded and executed in the OS Domain at Ring 0 under NetWare 4.0. NetWare for SAA 1.3 cannot exist in the OS Protected Domain at rings 1, 2, or 3. b. 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 would display: "CE: unable to build stream driver ..." c. 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 the LOAD COMMEXEC. d. STREAMS NLM - The 4.0X installation for NWSAA copies a new STREAMS.NLM module to the server. If this module does not get loaded into memory, you may experience an ABEND while performing a DOWN operation. To avoid this problem, make certain that you down the server after installation to ensure that the new STREAMS.NLM gets loaded. e. The Eicon 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. f. 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. g. 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. h. Make sure you have the LSLENH and SPXFIX2 load statements before loading any LAN adapters. 4. Binding and Unbinding a Transport Protocol To bind a transport protocol manually, issue the following command at the NetWare console: CSBIND [spx|appletalk|tcp-ip] To unbind a transport protocol manually, issue the following command at the NetWare console: CSUNBIND [spx|appletalk|tcp-ip] Under NetWare 4.0, CSUNBIND is the only method of unloading a transport protocol while workstations are connected to NetWare for SAA. If you need to remove Directory Services from the server that has NetWare for SAA installed on it, first backup the profiles (using SAACOPY), then remove NWSAA and COMMEXEC from the server. After reinstalling the Directory Services, you should reinstall the COMMEXEC and NWSAA. Then, copy the profiles back to the server, using SAACOPY. 5. 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. 6. 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. We have observed that Netware 4.01 may generate a spurious server-down events when objects are created in the directory services. These events may cause the CSL.NLM to enter a state where it will no longer allow drivers to get their configuration and load. To avoid this problem, make certain that CSL is unloaded and reloaded again after performing any operations such as loading the Newport X.25 driver, running CSCON to configure profiles, groups or ACL's. There is a patch for Directory Services, that will eliminate the problem described above. The name of the patch is DSPAT.ZIP and it is on NETWIRE. This directory services patch corrects several other problems related to directory services. If you are using the CSL.NLM you should obtain this directory services patch and follow the DSPAT.TXT file to install the patch. 7. 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. 8. Novell recommends the use of ODI drivers, for both the host connection and the LAN connection. 9. 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" This message is informational, to let you know that a locally administered node address has been specified. 10. Novell recommends the use of 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. At the present time, only the Newport driver is available for operation in a NetWare 4.0 environment. 11. 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 12. 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. 13. QLLC Support To support PVC links on a VM/CMS 9370, the host must be configured to retry QSM(SNRM) and QXID(XID) indefinitely. 14. 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. 15. 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. 16. When upgrading from NetWare for SAA v1.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. 17. 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. 18. NetWare Update Considerations If NetWare for SAA 1.3 is installed on a NetWare 3.11 server that is later upgraded to NetWare 4.0, the first invocation of COMMEXEC.NLM (in the upgraded NetWare 4.0 system) will automatically perform the necessary conversion to enable COMMEXEC.NLM to run in the NetWare 4.0 environment. If you plan to upgrade more than one NetWare for SAA server from NetWare 3.11 to NetWare 4.0 to the same Organizational Unit (context) in a NetWare 4.0 directory tree, after each upgrade issue the following command on the server console to upgrade each NetWare for SAA server: LOAD CSUPDT40 NOTE: Only users defined in the same organizational unit in which NetWare for SAA has been installed can access NetWare for SAA services. Login control and ACL checking are done in the same context in which NetWare for SAA is installed. 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. 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." 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. 5. 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 6. Do not unload DLM while NetWare for SAA is loaded. 7. 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. 8. When using the Newport Driver and X.25 (QLLC), occasionally, calls will not get made from the X.25 driver. The workaround for this is: >CSUNLOAD >UNLOAD >LOAD >CSLOAD 9. Running SDLC on servers faster than 50 Mhz 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. 10. 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. 11. 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. 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. 12. 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 13. 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. ÿ