("Besides the device, the box should contain:

* Eight little rectangular snippets of paper that say "WARNING"

* A plastic packet containing four 5/17 inch pilfer grommets and two club-ended 6/93 inch boxcar prawns.

YOU WILL NEED TO SUPPLY: a matrix wrench and 60,000 feet of tram cable.

IF ANYTHING IS DAMAGED OR MISSING: You IMMEDIATELY should turn to your spouse and say: "Margaret, you know why this country can't make a car that can get all the way through the drive-through at Burger King without a major transmission overhaul? Because nobody cares, that's why."

WARNING: This is assuming your spouse's name is Margaret."\ITALIC) (-- Dave Barry, "Read This First!"\BOLD) (INTRODUCTION\CMUIP_INST_1)

This chapter will take you step-by-step through the entire CMU-OpenVMS/IP installation procedure. You should read through this chapter once (at least the Pre-Installation section) and then re-read it as you follow the installation instructions.

The software is installed with DEC's VMSINSTAL utility. The VMSINSTAL utility is used to install all of DEC's layered products, including VMS itself, so the system manager should be somewhat familiar with this routine. Unless there is an indication to the contrary, it is assumed that the user is installing CMU-OpenVMS/IP images and documentation but not the source code. (PRE-INSTALLATION\CMUIP_INST_2) (Pre-installation)

In order to install the CMU-OpenVMS/IP software you will need three things:

(UNNUMBERED) The CMU-OpenVMS/IP software A VAX/VMS system A human being

The next section discuss the complications arising from these requirements. The section after that discusses a few pieces of information you will have to obtain before you begin the installation. (Things you need to have\CMUIP_INST_3) (The CMU-OpenVMS/IP software\CMUIP_INST_4)

The software usually comes on either a TK-50 or mag tape. This tape contains, among other things, three savesets called CMUIPxxx.A, CMUIPxxx.B, and CMUIPxxx.C where xxx represents the version number (ie. 066 == version 6.6). If you are planning on installing the software directly from the distribution tape, you will need to have the tape mounted before you proceed. (A VAX/VMS system\CMUIP_INST_5) (VMS, version of)

You can run CMU-OpenVMS/IP 6.6 under any VAX/VMS system running VMS 5.0 or higher. (Space required\CMUIP_INST_6) (disk space)

The peak utilization of disk space during a complete installation is about 6000 disk blocks. You should check to make sure you have at least this many blocks free on the disk you wish to hold the software. This assumes that you are not installing the source code. (Hardware required\CMUIP_INST_7) (hardware) (DECNet)

Technically there are no hardware requirements. The IPACP can run without communicating with the outside world. Most sites hook the IPACP up to an EtherNet card. You can also run IP over a serial line, or encapsulated within DECNet. (A human being\CMUIP_INST_8)

To operate the keyboard, of course, and also to be in charge of distributing unique IP addresses. There are several people needed, in fact. (Network Manager)

The Network Manager's job is to coordinate the structure of the local IP network and to distribute unique IP addresses. The Network Manager should be familiar with the TCP/IP protocols and also the physical networks they are to run over. If you (yes, you!) have been elected to be the Network Manager and you are unfamiliar with TCP/IP, see the preface of this document for some suggested reading. (System Manager)

The System Manager is in charge of maintaining and tuning the VMS system as well as installing and monitoring the system software, including CMU-OpenVMS/IP. The System Manager should be familiar which the basic operation and maintenance of the VMS system. She should know what hardware is attached to the machine, especially which network devices. (Things you need to know\CMUIP_INST_9)

This section describes several bits of information which you will need to be in possession of when you begin the installation procedure. (An IP address\CMUIP_INST_10) (IPaddress)

An IP address is a 32-bit number which identifies a machine on the network. This 32 bit address is completely independent of the hardware address of the communication device which IP will be using (for instance: the 48-bit address on an EtherNet card). Usually the address is displayed in "dotted-decimal" notation which means that the address is broken into four 8-bit parts and printed as decimal numbers separated by periods (for instance: 128.2.232.69). Every host with an internet (TCP/IP network) needs to have a unique IP address associated with it. The installation procedure will ask you for an IP address, so you should obtain one from your local network administrator. It is very important that two hosts on the same network do not have the same IP address.

Every IP address can be broken into two parts: the network address and the host address. Consider the address 128.2.232.68. Normally, this is broken down into a network part of 128.2.0.0 and a host part of 0.0.232.69 although there are other ways to split it up. The IPACP determines how to spilt it up by using an IP address mask. (IP address mask\CMUIP_INST_11) (IPaddress mask)

The address mask is another 32-bit IP address which is used to determine whether outgoing packets should be delivered directly to their destination or else handed off to a gateway. The local IP address is "AND"ed with the network mask to determine the local network address. In the case of 128.2.232.69 and a network mask of 255.255.0.0, the network address will be 128.2.0.0. If the IP software wants to send a packet out, it will compare the destination network for that packet with the local network address to see whether direct (no routers involved) communication is possible.

The installation procedure makes an educated guess at what your IP address mask should be and it will usually be correct. It is best, however, to ask your site's network manager for an address mask. (Host Name\CMUIP_INST_12) (host name)

Each host on the network must have a unique name. You will probably want your host name to be a domain host name.

For example, the name ``NO1.ANDREW.CMU.EDU'' is a domain host name. The ``EDU'' part is the most significant. On the Internet the ``EDU'' signifies an educational institution. Other "top-level" domains are: ``COM'' for commercial sites, ``MIL'' for military sites, ``GOV'' for government sites, and country abbreviations for sites outside the United States (like ``UK'', ``CA'', and ``AU'' for the United Kingdom, Canada, and Australia respectively). The next most significant part is ``CMU'', for Carnegie Mellon University. ``ANDREW'' stands for the cmu sub-domain populated by machines related to the CMU Andrew project, a distributed workstation network. Finally, ``NO1'', the name of the individual machine, is the least-significant part of the address, in the grand scheme of things, that is.

Your network administrator will be able to supply you with a domain host name prefix. You will be able to choose the least significant part.

The name can be arbitrarily long. Well, there are probably some limits, so keep it reasonable. After all, you are going to type it many times during the life of your machine. The name must begin with an alphabetic character and contain only alphanumeric characters. Host names are case insensitive.

For example, if your network administrator tells you that your domain name prefix is ``FOO.BAR.BAZ'', then the following names are legal (UNNUMBERED) GORP.FOO.BAR.BAZ GAZORCH1.FOO.BAR.BAZ

The following names are not legal: (UNNUMBERED) 1GAZORCH.FOO.BAR.BAZ (Does not begin with Alphabetic character) GAZORCH#.FOO.BAR.BAZ (Contains non-alphanumeric character) MY VAX.FOO.BAR.BAZ (No spaces allowed)

As a suggestion, if you may ever want to run DECNet simultaneously with the CMU-OpenVMS/IP software, you may want to choose the local part of the domain name that will also be compatible with the DECNet naming Scheme. The DECNet naming scheme requires 6 alphanumeric characters or less. For instance, if your DECNet node name is VAX1 and your domain prefix is HSS.KALAMAZOO.EDU, you might want to use VAX1.HSS.KALAMAZOO.EDU as your internet domain name.

Once you've chosen a name, let your network administrator know of your choice. S/he will be able to tell you if your choice is unique. The network administrator will also make sure that the other hosts on the IP network will eventually be able to recognize your name as well. She (or he, as the case may be) will do this by having it entered into the Domain name system and perhaps a host table that is distributed to the nodes at your site. (Communication device\CMUIP_INST_13)

You will need to know the name of the device you will be using to transmit and receive IP datagrams. The System Manager should be able to give the name of the EtherNet card (or other such device) that you need. (Gateways\CMUIP_INST_14) (Gateways)

If you wish to contact any hosts which are not on the same physical network as you are, you will probably need to define one or more gateways to use. Your site's Network Manager can give you the names and addresses of these servers. (Name Servers\CMUIP_INST_15) (Name Servers)

Name Servers are hosts who are able to translate Domain Names, like NO1.ANDREW.CMU.EDU, into IP addresses, like 128.2.232.69. Once again, ask your Network Manager for the names and addresses of any Name Servers that are available to you. (Installation\CMUIP_INST_16)

You are now ready to begin the installation process. (Getting started\CMUIP_INST_17)

The example presented below is a typical CMU installation. If you are installing the software at CMU, you should use the same name servers and gateways used below. Note that this is a 6.6 installation which is *very* different from a 6.4 or earlier installation. (Example\CMUIP_INST_18)

SOLW@ @sys$update:vmsinstal cmuip bitbkt$mua0: options n VAX/VMS Software Product Installation Procedure V5.4-2 It is 28-MAY-1991 at 14:21. Enter a question mark (?) at any time for help. %VMSINSTAL-W-NOTSYSTEM, You are not logged in to the SYSTEM account. %VMSINSTAL-W-ACTIVE, The following processes are still active: BULLCP Synny BATCH_676 * Do you want to continue anyway [NO]? (YES\BOLD) (Return\BOX) * Are you satisfied with the backup of your system disk [YES]? (Return\BOX) The following products will be processed: CMUIP V6.6 Beginning installation of CMUIP V6.6 at 14:22 %VMSINSTAL-I-RESTORE, Restoring product save set A ... Release notes included with this kit are always copied to SYS$HELP. Additional Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. None of the above * Select option [2]: 1 (Return\BOX) DRYCAS$DKA0:[SYS10.SYSUPD.CMUIP066]CMUIP066.RELEASE_NOTES;4 CMU-OpenVMS/IP 6.6 Release Notes - Fixed miscellaneous bugs in the central IP modules which would cause spurious ACCVIO and INSVIRMEM crashes of the ACP. - Improved (and provided) IP fragmentation. The IP module can now send and receive packets of nearly arbitrary size (at least 8K). You should increase your MAXBUF parameter to allow this to work. - Provided an initial NFS server. - FTP now allows STRU O VMS file transfers which work in the same fashion as Multinet for sending arbitrary VMS files across FTP. You can exchange indexed, sequential, or just about any kind of files with other CMU-OpenVMS/IP (with FTP 2.9) or Multinet systems. - Telnet now supports local editing for line-mode connections * Do you want to continue the installation [NO]? (YES\BOLD) (Return\BOX) %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. This is the CMU-OpenVMS/IP installation kit. This kit provides everything you need to run CMU-OpenVMS/IP. The installation will now ask if you want to purge any old CMU-OpenVMS/IP images from your disk. The only reasons that come to mind not to do this are: a) you may want to revert to an older image, b) you want to preserve configuration files, or c) you want to compare the new and old images. * Do you want to purge files replaced by this installation [YES]? (Return\BOX) This version of CMU-OpenVMS/IP must reside in a system root directory. This directory must be rooted and contain the following subdirectories: SYSEXE,SYSMGR,SYSLIB, SYSUPD, SYS$LDR, and SYSHLP. A system logical will be defined, CMUIP_ROOT, and the software will make frequent use of this. You have three choices in deciding how CMUIP_ROOT should be defined: 1) Use one of the already declared system roots: SYS:[CMUIP.] DRYCAS$DKA0:[SYS10.] SYS$COMMON: 2) Allow the installation script to create the new directories. Note: If you "just wanna install the darn thing", hit the enter key. Your VMS system comes with two system roots already defined, a node-specific root called SYS$SPECIFIC and a cluster-shared root called SYS$COMMON. Most people use one of these roots. Some, however, may prefer to use a root of their own definition, in order to avoid mixing Digital and non-Digital software. If this is the case, you may wish to exit the installation procedure (with ^Y) now and define a new system root. In the example below, the installation "suggests that we use the node-specific root, and we tell it to use another root that we had defined earlier. * Where do you want the software installed [SYS:[CMUIP.]]: (Return\BOX) %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS:[CMUIP]. %CREATE-I-EXISTS, SYS:[CMUIP] already exists %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS:[CMUIP.SYS EXE]. %CREATE-I-EXISTS, SYS:[CMUIP.SYSEXE] already exists %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS:[CMUIP.SYS MGR]. %CREATE-I-EXISTS, SYS:[CMUIP.SYSMGR] already exists %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS:[CMUIP.SYS LIB]. %CREATE-I-EXISTS, SYS:[CMUIP.SYSLIB] already exists %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS:[CMUIP.SYS HLP]. %CREATE-I-EXISTS, SYS:[CMUIP.SYSHLP] already exists %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS:[CMUIP.SYS $LDR]. %CREATE-I-EXISTS, SYS:[CMUIP.SYS$LDR] already exists %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS:[CMUIP.SYS UPD]. %CREATE-I-EXISTS, SYS:[CMUIP.SYSUPD] already exists If you are installing into a new system root or onto a disk other than your system disk, these messages shown above may or may not appear during your installation. They are only informational and are not of concern. The CMU-OpenVMS/IP installation occurs in fours phases: Configuration, Software, Source Code, and Documentation. It may be the case that you would like to skip one or more of these phases. The next four questions will determine this. If you just want to install everything and get this procedure over with as soon as possible. Hit the enter key at the next five prompts. In an attempt to make the installation easier for people who want only a partial installation, the following questions have been added. Most people need not bother with these questions and should choose the default answers. Configuration: (startup files) The installation must know whether to configure the software for each application you choose to install. Answer: ALWAYS if you want to configure all of the software chosen. NEVER if you don't want any configuration done at all. ASK if you wanted to be asked for each application you choose. * Do you want to configure the software [ALWAYS]: (Return\BOX) Software: (Images, CLI definitions, and help files) The installation must know whether to install the software for each application you choose to install. Answer: ALWAYS if you want the software installed for each package chosen. NEVER if you don't want any software at all. ASK if you wanted to be asked for each application you choose. * Do you want to install the software [ALWAYS]: (Return\BOX) This command procedure updates the help library so that the DCL HELP command will provide information about the installed utilities. Here is a list of help libraries that already exist on your system: SYS$SYSROOT:[SYSHLP]HELPLIB.HLB SYS$HELP:SYSMSGHELP * Which library should have CMU-OpenVMS/IP help [SYS$SYSROOT:[SYSHLP]HELPLIB.HLB]: (Return\BOX) This procedure automatically leaves the application Command Language Definition (.CLD) files in the [.SYSMGR] sub-directory of CMUIP_ROOT:. It will optionally install the .CLD files in the system's DCL table. This table is updated by default. If you do not update this table, you must install the .CLD files by hand before you can use the CMU-OpenVMS/IP applications. To skip this step, type "NO" * Do you want to update the system DCL table [YES]? (Return\BOX) Source Code: (xxx.SRC savesets containing Bliss-32 code and MMS files) The installation must know whether to install the source code for each application you choose to install. Answer: ALWAYS if you want source code automatically installed. NEVER if you don't want any source code at all. ASK if you wanted to be asked for each application you choose. * Do you want to install the source code [NEVER]: (Return\BOX) Documentation: (Manuscript and PostScript files for the manuals) The installation must know whether to install the documentation for each application you choose to install. Answer: ALWAYS if you want documentation automatically installed. NEVER if you don't want any docs at all. ASK if you wanted to be asked for each application you choose. * Do you want to install the documentation [ALWAYS]: (NEVER\BOLD) (Return\BOX) This installation kit currently contains the following modules: Core (IPACP, NamRes, IPDriver, Central, and IPNCP) LPR Remote printing software FTP File Transfer system Telnet Remote login software Finger remote user information The installation will now ask if you want everything installed. If you answer "NO" it will ask you about each individual application. If you say "YES" it will install everything. * Do you want to install everything [YES]? (Return\BOX) * Do you want to install the development libraries [NO]? (YES\BOLD) (Return\BOX) ********************************************************************** PHASE 1: Configuration ********************************************************************** ------------------- Core configuration: ------------------- This phase of the installation will create four files; IP_STARTUP.COM, INTERNET.CONFIG, NAMRES.CONFIG, and NFS.CONFIG. IP_STARTUP.COM should be executed by the VMS startup procedure in order for CMU-OpenVMS/IP to begin running when the system is booted up. It will define logicals, install images, load devices, and then run the IPACP as a detatched process. INTERNET.CONFIG is a text file that contains the information which is specific to a peticular host. Every machine must have it's own copy sice this file contains unique information such as the host's IP address. If you like, you may make make changes to the CMU-OpenVMS/IP configuration by editing INTERNET.CONFIG instead or reinstalling the software. N.B.: Changes will not take effect until the IPACP is restarted. NAMRES.CONFIG is the configuration file for the Name Resolver. It too may be edited in order to change the configuration NFS.CONFIG defines your NFS server configuration. In it you should define which directory trees you will export as well as give Unix<->VMS translations. Your SYSGEN parameter MAXBUF is less than the recommended value. We recommend that you raise this parameter to 8192 to handle large I/O requests. You can change this parameter by including the line: min_MAXBUF=8192 in your SYS$SYSTEM:MODPARAMS.DAT and then running AUTOGEN. Although this parameter change is not required, it may prove to be necessary if your TCP/IP software sends or received large IP packets. Creating IP_STARTUP.COM: * Host Full Name [xyz.serendipityU.edu]: (SOLW.CLUB.CC.CMU.EDU\BOLD) (Return\BOX) Creating INTERNET.CONFIG: You must specify an IP address for this host. An IP address is a 32-bit number which uniquely identifies an Internet host. Type in the address using "dotted-decimal" notation, as in "128.2.232.69". IP address are generally distributed by a site's network manager in order to avoid duplication. * What is this Hosts IP address: (128.2.232.226\BOLD) (Return\BOX) You will now need to specify an address mask. The address mask is used to determine which interface to send IP packets out of for a given destination. If you have only one IP interface (the usual case), you should probably just hit enter now. It looks like you're on a class-B network. * What is the address mask [255.255.0.0]: (Return\BOX) You must now specify a device over which CMU-OpenVMS/IP will communicate. Normally this will be the system's Ethernet card. CMU-OpenVMS/IP can run on the same controller as DECNet and LAT without any conflict. * Which device is the network device (omit colon) [XQA0]: (Return\BOX) You may need to specify a gateway if you would like to communicate with hosts not on your local net (ie. ethernet). * Any (more) gateways [NO]? (YES\BOLD) (Return\BOX) * Gateway Name: (PRPNET-GW.CC.CMU.EDU\BOLD) (Return\BOX) * Gateway Address: (128.2.1.2\BOLD) (Return\BOX) * Gateway Network [0.0.0.0]: (Return\BOX) * Gateway Net Mask [0.0.0.0]: (Return\BOX) You may need to specify a gateway if you would like to communicate with hosts not on your local net (ie. ethernet). * Any (more) gateways [NO]? (Return\BOX) * Will you be providing an NFS server [YES]? (Return\BOX) To improve the NFS server's efficiency, you may wish to increase the SYSGEN parameter CHANNELCNT to 512. This will permit the NFS server to cache more files and improve response time from the client. You can do this by adding the following line to your MODPARAMS.DAT file in SYS$SYSTEM: and then running AUTOGEN: min_CHANNELCNT=512 * Would you like the SNMP module included [YES]? (Return\BOX) Creating NAMRES.CONFIG: The Domain name resolver performs its operations by querying other hosts. To perform its job, it must know at startup time - Which machines to ask (Example A.ISI.EDU), - The address of those machines (Example 26.3.0.103), and - The Domain that the remote machine is an authority for. Examples: "ANDREW.CMU.EDU." or "CS.CMU.EDU." or just "." If you have only one domain server, make it's domain "." You must now provide the installation with a list of machines which will act as domain name servers. If your site does not have access to any domain name servers, you may wish to use a host table instead. If you do have access to Name Servers, it is far preferable to use these. * Are there any (more) servers [NO]? (YES\BOLD) (Return\BOX) * Server Host Name: (NETSERVER.ANDREW.CMU.EDU\BOLD) (Return\BOX) * Server Address: (128.2.35.50\BOLD) (Return\BOX) * Server Domain [.]: (Return\BOX) * Are there any (more) servers [NO]? (Return\BOX) The NamRes software has implemented a search list scheme. The search list implements a scheme so that can host names can be shortened by the user. For example, if the user specifies a host name of "FOO.BAR", the NamRes software can look for "FOO.BAR.CS.CMU.EDU.", "FOO.BAR.RI.CMU.EDU.", "FOO.BAR.CMU.EDU.", and lastly "FOO.BAR." In this example the search list was "CS.CMU.EDU.", "RI.CMU.EDU.", "CMU.EDU." and ".". Enter the domin names one at a time, ending with ".". * Domain Suffix [.]: (CC.CMU.EDU.\BOLD) (Return\BOX) * Domain Suffix [.]: (CMU.EDU.\BOLD) (Return\BOX) * Domain Suffix [.]: (Return\BOX) Creating HOST.TXT A sample NFS.CONFIG file has been provided in CMUIP_ROOT:[SYSMGR]. You should customize this file to suit your needs. ------------------ LPR configuration: ------------------ * Do you want to overwrite your current PrintCap file [NO]? (Return\BOX) Please remember to add the following lines to your system shutdown command file. $ IF F$SEARCH("CMUIP_ROOT:[SYSMGR]LPR_SHUTDOWN.COM") .NES. "" THEN - @CMUIP_ROOT:[SYSMGR]LPR_SHUTDOWN.COM --------------------------------------------------------- The configuration phase is finished. The rest of this procedure is automated. Go grab a cupacoffee. This may take a while to complete... --------------------------------------------------------- ********************************************************************** PHASE 2: Software ********************************************************************** %VMSINSTAL-I-RESTORE, Restoring product save set B ... Installing the Core images... Linking IPACP Linking NAMRES Linking IPDriver Linking IP transports Linking IP transports Linking IPNCP.EXE Installing the DECwindows transport... Linking DECwindows transport module The DECwindows transport module has been installed on your system. In order to use this module, you need do the following after CMU-OpenVMS/IP's installation: - Customize SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM to have the line as shown below: $do_default: >>> $ decw$server_transports == "DECNET,LOCAL,LAT,CMU" $ exit Installing the LPR images... Linking LPR Symbiont Linking LPD Linking LPQ Linking LPRM Installing the FTP images... %COPY-S-COPIED, DRYCAS$DKA0:[SYS10.SYSUPD.CMUIP066]VMS054.OBJ;3 copied to DRYCAS $DKA0:[SYS10.SYSUPD.CMUIP066]PORT.OBJ;1 (1 block) Linking FTP client Linking FTP server Installing the Telnet images... Linking Telnet client Linking Telnet server Installing the psuedo-terminal images... Linking IPACP Installing the Finger images... Linking Finger client Linking Finger server ********************************************************************** PHASE 3: Source Code ********************************************************************** ********************************************************************** PHASE 4: Documentation ********************************************************************** %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Installation of CMUIP V6.6 completed at 15:00 VMSINSTAL procedure done at 15:02 SOLW@ (Post-Installation:\CMUIP_INST_19)

