31Jul95 NetWare for DEC Access 1.1 This document provides information on: - configuring NetWare for DEC Access 1.1 for your particular installation - available third party products - hardware and memory requirements for running NetWare for DEC Access The document also includes tips for setting up and running DEC Access. For the latest information regarding Novell Labs Product Certification of data link adapters and LAN adapters, systems, and drivers, contact Novell Labs through the FaxBack System at the following telephone numbers: - 801-429-2776 (international and domestic) - 800-414-5227 (domestic only) Overview of NetWare for DEC Access ---------------------------------- NetWare for DEC Access is Novell's networking gateway for bidirectional connection of users and resources in the Digital Equipment Corporation (Digital) network environment and the NetWare environment. NetWare for DEC Access works with NetWare 3.12 and NetWare 4.1 or later. Terminal emulation applications running on desktop workstations connect to the NetWare for DEC Access server over any local area network (LAN) supported by NetWare: - token ring - Ethernet - ARCnet by means of IPX/SPX, TCP/IP, or AppleTalk protocols. NetWare for DEC Access NetWare Loadable Module (NLM) applications use the DEC/LAT protocol to connect to the DEC network over an Ethernet connection. Desktop users can log onto DEC VAX and Alpha AXP systems through NetWare servers running NetWare for DEC Access. NetWare for DEC Access also supports other NLM applications that work with NetWare for DEC Access to integrate the NetWare and Digital environments. These third-party NLMs include products that provide bidirectional print integration, E-mail integration, and file transfer. NetWare for DEC Access provides you with the following capabilities: - Standard Telnet Support. NetWare for DEC Access provides standard TCP/IP telnet client support for terminal access from standard telnet clients such as LAN WorkPlace and UnixWare. - Bidirectional Connectivity. Users of either NetWare or DEC systems have access to the resources on the other side of the NetWare for DEC Access server. These resources are made available through third-party software described in the NetWare for DEC Access Info Guide. - Multiprotocol Support. Connecting through NetWare provides access to DEC systems over such other protocols as IPX/SPX, AppleTalk, and TCP/IP. Examples using AppleTalk and TCP/IP socket are shown in the NetWare for DEC Access Administration Guide. - NetWare Integration. NetWare for DEC Access takes advantage of NetWare security, administration, and status-monitoring tools. Third-Party Emulator Software Supporting NetWare for DEC Access --------------------------------------------------------------- Emulator software handles the interface between the workstation running the emulator and the server running NetWare for DEC Access. As a result, NetWare for DEC Access is transparent to NetWare users, enabling them to operate as if they were working at a Digital terminal directly connected to the DEC network. NOTE: When running NetWare 4.1 and using a client emulator that is not aware of NetWare Directory Services (NDS), the following must be true: - The bindery context must be set on the NetWare server. - Your username must be included in the bindery context.Table 1 lists companies providing "standard" DOS, Microsoft Windows, or Macintosh terminal emulation software (software supporting IPX/SPX, AppleTalk, or TCP/IP) that is written specifically to NetWare for DEC Access. Contact the manufacturer listed in the table for information on a particular product. Standard Terminal Emulator Software written to NetWare for DEC Access --------------------------------------------------------------------- Manufacturer Product Operating System ============ ======= ================ About Software 5PM Term Macintosh, Windows 408-725-4242 408-725-4243 FAX (+33) 93-24-76-00 (+33) 93-24-76-06 FAX Attachmate KEA! Windows, Windows NT 604-431-0727 604-431-0818 FAX (+33) 1-46-04-1010 (+33) 1-46-04-0323 FAX DCS EM320 DOS, Windows 303-447-9251 303-447-1406 FAX ERICOM PowerTerm DOS, Windows (+972) 3-560-2396 (+972) 3-560-9649 FAX Firefox NOVAX DOS 206-827-9066 206-827-8285 FAX (+44) 021/609-6090 (+44) 021/609-6060 FAX Pericom Plcteemtalk Windows 609-895-0404 609-895-0408 FAX (+44) 908-265533 (+44) 908-265534 FAX Persoft SmartTerm Windows 608-273-6000 608-273-8227 FAX WRQ Reflection DOS, Windows, Mac 206-324-0407 206-332-8151 FAX (+31) 70/375-1100 (+31) 70/356-1244 FAX Wall Data RUMBA for VAX Windows 206-883-4777 206-861-3175 FAX (+44) 081/813-8188 (+44) 081/813-8693 FAX Table 2 lists companies providing Telnet terminal emulation software that is known to be compatible with NetWare for DEC Access. Emulators listed below have passed the "one-minute" terminal test. (The one-minute terminal test consists of connecting through the DEC Access gateway to a DEC network, logging onto a VAX, and running a VMS application that performs basic screen and keyboard tests.) NOTE: Other telnet clients that conform to RFC1340 should also work. Table 2 Telnet Terminal Emulator Software Manufacturer Product Operating System ============ ======= ================ About Software 5PM Term Macintosh, Windows 408-725-4242 408-725-4243 FAX (+33) 93-24-76-00 (+33) 93-24-76-06 FAX Attachmate KEA! Windows, Windows NT 604-431-0727 604-431-0818 FAX (+33) 1-46-04-1010 (+33) 1-46-04-0323 FAX DCS EM320 DOS, Windows 303-447-9251 303-447-1406 FAX Dominion Talking Windows Windows (+61) 2-967-1260 (+61) 2-967-4757 FAX ERICOM PowerTerm 420 Windows (+972) 3-560-2396 (+972) 3-560-9469 FAX Frontier SuperTCP Windows 414-241-4555 414-241-7084 FAX FTP Software PC/TCP On Net Windows, DOS 214-484-5200 214-484-6100 FAX InterCon TCP/Connect II Windows, Macintosh 703-709-5500 703-709-5555 FAX Masterlink PopTerm DOS, Windows 415-884-3464 415-884-2141 FAX NCSA NCSA Telnet DOS, Macintosh ftp.ncsa.uiuc.edu 217-244-4130 NetManage Chameleon Windows 408-973-7171 408-256-6405 FAX Novell LAN WorkPlace DOS, Windows, OS/2, Macintosh www.novell.comftp.novell.com 1-800-NETWARE 801-429-5533 Novell UnixWare UNIX www.novell.comftp.novell.com 1-800-NETWARE 801-429-5533 Pericom Soft teemtalk Windows 609-895-0404 609-895-0408 FAX (+44) 908-265533 (+44) 908-265534 FAX Persoft SmartTerm Windows 608-273-6000 608-273-8227 FAX (+44) 0491-638090 (+44) 0491-638010 FAX WRQ Reflection DOS, Windows, Macintosh 206-324-0407 206-332-8151 FAX (+31) 70/375-1100 (+31) 70/356-1244 FAX Wall Data RUMBA for VAX Windows 206-883-4777 206-861-3175 FAX (+44) 081/813-8188 (+44)081/813-8693 FAX Wayne Warthen Kermit Windows wwarthen@kaiwan.com Wollongong Group Pathway Access Windows, DOS 415-962-7140 415-969-5549 FAX WAN Client Parameters --------------------- If you experience problems in a low-speed WAN environment using IPX/SPX, you may want to set the client parameters in the NET.CFG file on the workstation. For more information on this file, see the NetWare system administration guide for the version of NetWare that you have installed. SPX Clients ----------- Novell recommends that you set the protocol stack SPX parameters in the NET.CFG file for SPX clients as follows: For OS/2 For DOS and Windows ======== =================== protocol stack spx protocol stack spx abort timeout 6000 abort timeout 1080 listen timeout 12000 listen timeout 216 retry count 40 retry count 40 verify timeout 6000 verify timeout 108 TCP/IP Clients -------------- TCP clients may experience problems opening multiple Telnet sessions, or performance problems if the client's TCP/IP is not configured for performance. If you see such problems, or your client sessions drop, increase the number of packet buffers for your TCP/IP stack (for example, Novell's LAN WorkPlace TCP/IP stack). In the NET.CFG file, change the number of buffers under the Link Support heading from 4 to 8 or 16 for better performance. This number depends on the amount of RAM in your client workstation. NOTE: If the client software is running on top of LAN WorkPlace, the TCP/IP stack supports an unlimited number of sessions, and you wish to open as many sessions as possible (limited only by memory), remove the MAX STACK 8 line. This line allows you to open only eight sessions; removing the line will remove this limitation. To tune up these parameters for other TCP/IP stacks, refer to the emulator documentation. Operating System Parameters --------------------------- NetWare for DEC Access supports up to 128 ports where each port can support up to 4 sessions. If you want to bring up a large number of sessions, for example, 300 or more, you may need to tune up your server's performance in the following manner: 1. If you have an EISA computer running NetWare 3.12, set the following parameter: AUTO REGISTER MEMORY ABOVE 16 MB = ON NetWare 4.1 takes care of this parameter automatically. 2. If you have an ISA computer running NetWare 3.12, you must specify the REGISTER MEMORY START ADDRESS LENGTH parameter in the AUTOEXEC.NCF file. Refer to your NetWare manual for more information. NetWare 4.1 takes care of this parameter automatically. 3. In addition, on a NetWare 3.12 server, set the SHORT TERM MEMORY ALLOCATION to the appropriate memory value. The default is 8 MB and the maximum value is 32 MB. The additional memory required for the number of sessions specified is on page 8. NetWare 4.1 takes care of this parameter automatically. 4. On both NetWare 3.12 and NetWare 4.1 servers, set the maximum number of packet receive buffers to 2000. Please refer to your NetWare manual for more information on this parameter. Running NetWare for DEC Access and NetWare for SAA on One Server ---------------------------------------------------------------- You must have NetWare for SAA 2.0 or higher to run NetWare for DEC Access 1.1 and NetWare for SAA on the same server. Both products use the same Communication Executive version 2.0. If you have a DEC host system and an IBM mainframe or AS/400 systems, you may want to install NetWare for SAA and NetWare for DEC Access on the same server. Use the procedure outlined in the NetWare for DEC Access Administration Guide to install the NetWare for DEC Access software. You do not need to reinstall the Communication Executive. You will need at least 16 MB of RAM to run NetWare for SAA and NetWare for DEC Access concurrently. Using INETCFG ------------- The INETCFG utility does not recognize LAT as a protocol. If you are using INETCFG to configure your protocols and if you choose YES when prompted to transfer your AUTOEXEC.NCF LOAD and BIND statements, INETCFG does not comment the LAT statement out of the AUTOEXEC.NCF file. You must do this manually using a semicolon in front of it the statement, as follows: ;BIND LAT board You can still use INETCFG to load NetWare for DEC Access (NWDA) and bind LAT to the Ethernet card connected to your DEC network. Using NetWare for DEC Access on NetWare for Macintosh 3.12 If you wish to install both NetWare for Macintosh 3.12 and NetWare for DEC Access 1.1 on a NetWare 3.12 server, you must install the Communication Executive 2.x that ships with NetWare for DEC Access 1.1 after you install NetWare for Macintosh. The newer version of the Communication Executive updates the version of APPLETLK.NLM. This new NLM is necessary in order to load the ADSP.NLM (AppleTalk Data Stream Protocol) and subsequently the Communication Executive's Connection Manager for AppleTalk (CMAT.NLM). Using Multiple Network Adapter Cards ------------------------------------ NetWare allows you bind more than one protocol to a single network adapter card (NIC). If you have already loaded a driver for the Ethernet_II frame type, you need not load that driver again. You cannot load the same frame type for more than one protocol on a single card. For optimal performance, or if you are using the same frame type for more than one protocol, use one network adapter card to connect to the DEC network and a second to connect to the NetWare network. You can then give each card a unique name for binding purposes. Server Hardware Requirements and Recommendations ------------------------------------------------ The hardware necessary to run a NetWare for DEC Access server depends on the number of users that it must support and the other NLMs that are running on the server. NetWare for DEC Access 1.1 requires the following: - At least 1 MB of available RAM, in addition to the RAM required for NetWare and other NLMs that may be running on the server. - Approximately 15 MB of hard disk space. - A 386, 486, or Pentium processor. NetWare for DEC Access should operate on any NetWare server platform tested and approved by Novell Labs. The greater the processor speed and the more available RAM, the better your server performs. Table 3 lists the minimum CPU capacity recommended and amount of RAM required on your computer for each user configuration version of NetWare for DEC Access. The required minimum available memory is based on the number of users. For Telnet clients, each user can be viewed as an IP address. Every time a user connects from a computer with a certain IP address, one port on the NetWare for DEC Access server is used. A user can bring up a maximum of 4 sessions from each IP address. Any additional sessions will require additional ports. Approximately 6MB of available RAM is required to load NetWare for DEC Access including the supporting NLMs such as Communication Executive, CLIB, and STREAMS. Depending on the number of concurrent users you expect to support, you must add the amount shown in the following table to this base memory requirement of 6MB to get the total additional RAM required. Table 3 Server Hardware Recommendations and Memory Requirements --------------------------------------------------------------- Concurrent Users Recommended CPU Speed Available RAM ================ ==================== ============= 8 386DX/25 1MB 16 386DX/33 2MB 32 486DX/25 3MB 64 486DX/33 5MB 128 486DX2/66 10MB NOTE: The data in this table assumes one session per user. More memory may be required if more than one session per user is needed. For the latest information regarding Novell Labs Product Certification of data link adapters, LAN adapters, systems and drivers, contact Novell Labs through the FaxBack System, or contact the vendor. System Volume Space Requirements for DynaText and CBT Files ----------------------------------------------------------- If you will be installing the DynaText online versions of NetWare or NetWare for DEC Access manuals or the NetWare computer-based training (CBT) files, the following free system volume space is required in addition to that required for the software files: - DynaText software 6MB - NetWare for DEC Access 1.1 DynaText 2MB - NetWare 4.1 DynaText 50MB - NetWare 4.1 CBT 4MB - NetWare 3.12 DynaText 33MB Recommended Ethernet Drivers ---------------------------- WARNING: Use of an incompatible driver may cause problems and loss of connections to the server. Many drivers are bundled with NetWare for DEC Access for your convenience. All drivers provided with NetWare for DEC Access are compliant with version 4.1 of the Open Data-Link Interface (ODI) architecture. If you are using a driver that is not bundled with NetWare for DEC Access 1.1, make sure that it is ODI 4.1 compliant before installing NetWare for DEC Access 1.1. IMPORTANT: Problems can occur if you do not use ODI 4.1 compliant drivers. For the latest information regarding Novell Labs product certification of data link adapters and LAN adapters, systems, and drivers, contact Novell Labs through the FaxBack System, or contact the vendor. You may have to upgrade your LAN driver before installing NetWare for DEC Access 1.1. The following adapters have been certified by Novell: - Novell NE1000 Adapter - Novell NE2000 Adapter - Novell NE/2 Adapter - Novell NE3200 Adapter - Novell NE/2-32 Adapter ----------------------------------------------------------------- Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information. -----------------------------------------------------------------