                   7                      Compaq TCP/IP Services for OpenVMS 3                      Installation and Configuration   .                      Order Number: AA-LU49N-TE                          April 2002   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- B                                                   sedes the CompaqE                                                   TCP/IP Services for F                                                   OpenVMS InstallationC                                                   and Configuration E                                                   manual, Version 5.1   ?                      Software Version:            Compaq TCP/IP F                                                   Services for OpenVMS=                                                   Version 5.3   ?                      Operating Systems:           OpenVMS Alpha E                                                   Versions 7.2-2, 7.3 F                                                   OpenVMS VAX Versions:                                                   7.2, 7.3              0                      Compaq Computer Corporation#                      Houston, Texas                  H               __________________________________________________________  @                2002 Compaq Information Technologies Group, L.P.  B               Compaq, the Compaq logo, Alpha, OpenVMS, Tru64, VAX,@               VMS, and the Digital logo are trademarks of CompaqE               Information Technologies Group, L.P. in the U.S. and/or                other countries.  H               All other product names mentioned herein may be 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.                                E      ________________________________________________________________   E                                                              Contents     E      Preface..................................................      v     :      1  Preparing to Install and Configure TCP/IP Services  E            1.1   Understanding the Major Tasks................    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   Invoking the Installation Procedure..........    2-1 2            2.2   Stepping Through the InstallationE                  Procedure....................................    2-3 E            2.3   Postinstallation Tasks.......................    2-5         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-8H               3.3.4.1     Domain Configuration...................    3-9H               3.3.4.2     Interface Configuration................    3-9H               3.3.4.3     Dynamic Routing Configuration..........   3-10H               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-15H               3.3.7     Configuring the Optional Components......   3-17;               3.3.7.1     Configuring and Enabling Kerberos H                           Support................................   3-19@               3.4   Using TCPIP$CONFIG Option Commands to BypassH                     TCPIP$CONFIG Menus...........................   3-21H               3.5   Making Configuration Changes Take Effect.....   3-222               3.6   Stopping TCP/IP Services UsingH                     TCPIP$CONFIG.................................   3-232               3.7   Starting TCP/IP Services UsingH                     TCPIP$CONFIG.................................   3-24H               3.8   Verifying the Configuration..................   3-26=               3.8.1     Running the IVP from the TCPIP$CONFIG H                         Command Procedure........................   3-27<               3.8.2     Running the IVP from the OpenVMS DCLH                         Prompt...................................   3-27>               3.8.3     Verifying the TCP/IP Services InternetH                         Configuration............................   3-27H               3.8.4     Verifying the SNMP Configuration.........   3-28H               3.9   Additional Configuration Tasks...............   3-30<               3.10  Starting and Stopping TCP/IP Services byH                     Command......................................   3-31;               3.10.1    Automatically Starting and Stopping H                         TCP/IP Services..........................   3-31    
         iv                 =               3.10.2    Starting and Stopping TCP/IP Services H                         Manually.................................   3-32A               3.10.3    Starting and Stopping Individual Services H                         .........................................   3-32:               3.10.4    Starting and Stopping User-WrittenH                         Services.................................   3-33?               3.11  Specifying TCP/IP Services as the Transport H                     for DECwindows Applications..................   3-33    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-28            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 proceduresA               for Version 5.3 of the TCP/IP Services product. For H               information about last-minute changes to these procedures,G               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         Compaq TCP/IP Services    This manual provides conceptual infor-D         for OpenVMS Concepts and  mation about TCP/IP networking on E         Planning                  OpenVMS systems, including general  F                                   general planning issues to consider H                                   before configuring your system to use ?                                   the TCP/IP Services software.   H                                   This manual also describes the manualsH                                   in the documentation set and  providesB                                   a glossary of terms and acronymsB                                   for the TCP/IP Services software*                                   product.  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         Compaq 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         Compaq TCP/IP Services    This manual presents an overviewA         for OpenVMS ONC RPC       of high-level programming using ?         Programming               open network computing remote B                                   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 bestb.                                   performance.  @         Compaq TCP/IP Services    This manual describes the IPv6C         for OpenVMS Guide to      environment, the roles of systemsp@         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.k           Reader's Commentsw  G               Compaq welcomes your comments on this manual. Please sendr<               comments to either of the following addresses:  /               Internet    openvmsdoc@compaq.comh  5               Mail        Compaq Computer Corporationa>                           OSSG Documentation Group, ZKO3-4/U08,                           110 Spit Brook Rd./                           Nashua, NH 03062-2698   -         How to Order Additional Documentation_  H               Visit the following World Wide Web address for information:               about how to order additional documentation:  ,               http://www.openvms.compaq.com/          H                                                                       ix                          ConventionsT  2               The name TCP/IP Services means both:  9               o  Compaq TCP/IP Services for OpenVMS Alpha2  7               o  Compaq TCP/IP Services for OpenVMS VAX   E               The name UNIX refers to the Compaq Tru64 UNIX operating                system.g  @               The following conventions are used in this manual.@               In addition, please note that all IP addresses are               fictitious.   G               Ctrl/x           A sequence such as Ctrl/x indicates that F                                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,.1                                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, or C                                   other information can be entered.   	         x  v  i              @               .                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.e  >               ( )              In command format descriptions,A                                parentheses indicate that you musteD                                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. E                                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.f  E               { }              In command format descriptions, bracesVB                                indicate required choices; you mustG                                choose at least one of the items listed.rD                                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                   >               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).  F               UPPERCASE TEXT   Uppercase text indicates a command, theH                                name of a routine, the name of a file, orG                                the abbreviation for a system privilege.m  E               Monospace text   Monospace type indicates code examples ?                                and interactive screen displays.A  G                                In the C programming language, monospace2D                                type in text identifies the following?                                elements: keywords, the names ofEH                                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.   A               numbers          All numbers in text are assumed to.A                                be decimal unless otherwise noted. C                                Nondecimal radixes-binary, octal, or D                                hexadecimal-are explicitly indicated.                               xii                        H                                                                        1H         ________________________________________________________________  H                       Preparing to Install and Configure TCP/IP Services      E               This chapter explains how to prepare for installing andaF               configuring Compaq TCP/IP Services for OpenVMS software.  )         1.1 Understanding the Major Taskst  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 asi                a layered product.  G               After you install TCP/IP Services, you need to enable thelG               components and verify the configuration through the menu-TH               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 m  l      :         Preparing to Install and Configure TCP/IP Services)         1.1 Understanding the Major Tasks   H               Table_1-1_Major_Tasks:_Installing_and_Configuring_________  H               Step_Task________________________________Described_in...__  G               1    Prepare for installation and        Sections 1.2 ande:                    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.d  B               5    Start TCP/IP Services.              Section 3.5  B               6    Verify the configuration.           Section 3.8  B               7    Complete additional configuration   Section 3.9H               _____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.r  D               5    Register the TCP/IP Services        Section 1.2.4                    license PAK.   E               6    Check the disk space, memory, and   Sections 1.2.5 D                    system parameters.                  through 1.2.7  D               7    Assign a user identification code   Section 1.2.8'                    (UIC), if necessary.h  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. If C               you have an individual CD-ROM, supply the device name H               (such as DKAn) for the media when you issue the command to&               install TCP/IP Services.  G               Check that the kit contains everything listed on the BilliD               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 knowi-               before you install the product.   G               You can have the POLYCENTER Software Installation utility B               extract the release notes as either a text file or aE               PostScript file. To extract the release notes as a textvH               file, enter the following POLYCENTER Software Installation               utility command:  H                   Preparing to Install and Configure TCP/IP Services 1-3 e         :         Preparing to Install and Configure TCP/IP Services!         1.2 Preinstallation Tasks   Q               $ PRODUCT EXTRACT RELEASE_NOTES TCPIP/SELECT=TCPIP053.RELEASE_NOTESP  F               To extract the release notes as a PostScript file, enter               the following:  T               $ PRODUCT EXTRACT RELEASE_NOTES TCPIP/SELECT=TCPIP053_RELEASE_NOTES.PS  >         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 isuH               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 Keyc  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 optionaloF               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:n  E               o  Run the SYS$UPDATE:VMSLICENSE.COM file and enter them,                  data from your License PAK.  >         1-4 Preparing to Install and Configure TCP/IP Services n  n      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 OpenVMS                Cluster.  A               For complete information about LMF, see the OpenVMSo0               License Management Utility Manual.  %         1.2.5 Checking the Disk SpaceS  B               Make sure your system meets the following disk space               requirements:_  H               __________________________________________________________H               System_____________Minimum_Block_Size_____________________  (               OpenVMS Alpha      125,000  H               OpenVMS_VAX________70,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$SYSDEVICE   *         1.2.6 Checking the Physical Memory  F               Make sure the system meets the following physical memory               requirements:   H               __________________________________________________________H               System_____________Minimum_Memory_________________________  &               OpenVMS Alpha      32 MB  H               OpenVMS_VAX________24_MB__________________________________  )               To check the memory, enter:                   $ SHOW MEMORY/FULL  H                   Preparing to Install and Configure TCP/IP Services 1-5    m      :         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 readily @               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.o  3         1.2.7.1 Global Pagelets and Global Sections   F               The TCP/IP Services software requires 65 global sections'               and 8100 global pagelets.T  B               To check the number of available global pagelets andE               global sections, enter WRITE commands with the F$GETSYIMD               lexical functions. The following is an example from an#               OpenVMS Alpha system:   :               $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLPAGES")               143576  :               $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLSECTS")               249   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 GBLPAGESi;               and GBLSECTIONS, as in the following example:   !               ADD_GBLPAGES = 7500h"               ADD_GBLSECTIONS = 75  %         1.2.7.2 Nonpaged Dynamic Pool   E               Add at least 500,000 bytes of nonpaged dynamic pool for '               the software, as follows:   .               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 fora6                  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 F               help eliminate system startup warnings and failures. ForC               information about the PATHWORKS for OpenVMS (Advanced 7               Server), see the PATHWORKS documentation.o  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)  G               On VAX systems, make sure the AUTOGEN parameter SPTREQ issF               set to at least 6000. To check the minimum SPTREQ value,$               run SYSMAN as follows:  %               $ RUN SYS$SYSTEM:SYSMANt  +               SYSMAN> parameter show sptreqcE               %SYSMAN, a USE ACTIVE has been defaulted on node VMSVAX   6               Node VMSVAX:   Parameters in use: ACTIVEP               Parameter Name   Current  Default  Minimum  Maximum Unit   DynamicP               --------------   -------  -------  -------  ------- ----   -------G               SPTREQ              8000     3900     3000       -1 Pagese  H                   Preparing to Install and Configure TCP/IP Services 1-7 x         :         Preparing to Install and Configure TCP/IP Services!         1.2 Preinstallation Tasks                  SYSMAN>   C               To modify the minimum SPTREQ, run the AUTOGEN command E               procedure as described in the OpenVMS System Management H               Utilities Reference Manual: A-L. Modify the minimum SPTREQ               value as follows:e                 MIN_SPTREQ = 6000   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.   G               The TCPIP$CONFIG configuration procedure uses a group UICoD               to create accounts for components. If a user-specifiedD               UIC is not in place from a previous configuration, the@               procedure creates the following UIC group numbers:  H               __________________________________________________________               Default                UIC Group H               Number_____Description____________________________________  A               3655       The default UIC group number for servicep@                          accounts. If this is an initial productE                          configuration but the procedure detects thatfH                          number 3655 is in use, TCPIP$CONFIG prompts you4                          for a new UIC group number.  J               3375       The default UIC group number for the TCPIP$NOBODY&                          user account.  G               3376       The default UIC group number for the ANONYMOUS H               ___________account._______________________________________  F               Before you assign a new group UIC, check that the numberG               you chose is not already in use by entering the following                commands:i  >         1-8 Preparing to Install and Configure TCP/IP Services i  l      H                       Preparing to Install and Configure TCP/IP ServicesH                                                1.2 Preinstallation Tasks  (               $ RUN SYS$SYSTEM:AUTHORIZE  4               UAF> SHOW /BRIEF [your-group-number,*]  D               UAF> SHOW /IDENTIFIER /VALUE=UIC:[your-group-number,*]  E               To force TCPIP$CONFIG to allow you to specify a new UICrE               group number, assign the value TRUE to the logical nameaH               TCPIP$ASK_GROUP_UIC, as in the following example. When youE               configure TCP/IP Services, TCPIP$CONFIG prompts you fora               the group UIC.  /               $ DEFINE TCPIP$ASK_GROUP_UIC TRUEr  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 are G               reconfiguring after a product upgrade, the procedure useseG               the previous configuration information as the default for $               the new configuration.  E               For information to help you answer the questions on the F               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 .         :         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)?d  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 networka5         interface), might be configured automatically 0         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, WE0)?[1]_  H                                                        _________________  H                                                        _________________  F         [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 clientn         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         What is the group UIC for TCP/IP Services      _________________9         (see Section 1.2.8)? For example, [GROUP1,JONES].   H         Which type of routing is appropriate for the   _________________#         network, Static or Dynamic?o  /              Static - For simple networks wherec!              routes do not changet  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 wheree$              flexibility is required  0              If dynamic, you must specify either%              ROUTED or GATED routing.m  3         Do you plan to enable the BIND resolver? Ife         so:   H         *    What is the name of the BIND server you   _________________3              want the resolver to use (for example,               MAINSV)?o  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:   H         *    Do you want to allow SNMP management      _________________2              clients to modify the MIBs by issuing              set requests?  H                                                 (continued on next page)    H                  Preparing to Install and Configure TCP/IP Services 1-11           :         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         *    Do you want to enable authentication      _________________1              traps when the master agent receivese.              an SNMP request that specifies an+              unauthorized community string?   H         *    What is the name of the system's contact  _________________5              person? Specify text as in the following,               example: Sam Spade.  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 Angeles               - 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 communityi3              name. The default is "public." Specifye0              a string consisting of alphanumeric0              characters only. Do not enclose the4              string in quotes: the case is preserved+              as you enter it. Example: Rw2.g  H         *    Do you want to provide additional         _________________/              community names and addresses (forp3              implementing traps and allowing access 5              beyond the default read-only provided bygH         _____the_"public"_community)?___________________________________                    ?         1-12 Preparing to Install and Configure TCP/IP Services                        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 directlyiF               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.   /         2.1 Invoking the Installation Procedurer  E               When you have completed the recommended preinstallationiC               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 configureM+               this version of the software._  G               To install the TCP/IP Services software on an OpenVMS VAXu2               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.n  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$STARTUPm  H                                           Installing TCP/IP Services 2-1 l         "         Installing TCP/IP Services/         2.1 Invoking the Installation Procedure   B                  so that the current version of the product starts9                  automatically when the system starts up.u  F               4. If a previous version of the software is installed onE                  the system, shut it down. Enter one of the following.                  commands:  H                  _______________________________________________________                  SoftwareoH                  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 your1A                  system, you can create a log of the installationbE                  procedure by entering the following command and thena4                  log in to the system account again:  4                  $ SET HOST 0/LOG=file-specification  G                  In this command, file-specification is the name of thePH                  file to which you want the log written. The log file is2                  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:n  ?                  $ PRODUCT INSTALL TCPIP /SOURCE=directory-pathB  C                  In this command, directory-path specifies the diskoG                  and directory name for the source drive that holds thegP                  TCP/IP Services kit. For example, /SOURCE=DKA400:[TCPIPAXP053].  @                  If you do not specify the source qualifier, theF                  POLYCENTER Software Installation utility searches theE                  location defined by the logical name PCSI$SOURCE. IfcF                  not defined, the utility searches the current default                  directory.t  &         2-2 Installing TCP/IP Services y  .      H                                               Installing TCP/IP ServicesH                          2.2 Stepping Through the Installation Procedure  7         2.2 Stepping Through the Installation Procedure   B               After you invoke the installation procedure, you areB               prompted for information. Example 2-1 shows a sampleA               installation on an OpenVMS Alpha system that has annA               earlier version of TCP/IP Services installed on it.hH               Additional explanatory information follows each portion ofH               the script. For a sample installation on a system on whichC               the product has never been installed, see Appendix A.   A               The actual installation output that is displayed on ?               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 that )                 were created, then exits.n  ;                 The symbols xx in the following example and B                 elsewhere in this document represent the product's0                 two-digit update version number.  E                 _____________________________________________________t  C         Example 2-1 TCP/IP Services Installation: Sample POLYCENTERa;                     Software Installation Utility ProcedureK  B            1 - DEC AXPVMS TCPIP V5.3-xx            Layered ProductB            2 - DEC AXPVMS TCPIP V5.1-15            Layered ProductB            3 - DEC AXPVMS TCPIP V5.0-11            Layered Product(            4 - All products listed above            5 - Exite  N         Choose one or more items from the menu separated by commas: 1 <Return>  F               The menu that is displayed initially includes the latestE               TCP/IP Services product and any versions of the productPA               that are in place on the system. Install the latestS!               version (option 1).M        H                                           Installing TCP/IP Services 2-3 a  e  "         Installing TCP/IP Services7         2.2 Stepping Through the Installation Procedure       0         The following product has been selected:E             DEC AXPVMS TCPIP V5.3-xx                  Layered Productm  /         Do you want to continue? [YES] <Return>   G               Press Return to continue with the installation procedure.   (         Configuration phase starting ...  O         You will be asked to choose options, if any, for each selected product           and forsJ         any products that may be installed to satisfy software dependency          requirements.   E         DEC AXPVMS TCPIP V5.3-xx: Compaq TCP/IP Services for OpenVMS.   F             Copyright 2002 Compaq Information Technologies Group, L.P.  '             Compaq Computer Corporationd  N             Compaq TCP/IP Services for OpenVMS offers several license options.  @         Do you want the defaults for all options? [YES] <Return>  G               Answer YES to choose the POLYCENTER Software Installation D               utility defaults for the options or NO to choose other               options.  8         Do you want to review the options? [NO] <Return>  G               Answer YES to review the POLYCENTER Software InstallationeC               utility options. In this example, the options are noth               reviewed.e  F               If you select YES, the options are displayed and you areE               asked whether you are satisfied with the options. PresseE               Return to accept the options as listed, or answer NO tos!               change the options.n  $         Execution phase starting ...  ?         The following product will be installed to destination:bM             DEC AXPVMS TCPIP V5.3-xx              DISK$ALPHASYS:[VMS$COMMON.]_?         The following product will be removed from destination: M             DEC AXPVMS TCPIP V5.1-15              DISK$ALPHASYS:[VMS$COMMON.]5  N         Portion done: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%  &         2-4 Installing TCP/IP Services        H                                               Installing TCP/IP ServicesH                          2.2 Stepping Through the Installation Procedure  F               The following message appears only if an earlier versionA               of TCP/IP Services was configured on your system. A F               similar message, verifying the product name and version,?               appears if you are installing for the first time._  =         %PCSI-I-PRCOUTPUT, output from subprocess follows ...u         % TCPIP-W-PCSI_INSTALL         % - BG device exists.rG         %   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: B             DEC AXPVMS TCPIP V5.3-xx               Layered Product/         The following product has been removed: B             DEC AXPVMS TCPIP V5.1-15               Layered Product  E         DEC AXPVMS TCPIP V5.3-xx: Compaq TCP/IP Services for OpenVMS.r  F             Check the release notes for current status of the product.  "         2.3 Postinstallation Tasks  E               After the installation completes, perform the followinge               steps:  %               1. Optionally, you can:I  ?                  -  Read the Compaq TCP/IP Services for OpenVMS @                     Release Notes on line or print the file from9                     SYS$HELP:TCPIP053_RELEASE_NOTES.PS orb4                     SYS$HELP:TCPIP053.RELEASE_NOTES.  D                  -  Display a list of the TCP/IP Services files that@                     were installed. Enter the following command:  ?                     $ PRODUCT LIST TCPIP /SOURCE=directory-path.  A                     In this command, directory-path specifies thee@                     disk and directory name for the source driveD                     that holds the TCP/IP Services kit (for example,H                     /SOURCE=DKA400:[TCPIPAXP053]). If you do not specifyA                     the source qualifier, the POLYCENTER Software F                     Installation utility searches the location defined  H                                           Installing TCP/IP Services 2-5 T  I      "         Installing TCP/IP Services"         2.3 Postinstallation Tasks  H                     by the logical name PCSI$SOURCE. If not defined, theC                     utility searches the current default directory.   A               2. 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 newaD                  TCP/IP Services software to take effect. Proceed to                  step 4.  E                 _____________________ Important _____________________D  <                 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 configurationc)                 (described in Chapter 3).   E                 _____________________________________________________   D               3. Log out of the SYSTEM account, and then log back inE                  to the SYSTEM account to establish the TCPIP command_                  environment.5  C               4. Proceed to Chapter 3 to configure TCP/IP Services._                                          &         2-6 Installing TCP/IP Services t  a                  H                                                                        3H         ________________________________________________________________  H                                              Configuring TCP/IP Services      C               After you install Compaq TCP/IP Services for OpenVMS, G               you need to enable the components and characteristics youoF               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 additionalo,               configuration and setup tasks.  =         3.1 Recommended Order for Configuring TCP/IP Servicesn  C               Table 3-1 lists the tasks involved in configuring the_C               TCP/IP Services components and functionality, and the_1               sections that describe these tasks./                                          H                                          Configuring TCP/IP Services 3-1    t      #         Configuring TCP/IP Services_=         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.f  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 convert_8                   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.e  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.8  F               8   Complete additional configuration        Section 3.9H               ____tasks,_as_appropriate.________________________________  A         3.2 Automatic Configuration of TCP/IP Services Using DHCPg             Client  C               TCP/IP Services Version 5.3 supports the DHCP client,_G               which allows you to have your system configured automati-tH               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 setsiF                  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 clients  !                  -  TELNET serverp                    -  SMTP  G                  For more information about DHCP, see the Compaq TCP/IP_8                  Services for OpenVMS Management manual.  @               o  Run TCPIP$CONFIG. Choose option 2 from the Core@                  Environment Configuration menu to configure theF                  Internet interface, and then choose option 2 from the.                  Interface Configuration menu:  '                  Configuration options:   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:i  H               o  Make selections that enable components for your system.=                  To select the default, press the Return key.l  8               o  Start or stop TCP/IP Services software.  *               o  Verify the configuration.  $               To get started, enter:  )               $ @SYS$MANAGER:TCPIP$CONFIG   H                                          Configuring TCP/IP Services 3-3    p      #         Configuring TCP/IP Services           3.3 Running TCPIP$CONFIG  E         3.3.1 Converting Existing TCP/IP Services Configuration Filesa               (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 youtE               have never configured a V5.x product on the system, thetG               procedure begins by asking you whether to convert the oldn2               TCP/IP Services configuration files:  5               Convert the old configuration files [Y].  @               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 beingd               created:  P               Checking TCP/IP Services for OpenVMS configuration database files.  1               No new database files were created.   @               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 requiredlC           to run Compaq TCP/IP Services for OpenVMS on this system.o             NOTE: G           TCP/IP has been previously configured from an earlier version_G           of this product.  You can avoid a complete reconfiguration of_H           TCP/IP by allowing this procedure to automatically convert theI           old configuration files.  If you choose not to do this now, you I           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...i      '         3-4 Configuring TCP/IP Servicesn e         H                                              Configuring TCP/IP ServicesH                                                 3.3 Running TCPIP$CONFIG  8             UCX$SERVICE.DAT        --> TCPIP$SERVICE.DAT5             UCX$HOST.DAT           --> TCPIP$HOST.DATh8             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.DATe  2                No new database files were created.            FTP SERVER Configuration            LPD SERVER Configuration  -         Service is not defined in the SYSUAF.n3           Nonprivileged user access is not enabled.   A         By default, Compaq TCP/IP Services for OpenVMS configures F         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 queue *                  - Name of the remote host9                  - Spooling directory for the local queue   P                To add or delete printers in the TCPIP PRINTCAP database, use the6                $RUN SYS$SYSTEM:TCPIP$LPRSETUP command.	         .e	         . 	         .d  >         3.3.2 Creating New TCP/IP Services Configuration Files  G               If you do not have an existing TCP/IP Services configura-oG               tion in place from a previous version of the product, theoH               procedure begins by creating configuration database files,6               as shown in the following sample output:  H                                          Configuring TCP/IP Services 3-5 l  s      #         Configuring TCP/IP Services           3.3 Running TCPIP$CONFIG  /          TCP/IP Network Configuration Proceduret  @          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.a  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,          Creating TCPIP$ETC:SYSCONFIGTAB.DAT  G         Compaq TCP/IP Services for OpenVMS requires a definition for atAE         least one interface.  There are no interfaces defined on thisM         system.   J         Please select the Interface option from the Core Environment Menu.  3         3.3.3 Understanding the Configuration Menuse  E               After the configuration files are converted or created,s7               the Main Configuration menu is displayed:t  =         Compaq TCP/IP Services for OpenVMS Configuration Menu/  "             Configuration options:  )                    1  -  Core environmentc*                    2  -  Client components*                    3  -  Server components,                    4  -  Optional componentsD                    5  -  Shutdown Compaq TCP/IP Services for OpenVMSC                    6  -  Startup Compaq TCP/IP Services for OpenVMS "                    7  -  Run tests  0                    A  -  Configure options 1 - 45                   [E] -  Exit configuration procedurei  #         Enter configuration option:r      '         3-6 Configuring TCP/IP Serviceso u         H                                              Configuring TCP/IP ServicesH                                                 3.3 Running TCPIP$CONFIG  )               The options are as follows:f  H         ________________________________________________________________H         Option_______________Description________________________________  C         1   Core environ-    Configure software associated with theuG             ment             Network, Internet, and Transport layers of E                              the TCP/IP architecture (Section 3.3.4).t  G         2   Client           Configure application software and relatedo8             components       components (Section 3.3.5).  B         3   Server           Configure server software and related8             components       components (Section 3.3.6).  E         4   Optional         Configure software necessary if you plan B             components       to allow Anonymous FTP access, enableC                              Kerberos authentication for the TELNETeF                              server, or run such products as PATHWORKSD                              for OpenVMS (Advanced Server), AdvancedD                              Server for OpenVMS, DECnet over TCP/IP,F                              or any applications that use the StanfordE                              Research Institute (SRI) QIO application B                              programming interface (Section 3.3.7)  @         5   Shutdown TCP/IP  Stop TCP/IP Services (Section 3.6).             Services for             OpenVMS   A         6   Startup TCP/IP   Start TCP/IP Services (Section 3.7).8             Services for             OpenVMSc  H         7   Run tests        Run the installation verification procedure+                              (Section 3.8).p  >         A   Configure        Configure all the TCP/IP ServicesB             options 1 -      components (the core, client, server,D             4                and optional components). The procedureD                              takes you through each of the component3                              configuration options.   9         E   Exit the         Return to the system prompt.              configuration H         ____procedure___________________________________________________  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 command  H                                          Configuring TCP/IP Services 3-7 o  t      #         Configuring TCP/IP Servicesq          3.3 Running TCPIP$CONFIG  C               parameters when you run TCPIP$CONFIG. For information <               about the command parameters, see Section 3.4.  .         3.3.4 Configuring the Core Environment  H               To display the Core Environment Configuration menu, chooseE               option 1 (Core environment) from the Main Configuration E               menu. If you chose option A from the Main ConfigurationYC               menu to configure all the TCP/IP Services components,PB               the Core Environment Configuration menu is displayedE               first. The sample output in the following sections show H               the progression of the procedure when you choose option A.  C               You are required to configure the Domain, Interfaces,cE               and Routing components; BIND Resolver and Time Zone ared               optional.   F                 ________________________Note  ________________________  ?                 Use the Interfaces menu (option 2) to set up an >                 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 EnvironmentT<                 components. Ask your network manager whetherA                 these components are configured by DHCP. For moreI?                 information, see the DHCP client documentation.s  E                 _____________________________________________________s  N         Compaq TCP/IP Services for OpenVMS Core Environment Configuration Menu  !            Configuration options:u                      1 - Domaino!                    2 - Interfaces                     3 - Routing$                    4 - BIND Resolver                     5 - Time Zone  /                    A  - Configure options 1 - 5 !                   [E] - Exit menut  .         Enter configuration option: A <Return>    '         3-8 Configuring TCP/IP Services  i         H                                              Configuring TCP/IP ServicesH                                                 3.3 Running TCPIP$CONFIG  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  H               The following is sample output for configuring the domain:           DOMAIN Configuration  E         Enter Internet domain [budget.acme.com]: widgets.com <Return>e  '         3.3.4.2 Interface Configuration   @               The following is sample output for configuring the!               Internet interface:            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.255PA            C_Addr:             C_NETWRK:                C_BRDCST:t              Flags:e"            Receive buffer:       0  M              Compaq TCP/IP Services for OpenVMS Interface WE0 Reconfigurationv              Menu   %              Reconfiguration options:   I                    1  -  Configure interface manually   (Current default) 5                    2  -  Let DHCP configure interface_  E                   [E] -  Exit menu (Do not reconfigure interface WE0)b  ,         Enter configuration option: <Return>  D               In this example, no changes are made to the interface.  H                                          Configuring TCP/IP Services 3-9      #         Configuring TCP/IP Servicesu          3.3 Running TCPIP$CONFIG  -         3.3.4.3 Dynamic Routing Configuration   D               The following is sample output for configuring dynamic               routing:  %         DYNAMIC ROUTING Configurationp  1          Dynamic routing has not been configured.   >             You may configure dynamic ROUTED or GATED routing.A             You cannot enable both at the same time.  If you wantrA             to change from one to the other, you must disable thenC             current routing first, then enable the desired routing.t  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 othern8             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 information ,             with other hosts on the network:B                 Routing Information Protocol (RIP) - Version 1 & 21                 Router Discovery Protocol (RDISC) /                 Open Shortest Path First (OSPF)r/                 Exterior Gateway Protocol (EGP)A/                 Border Gateway Protocol (BGP-4)                  Static routes   I         * Do you want to configure dynamic ROUTED or GATED routing [NO]: n         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 an (             internetwork gateway or not.  P         * Do you want this host to supply its dynamic routing information [NO]:          <Return>    (         3-10 Configuring TCP/IP Services u  r      H                                              Configuring TCP/IP ServicesH                                                 3.3 Running TCPIP$CONFIG  +         3.3.4.4 BIND Resolver Configuration   E               The following is sample output for configuring the BIND                resolver:o  4         A BIND resolver has already been configured.  #         BIND Resolver Configuration              Transport:  UDPC%           Domain:     budget.acme.com            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.   '         3.3.4.5 Time Zone ConfigurationP  E               The following is sample output for configuring the time                zone:            TIME ZONE Configuratione  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.yN           A warning message (TCPIP-W-) indicates that corrective action shouldK           be taken. TCPIP will appear to operate but components may display O           either the wrong time or a time inconsistent with other applications.C  <         %TCPIP-I-INFO, Logical name SYS$TIMEZONE_RULE found.M         -TCPIP-I-INFO, Software for automatic Summer/Winter time (TDF) changeg"         -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 m  h      #         Configuring TCP/IP Servicesg          3.3 Running TCPIP$CONFIG  G               After you configure the core environment, press Return or E               choose option E to exit from the Core Environment menu. G               If you chose option A from the Main Configuration menu tooF               configure all the TCP/IP Services components, the ClientE               Components Configuration menu displays next; otherwise,nG               the procedure returns to the the Main Configuration menu.:  0         3.3.5 Configuring the Client Environment  B               To display the Client Components Configuration menu,?               choose option 2 (Client components) from the MainwE               Configuration menu. If you chose option A from the MainoE               Configuration menu to configure all the TCP/IP Services B               components, the Client Components Configuration menuE               displays automatically after you finish configuring thea*               core environment components.  C               From the Client Components Configuration menu, choose >               option A to configure all the client components.H               Alternatively, you can configure one client component at aH               time. The sample output in the following sections show theD               progression of the procedure when you choose option A.  O         Compaq TCP/IP Services for OpenVMS Client Components Configuration Menur           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 beenPC               enabled in the TCP/IP Services configuration databasefA               (TCPIP$CONFIGURATION.DAT). The enabled services arePC               started the next time TCP/IP Services is started. YouF  (         3-12 Configuring TCP/IP Services e  l      H                                              Configuring TCP/IP ServicesH                                                 3.3 Running TCPIP$CONFIG  D               can also start (or stop) a specific component, withoutG               having to restart TCP/IP Services, by choosing the "Start G               service" option from that component's configuration menu.:E               In addition, you can use command procedures to start orfH               stop a specific component, as explained in Section 3.10.3.  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 D               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 madep-               from the Core Environment menu.   E               To minimize resource consumption, enable and start onlylF               those components that you are sure to use. Disable those%               you do not plan to use.   F               To configure all the client components, choose option A.  G               The following is an example of the output for configuring G               an FTP client. The configuration output for other clientseF               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.e  .         Enter configuration option: 1 <Return>            FTP CLIENT Configuration  ,         Service is enabled on specific node.         Service is stopped.e  2                  FTP CLIENT configuration options:  9                          1 - Disable service on this nodeP  7                          2 - Start service on this node   ;                         [E] - Exit FTP_CLIENT configurationi  .         Enter configuration option: 1 <Return>  "         The FTP SERVER is enabled.  A         * Do you want to configure the FTP SERVER [NO] ? <Return>   H                                         Configuring TCP/IP Services 3-13           #         Configuring TCP/IP Servicest          3.3 Running TCPIP$CONFIG  E               In the preceding example, the FTP client was originally @               enabled, and you chose option 1 to disable it. TheC               following example shows the configuration output that H               might be seen if you want to enable an FTP client that had               been disabled.            FTP CLIENT Configuration           Service is not enabled.n         Service is stopped.   1                 FTP CLIENT configuration options:o  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/IPGE               Services software has already been started, so you have_G               the choice of starting the client as well as enabling it._H               If you choose option 1, the FTP service is enabled and FTPE               starts the next time TCP/IP Services is started. If you E               choose option 2, the FTP service is started immediately A               and then every time the TCP/IP Services is started.l  E               If the TCP/IP Services software is not already started,oE               then the FTP Client Components Configuration menu gives F               you only the option of enabling the component, as in the                following example:  7                         1 - Enable service on this nodeu  :                        [E] - Exit FTP_CLIENT configuration  C               After you configure the client component environment,tE               press Return or choose option E to exit from the ClientsB               Components menu. If you chose option A from the MainE               Configuration menu to configure all the TCP/IP ServicesvB               components, the Server Components Configuration menuD               displays next; otherwise, the procedure returns to the*               the Main Configuration menu.  (         3-14 Configuring TCP/IP Services           H                                              Configuring TCP/IP ServicesH                                                 3.3 Running TCPIP$CONFIG  0         3.3.6 Configuring the Server Environment  B               To display the Server Components Configuration menu,?               choose option 3 (Server components) from the Main)E               Configuration menu. If you chose option A from the Main E               Configuration menu to configure all the TCP/IP Services B               components, the Server Components Configuration menuE               displays automatically after you finish configuring the                 client components.  O         Compaq TCP/IP Services for OpenVMS Server Components Configuration Menu   P           1 - BIND         Enabled  Started    12 - NTP         Enabled  StartedP           2 - BOOTP        Disabled Stopped    13 - PC-NFS      Enabled  StartedP           3 - DHCP         Enabled  Started    14 - POP         Enabled  StartedP           4 - FINGER       Enabled  Started    15 - PORTMAPPER  Enabled  StartedP           5 - FTP          Enabled  Started    16 - RLOGIN      Enabled  StartedP           6 - IMAP         Disabled Stopped    17 - RMT         Disabled StoppedP           7 - LBROKER      Disabled Stopped    18 - SNMP        Enabled  StoppedP           8 - LPR/LPD      Disabled Stopped    19 - TELNET      Enabled  StartedP           9 - METRIC       Enabled  Started    20 - TFTP        Enabled  StartedP          10 - NFS          Enabled  Started    21 - XDM         Enabled  Started+          11 - LOCKD/STATD  Disabled Stoppedt  (           A  -  Configure options 1 - 21          [E] -  Exit menut  #         Enter configuration option:l  C               Components are enabled if they have been added to theCO               TCP/IP Services configuration database (TCPIP$CONFIGURATION.DAT),l@               and they are started the next time TCP/IP ServicesA               is started. You can also start (or stop) a specificoF               component, without having to restart TCP/IP Services, byG               choosing the "Start service" option from that component's B               configuration menu. In addition, you can use commandB               procedures to start or stop a specific component, as*               explained in Section 3.10.3.  E               The initial status of the components depends on whetheryC               you have other TCP/IP Services installations in placenC               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 not  H                                         Configuring TCP/IP Services 3-15 u         #         Configuring TCP/IP Services           3.3 Running TCPIP$CONFIG  G               plan to use. You can choose 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 youC               configure the server component you are prompted about F               whether to configure the corresponding client component.  F                 ________________________Note  ________________________  C                 TELNET and RLOGIN are enabled from the client menu.tC                 If you want to disable the TELNET or RLOGIN server,l?                 then you must disable the service. To enable orsC                 disable the TELNET server or the RLOGIN server, usee@                 the Client Components Configuration menu, choose@                 the appropriate client, and disable and stop theB                 service by choosing the "Disable & Stop service on"                 this node" option.  E                 _____________________________________________________a  H               The following is an example of an XDM server configurationA               output. The configuration displays for other servern$               components might vary.  5               Enter configuration option: 21 <Return>o                 XDM Configurations  /               Service is defined in the SYSUAF.nC               Service is not defined in the TCPIP$SERVICE database. %               Service is not enabled.e!               Service is stopped.r  )                XDM configuration options:e  0                  1 - Enable service on this node  ,                 [E] - Exit XDM configuration  )               Enter configuration option:   F                 ________________________Note  ________________________  C                 XDM requires the following DECwindows components to0                 be installed:S  6                 o  SYS$COMMON:[SYSLIB]DECW$XLIBSHR.EXE  (         3-16 Configuring TCP/IP Services t  s      H                                              Configuring TCP/IP ServicesH                                                 3.3 Running TCPIP$CONFIG  9                 o  SYS$COMMON:[SYSLIB]DECW$XTLIBSHRR5.EXE   D                 o  SYS$COMMON:[SYSLIB]DECW$TRANSPORT_COMMON.EXE (VAX                    only)  ?                 The TCPIP$CONFIG procedure checks whether theseu@                 components are installed. If they are not found,B                 TCPIP$CONFIG notifies you and gives you the option@                 of configuring XDM and installing the DECwindowsD                 components later before you attempt to activate XDM.;                 The notification and prompt are as follows:e  J                 XDM requires DECwindows components that are not installed.3                 Attempts to activate XDM will fail.m  N                 Type C to continue with XDM configuration, or E to exit [ E ]:  E                 _____________________________________________________   E               After you configure the server components, press ReturneC               or choose option E to exit from the Server ComponentsnE               Configuration menu. If you chose option A from the Main E               Configuration menu to configure all the TCP/IP ServiceswD               components, the Optional Components Configuration menuD               displays next; otherwise, the procedure returns to the&               Main Configuration menu.  1         3.3.7 Configuring the Optional Componentsh  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 C                  Advanced Server for OpenVMS, or DECnet over TCP/IPt                  software.  B               o  Run or develop applications that use the StanfordG                  Research Institute's (SRI) QIO application programmingy!                  interface (API).   ,               o  Allow Anonymous FTP access.  B               o  Initialize Kerberos authentication for the TELNET                  server.  H                                         Configuring TCP/IP Services 3-17           #         Configuring TCP/IP Servicesn          3.3 Running TCPIP$CONFIG  D               To display the Optional Components Configuration menu,A               choose option 4 (Optional components) from the MaintE               Configuration menu. If you chose option A from the Main0E               Configuration menu to configure all the TCP/IP Services D               components, the Optional Components Configuration menuE               displays automatically after you finish configuring theD                server components.  E               The Optional Components Configuration menu displays the %               following menu options:l  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)o@                 3 - Set up Anonymous FTP Account and Directories3                 4 - Configure Kerberos Applicationse  +                 A - Configure options 1 - 3                 [E] - Exit menu  #         Enter configuration option:w  F               Choose the options that are appropriate for your system:C               the PWIP Driver, the SRI QIO Interface, Anonymous FTPmF               Accounts and Directories, or Kerberos authentication for               TELNET.n  C               o  If you want to run PATHWORKS for OpenVMS (Advanced E                  Server), Advanced Server for OpenVMS, or DECnet overoH                  TCP/IP, configure the PWIP driver by choosing option 1.H                  In addition, refer to the appropriate documentation for%                  the layered product.   H               o  If you run or develop applications that use the SRI QIO&                  API, choose option 2.  B               o  If you want to allow Anonymous FTP access, choose@                  option 3 to set up an Anonymous FTP account and@                  directories. Make sure you obtain the necessaryD                  user information code (UIC) (see Section 1.2.8) and1                  determine guest user privileges.   (         3-18 Configuring TCP/IP Services P  r      H                                              Configuring TCP/IP ServicesH                                                 3.3 Running TCPIP$CONFIG  @               o  If you want to provide the security benefits ofF                  Kerberos authentication for the TELNET server, chooseB                  option 4 to configure Kerberos. For details aboutC                  configuring Kerberos support, see Section 3.3.7.1.m  H               The following example shows the output for 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.   P          TCPIP Transport for DECnet and Pathworks Service configuration options:  ,             1 - Disable service on this node  /            [E] - Exit PWIP_DRIVER configurationf  #         Enter configuration option:a  9         3.3.7.1 Configuring and Enabling Kerberos Support   B               To configure the TELNET service to support Kerberos,A               follow these steps. For more details about Kerberos D               features, including prerequisites and instructions forH               using Kerberos, see the Compaq TCP/IP Services for OpenVMS               Release Notes.  F                 ________________________Note  ________________________  C                 Before you begin the following steps, make sure thei*                 TELNET service is stopped.  E                 _____________________________________________________   K               1. From the the TCPIP$CONFIG.COM procedure Main Configurationn;                  menu, choose option 2 (Client components).   D               2. From the list of client components, choose option 6                  (TELNET).  D               3. From the TELNET Configuration menu, choose option 1E                  (Enable service on all nodes). This step creates the 9                  TCPIP$TELNET user account and directory.E  7               4. Return to the Main Configuration menu.n  H                                         Configuring TCP/IP Services 3-19    m    #         Configuring TCP/IP Servicesn          3.3 Running TCPIP$CONFIG  B               5. From the Main Configuration menu, choose option 4'                  (Optional components).l  A               6. From the Optional Components Configuration menu, C                  choose option 4 (Configure Kerberos Applications). 1                  The following menu is displayed:C  9                  Kerberos Applications Configuration Menu   N                  TELNET Kerberos is not defined in the TCPIP$SERVICE database.  -                        Configuration options:g  C                                1  -  Add Kerberos for TELNET servervF                                2  -  Remove Kerberos for TELNET server  .                               [E] -  Exit menu  ,                  Enter configuration option:  C               7. From the Kerberos Applications Configuration menu,hB                  choose option 1 (Add Kerberos for TELNET Server).  ,               8. Exit the command procedure.  C               9. When you are prompted to start the TELNET service,                   enter N.d  A              10. Start the TELNET service by executing the TELNETdF                  startup procedure, as shown in the following example:  8                  $ @SYS$STARTUP:TCPIP$TELNET_STARTUP.COMI                  %TCPIP-I-INFO, image SYS$SYSTEM:TCPIP$TELNET_SERVER.EXE a                  installedK                  %TCPIP-I-INFO, image SYS$SYSTEM:TCPIP$TELNET.EXE installed 5                  %TCPIP-I-INFO, logical names createdt6                  %TCPIP-I-INFO, telnet service enabledA                  %TCPIP-I-INFO, telnet (kerberos) service enabled C                  %TCPIP-S-STARTDONE, TCPIP$TELNET startup completed   A                  The information message confirms that the TELNET 3                  Kerberos service has been enabled.e        (         3-20 Configuring TCP/IP Services e  o      H                                              Configuring TCP/IP ServicesH      3.4 Using TCPIP$CONFIG Option Commands to Bypass TCPIP$CONFIG Menus  E         3.4 Using TCPIP$CONFIG Option Commands to Bypass TCPIP$CONFIG              Menus   A               If you are an experienced TCP/IP Services user, youeE               may want to bypass the configuration menus to enable ord0               disable functionality, as follows:  .               1. Log in to the SYSTEM account.  C               2. Run the TCPIP$CONFIG command procedure and includeyF                  appropriate options and keywords in the command line,                  as shown:  P                  @SYS$MANAGER:TCPIP$CONFIG [option] {DISABLE | ENABLE} [CLUSTER]  A                  In this format, option can be one of the optionspA                  described in the following table. The table alsocC                  describes the function of the DISABLE, ENABLE, andw"                  CLUSTER keywords.  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, InternetE                                interfaces, Rlogin client, FTP client,pD                                FTP server, TELNET client, and TELNET?                                server. Prompts you for optionalt*                                components.  C                  SERVER        Configures all server components and 0                                related software.  H                  WORKSTATION   Configures the BIND resolver, the domain,D                                dynamic routing, Internet interfaces,E                                time zone, remote login, remote shell,yH                                remote executive, FTP client, FTP server,F                                TELNET client, TELNET server, and SMTP.    H                                         Configuring TCP/IP Services 3-21 s  i      #         Configuring TCP/IP Services[K         3.4 Using TCPIP$CONFIG Option Commands to Bypass TCPIP$CONFIG Menusl  H                  _______________________________________________________H                  Keyword_______Description______________________________  B                  CLUSTER       Configures all specified componentsF                                clusterwide (except for the BIND serverC                                and SMTP, which you cannot configurer,                                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 enabling B                 and disabling: clusterwide and single node (exceptA                 for SMTP, which is configured and enabled as nodeu                 specific only).c  E                 _____________________________________________________   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. Do E               this before you run tests or customize the environment. F               Start TCP/IP Services from TCPIP$CONFIG by following the1               procedure described in Section 3.7.   D               If you made changes to the client, server, or optionalE               components only (that is, not to the core environment),bG               you do not have to restart TCP/IP Services; to initialize B               the changes, you can restart the affected componentsH               individually by choosing the "Start service" option in theE               affected component's configuration menu. Alternatively,SH               you can use each component's startup command procedure, as*               described in Section 3.10.3.  ?               You can have the TCP/IP Services software startedpE               automatically each time the OpenVMS operating system isPD               rebooted, or you can restart the software manually, as(               explained in Section 3.10.  (         3-22 Configuring TCP/IP Services a  l      H                                              Configuring TCP/IP ServicesH                          3.6 Stopping TCP/IP Services Using TCPIP$CONFIG  7         3.6 Stopping TCP/IP Services Using TCPIP$CONFIGn  D               Stop TCP/IP Services on your system by choosing optionF               5 (Shutdown Compaq TCP/IP Services for OpenVMS) from theC               Main Configuration menu, as in the following example:e  =         Compaq TCP/IP Services for OpenVMS Configuration Menu   "             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 OpenVMS "                    7  -  Run tests  0                    A  -  Configure options 1 - 45                   [E] -  Exit configuration procedureo  %         Enter configuration option: 5m         Begin Shutdown...o  H         %TCPIP-I-INFO, TCP/IP Services shutdown beginning at  5-MAR-2002         15:26:14.39r:         %TCPIP-S-SHUTDONE, TCPIP$FINGER shutdown completed>         %TCPIP-S-SHUTDONE, TCPIP$FTP_CLIENT shutdown completed7         %TCPIP-S-SHUTDONE, TCPIP$FTP shutdown completed 8         %TCPIP-S-SHUTDONE, TCPIP$IMAP shutdown completed;         %TCPIP-S-SHUTDONE, TCPIP$LBROKER shutdown completedn9         %TCPIP-S-SHUTDONE, TCPIP$LOCKD shutdown completed >         %TCPIP-S-SHUTDONE, TCPIP$LPD_CLIENT shutdown completed7         %TCPIP-S-SHUTDONE, TCPIP$LPD shutdown completeds:         %TCPIP-S-SHUTDONE, TCPIP$METRIC shutdown completed>         %TCPIP-S-SHUTDONE, TCPIP$NFS_CLIENT shutdown completed7         %TCPIP-S-SHUTDONE, TCPIP$NFS shutdown completed 7         %TCPIP-S-SHUTDONE, TCPIP$NTP shutdown completed 9         %TCPIP-S-SHUTDONE, TCPIP$PCNFS shutdown completed_7         %TCPIP-S-SHUTDONE, TCPIP$POP shutdown completed >         %TCPIP-S-SHUTDONE, TCPIP$PORTMAPPER shutdown completed9         %TCPIP-S-SHUTDONE, TCPIP$PROXY shutdown completedr?         %TCPIP-S-SHUTDONE, TCPIP$PWIP_DRIVER shutdown completed 9         %TCPIP-S-SHUTDONE, TCPIP$REXEC shutdown completedf:         %TCPIP-S-SHUTDONE, TCPIP$RLOGIN shutdown completed7         %TCPIP-S-SHUTDONE, TCPIP$RMT shutdown completedV  H                                         Configuring TCP/IP Services 3-23 s  o      #         Configuring TCP/IP Serviceso7         3.6 Stopping TCP/IP Services Using TCPIP$CONFIGo  7         %TCPIP-S-SHUTDONE, TCPIP$RSH shutdown completed 8         %TCPIP-S-SHUTDONE, TCPIP$SMTP shutdown completed8         %TCPIP-S-SHUTDONE, TCPIP$SNMP shutdown completed9         %TCPIP-S-SHUTDONE, TCPIP$STATD shutdown completedn=         %TCPIP-S-SHUTDONE, TCPIP$TELNETSYM shutdown completedS:         %TCPIP-S-SHUTDONE, TCPIP$TELNET shutdown completed8         %TCPIP-S-SHUTDONE, TCPIP$TFTP shutdown completed7         %TCPIP-S-SHUTDONE, TCPIP$XDM shutdown completed ;         %TCPIP-S-SHUTDONE, TCP/IP Kernel shutdown completedGL         %TCPIP-S-SHUTDONE, TCP/IP Services shutdown completed at  5-MAR-2002         15:26:17.78S  #         Shutdown request completed.   7         3.7 Starting TCP/IP Services Using TCPIP$CONFIGo  B               After configuring the core environment, start TCP/IPC               Services on your system by choosing option 6 (Startupn?               Compaq TCP/IP Services for OpenVMS) from the Mains>               Configuration menu, as in the following example:  =         Compaq TCP/IP Services for OpenVMS Configuration Menud  "             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 procedureo                    (         3-24 Configuring TCP/IP Services o  g      H                                              Configuring TCP/IP ServicesH                          3.7 Starting TCP/IP Services Using TCPIP$CONFIG  %         Enter configuration option: 6u         Begin Startup...  F         %TCPIP-I-INFO, TCP/IP Services startup beginning at 5-MAR-2002         15:27:08.34o6         %TCPIP-I-NORMAL, timezone information verifiedE         %RUN-S-PROC_ID, identification of created process is 00000D42S;         %TCPIP-I-SETLOCAL, setting domain and/or local hostr2         %TCPIP-I-STARTCOMM, starting communication6         %TCPIP-I-SETPROTP, setting protocol parameters-         %TCPIP-I-DEFINTE, defining interfacesc1         %TCPIP-I-STARTNAME, starting name service ;         %TCPIP-S-STARTDONE, TCP/IP Kernel startup completedo8         %TCPIP-I-PROXYLOADED, loaded 0 NFS proxy recordsA         %TCPIP-I-LOADSERV, loading TCPIP server proxy information I         %TCPIP-I-SERVLOADED, auxiliary server loaded with 0 proxy records @         -TCPIP-I-SERVSKIP, skipped 0 communication proxy records9         -TCPIP-I-SERVTOTAL, total of 0 proxy records reads9         %TCPIP-S-STARTDONE, TCPIP$PROXY startup completeda>         %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 completed8         %TCPIP-S-STARTDONE, TCPIP$IMAP startup completed;         %TCPIP-S-STARTDONE, TCPIP$LBROKER startup completed 9         %TCPIP-S-STARTDONE, TCPIP$LOCKD startup completed 7         %TCPIP-S-STARTDONE, TCPIP$LPD startup completedP>         %TCPIP-S-STARTDONE, TCPIP$LPD_CLIENT startup completed:         %TCPIP-S-STARTDONE, TCPIP$METRIC startup completed7         %TCPIP-S-STARTDONE, TCPIP$NFS startup completedS>         %TCPIP-S-STARTDONE, TCPIP$NFS_CLIENT startup completed7         %TCPIP-S-STARTDONE, TCPIP$NTP startup completedD9         %TCPIP-S-STARTDONE, TCPIP$PCNFS startup completedi7         %TCPIP-S-STARTDONE, TCPIP$POP startup completed E         %RUN-S-PROC_ID, identification of created process is 00000C4E ?         %TCPIP-S-STARTDONE, TCPIP$PWIP_DRIVER startup completede9         %TCPIP-S-STARTDONE, TCPIP$REXEC startup completedn:         %TCPIP-S-STARTDONE, TCPIP$RLOGIN startup completed7         %TCPIP-S-STARTDONE, TCPIP$RMT startup completed 7         %TCPIP-S-STARTDONE, TCPIP$RSH startup completedn8         %TCPIP-S-STARTDONE, TCPIP$SMTP startup completed8         %TCPIP-S-STARTDONE, TCPIP$SNMP startup completed9         %TCPIP-S-STARTDONE, TCPIP$STATD startup completedi    H                                         Configuring TCP/IP Services 3-25 o  t      #         Configuring TCP/IP Servicesp7         3.7 Starting TCP/IP Services Using TCPIP$CONFIG   :         %TCPIP-S-STARTDONE, TCPIP$TELNET startup completed=         %TCPIP-S-STARTDONE, TCPIP$TELNETSYM startup completedn8         %TCPIP-S-STARTDONE, TCPIP$TFTP startup completed7         %TCPIP-S-STARTDONE, TCPIP$XDM startup completed K         %TCPIP-S-STARTDONE, TCP/IP Services startup completed at 5-MAR-2002e         15:27:50.47 "         Startup request completed.$         Press Return to continue ...    '         3.8 Verifying the ConfigurationI  G               You can verify the configuration by running the installa-I0               tion verification procedure (IVP).  C               You should run the IVP if any of the following apply:r  H               o  You loaded the Product Authorization Key (PAK), and youE                  want to verify that the lower-layer software and theS<                  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.l  C               o  You require the software to transfer device socketaH                  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 ito4                  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 hasnC               started and you have SYSPRV, OPER, NETMBX, and TMPMBXe               privileges.s  E               You can run the IVP from the TCPIP$CONFIG configuration_E               procedure or by command line at the OpenVMS DCL prompt.uB               When you run the IVP from TCPIP$CONFIG, you have theD               option of running an additional test that verifies the!               SNMP configuration.   (         3-26 Configuring TCP/IP Services M         H                                              Configuring TCP/IP ServicesH                                          3.8 Verifying the Configuration  E         3.8.1 Running the IVP from the TCPIP$CONFIG Command Procedurem  C               In the TCP/IP Services for OpenVMS Main ConfigurationhG               menu, choose option 7 (Run tests). The Test menu appears,c*               as in the following example:  4         Compaq TCP/IP Services for OpenVMS TEST Menu                   Test options:i  +                          1  -  Internet IVPP'                          2  -  SNMP IVPF  *                          A  -  Tests 1 - 2(                         [E] -  Exit menu           Enter test option:  D               Choose the appropriate option for the test you want to               perform.  9         3.8.2 Running the IVP from the OpenVMS DCL Prompte  F               To run the IVP at the DCL prompt, any time after exitingG               the configuration procedure, enter the following command.t?               This procedure performs the same test as option 1n;               (Internet IVP) of the TCPIP$CONFIG Test menu.o  #               $ @SYS$TEST:TCPIP$IVP   B         3.8.3 Verifying the TCP/IP Services Internet Configuration  B               When you choose either option 1 or option A from theB               TCPIP$CONFIG Test menu, or run the TCPIP$IVP commandD               procedure at the command line, the IVP tests the basic?               TCP/IP Services software configuration, as in the G               following example. Here, the test completes successfully.   %         Enter test option: 1 <Return>S  "         %%% TCPIP IVP: started %%%  5         UDP/IP test started at 5-MAR-2002 16:13:03.02i3         UDP/IP test ended at 5-MAR-2002 16:13:03.69TB         UDP/IP transferred successfully in 0 seconds 4198400 bytes  5         TCP/IP test started at 5-MAR-2002 16:13:04.20i3         TCP/IP test ended at 5-MAR-2002 16:13:41.21YC         TCP/IP transferred successfully in 37 seconds 4198400 bytesi  H                                         Configuring TCP/IP Services 3-27           #         Configuring TCP/IP Servicese'         3.8 Verifying the Configuration-  5         RAW_IP test started at 5-MAR-2002 16:13:41.71 3         RAW_IP test ended at 5-MAR-2002 16:13:41.79 A         RAW_IP transferred successfully in 0 seconds 251000 bytes   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:i  3               %TCPIP-E-IDENT, explanation of error.t  G               Table 3-2 lists some common problems that cause IVP errorcF               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.)G                                       Then shut down and restart TCP/IP /                                       Services.e  @               Installation kit is     Request a replacement kit.               defective.  G               IVP fails because the   Register a Compaq TCP/IP Services H               PAK_is_missing._________for_OpenVMS_PAK.__________________  .         3.8.4 Verifying the SNMP Configuration  @               If you choose either option 2 or option A from theH               TCPIP$CONFIG Test menu, the IVP tests the SNMP service, as'               in the following example:       (         3-28 Configuring TCP/IP Services    S      H                                              Configuring TCP/IP ServicesH                                          3.8 Verifying the Configuration                 Begin SNMP IVP...   F               The SNMP IVP requires that TCPIP/IP Services be running.E               It performs the following startups and shutdowns on the I               SNMP service only (other TCP/IP services are not affected):   B               - If SNMP is running, shuts down SNMP before initial                 configurationf*               - Starts SNMP and runs testsB               - Shuts down SNMP and restores initial configuration+               - Before exiting, starts SNMPl  5               Shutting down the SNMP service... done._  C               Creating temporary read/write community SNMPIVP_6520._  &               Enabling SET operations.  3               Starting up the SNMP service... done.   5                     Saving sysContact: Ralph Nickleby 4                 Setting sysContact to: Julius Caesar4                  Retrieved sysContact: Julius Caesar2               (Retrieved value matches SET value.)5               Restoring sysContact to: Ralph NicklebyB  ;                   Saving snmpEnableAuthenTraps: 1 (enabled) <               Setting snmpEnableAuthenTraps to: 2 (disabled)<                Retrieved snmpEnableAuthenTraps: 2 (disabled)2               (Retrieved value matches SET value.);                Restoring snmpEnableAuthenTraps: 1 (enabled)_  '               Disabling SET operations.   C               Deleting temporary read/write community SNMPIVP_6520.l  >               Shutting down and restarting the SNMP service...5               Shutting down the SNMP service... done.   3               Starting up the SNMP service... done._  )               SNMP IVP request completed. *               Press Return to continue ...    H                                         Configuring TCP/IP Services 3-29           #         Configuring TCP/IP Servicese'         3.8 Verifying the ConfigurationP  H               If one of the SNMP tests fails, you will see messages such               as the following:r  =         SNMPIVP: unexpected text in response to SNMP request:y         "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 = 0 4         The SNMP IVP has NOT completed successfully.  A               In this case, the error could indicate that not alloC               SNMP components have started, or that SNMP tracing isoE               enabled and needs to be disabled. For information abouttD               SNMP trace, see the Compaq TCP/IP Services for OpenVMS               Management guide.e  *         3.9 Additional Configuration Tasks  E               After you run TCPIP$CONFIG and enable the functionalityaC               and components appropriate for your network, you needdB               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.O  9               The additional configuration tasks include:I  F               o  Populating databases (for example, for BIND and DHCP)  )               o  Setting up user accountsv  9               o  Setting up communication and NFS proxiesm  &               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 orG               optimization. For more information about how to configure C               each service, refer to the Compaq TCP/IP Services for '               OpenVMS Management guide.P  (         3-30 Configuring TCP/IP Services    n      H                                              Configuring TCP/IP ServicesH                    3.10 Starting and Stopping TCP/IP Services by Command  =         3.10 Starting and Stopping TCP/IP Services by Commande  G               You can use commands in your OpenVMS startup file to havePH               TCP/IP Services started and stopped automatically when theE               OpenVMS system starts up or shuts down, as explained inFC               Section 3.10.1. These commands start and stop all thenB               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 affectingA               other TCP/IP Services components currently running.DD               For information about starting and stopping individual-               components, see Section 3.10.3.S  B               If necessary, you can start and stop TCP/IP ServicesD               manually, as explained in Section 3.10.2. You can alsoC               start and stop user-written services, as explained inp               Section 3.10.4.N  B         3.10.1 Automatically Starting and Stopping TCP/IP Services  >               To allow TCP/IP Services software to start auto->               matically when the system starts up, and to stop@               automatically when the system shuts down, edit theC               SYS$COMMON:[SYSMGR]SYSTARTUP_VMS.COM file and includep$               the following command:  (               @SYS$STARTUP:TCPIP$STARTUP  E               If your system had earlier versions of TCP/IP Services,gA               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               If you want TCP/IP Services to start after you log in C               to your OpenVMS account, the OpenVMS systemwide loginTE               procedure (typically SYS$MANAGER:SYLOGIN.COM) must haveD8               world read and execute protections (W:RE).  E               To display the current protections, enter the followingn               command:  6               $ DIR/PROTECTION SYS$MANAGER:SYLOGIN.COM  E               For information about protections, refer to the OpenVMSl               documentation.  H                                         Configuring TCP/IP Services 3-31 e  v      #         Configuring TCP/IP Servicesc=         3.10 Starting and Stopping TCP/IP Services by Command   =         3.10.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 following                command:  +               $ @SYS$STARTUP:TCPIP$SHUTDOWNs  8         3.10.3 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. H               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.T  E               o  SYS$STARTUP:TCPIP$service_SHUTDOWN.COM allows you ton/                  shut down the service service.   >               To preserve site-specific parameter settings andC               commands, create the following files. These files aresA               not overwritten when you reinstall TCP/IP Services:r  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 usedlB                  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 servicerE               to be started or shut down. For example, use TCPIP$NTP_m4               SHUTDOWN to shut down the NTP service.  F               For more information, see the Compaq TCP/IP Services for'               OpenVMS Management guide.T  (         3-32 Configuring TCP/IP Services    I      H                                              Configuring TCP/IP ServicesH                    3.10 Starting and Stopping TCP/IP Services by Command  :         3.10.4 Starting and Stopping User-Written Services  F               TCP/IP Services supplies command procedures for startingB               and stopping user-written services. To start a user-;               written service, enter the following command:I  G               $ SYS$STARTUP:TCPIP$CUSTOMER_SERVICE_STARTUP service-nameu  B               For service-name, specify the name of the service asF               defined using the TCP/IP management command SET SERVICE.  C               To stop the user-written service, enter the followingT               command:  H               $ SYS$STARTUP:TCPIP$CUSTOMER_SERVICE_SHUTDOWN service-name  G         3.11 Specifying TCP/IP Services as the Transport for DECwindows               Applications   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 command                procedure:  >               $ DECW$SERVER_TRANSPORTS == "DECNET,LOCAL,TCPIP"  &               Then restart DECwindows:  1               $ @SYS$STARTUP:DECW$STARTUP RESTART   C               If DECnet or DECnet-Plus software runs on the system,S               start it.s  B               To display DECwindows applications from a DECwindows?               client (remote host) to a DECwindows server (yourt/               workstation), proceed as follows:   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 the                    following line:  A                  $ DECW$SERVER_TRANSPORTS == "DECNET,LOCAL,TCPIP"I  C               4. Set the display for the applications to the remote                   host:  F                  $ SET DISPLAY/CREATE/NODE=remote-host/TRANSPORT=TCPIP  H                                         Configuring TCP/IP Services 3-33 y  s              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 Procedureu  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 not C               been installed. If TCP/IP Services had been installed E               previously on the system, the installation dialog wouldN.               differ slightly (see Chapter 2).  F                 ________________________Note  ________________________  A                 The symbols xx in the following example representu>                 the product's two-digit update version number.  E                 _____________________________________________________e  E         Choose one or more items from the menu separated by commas: 1e  0         The following product has been selected:B             DEC VAXVMS TCPIP V5.3-xx               Layered Product  /         Do you want to continue? [YES] <Return>   (         Configuration phase starting ...  O         You will be asked to choose options, if any, for each selected product           and for J         any products that may be installed to satisfy software dependency          requirements.l  E         DEC VAXVMS TCPIP V5.3-xx: Compaq TCP/IP Services for OpenVMS.   E             Copyright 2002 Compaq Information Technologies Group, L.P   '             Compaq Computer CorporationV  H            Sample New TCP/IP Services Installation and Configuration A-1    i      A         Sample New TCP/IP Services Installation and Configurationa-         A.1 Sample New Installation Procedure   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 ...  ?         The following product will be installed to destination:oP             DEC VAXVMS TCPIP V5.3-xx               DISK$OVMSVAXSYS:[VMS$COMMON.]  N         Portion done: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%=         %PCSI-I-PRCOUTPUT, output from subprocess follows ...C         % TCPIP-W-PCSI_INSTALLO         % - Execute SYS$MANAGER:TCPIP$CONFIG.COM to proceed with configuration e
         of#         %   Compaq TCP/IP Services.n	         %            Portion done: 100%  1         The following product has been installed: B             DEC VAXVMS TCPIP V5.3-xx               Layered Product  E         DEC VAXVMS TCPIP T5.3-xx: 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 dialognH               for the TCP/IP Services, in which the following components               are configured:   !               o  Core environment                  o  TELNET client                 o  FTP servern  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).    E         A-2 Sample New TCP/IP Services Installation and Configuration.           H                Sample New TCP/IP Services Installation and ConfigurationH                                   A.2 Sample New Configuration Procedure  0           TCP/IP Network Configuration Procedure  ?         This procedure helps you define the parameters required A         to run Compaq TCP/IP Services for OpenVMS on this system.   J         Checking TCP/IP Services for OpenVMS configuration database files.  5         Creating SYS$COMMON:[SYSEXE]TCPIP$SERVICE.DAT 2         Creating SYS$COMMON:[SYSEXE]TCPIP$HOST.DAT5         Creating SYS$COMMON:[SYSEXE]TCPIP$NETWORK.DAT_3         Creating SYS$COMMON:[SYSEXE]TCPIP$ROUTE.DAT 3         Creating SYS$COMMON:[SYSEXE]TCPIP$PROXY.DATn;         Creating SYS$COMMON:[SYSEXE]TCPIP$CONFIGURATION.DATt+         Creating TCPIP$ETC:SYSCONFIGTAB.DAT.  G         Compaq TCP/IP Services for OpenVMS requires a definition for at E         least one interface.  There are no interfaces defined on this          system.s  J         Please select the Interface option from the Core Environment Menu.  ?           Compaq TCP/IP Services for OpenVMS Configuration Menuc              Configuration options:  %                1  -  Core environment &                2  -  Client components&                3  -  Server components(                4  -  Optional components  @                5  -  Shutdown Compaq TCP/IP Services for OpenVMS?                6  -  Startup Compaq TCP/IP Services for OpenVMSh                7  -  Run tests  ,                A  -  Configure options 1 - 41               [E] -  Exit configuration procedurel  .         Enter configuration option: 1 <Return>  P           Compaq TCP/IP Services for OpenVMS Core Environment Configuration Menu              Configuration options:                  1  -  Domainr                2  -  Interfaces                 3  -  Routing"                4  -  BIND Resolver                5  -  Time Zone  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  ,                A  -  Configure options 1 - 5               [E] -  Exit menu  .         Enter configuration option: A <Return>           DOMAIN Configuration  .         Enter Internet domain: budget.acme.com           INTERFACE Configurationr  N           The Ethernet device(s) on your system are: EWA0:  * Not Configured *  F           Start of configuration questions for Internet interface WE0.  *           WE0 is the Ethernet device ESA0:  %           WE0 has not been configured   M           Compaq TCP/IP Services for OpenVMS Interface WE0 Configuration Menus  "             Configuration options:  3                  1  -  Configure interface manuallye3                  2  -  Let DHCP configure interface   A                 [E] -  Exit menu (Do not configure interface WE0)n  .         Enter configuration option: 1 <Return>H         Enter fully qualified host name: HEARTS.BUDGET.ACME.COM <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 WE0:P  7               Host name:         hearts.budget.acme.comr)               Internet address:  10.0.2.4q*               Network mask:      255.0.0.0+               Broadcast mask:    10.0.2.255   /          * Is the above correct [YES]: <Return>   E             End of configuration questions for Internet interface WE0h  %         DYNAMIC ROUTING Configurationo  5              Dynamic routing has not been configured.   E         A-4 Sample New TCP/IP Services Installation and Configuratione    P      H                Sample New TCP/IP Services Installation and ConfigurationH                                   A.2 Sample New Configuration Procedure  ?              You may configure dynamic ROUTED or GATED routing.aB              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.  I              If you enable dynamic ROUTED routing, this host will use the E              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.n  E              If you enable dynamic GATED routing, you will be able totH              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)C/                 Open Shortest Path First (OSPF) /                 Exterior Gateway Protocol (EGP)F/                 Border Gateway Protocol (BGP-4)u                 Static routesu  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.66   #         BIND RESOLVER Configurationi  1          A BIND resolver has not been configured.a  O          Compaq TCP/IP Services for OpenVMS supports the Berkeley Internet Name P          Domain (BIND) resolver.  BIND is a network service that enables clientsN          to name resources or objects and share information with other objects          on the network.  F          Before configuring your system as a BIND resolver, you shouldG          first be sure that there is at least one system on the networkSD          configured as either a BIND primary or secondary server for          this domain.s  H            Sample New TCP/IP Services Installation and Configuration A-5 o  a      A         Sample New TCP/IP Services Installation and Configurationg.         A.2 Sample New Configuration Procedure  >          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.  8          You will be asked one question for each server.:          Press Return at the prompt to terminate the list.  C         Enter your BIND server name: NUMB9.BUDGET.ACME.COM <Return>p  C            numb9.budget.acme.com is not in the local host database.   C         Enter Internet address for numb9.budget.acme.com: 10.0.2.11t-         Enter your BIND server name: <Return>s  ,          Creating file TCPIP$ETC:IPNODES.DAT-          Creating file TCPIP$ETC:SERVICES.DAT   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.b  L            This section verifies the current OpenVMS timezone configuration.O            A warning message (TCPIP-W-) indicates that corrective action shouldyL            be taken. TCPIP will appear to operate but components may displayP            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) change "         -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 ... <Return>   P           Compaq TCP/IP Services for OpenVMS Core Environment Configuration Menu              Configuration options:                  1  -  DomainP                2  -  Interfaces                 3  -  Routing"                4  -  BIND Resolver                5  -  Time Zone  ,                A  -  Configure options 1 - 5               [E] -  Exit menu  ,         Enter configuration option: <Return>  E         A-6 Sample New TCP/IP Services Installation and Configuration          H                Sample New TCP/IP Services Installation and ConfigurationH                                   A.2 Sample New Configuration Procedure  A             Compaq TCP/IP Services for OpenVMS Configuration Menuc  "             Configuration options:  '                  1  -  Core environmentn(                  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 OpenVMSs                   7  -  Run tests  .                  A  -  Configure options 1 - 43                 [E] -  Exit configuration procedurel  .         Enter configuration option: 2 <Return>  O             Compaq TCP/IP Services for OpenVMS Client Components Configuration               Menu  "             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.          Service is not enabled.          Service is stopped.   )             TELNET configuration options:e  0                  1 - Enable service on this node  /                 [E] - Exit TELNET configuration   .         Enter configuration option: 1 <Return>%         Creating TELNET Service Entry   H            Sample New TCP/IP Services Installation and Configuration A-7    1    A         Sample New TCP/IP Services Installation and Configurationa.         A.2 Sample New Configuration Procedure  O             Compaq TCP/IP Services for OpenVMS Client Components Configuration n             Menu  "             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 Menud  "             Configuration options:  '                  1  -  Core environmentO(                  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 proceduret  .         Enter configuration option: 3 <Return>  O         Compaq TCP/IP Services for OpenVMS Server Components Configuration Menu.  P           1 - BIND         Enabled  Started    12 - NTP         Enabled  StartedP           2 - BOOTP        Disabled Stopped    13 - PC-NFS      Enabled  StartedP           3 - DHCP         Enabled  Started    14 - POP         Enabled  StartedP           4 - FINGER       Enabled  Started    15 - PORTMAPPER  Enabled  StartedP           5 - FTP          Enabled  Started    16 - RLOGIN      Enabled  StartedP           6 - IMAP         Disabled Stopped    17 - RMT         Disabled StoppedP           7 - LBROKER      Disabled Stopped    18 - SNMP        Enabled  StoppedP           8 - LPR/LPD      Disabled Stopped    19 - TELNET      Enabled  StartedP           9 - METRIC       Enabled  Started    20 - TFTP        Enabled  StartedP          10 - NFS          Enabled  Started    21 - XDM         Enabled  Started+          11 - LOCKD/STATD  Disabled Stoppedd  E         A-8 Sample New TCP/IP Services Installation and Configurationl           H                Sample New TCP/IP Services Installation and ConfigurationH                                   A.2 Sample New Configuration Procedure  (           A  -  Configure options 1 - 21          [E] -  Exit menua  .         Enter configuration option: 5 <Return>           FTP Configurationv  )         Service is defined in the SYSUAF.o=         Service is not defined in the TCPIP$SERVICE database.          Service is not enabled..         Service is stopped._  &             FTP configuration options:  0                  1 - Enable service on this node  ,                 [E] - Exit FTP configuration  .         Enter configuration option: 1 <Return>"         Creating FTP Service Entry  "         The FTP CLIENT is enabled.  <         * Do you want to configure FTP CLIENT [NO]: <Return>  O         Compaq TCP/IP Services for OpenVMS Server Components Configuration Menu-  P           1 - BIND         Enabled  Started    12 - NTP         Enabled  StartedP           2 - BOOTP        Disabled Stopped    13 - PC-NFS      Enabled  StartedP           3 - DHCP         Enabled  Started    14 - POP         Enabled  StartedP           4 - FINGER       Enabled  Started    15 - PORTMAPPER  Enabled  StartedP           5 - FTP          Enabled  Started    16 - RLOGIN      Enabled  StartedP           6 - IMAP         Disabled Stopped    17 - RMT         Disabled StoppedP           7 - LBROKER      Disabled Stopped    18 - SNMP        Enabled  StoppedP           8 - LPR/LPD      Disabled Stopped    19 - TELNET      Enabled  StartedP           9 - METRIC       Enabled  Started    20 - TFTP        Enabled  StartedP          10 - NFS          Enabled  Started    21 - XDM         Enabled  Started+          11 - LOCKD/STATD  Disabled StoppedS  (           A  -  Configure options 1 - 21          [E] -  Exit menu   -          Enter configuration option: <Return>   A             Compaq TCP/IP Services for OpenVMS Configuration Menu   "             Configuration options:  H            Sample New TCP/IP Services Installation and Configuration A-9 4  .      A         Sample New TCP/IP Services Installation and Configurationr.         A.2 Sample New Configuration Procedure  '                  1  -  Core environmentO(                  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 procedure   .         Enter configuration option: 6 <Return>           Begin Startup...  O         %TCPIP-I-INFO, TCP/IP Services startup beginning at 5-MAR-2002 13:22:27e         .82hO         %TCPIP-I-INFO, creating UCX compatibility file SYS$COMMON:[SYSEXE]UCX$Sn         ERVICE.DAT6         %TCPIP-I-NORMAL, timezone information verifiedE         %RUN-S-PROC_ID, identification of created process is 00000058y;         %TCPIP-I-SETLOCAL, setting domain and/or local hoste2         %TCPIP-I-STARTCOMM, starting communication6         %TCPIP-I-SETPROTP, setting protocol parameters-         %TCPIP-I-DEFINTE, defining interfaces 1         %TCPIP-I-STARTNAME, starting name serviceo;         %TCPIP-S-STARTDONE, TCP/IP Kernel startup completed 8         %TCPIP-I-PROXYLOADED, loaded 0 NFS proxy recordsA         %TCPIP-I-LOADSERV, loading TCPIP server proxy information I         %TCPIP-I-SERVLOADED, auxiliary server loaded with 0 proxy recordsl@         -TCPIP-I-SERVSKIP, skipped 0 communication proxy records9         -TCPIP-I-SERVTOTAL, total of 0 proxy records readg9         %TCPIP-S-STARTDONE, TCPIP$PROXY startup completed 7         %TCPIP-S-STARTDONE, TCPIP$FTP startup completed :         %TCPIP-S-STARTDONE, TCPIP$TELNET startup completedO         %TCPIP-S-STARTDONE, TCP/IP Services startup completed at 5-MAR-2002 13:X         23:00.49  "         Startup request completed.$         Press Return to continue ...        F         A-10 Sample New TCP/IP Services Installation and Configuration A                             E      ________________________________________________________________e  E                                                                 Index     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-8 to2        configuring, 3-17                      3-12?      Automatic configuration of            description of major/9         TCP/IP Services, 3-2                  tasks,  1-1   B                                            new configuration,  1-1E      B__________________________           optional components,  3-17t  C      BIND resolver                         postconfiguration tasks,o2        configuring, 3-11                      3-30D      BIND server                           server components,  3-15,2        configuring, 3-15                      3-17D      BOOTP server                          server environment,  3-155        configuring, 3-15                      to 3-17   =                                            tasks, recommendedg<      C__________________________              sequence,  3-1  C      CD-ROM distribution kit               TCPIP$CONFIG menus,  3-8e>        inspecting, 1-3                     TCPIP$CONFIG menus,?      Client components                        description,  3-6e>        starting and stopping               TCPIP$CONFIG option=          individually,  3-32                  commands,  3-21 >      Client environment                    time required,  1-2D        configuring, 3-12                   verifying services,  3-26        Configuration worksheet, E         1-9                               D__________________________   <      Configuring TCP/IP Services          DECnet over TCP/IPD        automatic, 3-2                      configuring to use,  3-174        client components, 3-13            DECwindowsB        client environment, 3-12            components required for8          to 3-14                              XDM,  3-16  E                                                               Index-1. .  R            5         DECwindows (cont'd)                 Interface ?          defining TCP transport,              configuring,  3-9.=             3-33                            IVP (InstallationeF          requirements for product              Verification Procedure)@             installation,  1-4                description,  3-26           DHCP clientqG          configuring,  3-12                 K__________________________k  4         DHCP server                         Kerberos=          configuring,  3-15                   benefits,  3-18IG          configuring TCP/IP                   configuring and enabling, 5             Services,  3-2                       3-19 @         Disk                                  optional componentD          space requirements,  1-5                configuration, 3-17C          system, backing up,  1-4           Kerberos authenticationCG         Distribution kit                      configuring and enabling,r5          inspecting,  1-3                        3-19tH         Domain                                configuring to use,  3-17,5          configuring,  3-9                       3-18r         Dynamic routinge-          configuring,  3-10                 LcG                                             ___________________________n:         F__________________________         LBROKER server@         FINGER server                         configuring,  3-15  ;          configuring,  3-15                 License Producta@         FTP client                             Authorization Key  5          configuring,  3-13                   See PAKb>         FTP server                          LOCKD/STATD server@          configuring,  3-15                   configuring,  3-15:                                             LPR/LPD client@         G__________________________           configuring,  3-12:         Global pagelets and                 LPR/LPD server@           sections                            configuring,  3-15  -          increasing,  1-6                   MeG          requirements,  1-6                 ___________________________P2                                             Memory=         I__________________________           physical memorytB         Installing TCP/IP Services,              requirements, 1-51           2-1 to 2-6                        MenusE@          installed files,  2-6                TCPIP$CONFIG,  3-69          major tasks,  1-1                  METRIC serverm@          new installation,  A-2               configuring,  3-15            time required,  1-2           Index-2     I            9                                             PC-NFS serverf@         N__________________________           configuring,  3-15?         NFS client                          POLYCENTER SoftwareDC          configuring,  3-12                    Installation utilitys?         NFS server                            for installing or C          configuring,  3-15                      upgrading (OpenVMSoF         Nonpaged dynamic pool                    VAX or Alpha), 2-1 to4          increasing,  1-6                        2-66         NTP server                          POP server@          configuring,  3-15                   configuring,  3-15=                                             PORTMAPPER serverI@         O__________________________           configuring,  3-15D         OpenVMS License Management          Postconfiguration tasks,3           Facility (LMF)                       3-30e0          using to register PAK,             PWIP@             1-4                               configuring,  3-18D         OpenVMS operating system              requirement, interruptA          reboot,  2-5                            stack pages, 1-7   -          upgrading,  1-4                    RlG         Optional components,                ___________________________c8           configuring                       Reboot,  2-69          Advanced Server for                Release notes D             OpenVMS,  3-18                    extracting into a .TXT:          Anonymous FTP,  3-18                    file, 1-3<          Kerberos authentication,             location afterB             3-18                                 installation, 2-6@          PATHWORKS (Advanced                REXEC and RSH client@             Server),  3-18                    configuring,  3-129          PWIP driver,  3-18                 RLOGIN clientP@          SRI QIO interface,  3-18             configuring,  3-129                                             RLOGIN serveri@         P__________________________           configuring,  3-156         PAK                                 RMT server@          registering,  1-4                    configuring,  3-15  -         PATHWORKS                           S G          configuring,  3-17                 ___________________________t=         PATHWORKS Advanced Server,          Server components C           1-7                                 starting and stoppinggC         PATHWORKS Internet Protocol              individually, 3-32   @           driver                            Shutting down TCP/IP7          See PWIP                              Services   A                                               See Stopping TCP/IP 9                                                  Servicesp  H                                                                  Index-3 g  t            ;         SMTP client                         TCP/IP ServicesaA          configuring,  3-12                   configuration filesC9         SNMP                                     (cont'd)s@          testing,  3-28                          converting from<          verifying the                              previousF             configuration,  3-28                    configuration, 3-4>         SNMP server                           core environmentE          configuring,  3-15                      configuring,  3-8 to 8         SRI QIO                                     3-12G          configuring to use,  3-17            installation,  2-1 to 2-6 :         Starting TCP/IP Services                 new,  A-1E          after configuration,  3-24           preparing to configure,e4          automatically,  3-31                    1-9H          by command,  3-31                    preparing to install,  1-27          manually,  3-32                         to 1-9 ?          using TCPIP$CONFIG,  3-24            server componentsRF         Stopping TCP/IP Services                 configuring,  3-15 to          automatically,  3-31 8          by command,  3-31                          3-17F          manually,  3-32                         starting and stoppingF          using TCPIP$CONFIG,  3-23                  individually, 3-32<         System parameters                     starting afterD          checking and changing                   configuration, 3-22C             before installing,  1-6           starting and stopping D             to 1-7                               automatically, 3-31C          setting the SPTREQ                   starting and stoppingu?             parameter,  1-7                      manually, 3-32o<                                               starting usingC         T__________________________              TCPIP$CONFIG, 3-24e<         Tasks                                 stopping usingC          major, installing and                   TCPIP$CONFIG, 3-23vD             configuring,  1-1                 upgrading,  2-1 to 2-6>         TCP/IP Services                       verifying,  3-26>          and Anonymous FTP access,          TCPIP$CONFIG menus?             3-18                              description,  3-6   B          client components                  TCPIP$CONFIG procedure  D             configuring,  3-12 to             See Configuring TCP/IP9                3-14                              Services 9             starting and stopping           TELNET client @                individually,  3-32            configuring,  3-129          configuration,  3-1 to             TELNET server8@             3-30                              configuring,  3-15               new,  A-2           configuration files           Index-4o g  t            B         TFTP server                           configuring to allowF          configuring,  3-15                      Anonymous FTP access,5         Time zone                                3-17p          configuring,  3-11 G         Troubleshooting                     V__________________________ >          configuration procedure            Verifying the SNMPB             problems,  3-28                    configuration, 3-28  @         U                                   Verifying the TCP/IPF         ___________________________            Services configuration,3         UIC codes                              3-26           assigning,  1-8-         Upgrading TCP/IP Services,          X G           2-1 to 2-6                        ___________________________ 6         User access                         XDM server<                                               and DECwindowsC                                                  requirements, 3-16 @                                               configuring,  3-16                                                      H                                                                  Index-5