Don't go away yet! There's still a little more work to be done... (Important files you should know about\CMUIP_INST_20)

These are: IP_STARTUP.COM, INTERNET.CONFIG (INET$CONFIG), and NAMRES.CONFIG (NAMRES$CONFIG). You can find out more about them in the chapter on System Management.( For a complete list of files added to the system, see the appendix.) (Updating the System Startup File\CMUIP_INST_21)

To start the IPACP upon each system boot, modify the system startup command file to call the IP_STARTUP command procedure by inserting the following lines in the file SYS$MANAGER:SYSTARTUP.COM. $ IF F$SEARCH("SYS$MANGER:IP_STARTUP.COM") .NES. "" THEN - @SYS$MANAGER:IP_STARTUP.COM

If you plan on running both DECNet and the CMU-OpenVMS/IP software at the same time over the same interface, please be sure to start DECNet first and then start the IP software. It is necessary to do it in this order because DECNet changes the EtherNet hardware address of your interface to suit its own purposes and the TCP/IP software does not appreciate having its physical network address change dynamically. (System Tuning\CMUIP_INST_22)

Since the IPACP consumes some of the system resources, it may be necessary to adjust some of the system parameters. The easiest way to do the adjustment is with AUTOGEN. To find out more about the AUTOGEN facility and system tuning, consult (Guide to VAX/VMS Performance Management) and (Guide to VAX/VMS System Management and Daily Operations).

