                 C                      Compaq_TCP/IP_Services_for_OpenVMS____________ 3                      Installation and Configuration   .                      Order Number: AA-LU49M-TE    !                      January 2001   F                      This manual explains how to install and configureF                      the Compaq TCP/IP Services for OpenVMS product on'                      your OpenVMS host.           C                      Revision Information:        This guide super- C                                                   sedes the Digital E                                                   TCP/IP Services for F                                                   OpenVMS InstallationC                                                   and Configuration E                                                   manual, Version 5.0   ?                      Operating Systems:           OpenVMS Alpha B                                                   Versions 7.1 and7                                                   7.2-1 F                                                   OpenVMS VAX Versions=                                                   7.1 and 7.2   ?                      Software Version:            Compaq TCP/IP F                                                   Services for OpenVMS=                                                   Version 5.1               0                      Compaq Computer Corporation#                      Houston, Texas                  H               __________________________________________________________  0                2001 Compaq Computer Corporation  G               COMPAQ, OpenVMS, VAX, VMS, and the Compaq logo Registered 2               in U.S. Patent and Trademark Office.  B               DECnet, OpenVMS, PATHWORKS, and Tru64 are registeredG               trademarks of Compaq Information Technologies Group, L.P. 7               in the United States and other countries.   A               All other product names mentioned herein may be the 7               trademarks of their respective companies.   G               Confidential computer software. Valid license from Compaq B               required for possession, use, or copying. ConsistentG               with FAR 12.211 and 12.212, Commercial Computer Software, E               Computer Software Documentation, and Technical Data for H               Commercial Items are licensed to the U.S. Government under3               vendor's standard commercial license.   C               Compaq shall not be liable for technical or editorial C               errors or omissions contained herein. The information C               in this document is provided "as is" without warranty B               of any kind and is subject to change without notice.A               The warranties for Compaq products are set forth in B               the express limited warranty statements accompanyingB               such products. Nothing herein should be construed as2               constituting an additional warranty.  H                                                                   ZK6524  3               This document is available on CD-ROM.   C               This document was prepared using DECdocument, Version                3.3-1b.                                E      ________________________________________________________________   E                                                              Contents     E      Preface..................................................      v     :      1  Preparing to Install and Configure TCP/IP Services  E            1.1   Understanding the Major Tasks Involved.......    1-1 E            1.2   Preinstallation Tasks........................    1-2 E            1.2.1     Inspecting the Distribution Kit..........    1-3 E            1.2.2     Extracting the Release Notes.............    1-3 =            1.2.3     Backing Up the System Disk and Upgrading E                      OpenVMS..................................    1-4 4            1.2.4     Registering the License ProductE                      Authorization Key........................    1-4 E            1.2.5     Checking the Disk Space..................    1-5 E            1.2.6     Checking the Physical Memory.............    1-5 E            1.2.7     Checking the System Parameters...........    1-6 E            1.2.7.1     Global Pagelets and Global Sections ...    1-6 E            1.2.7.2     Nonpaged Dynamic Pool..................    1-6 E            1.2.7.3     Interrupt Stack Pages (VAX Only).......    1-7 :            1.2.7.4     System Page Table Entries ParameterE                        (VAX Only) ............................    1-7 E            1.2.8     Assigning a User Identification Code.....    1-8 E            1.3   Assembling Configuration Information.........    1-9   "      2  Installing TCP/IP Services  E            2.1   Installation Procedure.......................    2-1               E                                                                   iii                  &         3  Configuring TCP/IP Services  <               3.1   Recommended Order for Configuring TCP/IPH                     Services.....................................    3-1>               3.2   Automatic Configuration of TCP/IP ServicesH                     Using DHCP Client............................    3-2H               3.3   Running TCPIP$CONFIG.........................    3-3;               3.3.1     Converting Existing TCP/IP Services H                         Configuration Files (Upgrade Only).......    3-44               3.3.2     Creating New TCP/IP ServicesH                         Configuration Files......................    3-5H               3.3.3     Understanding the Configuration Menus....    3-6H               3.3.4     Configuring the Core Environment.........    3-7H               3.3.4.1     Domain Configuration...................    3-8H               3.3.4.2     Interface Configuration................    3-9H               3.3.4.3     Dynamic Routing Configuration..........    3-9H               3.3.4.4     BIND Resolver Configuration............   3-11H               3.3.4.5     Time Zone Configuration................   3-11H               3.3.5     Configuring the Client Environment.......   3-12H               3.3.6     Configuring the Server Environment.......   3-14H               3.3.7     Configuring the Optional Components......   3-17@               3.4   Using TCPIP$CONFIG Option Commands to BypassH                     TCPIP$CONFIG Menus...........................   3-18H               3.5   Making Configuration Changes Take Effect.....   3-206               3.5.1     Starting TCP/IP Services UsingH                         TCPIP$CONFIG.............................   3-20H               3.6   Verifying the Configuration..................   3-22=               3.6.1     Running the IVP from the TCPIP$CONFIG H                         Command Procedure........................   3-23<               3.6.2     Running the IVP from the OpenVMS DCLH                         Prompt...................................   3-23>               3.6.3     Verifying the TCP/IP Services InternetH                         Configuration............................   3-23H               3.6.4     Verifying the SNMP Configuration.........   3-24H               3.7   Additional Configuration Tasks...............   3-26H               3.8   Starting and Stopping TCP/IP Services........   3-27;               3.8.1     Automatically Starting and Stopping H                         TCP/IP Services..........................   3-27=               3.8.2     Starting and Stopping TCP/IP Services H                         Manually.................................   3-28H               3.9   Starting and Stopping Individual Services ...   3-28?               3.10  Specifying TCP/IP Services as the Transport H                     for DECwindows Applications..................   3-29    
         iv                 6         A  Sample New TCP/IP Services Installation and            Configuration  H               A.1   Sample New Installation Procedure............    A-1H               A.2   Sample New Configuration Procedure...........    A-2  
         Index              Examples  <               2-1       TCP/IP Services Installation: Sample@                         POLYCENTER Software Installation UtilityH                         Procedure................................    2-3           Tables  H               1         TCP/IP Services Documentation............     vi  3               1-1       Major Tasks: Installing and H                         Configuring..............................    1-2  H               1-2       Preinstallation Tasks....................    1-3  H               1-3       Configuration Planning Worksheet.........   1-10  H               3-1       Configuring TCP/IP Services..............    3-2  H               3-2       Troubleshooting IVP Errors ..............   3-24                                H                                                                        v                           H         ________________________________________________________________  H                                                                  Preface      C               The Compaq TCP/IP Services for OpenVMS product is the E               Compaq implementation of the TCP/IP networking protocol G               suite and internet services for OpenVMS Alpha and OpenVMS                VAX systems.  ?               TCP/IP Services provides a comprehensive suite of G               functions and applications that support industry-standard D               protocols for heterogeneous network communications and               resource sharing.   C               This manual explains how to install and configure the B               Compaq TCP/IP Services for OpenVMS (TCP/IP Services)C               networking software on an OpenVMS system. This manual D               reflects the installation and configuration proceduresG               for Version 5.1 of the Compaq TCP/IP Services for OpenVMS C               product. For information about last-minute changes to B               these procedures, see the Compaq TCP/IP Services for$               OpenVMS Release Notes.           Intended Audience   D               This manual is for experienced OpenVMS and UNIX systemH               managers and assumes a working knowledge of OpenVMS systemD               management, TCP/IP networking, and TCP/IP terminology.           Document Structure  C               This manual contains three chapters and one appendix:   E               o  Chapter 1 explains how to prepare for installing and -                  configuring TCP/IP Services.   C               o  Chapter 2 describes how to install TCP/IP Services C                  on an OpenVMS system using the POLYCENTER Software &                  Installation utility.  H                                                                        v                 B               o  Chapter 3 provides guidelines on how to configureB                  the TCP/IP Services components and services after                  installation.  >               o  Appendix A provides a sample installation andC                  configuration script as might appear on an OpenVMS ?                  system upon which TCP/IP Services has not been G                  installed previously. The script examples in Chapter 3 @                  show what might be seen when you upgrade TCP/IP#                  Services software.            Related Documents   H               Table 1 lists the documents available with this version of               TCP/IP Services.  H         Table_1_TCP/IP_Services_Documentation___________________________  H         Manual____________________Contents______________________________  H         DIGITAL TCP/IP Services   This manual provides conceptual infor-H         for OpenVMS Concepts and  mation about networking and the TCP/IPB         Planning                  protocol including a descriptionE                                   of the Compaq implementation of the F                                   Berkeley Internet Name Domain (BIND)E                                   service and the Network File System E                                   (NFS). It outlines general planning G                                   issues to consider before configuring H                                   your system to use the TCP/IP Services+                                   software.   H                                   This manual also describes the manualsD                                   in the documentation set, providesB                                   a glossary of terms and acronymsB                                   for the TCP/IP Services softwareG                                   product, and documents how to contact F                                   the InterNIC Registration Service toF                                   register domains and access Requests6                                   for Comments (RFCs).  H                                                 (continued on next page)        
         vi                 H         Table_1_(Cont.)_TCP/IP_Services_Documentation___________________  H         Manual____________________Contents______________________________  D         Compaq TCP/IP Services    The release notes provide version-F         for OpenVMS Release       specific information that supersedesF         Notes                     the information in the documentationF                                   set. The features, restrictions, andD                                   corrections in this version of theG                                   software are described in the release F                                   notes. Always read the release notesA                                   before installing the software.   E         Compaq TCP/IP Services    This manual explains how to install C         for OpenVMS Installation  and configure the TCP/IP Services *         and Configuration         product.  B         DIGITAL TCP/IP Services   This manual describes how to useA         for OpenVMS User's Guide  the applications available with E                                   TCP/IP Services such as remote file D                                   operations, email, TELNET, TN3270,C                                   and network printing. This manual D                                   explains how to use these services@                                   to communicate with systems onG                                   private internets or on the worldwide +                                   Internet.   H         Compaq TCP/IP Services    This manual describes how to configure@         for OpenVMS Management    and manage the TCP/IP Services*                                   product.  A                                   Use this manual with the Compaq H                                   TCP/IP Services for OpenVMS Management;                                   Command Reference manual.   B         Compaq TCP/IP Services    This manual describes the TCP/IP?         for OpenVMS Management    Services management commands. A         Command Reference         Use this manual with the Compaq   H                                   TCP/IP Services for OpenVMS Management)                                   manual.   H                                                 (continued on next page)    H                                                                      vii                 H         Table_1_(Cont.)_TCP/IP_Services_Documentation___________________  H         Manual____________________Contents______________________________  F         Compaq TCP/IP Services    This reference card lists the TCP/IPF         for OpenVMS Management    management commands by component andH         Command Quick Reference   describes the purpose of each command.         Card  >         Compaq TCP/IP Services    This reference card containsF         for OpenVMS UNIX Command  information about commonly performedD         Reference Card            network management tasks and theirE                                   corresponding TCP/IP management and D                                   Compaq Tru64 UNIX command formats.  B         DIGITAL TCP/IP Services   This manual presents an overviewA         for OpenVMS ONC RPC       of high-level programming using ?         Programming               open network computing remoteoB                                   procedure calls (ONC RPCs). This?                                   manual also describes the RPC F                                   programming interface and how to useH                                   the RPCGEN protocol compiler to create/                                   applications.   >         Compaq TCP/IP Services    This manual describes how toA         for OpenVMS Sockets       use the Sockets API and OpenVMS D         API and System Services   system services to develop network/         Programming               applications.   B         Compaq TCP/IP Services    This manual describes the SimpleD         for OpenVMS SNMP          Network Management Protocol (SNMP)F         Programming and           and the SNMP application programmingA         Reference                 interface (eSNMP). It describes D                                   the subagents provided with TCP/IPB                                   Services, utilities provided forF                                   managing subagents, and how to build5                                   your own subagents.   H                                                 (continued on next page)                     viii                 H         Table_1_(Cont.)_TCP/IP_Services_Documentation___________________  H         Manual____________________Contents______________________________  B         Compaq TCP/IP Services    This manual provides informationD         for OpenVMS Tuning and    about how to isolate the causes ofF         Troubleshooting           network problems and how to tune theG                                   TCP/IP Services software for the best .                                   performance.  @         Compaq TCP/IP Services    This manual describes the IPv6C         for OpenVMS Guide to      environment, the roles of systemsi@         IPv6                      in this environment, the typesD                                   and function of the different IPv6H                                   addresses, and how to configure TCP/IPH         __________________________Services_to_access_the_6bone_network._  H               For a comprehensive overview of the TCP/IP protocol suite,B               you might find the book Internetworking with TCP/IP:H               Principles, Protocols, and Architecture, by Douglas Comer,               useful.            Reader's Commentsw  G               Compaq welcomes your comments on this manual. Please sendt<               comments to either of the following addresses:  /               Internet    openvmsdoc@compaq.coma  5               Mail        Compaq Computer Corporationt>                           OSSG Documentation Group, ZKO3-4/U08,                           110 Spit Brook Rd./                           Nashua, NH 03062-2698   -         How to Order Additional Documentationb  H               Visit the following World Wide Web address for information:               about how to order additional documentation:  ,               http://www.openvms.compaq.com/  F               If you need help deciding which documentation best meets,               your needs, call 800-282-6672.    H                                                                       ix r                        Conventionse  2               The name TCP/IP Services means both:  9               o  Compaq TCP/IP Services for OpenVMS AlphaT  7               o  Compaq TCP/IP Services for OpenVMS VAXI  E               The name UNIX refers to the Compaq Tru64 UNIX operatingt               system.e  @               The following conventions are used in this manual.@               In addition, please note that all IP addresses areD               fictitious. The following conventions are used in thisH               manual. In addition, please note that all IP addresses are               fictitious.   G               Ctrl/x           A sequence such as Ctrl/x indicates thateF                                you must hold down the key labeled CtrlH                                while you press another key or a pointing-                                device button.   F               PF1 x            A sequence such as PF1 x indicates thatG                                you must first press and release the key E                                labeled PF1 and then press and release G                                another key or a pointing device button.   D               <Return>         In examples, a key name enclosed in aD                                box indicates that you press a key onH                                the keyboard. (In text, a key name is not2                                enclosed in a box.)  D                                In the HTML version of this document,C                                this convention appears as brackets,m1                                rather than a box.   F                . . .           A horizontal ellipsis in examples indi-H                                cates one of the following possibilities:  D                                o  Additional optional arguments in a>                                   statement have been omitted.  D                                o  The preceding item or items can be=                                   repeated one or more times.   C                                o  Additional parameters, values, orrC                                   other information can be entered.e  	         x  f  r              @               .                A vertical ellipsis indicates theD               .                omission of items from a code exampleG               .                or command format; the items are omitted.D                                because they are not important to the5                                topic being discussed.D  >               ( )              In command format descriptions,A                                parentheses indicate that you must.D                                enclose choices in parentheses if you5                                specify more than one.   G               [ ]              In command format descriptions, brackets-H                                indicate optional choices. You can chooseD                                one or more items or no items. Do notE                                type the brackets on the command line.0E                                However, you must include the brackets B                                in the syntax for OpenVMS directoryA                                specifications and for a substring H                                specification in an assignment statement.  G               |                In command format descriptions, vertical D                                bars separate choices within bracketsF                                or braces. Within brackets, the choicesD                                are optional; within braces, at leastF                                one choice is required. Do not type theA                                vertical bars on the command line.   E               { }              In command format descriptions, braces B                                indicate required choices; you mustG                                choose at least one of the items listed. D                                Do not type the braces on the command$                                line.  H               bold text        This typeface represents the introductionD                                of a new term. It also represents theF                                name of an argument, an attribute, or a&                                reason.              H                                                                       xi e  C              >               italic text      Italic text indicates important>                                information, complete titles ofG                                manuals, or variables. Variables include G                                information that varies in system output B                                (Internal error number), in commandE                                lines (/PRODUCER=name), and in command.F                                parameters in text (where dd representsH                                the predefined code for the device type).  H               UPPERCASE TEXT   Uppercase text indicates names of OpenVMSE                                and Compaq TCP/IP Services for OpenVMS.C                                commands, options, utilities, files,l=                                directories, hosts, and users.f  E               Monospace text   Monospace type indicates code examplesr?                                and interactive screen displays.   B                                This typeface indicates UNIX systemG                                output or user input, commands, options,_H                                files, directories, utilities, hosts, and%                                users.   B                                In the C programming language, this@                                typeface identifies the following?                                elements: keywords, the names ofoH                                independently compiled external functions?                                and files, syntax summaries, and E                                references to variables or identifiers 8                                introduced in an example.  F               -                A hyphen at the end of a command formatF                                description, command line, or code lineF                                indicates that the command or statement?                                continues on the following line.                              xii                        H                                                                        1H         ________________________________________________________________  H                       Preparing to Install and Configure TCP/IP Services      E               This chapter explains how to prepare for installing andVF               configuring Compaq TCP/IP Services for OpenVMS software.  2         1.1 Understanding the Major Tasks Involved  F               Installing the TCP/IP Services software takes just a fewF               minutes to complete. You can install the software duringG               the OpenVMS operating system installation procedure or as                 a layered product.  G               After you install TCP/IP Services, you need to enable theeG               components and verify the configuration through the menu- H               driven TCPIP$CONFIG configuration procedure. This step may0               take about 15 minutes to complete.  H               Table 1-1 lists the major tasks involved in installing andH               configuring TCP/IP Services and the sections that describe               these tasks.                                  H                   Preparing to Install and Configure TCP/IP Services 1-1 g  a      :         Preparing to Install and Configure TCP/IP Services2         1.1 Understanding the Major Tasks Involved  H               Table_1-1_Major_Tasks:_Installing_and_Configuring_________  H               Step_Task________________________________Described_in...__  G               1    Prepare for installation and        Sections 1.2 anda:                    configuration.                      1.3  B               2    Shut down any previous versions     Section 2.14                    of TCP/IP Services running on the                    system.  @               3    Install TCP/IP Services.            Chapter 2  @               4    Configure TCP/IP Services           Chapter 33                    according to your network needs.l  B               5    Start TCP/IP Services.              Section 3.5  B               6    Verify the configuration.           Section 3.6  B               7    Complete additional configuration   Section 3.7H               _____and_setup_tasks,_as_appropriate._____________________  !         1.2 Preinstallation Tasks   F               Table 1-2 lists the tasks you should complete before youF               install TCP/IP Services on your system, and the sections(               that describe these tasks.                                  >         1-2 Preparing to Install and Configure TCP/IP Services           H                       Preparing to Install and Configure TCP/IP ServicesH                                                1.2 Preinstallation Tasks  H               Table_1-2_Preinstallation_Tasks___________________________  H               Step_Task________________________________Described_in...__  D               1    Inspect the distribution kit.       Section 1.2.1  D               2    Extract and read the TCP/IP         Section 1.2.2*                    Services release notes.  D               3    Back up the system disk.            Section 1.2.3  D               4    Perform an OpenVMS operating        Section 1.2.31                    system upgrade, if applicable._  D               5    Register the TCP/IP Services        Section 1.2.4                    license PAK.o  E               6    Check the disk space, memory, and   Sections 1.2.5eD                    system parameters.                  through 1.2.7  D               7    Assign a user identification code   Section 1.2.8'                    (UIC), if necessary.i  B               8    Assemble information for            Section 1.3H               _____configuration._______________________________________  -         1.2.1 Inspecting the Distribution Kit   F               Make sure you have a complete software distribution kit.F               If you have the OpenVMS consolidated distribution CD-ROME               kit, check the CD master index for the kit location. IfrE               you have a magnetic tape or TK50 kit, supply the deviceoF               name for the media when you issue the command to install               TCP/IP Services.  G               Check that the kit contains everything listed on the Bill D               of Materials (BOM). If anything is missing or damaged,1               contact your Compaq representative.   *         1.2.2 Extracting the Release Notes  B               The Compaq TCP/IP Services for OpenVMS Release NotesE               document contains important information you should knoww-               before you install the product.t  @               To extract the release notes to a text file, enterD               the following POLYCENTER Software Installation utility               command:  F               $ PRODUCT EXTRACT RELEASE_NOTES TCPIP/FILE=file-name.TXT  H                   Preparing to Install and Configure TCP/IP Services 1-3 p  M      :         Preparing to Install and Configure TCP/IP Services!         1.2 Preinstallation Taskse  G               where file-name.TXT is the file name you give the release C               notes. If you do not specify a file name, the releasesK               notes are written to a file called DEFAULT.PCSI$RELEASE_NOTESr'               in the current directory.   >         1.2.3 Backing Up the System Disk and Upgrading OpenVMS  H               Before you install TCP/IP Services, Compaq recommends thatE               you back up the system disk using the backup procedures E               established at your site. After the backup operation is H               complete, you should upgrade the OpenVMS operating system,               if applicable.  E               For information about backing up a system disk, see the :               OpenVMS System Manager's Manual: Essentials.  H               For information about how to upgrade OpenVMS, refer to theB               appropriate OpenVMS upgrade and installation manual.  ?         1.2.4 Registering the License Product Authorization Key   D               Before you install TCP/IP Services on a newly licensedB               node or cluster, you must register a License Product?               Authorization Key (PAK) using the OpenVMS License C               Management Facility (LMF). Without a PAK, you can use 8               only DECwindows TCP/IP Transport software.  G               If you are upgrading TCP/IP Services on a node or cluster B               that is licensed for this software, you have alreadyB               completed the License PAK registration requirements.  D               If you ordered the license and the media together, theH               PAK is included with your distribution kit. Otherwise, theH               PAK is shipped separately to the location specified on the               license order.  A               If you are also installing prerequisite or optionalnF               software, review the PAK status and install the PAKs forF               any prerequisite or optional software before you install               TCP/IP Services.  H               To register a license, log in to the SYSTEM account and do#               one of the following:   E               o  Run the SYS$UPDATE:VMSLICENSE.COM file and enter the ,                  data from your License PAK.  >         1-4 Preparing to Install and Configure TCP/IP Services           H                       Preparing to Install and Configure TCP/IP ServicesH                                                1.2 Preinstallation Tasks  F               o  At the DCL prompt, enter the LICENSE REGISTER command0                  and the appropriate qualifiers.  E               You must register a license for each node in an OpenVMSo               Cluster.  A               For complete information about LMF, see the OpenVMS_0               License Management Utility Manual.  %         1.2.5 Checking the Disk Space   B               Make sure your system meets the following disk space               requirements:w  H               __________________________________________________________H               System_____________Minimum_Block_Size_____________________  '               OpenVMS Alpha      75,000h  H               OpenVMS_VAX________52,000_________________________________  B               The actual disk space needed varies depending on theF               system environment, configuration, and software options.  H               To find out how many free blocks exist on the system disk,               enter:  )               $ SHOW DEVICE SYS$SYSDEVICEs  *         1.2.6 Checking the Physical Memory  F               Make sure the system meets the following physical memory               requirements:n  H               __________________________________________________________H               System_____________Minimum_Memory_________________________  &               OpenVMS Alpha      32 MB  H               OpenVMS_VAX________24_MB__________________________________  )               To check the memory, enter:n                  $ SHOW MEMORY/FULL  H                   Preparing to Install and Configure TCP/IP Services 1-5 n  i      :         Preparing to Install and Configure TCP/IP Services!         1.2 Preinstallation Tasks   ,         1.2.7 Checking the System Parameters  A               Most systems have adequate system resources readilya@               available to include the TCP/IP Services software.F               However, you should check the system parameters outlinedF               in the following sections. Make any necessary changes toG               the MODPARAMS.DAT file, then run AUTOGEN, and reboot your                system.   3         1.2.7.1 Global Pagelets and Global Sectionsn  F               The TCP/IP Services software requires 65 global sections'               and 8100 global pagelets.   B               To check the number of available global pagelets andE               global sections, enter WRITE commands with the F$GETSYI D               lexical functions. The following is an example from an#               OpenVMS Alpha system:n  :               $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLPAGES")               143576  :               $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLSECTS")               249e  F               To increase the global pagelets and global sections, addB               statements to the SYS$SYSTEM:MODPARAMS.DAT file thatC               increase the values of the system parameters GBLPAGES ;               and GBLSECTIONS, as in the following example:i  !               ADD_GBLPAGES = 7500v"               ADD_GBLSECTIONS = 75  %         1.2.7.2 Nonpaged Dynamic Poola  E               Add at least 500,000 bytes of nonpaged dynamic pool for '               the software, as follows:l  .               1. Log in to the SYSTEM account.  E               2. Identify the amount of additional nonpaged pool your D                  system requires. Use the estimated value of 500,000D                  bytes, and then increase the value depending on theE                  maximum amount of sockets you have. For each socket, .                  allow a value of 2,000 bytes.  F                 ________________________Note  ________________________  =                 On a system that uses FDDI, the default sizes A                 for the TCP/IP socket buffer quotas are increased   >         1-6 Preparing to Install and Configure TCP/IP Services           H                       Preparing to Install and Configure TCP/IP ServicesH                                                1.2 Preinstallation Tasks  C                 automatically. This increases throughput across the /                 FDDI for local TCP connections.   E                 _____________________________________________________   >               3. Refer to the following example, and then editC                  MODPARAMS.DAT to reflect the appropriate value for 6                  the NPAGEDYN and NPAGEVIR parameters:  L                  ! Add nonpaged pool for Compaq TCP/IP Services for OpenVMS.                  !$                  ADD_NPAGEDYN=500000$                  ADD_NPAGEVIR=500000  G               For more information about nonpaged dynamic pool, see the :               OpenVMS System Manager's Manual: Essentials.  0         1.2.7.3 Interrupt Stack Pages (VAX Only)  D               If you are using PATHWORKS Internet Protocol (PWIP) onC               an OpenVMS VAX system, you should increase the number E               of interrupt stack pages (INTSTKPAGES) to 12 or more to E               help eliminate system startup warnings and crashes. For C               information about the PATHWORKS for OpenVMS (Advanced 7               Server), see the PATHWORKS documentation.n  D               To increase the number of interrupt stack pages, add aD               statement to the MODPARAMS.DAT file that increases theB               value of the INTSTKPAGES system parameter, as in the                following example:  "               ADD_INTSTKPAGES = 12  >         1.2.7.4 System Page Table Entries Parameter (VAX Only)  D               On VAX systems, make sure the AUTOGEN parameter SPTREQF               is set to at least 6000. Run SYSMAN to check the minimum&               SPTREQ value as follows:  %               $ RUN SYS$SYSTEM:SYSMANs  +               SYSMAN> parameter show sptreqwE               %SYSMAN, a USE ACTIVE has been defaulted on node VMSVAXq  6               Node VMSVAX:   Parameters in use: ACTIVE^               Parameter Name            Current    Default    Minimum    Maximum Unit  Dynamic^               --------------            -------    -------    -------    ------- ----  -------V               SPTREQ                       8000       3900       3000         -1 Pages  H                   Preparing to Install and Configure TCP/IP Services 1-7           :         Preparing to Install and Configure TCP/IP Services!         1.2 Preinstallation Taskso                 SYSMAN>r  C               To modify the minimum SPTREQ, run the AUTOGEN commandiE               procedure as described in the OpenVMS System Management H               Utilities Reference Manual: A-L. Modify the minimum SPTREQ               value as follows:l                 MIN_SPTREQ = 6000i  2         1.2.8 Assigning a User Identification Code  B               An OpenVMS user or group of users is identified by aD               unique, assigned user identification code (UIC) in theH               format [group,member], where group and member are numeric,H               alphanumeric, or alphabetic characters. For example, a UICH               can be either [306,210], [GROUP1, JONES], or simply JONES.H               The UIC is linked to a system-defined rights database that3               determines user and group privileges.p  G               The TCPIP$CONFIG configuration procedure uses a group UICCD               to create accounts for components. If a user-specifiedD               UIC is not in place from a previous configuration, theA               octal number 3655 (the default UIC group number forsF               service accounts) is used. If this is an initial productF               configuration but the procedure detects that number 3655D               is in use, you are prompted for a new UIC group number(               when you run TCPIP$CONFIG.  F               Before you assign a new group UIC, check that the numberG               you chose is not already in use by entering the followingr               commands:   (               $ RUN SYS$SYSTEM:AUTHORIZE  4               UAF> SHOW /BRIEF [your-group-number,*]  D               UAF> SHOW /IDENTIFIER /VALUE=UIC:[your-group-number,*]                >         1-8 Preparing to Install and Configure TCP/IP Services s  a      H                       Preparing to Install and Configure TCP/IP ServicesH                                                1.2 Preinstallation Tasks  E               To force TCPIP$CONFIG to allow you to specify a new UIC E               group number, assign the value TRUE to the logical name H               TCPIP$ASK_GROUP_UIC, as in the following example. When youE               configure TCP/IP Services, TCPIP$CONFIG prompts you for                the group UIC.  /               $ DEFINE TCPIP$ASK_GROUP_UIC TRUE   0         1.3 Assembling Configuration Information  F               Use the worksheet in Table 1-3 to assemble configuration               information.  B               If you are configuring TCP/IP Services on the systemD               for the first time, the TCPIP$CONFIG procedure promptsE               you for the information listed in Table 1-3. If you areaG               reconfiguring after a product upgrade, the procedure usesrG               the previous configuration information as the default fore$               the new configuration.  E               For information to help you answer the questions on theeF               configuration worksheet, see appropriate chapters in theB               Compaq TCP/IP Services for OpenVMS Management guide.                                            H                   Preparing to Install and Configure TCP/IP Services 1-9 t         :         Preparing to Install and Configure TCP/IP Services0         1.3 Assembling Configuration Information  H         Table_1-3_Configuration_Planning_Worksheet______________________  H         _____Question__________________________________Answer___________  H         What is the system's host name (for example,   _________________         MYNODE)?  H         What is the system's Internet domain name      _________________#         (for example, widgets.com)?s  H         Do you plan to have your IP interface under    _________________.         control of the DHCP client? If so, the2         next items on this worksheet (the system's5         addresses and masks, and the system's network 5         interface), might be configured automaticallyu0         by the DHCP server, in which case you do2         not need to specify them. Ask your network         manager for details.    5         What are the system's addresses and masks?[1]   H         *    IP address (for example, 19.112.139.14)   _________________  H         *    Subnet (network mask) address (for        _________________               example, 255.0.0.0)  H         *    Broadcast address (for example,           _________________              19.255.255.255)  H         What is the system's network interface (for    _________________         example, SE0)?[1]   H         What is the group UIC for TCP/IP Services      _________________9         (see Section 1.2.8)? For example, [GROUP1,JONES].P  H         [1]If_the_IP_interface_runs_under_control_of_the_DHCP_client,___  F         this information might be configured automatically. Check withG         your network manager. For more information, see the DHCP clientp         documentation.  H                                                 (continued on next page)    ?         1-10 Preparing to Install and Configure TCP/IP Services_ _  _      H                       Preparing to Install and Configure TCP/IP ServicesH                                 1.3 Assembling Configuration Information  H         Table_1-3_(Cont.)_Configuration_Planning_Worksheet______________  H         _____Question__________________________________Answer___________  H         Which type of routing is appropriate for the   _________________#         network, Static or Dynamic?n  /              Static - For simple networks wherec!              routes do not changee  3              If static, enter the default gateway's 0              host name and address (for example,"              GATWY1; 19.112.0.65).  1              Dynamic - For complex networks where $              flexibility is required  0              If dynamic, you must specify either%              ROUTED or GATED routing.c  3         Do you plan to enable the BIND resolver? If          so:c  H         *    What is the name of the BIND server you   _________________3              want the resolver to use (for example,i              MAINSV)?e  H         *    What is the IP address of the BIND        _________________1              server (for example, 19.112.139.10)?   H         *    What is the domain name (for example,     _________________!              mainsv.widgets.com)?   +         Do you plan to enable SNMP? If yes:e  H         *    Do you want to allow SNMP management      _________________2              clients to modify the MIBs by issuing              set requests?  H         *    Do you want to enable authentication      _________________1              traps when the master agent receives .              an SNMP request that specifies an+              unauthorized community string?O  H         *    What is the name of the system's contact  _________________5              person? Specify text as in the followingp               example: Sam Spade.  H                                                 (continued on next page)  H                  Preparing to Install and Configure TCP/IP Services 1-11    D      :         Preparing to Install and Configure TCP/IP Services0         1.3 Assembling Configuration Information  H         Table_1-3_(Cont.)_Configuration_Planning_Worksheet______________  H         _____Question__________________________________Answer___________  H         *    What is the location of the system?       _________________4              Specify one or two fields of text as in*              the following three examples:  +              - Falcon Building, Los Angelest              - Boston, MA.              - Northwest  H         *    Do you want to allow any network manager  _________________4              to remotely monitor your system? If so,3              you need to specify a public community 3              name. The default is "public." Specifyi0              a string consisting of alphanumeric0              characters only. Do not enclose the4              string in quotes: the case is preserved+              as you enter it. Example: Rw2.   H         *    Do you want to provide additional         _________________/              community names and addresses (for 3              implementing traps and allowing accessn5              beyond the default read-only provided bycH         _____the_"public"_community)?___________________________________                                      ?         1-12 Preparing to Install and Configure TCP/IP Servicesu r  t                  H                                                                        2H         ________________________________________________________________  H                                               Installing TCP/IP Services      D               This chapter explains how to install the Compaq TCP/IP@               Services for OpenVMS software as a layered productE               using the POLYCENTER Software Installation utility. The F               instructions are appropriate for an initial installation               or an upgrade.  G               For information about how to install the product directly F               from the OpenVMS Alpha CD-ROM menu, refer to the OpenVMS4               Alpha Upgrade and Installation Manual.  H               For information about the POLYCENTER Software InstallationD               utility, refer to the OpenVMS System Manager's Manual:               Essentials.S  "         2.1 Installation Procedure  E               When you have completed the recommended preinstallationfC               tasks outlined in Chapter 1 and have read the release H               notes (Section 1.2.2), you are ready to upgrade or install               TCP/IP Services.  H               During a product upgrade, existing configuration files areG               preserved in case you want to use them when you configurer+               this version of the software.   G               To install the TCP/IP Services software on an OpenVMS VAXs2               or Alpha system, proceed as follows:  .               1. Log in to the SYSTEM account.  F               2. Check to make sure that other users are not logged in                  to the system.i  F               3. Edit the SYS$STARTUP:SYSTARTUP_VMS.COM file and checkB                  to see if the command @SYS$STARTUP:UCX$STARTUP isH                  defined. If this command is defined, edit the line, re-O                  placing the command definition with @SYS$STARTUP:TCPIP$STARTUPh  H                                           Installing TCP/IP Services 2-1 _  _      "         Installing TCP/IP Services"         2.1 Installation Procedure  >                  so that the new version of the product starts9                  automatically when the system starts up.t  F               4. If a previous version of the software is installed onE                  the system, shut it down. Enter one of the following                   commands:  H                  _______________________________________________________                  Software_H                  Version_____Use_This_Command___________________________  :                  Version     @SYS$MANAGER:UCX$SHUTDOWN.COM                  4.x  <                  Version     @SYS$STARTUP:TCPIP$SHUTDOWN.COMH                  5.x____________________________________________________  @               5. Compaq recommends that you log the installationA                  procedure. If you have DECnet configured on youraA                  system, you can create a log of the installation E                  procedure by entering the following command and thene4                  log in to the system account again:  4                  $ SET HOST 0/LOG=file-specification  D                  where file-specification is the name of the file toE                  which you want the log written. The log file will be 2                  written to the current directory.  F               6. Start the POLYCENTER Software Installation utility byH                  entering the PRODUCT INSTALL command with the directory?                  path appropriate for your system. For example:s  ?                  $ PRODUCT INSTALL TCPIP /SOURCE=directory-paths  F                  where directory-path specifies the disk and directory@                  name for the source drive that holds the TCP/IPI                  Services kit. For example, /SOURCE=DKA400:[TCPIPAXP051].U  @                  If you do not specify the source qualifier, theF                  POLYCENTER Software Installation utility searches theE                  location defined by the logical name PCSI$SOURCE. If F                  not defined, the utility searches the current default                  directory.f  G               7. The interactive installation procedure begins, and youf.                  are prompted for information.  &         2-2 Installing TCP/IP Services           H                                               Installing TCP/IP ServicesH                                               2.1 Installation Procedure  F                  Example 2-1 shows a sample installation on an OpenVMSA                  Alpha system that has earlier versions of TCP/IPsA                  Services installed on it. Additional explanatory D                  information follows each portion of the script. ForG                  a sample installation on a system on which the productaE                  has never been installed previously, see Appendix A._  D                  The actual installation output that is displayed onB                  your system might vary, depending on your current                  configuration.   F                 ________________________Note  ________________________  C                 To stop the installation at any time, press Ctrl/Y. A                 The installation procedure deletes any files thatT)                 were created, then exits.   E                 _____________________________________________________e  C         Example 2-1 TCP/IP Services Installation: Sample POLYCENTER_;                     Software Installation Utility Procedure,  B            1 - DEC AXPVMS TCPIP V5.1-0             Layered ProductB            2 - DEC AXPVMS TCPIP V5.0-11            Layered Product(            3 - All products listed above            4 - Exitr  N         Choose one or more items from the menu separated by commas: 1 <Return>  B                  The menu that is displayed initially includes theC                  latest TCP/IP Services product and any versions ofME                  the product that are in place on the system. InstallV/                  the latest version (option 1).R  0         The following product has been selected:D             DEC AXPVMS TCPIP V5.1                    Layered Product  /         Do you want to continue? [YES] <Return>   ?                  Press Return to continue with the installationo                  procedure.         H                                           Installing TCP/IP Services 2-3 d  m      "         Installing TCP/IP Services"         2.1 Installation Procedure      (         Configuration phase starting ...  V         You will be asked to choose options, if any, for each selected product and forW         any products that may be installed to satisfy software dependency requirements..  B         DEC AXPVMS TCPIP V5.1: Compaq TCP/IP Services for OpenVMS.  F             (c) Compaq Computer Corporation 2000. All rights reserved.  '             Compaq Computer Corporatione  N             Compaq TCP/IP Services for OpenVMS offers several license options.  @         Do you want the defaults for all options? [YES] <Return>  J                  Answer YES to choose the POLYCENTER Software InstallationG                  utility defaults for the options or NO to choose other                   options.   8         Do you want to review the options? [NO] <Return>  J                  Answer YES to review the POLYCENTER Software InstallationF                  utility options. In this example, the options are not                  reviewed.  E                  If you select YES, the options are displayed and you F                  are asked whether you are satisfied with the options.G                  Press Return to accept the options as listed or answer *                  NO to change the options.  $         Execution phase starting ...  ?         The following product will be installed to destination: N             DEC AXPVMS TCPIP V5.1                  DISK$ALPHASYS:[VMS$COMMON.]?         The following product will be removed from destination:eN             DEC AXPVMS TCPIP V5.0-11               DISK$ALPHASYS:[VMS$COMMON.]  N         Portion done: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%  A                  The following message appears only if an earlier B                  version of TCP/IP Services was configured on yourF                  system. A similar message, verifying the product nameC                  and version, appears if you are installing for thet                  first time.  &         2-4 Installing TCP/IP Services           H                                               Installing TCP/IP ServicesH                                               2.1 Installation Procedure    =         %PCSI-I-PRCOUTPUT, output from subprocess follows ...          % TCPIP-W-PCSI_INSTALL         % - BG device exists.eQ         %   To use the version of Compaq TCP/IP Services that was just installed, $         %   system must be rebooted.	         %            Portion done: 100%  1         The following product has been installed:yB             DEC AXPVMS TCPIP V5.1                  Layered Product/         The following product has been removed:sB             DEC AXPVMS TCPIP V5.0-11               Layered Product  D         DEC AXPVMS TCPIP V5.1-0: Compaq TCP/IP Services for OpenVMS.  F             Check the release notes for current status of the product.  ;               8. After the installation completes, you can:   ?                  -  Read the Compaq TCP/IP Services for OpenVMS @                     Release Notes on line or print the file fromT                     SYS$HELP:TCPIP051.RELEASE_NOTES.PS or SYS$HELP:TCPIP051.RELEASE_                     NOTES.TXT.  D                  -  Display a list of the TCP/IP Services files that@                     were installed. Enter the following command:  ?                     $ PRODUCT LIST TCPIP /SOURCE=directory-path   F                     where directory-path specifies the disk and direc-H                     tory name for the source drive that holds the TCP/IPM                     Services kit (for example, /SOURCE=DKA400:[TCPIPAXP051]).3?                     If you do not specify the source qualifier, @                     the POLYCENTER Software Installation utilityE                     searches the location defined by the logical name E                     PCSI$SOURCE. If not defined, the utility searches 2                     the current default directory.  A               9. If you had a previous version of TCP/IP Services ?                  configured on your system and the software was C                  previously started, reboot your system for the new D                  TCP/IP Services software to take effect. Proceed to                  step 11.v  H                                           Installing TCP/IP Services 2-5           "         Installing TCP/IP Services"         2.1 Installation Procedure  E                 _____________________ Important _____________________   <                 Do not delete any files that remain from the>                 previous version of the product. Many of theseB                 files are used by TCPIP$CONFIG for converting your?                 existing configuration to the new configuration_)                 (described in Chapter 3).   E                 _____________________________________________________a  D              10. Log out of the SYSTEM account, and then log back inE                  to the SYSTEM account to establish the TCPIP commande                  environment.r  C              11. Proceed to Chapter 3 to configure TCP/IP Services.w                                                            &         2-6 Installing TCP/IP Services                       H                                                                        3H         ________________________________________________________________  H                                              Configuring TCP/IP Services      C               After you install Compaq TCP/IP Services for OpenVMS,eG               you need to enable the components and characteristics you_F               require for your particular system using the menu-driven%               TCPIP$CONFIG procedure._  D               This chapter explains the TCPIP$CONFIG menus, providesC               sample installation output, and summarizes additional?,               configuration and setup tasks.  =         3.1 Recommended Order for Configuring TCP/IP Services   C               Table 3-1 lists the tasks involved in configuring the C               TCP/IP Services components and functionality, and thep1               sections that describe these tasks.                                           H                                          Configuring TCP/IP Services 3-1           #         Configuring TCP/IP Serviceso=         3.1 Recommended Order for Configuring TCP/IP Services   H               Table_3-1_Configuring_TCP/IP_Services_____________________  D                                                            DescribedH               StepTask_____________________________________in...________  F               1   Assemble system information to prepare   Section 1.3+                   for running TCPIP$CONFIG.o  F               2   Run TCPIP$CONFIG. If you have a TCP/IP   Section 3.35                   Services V4.x configuration on your 3                   system, answer prompts to convertT8                   existing databases or create new ones.  F               3   If preferred, have TCP/IP Services       Section 3.28                   software configured automatically by a                   DHCP server.  H               4   Manually configure the major components  Section 3.3.47                   and functionality using TCPIP$CONFIG.   H               5   Configure the optional components using  Section 3.3.7.                   TCPIP$CONFIG, as applicable.  F               6   Start TCP/IP Services.                   Section 3.5  F               7   Verify the configuration.                Section 3.6  F               8   Complete additional configuration        Section 3.7H               ____tasks,_as_appropriate.________________________________  A         3.2 Automatic Configuration of TCP/IP Services Using DHCP              Client  C               TCP/IP Services Version 5.1 supports the DHCP client,_G               which allows you to have your system configured automati- H               cally by a DHCP server. You can achieve this in one of two               ways:   @               o  If TCP/IP Services has never been configured onE                  your system, you can run the TCP/IP Services startup F                  procedure, SYS$MANAGER:TCPIP$STARTUP.COM. The startupD                  procedure detects the fact that the TCP/IP ServicesF                  software has not been configured and asks whether youD                  want the DHCP client to configure the host for you.                  Answer YES.  '         3-2 Configuring TCP/IP Services_ _         H                                              Configuring TCP/IP ServicesH         3.2 Automatic Configuration of TCP/IP Services Using DHCP Client  G                  The startup procedure invokes TCPIP$CONFIG, which setsgF                  up the environment for the DHCP client and designatesD                  any unconfigured interfaces to be under DHCP clientD                  control. The procedure enables the following set of(                  services automatically:                    -  FTP client  !                  -  TELNET cliente  !                  -  TELNET server                     -  SMTP  G                  For more information about DHCP, see the Compaq TCP/IP 8                  Services for OpenVMS Management manual.  >               o  Run TCPIP$CONFIG. Select option 2 in the Core@                  Environment Configuration menu to configure theF                  Internet interface, and then select option 2 from the.                  Interface Configuration menu:  '                  Configuration options:o  J                       1 - Configure interface manually   (Current default)6                       2 - Let DHCP configure interface  F                  You can also use TCPIP$CONFIG to configure additional4                  services and parameters, as needed.            3.3 Running TCPIP$CONFIG  F               The TCPIP$CONFIG procedure displays menus from which you               do the following:   H               o  Make selections that enable components for your system.=                  To select the default, press the Return key.   8               o  Start or stop TCP/IP Services software.  *               o  Verify the configuration.  $               To get started, enter:  )               $ @SYS$MANAGER:TCPIP$CONFIGn  H                                          Configuring TCP/IP Services 3-3 e  S      #         Configuring TCP/IP Services           3.3 Running TCPIP$CONFIG  E         3.3.1 Converting Existing TCP/IP Services Configuration Filesf               (Upgrade Only)  H               If you have a TCP/IP Services for OpenVMS (UCX) configura-G               tion in place from a V4.x version of the product, and youuE               have never configured a V5.x product on the system, theuF               procedure begins by prompting you whether to convert the6               old TCP/IP Services configuration files:  5               Convert the old configuration files [Y]t  @               Unless you respond NO to the prompt, the procedureH               converts existing configuration files to new configuration               files.  H               If you have already configured this product, the procedureA               indicates that no new configuration files are being                created:  P               Checking TCP/IP Services for OpenVMS configuration database files.  1               No new database files were created.E  @               The following sample output shows the start of theD               TCPIP$CONFIG procedure and a portion of the conversion*               of a previous configuration:  6                 TCP/IP Network Configuration Procedure  A           This procedure helps you define the parameters required C           to run Compaq TCP/IP Services for OpenVMS on this system.t             NOTE:cG           TCP/IP has been previously configured from an earlier versionwG           of this product.  You can avoid a complete reconfiguration ofyH           TCP/IP by allowing this procedure to automatically convert theI           old configuration files.  If you choose not to do this now, youhI           will not be asked again.  At the end of the conversion you will_7           be able to further modify your configuration.   9         Convert the old configuration files [Y]: <Return>_)         Preparing files for conversion...V      '         3-4 Configuring TCP/IP Services            H                                              Configuring TCP/IP ServicesH                                                 3.3 Running TCPIP$CONFIG  8             UCX$SERVICE.DAT        --> TCPIP$SERVICE.DAT5             UCX$HOST.DAT           --> TCPIP$HOST.DATe8             UCX$NETWORK.DAT        --> TCPIP$NETWORK.DAT6             UCX$ROUTE.DAT          --> TCPIP$ROUTE.DAT6             UCX$PROXY.DAT          --> TCPIP$PROXY.DAT>             UCX$CONFIGURATION.DAT  --> TCPIP$CONFIGURATION.DAT7             UCX$EXPORT.DAT         --> TCPIP$EXPORT.DAT-9             UCX$PRINTCAP.DAT       --> TCPIP$PRINTCAP.DATw  2                No new database files were created.            FTP SERVER Configuration            LPD SERVER Configuration  -         Service is not defined in the SYSUAF. 3           Nonprivileged user access is not enabled.m  A         By default, Compaq TCP/IP Services for OpenVMS configuressF         LPD such that nonprivileged users cannot modify queue entries.  :         Creating TCPIP$AUX identifier with a value of 3655  L              Compaq TCP/IP Services for OpenVMS supports Line Printer Daemon%              Protocol (see RFC 1179).   *                LPD requires the following:*                  - Name of the local queue+                  - Name of the remote queueP*                  - Name of the remote host9                  - Spooling directory for the local queuen  P                To add or delete printers in the TCPIP PRINTCAP database, use the6                $RUN SYS$SYSTEM:TCPIP$LPRSETUP command.	         .r	         .a	         .c  >         3.3.2 Creating New TCP/IP Services Configuration Files  G               If you do not have an existing TCP/IP Services configura- G               tion in place from a previous version of the product, the H               procedure begins by creating configuration database files,6               as shown in the following sample output:  H                                          Configuring TCP/IP Services 3-5           #         Configuring TCP/IP Servicesx          3.3 Running TCPIP$CONFIG  /          TCP/IP Network Configuration Procedure   @          This procedure helps you define the parameters requiredB          to run Compaq TCP/IP Services for OpenVMS on this system.  K          Checking TCP/IP Services for OpenVMS configuration database files.   6          Creating SYS$COMMON:[SYSEXE]TCPIP$SERVICE.DAT3          Creating SYS$COMMON:[SYSEXE]TCPIP$HOST.DAT 6          Creating SYS$COMMON:[SYSEXE]TCPIP$NETWORK.DAT4          Creating SYS$COMMON:[SYSEXE]TCPIP$ROUTE.DAT4          Creating SYS$COMMON:[SYSEXE]TCPIP$PROXY.DAT<          Creating SYS$COMMON:[SYSEXE]TCPIP$CONFIGURATION.DAT  G         Compaq TCP/IP Services for OpenVMS requires a definition for at_E         least one interface.  There are no interfaces defined on thisa         system.   J         Please select the Interface option from the Core Environment Menu.  3         3.3.3 Understanding the Configuration Menus   E               After the configuration files are converted or created, 7               the Main Configuration menu is displayed:   =         Compaq TCP/IP Services for OpenVMS Configuration Menus  "             Configuration options:  )                    1  -  Core environment *                    2  -  Client components*                    3  -  Server components,                    4  -  Optional componentsD                    5  -  Shutdown Compaq TCP/IP Services for OpenVMSC                    6  -  Startup Compaq TCP/IP Services for OpenVMSV"                    7  -  Run tests  0                    A  -  Configure options 1 - 45                   [E] -  Exit configuration proceduree  #         Enter configuration option:u  )               The options are as follows:   @               1. Core environment - Software associated with theF                  Network, Internet, and Transport layers of the TCP/IP-                  architecture (Section 3.3.4)o  E               2. Client components - Application software and relatedf+                  components (Section 3.3.5)d  '         3-6 Configuring TCP/IP Servicess           H                                              Configuring TCP/IP ServicesH                                                 3.3 Running TCPIP$CONFIG  @               3. Server components - Server software and related+                  components (Section 3.3.6)   B               4. Optional components - Software that you configureC                  if you plan to allow anonymous FTP access, or suchiE                  products as PATHWORKS for OpenVMS (Advanced Server),tA                  Advanced Server for OpenVMS, DECnet over TCP/IP,hC                  or any applications that use the Stanford Research F                  Institute (SRI) QIO application programming interface                   (Section 3.3.7)  <               5. Shutdown Compaq TCP/IP Services for OpenVMS  K               6. Startup Compaq TCP/IP Services for OpenVMS (Section 3.5.1)e  (               7. Run tests (Section 3.6)  D               If you do not have experience with the TCP/IP ServicesG               product, you should use the configuration menus. However, F               if you have experience configuring the software and wantB               to bypass the menus, you can add one or more commandC               parameters when you run TCPIP$CONFIG. For informatione<               about the command parameters, see Section 3.4.  .         3.3.4 Configuring the Core Environment  H               From the Core Environment Configuration menu, enter optionA               A to configure all the core environment components.iD               Alternatively, you can configure one option at a time.B               The sample output in the following sections show theG               progression of the procedure when you choose to configuret               all components.T  F               If you select option A from the Main Configuration menu,B               the Core Environment Configuration menu is displayedE               first. You can enter option A to configure all the coreuG               environment components. You are required to configure the H               Domain, Interfaces, and Routing options; the BIND Resolver)               and Time Zone are optional.   F                 ________________________Note  ________________________  ?                 Use the Interfaces menu (option 2) to set up anV>                 interface under control of the DHCP client. If@                 you mark a DHCP client interface as primary, youC                 might not need to set up the other Core Environment:<                 components. Ask your network manager whether  H                                          Configuring TCP/IP Services 3-7 i  a      #         Configuring TCP/IP Services           3.3 Running TCPIP$CONFIG  A                 these components are configured by DHCP. For moret?                 information, see the DHCP client documentation.E  E                 _____________________________________________________   N         Compaq TCP/IP Services for OpenVMS Core Environment Configuration Menu  !            Configuration options:n                      1 - Domain !                    2 - Interfaceso                    3 - Routing$                    4 - BIND Resolver                     5 - Time Zone  /                    A  - Configure options 1 - 5P!                   [E] - Exit menu(  .         Enter configuration option: A <Return>  G               The following sections include sample output for the core B               environment components. The samples reflect a TCP/IPB               Services product configuration for a system on whichD               other TCP/IP Services configurations are in place. TheG               output varies for a new TCP/IP Services installation (see                Appendix A).  B               Enter your responses to the menu questions using theD               information from your configuration planning worksheet               (Section 1.3).  $         3.3.4.1 Domain Configuration  B               The following is a sample output for configuring the               domain:I           DOMAIN Configuration  E         Enter Internet domain [budget.acme.com]: widgets.com <Return>             '         3-8 Configuring TCP/IP Services_ _  _      H                                              Configuring TCP/IP ServicesH                                                 3.3 Running TCPIP$CONFIG  '         3.3.4.2 Interface Configuration   B               The following is a sample output for configuring the!               Internet interface:p           INTERFACE Configuration_  @                 The Ethernet device(s) on your system are: EWA0:  L                 Start of configuration questions for Internet interface WE0.0                 WE0 is the Ethernet device EWA0:           Interface: WE0M           IP_Addr: 10.10.2.2     NETWRK: 255.255.255.0    BRDCST: 10.10.2.255 A            C_Addr:             C_NETWRK:                C_BRDCST:t              Flags:s"            Receive buffer:       0  M              Compaq TCP/IP Services for OpenVMS Interface WE0 Reconfiguration_              Menu_  %              Reconfiguration options:   I                    1  -  Configure interface manually   (Current default) 5                    2  -  Let DHCP configure interfacef  E                   [E] -  Exit menu (Do not reconfigure interface WE0)e  ,         Enter configuration option: <Return>  D               In this example, no changes are made to the interface.  -         3.3.4.3 Dynamic Routing ConfigurationC  F               The following is a sample output for configuring dynamic               routing:                H                                          Configuring TCP/IP Services 3-9    /      #         Configuring TCP/IP Servicest          3.3 Running TCPIP$CONFIG  %         DYNAMIC ROUTING Configurationp  1          Dynamic routing has not been configured.t  >             You may configure dynamic ROUTED or GATED routing.A             You cannot enable both at the same time.  If you wantIA             to change from one to the other, you must disable the C             current routing first, then enable the desired routing.   H             If you enable dynamic ROUTED routing, this host will use theD             Routing Information Protocol (RIP) - Version 1 to listenA             for all dynamic routing information coming from other_8             hosts to update its internal routing tables.=             It will also supply its own Internet addresses to 4             routing requests made from remote hosts.  D             If you enable dynamic GATED routing, you will be able toG             configure this host to use any combination of the following E             routing protocols to exchange dynamic routing informationr,             with other hosts on the network:B                 Routing Information Protocol (RIP) - Version 1 & 21                 Router Discovery Protocol (RDISC)n/                 Open Shortest Path First (OSPF) /                 Exterior Gateway Protocol (EGP) /                 Border Gateway Protocol (BGP-4)o                 Static routes   U         * Do you want to configure dynamic ROUTED or GATED routing [NO]: YES <Return> J         * Do you want to enable GATED routing configuration [NO]: <Return>               ROUTED option   A             If you enable the 'supply' option of dynamic routing, @             this host will supply dynamic routing information toA             other hosts on the network whether it is acting as ani(             internetwork gateway or not.  X         * Do you want this host to supply its dynamic routing information [NO]: <Return>              (         3-10 Configuring TCP/IP Services l  y      H                                              Configuring TCP/IP ServicesH                                                 3.3 Running TCPIP$CONFIG  +         3.3.4.4 BIND Resolver Configuratione  G               The following is a sample output for configuring the BINDs               resolver:p  4         A BIND resolver has already been configured.  #         BIND Resolver Configurationi             Transport:  UDP %           Domain:     budget.acme.comc           Retry:         4           Timeout:       4,           Servers:    island.budget.acme.com'           Path:       No values defined   8         * Do you want to reconfigure BIND [NO]: <Return>  >               In this example, no changes are made to the BIND               resolver.p  '         3.3.4.5 Time Zone Configuration   G               The following is a sample output for configuring the time                zone:n           TIME ZONE Configuration   K           TCPIP uses timezone information provided by the OpenVMS Operating J           System. No additional timezone configuration is needed for TCPIP<           when the operating system is configured correctly.  K           This section verifies the current OpenVMS timezone configuration. N           A warning message (TCPIP-W-) indicates that corrective action shouldK           be taken. TCPIP will appear to operate but components may displayeO           either the wrong time or a time inconsistent with other applications.   <         %TCPIP-I-INFO, Logical name SYS$TIMEZONE_RULE found.M         -TCPIP-I-INFO, Software for automatic Summer/Winter time (TDF) changeo"         -TCPIP-I-INFO, is present.L         -TCPIP-I-INFO, Further action to ensure TDF change is not necessary.  6         %TCPIP-I-NORMAL, timezone information verified  $         Press Return to continue ...  H                                         Configuring TCP/IP Services 3-11 C  $      #         Configuring TCP/IP Serviceso          3.3 Running TCPIP$CONFIG  0         3.3.5 Configuring the Client Environment  E               After the core environment is configured, the procedure E               returns to the Core Environment menu. Enter option E toSF               exit. If you selected option A in the Main Configuration?               menu, the Client Components Configuration menu is                displayed next.n  O         Compaq TCP/IP Services for OpenVMS Client Components Configuration MenuS           Configuration options:  6                 1  - FTP              Enabled  Stopped6                 2  - NFS Client       Enabled  Stopped6                 3  - REXEC and RSH    Enabled  Stopped6                 4  - RLOGIN           Enabled  Stopped6                 5  - SMTP             Enabled  Stopped6                 6  - TELNET           Enabled  Stopped6                 7  - DHCP             Disabled Stopped6                 8  - Telnetsym        Disabled Stopped  ,                 A  - Configure options 1 - 8                [E] - Exit menu  B               Note that the sample Client Components Configuration@               menu shows most components enabled and all of them?               stopped. Components are enabled if they have been C               enabled in the TCP/IP Services configuration database A               (TCPIP$CONFIGURATION.DAT). The enabled services are C               started the next time TCP/IP Services is started. YouVD               can also start (or stop) a specific component, withoutH               having to restart TCP/IP Services, by selecting the "StartG               service" option from that component's configuration menu.vE               In addition, you can use command procedures to start orCE               stop a specific component, as explained in Section 3.9.y  E               The initial status of the components depends on whethereC               you have other TCP/IP Services installations in placehC               on the system, and whether the software or individualtD               components have been started. On a new system, all theD               components would be disabled (the default). The statusG               of components is also affected by the selections you made -               from the Core Environment menu.h    (         3-12 Configuring TCP/IP Services h  m      H                                              Configuring TCP/IP ServicesH                                                 3.3 Running TCPIP$CONFIG  E               To minimize resource consumption, enable and start only F               those components that you are sure to use. Disable those%               you do not plan to use.F  @               You can enter option A to configure all the client               components.   G               The following is an example of the output for configuringKG               an FTP client. The configuration output for other clients F               might vary. Note that after you configure a client (suchF               as FTP) that has an associated server, the configurationF               prompts you about whether to configure the corresponding               server.   .         Enter configuration option: 1 <Return>            FTP CLIENT Configuration  ,         Service is enabled on specific node.         Service is stopped.   2                  FTP CLIENT configuration options:  9                          1 - Disable service on this nodeu  7                          2 - Start service on this nodef  ;                         [E] - Exit FTP_CLIENT configurationa  .         Enter configuration option: 1 <Return>  "         The FTP SERVER is enabled.  A         * Do you want to configure the FTP SERVER [NO] ? <Return>r  E               In the preceding example, the FTP client was originally C               enabled, and you selected option 1 to disable it. TheeC               following example shows the configuration output thatuH               might be seen if you want to enable an FTP client that had               been disabled.          H                                         Configuring TCP/IP Services 3-13 .         #         Configuring TCP/IP ServicesF          3.3 Running TCPIP$CONFIG            FTP CLIENT Configuration           Service is not enabled.l         Service is stopped.f  1                 FTP CLIENT configuration options:   8                          1 - Enable service on this node  @                          2 - Enable & Start service on this node  ;                         [E] - Exit FTP_CLIENT configuration   .         Enter configuration option: 2 <Return>  C               In this example, as with the previous one, the TCP/IP E               Services software has already been started, so you have G               the choice of starting the client as well as enabling it.eE               If you select option 1, the FTP service will be enabled E               and FTP will start the next time the TCP/IP Services isYF               started. If you select option 2, the FTP service will beG               started immediately and then every time the TCP/IP kernel                is started.[  B               If the TCP/IP Services software had not already beenH               started, then the FTP Client Components Configuration menuG               would only give you the option of enabling the component,e*               as in the following example:  7                         1 - Enable service on this nodet  :                        [E] - Exit FTP_CLIENT configuration  0         3.3.6 Configuring the Server Environment  H               If you selected option A from the Main Configuration menu,H               the Server Components menu is displayed after you exit the3               Client Components Configuration menu.               (         3-14 Configuring TCP/IP Services    p      H                                              Configuring TCP/IP ServicesH                                                 3.3 Running TCPIP$CONFIG  O         Compaq TCP/IP Services for OpenVMS Server Components Configuration Menu            Configuration options:  O           1 - BIND        Disabled Stopped    11 - NTP         Enabled  Stopped O           2 - BOOTP       Disabled Stopped    12 - PC-NFS      Enabled  Stopped O           3 - DHCP        Disabled Stopped    13 - POP         Enabled  StoppedcO           4 - FINGER      Enabled  Stopped    14 - PORTMAPPER  Enabled  StoppedCO           5 - FTP         Enabled  Stopped    15 - RLOGIN      Enabled  StoppedoO           6 - LBROKER     Enabled  Stopped    16 - RMT         Enabled  StoppednO           7 - LPR/LPD     Enabled  Stopped    17 - SNMP        Enabled  Stopped O           8 - METRIC      Enabled  Stopped    18 - TELNET      Enabled  Stopped O           9 - NFS         Enabled  Stopped    19 - TFTP        Enabled  StoppedpO          10 - LOCKD/STATD Disabled Stopped    20 - XDM         Disabled Stopped   (           A  -  Configure options 1 - 20          [E] -  Exit menu   #         Enter configuration option:n  C               Components are enabled if they have been added to therO               TCP/IP Services configuration database (TCPIP$CONFIGURATION.DAT),t@               and they are started the next time TCP/IP ServicesA               is started. You can also start (or stop) a specificnF               component, without having to restart TCP/IP Services, byH               selecting the "Start service" option from that component'sB               configuration menu. In addition, you can use commandB               procedures to start or stop a specific component, as'               explained in Section 3.9.   E               The initial status of the components depends on whether C               you have other TCP/IP Services installations in place C               on the system, and whether the software or individual @               components have been started. To minimize resource?               consumption, enable and start the specific server F               components you plan to use, and disable those you do notF               plan to use. You can enter option A to configure all the                server components.  ?               For server components that have associated client F               components (such as the FTP server and client), when youH               configure the server component, you will be prompted aboutD               whether you want to configure the corresponding client               component.  H                                         Configuring TCP/IP Services 3-15 l  d      #         Configuring TCP/IP Services           3.3 Running TCPIP$CONFIG  H               The following is an example of an XDM server configurationA               output. The configuration displays for other server $               components might vary.  /         Enter configuration option: 20 <Return>e           XDM Configuration   )         Service is defined in the SYSUAF.o=         Service is not defined in the TCPIP$SERVICE database.t         Service is not enabled.          Service is stopped.r  #          XDM configuration options:i  *            1 - Enable service on this node  &           [E] - Exit XDM configuration  #         Enter configuration option:   F                 ________________________Note  ________________________  C                 XDM requires the following DECwindows components toG                 be installed:n  6                 o  SYS$COMMON:[SYSLIB]DECW$XLIBSHR.EXE  9                 o  SYS$COMMON:[SYSLIB]DECW$XTLIBSHRR5.EXE   D                 o  SYS$COMMON:[SYSLIB]DECW$TRANSPORT_COMMON.EXE (VAX                    only)  <                 The TCPIP$CONFIG procedure checks that these@                 components are installed. If they are not found,B                 TCPIP$CONFIG notifies you and gives you the optionA                 of configuring XDM, assuming you will install the =                 DECwindows components later before attempting @                 to activate XDM. The notification and prompt are%                 displayed as follows:c  J                 XDM requires DECwindows components that are not installed.3                 Attempts to activate XDM will fail.t  N                 Type C to continue with XDM configuration, or E to exit [ E ]:  E                 _____________________________________________________r  (         3-16 Configuring TCP/IP Services x  .      H                                              Configuring TCP/IP ServicesH                                                 3.3 Running TCPIP$CONFIG  H               After you configure the server components, press Return toF               go to the Main Configuration menu. If you entered optionG               A in the Main Configuration menu, the Optional Componentse3               Configuration menu is displayed next.   1         3.3.7 Configuring the Optional Components   F               You may need to configure optional product components if:               you plan to do one or more of the following:  E               o  Run the PATHWORKS for OpenVMS (Advanced Server), the D                  Advanced Server for OpenVMS, or DECnet over TCP/IP.  B               o  Run or develop applications that use the StanfordG                  Research Institute's (SRI) QIO application programming !                  interface (API).r  ,               o  Allow anonymous FTP access.  B               To configure the optional components, enter option 4G               from the Main Configuration menu. The Optional ComponentsdE               Configuration menu displays the following menu options:s  L         Compaq TCP/IP Services for OpenVMS Optional Components Configuration         Menu           Configuration options:  I                 1 - Configure PWIP Driver (for DECnet-Plus and PATHWORKS) =                 2 - Configure SRI QIO Interface (INET Driver) @                 3 - Set up Anonymous FTP Account and Directories  +                 A - Configure options 1 - 3W                [E] - Exit menu  #         Enter configuration option:n  E               Enter the options that are appropriate for your system:yF               the PWIP Driver, the SRI QIO Interface, or Anonymous FTP'               Accounts and Directories.   C               o  If you want to run PATHWORKS for OpenVMS (AdvancedCE                  Server), Advanced Server for OpenVMS, or DECnet overPH                  TCP/IP, configure the PWIP driver by entering option 1.H                  In addition, refer to the appropriate documentation for%                  the layered product.D  H               o  If you run or develop applications that use the SRI QIO%                  API, enter option 2.o  H                                         Configuring TCP/IP Services 3-17    b      #         Configuring TCP/IP Servicesy          3.3 Running TCPIP$CONFIG  H               o  If you want to allow anonymous FTP access, enter optionF                  3 to set up an anonymous FTP account and directories.D                  Make sure you obtain the necessary user informationH                  code (UIC) (see Section 1.2.8) and determine guest user                  privileges.  F               The following shows the output when configuring the PWIP               driver:   .         Enter configuration option: 1 <Return>  F         TCPIP Transport for DECnet and Pathworks Service Configuration  ,         Service is enabled on specific node.         Service is stopped.t  P          TCPIP Transport for DECnet and Pathworks Service configuration options:  ,             1 - Disable service on this node  /            [E] - Exit PWIP_DRIVER configurationP  #         Enter configuration option:G  E         3.4 Using TCPIP$CONFIG Option Commands to Bypass TCPIP$CONFIGy             Menuse  A               If you are an experienced TCP/IP Services user, youuE               may want to bypass the configuration menus to enable or 0               disable functionality, as follows:  .               1. Log in to the SYSTEM account.  C               2. Run the TCPIP$CONFIG command procedure and include F                  appropriate options and keywords in the command line,                  as shown:  P                  @SYS$MANAGER:TCPIP$CONFIG [option] {DISABLE | ENABLE} [CLUSTER]  H                  where option can be one of the options described in theG                  following table. The table also describes the function >                  of the DISABLE, ENABLE, and CLUSTER keywords.      (         3-18 Configuring TCP/IP Services           H                                              Configuring TCP/IP ServicesH      3.4 Using TCPIP$CONFIG Option Commands to Bypass TCPIP$CONFIG Menus  H                  _______________________________________________________H                  Option________Description______________________________  F                  ALL           Configures the core environment and all<                                client and server components.  C                  CLIENT        Configures all client components and 0                                related software.  >                  MINIMUM       Configures the domain, InternetH                                interfaces, remote login, FTP client, FTPH                                server, TELNET client, and TELNET server.C                                Prompts you for optional components.o  C                  SERVER        Configures all server components anda0                                related software.  H                  WORKSTATION   Configures the BIND resolver, the domain,D                                dynamic routing, Internet interfaces,E                                time zone, remote login, remote shell,iH                                remote executive, FTP client, FTP server,F                                TELNET client, TELNET server, and SMTP.H                  _______________________________________________________H                  Keyword_______Description______________________________  B                  CLUSTER       Configures all specified componentsF                                clusterwide (except for the BIND serverC                                and SMTP, which you cannot configureP,                                clusterwide).  @                  ENABLE        Enables the specified components.  H                  DISABLE_______Disables_the_specified_components._______  F                  For example, the following command enables the client3                  components for the entire cluster:t  B                  $ @SYS$MANAGER:TCPIP$CONFIG CLIENT ENABLE CLUSTER  F                 ________________________Note  ________________________  ?                 The procedure implements two levels of enablingnB                 and disabling: clusterwide and single node (exceptA                 for SMTP, which is configured and enabled as node-                 specific only).d  E                 _____________________________________________________   H                                         Configuring TCP/IP Services 3-19 n  e      #         Configuring TCP/IP Services 4         3.5 Making Configuration Changes Take Effect  4         3.5 Making Configuration Changes Take Effect  F               Whenever you configure the core TCP/IP Services softwareF               (the core environment), you must then start (or restart)A               TCP/IP Services to make the changes take effect. DonE               this before you run tests or customize the environment.eF               Start TCP/IP Services from TCPIP$CONFIG by following the3               procedure described in Section 3.5.1.N  D               If you made changes to the client, server, or optionalE               components only (that is, not to the core environment),aA               you do not have to restart TCP/IP Services: you canPB               restart the affected components individually to ini-C               tialize the changes, by selecting the "Start service"yD               option in the affected component's configuration menu.A               Alternatively, you can use each component's startupn=               command procedure, as described in Section 3.9.   ?               You can have the TCP/IP Services software started E               automatically each time the OpenVMS operating system is D               rebooted, or you can restart the software manually, as'               explained in Section 3.8.l  9         3.5.1 Starting TCP/IP Services Using TCPIP$CONFIGb  B               After configuring the core environment, start TCP/IPD               Services on your system by selecting option 6 (Startup?               Compaq TCP/IP Services for OpenVMS) from the Mainc>               Configuration menu, as in the following example:  =         Compaq TCP/IP Services for OpenVMS Configuration Menun  "             Configuration options:  )                    1  -  Core environmentb*                    2  -  Client components*                    3  -  Server components,                    4  -  Optional componentsD                    5  -  Shutdown Compaq TCP/IP Services for OpenVMSC                    6  -  Startup Compaq TCP/IP Services for OpenVMSu"                    7  -  Run tests  0                    A  -  Configure options 1 - 45                   [E] -  Exit configuration proceduree  (         3-20 Configuring TCP/IP Services    u      H                                              Configuring TCP/IP ServicesH                             3.5 Making Configuration Changes Take Effect  %         Enter configuration option: 6d         Begin Startup...  R         %TCPIP-I-INFO, TCP/IP Services startup beginning at 5-DEC-2000 15:27:08.346         %TCPIP-I-NORMAL, timezone information verifiedE         %RUN-S-PROC_ID, identification of created process is 00000D42 ;         %TCPIP-I-SETLOCAL, setting domain and/or local hosto2         %TCPIP-I-STARTCOMM, starting communication6         %TCPIP-I-SETPROTP, setting protocol parameters-         %TCPIP-I-DEFINTE, defining interfacese1         %TCPIP-I-STARTNAME, starting name service ;         %TCPIP-S-STARTDONE, TCP/IP Kernel startup completedhA         %TCPIP-I-LOADSERV, loading TCPIP server proxy informationtI         %TCPIP-I-SERVLOADED, auxiliary server loaded with 0 proxy recordsh@         -TCPIP-I-SERVSKIP, skipped 0 communication proxy records9         -TCPIP-I-SERVTOTAL, total of 6 proxy records read 9         %TCPIP-S-STARTDONE, TCPIP$PROXY startup completedn>         %TCPIP-S-STARTDONE, TCPIP$PORTMAPPER startup completed:         %TCPIP-S-STARTDONE, TCPIP$FINGER startup completed7         %TCPIP-S-STARTDONE, TCPIP$FTP startup completed >         %TCPIP-S-STARTDONE, TCPIP$FTP_CLIENT startup completed;         %TCPIP-S-STARTDONE, TCPIP$LBROKER startup completed 9         %TCPIP-S-STARTDONE, TCPIP$LOCKD startup completed 7         %TCPIP-S-STARTDONE, TCPIP$LPD startup completed >         %TCPIP-S-STARTDONE, TCPIP$LPD_CLIENT startup completed:         %TCPIP-S-STARTDONE, TCPIP$METRIC startup completed7         %TCPIP-S-STARTDONE, TCPIP$NFS startup completed >         %TCPIP-S-STARTDONE, TCPIP$NFS_CLIENT startup completed7         %TCPIP-S-STARTDONE, TCPIP$NTP startup completedi9         %TCPIP-S-STARTDONE, TCPIP$PCNFS startup completed 7         %TCPIP-S-STARTDONE, TCPIP$POP startup completedeE         %RUN-S-PROC_ID, identification of created process is 00000C4Ee?         %TCPIP-S-STARTDONE, TCPIP$PWIP_DRIVER startup completedv9         %TCPIP-S-STARTDONE, TCPIP$REXEC startup completedt:         %TCPIP-S-STARTDONE, TCPIP$RLOGIN startup completed7         %TCPIP-S-STARTDONE, TCPIP$RMT startup completede7         %TCPIP-S-STARTDONE, TCPIP$RSH startup completed 8         %TCPIP-S-STARTDONE, TCPIP$SMTP startup completed8         %TCPIP-S-STARTDONE, TCPIP$SNMP startup completed9         %TCPIP-S-STARTDONE, TCPIP$STATD startup completed :         %TCPIP-S-STARTDONE, TCPIP$TELNET startup completed=         %TCPIP-S-STARTDONE, TCPIP$TELNETSYM startup completede8         %TCPIP-S-STARTDONE, TCPIP$TFTP startup completed    H                                         Configuring TCP/IP Services 3-21           #         Configuring TCP/IP Servicesn4         3.5 Making Configuration Changes Take Effect  7         %TCPIP-S-STARTDONE, TCPIP$XDM startup completedpW         %TCPIP-S-STARTDONE, TCP/IP Services startup completed at 5-DEC-2000 15:27:50.47t"         Startup request completed.$         Press Return to continue ...    '         3.6 Verifying the Configuration   G               You can verify the configuration by running the installa-H0               tion verification procedure (IVP).  <               You should run the IVP if the following apply:  H               o  You loaded the Product Authorization Key (PAK), and youE                  want to verify that the lower-layer software and thee<                  Portmapper service are installed correctly.  F               o  You did not load the PAK, but you want to verify thatF                  TCP/IP Services is installed correctly for DECwindows=                  to display the TCP/IP Services applications.   C               o  You require the software to transfer device socket0H                  packets that continuously vary in size between a sender                   and a receiver.  D               o  You need to test the Portmapper service with a pairG                  of client/server programs. The IVP reports the time itg4                  took to run the test to SYS$OUTPUT.  4               o  You need to test your SNMP service.  C               Before you run the IVP, make sure TCP/IP Services has C               started and you have SYSPRV, OPER, NETMBX, and TMPMBX                privileges.   E               You can run the IVP from the TCPIP$CONFIG configuration E               procedure or by command line at the OpenVMS DCL prompt.rB               When you run the IVP from TCPIP$CONFIG, you have theD               option of running an additional test that verifies the!               SNMP configuration.e          (         3-22 Configuring TCP/IP Services           H                                              Configuring TCP/IP ServicesH                                          3.6 Verifying the Configuration  E         3.6.1 Running the IVP from the TCPIP$CONFIG Command Procedureu  C               In the TCP/IP Services for OpenVMS Main ConfigurationtG               menu, select option 7 (Run tests). The Test menu appears, *               as in the following example:  4         Compaq TCP/IP Services for OpenVMS TEST Menu                   Test options:   +                          1  -  Internet IVPo'                          2  -  SNMP IVPh  *                          A  -  Tests 1 - 2(                         [E] -  Exit menu           Enter test option:  D               Select the appropriate option for the test you want to               perform.  9         3.6.2 Running the IVP from the OpenVMS DCL Prompta  F               To run the IVP at the DCL prompt, any time after exitingG               the configuration procedure, enter the following command. F               This procedure performs the same test as option 1 of the4               TCPIP$CONFIG Test menu (Internet IVP).  #               $ @SYS$TEST:TCPIP$IVP   B         3.6.3 Verifying the TCP/IP Services Internet Configuration  F               When you select option 1 or A from the TCPIP$CONFIG TestA               menu, or run the TCPIP$IVP command procedure at theaC               command line, the IVP tests the basic TCP/IP Services_E               for OpenVMS software configuration, as in the following =               example. Here, the test completes successfully.   %         Enter test option: 1 <Return>S  "         %%% TCPIP IVP: started %%%  6         UDP/IP test started at 31-MAR-2000 16:13:03.024         UDP/IP test ended at 31-MAR-2000 16:13:03.69B         UDP/IP transferred successfully in 0 seconds 4198400 bytes  6         TCP/IP test started at 31-MAR-2000 16:13:04.204         TCP/IP test ended at 31-MAR-2000 16:13:41.21C         TCP/IP transferred successfully in 37 seconds 4198400 bytes   H                                         Configuring TCP/IP Services 3-23 w  o      #         Configuring TCP/IP Services '         3.6 Verifying the Configurationt  6         RAW_IP test started at 31-MAR-2000 16:13:41.714         RAW_IP test ended at 31-MAR-2000 16:13:41.79A         RAW_IP transferred successfully in 0 seconds 251000 bytesw  1         %%% TCPIP IVP: completed successfully %%%          IVP request completed.$         Press Return to continue ...  F               If the IVP does not complete successfully, the procedureB               displays error messages. All IVP errors use the same=               format as OpenVMS system messages. For example:   3               %TCPIP-E-IDENT, explanation of error.   G               Table 3-2 lists some common problems that cause IVP error F               messages. If the recommended action does not correct theB               problem, contact your Compaq support representative.  H               Table_3-2_Troubleshooting_IVP_Errors______________________  H               Problem_________________Corrective_Action_________________  C               Network configuration   Shut down TCP/IP Services and H               is incorrect.           rerun the configuration procedure.  H               Startup fails.          Check the system parameters in theH                                       MODPARAMS.DAT file and adjust themH                                       if necessary. (See Section 1.2.7.)  B                                       Shut down and restart TCP/IP/                                       Services.o  @               Installation kit is     Request a replacement kit.               defective.  G               IVP fails because the   Register a Compaq TCP/IP ServicesuH               PAK_is_missing._________for_OpenVMS_PAK.__________________  .         3.6.4 Verifying the SNMP Configuration  D               If you select option 2 or A from the TCPIP$CONFIG TestG               menu, the IVP tests the SNMP service, as in the followingE               example:    (         3-24 Configuring TCP/IP Services i         H                                              Configuring TCP/IP ServicesH                                          3.6 Verifying the Configuration           Begin SNMP IVP...   @         The SNMP IVP requires that TCPIP/IP Services be running.?         It performs the following startups and shutdowns on the C         SNMP service only (other TCP/IP services are not affected):   J         - If SNMP is running, shuts down SNMP before initial configuration$         - Starts SNMP and runs tests<         - Shuts down SNMP and restores initial configuration%         - Before exiting, starts SNMP   /         Shutting down the SNMP service... done.   =         Creating temporary read/write community SNMPIVP_6520.             Enabling SET operations.  -         Starting up the SNMP service... done.   /               Saving sysContact: Ralph Nicklebyr.           Setting sysContact to: Julius Caesar.            Retrieved sysContact: Julius Caesar,         (Retrieved value matches SET value.)/         Restoring sysContact to: Ralph Nicklebyi  5             Saving snmpEnableAuthenTraps: 1 (enabled)e6         Setting snmpEnableAuthenTraps to: 2 (disabled)6          Retrieved snmpEnableAuthenTraps: 2 (disabled),         (Retrieved value matches SET value.)5          Restoring snmpEnableAuthenTraps: 1 (enabled)   !         Disabling SET operations.t  =         Deleting temporary read/write community SNMPIVP_6520.P  8         Shutting down and restarting the SNMP service.../         Shutting down the SNMP service... done.   -         Starting up the SNMP service... done.k  #         SNMP IVP request completed. $         Press Return to continue ...  H               If one of the SNMP tests fails, you will see messages such               as the following:   H                                         Configuring TCP/IP Services 3-25           #         Configuring TCP/IP ServicesP'         3.6 Verifying the Configurationa  =         SNMPIVP: unexpected text in response to SNMP request:          "No reply.",J         See file SYS$SYSDEVICE:[TCPIP$SNMP]TCPIP$SNMP_REQUEST.DAT for more         details..         Verify that SNMP trace is not enabled.5         sysContact could not be retrieved. Status = 0a4         The SNMP IVP has NOT completed successfully.  A               In this case, the error could indicate that not all C               SNMP components have started, or that SNMP tracing istE               enabled and needs to be disabled. For information abouttD               SNMP trace, see the Compaq TCP/IP Services for OpenVMS               Management guide.P  *         3.7 Additional Configuration Tasks  E               After you run TCPIP$CONFIG and enable the functionalityPC               and components appropriate for your network, you need B               to complete additional configuration tasks to enableH               access to product applications. TCP/IP Services provides aH               management command interface and logical names you can useG               to modify or customize the software for your environment.   9               The additional configuration tasks include:   F               o  Populating databases (for example, for BIND and DHCP)  )               o  Setting up user accounts   9               o  Setting up communication and NFS proxies   &               o  Defining print queues  D               o  Setting up, exporting, and maintaining file systems  :               o  Tuning the system for optimum performance  F               Many of the services require additional configuration orE               optimization. For more information about the additionalsE               configuration tasks and how each service can be furthereA               configured, refer to the Compaq TCP/IP Services forl'               OpenVMS Management guide.       (         3-26 Configuring TCP/IP Services ,         H                                              Configuring TCP/IP ServicesH                                3.8 Starting and Stopping TCP/IP Services  1         3.8 Starting and Stopping TCP/IP Services_  G               You can use commands in your OpenVMS startup file to havenD               TCP/IP Services started and stopped automatically whenF               the OpenVMS system starts up or shuts down, as explainedE               in Section 3.8.1. These commands start and stop all theAB               TCP/IP Services components installed on your system.E               Alternatively, you can start and stop individual TCP/IP D               Services client or server components without affectingE               the other TCP/IP Services components currently running.ED               For information about starting and stopping individual*               components, see Section 3.9.  B               If necessary, you can start and stop TCP/IP Services6               manually, as explained in Section 3.8.2.  A         3.8.1 Automatically Starting and Stopping TCP/IP Servicesn  A               To allow TCP/IP Services software to start automat-_>               ically when the system starts up and to stop au->               tomatically when the system shuts down, edit theC               SYS$COMMON:[SYSMGR]SYSTARTUP_VMS.COM file and includeu$               the following command:  (               @SYS$STARTUP:TCPIP$STARTUP  E               If your system had earlier versions of TCP/IP Services,eA               UCX$STARTUP.COM and UCX$SHUTDOWN.COM files might betA               present. These are no longer applicable; delete any.D               definition of them from SYS$MANAGER:SYSTARTUP_VMS.COM.  C               For TCP/IP Services to start after you log in to youriE               OpenVMS account, the OpenVMS systemwide login procedure F               (typically SYS$MANAGER:SYLOGIN.COM) must have world read-               and execute protections (W:RE).n  E               To display the current protections, enter the followingo               command:  6               $ DIR/PROTECTION SYS$MANAGER:SYLOGIN.COM  A               The protections are displayed for four groups, each C               separated by a comma, such as (RWED,RWED,WRE,RE). The F               protections for the World group are the last ones in theF               series (in this example, RE). If the protections are not               RE, enter:  H                                         Configuring TCP/IP Services 3-27 t         #         Configuring TCP/IP Servicesc1         3.8 Starting and Stopping TCP/IP Services   =               $ SET PROTECTION=(W:RE) SYS$MANAGER:SYLOGIN.COMc  <         3.8.2 Starting and Stopping TCP/IP Services Manually  D               To start TCP/IP Services manually, enter the following               command:  *               $ @SYS$STARTUP:TCPIP$STARTUP  C               To stop TCP/IP Services manually, enter the followingl               command:  +               $ @SYS$STARTUP:TCPIP$SHUTDOWNi  5         3.9 Starting and Stopping Individual Services   B               On a system already running TCP/IP Services, you canH               configure an individual server or client component withoutG               affecting the other TCP/IP Services components running on H               your system and without having to restart TCP/IP Services.  G               Most services can be shut down and started independently.AH               This is useful when you change parameters or logical names7               that require the service to be restarted.   /               The following files are provided:   D               o  SYS$STARTUP:TCPIP$service_STARTUP.COM allows you to+                  start the service service.   E               o  SYS$STARTUP:TCPIP$service_SHUTDOWN.COM allows you toP/                  shut down the service service.E  >               To preserve site-specific parameter settings andC               commands, create the following files. These files aresA               not overwritten when you reinstall TCP/IP Services:h  D               o  SYS$STARTUP:TCPIP$service_SYSTARTUP.COM can be usedB                  as a repository for site-specific definitions andB                  parameters to be invoked when service is started.  E               o  SYS$STARTUP:TCPIP$service_SYSHUTDOWN.COM can be used B                  as a repository for site-specific definitions andD                  parameters to be invoked when service is shut down.  E               In these file names, service is the name of the service E               to be started or shut down. For example, use TCPIP$NTP_A4               SHUTDOWN to shut down the NTP service.  (         3-28 Configuring TCP/IP Services d         H                                              Configuring TCP/IP ServicesG                           3.9 Starting and Stopping Individual Services_  F               For more information, see the Compaq TCP/IP Services for'               OpenVMS Management guide.   G         3.10 Specifying TCP/IP Services as the Transport for DECwindowsu              ApplicationsP  B               To enable TCP/IP Services as the transport interfaceD               for DECwindows applications, add the following line toC               the SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM commandE               procedure:  >               $ DECW$SERVER_TRANSPORTS == "DECNET,LOCAL,TCPIP"  &               Then restart DECwindows:  1               $ @SYS$STARTUP:DECW$STARTUP RESTARTo  C               If DECnet or DECnet-Plus software runs on the system,0               start it.S  B               To display DECwindows applications from a DECwindows?               client (remote host) to a DECwindows server (yourE/               workstation), proceed as follows:S  4               1. Set up security on the remote host.  C               2. Add the remote client to the local hosts database.   E               3. Add to SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM thet                   following line:  A                  $ DECW$SERVER_TRANSPORTS == "DECNET,LOCAL,TCPIP"C  C               4. Set the display for the applications to the remoteY                  host:  F                  $ SET DISPLAY/CREATE/NODE=remote-host/TRANSPORT=TCPIP                H                                         Configuring TCP/IP Services 3-29    /                  H                                                                        AH         ________________________________________________________________  H                Sample New TCP/IP Services Installation and Configuration      F               This appendix shows a sample installation and configura-F               tion of the TCP/IP Services product on a system on which3               the product has never been installed.   -         A.1 Sample New Installation Proceduret  F               The following example shows a sample installation dialogH               for the TCP/IP Services. In this example, the installation?               takes place on a system where the product has notcC               been installed. If TCP/IP Services had been installedAE               previously on the system, the installation dialog wouldt.               differ slightly (see Chapter 2).  E         Choose one or more items from the menu separated by commas: 1q  0         The following product has been selected:A             DEC VAXVMS TCPIP V5.1-0               Layered Product   /         Do you want to continue? [YES] <Return>   (         Configuration phase starting ...  V         You will be asked to choose options, if any, for each selected product and forW         any products that may be installed to satisfy software dependency requirements.S  D         DEC VAXVMS TCPIP V5.1-0: Compaq TCP/IP Services for OpenVMS.  F             (c) Compaq Computer Corporation 2000. All Rights Reserved.  '             Compaq Computer Corporation   N             Compaq TCP/IP Services for OpenVMS offers several license options.  @         Do you want the defaults for all options? [YES] <Return>  8         Do you want to review the options? [NO] <Return>  $         Execution phase starting ...  H            Sample New TCP/IP Services Installation and Configuration A-1    -      A         Sample New TCP/IP Services Installation and Configuration -         A.1 Sample New Installation Procedure   ?         The following product will be installed to destination:iO             DEC VAXVMS TCPIP V5.1-0               DISK$OVMSVAXSYS:[VMS$COMMON.]   N         Portion done: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%=         %PCSI-I-PRCOUTPUT, output from subprocess follows ...          % TCPIP-W-PCSI_INSTALLQ         % - Execute SYS$MANAGER:TCPIP$CONFIG.COM to proceed with configuration ofe#         %   Compaq TCP/IP Services. 	         %t           Portion done: 100%  1         The following product has been installed: A             DEC VAXVMS TCPIP V5.1-0               Layered Product   D         DEC VAXVMS TCPIP T5.1-0: Compaq TCP/IP Services for OpenVMS.  F             Check the release notes for current status of the product.  .         A.2 Sample New Configuration Procedure  G               The following example shows a sample configuration dialogoH               for the TCP/IP Services, in which the following components               are configured:   !               o  Core environmentI                 o  TELNET client                 o  FTP serverC  H               In this example, the configuration takes place on a systemD               where the product has never been configured. If TCP/IPH               Services had been configured previously on the system, the@               dialog would differ significantly (see Chapter 3).  0           TCP/IP Network Configuration Procedure  ?         This procedure helps you define the parameters requiredpA         to run Compaq TCP/IP Services for OpenVMS on this system.   J         Checking TCP/IP Services for OpenVMS configuration database files.      E         A-2 Sample New TCP/IP Services Installation and ConfigurationD P  a      H                Sample New TCP/IP Services Installation and ConfigurationH                                   A.2 Sample New Configuration Procedure  5         Creating SYS$COMMON:[SYSEXE]TCPIP$SERVICE.DATo2         Creating SYS$COMMON:[SYSEXE]TCPIP$HOST.DAT5         Creating SYS$COMMON:[SYSEXE]TCPIP$NETWORK.DAT 3         Creating SYS$COMMON:[SYSEXE]TCPIP$ROUTE.DATe3         Creating SYS$COMMON:[SYSEXE]TCPIP$PROXY.DATr;         Creating SYS$COMMON:[SYSEXE]TCPIP$CONFIGURATION.DAT3  G         Compaq TCP/IP Services for OpenVMS requires a definition for atsE         least one interface.  There are no interfaces defined on this          system.   J         Please select the Interface option from the Core Environment Menu.  =         Compaq TCP/IP Services for OpenVMS Configuration Menua           Configuration options:  '                  1  -  Core environmentM(                  2  -  Client components(                  3  -  Server components*                  4  -  Optional components  B                  5  -  Shutdown Compaq TCP/IP Services for OpenVMSA                  6  -  Startup Compaq TCP/IP Services for OpenVMSa                   7  -  Run tests  .                  A  -  Configure options 1 - 43                 [E] -  Exit configuration proceduree  .         Enter configuration option: 1 <Return>  O          Compaq TCP/IP Services for OpenVMS Core Environment Configuration Menu             Configuration options:                     1  -  Domain !                  2  -  Interfaces                   3  -  Routing$                  4  -  BIND Resolver                   5  -  Time Zone  .                  A  -  Configure options 1 - 5                  [E] -  Exit menu  .         Enter configuration option: A <Return>           DOMAIN Configuration  .         Enter Internet domain: budget.acme.com  H            Sample New TCP/IP Services Installation and Configuration A-3           A         Sample New TCP/IP Services Installation and Configuration .         A.2 Sample New Configuration Procedure           INTERFACE Configuration.  N           The Ethernet device(s) on your system are: ESA0:  * Not Configured *  F           Start of configuration questions for Internet interface SE0.  *           SE0 is the Ethernet device ESA0:  %           SE0 has not been configurede  M           Compaq TCP/IP Services for OpenVMS Interface SE0 Configuration MenuP  "             Configuration options:  3                  1  -  Configure interface manually 3                  2  -  Let DHCP configure interfacee  A                 [E] -  Exit menu (Do not configure interface SE0)n  .         Enter configuration option: 1 <Return>4         Enter unqualified host name: HEARTS <Return><         Enter Internet address for hearts: 10.0.2.4 <Return>N         Enter Internet network mask for hearts [255.0.1.0]: 255.1.12.1<Return>>         Enter broadcast mask for hearts [10.0.2.255]: <Return>  ?             The following parameters will be used to define the #             Internet interface SE0:o  7               Host name:         hearts.budget.acme.com )               Internet address:  10.0.2.4o+               Network mask:      255.1.12.1h+               Broadcast mask:    10.0.2.255J  /          * Is the above correct [YES]: <Return>u  E             End of configuration questions for Internet interface SE0   %         DYNAMIC ROUTING Configuration   5              Dynamic routing has not been configured.e  ?              You may configure dynamic ROUTED or GATED routing.mB              You cannot enable both at the same time.  If you wantB              to change from one to the other, you must disable theD              current routing first, then enable the desired routing.  E         A-4 Sample New TCP/IP Services Installation and Configurationt S         H                Sample New TCP/IP Services Installation and ConfigurationH                                   A.2 Sample New Configuration Procedure  I              If you enable dynamic ROUTED routing, this host will use thefE              Routing Information Protocol (RIP) - Version 1 to listen B              for all dynamic routing information coming from other9              hosts to update its internal routing tables. >              It will also supply its own Internet addresses to5              routing requests made from remote hosts.l  E              If you enable dynamic GATED routing, you will be able tooH              configure this host to use any combination of the followingF              routing protocols to exchange dynamic routing information-              with other hosts on the network: B                 Routing Information Protocol (RIP) - Version 1 & 21                 Router Discovery Protocol (RDISC)a/                 Open Shortest Path First (OSPF)i/                 Exterior Gateway Protocol (EGP)P/                 Border Gateway Protocol (BGP-4)S                 Static routese  P         * Do you want to configure dynamic ROUTED or GATED routing [NO]:<Return>  8                 A default route has not been configured.B         * Do you want to configure a default route [YES]: <Return>N         Enter your Default Gateway host name or address: GATE1.BUDGET.ACME.COM  F               gate1.budget.acme.com is not in the local host database.  C         Enter Internet address for gate1.budget.acme.com: 10.0.2.66c  #         BIND RESOLVER Configuratione  3            A BIND resolver has not been configured.s  Q            Compaq TCP/IP Services for OpenVMS supports the Berkeley Internet Name R            Domain (BIND) resolver.  BIND is a network service that enables clientsP            to name resources or objects and share information with other objects            on the network.  H            Before configuring your system as a BIND resolver, you shouldI            first be sure that there is at least one system on the networkgF            configured as either a BIND primary or secondary server for            this domain.   @            You can specify a BIND server by its address or name;>            however, if specified by name, an entry for it must,            exist in the TCPIP$HOST database.  :            You will be asked one question for each server.<            Press Return at the prompt to terminate the list.  H            Sample New TCP/IP Services Installation and Configuration A-5           A         Sample New TCP/IP Services Installation and Configuration .         A.2 Sample New Configuration Procedure  C         Enter your BIND server name: NUMB9.BUDGET.ACME.COM <Return>   C            numb9.budget.acme.com is not in the local host database.   C         Enter Internet address for numb9.budget.acme.com: 10.0.2.11 -         Enter your BIND server name: <Return>d  L            TCPIP uses timezone information provided by the OpenVMS OperatingJ            System. No additonal timezone configuration is needed for TCPIP=            when the operating system is configured correctly.y  L            This section verifies the current OpenVMS timezone configuration.O            A warning message (TCPIP-W-) indicates that corrective action shouldaL            be taken. TCPIP will appear to operate but components may displayP            either the wrong time or a time inconsistent with other applications.-         Press Return to continue ... <Return>r  R             Compaq TCP/IP Services for OpenVMS Core Environment Configuration Menu  "             Configuration options:                    1  -  Domain !                  2  -  InterfacesV                  3  -  Routing$                  4  -  BIND Resolver                   5  -  Time Zone  .                  A  -  Configure options 1 - 5                  [E] -  Exit menu  ,         Enter configuration option: <Return>  A             Compaq TCP/IP Services for OpenVMS Configuration Menud  "             Configuration options:  '                  1  -  Core environment (                  2  -  Client components(                  3  -  Server components*                  4  -  Optional components  B                  5  -  Shutdown Compaq TCP/IP Services for OpenVMSA                  6  -  Startup Compaq TCP/IP Services for OpenVMS                    7  -  Run tests  .                  A  -  Configure options 1 - 43                 [E] -  Exit configuration procedureG  .         Enter configuration option: 2 <Return>  S             Compaq TCP/IP Services for OpenVMS Client Components Configuration MenuW  E         A-6 Sample New TCP/IP Services Installation and Configurationa o         H                Sample New TCP/IP Services Installation and ConfigurationH                                   A.2 Sample New Configuration Procedure  "             Configuration options:  8                  1  -  FTP              Disabled Stopped8                  2  -  NFS Client       Disabled Stopped8                  3  -  REXEC and RSH    Disabled Stopped8                  4  -  RLOGIN           Disabled Stopped8                  5  -  SMTP             Disabled Stopped8                  6  -  TELNET           Disabled Stopped8                  7  -  DHCP             Disabled Stopped8                  8  -  Telnetsym        Disabled Stopped  .                  A  -  Configure options 1 - 8                  [E] -  Exit menu  .         Enter configuration option: 6 <Return>           TELNET Configuration  =         Service is not defined in the TCPIP$SERVICE database.o         Service is not enabled.t         Service is stopped.   )             TELNET configuration options:s  0                  1 - Enable service on this node  /                 [E] - Exit TELNET configurations  .         Enter configuration option: 1 <Return>%         Creating TELNET Service Entryl  S             Compaq TCP/IP Services for OpenVMS Client Components Configuration Menuo  "             Configuration options:  8                  1  -  FTP              Disabled Stopped8                  2  -  NFS Client       Disabled Stopped8                  3  -  REXEC and RSH    Disabled Stopped8                  4  -  RLOGIN           Disabled Stopped8                  5  -  SMTP             Disabled Stopped8                  6  -  TELNET           Enabled  Stopped8                  7  -  DHCP             Disabled Stopped8                  8  -  Telnetsym        Disabled Stopped  .                  A  -  Configure options 1 - 8                  [E] -  Exit menu  ,         Enter configuration option: <Return>  A             Compaq TCP/IP Services for OpenVMS Configuration MenuS  H            Sample New TCP/IP Services Installation and Configuration A-7 i  y      A         Sample New TCP/IP Services Installation and Configurationo.         A.2 Sample New Configuration Procedure  "             Configuration options:  '                  1  -  Core environmentr(                  2  -  Client components(                  3  -  Server components*                  4  -  Optional components  B                  5  -  Shutdown Compaq TCP/IP Services for OpenVMSA                  6  -  Startup Compaq TCP/IP Services for OpenVMSt                   7  -  Run tests  .                  A  -  Configure options 1 - 43                 [E] -  Exit configuration procedure   .         Enter configuration option: 3 <Return>  P          Compaq TCP/IP Services for OpenVMS Server Components Configuration Menu            Configuration options:t  P            1 - BIND        Disabled Stopped    11 - NTP         Disabled StoppedP            2 - BOOTP       Disabled Stopped    12 - PC-NFS      Disabled StoppedP            3 - DHCP        Disabled Stopped    13 - POP         Disabled StoppedP            4 - FINGER      Disabled Stopped    14 - PORTMAPPER  Disabled StoppedP            5 - FTP         Disabled Stopped    15 - RLOGIN      Enabled  StoppedP            6 - LBROKER     Disabled Stopped    16 - RMT         Disabled StoppedP            7 - LPR/LPD     Disabled Stopped    17 - SNMP        Disabled StoppedP            8 - METRIC      Disabled Stopped    18 - TELNET      Enabled  StoppedP            9 - NFS         Disabled Stopped    19 - TFTP        Disabled StoppedP           10 - LOCKD/STATD Disabled Stopped    20 - XDM         Disabled Stopped  )            A  -  Configure options 1 - 20n           [E] -  Exit menu  .         Enter configuration option: 5 <Return>           FTP Configurationy  )         Service is defined in the SYSUAF. =         Service is not defined in the TCPIP$SERVICE database.m         Service is not enabled.          Service is stopped.   &             FTP configuration options:  0                  1 - Enable service on this node  ,                 [E] - Exit FTP configuration  E         A-8 Sample New TCP/IP Services Installation and Configuration_ _  _      H                Sample New TCP/IP Services Installation and ConfigurationH                                   A.2 Sample New Configuration Procedure  .         Enter configuration option: 1 <Return>"         Creating FTP Service Entry  "         The FTP CLIENT is enabled.  <         * Do you want to configure FTP CLIENT [NO]: <Return>  P          Compaq TCP/IP Services for OpenVMS Server Components Configuration Menu            Configuration options:   P            1 - BIND        Disabled Stopped    11 - NTP         Disabled StoppedP            2 - BOOTP       Disabled Stopped    12 - PC-NFS      Disabled StoppedP            3 - DHCP        Disabled Stopped    13 - POP         Disabled StoppedP            4 - FINGER      Disabled Stopped    14 - PORTMAPPER  Disabled StoppedP            5 - FTP         Enabled  Stopped    15 - RLOGIN      Enabled  StoppedP            6 - LBROKER     Disabled Stopped    16 - RMT         Disabled StoppedP            7 - LPR/LPD     Disabled Stopped    17 - SNMP        Disabled StoppedP            8 - METRIC      Disabled Stopped    18 - TELNET      Enabled  StoppedP            9 - NFS         Disabled Stopped    19 - TFTP        Disabled StoppedP           10 - LOCKD/STATD Disabled Stopped    20 - XDM         Disabled Stopped  )            A  -  Configure options 1 - 20            [E] -  Exit menu  -          Enter configuration option: <Return>   A             Compaq TCP/IP Services for OpenVMS Configuration Menu   "             Configuration options:  '                  1  -  Core environmenty(                  2  -  Client components(                  3  -  Server components*                  4  -  Optional components  B                  5  -  Shutdown Compaq TCP/IP Services for OpenVMSA                  6  -  Startup Compaq TCP/IP Services for OpenVMSw                   7  -  Run tests  .                  A  -  Configure options 1 - 43                 [E] -  Exit configuration procedure   .         Enter configuration option: 6 <Return>           Begin Startup...  H            Sample New TCP/IP Services Installation and Configuration A-9 m  b      A         Sample New TCP/IP Services Installation and Configuration .         A.2 Sample New Configuration Procedure  O         %TCPIP-I-INFO, TCP/IP Services startup beginning at 5-DEC-2000 13:22:27          .82 6         %TCPIP-I-NORMAL, timezone information verifiedE         %RUN-S-PROC_ID, identification of created process is 00000058 ;         %TCPIP-I-SETLOCAL, setting domain and/or local host.2         %TCPIP-I-STARTCOMM, starting communication6         %TCPIP-I-SETPROTP, setting protocol parameters-         %TCPIP-I-DEFINTE, defining interfaces 1         %TCPIP-I-STARTNAME, starting name service ;         %TCPIP-S-STARTDONE, TCP/IP Kernel startup completednA         %TCPIP-I-LOADSERV, loading TCPIP server proxy informationoI         %TCPIP-I-SERVLOADED, auxiliary server loaded with 0 proxy records @         -TCPIP-I-SERVSKIP, skipped 0 communication proxy records9         -TCPIP-I-SERVTOTAL, total of 6 proxy records readi9         %TCPIP-S-STARTDONE, TCPIP$PROXY startup completedd7         %TCPIP-S-STARTDONE, TCPIP$FTP startup completedd:         %TCPIP-S-STARTDONE, TCPIP$TELNET startup completedO         %TCPIP-S-STARTDONE, TCP/IP Services startup completed at 5-DEC-2000 13:a         23:00.49  "         Startup request completed.$         Press Return to continue ...                                              F         A-10 Sample New TCP/IP Services Installation and Configuration l  o                          E      ________________________________________________________________n  E                                                                 Indexn    E      A                                    Configuring TCP/IP Services 4      ___________________________            (cont'd)>      Advanced Server for OpenVMS           configuration files@        configuring, 3-17                      creating new,  3-5D      Anonymous FTP                         core environment,  3-7 to2        configuring to use, 3-17               3-11?      Automatic configuration of            description of majorf9         TCP/IP Services, 3-2                  tasks,  1-1t  B                                            new configuration,  1-1E      B__________________________           optional components,  3-17n  C      BIND resolver                         postconfiguration tasks, 2        configuring, 3-11                      3-26D      BIND server                           server components,  3-14,2        configuring, 3-14                      3-16D      BOOTP server                          server environment,  3-145        configuring, 3-14                      to 3-17   C                                            tasks, recommended order 6      C__________________________              of,  3-1  >      CD-ROM distribution kit               TCPIP$CONFIG menus,?        inspecting, 1-3                        description,  3-6 >      Client components                     time required,  1-2D        starting and stopping               using TCPIP$CONFIG menus,1          individually,  3-28                  3-75D      Client environment                    using TCPIP$CONFIG option=        configuring, 3-12                      commands,  3-18iD      Configuration worksheet,              verifying services,  3-22           1-9e       Configuring TCP/IP Services        automatic, 3-2l        client components, 3-13        client environment, 3-12P          to 3-14  E                                                               Index-1e                   G         D__________________________         I__________________________A  G         DECnet over TCP/IP                  Installing TCP/IP Services,t9          configuring to use,  3-17             2-1 to 2-6eC         DECwindows                            listing the installedT;          components required for                 files, 2-5 ?             XDM,  3-16                        major tasks,  1-1nD          defining TCP transport,              new installation,  A-2A             3-29                              time required,  1-2t5          requirements for product           InterfaceR?             installation,  1-4                configuring,  3-9 =         DHCP client                         IVP (Installation F          configuring,  3-12                    Verification Procedure)@         DHCP server                           description,  3-22          configuring,  3-14aG          configuring TCP/IP                 L__________________________o:             Services,  3-2                  LBROKER server@         Disk                                  configuring,  3-14;          space requirements,  1-5           License Product.@          system, backing up,  1-4              Authorization Key         Distribution kit5          inspecting,  1-3                     See PAKY>         Domain                              LOCKD/STATD server@          configuring,  3-8                    configuring,  3-14:         Dynamic routing                     LPR/LPD client@          configuring,  3-9                    configuring,  3-12:                                             LPR/LPD server@         F__________________________           configuring,  3-14  -         FINGER server                       MoG          configuring,  3-14                 ___________________________aF         FTP client                          Magnetic tape distribution2          configuring,  3-13                    kit>         FTP server                            inspecting,  1-32          configuring,  3-14                 Memory=                                               physical memoryoB         G__________________________              requirements, 1-51         Global pagelets and                 Menusr?           sections                            understanding the D          increasing,  1-6                        TCPIP$CONFIG menus,4          requirements,  1-6                      3-69                                             METRIC serverx@                                               configuring,  3-14           Index-2                  ?                                             POLYCENTER SoftwaretC         N__________________________            Installation utilityr?         NFS client                            for installing or C          configuring,  3-12                      upgrading (OpenVMSrF         NFS server                               VAX or Alpha), 2-1 to4          configuring,  3-14                      2-66         Nonpaged dynamic pool               POP server@          increasing,  1-6                     configuring,  3-14=         NTP server                          PORTMAPPER server @          configuring,  3-14                   configuring,  3-14D                                             Postconfiguration tasks,3         O__________________________            3-26B0         OpenVMS License Management          PWIP@           Facility (LMF)                      configuring,  3-17D          using to register PAK,               requirement, interruptA             1-4                                  stack pages, 1-7   -         OpenVMS operating system            RoG          reboot,  2-4                       ___________________________o8          upgrading,  1-4                    Reboot,  2-59         Optional components,                Release notessD           configuring                         extracting into a .TXT:          Advanced Server for                     file, 1-3<             OpenVMS,  3-17                    location afterB          anonymous FTP,  3-17                    installation, 2-5@          PATHWORKS (Advanced                REXEC and RSH client@             Server),  3-17                    configuring,  3-129          PWIP driver,  3-17                 RLOGIN client @          SRI QIO interface,  3-17             configuring,  3-129                                             RLOGIN serveru@         P__________________________           configuring,  3-146         PAK                                 RMT server@          registering,  1-4                    configuring,  3-14  -         PATHWORKS                           SrG          configuring,  3-17                 ___________________________n=         PATHWORKS Advanced Server,          Server componentsoC           1-7                                 starting and stoppingpC         PATHWORKS Internet Protocol              individually, 3-28e7           driver                            SMTP client @          See PWIP                             configuring,  3-120         PC-NFS server                       SNMP<          configuring,  3-14                   testing,  3-24;                                               verifying the D                                                  configuration, 3-24  H                                                                  Index-3 g  t            D         SNMP server                         TCP/IP Services (cont'd)E          configuring,  3-14                   preparing to configure, 4         SRI QIO                                  1-9H          configuring to use,  3-17            preparing to install,  1-27         Starting TCP/IP Services                 to 1-9q?          after configuration,  3-20           server componentsoF          automatically,  3-27                    configuring,  3-14 to8          manually,  3-28                            3-17F          using TCPIP$CONFIG,  3-20               starting and stoppingF         Stopping TCP/IP Services                    individually, 3-28<          automatically,  3-27                 starting afterD          manually,  3-28                         configuration, 3-20C         System parameters                     starting and stopping D          checking and changing                   automatically, 3-27C             before installing,  1-6           starting and stopping ?             to 1-7                               manually, 3-28 <          setting the SPTREQ                   starting usingC             parameter,  1-7                      TCPIP$CONFIG, 3-20e  D         T                                     upgrading,  2-1 to 2-6>         ___________________________           verifying,  3-22>         Tasks                               TCPIP$CONFIG menus?          major, installing and                description,  3-6 B             configuring,  1-1               TCPIP$CONFIG procedureD         TCP/IP Services                       See Configuring TCP/IP9          and anonymous FTP access,               Servicesl9             3-18                            TELNET clientd@          client components                    configuring,  3-129             configuring,  3-12 to           TELNET serverp@                3-14                           configuring,  3-147             starting and stopping           TFTP server @                individually,  3-28            configuring,  3-145          configuration,  3-1 to             Time zone1@             3-26                              configuring,  3-11A             new,  A-2                       TK50 distribution kit >          configuration files                  inspecting,  1-3;             converting from                 TroubleshootingoE                previous                       configuration procedure ?                configuration,  3-4               problems, 3-24           core environment               configuring,  3-7 to                3-11 "          installation,  2-1 to 2-6             new,  A-1            Index-4                    G         U__________________________         V__________________________   >         UIC codes                           Verifying the SNMPB          assigning,  1-8                       configuration, 3-24@         Upgrading TCP/IP Services,          Verifying the TCP/IPF           2-1 to 2-6                           Services configuration,3         User access                            3-22m          configuring to allowaG             anonymous FTP access,           X__________________________c6             3-17                            XDM server  <                                               and DECwindowsC                                                  requirements, 3-16C@                                               configuring,  3-16                                                            H                                                                  Index-5