           C                      HP_TCP/IP_Services_for_OpenVMS________________ 3                      Installation and Configuration   .                      Order Number: BA548-90005                          July 2006  F                      This manual explains how to install and configureG                      the HP TCP/IP Services for OpenVMS product on your $                      OpenVMS system.          C                      Revision Information:        This guide super- A                                                   sedes HP TCP/IP F                                                   Services for OpenVMSB                                                   Installation and@                                                   Configuration,>                                                   Version 5.5.  D                      Software Version:            HP TCP/IP ServicesE                                                   for OpenVMS Version 5                                                   5.6   E                      Operating Systems:           OpenVMS I64 Version 7                                                   8.2-1 E                                                   OpenVMS I64 Version 5                                                   8.3 G                                                   OpenVMS Alpha Version 5                                                   8.2 G                                                   OpenVMS Alpha Version 5                                                   8.3               ,                      Hewlett-Packard Company*                      Palo Alto, California                 H               __________________________________________________________  H                Copyright 2006 Hewlett-Packard Development Company, L.P.  C               Confidential computer software. Valid license from HP F               required for possession, use or copying. Consistent withB               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               The information contained herein is subject to change A               without notice. The only warranties for HP products @               and services are set forth in the express warrantyA               statements accompanying such products and services. C               Nothing herein should be construed as constituting an G               additional warranty. HP shall not be liable for technical @               or editorial errors or omissions contained herein.  G               Intel and Itanium are trademarks or registered trademarks D               of Intel Corporation or its subsidiaries in the United)               States and other countries.   ?               UNIX is a registered trademark of The Open Group.   H                                                                   ZK6524                 Printed in the US   A               The HP TCP/IP Services for OpenVMS documentation is "               available on CD-ROM.  C               This document was prepared using DECdocument, Version                3.3-1b.                                E      ________________________________________________________________   E                                                              Contents     E      Preface..................................................    vii     :      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-4 =            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-7 E            1.2.8     Assigning a User Identification Code.....    1-7 E            1.2.9     Remove Early Adopters Kits (EAKs)........    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-2H               3.2   Adding a System to an OpenVMS Cluster........    3-4>               3.2.1     Running a Newly Configured Host in theH                         Cluster..................................    3-4A               3.2.2     Configuring TCP/IP Services Before Adding H                         the System to the Cluster................    3-5>               3.3   Automatic Configuration of TCP/IP ServicesH                     Using DHCP Client............................    3-5H               3.4   Running TCPIP$CONFIG.........................    3-8;               3.4.1     Converting Existing TCP/IP Services H                         Configuration Files (Upgrade Only).......    3-84               3.4.2     Creating New TCP/IP ServicesH                         Configuration Files......................   3-10H               3.4.3     Understanding the Configuration Menus....   3-10H               3.4.4     Configuring the Core Environment.........   3-12H               3.4.4.1     Domain Configuration...................   3-145               3.4.4.2     First-time Configuration of H                           Interfaces.............................   3-14H               3.4.4.3     Interface IP Address Configuration.....   3-16H               3.4.4.4     failSAFE IP Address Configuration......   3-19H               3.4.4.5     Dynamic Routing Configuration..........   3-23H               3.4.4.5.1    Default Route Configuration...........   3-25H               3.4.4.6     BIND Resolver Configuration............   3-25H               3.4.4.7     Time Zone Configuration................   3-28H               3.4.5     Configuring the Client Environment.......   3-28H               3.4.6     Configuring the Server Environment.......   3-32H               3.4.7     Configuring the Optional Components......   3-35;               3.4.7.1     Configuring and Enabling Kerberos H                           Support................................   3-37>               3.4.7.2     Configuring and Enabling failSAFE IPH                           Support................................   3-38@               3.5   Using TCPIP$CONFIG Option Commands to BypassH                     TCPIP$CONFIG Menus...........................   3-39H               3.6   Making Configuration Changes Take Effect.....   3-412               3.7   Stopping TCP/IP Services UsingH                     TCPIP$CONFIG.................................   3-422               3.8   Starting TCP/IP Services UsingH                     TCPIP$CONFIG.................................   3-44H               3.9   Verifying the Configuration..................   3-46      
         iv                 =               3.9.1     Running the IVP from the TCPIP$CONFIG H                         Command Procedure........................   3-47<               3.9.2     Running the IVP from the OpenVMS DCLH                         Prompt...................................   3-47>               3.9.3     Verifying the TCP/IP Services InternetH                         Configuration............................   3-47H               3.9.4     Verifying the SNMP Configuration.........   3-49H               3.10  Additional Configuration Tasks...............   3-51H               3.11  Starting and Stopping TCP/IP Services........   3-51;               3.11.1    Automatically Starting and Stopping H                         TCP/IP Services..........................   3-52=               3.11.2    Starting and Stopping TCP/IP Services H                         Manually.................................   3-52A               3.11.3    Starting and Stopping Individual Services H                         .........................................   3-53:               3.11.4    Starting and Stopping User-WrittenH                         Services.................................   3-53?               3.12  Specifying TCP/IP Services as the Transport H                     for DECwindows Applications..................   3-54             4  Configuring IPv6   H               4.1   Configuring an IPv6 Host.....................    4-4H               4.2   Configuring an IPv6 Router...................   4-11H               4.3   Configuring failSAFE IP IPv6 Addresses.......   4-20  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                       H                                                                        v                          Examples  <               2-1       TCP/IP Services Installation: Sample@                         POLYCENTER Software Installation UtilityH                         Procedure................................    2-4           Tables  H               1         TCP/IP Services Documentation............   viii  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-3  H               3-2       Minimum Values for SYSUAF Parameters.....    3-4  9               3-3       Making Configuration Changes Take H                         Effect...................................   3-41  H               3-4       Troubleshooting IVP Errors...............   3-49                                        
         vi                           H         ________________________________________________________________  H                                                                  Preface      B               The HP TCP/IP Services for OpenVMS product is the HPD               implementation of the TCP/IP networking protocol suiteF               and internet services for OpenVMS Alpha and I64 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.   F               This manual explains how to install and configure the HPF               TCP/IP Services for OpenVMS (TCP/IP Services) networkingE               software on an OpenVMS system. This manual reflects the C               installation and configuration procedures for Version G               5.6 of the TCP/IP Services product. For information about F               last-minute changes to these procedures, refer to the HP8               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                                                                      vii                 F               o  Chapter 3 provides guidelines on how to configure the?                  TCP/IP Services components after installation.   G               o  Chapter 4 explains how to configure the IPv6 software.   >               o  Appendix A provides a sample installation andD                  configuration display as might appear on an OpenVMS?                  system upon which TCP/IP Services has not been H                  installed previously. The display 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______________________________  A         Compaq TCP/IP Services    This manual provides conceptual E         for OpenVMS Concepts and  information about TCP/IP networking G         Planning                  on OpenVMS systems, including general D                                   planning issues to consider beforeD                                   configuring your system to use the;                                   TCP/IP Services software.   H                                   This manual also describes the manualsF                                   in the TCP/IP Services documentationF                                   set and provides a glossary of termsF                                   and acronyms for the TCP/IP Services3                                   software product.   D         HP TCP/IP Services for    The release notes provide version-F         OpenVMS Release Notes     specific information that supersedesF                                   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.   H                                                 (continued on next page)           viii                 H         Table_1_(Cont.)_TCP/IP_Services_Documentation___________________  H         Manual____________________Contents______________________________  E         HP TCP/IP Services for    This manual explains how to install C         OpenVMS Installation and  and configure the TCP/IP Services *         Configuration             product.  B         HP TCP/IP Services for    This manual describes how to useA         OpenVMS User's Guide      the applications available with E                                   TCP/IP Services such as remote file H                                   operations, email, TELNET, TN3270, and3                                   network printing.   H         HP TCP/IP Services for    This manual describes how to configure@         OpenVMS Management        and manage the TCP/IP Services*                                   product.  B         HP TCP/IP Services        This manual describes the TCP/IP?         for OpenVMS Management    Services management commands.          Command Reference   F         HP 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  >         HP TCP/IP Services for    This reference card containsF         OpenVMS UNIX Command      information about commonly performedD         Equivalents Reference     network management tasks and theirE         Card                      corresponding TCP/IP management and 7                                   UNIX command formats.   B         HP 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.   >         HP TCP/IP Services for    This manual describes how toD         OpenVMS Guide to SSH      configure, set up, use, and manage?                                   the SSH for OpenVMS software.   H                                                 (continued on next page)  H                                                                       ix                 H         Table_1_(Cont.)_TCP/IP_Services_Documentation___________________  H         Manual____________________Contents______________________________  F         HP TCP/IP Services for    This manual describes how to use theB         OpenVMS Sockets API       Berkeley Sockets API and OpenVMSD         and System Services       system services to develop network/         Programming               applications.   B         HP TCP/IP Services for    This manual describes the SimpleD         OpenVMS SNMP Programming  Network Management Protocol (SNMP)F         and Reference             and the SNMP application programmingA                                   interface (eSNMP). It describes D                                   the subagents provided with TCP/IPB                                   Services, utilities provided forF                                   managing subagents, and how to build5                                   your own subagents.   B         HP TCP/IP Services        This manual provides informationD         for OpenVMS Tuning and    about how to isolate the causes ofF         Troubleshooting           network problems and how to tune theG                                   TCP/IP Services software for the best .                                   performance.  @         HP TCP/IP Services for    This manual describes the IPv6C         OpenVMS Guide to IPv6     environment, the roles of systems @                                   in this environment, the typesD                                   and function of the different IPv6A                                   addresses, and how to configure D                                   TCP/IP Services to access the IPv6F                                   network. Note that the configurationG                                   information in HP TCP/IP Services for H                                   OpenVMS Guide to IPv6 is superseded byH                                   the IPv6 configuration information nowH                                   provided in Chapter 4 of the HP TCP/IPG                                   Services for OpenVMS Installation and H         __________________________Configuration.________________________  F               For additional information about HP OpenVMS products andC               services, visit the following World Wide Web address:   *               http://www.hp.com/go/openvms  H               For a comprehensive overview of the TCP/IP protocol suite,H               refer to the book Internetworking with TCP/IP: Principles,<               Protocols, and Architecture, by Douglas Comer.  	         x                           Reader's Comments     C               HP welcomes your comments on this manual. Please send <               comments to either of the following addresses:  +               Internet    openvmsdoc@hp.com   1               Postal      Hewlett-Packard Company >               Mail        OSSG Documentation Group, ZKO3-4/U08,                           110 Spit Brook Rd./                           Nashua, NH 03062-2698   -         How to Order Additional Documentation   F               For information about how to order additional documenta-?               tion, visit the following World Wide Web address:   4               http://www.hp.com/go/openvms/doc/order           Conventions   -               The name TCP/IP Services means:   5               o  HP TCP/IP Services for OpenVMS Alpha   3               o  HP TCP/IP Services for OpenVMS I64   3               o  HP TCP/IP Services for OpenVMS VAX   @               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.     H                                                                       xi                   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.   @               .                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.   >               ( )              In command format descriptions,A                                parentheses indicate that you must D                                enclose choices in parentheses if you5                                specify more than one.   G               [ ]              In command format descriptions, brackets H                                indicate optional choices. You can chooseD                                one or more items or no items. Do notE                                type the brackets on the command line. 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.                 xii                    G               |                In command format descriptions, vertical D                                bars separate choices within bracketsF                                or braces. Within brackets, the choicesD                                are optional; within braces, at leastF                                one choice is required. Do not type theA                                vertical bars on the command line.   E               { }              In command format descriptions, braces B                                indicate required choices; you mustG                                choose at least one of the items listed. D                                Do not type the braces on the command$                                line.  D               bold type        Bold type represents the introductionD                                of a new term. It also represents theF                                name of an argument, an attribute, or a&                                reason.  >               italic type      Italic type 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 TYPE   Uppercase type indicates a command, theH                                name of a routine, the name of a file, orG                                the abbreviation for a system privilege.   E               Example          This typeface indicates code examples, @                                command examples, and interactiveB                                screen displays. In text, this typeF                                also identifies URLs, UNIX commands andH                                pathnames, PC-based commands and folders,H                                and certain elements of the C programming(                                language.  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.   H                                                                     xiii                   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.                                                                                         xiv                        H                                                                        1H         ________________________________________________________________  H                       Preparing to Install and Configure TCP/IP Services      E               This chapter explains how to prepare for installing and B               configuring HP TCP/IP Services for OpenVMS software.  )         1.1 Understanding the Major Tasks   F               Installing the TCP/IP Services software takes just a fewF               minutes to complete. You can install the software duringG               the OpenVMS operating system installation procedure or as                 a layered product.  G               After you install TCP/IP Services, you need to enable the E               services and verify the configuration through the menu- H               driven TCPIP$CONFIG configuration procedure. This step may0               take about 15 minutes to complete.  H               Table 1-1 lists the major tasks involved in installing andH               configuring TCP/IP Services and the sections that describe               these tasks.                                  H                   Preparing to Install and Configure TCP/IP Services 1-1           :         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_to_perform...__________________Described_in...__  G               1    Prepare for installation and        Sections 1.2 and :                    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.   B               5    Start TCP/IP Services.              Section 3.6  B               6    Verify the configuration.           Section 3.9  C               7    Complete additional configuration   Section 3.10 3                    and setup tasks, as appropriate.   @               8    Configure the system as an IPv6     Chapter 4H               _____host_or_IPv6_router._________________________________  !         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_to_perform...__________________Described_in...__  D               1    Inspect the distribution kit.       Section 1.2.1  D               2    Extract and read the TCP/IP         Section 1.2.2*                    Services release notes.  D               3    Back up the system disk.            Section 1.2.3  D               4    Perform an OpenVMS operating        Section 1.2.31                    system upgrade, if applicable.   D               5    Register the TCP/IP Services        Section 1.2.4                    license PAK.   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.   B               8    Assemble information for            Section 1.3!                    configuration.   D               9    Remove any Version 5.0 IPv6 and     Section 1.2.94                    Version 5.3 SSH or failSAFE EarlyH               _____Adopters_Kits_(EAKs).________________________________  -         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, also known as the Software Products Library (SPL), F               check the CD master index for the location of the TCP/IPE               Services for OpenVMS kit. If you have an individual CD- F               ROM, supply the device name (such as DKAn) for the mediaD               when you issue the command to install TCP/IP Services.  G               Check that the kit contains everything listed on the Bill D               of Materials (BOM). If anything is missing or damaged,-               contact your HP representative.     H                   Preparing to Install and Configure TCP/IP Services 1-3           :         Preparing to Install and Configure TCP/IP Services!         1.2 Preinstallation Tasks   *         1.2.2 Extracting the Release Notes  G               The HP TCP/IP Services for OpenVMS Release Notes document G               contains important information you should know 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 text_H               file, enter the following POLYCENTER Software Installation               utility command:  H               $ PRODUCT EXTRACT FILE TCPIP/SELECT=TCPIP055.RELEASE_NOTES  F               To extract the release notes as a PostScript file, enter               the following:  K               $ PRODUCT EXTRACT FILE TCPIP/SELECT=TCPIP055_RELEASE_NOTES.PS   >         1.2.3 Backing Up the System Disk and Upgrading OpenVMS  D               Before you install TCP/IP Services, HP recommends thatE               you back up the system disk using the backup procedures E               established at your site. After the backup operation is H               complete, you should upgrade the OpenVMS operating system,               if applicable.  F               For information about backing up a system disk, refer toA               the HP OpenVMS System Manager's Manual: Essentials.e  H               For information about how to upgrade OpenVMS, refer to theB               appropriate OpenVMS upgrade and installation manual.  ?         1.2.4 Registering the License Product Authorization Key   D               Before you install TCP/IP Services on a newly licensedB               node or cluster, you must register a License Product?               Authorization Key (PAK) using the OpenVMS License C               Management Facility (LMF). Without a PAK, you can use 8               only DECwindows TCP/IP Transport software.  F               On OpenVMS I64 systems, an OpenVMS Operating Environment@               (OE) PAK must be installed. The license for TCP/IPE               Services for OpenVMS is contained within each of the OE_               licenses.   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.  >         1-4 Preparing to Install and Configure TCP/IP Services r         H                       Preparing to Install and Configure TCP/IP ServicesH                                                1.2 Preinstallation Tasks  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 optional F               software, review the PAK status and install the PAKs forF               any prerequisite or optional software before you install               TCP/IP Services.  H               To register a license, log in to the SYSTEM account and do#               one of the following:   E               o  Run the SYS$UPDATE:VMSLICENSE.COM file and enter the ,                  data from your License PAK.  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 OpenVMSI               Cluster.  F               For complete information about LMF, refer to the OpenVMS0               License Management Utility Manual.  %         1.2.5 Checking the Disk Space   B               Make sure your system has at least 150,000 blocks ofG               disk space available. The actual disk space needed varies E               depending on the system environment, configuration, and.               software options.1  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               The minimum physical memory required for TCP/IP ServicesF               for OpenVMS is the same as that required for the OpenVMSD               operating system. For OpenVMS physical memory require-F               ments, refer to the the Software Product Description for:               the OpenVMS operating system (SPD 82.35.xx).  8               To check the memory on your system, enter:                  $ SHOW MEMORY/FULL  H                   Preparing to Install and Configure TCP/IP Services 1-5 h  c      :         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 readilyl@               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.n  F                 ________________________Note  ________________________  =                 Booting OpenVMS with MIN, INST, or UPGRADE is.<                 not supported. The product configuration and@                 startup command procedures (TCPIP$CONFIG.COM andB                 TCPIP$STARTUP.COM) fail if you perform any kind of,                 boot other than a full boot.  >                 The following recommendations apply to minimalA                 configurations. Requirements will increase as you.A                 add services and inbound or outbound connections..  E                 _____________________________________________________n  3         1.2.7.1 Global Pagelets and Global Sections.  G               The TCP/IP Services software requires at least 160 global C               sections and 12,000 global pagelets be available. The.G               minimum requirement is affected by the number of services                you enable.   B               To check the number of available global pagelets andE               global sections, enter WRITE commands with the F$GETSYI D               lexical functions. The following is an example from an#               OpenVMS Alpha system:)  :               $ 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 GBLPAGES ;               and GBLSECTIONS, as in the following example:   !               ADD_GBLPAGES = 7500."               ADD_GBLSECTIONS = 75  >         1-6 Preparing to Install and Configure TCP/IP Services    .      H                       Preparing to Install and Configure TCP/IP ServicesH                                                1.2 Preinstallation Tasks  %         1.2.7.2 Nonpaged Dynamic Pool   F               Add at least 500,000 bytes of available nonpaged dynamic0               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 increasedsC                 automatically. This increases throughput across the /                 FDDI for local TCP connections.a  E                 _____________________________________________________s  >               3. Refer to the following example, and then editC                  MODPARAMS.DAT to reflect the appropriate value for 6                  the NPAGEDYN and NPAGEVIR parameters:  H                  ! Add nonpaged pool for HP TCP/IP Services for OpenVMS.                  !$                  ADD_NPAGEDYN=500000$                  ADD_NPAGEVIR=500000  H               For more information about nonpaged dynamic pool, refer toA               the HP OpenVMS System Manager's Manual: Essentials.O  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.i  C               The TCPIP$CONFIG configuration procedure uses a groupaF               UIC to create accounts for services. If a user-specifiedD               UIC is not in place from a previous configuration, the@               procedure creates the following UIC group numbers:  H                   Preparing to Install and Configure TCP/IP Services 1-7 p         :         Preparing to Install and Configure TCP/IP Services!         1.2 Preinstallation Tasks   H               __________________________________________________________               Default.               UIC Group H               Number_____Description____________________________________  A               3655       The default UIC group number for servicen@                          accounts. If this is an initial productE                          configuration but the procedure detects that H                          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 ANONYMOUSvH               ___________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:   (               $ 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 UIC E               group number, assign the value TRUE to the logical name H               TCPIP$ASK_GROUP_UIC, as in the following example. When youE               configure TCP/IP Services, TCPIP$CONFIG prompts you for                the group UIC.  /               $ DEFINE TCPIP$ASK_GROUP_UIC TRUE   /         1.2.9 Remove Early Adopters Kits (EAKs)   F               If you have installed one or more of the following EAKs,E               you must use the PCSI REMOVE command to remove the EAKs =               before you install TCP/IP Services Version 5.5:   %               o  Version 5.0 IPv6 EAK_  F                 ________________________Note  ________________________  C                 After you remove the Version 5.0 IPv6 EAK, you mustT!                 do the following:i  D                    1. Run the TCPIP$IP6_SETUP.COM command procedure.:                       For more information, see Chapter 4.  >         1-8 Preparing to Install and Configure TCP/IP Services h  i      H                       Preparing to Install and Configure TCP/IP ServicesH                                                1.2 Preinstallation Tasks  >                    2. After you install the current version of@                       TCP/IP Services, recompile and relink your#                       applications.s  E                 _____________________________________________________f  0               o  Version 5.3 SSH for OpenVMS EAK  ,               o  Version 5.3 failSAFE IP EAK  0         1.3 Assembling Configuration Information  F               Use the worksheet in Table 1-3 to assemble configuration               information.  F               If you are configuring TCP/IP Services on the system forF               the first time, the TCPIP$CONFIG configuration procedureB               prompts you for the information listed in Table 1-3.C               If you are reconfiguring after a product upgrade, the F               procedure uses the previous configuration information as4               the default for the new configuration.  E               For information to help you answer the questions on theTH               configuration worksheet, refer to the appropriate chaptersF               in the HP TCP/IP Services for OpenVMS Management manual.B               For information to help you answer SSH configurationH               options, refer to the HP TCP/IP Services for OpenVMS Guide               to SSH.                                   H                   Preparing to Install and Configure TCP/IP Services 1-9 l  i      :         Preparing to Install and Configure TCP/IP Services0         1.3 Assembling Configuration Information  H         Table_1-3_Configuration_Planning_Worksheet______________________  G                                                        Your answer willsH         _____When_the_configuration_procedure_asks...__be...____________  H         What is the system's host name (for example,   _________________         MYNODE)?  H         What is the system's Internet domain name      _________________#         (for example, widgets.com)?h  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 networkc5         interface), might be configured automaticallyn0         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]n  H                                                        _________________  H                                                        _________________  H         [1]If_the_IP_interface_runs_under_control_of_the_DHCP_client,___  F         this information might be configured automatically. Check withE         your network manager. For more information, refer to the DHCPa         client documentation.   H                                                 (continued on next page)  ?         1-10 Preparing to Install and Configure TCP/IP Services     o      H                       Preparing to Install and Configure TCP/IP ServicesH                                 1.3 Assembling Configuration Information  H         Table_1-3_(Cont.)_Configuration_Planning_Worksheet______________  G                                                        Your answer willlH         _____When_the_configuration_procedure_asks...__be...____________    H         For failSAFE IP, what are the interfaces that  _________________2         will be used for the IP address's standby?  H                                                        _________________  H                                                        _________________  H         What is the UIC group number for TCP/IP        _________________2         Services (see Section 1.2.8)? For example,
         3655.o  H         Which type of routing is appropriate for the   _________________#         network, Static or Dynamic?s  /              Static - For simple networks where !              routes do not changea  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 whereo$              flexibility is required  0              If dynamic, you must specify either%              ROUTED or GATED routing.M  3         Do you plan to enable the BIND resolver? If          so:   H         *    What is the name of the BIND server you   _________________3              want the resolver to use (for example,o              MAINSV)?   H         *    What is the IP address of the BIND        _________________1              server (for example, 19.112.139.10)?   H                                                 (continued on next page)  H                  Preparing to Install and Configure TCP/IP Services 1-11 s         :         Preparing to Install and Configure TCP/IP Services0         1.3 Assembling Configuration Information  H         Table_1-3_(Cont.)_Configuration_Planning_Worksheet______________  G                                                        Your answer will H         _____When_the_configuration_procedure_asks...__be...____________  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         *    Do you want to enable authentication      _________________1              traps when the master agent receives .              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 community 1              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 entered. Example: Rw2.  H         *    Do you want to provide additional         _________________/              community names and addresses (forn3              implementing traps and allowing accessa5              beyond the default read-only provided byl%              the "public" community)?d  H                                                 (continued on next page)  ?         1-12 Preparing to Install and Configure TCP/IP Services     P      H                       Preparing to Install and Configure TCP/IP ServicesH                                 1.3 Assembling Configuration Information  H         Table_1-3_(Cont.)_Configuration_Planning_Worksheet______________  G                                                        Your answer will,H         _____When_the_configuration_procedure_asks...__be...____________  H         ________________________________________________________________                                                                              H                  Preparing to Install and Configure TCP/IP Services 1-13 e                     H                                                                        2H         ________________________________________________________________  H                                               Installing TCP/IP Services      @               This chapter explains how to install the HP 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 directlyiE               from the OpenVMS operating system CD/DVD menu, refer to :               the OpenVMS Upgrade and Installation Manual.  H               For information about the POLYCENTER Software InstallationG               utility, refer to the HP OpenVMS System Manager's Manual:                Essentials.h  /         2.1 Invoking the Installation Procedure   E               When you have completed the recommended preinstallation C               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 configuree+               this version of the software.   C               To install the TCP/IP Services software on an OpenVMSP6               Alpha or I64 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.   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$STARTUPo  H                                           Installing TCP/IP Services 2-1 F         "         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.   F               4. If a previous version of the TCP/IP Services softwareF                  is installed on the system, shut it down by using the%                  appropriate command:x  H                  _______________________________________________________                   If the softwareH                  version_is..._________Use_this_command...______________  D                  Version 4.x           @SYS$MANAGER:UCX$SHUTDOWN.COM  H                  Version_5.x___________@SYS$STARTUP:TCPIP$SHUTDOWN.COM__  G               5. HP recommends that you log the installation procedure.eF                  If you have DECnet configured on your system, you canG                  create a log of the installation procedure by enteringnD                  the following command and then log in to the system                  account again:   4                  $ SET HOST 0/LOG=file-specification  G                  In this command, file-specification is the name of the H                  file to which you want the log written. The log file is2                  written to the current directory.  D                  If you do not have DECnet but have the LAT protocolB                  (Version 5.0 or later), you can use the following                  command:   8                  $ SET HOST /LAT /LOG=file-specification  F               6. Start the POLYCENTER Software Installation utility byH                  entering the PRODUCT INSTALL command with the directory?                  path appropriate for your system. For example:I  ?                  $ PRODUCT INSTALL TCPIP /SOURCE=directory-pathn  C                  In this command, directory-path specifies the diskcG                  and directory name for the source drive that holds the P                  TCP/IP Services kit. For example, /SOURCE=DKA400:[TCPIPAXP055].  @                  If you do not specify the source qualifier, theF                  POLYCENTER Software Installation utility searches theE                  location defined by the logical name PCSI$SOURCE. IfnF                  not defined, the utility searches the current default                  directory.   &         2-2 Installing TCP/IP Services y         H                                               Installing TCP/IP ServicesH                                  2.1 Invoking 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 an A               earlier version of TCP/IP Services installed on it. H               Additional explanatory information follows each portion ofH               the installation procedure. For a sample installation on aG               system on which the product has never been installed, see                Appendix A.c  F               The actual installation output that is displayed on yourH               system might vary, depending on your current configuration6               and the operating system (Alpha or I64).  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.   ;                 The symbols xx in the following example and B                 elsewhere in this document represent the product's0                 two-digit update version number.  A                 The following example shows an installation on anyA                 OpenVMS Alpha system. Output for installations on)B                 OpenVMS I64 systems are similar. One difference is@                 the TCP/IP Services product name: on OpenVMS I64?                 systems it is HP I64VMS TCPIP, while on OpenVMSiA                 Alpha systems it is DEC AXPVMS TCPIP, as shown inp                 Example 2-1.  E                 _____________________________________________________i                      H                                           Installing TCP/IP Services 2-3 x  l      "         Installing TCP/IP Services7         2.2 Stepping Through the Installation Procedure,  C         Example 2-1 TCP/IP Services Installation: Sample POLYCENTERx;                     Software Installation Utility ProcedureU  B            1 - DEC AXPVMS TCPIP V5.5-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 - Exit   N         Choose one or more items from the menu separated by commas: 1 <Return>  D               The initial menu that is displayed includes the latestE               TCP/IP Services product and any versions of the product A               that are in place on the system. Install the latest !               version (option 1).   0         The following product has been selected:E             DEC AXPVMS TCPIP V5.5-xx                  Layered Productn  /         Do you want to continue? [YES] <Return>a  ?               Pressing Return allows the procedure to continue.l  (         Configuration phase starting ...  V         You will be asked to choose options, if any, for each selected product and forW         any products that may be installed to satisfy software dependency requirements.   A         DEC AXPVMS TCPIP V5.5-xx: HP TCP/IP Services for OpenVMS._  J             Copyright 1976, 2004 Hewlett-Packard Development Company, L.P.  5             Hewlett-Packard Development Company, L.P.f  J             HP TCP/IP Services for OpenVMS offers several license options.  @         Do you want the defaults for all options? [YES] <Return>  B               Press Return (or enter YES) to choose the POLYCENTERH               Software Installation utility defaults for the options, or/               enter NO to choose other options.c  8         Do you want to review the options? [NO] <Return>  F               Enter YES to review the POLYCENTER Software InstallationE               utility options. Press Return (or enter NO) to continue 7               with the final phase of the installation.p  &         2-4 Installing TCP/IP Services c  l      H                                               Installing TCP/IP ServicesH                          2.2 Stepping Through the Installation Procedure  C               In this example, the options are not reviewed. If you E               enter YES to review the options, the procedure displays E               the options and asks whether you are satisfied with the H               options. To accept the options as listed, press Return. To+               change the options, enter NO.       $         Execution phase starting ...  ?         The following product will be installed to destination:lM             DEC AXPVMS TCPIP V5.5-xx              DISK$ALPHASYS:[VMS$COMMON.] ?         The following product will be removed from destination:oM             DEC AXPVMS TCPIP V5.1-15              DISK$ALPHASYS:[VMS$COMMON.]   N         Portion done: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%  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 ...          % TCPIP-W-PCSI_INSTALL         % - BG device exists. M         %   To use the version of HP TCP/IP Services that was just installed,r$         %   system must be rebooted.	         %          Portion done: 100%  1         The following product has been installed: B             DEC AXPVMS TCPIP V5.5-xx               Layered Product/         The following product has been removed:tB             DEC AXPVMS TCPIP V5.1-15               Layered Product  A         DEC AXPVMS TCPIP V5.5-xx: HP TCP/IP Services for OpenVMS.   F             Check the release notes for current status of the product.  "         2.3 Postinstallation Tasks  E               After the installation completes, perform the followingk               steps:    H                                           Installing TCP/IP Services 2-5 _         "         Installing TCP/IP Services"         2.3 Postinstallation Tasks  %               1. Optionally, you can:   C                  -  Read the HP TCP/IP Services for OpenVMS Release K                     Notes on line or print the file from SYS$HELP:TCPIP056_ '                     RELEASE_NOTES.PS or 4                     SYS$HELP:TCPIP056.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 the @                     disk and directory name for the source driveD                     that holds the TCP/IP Services kit (for example,H                     /SOURCE=DKA400:[TCPIPAXP055]). If you do not specifyA                     the source qualifier, the POLYCENTER Software2F                     Installation utility searches the location definedH                     by the logical name PCSI$SOURCE. If not defined, theC                     utility searches the current default directory.e  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 newh9                  TCP/IP Services software to take effect.   E                 _____________________ Important _____________________   <                 Do not delete any files that remain from the>                 previous version of the product. Many of theseB                 files are used by TCPIP$CONFIG for converting your?                 existing configuration to the new configurationg)                 (described in Chapter 3).   ;                 When rebooting OpenVMS, perform only a fulld?                 boot. Any other kind of boot causes the producto<                 configuration and startup command proceduresA                 (TCPIP$CONFIG.COM and TCPIP$STARTUP.COM) to fail.   E                 _____________________________________________________   C               3. Proceed to Chapter 3 to configure TCP/IP Services.       &         2-6 Installing TCP/IP Services o  a      H                                               Installing TCP/IP ServicesH                                               2.3 Postinstallation Tasks      F                 ________________________Note  ________________________  C                 With previous versions of TCP/IP Services, you were B                 required to log out of the SYSTEM account and thenB                 log back in to the SYSTEM account to establish theD                 TCPIP command environment. Starting with Version 5.4?                 of TCP/IP Services, this is no longer required.   E                 _____________________________________________________y                                                                    H                                           Installing TCP/IP Services 2-7    y                  H                                                                        3H         ________________________________________________________________  H                                              Configuring TCP/IP Services      C               After you install HP TCP/IP Services for OpenVMS, youoC               need to enable the components and characteristics youtF               require for your particular system using the menu-driven3               TCPIP$CONFIG configuration procedure.   D               This chapter explains the TCPIP$CONFIG menus, providesC               sample installation output, and summarizes additionalu,               configuration and setup tasks.  F                 ________________________Note  ________________________  D                 Before configuring TCP/IP services for OpenVMS, make*                 sure you do the following:  >                 o  Create a System Authorization File (SYSUAF)K                    database and a RIGHTSLIST database. The TCPIP$CONFIG.COMfC                    configuration procedure fails on systems that doi,                    not have these databases.  @                 o  Create and start the queue manager. The queue=                    manager must be running. This is important A                    especially if you plan to enable services thatr4                    use queues, such as SMTP and LPD.  D                    The queue manager is normally enabled by default.@                    To determine whether it is running, enter theB                    following command at the OpenVMS DCL prompt, as                    shown:t  '                    $ SHOW QUEUE/MANAGERp  B                    If the queue manager is running, the display isC                    as follows (where the local node is named ACME):t  F                    Queue manager SYS$QUEUE_MANAGER, running, on ACME::  A                    If the following is displayed instead, the re-iD                    quired queue files have not yet been created. The  H                                          Configuring TCP/IP Services 3-1 g         #         Configuring TCP/IP ServicesC    C                    files do not exist after an initial installation.2                    of OpenVMS and must be created.  -                    -RMS-E-FNF, file not founda  =                    To create these files, enter the followings'                    OpenVMS DCL command:   -                    $ START/QUEUE/MANAGER/NEW.a  @                    For more information, refer to the HP OpenVMSC                    System Manager's Manual: Essentials. Information B                    is also available in the SYS$MANAGER:SYSTARTUP_%                    VMS.TEMPLATE file.l  E                 _____________________________________________________m  =         3.1 Recommended Order for Configuring TCP/IP Services   F               Table 3-1 lists the tasks involved in configuring TCP/IPC               Services, and the sections that describe these tasks.                                                 '         3-2 Configuring TCP/IP Servicesr f  T      H                                              Configuring TCP/IP ServicesH                    3.1 Recommended Order for Configuring TCP/IP Services  H               Table_3-1_Configuring_TCP/IP_Services_____________________  E                                                             Described H               Step__Task_to_perform...______________________in..._______  G               1     Assemble system information to prepare  Section 1.3c-                     for running TCPIP$CONFIG.a  G               2     If applicable, add your system to the   Section 3.2 :                     OpenVMS Cluster to perform as a TCP/IP                     host  G               3     Run TCPIP$CONFIG. (Alternatively,       Section 3.4v3                     have TCP/IP Services configuredc7                     automatically, as explained in stepl:                     4.) If you have a TCP/IP Services V4.x8                     configuration on your system, answer9                     prompts to convert existing databases_*                     or to create new ones.  G               4     If you prefer, have TCP/IP Services     Section 3.3 :                     software configured automatically by a                      DHCP server.  D               5     Manually configure the TCP/IP Services  SectionsA                     core environment, clients, and servers  3.4.4 C                     using TCPIP$CONFIG.                     through A                                                             3.4.6   I               6     Configure the optional components       Section 3.4.7 6                     using TCPIP$CONFIG, as applicable.  G               7     Start TCP/IP Services.                  Section 3.6   G               8     Verify the configuration.               Section 3.9o  H               9     Complete additional configuration       Section 3.10H               ______tasks,_as_appropriate.______________________________  F                 ________________________Note  ________________________  A                 Configuration changes made to the TCP/IP Services >                 software do not take effect until you start or6                 restart the software. See Section 3.6.  E                 _____________________________________________________   H                                          Configuring TCP/IP Services 3-3           #         Configuring TCP/IP Services 1         3.2 Adding a System to an OpenVMS Clustert  1         3.2 Adding a System to an OpenVMS Cluster   E               The TCPIP$CONFIG.COM configuration procedure for TCP/IPnH               Services Version 5.5 creates OpenVMS accounts using largerE               system parameter values than in previous versions. OnlyoD               new accounts get these larger values. These values areF               useful on OpenVMS Alpha systems but essential on OpenVMS               I64 systems.  E               To have your OpenVMS I64 system join an OpenVMS Cluster B               as a TCP/IP host, HP recommends adding the system toC               the cluster before you configure TCP/IP Services. The G               guidelines in Section 3.2.1 assume you have followed thist               recommendation.u  H               If you configure TCP/IP Services before you add the system.               to a cluster, see Section 3.2.2.  <         3.2.1 Running a Newly Configured Host in the Cluster  F               The following recommendations assume you are configuringB               TCP/IP Services on the system after having added the,               system to the OpenVMS Cluster.  C               If TCP/IP Services has previously been installed on arF               node in the cluster and you encounter problems running aG               TCP/IP component on the system, modify the cluster SYSUAF F               to increase the parameter values for the account used byH               the affected component. The minimum recommended values are"               listed in Table 3-2.  H               Table_3-2_Minimum_Values_for_SYSUAF_Parameters____________  H               Parameter_____Minimum_Value_______________________________                 ASTLM         100                  BIOLM         400   "               BYTLM         108000                 DIOLM         50                 ENQLM         100                  FILLM         100a  H                                                 (continued on next page)  '         3-4 Configuring TCP/IP Servicesg p         H                                              Configuring TCP/IP ServicesH                                3.2 Adding a System to an OpenVMS Cluster  H               Table_3-2_(Cont.)_Minimum_Values_for_SYSUAF_Parameters____  H               Parameter_____Minimum_Value_______________________________  !               PGFLQUOTA[1]  50000l                 TQELM         50                  WSEXTENT      4000                  WSQUOTA       1024H               [1]This_parameter's_value_setting_is_especially_critical._  H               __________________________________________________________  D               The IMAP, DHCP, and XDM components can exhibit accountF               parameter problems if the value assigned to PGFLQUOTA orG               to any of the other listed parameters is too low. Use the D               OpenVMS AUTHORIZE utility to modify SYSUAF parameters.B               For more information, refer to the HP OpenVMS System9               Management Utilities Reference Manual: A-L.   E         3.2.2 Configuring TCP/IP Services Before Adding the System to_               the Cluster   H               If you configure TCP/IP Services before you add the systemB               to a cluster, when you add the system to the clusterE               the owning UIC for each of the TCP/IP service SYS$LOGIN D               directories (TCPIP$service-name, where service-name isH               the name of the service) may be incorrect. Use the OpenVMS6               AUTHORIZE utility to correct these UICs.  A         3.3 Automatic Configuration of TCP/IP Services Using DHCPt             Client  B               Beginning with Version 5.5, TCP/IP Services supportsC               the DHCP client, which allows you to have your systemIH               configured automatically 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 startupIF                  procedure, SYS$STARTUP: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.  H                                          Configuring TCP/IP Services 3-5 P  A      #         Configuring TCP/IP ServicesEH         3.3 Automatic Configuration of TCP/IP Services Using DHCP Client  G                  The startup procedure invokes TCPIP$CONFIG, which setsaF                  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 client   !                  -  TELNET server                     -  SMTP  8                  WORF_system> @sys$startup:tcpip$startupE                  %TCPIP-I-NOCONFIG, TCP/IP Services is not configured G                  Autoconfigure TCP/IP Services using DHCP client [YES]:   H                  For more information about DHCP, refer to the HP TCP/IP8                  Services for OpenVMS Management manual.  @               o  Run TCPIP$CONFIG. Choose Option 2 from the CoreC                  Environment Configuration Menu, then choose Option_C                  2-Interfaces. Here you will find the Interface andiD                  Address Configuration Menu from which to choose theE                  interface you want to configure for DHCP. Select the F                  Option containing the interface you want to configure                  for DHCP.  F                  Then choose Option 3 from the Interface ConfigurationH                  Menu, enabling the DHCP client to manage the address on                   that interface.  C                  Following is an example of the Interface & Addressu$                  Configuration menu:  V                  HP TCP/IP Services for OpenVMS Interface & Address Configuration Menu  c                                  Hostname Details: Configured=Not Configured, Active=Not Configured   7                                  Configuration options: L                                  1  -  WE0 Menu (EWA0: TwistedPair 1000mbps)K                                  2  -  IE0 Menu (EIA0: TwistedPair 100mbps)p0                                 [E] -  Exit menu  <                                  Enter configuration option:  '         3-6 Configuring TCP/IP Servicesd n  u      H                                              Configuring TCP/IP ServicesH         3.3 Automatic Configuration of TCP/IP Services Using DHCP Client  G                  Following is an example of the Interface Configuration @                  Menu pertaining to the interface WE0 selection:  `                                  HP TCP/IP Services for OpenVMS Interface WE0 Configuration Menu  7                                  Configuration options:   B                                  1  - Add a primary address on WE0A                                  2  - Add an alias address on WE0oQ                                  3  - Enable DHCP client to manage address on WE0t/                                 [E] - Exit menu   <                                  Enter configuration option:  5                  This prompts you with the following:u  C                  Configure WE0 as the DHCP PRIMARY? (Y,N,HELP) [Y]:   +         Press return to accept the default.k  ?                  The resulting display resembles the following:d  V                  HP TCP/IP Services for OpenVMS Interface & Address Configuration Menu  c                                  Hostname Details: Configured=Not Configured, Active=Not Configuredp  7                                  Configuration options:lo                                  1  -  WE0 Menu (EWA0: TwistedPair 1000mbps) (Managed by DHCP client - PRIMARY)oK                                  2  -  IE0 Menu (EIA0: TwistedPair 100mbps) 0                                 [E] -  Exit menu  ;                                 Enter configuration option:_  F                  You can also use TCPIP$CONFIG to configure additional4                  services and parameters, as needed.  F                 ________________________Note  ________________________  >                 Verify that a DHCP Server is already setup and?                 running on another system first; otherwise, youtB                 could receive errors when the DHCP Client tries to0                 start, similar to the following:      H                                          Configuring TCP/IP Services 3-7 s  b      #         Configuring TCP/IP ServicesaH         3.3 Automatic Configuration of TCP/IP Services Using DHCP Client  H          %TCPIP-I-DHCPC_STRD_CLNT, DHCP client started with PID 00000556c         liam$dka0:[sys0.syscommon.][sysexe]tcpip$dhcp_client_conf.exe;1: timed out after 30 seconds =         %TCPIP-E-DHCPC_TIMEOUT, controlling program timed outrK         %TCPIP-E-DHCPCONFERR, DHCP client failed to configure interface WE0 =         -TCPIP-E-DHCPC_TIMEOUT, controlling program timed out   ?                 The DHCP server needs the following files to beu"                 setup for success:                   -  nets.                   -  netmasks.                   -  dhcpcap.c                   -  .ddnskeys                   -  server.pcy   E                 _____________________________________________________o            3.4 Running TCPIP$CONFIG  E               The TCPIP$CONFIG configuration procedure displays menus .               from which you do the following:  F               o  Make selections that enable services for your system.=                  To select the default, press the Return key.   8               o  Start or stop TCP/IP Services software.  *               o  Verify the configuration.  $               To get started, enter:  )               $ @SYS$MANAGER:TCPIP$CONFIG   E         3.4.1 Converting Existing TCP/IP Services Configuration Filesr               (Upgrade Only)  H               If you have a TCP/IP Services for OpenVMS (UCX) configura-H               tion in place (Version 4.x), and you have never configuredG               a Version 5.x product on the system, the procedure begins D               by asking you whether to convert the Version 4.x (UCX)2               TCP/IP Services configuration files:  5               Convert the old configuration files [Y]a  @               Unless you respond NO to the prompt, the procedureH               converts existing configuration files to new configuration               files.  '         3-8 Configuring TCP/IP Servicess _  .      H                                              Configuring TCP/IP ServicesH                                                 3.4 Running TCPIP$CONFIG  H               If you have already configured this product, the procedureA               indicates that no new configuration files are beings               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 required??           to run HP TCP/IP Services for OpenVMS on this system.o             NOTE: G           TCP/IP has been previously configured from an earlier versionoG           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, youeI           will not be asked again.  At the end of the conversion you wille7           be able to further modify your configuration.   9         Convert the old configuration files [Y]: <Return>n)         Preparing files for conversion...   8             UCX$SERVICE.DAT        --> TCPIP$SERVICE.DAT5             UCX$HOST.DAT           --> TCPIP$HOST.DAT 8             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.DATg9             UCX$PRINTCAP.DAT       --> TCPIP$PRINTCAP.DAT   2                No new database files were created.            FTP SERVER Configuration            LPD SERVER Configuration  -         Service is not defined in the SYSUAF.o3           Nonprivileged user access is not enabled.   =         By default, HP TCP/IP Services for OpenVMS configures,F         LPD such that nonprivileged users cannot modify queue entries.  H                                          Configuring TCP/IP Services 3-9           #         Configuring TCP/IP Services           3.4 Running TCPIP$CONFIG  :         Creating TCPIP$AUX identifier with a value of 3655  H              HP 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 queuev*                  - Name of the remote host9                  - Spooling directory for the local queuer  P                To add or delete printers in the TCPIP PRINTCAP database, use the6                $RUN SYS$SYSTEM:TCPIP$LPRSETUP command.	         .a	         .n	         .l  >         3.4.2 Creating New TCP/IP Services Configuration Files  G               If you do not have an existing TCP/IP Services configura-VG               tion in place from a previous version of the product, therH               procedure begins by creating configuration database files,6               as shown in the following sample output:  J         Checking TCP/IP Services for OpenVMS configuration database files.  8          Creating SYS$COMMON:[SYSEXE]TCPIP$SERVICE.DAT;15          Creating SYS$COMMON:[SYSEXE]TCPIP$HOST.DAT;1a8          Creating SYS$COMMON:[SYSEXE]TCPIP$NETWORK.DAT;16          Creating SYS$COMMON:[SYSEXE]TCPIP$ROUTE.DAT;16          Creating SYS$COMMON:[SYSEXE]TCPIP$PROXY.DAT;1>          Creating SYS$COMMON:[SYSEXE]TCPIP$CONFIGURATION.DAT;1  @          Interface - NONE configured.  DHCP will be the default.  3         3.4.3 Understanding the Configuration Menusr  E               After the configuration files are converted or created,f7               the Main Configuration menu is displayed:p  =             HP TCP/IP Services for OpenVMS Configuration Menun  "             Configuration options:  )                    1  -  Core environment *                    2  -  Client components*                    3  -  Server components,                    4  -  Optional components  (         3-10 Configuring TCP/IP Services           H                                              Configuring TCP/IP ServicesH                                                 3.4 Running TCPIP$CONFIG  @                    5  -  Shutdown HP TCP/IP Services for OpenVMS?                    6  -  Startup HP TCP/IP Services for OpenVMSt"                    7  -  Run tests  0                    A  -  Configure options 1 - 45                   [E] -  Exit configuration procedurem  #         Enter configuration option:r  )               The options are as follows:e  H         ________________________________________________________________H         Option_______________Description________________________________  C         1   Core environ-    Configure software associated with theeG             ment             Network, Internet, and Transport layers of_E                              the TCP/IP architecture (Section 3.4.4).M  G         2   Client           Configure application software and related_6             components       services (Section 3.4.5).  B         3   Server           Configure server software and related6             components       services (Section 3.4.6).  H         4   Optional         Configure software necessary if you plan toH             components       allow Anonymous FTP access, enable KerberosB                              authentication for the TELNET server,D                              enable failSAFE IP support, or run suchH                              products as PATHWORKS for OpenVMS (AdvancedB                              Server), Advanced Server for OpenVMS,D                              DECnet over TCP/IP, or any applicationsE                              that use the Stanford Research Institute H                              (SRI) QIO application programming interface,                              (Section 3.4.7)  @         5   Shutdown TCP/IP  Stop TCP/IP Services (Section 3.7).             Services for             OpenVMSp  A         6   Startup TCP/IP   Start TCP/IP Services (Section 3.8).S             Services for             OpenVMS   H         7   Run tests        Run the installation verification procedure+                              (Section 3.9).   H                                         Configuring TCP/IP Services 3-11 T  P      #         Configuring TCP/IP Servicess          3.4 Running TCPIP$CONFIG  H         ________________________________________________________________H         Option_______________Description________________________________  >         A   Configure        Configure all the TCP/IP ServicesF             options 1 -      components (the core, client, server, andH             4                optional services). The procedure takes youG                              through each of the configuration options.i  9         E   Exit the         Return to the system prompt.              configuration H         ____procedure___________________________________________________  F                 ________________________Note  ________________________  =                 If you do not have experience with the TCP/IPeB                 Services product, you should use the configuration@                 menus provided by the TCPIP$CONFIG configurationA                 procedure to configure the product (use options 1 (                 through 4, or option A).  ?                 If you have experience configuring the softwareh?                 and want to bypass the configuration menus, you ?                 can add one or more command parameters when you C                 run TCPIP$CONFIG. For information about the command ,                 parameters, see Section 3.5.  E                 _____________________________________________________   .         3.4.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 Configuration C               menu to configure all the TCP/IP Services components,mB               the Core Environment Configuration menu is displayedE               first. The sample output in the following sections showrH               the progression of the procedure when you choose option A.  C               You are required to configure the Domain, Interfaces,iC               and Routing services; BIND Resolver and Time Zone are                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, you  (         3-12 Configuring TCP/IP Services C  P      H                                              Configuring TCP/IP ServicesH                                                 3.4 Running TCPIP$CONFIG  C                 might not need to set up the other Core Environment <                 components. Ask your network manager whetherA                 these components are configured by DHCP. For more ?                 information, see the DHCP client documentation.e  E                 _____________________________________________________   H            HP TCP/IP Services for OpenVMS Core Environment Configuration            Menuh  !            Configuration options:                       1 - Domainl!                    2 - Interfaceso                    3 - Routing$                    4 - BIND Resolver                     5 - Time Zone  /                    A  - Configure options 1 - 5o!                   [E] - Exit menu   .         Enter configuration option: A <Return>  F                 ________________________Note  ________________________  D                 If you have run the TCPIP$IP6_SETUP.COM procedure toB                 enable IPv6, and then you run the TCPIP$CONFIG.COM@                 command procedure, TCPIP$CONFIG.COM displays theA                 following warning message prior to displaying theP@                 Core Environment configuration options. For more+                 information, see Chapter 4.P  :                                                - WARNING -V                    This node has been configured for IPv6.  If you make any additionalO                    changes to the configuration of the interfaces, you must run Q                    TCPIP$IP6_SETUP again and update your host name information ins;                    BIND/DNS for the changes to take effect.>  E                 _____________________________________________________n  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 (seet               Appendix A).  H                                         Configuring TCP/IP Services 3-13 e  e      #         Configuring TCP/IP Servicess          3.4 Running TCPIP$CONFIG  B               Enter your responses to the menu questions using theD               information from your configuration planning worksheet               (Section 1.3).  $         3.4.4.1 Domain Configuration  H               The following is sample output for configuring the domain:  Q                HP TCP/IP Services for OpenVMS Core Environment Configuration Menus  &                 Configuration options:  %                          1  -  DomainM)                          2  -  Interfaces2&                          3  -  Routing,                          4  -  BIND Resolver(                          5  -  Time Zone  6                          A  -  Configure options 1 - 5(                         [E] -  Exit menu  %         Enter configuration option: 1            DOMAIN Configuration           Enter Internet domain:  H               After you enter the domain name, the display resembles the               following:           DOMAIN Configuration  3         Enter Internet domain: sqa.tcpip.zko.hp.coms>         Communication domain updated in configuration database  6         3.4.4.2 First-time Configuration of Interfaces  E               The interface and address menus allow the configurationyF               and management of both the permanent database as well asE               the live system. The menu supports multi-homed systems,EB               which have multiple addresses and/or interfaces. TheE               menus are context sensitive, so the menu options change 3               according to the state of the system.h  @               The following is sample output for configuring the!               Internet interface:   (         3-14 Configuring TCP/IP Services _         H                                              Configuring TCP/IP ServicesH                                                 3.4 Running TCPIP$CONFIG  R                 Checking TCP/IP Services for OpenVMS configuration database files.  A                 HP TCP/IP Services for OpenVMS Configuration Menuo  &                 Configuration options:  /                          1  -  Core environmentt0                          2  -  Client components0                          3  -  Server components2                          4  -  Optional components  F                          5  -  Shutdown HP TCP/IP Services for OpenVMSE                          6  -  Startup HP TCP/IP Services for OpenVMSe(                          7  -  Run tests  6                          A  -  Configure options 1 - 4;                         [E] -  Exit configuration procedure   .         Enter configuration option: 1 <Return>  R                 HP TCP/IP Services for OpenVMS Core Environment Configuration Menu  &                 Configuration options:  %                          1  -  Domain )                          2  -  Interfacesr&                          3  -  Routing,                          4  -  BIND Resolver(                          5  -  Time Zone  6                          A  -  Configure options 1 - 5(                         [E] -  Exit menu  .         Enter configuration option: 2 <Return>  U                 HP TCP/IP Services for OpenVMS Interface & Address Configuration Menu   R                 Hostname Details: Configured=Not Configured, Active=Not Configured  &                 Configuration options:  D                          1  -  WE0 Menu (EWA0: TwistedPair 1000mbps)C                          2  -  IE0 Menu (EIA0: TwistedPair 100mbps)d  (                         [E] -  Exit menu  )               Enter configuration option:   H                                         Configuring TCP/IP Services 3-15 g  t      #         Configuring TCP/IP Services           3.4 Running TCPIP$CONFIG  H               In this example, no changes are made to the interface. TheG               systems TCP/IP hostname is displayed as "Not Configured."uE               This will automatically be configured the first time an C               IP address is configured. The assigned systems TCP/IPP@               hostname may be changed using the menu options for$               configuring addresses.  C               Additional information is provided for each interface @               name. For instance, the TCP/IP interface named WE0E               corresponds to the OpenVMS device EWA0: and is twisted- @               pair. If you want to configure a standby interfaceD               for failSAFE IP failover support, see Section 3.4.4.4;1               otherwise, skip to Section 3.4.4.5.u  2         3.4.4.3 Interface IP Address Configuration  A               To configure an interface, select the Option of the F               desired interface, then Option 1 - Add a primary addressF               on <chosen interface>, and answer the prompts for the IP8               address, netmask and hostname information.  &               Following is an example:  U                 HP TCP/IP Services for OpenVMS Interface & Address Configuration MenuT  R                 Hostname Details: Configured=Not Configured, Active=Not Configured  &                 Configuration options:  ;                 1  -  WE0 Menu (EWA0: TwistedPair 1000mbps)r:                 2  -  IE0 Menu (EIA0: TwistedPair 100mbps)                  [E] -  Exit menu   +               Enter configuration option: 1$  B               This menu allows the configuration of a "primary" orC               an "alias" address as well as giving control to DHCP- E               client for address assignment. The "primary" address is_H               considered the most often used address for this interface,B               whereas an "alias" address is considered a secondaryD               address. By default, data sent via an interface with aH               "primary" and an "alias" address, will be transmitted withA               the IP source address set to the 'primary' address.t  (         3-16 Configuring TCP/IP Services e         H                                              Configuring TCP/IP ServicesH                                                 3.4 Running TCPIP$CONFIG  E               The following example shows that WE0 is configured with C               a primary IP address of 10.0.0.1 and an alias address F               of 10.0.1.1. The menus would be driven as follows, after:               selecting option "1" from the previous menu.  M               HP TCP/IP Services for OpenVMS Interface WE0 Configuration Menu   $               Configuration options:  0                1  - Add a primary address on WE0/                2  - Add an alias address on WE0 ?                3  - Enable DHCP client to manage address on WE0                  [E] - Exit menun  %         Enter configuration option: 1   >             IPv4 Address may be entered with CIDR bits suffix.7             E.g. For a 16-bit netmask enter 10.0.1.1/16   +             Enter IPv4 Address []: 10.0.0.1 J             Default netmask calculated from class of IP address: 255.0.0.0  C             IPv4 Netmask may be entered in dotted decimal notation, C             (e.g. 255.255.0.0), or as number of CIDR bits (e.g. 16)   2         Enter Netmask or CIDR bits [255.0.0.0]: 16         Enter hostname []: liam   C               The system displays the information entered. If it ism3               correct, press <Return> to accept it.   E               The following displays, showing all information entered H               and then the Interface & Address Menu again to display theF               change you have just made, configuration, and interface.                    H                                         Configuring TCP/IP Services 3-17           #         Configuring TCP/IP Servicesg          3.4 Running TCPIP$CONFIG            Requested configuration:  $               Address  : 10.0.0.1/164               Netmask  : 255.255.0.0 (CIDR bits: 16)               Hostname : liam             * Is this correct [YES]:7         Added hostname liam (10.0.0.1) to host databasem  
         NOTE:C  0           The system hostname is not configured.0           It will now be set to liam (10.0.0.1).I           This can be changed later via the Interface Configuration Menu.   9         Updated system hostname in configuration databasen  <         Added address WE0:10.0.0.1 to configuration database  S               HP TCP/IP Services for OpenVMS Interface & Address Configuration Menu   F               Hostname Details: Configured=liam, Active=Not Configured  $               Configuration options:  :                1  -  WE0 Menu (EWA0: TwistedPair 1000mbps)E                2  -  10.0.0.1/16     liam                  ConfiguredT9                3  -  IE0 Menu (EIA0: TwistedPair 100mbps)l                 [E] -  Exit menu  #         Enter configuration option:r  C               In the above example, Interface WE0 with 10.0.0.1 was F               configured as the address, 16 CIDR bits (255.255.0.0) as6               the netmask, and the hostname as "liam."  E               The address may be entered with the number of CIDR bitstD               or a Netmask. This example used 16 CIDR-bits, which is5               equivalent to a netmask of 255.255.0.0.v  A               Because this is the first address configured on therG               system, it will automatically become the TCP/IP hostname, 5               as is displayed under the "NOTE:" text.   >               The address "10.0.0.1" with a name of "liam" has@               automatically been assigned as the system's TCP/IPE               hostname. This automatic assignment only occurs when no ;               other addresses are configured on the system.c  (         3-18 Configuring TCP/IP Services           H                                              Configuring TCP/IP ServicesH                                                 3.4 Running TCPIP$CONFIG  B               After configuring an address the menu returns to theE               "Interface & Address" menu. It now displays the address B               "10.0.0.1/16" is configure on WE0. The newly createdH               address has its own menu option, "2," which allows furtherB               modification of the specific address. Note that menuD               options for configuring the other interfaces have been?               incremented compared to the first screen capture.p  D               The state of the address is described as "Configured".  1         3.4.4.4 failSAFE IP Address Configuratione  D               To provide high availability of an IP address, you mayE               configure it on multiple interfaces on a node or acrossoB               a cluster, then enable the failSAFE IP service. NoteC               that only one instance of the address will be active;uA               the others will be in standby mode. The failSAFE IP G               service continually monitors the health of interfaces andsF               upon detecting an interface failure, the address will beG               deactivated on the failed interface and a standby addresss!               will become active.o  E               When the failed interface recovers, failSAFE IP detectsi1               this and can return its IP address.   :               Configure the standby IP address as follows:  E               1. From the Core Environment Configuration menu, selectnA                  option 2 (Interfaces). The Interface and AddressS,                  Configuration menu appears.  A               2. From the Interface & Address Configuration Menu,ID                  select the menu item for the IP Address you want toE                  configure as an alias for failSAFE IP, then Option 4cE                  - Add standby aliases to configuration database (forcG                  failSAFE IP), then enter name of the Interface for thee                  failSAFE IP.o  @                  In the following example, 10.10.1.1 was alreadyD                  configured as an alias for interface WE0. (This wasB                  done by selecting the option for an alias addressD                  instead of the option for a primary address.) ThereF                  are now two IP addresses from which to choose for theE                  failSAFE IP. This example uses the 10.10.1.1 for the0E                  failSAFE IP and Interface IE0. Select Option 3, thent5                  Option 4, then enter IE0 as follows:   H                                         Configuring TCP/IP Services 3-19 c         #         Configuring TCP/IP Services           3.4 Running TCPIP$CONFIG  F                 ________________________Note  ________________________  <                 For information on configuring failSAFE IPv6+                 addresses, see Section 4.3.l  E                 _____________________________________________________                                                                               (         3-20 Configuring TCP/IP Services    _      H                                              Configuring TCP/IP ServicesH                                                 3.4 Running TCPIP$CONFIG  R              HP TCP/IP Services for OpenVMS Interface & Address Configuration Menu  E              Hostname Details: Configured=liam, Active=Not Configured   "             Configuration options:  6            1  -  WE0 Menu (EWA0: TwistedPair 1000mbps)A            2  -  10.0.0.1/16     liam                  Configured A            3  -  10.10.1.1/16    abby                  Configured   5            4  -  IE0 Menu (EIA0: TwistedPair 100mbps)u             [E] -  Exit menu  %         Enter configuration option: 3r  F              HP TCP/IP Services for OpenVMS Address Configuration Menu  3               WE0 10.10.1.1/16 abby Configured WEA0i            Configuration options:e  $                  1  - Change address8                  2  - Set "abby" as the default hostname8                  3  - Delete from configuration databaseU                  4  - Add standby aliases to configuration database (for failSAFE IP)                    [E] - Exit menu5  %         Enter configuration option: 4   8         Address 10.10.1.1/16 is currently configured on:              WE0  .         Interfaces available for failover are:  
           IE0h  /         Enter an interface for failSAFE IP: IE0PD         Added alias address IEA0:10.10.1.1 to configuration database  N              The failSAFE IP service, which monitors the health of interfaces,M              is not currently enabled.  Refer to the Optional Components Menut&              to configure the service.  (         Press <ENTER> key to continue...  P            HP TCP/IP Services for OpenVMS Interface & Address Configuration Menu  A          Hostname Details: Configured=liam, Active=Not ConfiguredC            Configuration options:   6            1  -  WE0 Menu (EWA0: TwistedPair 1000mbps)H            2  -  10.0.0.1/16     liam   Configuring TCPConfiguredes 3-21A            3  -  10.10.1.1/26    abby                  Configured   5            4  -  IE0 Menu (EIA0: TwistedPair 100mbps) E            5  -  10.10.1.1/26        abby                  ConfiguredC             [E] -  Exit menu  #         Enter configuration option:n e  f      #         Configuring TCP/IP Services           3.4 Running TCPIP$CONFIG      F               3. When you have started TCPIP services, you return backG                  to the Interace & Address Configuration Menu to verifypE                  that your selected address is now in "standby" mode,c2                  such as in the following example:  O           HP TCP/IP Services for OpenVMS Interface & Address Configuration MenuP  7          Hostname Details: Configured=liam, Active=liamn            Configuration options:   6            1  -  WE0 Menu (EWA0: TwistedPair 1000mbps)L            2  -  16.116.93.75/26     liam                  Configured,ActiveL            3  -  10.10.1.1/26        abby                  Configured,Active  5            4  -  IE0 Menu (EIA0: TwistedPair 100mbps) T            5  -  10.10.1.1/26        abby                  Configured,Active-Standby             [E] -  Exit menu  #         Enter configuration option:f  C                  Note that Item number 5 now has Configured,Active-n'                  Standby as its status.n  T                        HP TCP/IP Services for OpenVMS Address and Configuration Menu  L                         WE0 10.10.1.1/26 abby Configured,Active-Standby WE01  (                   Configuration options:  -                           1  - Change addressfV                           2  - Set "abby.sqa.tcpip.zko.hp.com" as the default hostnameA                           3  - Delete from configuration databaseC6                           4  - Remove from live system^                           5  - Add standby aliases to configuration database (for failSAFE IP)  (                          [E] - Exit menu  ,                  Enter configuration option:  C               4. After configuring the standby IP address, you mustrA                  configure and enable the failSAFE IP service, as .                  explained in Section 3.4.7.2.  (         3-22 Configuring TCP/IP Services s  i      H                                              Configuring TCP/IP ServicesH                                                 3.4 Running TCPIP$CONFIG  F                 ________________________Note  ________________________  ?                 You can also manually configure the failSAFE IPnA                 address using the TCP/IP management SET INTERFACE =                 command or the ifconfig utility. The ifconfigd?                 utility provides a greater degree of management ;                 control and is recommended for more complex @                 environments. For more information, refer to theA                 HP TCP/IP Services for OpenVMS Management manual.   E                 _____________________________________________________Y  -         3.4.4.5 Dynamic Routing Configuratione  D               The following is sample output for configuring dynamic               routing:                                                          H                                         Configuring TCP/IP Services 3-23 n  u      #         Configuring TCP/IP Services           3.4 Running TCPIP$CONFIG  %         DYNAMIC ROUTING Configuration   1          Dynamic routing has not been configured.0  >             You may configure dynamic ROUTED or GATED routing.A             You cannot enable both at the same time.  If you want A             to change from one to the other, you must disable the C             current routing first, then enable the desired routing.   H             If you enable dynamic ROUTED routing, this host will use theD             Routing Information Protocol (RIP) - Version 1 to listenA             for all dynamic routing information coming from othera8             hosts to update its internal routing tables.=             It will also supply its own Internet addresses tow4             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 followingPE             routing protocols to exchange dynamic routing informationg,             with other hosts on the network:B                 Routing Information Protocol (RIP) - Version 1 & 21                 Router Discovery Protocol (RDISC)m/                 Open Shortest Path First (OSPF)T/                 Exterior Gateway Protocol (EGP)T/                 Border Gateway Protocol (BGP-4)r                 Static routesP  U         * Do you want to configure dynamic ROUTED or GATED routing [NO]: YES <Return> J         * Do you want to enable GATED routing configuration [NO]: <Return>               ROUTED option   A             If you enable the 'supply' option of dynamic routing, @             this host will supply dynamic routing information toA             other hosts on the network whether it is acting as an (             internetwork gateway or not.  X         * Do you want this host to supply its dynamic routing information [NO]: <Return>              (         3-24 Configuring TCP/IP Services r  e      H                                              Configuring TCP/IP ServicesH                                                 3.4 Running TCPIP$CONFIG  D               3.4.4.5.1 Default Route Configuration   If you need toD               configure a default route, press <Return> at the firstH               prompt, accepting the default of NO to the dynamic routingF               option, then press <Return> at the next prompt to acceptE               the default of YES to the default route, then enter theeE               name of the gateway and its IP address, as shown in thep                following example:  Q         * Do you want to configure dynamic ROUTED or GATED routing [NO]: [return]o  8                 A default route has not been configured.B         * Do you want to configure a default route [YES]: [return]X         Enter your Default Gateway host name or address: cisco64net.sqa.tcpip.zko.hp.comR                 cisco64net.sqa.tcpip.zko.hp.com is not in the local host database.  P         Enter Internet address for cisco64net.sqa.tcpip.zko.hp.com: 16.116.93.65  +         3.4.4.6 BIND Resolver Configuration   F               To configure the BIND Resolver, select Option 4 from theC               Core Environment Menu, enter the BIND Server name Ande9               address, as shown in the following example:i                                              H                                         Configuring TCP/IP Services 3-25           #         Configuring TCP/IP Servicest          3.4 Running TCPIP$CONFIG  M            HP TCP/IP Services for OpenVMS Core Environment Configuration Menug  &                 Configuration options:  %                          1  -  Domains)                          2  -  Interfacesr&                          3  -  Routing,                          4  -  BIND Resolver(                          5  -  Time Zone  6                          A  -  Configure options 1 - 5(                         [E] -  Exit menu  %         Enter configuration option: 4i  #         BIND RESOLVER Configuratione  8                 A BIND resolver has not been configured.  R                 HP TCP/IP Services for OpenVMS supports the Berkeley Internet NameW                 Domain (BIND) resolver.  BIND is a network service that enables clients U                 to name resources or objects and share information with other objects                  on the network.   M                 Before configuring your system as a BIND resolver, you should N                 first be sure that there is at least one system on the networkK                 configured as either a BIND primary or secondary server forP                 this domain.  E                 You can specify a BIND server by its address or name; C                 however, if specified by name, an entry for it mustT1                 exist in the TCPIP$HOST database.e  ?                 You will be asked one question for each server. A                 Press Return at the prompt to terminate the list.Y  +         Enter your BIND server name: odessyn  9                 odessy is not in the local host database.e  7         Enter Internet address for odessy: 16.116.93.66   $         Enter next BIND server name:  R                 HP TCP/IP Services for OpenVMS Core Environment Configuration Menu  &                 Configuration options:  %                          1  -  Domaing)                          2  -  Interfaces &                          3  -  Routing,                          4  -  BIND Resolver(         3-26 Configuring 5CP-IPTimevZone  6                          A  -  Configure options 1 - 5(                         [E] -  Exit menu  #         Enter configuration option:  N         H                                              Configuring TCP/IP ServicesH                                                 3.4 Running TCPIP$CONFIG  E               To view the current BIND Resolver Configuration, select H               Option 4 from the Core Environment Menu. Press <Return> toF               accept the default if you do not want to reconfigure the?               BIND resolver, as shown in the following example:u  R                 HP TCP/IP Services for OpenVMS Core Environment Configuration Menu  &                 Configuration options:  %                          1  -  Domain )                          2  -  Interfacesi&                          3  -  Routing,                          4  -  BIND Resolver(                          5  -  Time Zone  6                          A  -  Configure options 1 - 5(                         [E] -  Exit menu  %         Enter configuration option: 4t  #         BIND RESOLVER Configuration1  4         A BIND resolver has already been configured.  #         BIND Resolver Configurationo             Transport:  UDPe*           Domain:     sqa.tcpip.zko.hp.com           Retry:         2           Timeout:       5           Servers:    odessy'           Path:       No values definedi  /         * Do you want to reconfigure BIND [NO]:v  E               The following is sample output for configuring the BIND:               resolver:   4         A BIND resolver has already been configured.  #         BIND Resolver Configuratione             Transport:  UDP %           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>  H                                         Configuring TCP/IP Services 3-27 6         #         Configuring TCP/IP Services           3.4 Running TCPIP$CONFIG  >               In this example, no changes are made to the BIND               resolver.t  '         3.4.4.7 Time Zone Configurationo  E               The following is sample output for configuring the time_               zone:_  K           TCPIP uses timezone information provided by the OpenVMS Operating_J           System. No additional timezone configuration is needed for TCPIP<           when the operating system is configured correctly.  K           This section verifies the current OpenVMS timezone configuration. N           A warning message (TCPIP-W-) indicates that corrective action shouldK           be taken. TCPIP will appear to operate but components may display4O           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) changen"         -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 ...  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 to F               configure all the TCP/IP Services components, the ClientE               Components Configuration menu displays next; otherwise, G               the procedure returns to the the Main Configuration menu.S  0         3.4.5 Configuring the Client Environment  B               To display the Client Components Configuration menu,?               choose option 2 (Client 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 Client Components Configuration menuE               displays automatically after you finish configuring the (               core environment services.  G               From the Client Components Configuration menu, choose op-_I               tion A to configure all the client services. Alternatively,PH               you can configure one client service at a time. The sampleF               output in the following sections show the progression of5               the procedure when you choose option A.   (         3-28 Configuring TCP/IP Services x  t      H                                              Configuring TCP/IP ServicesH                                                 3.4 Running TCPIP$CONFIG  F                 ________________________Note  ________________________  =                 Starting with Version 5.4 of TCP/IP Services, ?                 you can configure and use Secure Shell (SSH) to D                 provide secure login, remote command execution, file@                 copying, and file transfer. For more information>                 about configuring, managing, and using the SSH=                 software, refer to the HP TCP/IP Services for %                 OpenVMS Guide to SSH.   C                 The SSH client and server on this version of TCP/IP <                 Services cannot use configuration files from?                 previous versions of SSH. If the SSH client and_A                 server detect systemwide configuration files from.C                 an older version of SSH, the client and server willrA                 fail to start. For more information, refer to theo.                 TCP/IP Services release notes.  E                 _____________________________________________________   K         HP TCP/IP Services for OpenVMS Client Components Configuration Menu            Configuration options:  6                 1  - DHCP Client      Disabled Stopped6                 2  - FTP Client       Enabled  Stopped6                 3  - NFS Client       Enabled  Started6                 4  - REXEC and RSH    Enabled  Started6                 5  - RLOGIN           Enabled  Started6                 6  - SMTP             Enabled  Started6                 7  - SSH Client       Enabled  Stopped6                 8  - TELNET           Enabled  Started6                 9  - TELNETSYM        Disabled Stopped  ,                 A  - Configure options 1 - 9                [E] - Exit menu  G               Note that the sample Client Components Configuration menu A               shows most clients enabled and all of them stopped.e?               Clients are enabled for startup if they have beennC               enabled in the TCP/IP Services configuration databaseCA               (TCPIP$CONFIGURATION.DAT). The enabled services aregC               started the next time TCP/IP Services is started. YouFB               can also start (or stop) a specific service, withoutG               having to restart TCP/IP Services, by choosing the "Start_H               service" option from that service's configuration menu. In  H                                         Configuring TCP/IP Services 3-29           #         Configuring TCP/IP Servicesr          3.4 Running TCPIP$CONFIG  G               addition, you can use command procedures to start or stopeA               a specific service, as explained in Section 3.11.3.   G               The initial status of the services depends on whether you F               have other TCP/IP Services installations in place on theE               system, and whether the software or individual services H               have been started. On a new system, all the services wouldB               be disabled (the default). The status of services isD               also affected by the selections you made from the Core               Environment menu.n  E               To minimize resource consumption, enable and start only H               those services that you are sure to use. Disable those you!               do not plan to use.v  D               To configure all the client services, choose option A.  G               The following is an example of the output for configuringPG               an FTP client. The configuration output for other clients/F               might vary. Note that after you configure a client (suchF               as FTP) that has an associated server, the configurationF               prompts you about whether to configure the corresponding               server.e  .         Enter configuration option: 2 <Return>            FTP CLIENT Configuration  ,         Service is enabled on specific node.         Service is stopped.   2                  FTP CLIENT configuration options:  9                          1 - Disable service on this node   7                          2 - Start service on this node   ;                         [E] - Exit FTP_CLIENT configuration   .         Enter configuration option: 1 <Return>  "         The FTP SERVER is enabled.  A         * Do you want to configure the FTP SERVER [NO] ? <Return>   E               In the preceding example, the FTP client was originally B               enabled, and option 1 disables it. The configurationD               procedure indicates that the FTP server is enabled and<               asks whether you want to configure it as well.  (         3-30 Configuring TCP/IP Services           H                                              Configuring TCP/IP ServicesH                                                 3.4 Running TCPIP$CONFIG  G               The following example shows the configuration output that H               you might see if you want to enable an FTP client that had               been disabled.            FTP CLIENT Configuration           Service is not enabled.a         Service is stopped.s  1                 FTP CLIENT configuration options:i  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/IPdE               Services software has already been started, so you havelG               the choice of starting the client as well as enabling it.tH               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.s  E               If the TCP/IP Services software is not already started,TE               then the FTP Client Components Configuration menu givesnD               you only the option of enabling the service, as in the                following example:  7                         1 - Enable service on this nodei  :                        [E] - Exit FTP_CLIENT configuration  A               After you configure the client service environment, E               press Return or choose option E to exit from the Client B               Components menu. If you chose option A from the MainE               Configuration menu to configure all the TCP/IP Services B               components, the Server Components Configuration menuD               displays next; otherwise, the procedure returns to the*               the Main Configuration menu.    H                                         Configuring TCP/IP Services 3-31 t  >      #         Configuring TCP/IP ServicesO          3.4 Running TCPIP$CONFIG  0         3.4.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 thea               client services.  F                 ________________________Note  ________________________  A                 Starting with Version 5.4 of the TCP/IP Services, ?                 you can configure and use Secure Shell (SSH) to D                 provide secure login, remote command execution, file@                 copying, and file transfer. For more information>                 about configuring, managing, and using the SSH=                 software, refer to the HP TCP/IP Services forCD                 OpenVMS Guide to SSH and the TCP/IP Services release                 notes.  E                 _____________________________________________________d  K         HP TCP/IP Services for OpenVMS Server Components Configuration Menuu  P           1 - BIND         Enabled  Started    12 - NTP         Enabled  StartedP           2 - BOOTP        Disabled Stopped    13 - PC-NFS      Enabled  StartedP           3 - DHCP         Disabled Stopped    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 - SSH         Enabled  StartedP           9 - METRIC       Enabled  Started    20 - TELNET      Enabled  StartedP          10 - NFS          Enabled  Started    21 - TFTP        Enabled  StartedP          11 - LOCKD/STATD  Disabled Stopped    22 - XDM         Enabled  Started  (           A  -  Configure options 1 - 22          [E] -  Exit menu   #         Enter configuration option:t        (         3-32 Configuring TCP/IP Services    o      H                                              Configuring TCP/IP ServicesH                                                 3.4 Running TCPIP$CONFIG  ?               Servers are enabled for startup if they have been A               added to the TCP/IP Services configuration database F               (TCPIP$CONFIGURATION.DAT), and they are started the nextE               time TCP/IP Services is started. You can also start (oriG               stop) a specific server, without having to restart TCP/IPrC               Services, by choosing the "Start service" option fromeH               that server's configuration menu. In addition, you can useG               command procedures to start or stop a specific server, ase*               explained in Section 3.11.3.  F               The initial status of the servers depends on whether youF               have other TCP/IP Services installations in place on theD               system, and whether the software or individual serversB               have been started. To minimize resource consumption,D               enable and start the specific servers you plan to use,F               and disable those you do not plan to use. You can choose4               option A to configure all the servers.  D               For servers that have associated client services (suchC               as the FTP server and client), when you configure theeD               server you are prompted about whether to configure the#               corresponding client.   F                 ________________________Note  ________________________  C                 TELNET and RLOGIN are enabled from the client menu.oC                 If you want to disable the TELNET or RLOGIN server,o?                 then you must disable the service. To enable or C                 disable the TELNET server or the RLOGIN server, use @                 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                 _____________________________________________________.  H               The following is an example of an XDM server configurationH               output. The configuration displays for other servers might               vary.             H                                         Configuring TCP/IP Services 3-33 n  h      #         Configuring TCP/IP Servicess          3.4 Running TCPIP$CONFIG  5               Enter configuration option: 21 <Return>                  XDM Configuration   /               Service is defined in the SYSUAF. C               Service is not defined in the TCPIP$SERVICE database.C%               Service is not enabled.r!               Service is stopped.1  )                XDM configuration options:0  0                  1 - Enable service on this node  ,                 [E] - Exit XDM configuration  )               Enter configuration option:   F                 ________________________Note  ________________________  C                 XDM requires the following DECwindows components ton                 be installed:f  6                 o  SYS$COMMON:[SYSLIB]DECW$XLIBSHR.EXE  9                 o  SYS$COMMON:[SYSLIB]DECW$XTLIBSHRR5.EXE   ?                 The TCPIP$CONFIG configuration procedure checksVC                 whether these components are installed. If they areDB                 not found, TCPIP$CONFIG notifies you and gives you@                 the option of configuring XDM and installing theA                 DECwindows components later before you attempt to @                 activate XDM. The notification and prompt are as                 follows:  J                 XDM requires DECwindows components that are not installed.3                 Attempts to activate XDM will fail.   N                 Type C to continue with XDM configuration, or E to exit [ E ]:  E                 _____________________________________________________s  E               After you configure the servers, press Return or choosekG               option E to exit from the Server Components Configuration E               menu. If you chose option A from the Main ConfigurationrC               menu to configure all the TCP/IP Services components,eG               the Optional Components Configuration menu displays next;:H               otherwise, the procedure returns to the Main Configuration               menu.a  (         3-34 Configuring TCP/IP Services           H                                              Configuring TCP/IP ServicesH                                                 3.4 Running TCPIP$CONFIG  1         3.4.7 Configuring the Optional Components   F               You may need to configure optional product components if:               you plan to do one or more of the following:  E               o  Run the PATHWORKS for OpenVMS (Advanced Server), the C                  Advanced Server for OpenVMS, or DECnet over TCP/IP                   software.  B               o  Run or develop applications that use the StanfordG                  Research Institute's (SRI) QIO application programmingf!                  interface (API).   ,               o  Allow Anonymous FTP access.  B               o  Initialize Kerberos authentication for the TELNET                  server.  H               o  Where a node or cluster has multiple interfaces, enableG                  failSAFE IP to monitor the health of network interfaceiA                  cards and, when an interface fails, to perform apB                  failover to another interface to maintain network                  connectivity.  D               To display the Optional Components Configuration menu,A               choose option 4 (Optional components) from the Main E               Configuration menu. If you chose option A from the MainnE               Configuration menu to configure all the TCP/IP Services D               components, the Optional Components Configuration menuE               displays automatically after you finish configuring thei               servers.  E               The Optional Components Configuration menu displays the %               following menu options:P                      H                                         Configuring TCP/IP Services 3-35           #         Configuring TCP/IP Servicesc          3.4 Running TCPIP$CONFIG  H         HP TCP/IP Services for OpenVMS Optional Components Configuration         Menu           Configuration options:  I                 1 - Configure PWIP Driver (for DECnet-Plus and PATHWORKS)a=                 2 - Configure SRI QIO Interface (INET Driver)a@                 3 - Set up Anonymous FTP Account and Directories3                 4 - Configure Kerberos Applications )                 5 - Configure failSAFE IP   +                 A - Configure options 1 - 5a                [E] - Exit menu  #         Enter configuration option:s  F               Choose the options that are appropriate for your system:C               the PWIP Driver, the SRI QIO Interface, Anonymous FTP C               Accounts and Directories, Kerberos authentication foreC               TELNET, and failSAFE IP (provides IP address failoverhG               capability for multiple interfaces on a host or cluster).t  C               o  If you want to run PATHWORKS for OpenVMS (Advanced E                  Server), Advanced Server for OpenVMS, or DECnet over H                  TCP/IP, configure the PWIP driver by choosing option 1.H                  In addition, refer to the appropriate documentation for%                  the layered product.c  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.   @               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.4.7.1.l  F               o  If you want to provide IP address failover capabilityE                  for multiple interfaces on a host or cluster, chooseaE                  option 5 to configure failSAFE IP. For details aboutoF                  configuring failSAFE IP support, see Section 3.4.7.2.D                  More information is available also in the HP TCP/IP8                  Services for OpenVMS Management manual.  (         3-36 Configuring TCP/IP Services a  "      H                                              Configuring TCP/IP ServicesH                                                 3.4 Running TCPIP$CONFIG  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.e  P          TCPIP Transport for DECnet and Pathworks Service configuration options:  ,             1 - Disable service on this node  /            [E] - Exit PWIP_DRIVER configuratione  #         Enter configuration option:   9         3.4.7.1 Configuring and Enabling Kerberos Supporte  B               To configure the TELNET service to support Kerberos,A               follow these steps. For more details about KerberosuD               features, including prerequisites and instructions forA               using Kerberos, refer to the HP TCP/IP Services for (               OpenVMS Management manual.  F                 ________________________Note  ________________________  C                 Before you begin the following steps, make sure the *                 TELNET service is stopped.  E                 _____________________________________________________e  K               1. From the the TCPIP$CONFIG.COM procedure Main Configuration ;                  menu, choose option 2 (Client components).o  B               2. From the list of client services, choose option 6                  (TELNET).  D               3. From the TELNET Configuration menu, choose option 1E                  (Enable service on all nodes). This step creates thel9                  TCPIP$TELNET user account and directory.A  7               4. Return to the Main Configuration menu.n  B               5. From the Main Configuration menu, choose option 4'                  (Optional components).1  H                                         Configuring TCP/IP Services 3-37 ,  i      #         Configuring TCP/IP Servicesb          3.4 Running TCPIP$CONFIG  A               6. From the Optional Components Configuration menu, C                  choose option 4 (Configure Kerberos Applications).S1                  The following menu is displayed:e  9                  Kerberos Applications Configuration Menuu  N                  TELNET Kerberos is not defined in the TCPIP$SERVICE database.  -                        Configuration options:M  C                                1  -  Add Kerberos for TELNET server.F                                2  -  Remove Kerberos for TELNET server  .                               [E] -  Exit menu  ,                  Enter configuration option:  C               7. From the Kerberos Applications Configuration menu, B                  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.   A              10. Start the TELNET service by executing the TELNEToF                  startup procedure, as shown in the following example:  8                  $ @SYS$STARTUP:TCPIP$TELNET_STARTUP.COMR                  %TCPIP-I-INFO, image SYS$SYSTEM:TCPIP$TELNET_SERVER.EXE installedK                  %TCPIP-I-INFO, image SYS$SYSTEM:TCPIP$TELNET.EXE installed 5                  %TCPIP-I-INFO, logical names created 6                  %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.c  <         3.4.7.2 Configuring and Enabling failSAFE IP Support  ?               Two steps are necessary to configure failSAFE IP:e  C               1. Configure the standby IP address on the interfaces ?                  for which failover is desired, as explained in ?                  Section 3.4.4.4; these are the failover target_4                  interfaces for each home interface.  (         3-38 Configuring TCP/IP Services p  f      H                                              Configuring TCP/IP ServicesH                                                 3.4 Running TCPIP$CONFIG  C               2. Configure failSAFE IP support by choosing option 5iE                  (Configure failSAFE IP) from the Optional Componentsg$                  Configuration menu.  H               In addition, you can configure failSAFE IP IPv6 addresses.7               Information about this is in Section 4.3.   J               Choosing option 5 from the Optional Components ConfigurationG               menu displays the following menu. Note that in this menu,dF               Option 1 (Enable service on all nodes) appears only in aG               cluster configuration. Choose Option 1 to enable failSAFE1C               IP on all nodes in the cluster, or choose option 2 too8               enable failSAFE IP on the local node only.  5                       failSAFE configuration options:t  >                                1 - Enable service on all nodes>                                2 - Enable service on this node  F                                3 - Enable & Start service on this node  ?                               [E] - Exit FAILSAFE configurationn  )               Enter configuration option:o  H               For more details about failSAFE IP, refer to the HP TCP/IP5               Services for OpenVMS Management manual.C  E         3.5 Using TCPIP$CONFIG Option Commands to Bypass TCPIP$CONFIGe             Menuso  A               If you are an experienced TCP/IP Services user, you E               may want to bypass the configuration menus to enable orE0               disable functionality, as follows:  .               1. Log in to the SYSTEM account.  C               2. Run the TCPIP$CONFIG command procedure and includelF                  appropriate options and keywords in the command line,,                  using the following format:  P                  @SYS$MANAGER:TCPIP$CONFIG [option] {DISABLE | ENABLE} [CLUSTER]  A                  In this format, option can be one of the optionsaA                  described in the following table. The table alsoCC                  describes the function of the DISABLE, ENABLE, and "                  CLUSTER keywords.  H                                         Configuring TCP/IP Services 3-39 F         #         Configuring TCP/IP ServicesfK         3.5 Using TCPIP$CONFIG Option Commands to Bypass TCPIP$CONFIG Menuse  H                  _______________________________________________________H                  Option________Description______________________________  F                  ALL           Configures the core environment and all:                                client and server services.  A                  CLIENT        Configures all client services and 0                                related software.  >                  MINIMUM       Configures the domain, InternetE                                interfaces, Rlogin client, FTP client,[D                                FTP server, TELNET client, and TELNET?                                server. Prompts you for optionala*                                components.  A                  SERVER        Configures all servers and relatedk(                                software.  H                  WORKSTATION   Configures the BIND resolver, the domain,D                                dynamic routing, Internet interfaces,E                                time zone, remote login, remote shell,oH                                remote executive, FTP client, FTP server,F                                TELNET client, TELNET server, and SMTP.H                  _______________________________________________________H                  Keyword_______Description______________________________  B                  CLUSTER       Configures all specified componentsF                                clusterwide (except for the BIND serverC                                and SMTP, which you cannot configureN,                                clusterwide).  @                  ENABLE        Enables the specified components.  H                  DISABLE_______Disables_the_specified_components._______  F                  For example, the following command enables the client1                  services for the entire cluster:P  B                  $ @SYS$MANAGER:TCPIP$CONFIG CLIENT ENABLE CLUSTER  F                 ________________________Note  ________________________  C                 The procedure implements two levels of enabling andr@                 disabling: clusterwide and node specific (exceptA                 for SMTP, which is configured and enabled as nodeu                 specific only).e  E                 _____________________________________________________o  (         3-40 Configuring TCP/IP Services s  e      H                                              Configuring TCP/IP ServicesH                             3.6 Making Configuration Changes Take Effect  4         3.6 Making Configuration Changes Take Effect  G               Configuration changes made to TCP/IP Services software dorG               not take effect until you start (or restart) the affectedhB               services. You may need to restart TCP/IP Services orC               simply the individual services affected, as explainedn               in Table 3-3..  H         Table_3-3_Making_Configuration_Changes_Take_Effect______________           When you changer6         the following         Do the following to makeH         services...___________the_changes_take_effect____Comments_______  G         Core environment      Start or restart the       Do this before F         (domain, Internet     TCP/IP Services software.  you run testsF         interface, routing,                              (verificationG         BIND resolver, time                              procedures) oriF         zone)                                            customize theE                                                          environment..C                                                          Methods tolE                                                          start TCP/IPnE                                                          Services areoE                                                          described intE                                                          Sections 3.8SB                                                          and 3.11.  H                                                 (continued on next page)                                  H                                         Configuring TCP/IP Services 3-41           #         Configuring TCP/IP Services 4         3.6 Making Configuration Changes Take Effect  H         Table_3-3_(Cont.)_Making_Configuration_Changes_Take_Effect______           When you changeo6         the following         Do the following to makeH         services...___________the_changes_take_effect____Comments_______  A         Client, server, or    If you did not make        Usage of:H         optional services     changes to the core        startup commandC         only                  environment, you need      proceduresnG                               only start or restart      for individualnD                               each affected service      services isE                               individually. Do this      explained in H                               by choosing the "Start     Section 3.11.3.4                               service" option in the5                               service's configurationa2                               menu. Alternatively,.                               you can use each7                               service's startup commande(                               procedure.  6                               If you also made changes1                               to core environmenth4                               services, start TCP/IPH         ______________________Services._________________________________  F                 ________________________Note  ________________________  A                 You can have the TCP/IP Services software started =                 automatically each time the OpenVMS operating C                 system is rebooted, or you can restart the softwareh7                 manually, as explained in Section 3.11.a  E                 _____________________________________________________a  7         3.7 Stopping TCP/IP Services Using TCPIP$CONFIGa  F               Stop TCP/IP Services on your system by choosing option 5E               (Shutdown HP TCP/IP Services for OpenVMS) from the Mainl>               Configuration menu, as in the following example:            (         3-42 Configuring TCP/IP Services T  P      H                                              Configuring TCP/IP ServicesH                          3.7 Stopping TCP/IP Services Using TCPIP$CONFIG  9         HP TCP/IP Services for OpenVMS Configuration Menuf  "             Configuration options:  )                    1  -  Core environmento*                    2  -  Client components*                    3  -  Server components,                    4  -  Optional components@                    5  -  Shutdown HP TCP/IP Services for OpenVMS?                    6  -  Startup HP TCP/IP Services for OpenVMS "                    7  -  Run tests  0                    A  -  Configure options 1 - 45                   [E] -  Exit configuration procedured  %         Enter configuration option: 5n  F               The TCP/IP Services shutdown procedure displays a seriesH               of messages similar to the following example (the messages5               displayed depend on the configuration):/                 Begin Shutdown...n  N               %TCPIP-I-INFO, TCP/IP Services shutdown beginning at  5-SEP-2004               15:26:14.39n@               %TCPIP-S-SHUTDONE, TCPIP$FINGER shutdown completedD               %TCPIP-S-SHUTDONE, TCPIP$FTP_CLIENT shutdown completed=               %TCPIP-S-SHUTDONE, TCPIP$FTP shutdown completedPE               %TCPIP-S-SHUTDONE, TCPIP$INET_DRIVER shutdown completedp@               %TCPIP-S-SHUTDONE, TCPIP$METRIC shutdown completedD               %TCPIP-S-SHUTDONE, TCPIP$NFS_CLIENT shutdown completed=               %TCPIP-S-SHUTDONE, TCPIP$NFS shutdown completed =               %TCPIP-S-SHUTDONE, TCPIP$NTP shutdown completed ?               %TCPIP-S-SHUTDONE, TCPIP$PCNFS shutdown completed$=               %TCPIP-S-SHUTDONE, TCPIP$POP shutdown completed_D               %TCPIP-S-SHUTDONE, TCPIP$PORTMAPPER shutdown completed?               %TCPIP-S-SHUTDONE, TCPIP$PROXY shutdown completedeE               %TCPIP-S-SHUTDONE, TCPIP$PWIP_DRIVER shutdown completedu?               %TCPIP-S-SHUTDONE, TCPIP$REXEC shutdown completedi@               %TCPIP-S-SHUTDONE, TCPIP$RLOGIN shutdown completed=               %TCPIP-S-SHUTDONE, TCPIP$RSH shutdown completedi>               %TCPIP-S-SHUTDONE, TCPIP$SMTP shutdown completed>               %TCPIP-S-SHUTDONE, TCPIP$SNMP shutdown completedD               %TCPIP-S-SHUTDONE, TCPIP$SSH_CLIENT shutdown completed=               %TCPIP-S-SHUTDONE, TCPIP$SSH shutdown completed   H                                         Configuring TCP/IP Services 3-43 r  r      #         Configuring TCP/IP Services 7         3.7 Stopping TCP/IP Services Using TCPIP$CONFIGt  @               %TCPIP-S-SHUTDONE, TCPIP$TELNET shutdown completed>               %TCPIP-S-SHUTDONE, TCPIP$TFTP shutdown completed=               %TCPIP-S-SHUTDONE, TCPIP$XDM shutdown completedu@               %TCPIP-I-SERVSTOPPED, BIND service already stopped>               %TCPIP-S-SHUTDONE, TCPIP$BIND shutdown completedA               %TCPIP-S-SHUTDONE, TCP/IP Kernel shutdown completed R               %TCPIP-S-SHUTDONE, TCP/IP Services shutdown completed at  5-SEP-2004               15:26:17.78   )               Shutdown request completed.   7         3.8 Starting TCP/IP Services Using TCPIP$CONFIGn  B               After configuring the core environment, start TCP/IPF               Services on your system by choosing option 6 (Startup HPF               TCP/IP Services for OpenVMS) from the Main Configuration0               menu, as in the following example:  9         HP TCP/IP Services for OpenVMS Configuration Menus  "             Configuration options:  )                    1  -  Core environmentf*                    2  -  Client components*                    3  -  Server components,                    4  -  Optional components@                    5  -  Shutdown HP TCP/IP Services for OpenVMS?                    6  -  Startup HP TCP/IP Services for OpenVMSa"                    7  -  Run tests  0                    A  -  Configure options 1 - 45                   [E] -  Exit configuration proceduree  %         Enter configuration option: 6   '               END-Internal-only Comment   H               The TCP/IP Services startup procedure displays a series ofE               messages similar to the following example (the messageso5               displayed depend on the configuration):c          (         3-44 Configuring TCP/IP Services           H                                              Configuring TCP/IP ServicesH                          3.8 Starting TCP/IP Services Using TCPIP$CONFIG           Begin Startup...  F         %TCPIP-I-INFO, TCP/IP Services startup beginning at 5-SEP-2004         15:27:08.34u6         %TCPIP-I-NORMAL, timezone information verifiedE         %RUN-S-PROC_ID, identification of created process is 00000D42f;         %TCPIP-I-SETLOCAL, setting domain and/or local host 2         %TCPIP-I-STARTCOMM, starting communication6         %TCPIP-I-SETPROTP, setting protocol parameters-         %TCPIP-I-DEFINTE, defining interfacesp1         %TCPIP-I-STARTNAME, starting name servicec5         %TCPIP-I-STARTDROUT, starting dynamic routingoE         %RUN-S-PROC_ID, identification of created process is 00000C4EF;         %TCPIP-S-STARTDONE, TCP/IP Kernel startup completed 8         %TCPIP-S-STARTDONE, TCPIP$BIND startup completed8         %TCPIP-I-PROXYLOADED, loaded 0 NFS proxy recordsA         %TCPIP-I-LOADSERV, loading TCPIP server proxy informationnI         %TCPIP-I-SERVLOADED, auxiliary server loaded with 0 proxy recordst@         -TCPIP-I-SERVSKIP, skipped 0 communication proxy records9         -TCPIP-I-SERVTOTAL, total of 0 proxy records reads9         %TCPIP-S-STARTDONE, TCPIP$PROXY startup completedi>         %TCPIP-S-STARTDONE, TCPIP$PORTMAPPER startup completed:         %TCPIP-S-STARTDONE, TCPIP$FINGER startup completed7         %TCPIP-S-STARTDONE, TCPIP$FTP startup completedg>         %TCPIP-S-STARTDONE, TCPIP$FTP_CLIENT startup completed?         %TCPIP-S-STARTDONE, TCPIP$INET_DRIVER startup completedi:         %TCPIP-S-STARTDONE, TCPIP$METRIC startup completedC         %TCPIP-I-NOMAP, no filesystem mapping information availableb7         %TCPIP-S-STARTDONE, TCPIP$NFS startup completed >         %TCPIP-S-STARTDONE, TCPIP$NFS_CLIENT startup completed7         %TCPIP-S-STARTDONE, TCPIP$NTP startup completed.9         %TCPIP-S-STARTDONE, TCPIP$PCNFS startup completed 7         %TCPIP-S-STARTDONE, TCPIP$POP startup completedTE         %RUN-S-PROC_ID, identification of created process is 000002DCn?         %TCPIP-S-STARTDONE, TCPIP$PWIP_DRIVER startup completed 9         %TCPIP-S-STARTDONE, TCPIP$REXEC startup completedy:         %TCPIP-S-STARTDONE, TCPIP$RLOGIN startup completed7         %TCPIP-S-STARTDONE, TCPIP$RSH startup completed 8         %TCPIP-S-STARTDONE, TCPIP$SMTP startup completed7         %TCPIP-S-STARTDONE, TCPIP$SSH startup completed >         %TCPIP-S-STARTDONE, TCPIP$SSH_CLIENT startup completed:         %TCPIP-S-STARTDONE, TCPIP$TELNET startup completed8         %TCPIP-S-STARTDONE, TCPIP$TFTP startup completed    H                                         Configuring TCP/IP Services 3-45 m  ,      #         Configuring TCP/IP Services 7         3.8 Starting TCP/IP Services Using TCPIP$CONFIGy  7         %TCPIP-S-STARTDONE, TCPIP$XDM startup completedsK         %TCPIP-S-STARTDONE, TCP/IP Services startup completed at 5-SEP-2004          15:27:50.47 "         Startup request completed.$         Press Return to continue ...  F                 ________________________Note  ________________________  A                 The TCPIP-I-NOMAP message in this example appears @                 only if no file systems are mapped in the TCP/IPA                 configuration database. If you need NFS services,eC                 set up mapping to a valid file system, as explainedt@                 in the HP TCP/IP Services for OpenVMS Management<                 manual. If you do not need NFS services, you?                 can safely ignore this message; you can preventrA                 recurrence of this message during future startupshB                 by disabling the NFS server using the TCPIP$CONFIG(                 configuration procedure.  E                 _____________________________________________________   '         3.9 Verifying the Configuration   G               You can verify the configuration by running the installa-e0               tion verification procedure (IVP).  C               You should run the IVP if any of the following apply:S  H               o  You loaded the Product Authorization Key (PAK), and youE                  want to verify that the lower-layer software and thee<                  Portmapper service are installed correctly.  F               o  You did not load the PAK, but you want to verify thatF                  TCP/IP Services is installed correctly for DECwindows=                  to display the TCP/IP Services applications.P  C               o  You require the software to transfer device socketoH                  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 it 4                  took to run the test to SYS$OUTPUT.  4               o  You need to test your SNMP service.  (         3-46 Configuring TCP/IP Services y  ,      H                                              Configuring TCP/IP ServicesH                                          3.9 Verifying the Configuration  C               Before you run the IVP, make sure TCP/IP Services hasvC               started and you have SYSPRV, OPER, NETMBX, and TMPMBX_               privileges._  E               You can run the IVP from the TCPIP$CONFIG configurationCE               procedure or by command line at the OpenVMS DCL prompt. B               When you run the IVP from TCPIP$CONFIG, you have theD               option of running an additional test that verifies the!               SNMP configuration.   E         3.9.1 Running the IVP from the TCPIP$CONFIG Command Procedure   C               In the TCP/IP Services for OpenVMS Main ConfigurationeG               menu, choose option 7 (Run tests). The Test menu appears,e*               as in the following example:  0         HP TCP/IP Services for OpenVMS TEST Menu                   Test options:   +                          1  -  Internet IVP1'                          2  -  SNMP IVP   *                          A  -  Tests 1 - 2(                         [E] -  Exit menu           Enter test option:  D               Choose the appropriate option for the test you want to               perform.  9         3.9.2 Running the IVP from the OpenVMS DCL Prompt   F               To run the IVP at the DCL prompt, any time after exitingG               the configuration procedure, enter the following command. ?               This procedure performs the same test as option 1 ;               (Internet IVP) of the TCPIP$CONFIG Test menu.I  #               $ @SYS$TEST:TCPIP$IVPn  B         3.9.3 Verifying the TCP/IP Services Internet Configuration  B               When you choose either option 1 or option A from theA               TCPIP$CONFIG Test menu, or if you run the TCPIP$IVPvF               command procedure at the command line, the IVP tests theE               basic TCP/IP Services software configuration, as in thecG               following example. Here, the test completes successfully:f  H                                         Configuring TCP/IP Services 3-47 t         #         Configuring TCP/IP Services '         3.9 Verifying the Configuration   %         Enter test option: 1 <Return>e         Begin IVP...  "         %%% TCPIP IVP: started %%%  5         UDP/IP test started at 5-SEP-2004 16:13:03.62n3         UDP/IP test ended at 5-SEP-2004 16:13:03.69 B         UDP/IP transferred successfully in 0 seconds 4198400 bytes  5         TCP/IP test started at 5-SEP-2004 16:13:04.20s3         TCP/IP test ended at 5-SEP-2004 16:13:04:28oB         TCP/IP transferred successfully in 0 seconds 4198400 bytes  5         RAW_IP test started at 5-SEP-2004 16:13:41.71c3         RAW_IP test ended at 5-SEP-2004 16:13:41.72 A         RAW_IP transferred successfully in 0 seconds 251000 bytesp  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:l  3               %TCPIP-E-IDENT, explanation of error.h  G               Table 3-4 lists some common problems that cause IVP erroroF               messages. If the recommended action does not correct the>               problem, contact your HP support representative.                              (         3-48 Configuring TCP/IP Services           H                                              Configuring TCP/IP ServicesH                                          3.9 Verifying the Configuration  H               Table_3-4_Troubleshooting_IVP_Errors______________________  H               If_the_problem_is...____Do_the_following..._______________  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.   @               Installation kit is     Request a replacement kit.               defective.  D               IVP fails because the   Register a TCP/IP Services forH               PAK_is_missing._________OpenVMS_PAK.______________________  .         3.9.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:h                 Begin SNMP IVP...d  F               The SNMP IVP requires that TCPIP/IP Services be running.E               It performs the following startups and shutdowns on thetI               SNMP service only (other TCP/IP services are not affected):   B               - If SNMP is running, shuts down SNMP before initial                 configuration *               - Starts SNMP and runs testsB               - Shuts down SNMP and restores initial configuration+               - Before exiting, starts SNMPt  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.h  5                     Saving sysContact: Ralph Nicklebyf4                 Setting sysContact to: Julius Caesar4                  Retrieved sysContact: Julius Caesar2               (Retrieved value matches SET value.)5               Restoring sysContact to: Ralph Nicklebys  H                                         Configuring TCP/IP Services 3-49           #         Configuring TCP/IP Services '         3.9 Verifying the Configuration   <                   Saving snmpEnableAuthenTraps: 2 (disabled);               Setting snmpEnableAuthenTraps to: 1 (enabled) ;                Retrieved snmpEnableAuthenTraps: 1 (enabled) 2               (Retrieved value matches SET value.)<                Restoring snmpEnableAuthenTraps: 2 (disabled)  '               Disabling SET operations.S  C               Deleting temporary read/write community SNMPIVP_6520.   >               Shutting down and restarting the SNMP service...5               Shutting down the SNMP service... done.   3               Starting up the SNMP service... done.t  )               SNMP IVP request completed.(*               Press Return to continue ...  H               If one of the SNMP tests fails, you will see messages such               as the following:   =         SNMPIVP: unexpected text in response to SNMP request:          "No reply." J         See file SYS$SYSDEVICE:[TCPIP$SNMP]TCPIP$SNMP_REQUEST.DAT for more         details..         Verify that SNMP trace is not enabled.5         sysContact could not be retrieved. Status = 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 istE               enabled and needs to be disabled. For information abouttE               SNMP trace, refer to the HP TCP/IP Services for OpenVMSs                Management manual.  F                 ________________________Note  ________________________  C                 If options debug is listed in the resolv.conf file,tB                 the SNMP ivp will fail. Refer to the Release Notes(                 for further information.  E                 _____________________________________________________       (         3-50 Configuring TCP/IP Services    n      H                                              Configuring TCP/IP ServicesH                                      3.10 Additional Configuration Tasks  +         3.10 Additional Configuration Taskss  E               After you run TCPIP$CONFIG and enable the functionalityrC               and components appropriate for your network, you neediB               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.s  9               The additional configuration tasks include:n  F               o  Populating databases (for example, for BIND and DHCP)  )               o  Setting up user accountsI  9               o  Setting up communication and NFS proxiesr  &               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 configuremG               each service, refer to the HP TCP/IP Services for OpenVMSI                Management manual.  2         3.11 Starting and Stopping TCP/IP Services  G               You can use commands in your OpenVMS startup file to haveeH               TCP/IP Services started and stopped automatically when theE               OpenVMS system starts up or shuts down, as explained in C               Section 3.11.1. These commands start and stop all the B               TCP/IP Services components installed on your system.E               Alternatively, you can start and stop individual TCP/IPnB               Services client or server services without affectingA               other TCP/IP Services components currently running.gD               For information about starting and stopping individual+               services, see Section 3.11.3.   B               If necessary, you can start and stop TCP/IP ServicesD               manually, as explained in Section 3.11.2. You can alsoC               start and stop user-written services, as explained in.               Section 3.11.4.o  H                                         Configuring TCP/IP Services 3-51 M  a      #         Configuring TCP/IP Servicesg2         3.11 Starting and Stopping TCP/IP Services  B         3.11.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 theE               SYS$COMMON:[SYSMGR]SYSTARTUP_VMS.COM file to remove theiG               exclamation point (!) from the beginning of the following                line:   0               $!$ @SYS$STARTUP:TCPIP$STARTUP.COM  E               If your system had earlier versions of TCP/IP Services, A               UCX$STARTUP.COM and UCX$SHUTDOWN.COM files might be A               present. These are no longer applicable; delete anybD               definition of them from SYS$MANAGER:SYSTARTUP_VMS.COM.  C               If you want TCP/IP Services to start after you log iniC               to your OpenVMS account, the OpenVMS systemwide loginnE               procedure (typically SYS$MANAGER:SYLOGIN.COM) must haveP8               world read and execute protections (W:RE).  E               To display the current protections, enter the following                command:  6               $ DIR/PROTECTION SYS$MANAGER:SYLOGIN.COM  E               For information about protections, refer to the OpenVMS_               documentation.  =         3.11.2 Starting and Stopping TCP/IP Services Manuallyi  D               To start TCP/IP Services manually, enter the following               command:  *               $ @SYS$STARTUP:TCPIP$STARTUP  C               To stop TCP/IP Services manually, enter the followingC               command:  +               $ @SYS$STARTUP:TCPIP$SHUTDOWN           (         3-52 Configuring TCP/IP Services P  T      H                                              Configuring TCP/IP ServicesH                               3.11 Starting and Stopping TCP/IP Services  8         3.11.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.KH               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.r  E               o  SYS$STARTUP:TCPIP$service_SHUTDOWN.COM allows you to /                  shut down the service service.   >               To preserve site-specific parameter settings andC               commands, create the following files. These files are A               not overwritten when you reinstall TCP/IP Services:o  D               o  SYS$STARTUP:TCPIP$service_SYSTARTUP.COM can be usedB                  as a repository for site-specific definitions andB                  parameters to be invoked when service is started.  E               o  SYS$STARTUP:TCPIP$service_SYSHUTDOWN.COM can be used B                  as a repository for site-specific definitions andD                  parameters to be invoked when service is shut down.  E               In these file names, service is the name of the service E               to be started or shut down. For example, use TCPIP$NTP_ 4               SHUTDOWN to shut down the NTP service.  G               For more information, refer to the HP TCP/IP Services for (               OpenVMS Management manual.  :         3.11.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  B               $ SYS$STARTUP:TCPIP$CUSTOMER_SERVICE_STARTUP service  C               To stop the user-written service, enter the following_               command:  C               $ SYS$STARTUP:TCPIP$CUSTOMER_SERVICE_SHUTDOWN servicec  H                                         Configuring TCP/IP Services 3-53 I  e      #         Configuring TCP/IP Services 2         3.11 Starting and Stopping TCP/IP Services  C               In either command, specify the name of the service as F               defined using the TCP/IP management command SET SERVICE.  F                 ________________________Note  ________________________  =                 Remember that any service name with lowercase <                 characters is interpreted by the startup andC                 shutdown procedures as uppercase unless you enclosel?                 the name in quotation marks. If you defined thebC                 service using quotation marks to preserve the case,fC                 be sure to use quotation marks when you specify thelB                 service name with the startup or shutdown command.  E                 _____________________________________________________n  G         3.12 Specifying TCP/IP Services as the Transport for DECwindowsn              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 commande               procedure:  >               $ DECW$SERVER_TRANSPORTS == "DECNET,LOCAL,TCPIP"  &               Then restart DECwindows:  1               $ @SYS$STARTUP:DECW$STARTUP RESTARTF  C               If DECnet or DECnet-Plus software runs on the system,                start it.e  B               To display DECwindows applications from a DECwindows?               client (remote host) to a DECwindows server (youri/               workstation), proceed as follows:o  4               1. Set up security on the remote host.  C               2. Add the remote client to the local hosts database.o  E               3. Add to SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM theg                   following line:  A                  $ DECW$SERVER_TRANSPORTS == "DECNET,LOCAL,TCPIP"   C               4. Set the display for the applications to the remote                   host:  F                  $ SET DISPLAY/CREATE/NODE=remote-host/TRANSPORT=TCPIP  (         3-54 Configuring TCP/IP Services U  R                  H                                                                        4H         ________________________________________________________________  H                                                         Configuring IPv6      D               After configuring TCP/IP Services for OpenVMS with theH               TCPIP$CONFIG.COM command procedure, you can configure yourE               system to communicate in an IPv6 network environment by =               performing the tasks described in this chapter.   C               Starting with Version 5.5, TCP/IP Services introduced C               many significant changes and improvements to the IPv6 @               configuration procedure (TCPIP$IP6_SETUP.COM). ForC               instructions on configuring your node as an IPv6 hostLE               or router, use the documentation in this chapter ratheryF               than that provided in the HP TCP/IP Services for OpenVMS               Guide to IPv6.  H               The following table describes each section in this chapterH               and, where relevant, indicates the section of the Guide toH               IPv6 that it replaces. The section on configuring failSAFEE               IP IPv6 addresses is newly documented with this release C               of TCP/IP Services for OpenVMS. For information about F               IPv6 concepts and processes, DNS domain name and addressH               registration, and so forth, continue to refer to Chapter 2#               of the Guide to IPv6.i  H               __________________________________________________________E                                                     Replaces Guide to(H               Section..._Describes....______________IPv6_Section_...____  9               4.1        How to configure your      2.5.1r0                          system as an IPv6 host.  9               4.2        How to configure your      2.6.1s2                          system as an IPv6 router.  7               4.3        How to configure failSAFE  N/AtH               ___________IP_IPv6_addresses._____________________________  C               You can configure your node as either an IPv6 host or_F               IPv6 router. You make this choice while running the IPv6  H                                                     Configuring IPv6 4-1 c  t               Configuring IPv6    B               configuration procedure (TCPIP$IP6_SETUP.COM). AfterE               you run this configuration procedure and restart TCP/IP_G               Services, IPv6 processes associated with your choices arec%               started on your system.   F                 ________________________Note  ________________________  D                 Before running the TCPIP$IP6_SETUP.COM configuration=                 procedure, IPv4 must already be configured ono@                 your system. (The TCPIP$CONFIG.COM configuration+                 procedure configures IPv4.)a  D                 If you are upgrading TCP/IP Services from a previous=                 release, you must run the TCPIP$IP6_SETUP.COM .                 configuration procedure again.  E                 _____________________________________________________   G               The IPv6 configuration procedure requires you to specify:a  G               o  Whether the system is to be configured as an IPv6 host_#                  or an IPv6 router.r  D               o  Whether the system needs a 6to4 interface (requiredA                  for communicating between IPv4-only networks and B                  IPv6 sites). If so, you must specify the system'sF                  IPv4 address, the 6to4 tunnel address prefix, whetherD                  the system will support a 6to4 relay router and, if;                  applicable, the address of a relay router.   H               o  You must specify the interface names of interfaces that*                  will be enabled for IPv6.  E               o  Whether to configure an automatic tunnel. If so, youiC                  must also specify the IPv4 address of the tunnel'ss                  endpoint.  H               o  You must specify whether the system requires IPv6-over-F                  IPv4 tunnels. For each tunnel, you need to supply theG                  tunnel's source IPv4 address, the tunnel's destination H                  IPv4 address, and the address prefix for the IPv6-over-D                  IPv4 tunnel. You can create multiple IPv6-over-IPv4                  tunnels.C             4-2 Configuring IPv6 -  C      H                                                         Configuring IPv6    H               o  Whether the system requires IPv6-over-IPv6 tunnels. ForF                  each tunnel, you must supply the tunnel's source IPv6H                  address, the tunnel's destination IPv6 address, and theF                  the address prefix for the IPv6-over-IPv6 tunnel. You<                  can create multiple IPv6-over-IPv6 tunnels.  D               o  Whether the system requires manual IPv6 routes. ForF                  each route, you must supply the address prefix of theG                  destination IPv6 network, the interface to use to send G                  traffic for the route, and the link-local IPv6 address G                  of the first router in the path or the IPv4-compatiblevE                  IPv6 address of the automatic tunnel to use. You can,4                  create multiple manual IPv6 routes.  ;               o  For an IPv6 router, you also must specify:   @                  -  Whether to enable the RIPng protocol on each                     interface.  G                  -  Whether to advertise an IPv6 address prefix on eachvB                     interface and, if so, the IPv6 address prefix.  E                  -  For each tunnel you create, whether to enable the F                     RIPng protocol on the tunnel, whether to advertiseG                     an IPv6 address prefix on the tunnel interface, andM3                     if so, the IPv6 address prefix.y  F                  -  For each manual route you create, the interface toF                     use to forward traffic to the remote IPv6 network.  A               After you use the TCPIP$IP6_SETUP.COM configurationNC               procedure to configure your system as an IPv6 host or H               router, you can optionally configure your system as a BINDG               server (see Chapter 3 of the Guide to IPv6). In addition, H               you can configure failSAFE IP IPv6 addresses, as explained               in Section 4.3.   C               Once you configure IPv6 using the TCPIP$IP6_SETUP.COM C               configuration procedure, you must enable IPv6 on yourOE               system by shutting down and restarting TCP/IP Services.   C               You can make other changes to your IPv6 configuration D               later. Chapter 4 of the Guide to IPv6 describes how to#               make further changes.   H                                                     Configuring IPv6 4-3 6                  Configuring IPv6$         4.1 Configuring an IPv6 Host  $         4.1 Configuring an IPv6 Host  >               To configure your system as an IPv6 host, do the               following:  G               1. Invoke the TCPIP$IP6_SETUP.COM configuration proceduree3                  by entering the following command:i  5                        $ @SYS$MANAGER:TCPIP$IP6_SETUP   B                  The procedure displays information about the IPv6C                  network configuration procedure and tells you thatnG                  you can configure the system as either an IPv6 host orU                   an IPv6 router.  B               2. Choose to configure the system as an IPv6 host byH                  taking the default to the following prompt (press Enter                  or enter NO):  ?                  Configure this system as an IPv6 router? [NO]:,  F               3. At the following prompt, indicate whether you want to,                  configure a 6to4 interface:  8                        Configure a 6to4 interface? [NO]:  E                  A 6to4 interface is needed if this host is connectedSA                  to an IPv4-only network and needs to communicateSE                  with other 6to4 or native IPv6 sites. If this system,C                  is a host within a 6to4 site, do not create a 6to4,F                  interface; a 6to4 address is automatically configured?                  on this system using standard IPv6 mechanisms.,  H                  If you do not want to configure a 6to4 interface, pressH                  Enter. The configuration procedure continues at step 8.  F                  If you want to configure a 6to4 interface, enter YES.C                  The configuration procedure then displays the 6to4 "                  tunnel interface:  4                              The 6to4 tunnel is: TN1  @                  You are prompted to enter information about the/                  interface in subsequent steps.r           4-4 Configuring IPv6 /  S      H                                                         Configuring IPv6H                                             4.1 Configuring an IPv6 Host  0               4. Enter this host's IPv4 address:  X                        Enter this node's IPv4 address to use when generating your site's#                        6to4 prefix:   @                  Enter the IPv4 address in dotted-decimal formatE                  (d.d.d.d). The configuration procedure automatically G                  generates a 6to4 site prefix based on the IPv4 address E                  entered, and displays the prefix as in the following                   example:   A                           Your 6to4 site prefix is: 2002:x:x::/48o  @               5. Enter the address prefix for the 6to4 tunnel in2                  response to the following prompt:  B                        Enter an address prefix to use on interface+                        TN1 [2002:x:x::/64]:P  G                  To accept the IPv6 address prefix generated in step 4,o"                  take the default.  F                 ________________________Note  ________________________  A                 The high-order 48 bits of the 6to4 address prefix :                 must be the same as your 6to4 site prefix.  E                 _____________________________________________________   D               6. Indicate whether you want to configure a 6to4 relay                  router:  ;                        Configure a 6to4 relay router? [NO]:   C                  A relay router is needed to connect your system tomC                  native IPv6 sites. If you do not configure a relayaH                  router, your system can connect to other 6to4 sites but*                  not to native IPv6 sites.  E                  If you do not want to configure a 6to4 relay router, F                  press Enter. The configuration procedure continues at                  step 8.  D                  If you want to configure a 6to4 relay router, enter                  YES.   H                                                     Configuring IPv6 4-5 5  :               Configuring IPv6$         4.1 Configuring an IPv6 Host  7               7. Specify the address of a relay router:0  D                        Enter the 6to4 address of a 6to4 relay router*                        [2002:C058:6301::]:  F                  The address of the default relay router is displayed.F                  To use the default, press Enter. Otherwise, enter the=                  6to4 unicast address of a 6to4 relay router.t  E               8. For each interface on your system, the configuration4G                  procedure asks whether you want to enable IPv6 on that E                  interface, as in the following example, where ddn isY2                  the interface name (such as WE0):  :                       Enable IPv6 on interface ddn? [YES]:  D                  If you want to enable IPv6 on this interface, press0                  Enter; if you do not, enter NO.  F                  If your system has multiple interfaces, the procedure:                  repeats this question for each interface.  D               9. Indicate whether you want to configure an automatic                  tunnel:  S                       Configure an IPv6 over IPv4 automatic tunnel interface? [NO]:   E                  If you do not want to configure an automatic tunnel,SD                  press Enter; the procedure continues at step 11. IfF                  you want to configure an automatic tunnel, enter YES;F                  the procedure displays the automatic tunnel interfaceG                  as in the following example. In step 10, the procedurep6                  prompts you for the tunnel's address.  6                           The automatic tunnel is: TN0  F                 ________________________Note  ________________________  <                 Because of potential IPv4-compatible addressD                 routing problems, HP recommends that you avoid using"                 automatic tunnels.  E                 _____________________________________________________t             4-6 Configuring IPv6 O         H                                                         Configuring IPv6H                                             4.1 Configuring an IPv6 Host  D              10. Enter the IPv4 address to use when constructing the-                  automatic tunnel's endpoint:   J                        Enter this node's IPv4 address to use when creating-                        your automatic tunnel:   @                  Enter the IPv4 address in dotted-decimal format                  (d.d.d.d).i  E              11. The configuration procedure asks whether you want toe<                  create an IPv6-over-IPv4 configured tunnel:  F                        Create IPv6 over IPv4 configured tunnels? [NO]:  C                  If you want to create an IPv6-over-IPv4 configured_D                  tunnel, enter YES. You are prompted for information7                  about this tunnel in subsequent steps.   ?                  If you do not want to create an IPv6-over-IPv4 H                  configured tunnel, press Enter; the procedure continues                  at step 16.  F              12. Enter the tunnel's source IPv4 address in response to&                  the following prompt:  C                        Enter the source IPv4 address of tunnel ITn:m  F                  Enter the tunnel's source IPv4 address in the dotted-*                  decimal format (d.d.d.d).  H              13. Enter the tunnel's destination IPv4 address in response)                  to the following prompt:_  F                      Enter the destination IPv4 address of tunnel ITn:  G                  Enter the tunnel's destination IPv4 address in dotted-nA                  decimal format d.d.d.d. The tunnel's destination D                  address must differ from the source address entered                  in step 12.  H              14. Enter an address prefix to use on the tunnel interface:  N                        Enter an address prefix to use on interface ITn [DONE]:    H                                                     Configuring IPv6 4-7 f  h               Configuring IPv6$         4.1 Configuring an IPv6 Host  G                  If a router is not advertising a global address prefix A                  on this tunnel interface, enter a 64-bit address H                  prefix. You can configure multiple address prefixes forH                  this configured tunnel. You are prompted for additional7                  address prefixes until you enter DONE.s  C                  If you do not want the host to use an IPv6 addressr=                  prefix on the tunnel interface, press Enter.   E              15. The configuration procedure asks whether you want to A                  create another IPv6-over-IPv4 configured tunnel:   M                        Create another IPv6 over IPv4 configured tunnel? [NO]:n  H                  If you want to create another IPv6-over-IPv4 configuredB                  tunnel, enter YES. The procedure repeats steps 12E                  through 14 for each additional configured tunnel youe"                  choose to create.  D                  If you do not want to create another IPv6-over-IPv4H                  configured tunnel, press Enter. The procedure continues                  at step 16.  F              16. Indicate whether you want to create an IPv6-over-IPv6#                  configured tunnel:C  F                        Create IPv6 over IPv6 configured tunnels? [NO]:  H                  If you want to create an IPv6-over-IPv6 configured tun-F                  nel, enter YES. You are prompted to enter information7                  about this tunnel in subsequent steps.   ?                  If you do not want to create an IPv6-over-IPv61B                  configured tunnel, press Enter; the configuration0                  procedure continues at step 21.  F              17. Enter the tunnel's source IPv6 address in response to&                  the following prompt:  C                        Enter the source IPv6 address of tunnel ITn:V  F                  Enter the tunnel's source IPv6 address in the dotted-*                  decimal format (d.d.d.d).  C              18. Enter the IPv6-over-IPv6 tunnel's destination IPv6u=                  address in response to the following prompt:   F                      Enter the destination IPv6 address of tunnel ITn:           4-8 Configuring IPv6 C  P      H                                                         Configuring IPv6H                                             4.1 Configuring an IPv6 Host  H                  Enter an IPv6 address in dotted-decimal format d.d.d.d.F                  The tunnel's destination address must differ from the3                  source address entered in step 17.t  H              19. Enter an address prefix to use on the tunnel interface:  N                        Enter an address prefix to use on interface ITn [DONE]:  G                  If a router is not advertising a global address prefix1A                  on this tunnel interface, enter a 64-bit address%H                  prefix. You can configure multiple address prefixes forH                  this configured tunnel. You are prompted for additional7                  address prefixes until you enter DONE.   C                  If you do not want the host to use an IPv6 address2=                  prefix on the tunnel interface, press Enter.s  E              20. The configuration procedure asks whether you want to1A                  create another IPv6-over-IPv6 configured tunnel:   M                        Create another IPv6 over IPv6 configured tunnel? [NO]:V  H                  If you want to create another IPv6-over-IPv6 configuredB                  tunnel, enter YES. The procedure repeats steps 17E                  through 19 for each additional configured tunnel youA"                  choose to create.  D                  If you do not want to create another IPv6-over-IPv60                  configured tunnel, press Enter.  H              21. The procedure asks whether you want to configure manual                  IPv6 routes.d  :                        Configure manual IPv6 routes? [NO]:  C                  If you want to configure a manual IPv6 route to an-C                  adjacent router or remote IPv6 network, enter YES; A                  subsequent prompts ask you for information about E                  the route. Otherwise, press Enter; the configuration 0                  procedure continues at step 26.  B              22. Indicate the address prefix of a destination IPv6                  network:   D                        Enter the destination network address prefix:  F                  Enter the IPv6 address prefix of the destination IPv6A                  network, or enter DEFAULT for the default route.   H                                                     Configuring IPv6 4-9                    Configuring IPv6$         4.1 Configuring an IPv6 Host  G              23. Enter the name of the interface through which you will 9                  send traffic to the remote IPv6 network:l  G                        Enter interface to use when forwarding messages:     F              24. Enter the link-local IPv6 address of the first routerE                  in the path to the destination network. This address B                  along with the IPv6 address prefix constitute the,                  static routing table entry.  :                        Enter the next node's IPv6 address:  H                  If the next node is on the same link as this node or isG                  reachable through a configured tunnel, enter the link-bE                  local address. If the next node is reachable throughwD                  an automatic tunnel, enter the IPv4-compatible IPv6C                  address. For all other connections, enter the IPv6M                  address.   C              25. Indicate whether you want to define another manual D                  route to an adjacent router or remote IPv6 network:  A                        Configure another manual IPv6 route? [NO]:h  G                  If you want to define another manual route, enter YES.mE                  The configuration procedure repeats steps 22 through D                  24 for each additional manual IPv6 route you chooseG                  to define. If you do not want to define another manual:$                  route, press Enter.  F              26. At this point, the configuration procedure displays aF                  summary of your new IPv6 host configuration, as shown*                  in the following example:  J                          You configured this node as an IPv6 host with the#                          following:o                        Daemons:m  9                        ND6HOST   Dynamic Updates Disabledn                         Interfaces:             4-10 Configuring IPv6t T  s      H                                                         Configuring IPv6H                                             4.1 Configuring an IPv6 Host  F                        WE0       Dynamic Address Configuration EnabledE                        TN1       6to4 Tunneling Enabled using 5.6.7.8 9                                  Prefix 2002:506:708::/64 ?                                  Relay Router 2002:90A:B0C:1::1   #                      Manual Routes:d  J                        2002::/16                   TN1       FE80::5.6.7.8N                        DEFAULT                     TN1       2002:90A:B0C:1::1  B              27. The configuration procedure asks whether you wantE                  to create a new host configuration file based on the_'                  choices you have made:   J                        Create new IPv6 network configuration files? [YES]:  G                  If you are not satisfied with the configuration, enter.G                  NO; the configuration procedure ends immediately with- E                  out changing the current IPv6 network configuration.   C                  If you are satisfied with the configuration, press A                  Enter. The configuration procedure creates a new C                  host configuration file and displays the following_                  information:_  ]                        A  new  IPv6  configuration  file,  SYS$SYSTEM:TCPIP$INET6_CONFIG.DAT, ]                        has been created.  The previous configuration file  (if any)  has been H                        renamed to SYS$SYSTEM:TCPIP$INET6_CONFIG.DAT_OLD.  ]                        This new IPv6 network configuration will become active the  next  time >                        TCP/IP Services for OpenVMS is started.  &         4.2 Configuring an IPv6 Router  D               To configure your system as an IPv6 router, follow the-               steps provided in this section.r  G               1. Invoke the TCPIP$IP6_SETUP.COM configuration procedure 3                  by entering the following command:t  /                  $ @SYS$MANAGER:TCPIP$IP6_SETUPo  B                  The procedure displays information about the IPv6C                  network configuration procedure and tells you thatiG                  you can configure the system as either an IPv6 host orn                   an IPv6 router.  H                                                    Configuring IPv6 4-11                    Configuring IPv6&         4.2 Configuring an IPv6 Router  D               2. Choose to configure the system as an IPv6 router by6                  entering YES at the following prompt:  E                        Configure this system as an IPv6 router? [NO]:   >               3. Indicate whether you want to configure a 6to4                  interface:   8                        Configure a 6to4 interface? [NO]:  A                  A 6to4 interface is needed to configure a border ?                  router. If you do not want to configure a 6to4ID                  interface, press Enter. The configuration procedure%                  continues at step 7.S  F                  If you want to configure a 6to4 interface, enter YES.C                  The configuration procedure then displays the 6to4o"                  tunnel interface:  4                              The 6to4 tunnel is: TN1  @                  You are prompted to enter information about the/                  interface in subsequent steps.c  A               4. Enter the node's IPv4 address in response to theC"                  following prompt:  L                        Enter this node's IPv4 address to use when generating/                        your site's 6to4 prefix:   @                  Enter the IPv4 address in dotted-decimal formatE                  (d.d.d.d). The configuration procedure automatically G                  generates a 6to4 site prefix based on the IPv4 address E                  entered, and displays the prefix as in the followingg                  example:   A                           Your 6to4 site prefix is: 2002:x:x::/48t  ?                  This site prefix is advertised to hosts on theaH                  interfaces attached to the IPv6 site. This address mustG                  be a valid, globally unique IPv4 address configured ons<                  the router's interface to the IPv4 network.               4-12 Configuring IPv6Y O  N      H                                                         Configuring IPv6H                                           4.2 Configuring an IPv6 Router  G               5. The configuration procedure asks whether you want thisd;                  system to function as a 6to4 relay router:R  ;                        Configure a 6to4 relay router? [NO]:s  C                  If hosts in this border router's 6to4 site need toi@                  communicate with native IPv6 sites (IPv6 only),D                  configure this system as a 6to4 relay router. Enter                  YES.t  D                  If you do not want the system to function as a 6to4G                  relay router, press Enter. The configuration proceduret%                  continues at step 7.y  7               6. Specify the address of a relay router:   @                        Enter 6to4 address of a 6to4 relay router*                        [2002:C058:6301::]:  F                  The address of the default relay router is displayed.F                  To use the default, press Enter. Otherwise, enter the=                  6to4 unicast address of a 6to4 relay router.   F               7. For each interface on your system, the procedure asksF                  whether you want to enable IPv6 on that interface, asE                  in the following example, where ddn is the interface $                  name (such as WE0):  9                       Enable IPv6 on interface ddn [YES]?n  D                  If you want to enable IPv6 on this interface, press)                  Enter; if not, enter NO.3  E                  For each interface on your system, the configurationl5                  procedure repeats steps 7 through 9.o  F               8. Indicate whether you want the router to run the RIPng6                  protocol on the designated interface:  <                        Enable RIPng on interface ddn? [YES]:  F                  The RIPng protocol allows this router to exhange IPv6E                  routes with other routers. If you want the router torF                  run the RIPng protocol, press Enter; otherwise, enter                  NO.  H                                                    Configuring IPv6 4-13 A  P               Configuring IPv6&         4.2 Configuring an IPv6 Router  B               9. The configuration procedure asks whether you wantF                  the router to advertise an IPv6 address prefix on the&                  designated interface:  H                        Enter an address prefix to advertise on interface"                        ddn [DONE]:  D                  If you want the router to advertise an IPv6 address>                  prefix, enter a 64-bit address prefix for theG                  interface. You can configure multiple address prefixes D                  for this interface. You are prompted for additional7                  address prefixes until you enter DONE.i  C                  If you do not want the router to advertise an IPv6bH                  address prefix on the designated interface, enter DONE.  D              10. Indicate whether you want to configure an automatic                  tunnel:  T                        Configure an IPv6 over IPv4 automatic tunnel interface? [NO]:  E                  If you do not want to configure an automatic tunnel,MF                  press Enter. The configuration procedure continues at                  step 12.   D                  If you want to configure an automatic tunnel, enterA                  YES; the procedure displays the automatic tunnel G                  interface as in the following example, and in the nextR;                  step prompts you for the tunnel's address.o  6                           The automatic tunnel is: TN0  F                 ________________________Note  ________________________  <                 Because of potential IPv4-compatible addressD                 routing problems, HP recommends that you avoid using"                 automatic tunnels.  E                 _____________________________________________________e  D              11. Enter the IPv4 address to use when constructing the-                  automatic tunnel's endpoint:_  B                        Enter the IPv4 address to use when creating-                        your automatic tunnel:            4-14 Configuring IPv6e e         H                                                         Configuring IPv6H                                           4.2 Configuring an IPv6 Router  @                  Enter the IPv4 address in dotted-decimal format                  (d.d.d.d).o  E              12. The configuration procedure asks whether you want tow<                  create an IPv6-over-IPv4 configured tunnel:  F                        Create IPv6 over IPv4 configured tunnels? [NO]:  C                  If you want to create an IPv6-over-IPv4 configuredaD                  tunnel, enter YES. You are prompted for information7                  about this tunnel in subsequent steps.e  ?                  If you do not want to create an IPv6-over-IPv4EH                  configured tunnel, press Enter; the procedure continues                  at step 18.  8              13. Enter the tunnel's source IPv4 address:  C                        Enter the source IPv4 address of tunnel ITn:   F                  Enter the tunnel's source IPv4 address in the dotted-*                  decimal format (d.d.d.d).  H              14. Enter the tunnel's destination IPv4 address in response)                  to the following prompt:r  F                      Enter the destination IPv4 address of tunnel ITn:  H                  Enter an IPv4 address in dotted-decimal format d.d.d.d.F                  The tunnel's destination address must differ from the3                  source address entered in step 13.$  H              15. Indicate whether you want to enable the RIPng protocol:  <                        Enable RIPng on interface ITn? [YES]:  G                  The RIPng protocol allows this router to exchange IPv6PE                  routes with other routers. If you want to enable the H                  RIPng protocol on the tunnel interface, press Enter; if&                  you do not, enter NO.  E              16. Indicate whether you want the router to advertise an =                  IPv6 address prefix on the tunnel interface:   U                        Enter an address prefix to advertise on interface ITn? [DONE]:p  H                                                    Configuring IPv6 4-15 6  t               Configuring IPv6&         4.2 Configuring an IPv6 Router  D                  If you want the router to advertise an IPv6 address>                  prefix, enter a 64-bit address prefix for theA                  designated interface. You can configure multiple6F                  address prefixes for this interface. You are promptedF                  for additional address prefixes until you enter DONE.  E                  If you do not want the router to use an IPv6 addresss<                  prefix on the tunnel interface, enter DONE.  E              17. The configuration procedure asks whether you want tonA                  create another IPv6-over-IPv4 configured tunnel:   M                        Create another IPv6 over IPv4 configured tunnel? [NO]:I  H                  If you want to create another IPv6-over-IPv4 configuredB                  tunnel, enter YES. The procedure repeats steps 13E                  through 16 for each additional configured tunnel yout"                  choose to create.  D                  If you do not want to create another IPv6-over-IPv40                  configured tunnel, press Enter.  G              18. The procedure asks whether you want to create an IPv6-e-                  over-IPv6 configured tunnel:_  F                        Create IPv6 over IPv6 configured tunnels? [NO]:  H                  If you want to create an IPv6-over-IPv6 configured tun-F                  nel, enter YES. You are prompted to enter information7                  about this tunnel in subsequent steps.   ?                  If you do not want to create an IPv6-over-IPv6PB                  configured tunnel, press Enter; the configuration0                  procedure continues at step 24.  F              19. Enter the tunnel's source IPv6 address in response to&                  the following prompt:  C                        Enter the source IPv6 address of tunnel ITn:   F                  Enter the tunnel's source IPv6 address in the dotted-*                  decimal format (d.d.d.d).  C              20. Enter the IPv6-over-IPv6 tunnel's destination IPv6a=                  address in response to the following prompt:m  F                      Enter the destination IPv6 address of tunnel ITn:           4-16 Configuring IPv6i t  T      H                                                         Configuring IPv6H                                           4.2 Configuring an IPv6 Router  H                  Enter an IPv6 address in dotted-decimal format d.d.d.d.F                  The tunnel's destination address must differ from the3                  source address entered in step 19.   G              21. Indicate whether you want to enable the RIPng protocol_"                  on the interface:  <                        Enable RIPng on interface ITn? [YES]:  G                  The RIPng protocol allows this router to exchange IPv6 F                  routes with other routers. Press Enter if you want toF                  enable the RIPng protocol on this interface; enter NO                  if you do not.t  E              22. Indicate whether you want the router to advertise ant=                  IPv6 address prefix on the tunnel interface:e  U                        Enter an address prefix to advertise on interface ITn? [DONE]:   D                  If you want the router to advertise an IPv6 address>                  prefix, enter a 64-bit address prefix for theA                  designated interface. You can configure multipletF                  address prefixes for this interface. You are promptedF                  for additional address prefixes until you enter DONE.  E                  If you do not want the router to use an IPv6 address-<                  prefix on the tunnel interface, enter DONE.  G              23. You are asked whether you want to create another IPv6-t-                  over-IPv6 configured tunnel:e  M                        Create another IPv6 over IPv6 configured tunnel? [NO]:m  H                  If you want to create another IPv6-over-IPv6 configuredB                  tunnel, enter YES. The procedure repeats steps 19E                  through 22 for each additional configured tunnel youe"                  choose to create.  D                  If you do not want to create another IPv6-over-IPv60                  configured tunnel, press Enter.  H              24. Indicate whether you want to define manual routes to an8                  adjacent router or remote IPv6 network:  :                        Configure manual IPv6 routes? [NO]?  H                                                    Configuring IPv6 4-17 t  a               Configuring IPv6&         4.2 Configuring an IPv6 Router  F                  If you want to define a manual IPv6 route, enter YES.G                  In subsequent steps, the procedure asks you to specifyo,                  information for that route.  F                  If you do not want to define manual routes, enter NO;4                  the procedure continues at step 29.  G              25. Enter an address prefix of a destination IPv6 network:a  D                        Enter the destination network address prefix:  A                  Enter the address prefix of the destination IPv6 A                  network, or enter DEFAULT for the default route.   G              26. Enter the name of the interface through which you will 9                  send traffic to the remote IPv6 network:v  G                        Enter interface to use when forwarding messages:   ?              27. The procedure asks you to enter the link-local D                  IPv6 address of the first router in the path to theF                  destination network. This address along with the IPv6C                  address prefix constitute the static routing table                   entry.n  :                        Enter the next node's IPv6 address:  H                  If the next node is on the same link as this node or isG                  reachable through a configured tunnel, enter the link-oE                  local address. If the next node is reachable throughiD                  an automatic tunnel, enter the IPv4-compatible IPv6C                  address. For all other connections, enter the IPv6v                  address.y  F              28. Indicate whether you want to configure another manual@                  IPv6 route to an adjacent router or remote IPv6                  network:u  A                        Configure another manual IPv6 route? [NO]:   E                  If you want to configure another manual route, enter B                  YES. The configuration procedure repeats steps 25E                  through 27 for each additional manual IPv6 route younE                  choose to configure. If you do not want to configure 3                  another manual route, press Enter.g           4-18 Configuring IPv6  b  n      H                                                         Configuring IPv6H                                           4.2 Configuring an IPv6 Router  F              29. At this point, the configuration procedure displays aH                  summary of your new IPv6 router configuration, as shown*                  in the following example:  L                          You configured this node as an IPv6 router with the#                          following:o                        Daemons:                           IP6RTRD                         Interfaces:  ,                        WE0       RIP Enabled,                        IT0       RIP Enabled2                                  Tunnel Source ::17                                  Tunnel Destination ::2 1                                  Prefix AAAA::/64 1                                  Prefix BBBB::/64kE                        TN1       6to4 Tunneling Enabled using 1.2.3.4I>                                  Relay Router 2002:C058:6301::  #                      Manual Routes:   @                        ::4/64                      WE0       ::5  E              30. The configuration procedure asks whether you want to G                  create router configuration files based on the choices                   you have made:   J                        Create new IPv6 network configuration files? [YES]:  G                  If you are not satisfied with the configuration, entereG                  NO; the configuration procedure ends immediately with- E                  out changing the current IPv6 network configuration.p  C                  If you are satisfied with the configuration, pressq?                  Enter. The configuration procedure creates new F                  router configuration files and displays the following                  information:   ]                        A  new  IPv6  configuration  file,  SYS$SYSTEM:TCPIP$INET6_CONFIG.DAT, ]                        has been created.  The previous configuration file  (if any)  has been H                        renamed to SYS$SYSTEM:TCPIP$INET6_CONFIG.DAT_OLD.  X                        A new IPv6 configuration file, SYS$SYSTEM:TCPIP$IP6RTRD.CONF, hasY                        been created.  The previous configuration file  (if any)  has beeneD                        renamed to SYS$SYSTEM:TCPIP$IP6RTRD.CONF_OLD.  H                                                    Configuring IPv6 4-19 o                  Configuring IPv6&         4.2 Configuring an IPv6 Router  ]                        This new IPv6 network configuration will become active the  next  time >                        TCP/IP Services for OpenVMS is started.    2         4.3 Configuring failSAFE IP IPv6 Addresses  C               Standby failSAFE IP IPv6 addresses must be configured D               manually. IPv6 supports addresses with various scopes;B               only link-local addresses need to be configured withE               standby addresses. (Link-local addresses are those that_D               have high-order bits with the hexadecimal value FE80.)  E               To configure standby failSAFE IP IPv6 addresses, followu               these steps:  G               1. Determine the link-local IPv6 addresses that have been C                  dynamically created on each interface by using thetH                  ifconfig command, as in the following example. The lastE                  line for each interface contains the IPv6 link-localvH                  address. Note that the IPv4 addresses have already beenE                  configured with standby addresses. (The instructionstD                  for configuring IPv4 standby addresses are given in"                  Section 3.4.4.4.)                    $ ifconfig -aG                  IE0: flags=c43<UP,BROADCAST,RUNNING,MULTICAST,SIMPLEX>:,                       failSAFE IP Addresses:a                          inet 16.176.56.81 netmask fffffe00 broadcast 10.0.255.255 (on GRYFFIIE1) \                      *inet 16.176.56.65 netmask ff000000 broadcast 16.255.255.255 ipmtu 15004                      *inet6 fe80::202:a5ff:fe60:a368  G                  IE1: flags=c43<UP,BROADCAST,RUNNING,MULTICAST,SIMPLEX>r,                       failSAFE IP Addresses:a                          inet 16.176.56.65 netmask fffffe00 broadcast 10.0.255.255 (on GRYFFIIE0) [                      *inet 16.176.56.81 netmask fffffe00 broadcast 16.176.57.255 ipmtu 1500 4                      *inet6 fe80::202:a5ff:fe60:a369  ?               2. Create standby IPv6 addresses by executing the B                  following commands, specifying the IPv6 addresses$                  obtained in step 1:  D                  $ ifconfig ie1 inet6 alias fe80::202:a5ff:fe60:a368D                  $ ifconfig ie0 inet6 alias fe80::202:a5ff:fe60:a369             4-20 Configuring IPv6i u  i      H                                                         Configuring IPv6H                               4.3 Configuring failSAFE IP IPv6 Addresses  H                  In this example, the link-local IPv6 address configured?                  on interface IE0 is added to IE1 as a standby. D                  Similarly, the IPv6 address configured on interface2                  IE1 is added to IE0 as a standby.  D               3. Restart the failSAFE IP service to make the config-B                  uration changes take effect (see Section 3.6). ToG                  make the changes take effect each time TCP/IP Services E                  starts, edit SYS$STARTUP:TCPIP$SYSTARTUP.COM and add H                  the following commands, which include the same ifconfig.                  commands specified in step 2:                    $!r+                  $! IPv6 failSAFE Addresses                   $!iD                  $ ifconfig ie1 inet6 alias fe80::202:a5ff:fe60:a368D                  $ ifconfig ie0 inet6 alias fe80::202:a5ff:fe60:a369                  $! D                  $! Restart failSAFE to pick up IPv6 address changes                  $!.7                  $ @sys$startup:tcpip$failsafe_shutdownI6                  $ @sys$startup:tcpip$failsafe_startup                  $!                                             H                                                    Configuring IPv6 4-21 o  i                  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.f  -         A.1 Sample New Installation Procedurel  F               The following example shows a sample installation dialogH               for the TCP/IP Services. In this example, the installationA               takes place on an OpenVMS Alpha system on which theED               product has not been installed. If TCP/IP Services hadG               been installed previously on the system, the installationd;               dialog would differ slightly (see Chapter 2).o  F                 ________________________Note  ________________________  A                 The symbols xx in the following example represent >                 the product's two-digit update version number.  ?                 Output for installations on OpenVMS I64 systems B                 are similar. One difference is the TCP/IP ServicesD                 product name: on OpenVMS I64 systems it is HP I64VMS?                 TCPIP, while on OpenVMS Alpha systems it is DECtA                 AXPVMS TCPIP (as shown in the following example).r  E                 _____________________________________________________r  E         Choose one or more items from the menu separated by commas: 1   0         The following product has been selected:B             DEC AXPVMS TCPIP V5.6-xx               Layered Product  /         Do you want to continue? [YES] <Return>   (         Configuration phase starting ...  V         You will be asked to choose options, if any, for each selected product and forW         any products that may be installed to satisfy software dependency requirements.u  H            Sample New TCP/IP Services Installation and Configuration A-1    E      A         Sample New TCP/IP Services Installation and Configurationr-         A.1 Sample New Installation Procedurec  A         DEC AXPVMS TCPIP V5.6-xx: HP TCP/IP Services for OpenVMS.   J             Copyright 1976, 2006 Hewlett-Packard Development Company, L.P.  5             Hewlett-Packard Development Company, L.P.o  J             HP 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: L             DEC AXPVMS TCPIP V5.6-xx             DISK$ALPHASYS:[VMS$COMMON.]  N         Portion done: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%=         %PCSI-I-PRCOUTPUT, output from subprocess follows ...          % TCPIP-I-PCSI_INSTALLQ         % - Execute SYS$MANAGER:TCPIP$CONFIG.COM to proceed with configuration of          %   HP TCP/IP Services.a	         %o           Portion done: 100%  1         The following product has been installed:rB             DEC VAXVMS TCPIP V5.6-xx               Layered Product  A         DEC VAXVMS TCPIP V5.6-xx: HP TCP/IP Services for OpenVMS.1  F             Check the release notes for current status of the product.  	         $p  .         A.2 Sample New Configuration Procedure  G               The following example shows a sample configuration dialogeH               for the TCP/IP Services, in which the following components               are configured:   !               o  Core environmentd                 o  TELNET client                 o  FTP server   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  H               In this example, the configuration takes place on a systemG               on which the product has never been configured. If TCP/IPrH               Services had been configured previously on the system, the@               dialog would differ significantly (see Chapter 3).    A                 HP TCP/IP Services for OpenVMS Configuration Menue  &                 Configuration options:  /                          1  -  Core environment 0                          2  -  Client components0                          3  -  Server components2                          4  -  Optional components  F                          5  -  Shutdown HP TCP/IP Services for OpenVMSE                          6  -  Startup HP TCP/IP Services for OpenVMS (                          7  -  Run tests  6                          A  -  Configure options 1 - 4;                         [E] -  Exit configuration procedure   %         Enter configuration option: 1   R                 HP TCP/IP Services for OpenVMS Core Environment Configuration Menu  &                 Configuration options:  %                          1  -  Domaine)                          2  -  Interfaces &                          3  -  Routing,                          4  -  BIND Resolver(                          5  -  Time Zone  6                          A  -  Configure options 1 - 5(                         [E] -  Exit menu  %         Enter configuration option: 1t  R                 HP TCP/IP Services for OpenVMS Core Environment Configuration Menu  &                 Configuration options:  %                          1  -  Domain )                          2  -  Interfacese&                          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 Configurations.         A.2 Sample New Configuration Procedure  6                          A  -  Configure options 1 - 5(                         [E] -  Exit menu  %         Enter configuration option: 1.           DOMAIN Configuration  -         Enter Internet domain: yourdomain.com   R                 HP TCP/IP Services for OpenVMS Core Environment Configuration Menu  &                 Configuration options:  %                          1  -  Domain )                          2  -  Interfaces &                          3  -  Routing,                          4  -  BIND Resolver(                          5  -  Time Zone  6                          A  -  Configure options 1 - 5(                         [E] -  Exit menu  %         Enter configuration option: 2t  S               HP TCP/IP Services for OpenVMS Interface & Address Configuration Menug  K          Hostname Details: Configured=Not Configured, Active=Not Configuredr            Configuration options:h  5            1  -  WE0 Menu (EWA0: TwistedPair 100mbps)o  5            2  -  IE0 Menu (EIA0: TwistedPair 100mbps)   5            3  -  IE1 Menu (EIB0: TwistedPair 100mbps)              [E] -  Exit menu  %         Enter configuration option: 1n  M               HP TCP/IP Services for OpenVMS Interface WE0 Configuration Menuc            Configuration options:   2                  1  - Add a primary address on WE01                  2  - Add an alias address on WE0nA                  3  - Enable DHCP client to manage address on WE0l                   [E] - Exit menuM  %         Enter configuration option: 1   E         A-4 Sample New TCP/IP Services Installation and Configuration  r  e      H                Sample New TCP/IP Services Installation and ConfigurationH                                   A.2 Sample New Configuration Procedure  M               HP TCP/IP Services for OpenVMS Interface WE0 Configuration Menuu            Configuration options:   2                  1  - Add a primary address on WE01                  2  - Add an alias address on WE0 A                  3  - Enable DHCP client to manage address on WE0.                   [E] - Exit menu   %         Enter configuration option: 1   >             IPv4 Address may be entered with CIDR bits suffix.7             E.g. For a 16-bit netmask enter 10.0.1.1/16   *         Enter IPv4 Address []: 10.0.1.1/16&         Enter hostname []: yourmachine            Requested configuration:  $               Address  : 10.0.1.1/164               Netmask  : 255.255.0.0 (CIDR bits: 16)$               Hostname : yourmachine  )         * Is this correct [YES]: <Return>   >         Added hostname yourmachine (10.0.1.1) to host database  
         NOTE: 0           The system hostname is not configured.7           It will now be set to yourmachine (10.0.1.1).iI           This can be changed later via the Interface Configuration Menu.s  9         Updated system hostname in configuration database6  <         Added address WE0:10.0.1.1 to configuration database  S               HP TCP/IP Services for OpenVMS Interface & Address Configuration Menu6  H          Hostname Details: Configured=yourmachine, Active=Not Configured            Configuration options:0  5            1  -  WE0 Menu (EWA0: TwistedPair 100mbps)eE            2  -  10.0.1.1/16         yourmachine           Configuredt  5            3  -  IE0 Menu (EIA0: TwistedPair 100mbps)   5            4  -  IE1 Menu (EIB0: TwistedPair 100mbps)c             [E] -  Exit menu  ,         Enter configuration option: <Return>  H            Sample New TCP/IP Services Installation and Configuration A-5    e      A         Sample New TCP/IP Services Installation and Configurationn.         A.2 Sample New Configuration Procedure  R                 HP TCP/IP Services for OpenVMS Core Environment Configuration Menu  &                 Configuration options:  %                          1  -  Domainw)                          2  -  Interfaces &                          3  -  Routing,                          4  -  BIND Resolver(                          5  -  Time Zone  6                          A  -  Configure options 1 - 5(                         [E] -  Exit menu  %         Enter configuration option: 3   %         DYNAMIC ROUTING Configurationn  8                 Dynamic routing has not been configured.  B                 You may configure dynamic ROUTED or GATED routing.E                 You cannot enable both at the same time.  If you wantIE                 to change from one to the other, you must disable the G                 current routing first, then enable the desired routing.   L                 If you enable dynamic ROUTED routing, this host will use theH                 Routing Information Protocol (RIP) - Version 1 to listenE                 for all dynamic routing information coming from othere<                 hosts to update its internal routing tables.A                 It will also supply its own Internet addresses to 8                 routing requests made from remote hosts.  H                 If you enable dynamic GATED routing, you will be able toK                 configure this host to use any combination of the following I                 routing protocols to exchange dynamic routing information 0                 with other hosts on the network:F                     Routing Information Protocol (RIP) - Version 1 & 25                     Router Discovery Protocol (RDISC) 3                     Open Shortest Path First (OSPF) 3                     Exterior Gateway Protocol (EGP)a3                     Border Gateway Protocol (BGP-4) !                     Static routes   H         * Do you want to configure dynamic ROUTED or GATED routing [NO]:  8                 A default route has not been configured.9         * Do you want to configure a default route [YES]:iS         Enter your Default Gateway host name or address: yourgateway.yourdomain.com   E         A-6 Sample New TCP/IP Services Installation and Configurationa p  p      H                Sample New TCP/IP Services Installation and ConfigurationH                                   A.2 Sample New Configuration Procedure  M                 yourgateway.yourdomain.com is not in the local host database.I  G         Enter Internet address for yourgateway.yourdomain.com: 10.0.2.1   R                 HP TCP/IP Services for OpenVMS Core Environment Configuration Menu  &                 Configuration options:  %                          1  -  Domainn)                          2  -  Interfaces &                          3  -  Routing,                          4  -  BIND Resolver(                          5  -  Time Zone  6                          A  -  Configure options 1 - 5(                         [E] -  Exit menu  %         Enter configuration option: 4r  #         BIND RESOLVER Configurationd  8                 A BIND resolver has not been configured.  R                 HP TCP/IP Services for OpenVMS supports the Berkeley Internet NameW                 Domain (BIND) resolver.  BIND is a network service that enables clients U                 to name resources or objects and share information with other objectsf                 on the network.   M                 Before configuring your system as a BIND resolver, you should N                 first be sure that there is at least one system on the networkK                 configured as either a BIND primary or secondary server fore                 this domain.  E                 You can specify a BIND server by its address or name; C                 however, if specified by name, an entry for it must 1                 exist in the TCPIP$HOST database.   ?                 You will be asked one question for each server.EA                 Press Return at the prompt to terminate the list.t  /         Enter your BIND server name: yourserver   =                 yourserver is not in the local host database.6  7         Enter Internet address for yourserver: 10.0.2.2:  -         Enter next BIND server name: <Return>e  R                 HP TCP/IP Services for OpenVMS Core Environment Configuration Menu  H            Sample New TCP/IP Services Installation and Configuration A-7           A         Sample New TCP/IP Services Installation and Configuration .         A.2 Sample New Configuration Procedure  &                 Configuration options:  %                          1  -  Domainc)                          2  -  Interfaces &                          3  -  Routing,                          4  -  BIND Resolver(                          5  -  Time Zone  6                          A  -  Configure options 1 - 5(                         [E] -  Exit menu  @                HP TCP/IP Services for OpenVMS Configuration Menu  &                 Configuration options:  /                          1  -  Core environment 0                          2  -  Client components0                          3  -  Server components2                          4  -  Optional components  F                          5  -  Shutdown HP TCP/IP Services for OpenVMSE                          6  -  Startup HP TCP/IP Services for OpenVMSp(                          7  -  Run tests  6                          A  -  Configure options 1 - 4;                         [E] -  Exit configuration procedure   %         Enter configuration option: 2t  Q               HP TCP/IP Services for OpenVMS Client Components Configuration Menu   &                 Configuration options:  @                          1  -  DHCP Client      Disabled Stopped@                          2  -  FTP Client       Disabled Stopped@                          3  -  NFS Client       Disabled Stopped@                          4  -  REXEC and RSH    Disabled Stopped@                          5  -  RLOGIN           Disabled Stopped@                          6  -  SMTP             Disabled Stopped@                          7  -  SSH Client       Disabled Stopped@                          8  -  TELNET           Disabled Stopped@                          9  -  TELNETSYM        Disabled Stopped  6                          A  -  Configure options 1 - 9(                         [E] -  Exit menu  %         Enter configuration option: 8   E         A-8 Sample New TCP/IP Services Installation and Configurationt t  e      H                Sample New TCP/IP Services Installation and ConfigurationH                                   A.2 Sample New Configuration Procedure           TELNET Configuration  )         Service is defined in the SYSUAF.f9         Service is defined in the TCPIP$SERVICE database.          Service is not enabled.t         Service is stopped.r  -                 TELNET configuration options:R  8                          1 - Enable service on this node  @                          2 - Enable & Start service on this node  7                         [E] - Exit TELNET configuration_  %         Enter configuration option: 2n  B         %TCPIP-I-INFO, image SYS$SYSTEM:TCPIP$TELNET.EXE installed,         %TCPIP-I-INFO, logical names created&         %TCPIP-I-INFO, service enabled:         %TCPIP-S-STARTDONE, TCPIP$TELNET startup completed  )         Press <ENTER> key to continue ...e  Q               HP TCP/IP Services for OpenVMS Client Components Configuration Menu   &                 Configuration options:  @                          1  -  DHCP Client      Disabled Stopped@                          2  -  FTP Client       Disabled Stopped@                          3  -  NFS Client       Disabled Stopped@                          4  -  REXEC and RSH    Disabled Stopped@                          5  -  RLOGIN           Disabled Stopped@                          6  -  SMTP             Disabled Stopped@                          7  -  SSH Client       Disabled Stopped@                          8  -  TELNET           Enabled  Started@                          9  -  TELNETSYM        Disabled Stopped  6                          A  -  Configure options 1 - 9(                         [E] -  Exit menu  ,         Enter configuration option: <Return>  A                 HP TCP/IP Services for OpenVMS Configuration MenuI  &                 Configuration options:  H            Sample New TCP/IP Services Installation and Configuration A-9           A         Sample New TCP/IP Services Installation and Configuration .         A.2 Sample New Configuration Procedure  /                          1  -  Core environmentv0                          2  -  Client components0                          3  -  Server components2                          4  -  Optional components  F                          5  -  Shutdown HP TCP/IP Services for OpenVMSE                          6  -  Startup HP TCP/IP Services for OpenVMSa(                          7  -  Run tests  6                          A  -  Configure options 1 - 4;                         [E] -  Exit configuration procedure   %         Enter configuration option: 3   K         HP TCP/IP Services for OpenVMS Server Components Configuration Menun              Configuration options:  U             1 - BIND         Disabled Stopped      12 - NTP          Disabled StoppediU             2 - BOOTP        Disabled Stopped      13 - PC-NFS       Disabled StoppednU             3 - DHCP         Disabled Stopped      14 - POP          Disabled Stopped1U             4 - FINGER       Disabled Stopped      15 - PORTMAPPER   Disabled Stopped U             5 - FTP          Disabled Stopped      16 - RLOGIN       Enabled  StarteddU             6 - IMAP         Disabled Stopped      17 - RMT          Disabled Stopped U             7 - LBROKER      Disabled Stopped      18 - SNMP         Disabled Stopped U             8 - LPR/LPD      Disabled Stopped      19 - SSH          Disabled Stopped U             9 - METRIC       Disabled Stopped      20 - TELNET       Enabled  StartedaU            10 - NFS          Disabled Stopped      21 - TFTP         Disabled StoppediU            11 - LOCKD/STATD  Disabled Stopped      22 - XDM          Disabled Stoppede  *             A  -  Configure options 1 - 22            [E] -  Exit menu   %         Enter configuration option: 5t           FTP Configuration   )         Service is defined in the SYSUAF.e9         Service is defined in the TCPIP$SERVICE database.          Service is not enabled.          Service is stopped.e  *                 FTP configuration options:  8                          1 - Enable service on this node  @                          2 - Enable & Start service on this node  F         A-10 Sample New TCP/IP Services Installation and Configuration g  d      H                Sample New TCP/IP Services Installation and ConfigurationH                                   A.2 Sample New Configuration Procedure  4                         [E] - Exit FTP configuration  %         Enter configuration option: 2   E         %TCPIP-I-INFO, image SYS$SYSTEM:TCPIP$FTP_CHILD.EXE installedtF         %TCPIP-I-INFO, image SYS$SYSTEM:TCPIP$FTP_SERVER.EXE installed,         %TCPIP-I-INFO, logical names created&         %TCPIP-I-INFO, service enabled7         %TCPIP-S-STARTDONE, TCPIP$FTP startup completedt  )         Press <ENTER> key to continue ...   &         The FTP CLIENT is not enabled.  3         * Do you want to configure FTP CLIENT [NO]:   K         HP TCP/IP Services for OpenVMS Server Components Configuration Menu               Configuration options:  U             1 - BIND         Disabled Stopped      12 - NTP          Disabled Stopped U             2 - BOOTP        Disabled Stopped      13 - PC-NFS       Disabled StoppednU             3 - DHCP         Disabled Stopped      14 - POP          Disabled Stopped U             4 - FINGER       Disabled Stopped      15 - PORTMAPPER   Disabled StoppedaU             5 - FTP          Enabled  Started      16 - RLOGIN       Enabled  StartediU             6 - IMAP         Disabled Stopped      17 - RMT          Disabled Stopped U             7 - LBROKER      Disabled Stopped      18 - SNMP         Disabled Stopped U             8 - LPR/LPD      Disabled Stopped      19 - SSH          Disabled StoppeddU             9 - METRIC       Disabled Stopped      20 - TELNET       Enabled  StartedsU            10 - NFS          Disabled Stopped      21 - TFTP         Disabled Stopped U            11 - LOCKD/STATD  Disabled Stopped      22 - XDM          Disabled Stoppedh  *             A  -  Configure options 1 - 22            [E] -  Exit menu:  ,         Enter configuration option: <Return>  A                 HP TCP/IP Services for OpenVMS Configuration Menue  &                 Configuration options:  /                          1  -  Core environment 0                          2  -  Client components0                          3  -  Server components2                          4  -  Optional components  H           Sample New TCP/IP Services Installation and Configuration A-11 t  d      A         Sample New TCP/IP Services Installation and Configurationu.         A.2 Sample New Configuration Procedure  F                          5  -  Shutdown HP TCP/IP Services for OpenVMSE                          6  -  Startup HP TCP/IP Services for OpenVMSe(                          7  -  Run tests  6                          A  -  Configure options 1 - 4;                         [E] -  Exit configuration proceduret  %         Enter configuration option: 6            Begin Startup...  S         %TCPIP-I-INFO, TCP/IP Services startup beginning at 22-JUN-2006 09:18:20.58 6         %TCPIP-I-NORMAL, timezone information verified  E         %RUN-S-PROC_ID, identification of created process is 00000896 ;         %TCPIP-I-SETLOCAL, setting domain and/or local host-2         %TCPIP-I-STARTCOMM, starting communication6         %TCPIP-I-SETPROTP, setting protocol parameters-         %TCPIP-I-DEFINTE, defining interfaces 1         %TCPIP-I-STARTNAME, starting name service ;         %TCPIP-S-STARTDONE, TCP/IP Kernel startup completed ?         %TCPIP-I-NOSERVICES, no services configured for startup28         %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 read 9         %TCPIP-S-STARTDONE, TCPIP$PROXY startup completedPX         %TCPIP-S-STARTDONE, TCP/IP Services startup completed at 22-JUN-2006 09:18:23.54  "         Startup request completed.1         Press <ENTER> key to continue ...<Return>   A                 HP TCP/IP Services for OpenVMS Configuration Menun  &                 Configuration options:  /                          1  -  Core environmenta0                          2  -  Client components0                          3  -  Server components2                          4  -  Optional components  F                          5  -  Shutdown HP TCP/IP Services for OpenVMSE                          6  -  Startup HP TCP/IP Services for OpenVMS (                          7  -  Run tests  F         A-12 Sample New TCP/IP Services Installation and Configuration g         H                Sample New TCP/IP Services Installation and ConfigurationH                                   A.2 Sample New Configuration Procedure  6                          A  -  Configure options 1 - 4;                         [E] -  Exit configuration procedure   %         Enter configuration option: E                                                                                   H           Sample New TCP/IP Services Installation and Configuration A-13 r  h                          E      ________________________________________________________________a  E                                                                 Indexi    @      A                                    Configuration database1      ___________________________            files ?      Advanced Server for OpenVMS           creating,  3-10, A-3 A        configuring, 3-35                  Configuration procedure A      Anonymous FTP                         See Configuring TCP/IPaD        configuring, 3-35                      Services; TCPIP$CONFIGE      Automatic configuration of               configuration proceduredB         TCP/IP Services, 3-5              Configuration worksheet,  /      B                                      1-9oE      ___________________________          Configuring TCP/IP Servicesm@      BG device message                     See also TCPIP$CONFIGE        during installation, 2-5               configuration procedureg:      BIND resolver                         automatic,  3-5D        configuring, 3-25, A-3              client environment,  3-285      BIND server                              to 3-31oA        configuring, 3-32                   client services,  3-30 >      Booting OpenVMS,  1-6, 2-5            configuration filesA        precaution, 2-6                        creating new,  3-10lE      BOOTP server                          core environment,  3-12 to62        configuring, 3-32                      3-28  ?      C                                     description of major 9      ___________________________              tasks,  1-1r5      CD-ROM distribution kit               IPv6,  4-1tB        inspecting, 1-3                     new configuration,  1-1E      Client environment                    optional components,  3-351C        configuring, 3-28, A-3              postconfiguration tasks, 2      Client services                          3-51B        starting and stopping               preliminary tasks,  3-1D          individually,  3-53               server environment,  3-32  5                                               to 3-34o?                                            servers,  3-32, 3-34y  E                                                               Index-1a n  l            G         Configuring TCP/IP Services         Configuring TCP/IP ServiceseA           (cont'd)                            TCPIP$CONFIG output A          tasks, recommended                      example (cont'd)i  B             sequence,  3-2                       Server ComponentsG          TCPIP$CONFIG menus,  3-12                  Configuration menu, =          TCPIP$CONFIG menus,                        3-32, A-3t:             description,  3-10                   time zoneA          TCPIP$CONFIG option                        configurationTB             commands,  3-39                         example, 3-28,7          TCPIP$CONFIG output                        A-3 B             example,  A-3 to A-13                XDM Configuration>             beginning,  3-9                         menu, 3-33A             BIND resolver,  3-27              time required,  1-2oG             Client Environment                verifying services,  3-46d<                Configuration menu,          Core EnvironmentB                3-29, A-3                       Configuration menu,8             Core Environment                   3-13, A-3"                Configuration menu,G                3-13, A-3                    D__________________________ :             creating database               Database filesB                files,  3-10, A-3              creating,  3-10, A-3>             Dynamic Routing                 DECnet over TCP/IPD                Configuration menu,            configuration example,5                3-23, A-3                         3-37eG             failSAFE configuration            configuring to use,  3-35t6                ,  3-22, A-3                 DECwindowsE                options,  3-39                 components required forv:             FTP Client                           XDM, 3-34E                Configuration menu,            defining TCP transport, 5                3-30                              3-54nF             Interface                         requirements for productB                Configuration menu,               installation, 1-47                3-14                         DHCP client4@             Kerberos Applications             configuring,  3-297                Configuration menu,          DHCP serverc@                3-38                           configuring,  3-32@             Main Configuration                configuring TCP/IP>                menu,  3-10, A-3                  Services, 3-50             Optional Components             DiskF                Configuration menu,            space requirements,  1-5F                3-35, A-3                      system, backing up,  1-4               PWIP configuration                example,  3-37n           Index-2f :  8                     Distribution kitG          inspecting,  1-3                   G__________________________ ?         Domain                              Global pagelets andf7          configuring,  3-14, A-3               sections >         Dynamic routing                       increasing,  1-6@          configuring,  3-23, A-3              requirements,  1-6  -         E__________________________         IeG         EAK                                 ___________________________hG                                             Installing TCP/IP Services, 9          See Early Adopters Kits               2-1 to 2-7 A             (EAKs)                            configuration phase D         Early Adopters Kits (EAKs),              sample output,  2-4=           1-8                                 execution phase D         Error messages                           sample output,  2-5C          at SNMP verification,                installed files,  2-6 ?             3-50                              major tasks,  1-1 D          IVP (installation                    new installation,  A-2F             verification procedure)           sample output,  2-4, A-1A             ,  3-48                           time required,  1-2a5          TCPIP-I-NOMAP,  3-46               Interface ?                                               configuring,  A-3 G         F__________________________           first-time configuration, 5         failSAFE IP                              3-14eC          configuration options              Interface Configuration 9             menu,  3-39                        menu, 3-14e.          configuring,  3-35, 3-36           IPF          configuring and enabling             configuring interface IP>             client,  3-38                        address, 3-160          configuring IP address,            IPv6?             3-19                              configuring,  4-1@7          configuring target IP                EAK,  1-8@D             address,  3-16, A-3               failSAFE IP addresses,5          defined,  3-36                          4-20 @          EAK,  1-9                            warning message inC          IPv6 addresses,  4-20                   TCPIP$CONFIG, 3-13 5         FINGER server                       IPv6 host_?          configuring,  3-32                   configuring,  4-4P7         FTP client                          IPv6 router @          configuring,  3-30                   configuring,  4-11=         FTP server                          IVP (installationiF          configuring,  3-32, A-3               verification procedure)@                                               description,  3-46C                                               error messages,  3-48/<                                               example,  3-47  H                                                                  Index-3                          IVP (installation G           verification procedure)           N__________________________   6           (cont'd)                          NFS client  @          OpenVMS TEST menu,  3-47             configuring,  3-296          SNMP verification example          NFS server@             ,  3-49                           configuring,  3-32F                                             NOMAP error message,  3-46A         K__________________________         Nonpaged dynamic poole>         Kerberos                              increasing,  1-76          benefits,  3-36                    NTP server@          configuration menu,  3-38            configuring,  3-32  -          configuring and enabling,          O G             3-37                            ___________________________o;          configuring to use,  3-35,         OpenVMS Cluster G             3-36                              configuring TCP/IP beforeT=                                                  joining, 3-5nG         L__________________________           joining as a TCP/IP host,.4         LBROKER server                           3-4=          configuring,  3-32                   running a newly G         License Product                          configured TCP/IP host 8           Authorization Key                      in, 3-4F                                             OpenVMS License Management=          See PAK                               Facility (LMF)cD         LOCKD/STATD server                    using to register PAK,4          configuring,  3-32                      1-4D         LPR/LPD client                      OpenVMS operating system?          configuring,  3-29                   reboot,  1-6, 2-5 A         LPR/LPD server                           precaution,  2-6l=          configuring,  3-32                   upgrading,  1-4p  D                                             OpenVMS TEST menu,  3-47?         M__________________________         Optional components   A         Memory                                Advanced Server for >          physical memory                         OpenVMS, 3-36B             requirements,  1-5                Anonymous FTP,  3-36H         Menus                                 configuration menu,  3-35,4          TCPIP$CONFIG,  3-10                     A-3@         METRIC server                         failSAFE IP,  3-36F          configuring,  3-32                   Kerberos authentication,5         Mixed-case service names,                3-36oA           3-53                                PATHWORKS (Advancede>                                                  Server), 3-36@                                               PWIP driver,  3-36F                                               SRI QIO interface,  3-36           Index-4                  9                                             RLOGIN server @         P__________________________           configuring,  3-326         PAK                                 RMT server@          registering,  1-4                    configuring,  3-323         PATHWORKS                           RoutingeD          configuring,  3-35, 3-37             default configuration,5          Internet Protocol driver                3-25   -             See PWIP                        StG         PC-NFS server                       ___________________________ 8          configuring,  3-32                 Secure Shell5         POLYCENTER Software                   See SSHi3           Installation utility              Servers H          for installing or                    configuration menu,  3-32,4             upgrading,  2-1 to                   A-3C             2-7                               starting and stoppingnC         Pool, nonpaged dynamic,                  individually, 3-53 9           1-7                               Service names ?         POP server                            for user-supplied ?          configuring,  3-32                      services, 3-53 ?         PORTMAPPER server                     mixed-case,  3-53 4          configuring,  3-32                 Services:         Postconfiguration tasks,              user-written@           3-51                                   starting up andG         Preconfiguration tasks,                     shutting down, 3-53oF           3-1                               Shutdown command procedureC         PWIP                                  failure of,  1-6, 2-6 F          configuring,  3-36, 3-37             for individual services,5                                                  3-53oG         R__________________________           for user-written service,o5         Reboot, 2-6                              3-53v=          precaution,  2-6                     invoking,  3-52 C         Release notes                         output example,  3-43iB          extracting into a .TXT               version to use,  2-2  @             file,  1-4                      Shutting down TCP/IP7          location after                        Servicesl  A             installation,  2-6                See Stopping TCP/IP 9         REXEC and RSH client                     Servicesg7          configuring,  3-29                 SMTP client @         RIGHTSLIST database, 3-1              configuring,  3-290         RLOGIN client                       SNMP<          configuring,  3-29                   testing,  3-49@                                               verification error?                                                  messages, 3-50   H                                                                  Index-5 i                        SNMP (cont'd)rG          verification example,              T__________________________4  1             3-49                            TasksmC         SNMP server                           major, installing and A          configuring,  3-32                      configuring, 1-1 ;         SRI QIO                             TCP/IP ServicestG          configuring to use,  3-35            and Anonymous FTP access,u5         SSH                                      3-36C=          configuration note,  3-29,           client servicestF             3-32                                 configuring,  3-28 to8          EAK,  1-9                                  3-31F         SSH client                               starting and stoppingF          configuring,  3-29                         individually, 3-53D         SSH server                            configuration,  3-2 to5          configuring,  3-32                      3-50 :         Starting TCP/IP Services,                new,  A-2A           3-51                                configuration filesm@          after configuration,  3-44              converting from<          automatically,  3-52                       previousF          manually,  3-52                            configuration, 3-8G          using TCPIP$CONFIG,  3-44            configuration preparationP6         Startup command procedure                , 1-9>          failure of,  1-6, 2-6                core environmentF          for individual services,                configuring,  3-12 to8             3-53                                    3-28G          for user-written service,            installation,  2-1 to 2-7 :             3-53                                 new,  A-1G          invoking,  3-52                      installation preparation, ;          output example,  3-44,                  1-2 to 1-9 5             A-13                              servers:F         Stopping TCP/IP Services,                configuring,  3-32 to8           3-51                                      3-34F          automatically,  3-52                    starting and stoppingF          manually,  3-52                            individually, 3-53<          using TCPIP$CONFIG,  3-42            starting afterD         System Authorization File                configuration, 3-41C           (SYSUAF),  3-1                      starting and stoppingoD          OpenVMS Cluster,  3-4                   automatically, 3-52C         System parameters                     starting and stoppinga          checking and changing?             before installing,  1-6              manually, 3-52 <             to 1-7                            starting usingC                                                  TCPIP$CONFIG, 3-44M           Index-6a 1  b            F         TCP/IP Services (cont'd)            TCPIP$CONFIG configurationA          stopping using                        procedure (cont'd)   @             TCPIP$CONFIG,  3-42               PWIP configuration>          upgrading,  2-1 to 2-7                  example, 3-37?          verifying,  3-46                     Server Components D         TCPIP$CONFIG configuration               Configuration menu,:           procedure                              3-32, A-3  E          See also Configuring                 time zone configurationtC             TCP/IP Services                      example, 3-28, A-3 E          BIND resolver                        XDM Configuration menu, 5             configuration,  3-27                 3-33 G          Client Environment                 TCPIP$IP6_SETUP.COM command 8             Configuration menu,                procedure@             3-29, A-3                         introduction,  4-1C          Core Environment                   TCPIP$IP6_SETUP command 8             Configuration menu,                procedureA             3-13, A-3                         configuring an IPv6 =          Dynamic Routing                         router, 4-11 D             Configuration menu,               configuring IPv6 host,4             3-23, A-3                            4-4G          failSAFE configuration             TCPIP-I-NOMAP error message 5             example,  3-22, A-3                , 3-46t9          failSAFE configuration             TELNET clientoE             options menu,  3-39               configuring,  3-29, A-3o9          FTP Client Configuration           TELNET server @             menu,  3-30                       configuring,  3-327          Interface Configuration            TFTP server @             menu,  3-14                       configuring,  3-325          Kerberos Applications              Time zoneoE             Configuration menu,               configuring,  3-28, A-3 ;             3-38                            Troubleshooting E          Main Configuration menu,             configuration procedurei?             3-10, A-3                            problems, 3-48   -          menus                              UFG             description,  3-10              ___________________________ 5          Optional Components                UIC codes =             Configuration menu,               assigning,  1-7RF             3-35, A-3                       Upgrading TCP/IP Services,9          output example,  3-9 to               2-1 to 2-7u7             3-39, A-3 to A-13               User access B          output example, creating             configuring to allowF             database files,  3-10,               Anonymous FTP access,5             A-3                                  3-35n  H                                                                  Index-7 e  e            @         User identification code            Verifying the TCP/IPF           (UIC)                                Services configuration,3          assigning,  1-7                       3-46e  G         V__________________________         X__________________________p  6         Verifying the SNMP                  XDM server<           configuration,  3-49                and DECwindowsC                                                  requirements, 3-34 @                                               configuring,  3-33                                                                               Index-8g                                                                                                                                                                                                                                                                                                                                                                                                        rt.horseracing!6$ uk.sport.horseracing.point-to-point! uk.sport.ice-hockey! uk.sport.misc! uk.sport.motorsport! uk.sport.motorsport.formula1!  uk.sport.orienteering! uk.sport.speedway! uk.sport.squash! uk.tech.broadcast! uk.tech.digital-tv!s uk.tech.digital-tv.crypt!. uk.tech.electronic-security! uk.tech.home-automation!
 uk.tech.misc!. uk.tech.robotics!l uk.tech.rocketry!s uk.tech.tv.sky!s uk.tech.tv.video.pvr!7 uk.telecom!. uk.telecom.broadband!! uk.telecom.mobile! uk.test!
 uk.transport!s uk.transport.air!. uk.transport.buses!8 uk.transport.ferry!  uk.transport.london!
 ukr.archives!  ukr.bicycle! ukr.commerce.auto! ukr.commerce.chemical! ukr.commerce.construction! ukr.commerce.energy! ukr.commerce.estate! ukr.commerce.food! ukr.commerce.household!c ukr.commerce.infoserv! ukr.commerce.machinery!. ukr.commerce.metals! ukr.commerce.misc! ukr.commerce.money!  ukr.commerce.orgtech!l ukr.commerce.price-lists!1 ukr.commerce.talk! ukr.comp.binaries! ukr.comp.dbms.informix!l ukr.comp.hardware! ukr.comp.software!
 ukr.fido.os2!s ukr.fido.os2.announce! ukr.fido.os2.prog! ukr.finance! ukr.gc.chronical!4 ukr.gc.normativ!
 ukr.humright!e ukr.law! ukr.musics!  ukr.netnews!
 ukr.politics!.
 ukr.rules! ukr.science!	 ukr.test!. um.chinese!l um.comp-iss! um.forsale!! um.general!e um.h19!c um.housing!!	 um.music!. um.network!. um.org.mac-usergroup!s um.test! um.umcptalk! um.wam!c um.wam.bmgt301!c umiami.cs.announce!l umiami.general!. umich.academic.competitions! umich.announce.umnet!i
 umich.biking!2 umich.caen.announce! umich.class.test!c& umich.class.testing.once.again.ignore!
 umich.confer!. umich.eecs.announce! umich.eecs.ce.students!! umich.eecs.dco.announce! umich.eecs.dco.stats!s umich.eecs.dco.test!
 umich.geo! umich.housing.ethernet!s umich.ifs.outages! umich.interesting.people!t umich.isr.ahead! umich.itd.stats! umich.kinesiology.gradvice!l umich.linux! umich.michigan.review!
 umich.novell!l umich.org.bsn! umich.org.continuum! umich.org.lsasg! umich.org.tbp! umich.org.umec!s umich.org.umec.graduation! umich.physics.general!
 umich.rha!
 umich.sports!. umich.test.2mod! umich.test.mod!o umich.test.mod3! umich.test.woof! umich.umce.dialin! umich.umce.dns!h umich.umce.ifs!c umich.umce.lars+mars!s umich.umce.usenet! umich.umd.general! umn.aem.general! umn.aem.gradst!- umn.aem.net! umn.aem.seminars!a umn.aem.ugrads!a umn.avian.turkey!. umn.cbs.announce!! umn.cbs.general!
 umn.cbs.test!! umn.cems.ugrads! umn.cis.announce!a umn.cis.general! umn.cis.minnext! umn.cis.systems!
 umn.cis.test!s umn.coled.alumni!i umn.comp.ftp-mirror! umn.comp.os.unix!! umn.comp.os.vms! umn.comp.sys.ibm!c umn.comp.sys.mac!! umn.comp.sys.sgi!. umn.comp.sys.sun!o umn.config!s umn.cs.bldg! umn.cs.class.3317ext!o umn.cs.class.3321ext!  umn.cs.class.8011-scic!. umn.cs.curriculum! umn.cs.dept! umn.cs.faculty!o umn.cs.general!b umn.cs.gradst! umn.cs.gripes! umn.cs.jobs! umn.cs.labs.ai!. umn.cs.labs.grad!n umn.cs.lang.c! umn.cs.lang.misc!a umn.cs.net!  umn.cs.seminars! umn.cs.soc!t umn.cs.test! umn.cs.text.framemaker!c umn.cs.text.tex! umn.cs.ugrads! umn.cs.windows.x!i umn.csom.class.oms8995!c umn.csom.ids5410!c umn.csom.ids8110!  umn.csom.ids8450!c umn.csom.test! umn.daily.forum! umn.ee.announce! umn.ee.chatter!d umn.ee.computer! umn.ee.dept! umn.ee.faculty!a umn.ee.general!u
 umn.ee.grads!. umn.ee.seminar!o umn.ee.test! umn.ee.undergrads! umn.epsy.deaf.students!c umn.epsy.deaf.teacher-parent!. umn.fan.serge-rudaz! umn.fscn.general!t
 umn.fscn.ift!w umn.general.energy!s umn.general.events!  umn.general.food!. umn.general.housing! umn.general.jobs!. umn.general.lost+found!  umn.general.misc!. umn.general.movies!c umn.general.music! umn.general.sports!s umn.ioft.class.1001h!r umn.itlab.bldg!c umn.itlab.curriculum!. umn.itlab.dept!. umn.itlab.faculty! umn.itlab.general! umn.itlab.gradst!r umn.itlab.gripes!s umn.itlab.jobs!. umn.itlab.lang.c!c umn.itlab.lang.c++!. umn.itlab.lang.misc! umn.itlab.net! umn.itlab.soc! umn.itlab.systems.mac! umn.itlab.systems.misc!r umn.itlab.systems.pc!b umn.itlab.systems.status!w umn.itlab.systems.sun! umn.itlab.systems.unix!y umn.itlab.test!. umn.itlab.text.framemaker! umn.itlab.text.tex!. umn.itlab.ugrads!. umn.itlab.windows.x! umn.local-lists.aci-4d!g umn.local-lists.austrian-cultu!! umn.local-lists.cnug-dss!r umn.local-lists.decstation-man!p umn.local-lists.disc-env!. umn.local-lists.disc-evidence! umn.local-lists.disc-nordic! umn.local-lists.disc-nordlib!e umn.local-lists.disc-sar!c umn.local-lists.disc-tacfanout!  umn.local-lists.disc-vis-graph!r umn.local-lists.epixinfo!e umn.local-lists.ethnic-theater!. umn.local-lists.mac-consort! umn.local-lists.net-ops! umn.local-lists.news!d umn.local-lists.news-stats!t umn.local-lists.novell!d umn.local-lists.security!n umn.local-lists.sgi-admins!s umn.local-lists.siren! umn.local-lists.sun-news!y umn.local-lists.techc-admin! umn.local-lists.techc-all! umn.local-lists.techc-atm! umn.local-lists.techc-backup!! umn.local-lists.techc-cal! umn.local-lists.techc-email! umn.local-lists.techc-general! umn.local-lists.techc-microlan!e umn.local-lists.techc-modems!r umn.local-lists.techc-public!  umn.local-lists.techc-sgi! umn.local-lists.techc-site!i umn.local-lists.techc-unix!. umn.local-lists.techc-web! umn.local-lists.techc-workst!f umn.local-lists.ubike-info!o umn.local-lists.umn-email! umn.local-lists.umn-www! umn.local-lists.users-mlre!v umn.local-lists.wg-cscc! umn.local-lists.writingc!  umn.local-lists.x3j9-admin!o umn.local-lists.x3j9-tech! umn.math.dept!
 umn.math.zoo!. umn.morris.general!r umn.morris.misc! umn.net-lists.explorer!. umn.net-lists.info-appletalk!y umn.net-lists.rfc931-users!y umn.news-server.announce!a umn.news-server.questions! umn.news-server.test!. umn.news-server.traffic! umn.ophth.isrk!c umn.org.acm! umn.org.china! umn.org.india! umn.org.sps! umn.ortta.general! umn.rhet.general!o umn.rhet.gradst! umn.soc.faculty! umn.