Most of the extra system resources that the IPACP software consumes are in NPAGEDYN and IRPCOUNT. You may want to modify the file MODPARAMS.DAT to include the lines: add_NPAGEDYN=100000 add_IRPCOUNT=100 min_MAXBUF=8192

Also, if you will be using the NFS server, you should increase the number of channels which each process (most notably the IP_ACP(V6.6) process) can use. You can do this by adding this line to the above list: min_CHANNELCNT=512

Then rerun the AUTOGEN facility. You will have to keep a watch on system resources and judge for yourself which resources are being consumed. (Files Created During Installation\CMUIP_INST_23) (Files installed) (Installed filesSee Files installed)

The following files are created during the installation of the CMU-OpenVMS/IP software. All files are placed under the CMUIP_ROOT:[...] directory tree you specify at installation time. Files sizes are given in disk blocks. (4\18\8\6) (File Name\Installation Part\Size Blocks\Description) ((4)Files in CMUIP_ROOT:[SYS$LDR]) (IPDriver.exe\CORE\9\Provides interface to IP/TCP/UDP) (IPDriver) (IP0:) (PNDriver.exe\Telnet\7\Control portion of Pseudo terminal) (Pseudo-terminal driver) (PNA0:) (TZriver.exe\Telnet\5\Terminal portion of Pseudo terminal) (TZA0:) ((4)Files in CMUIP_ROOT:[SYSEXE]) (FINGER.EXE\FINGER\50\Finger client) (FINGER_SERVER.EXE\FINGER\51\Finger Server) (FTP.EXE\FTP\167\FTP client) (FTP_SERVER.EXE\FTP\83\FTP server) (IPACP.EXE\CORE\219\IP Ancillary Control Process image) (IPNCP.EXE\CORE\89\IP Network Control Program image) (LPD.EXE\LPR\86\LPR Demon) (LPQ.EXE\LPR\22\LPR Show Queue image) (LPRM.EXE\LPR\23\LPR Remove image) (LPRSMB.EXE\LPR\42\LPR Symbiont image (for spooling to remote queues)) (NAMRES.EXE\CORE\85\Name Resolver image (does name lookups)) (TELNET.EXE\Telnet\80\Outgoing TELNET image) (TELNET_SERVER.EXE\Telnet\39\Incoming TELNET image (not recommended)) ((4)Files in CMUIP_ROOT:[SYSHLP]) (FTP.HLB\FTP\132\Help library for FTP) (IPNCP.HLB\CORE\23\Help library for IPNCP) (TELNET.HLB\Telnet\23\Help library for TELNET) ((4)Files in CMUIP_ROOT:[SYSLIB]) (DNDRV.EXE\CORE\30\Driver library for IP-over-DECnet) (HOSTS.TXT\CORE\1\Host table, as per RFC 952) (SLDRV.EXE\CORE\18\Driver library for SLIP) (XEDRV.EXE\CORE\32\Driver library for Ethernet adapters) ((4)Files in CMUIP_ROOT:[SYSMGR]) (FINGER.CLD\Finger\1\Command definition for Finger) (FTP.CLD\FTP\3\Command definition for FTP) (INTERNET.CONFIG\CORE\6\IPACP configuration file) (IPNCP.CLD\CORE\1\Command definition for IPNCP) (IP_STARTUP.COM\CORE\6\DCL procedure to bring up network) (LPD_HOSTS.COM\LPR\7\DCL procedure to allow remote host to use local printer. See (LPD_HOSTS)) (LPQ.CLD\LPR\3\Command definition for LPQ) (LPRM.CLD\LPR\4\Command definition for LPR) (LPR_SHUTDOWN.COM\LPR\3\DCL procedure to remove LPR queues) (LPR_STARTUP.COM\LPR\6\DCL procedure to startup printer queues) (NAMRES.CONFIG\CORE\2\Initial Name Resolver configuration) (PRINTCAP.TXT\LPR\3\List of printers. See (PRINTCAP)) (TELNET.CLD\Telnet\2\Command definition for Telnet)