           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.                     E                                                                    -3           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                                                                     v                  &         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-22H               3.4.4.5.1    Default Route Configuration...........   3-24H               3.4.4.6     BIND Resolver Configuration............   3-24H               3.4.4.7     Time Zone Configuration................   3-27H               3.4.5     Configuring the Client Environment.......   3-27H               3.4.6     Configuring the Server Environment.......   3-31H               3.4.7     Configuring the Optional Components......   3-34;               3.4.7.1     Configuring and Enabling Kerberos H                           Support................................   3-36>               3.4.7.2     Configuring and Enabling failSAFE IPH                           Support................................   3-37@               3.5   Using TCPIP$CONFIG Option Commands to BypassH                     TCPIP$CONFIG Menus...........................   3-38H               3.6   Making Configuration Changes Take Effect.....   3-402               3.7   Stopping TCP/IP Services UsingH                     TCPIP$CONFIG.................................   3-412               3.8   Starting TCP/IP Services UsingH                     TCPIP$CONFIG.................................   3-43H               3.9   Verifying the Configuration..................   3-45      
         vi                 =               3.9.1     Running the IVP from the TCPIP$CONFIG H                         Command Procedure........................   3-46<               3.9.2     Running the IVP from the OpenVMS DCLH                         Prompt...................................   3-46>               3.9.3     Verifying the TCP/IP Services InternetH                         Configuration............................   3-46H               3.9.4     Verifying the SNMP Configuration.........   3-48H               3.10  Additional Configuration Tasks...............   3-50H               3.11  Starting and Stopping TCP/IP Services........   3-50;               3.11.1    Automatically Starting and Stopping H                         TCP/IP Services..........................   3-51=               3.11.2    Starting and Stopping TCP/IP Services H                         Manually.................................   3-51A               3.11.3    Starting and Stopping Individual Services H                         .........................................   3-52:               3.11.4    Starting and Stopping User-WrittenH                         Services.................................   3-52?               3.12  Specifying TCP/IP Services as the Transport H                     for DECwindows Applications..................   3-53             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                                                                      vii                          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-40  H               3-4       Troubleshooting IVP Errors...............   3-48                                                 viii                           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.                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                                                                       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:                 openvmsdoc@hp.com   -         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.B               If you have the OpenVMS consolidated distribution CDE               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               supply the device name (such as DKAn) for the media when?               you issue the command to install TCP/IP Services.   G               Check that the kit contains everything listed on the 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.   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           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 OpenVMS                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.   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           :         Preparing to Install and Configure TCP/IP Services!         1.2 Preinstallation Tasks   ,         1.2.7 Checking the System Parameters  A               Most systems have adequate system resources readily @               available to include the TCP/IP Services software.F               However, you should check the system parameters outlinedF               in the following sections. Make any necessary changes toG               the MODPARAMS.DAT file, then run AUTOGEN, and reboot your                system.   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                 _____________________________________________________   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 increased C                 automatically. This increases throughput across the /                 FDDI for local TCP connections.   E                 _____________________________________________________   >               3. Refer to the following example, and then editC                  MODPARAMS.DAT to reflect the appropriate value for 6                  the NPAGEDYN and NPAGEVIR parameters:  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.   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.   C               The TCPIP$CONFIG configuration procedure uses a group F               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           :         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 service @                          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 ANONYMOUS H               ___________account._______________________________________  F               Before you assign a new group UIC, check that the numberG               you chose is not already in use by entering the following                commands:   (               $ 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 must !                 do the following:   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                       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.   E                 _____________________________________________________   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 the H               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           :         Preparing to Install and Configure TCP/IP Services0         1.3 Assembling Configuration Information  H         Table_1-3_Configuration_Planning_Worksheet______________________  G                                                        Your answer will H         _____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         Do you plan to have your IP interface under    _________________.         control of the DHCP client? If so, the2         next items on this worksheet (the system's5         addresses and masks, and the system's network 5         interface), might be configured automatically 0         by the DHCP server, in which case you do2         not need to specify them. Ask your network         manager for details.    5         What are the system's addresses and masks?[1]   H         *    IP address (for example, 19.112.139.14)   _________________  H         *    Subnet (network mask) address (for        _________________               example, 255.0.0.0)  H         *    Broadcast address (for example,           _________________              19.255.255.255)  H         What is the system's network interface (for    _________________         example, WE0)?[1]   H                                                        _________________  H                                                        _________________  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 DHCP          client documentation.     ?         1-10 Preparing to Install and Configure TCP/IP Services            H                       Preparing to Install and Configure TCP/IP ServicesH                                 1.3 Assembling Configuration Information  H         Table_1-3_(Cont.)_Configuration_Planning_Worksheet______________  G                                                        Your answer will H         _____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.   H         Which type of routing is appropriate for the   _________________#         network, Static or Dynamic?   /              Static - For simple networks where !              routes do not change   3              If static, enter the default gateway's 0              host name and address (for example,"              GATWY1; 19.112.0.65).  1              Dynamic - For complex networks where $              flexibility is required  0              If dynamic, you must specify either%              ROUTED or GATED routing.   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,               MAINSV)?   H         *    What is the IP address of the BIND        _________________1              server (for example, 19.112.139.10)?   H         *    What is the domain name (for example,     _________________!              mainsv.widgets.com)?   H                  Preparing to Install and Configure TCP/IP Services 1-11           :         Preparing to Install and Configure TCP/IP Services0         1.3 Assembling Configuration Information  H         Table_1-3_(Cont.)_Configuration_Planning_Worksheet______________  G                                                        Your answer will H         _____When_the_configuration_procedure_asks...__be...____________  +         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. Specify 0              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 (for 3              implementing traps and allowing access 5              beyond the default read-only provided by H         _____the_"public"_community)?___________________________________      ?         1-12 Preparing to Install and Configure TCP/IP Services                        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 directly E               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.   /         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 configure +               this version of the software.   C               To install the TCP/IP Services software on an OpenVMS 6               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$STARTUP   H                                           Installing TCP/IP Services 2-1           "         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:   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. F                  If you have DECnet configured on your system, you canG                  create a log of the installation procedure by entering D                  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:   ?                  $ PRODUCT INSTALL TCPIP /SOURCE=directory-path   C                  In this command, directory-path specifies the disk G                  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. If F                  not defined, the utility searches the current default                  directory.   &         2-2 Installing TCP/IP Services           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.   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 an A                 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 OpenVMS A                 Alpha systems it is DEC AXPVMS TCPIP, as shown in                  Example 2-1.  E                 _____________________________________________________                       H                                           Installing TCP/IP Services 2-3           "         Installing TCP/IP Services7         2.2 Stepping Through the Installation Procedure   C         Example 2-1 TCP/IP Services Installation: Sample POLYCENTER ;                     Software Installation Utility Procedure   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 Product   /         Do you want to continue? [YES] <Return>   ?               Pressing Return allows the procedure to continue.   (         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.   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.   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.   &         2-4 Installing TCP/IP Services           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: M             DEC AXPVMS TCPIP V5.5-xx              DISK$ALPHASYS:[VMS$COMMON.] ?         The following product will be removed from destination: M             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, $         %   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: B             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 following                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 Software F                     Installation utility searches the location definedH                     by the logical name PCSI$SOURCE. If not defined, theC                     utility searches the current default directory.   A               2. If you had a previous version of TCP/IP Services ?                  configured on your system and the software was C                  previously started, reboot your system for the new 9                  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 configuration )                 (described in Chapter 3).   ;                 When rebooting OpenVMS, perform only a full ?                 boot. Any other kind of boot causes the product <                 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           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                 _____________________________________________________                                                                     H                                           Installing TCP/IP Services 2-7                       H                                                                        3H         ________________________________________________________________  H                                              Configuring TCP/IP Services      C               After you install HP TCP/IP Services for OpenVMS, you C               need to enable the components and characteristics you F               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 additional ,               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.COM C                    configuration procedure fails on systems that do ,                    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 that 4                    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:   '                    $ SHOW QUEUE/MANAGER   B                    If the queue manager is running, the display isC                    as follows (where the local node is named ACME):   F                    Queue manager SYS$QUEUE_MANAGER, running, on ACME::  A                    If the following is displayed instead, the re- D                    quired queue files have not yet been created. The  H                                          Configuring TCP/IP Services 3-1           #         Configuring TCP/IP Services     C                    files do not exist after an initial installation 2                    of OpenVMS and must be created.  -                    -RMS-E-FNF, file not found   =                    To create these files, enter the following '                    OpenVMS DCL command:   -                    $ START/QUEUE/MANAGER/NEW.   @                    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.   E                 _____________________________________________________   =         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 Services            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.3 -                     for running TCPIP$CONFIG.   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.4 3                     have TCP/IP Services configured 7                     automatically, as explained in step :                     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.9   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 Cluster   1         3.2 Adding a System to an OpenVMS Cluster   >               Beginning with Version 5.5, the TCPIP$CONFIG.COMD               configuration procedure for TCP/IP Services can createH               OpenVMS accounts using larger system parameter values thanF               in previous versions. Only new accounts get these largerF               values. These values are useful on OpenVMS Alpha systems3               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 this                recommendation.   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 a F               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         100   '         3-4 Configuring TCP/IP Services            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]  50000                  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 DHCP              Client  B               Beginning with Version 5.5, TCP/IP Services supportsC               the DHCP client, which allows you to have your system H               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 startup F                  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           #         Configuring TCP/IP Services H         3.3 Automatic Configuration of TCP/IP Services Using DHCP Client  G                  The startup procedure invokes TCPIP$CONFIG, which sets F                  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 E                  2-Interfaces. This option displays the Interface and D                  Address Configuration menu from which to choose theE                  interface you want to configure for DHCP. Select the G                  option containing the interface you want to configure.   F                  Then choose Option 3 from the Interface ConfigurationH                  menu, enabling the DHCP client to manage the address on                   that interface.  E                  Following is an example of the Interface and Address $                  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) 0                                 [E] -  Exit menu  <                                  Enter configuration option:  '         3-6 Configuring TCP/IP Services            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 WE0 Q                                  3  - Enable DHCP client to manage address on WE0 /                                 [E] - Exit menu   <                                  Enter configuration option:  5                  This prompts you with the following:   C                  Configure WE0 as the DHCP PRIMARY? (Y,N,HELP) [Y]:   4                  Press return to accept the default.  ?                  The resulting display resembles the following:   M         HP TCP/IP Services for OpenVMS Interface & Address Configuration Menu   Z                         Hostname Details: Configured=Not Configured, Active=Not Configured  .                         Configuration options:D                         1  -  WE0 Menu (EWA0: TwistedPair 1000mbps) @                               (Managed by DHCP client - PRIMARY)B                         2  -  IE0 Menu (EIA0: TwistedPair 100mbps)'                        [E] -  Exit menu   2                        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, you B                 could receive errors when the DHCP Client tries to0                 start, similar to the following:      H                                          Configuring TCP/IP Services 3-7           #         Configuring TCP/IP Services H         3.3 Automatic Configuration of TCP/IP Services Using DHCP Client  H          %TCPIP-I-DHCPC_STRD_CLNT, DHCP client started with PID 00000556I         liam$dka0:[sys0.syscommon.][sysexe]tcpip$dhcp_client_conf.exe;1:  "         timed out after 30 seconds=         %TCPIP-E-DHCPC_TIMEOUT, controlling program timed out K         %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 be "                 setup for success:                   -  nets.                   -  netmasks.                   -  dhcpcap.                    -  .ddnskeys                   -  server.pcy   E                 _____________________________________________________             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 Files                (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]   @               Unless you respond NO to the prompt, the procedureH               converts existing configuration files to new configuration               files.  '         3-8 Configuring TCP/IP Services            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 being                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.              NOTE: G           TCP/IP has been previously configured from an earlier version G           of this product.  You can avoid a complete reconfiguration of H           TCP/IP by allowing this procedure to automatically convert theI           old configuration files.  If you choose not to do this now, you I           will not be asked again.  At the end of the conversion you will 7           be able to further modify your configuration.   9         Convert the old configuration files [Y]: <Return> )         Preparing files for conversion...   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.DAT 9             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. 3           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 queue *                  - Name of the remote host9                  - Spooling directory for the local queue   P                To add or delete printers in the TCPIP PRINTCAP database, use the6                $RUN SYS$SYSTEM:TCPIP$LPRSETUP command.	         . 	         . 	         .   >         3.4.2 Creating New TCP/IP Services Configuration Files  G               If you do not have an existing TCP/IP Services configura- G               tion in place from a previous version of the product, the H               procedure begins by creating configuration database files,6               as shown in the following sample output:  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;1 8          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 Menus   E               After the configuration files are converted or created, 7               the Main Configuration menu is displayed:   =             HP TCP/IP Services for OpenVMS Configuration Menu   "             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 OpenVMS "                    7  -  Run tests  0                    A  -  Configure options 1 - 45                   [E] -  Exit configuration procedure   #         Enter configuration option:   )               The options are as follows:   H         ________________________________________________________________H         Option_______________Description________________________________  C         1   Core environ-    Configure software associated with the G             ment             Network, Internet, and Transport layers of E                              the TCP/IP architecture (Section 3.4.4).   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             OpenVMS   A         6   Startup TCP/IP   Start TCP/IP Services (Section 3.8).              Services for             OpenVMS   H         7   Run tests        Run the installation verification procedure+                              (Section 3.9).   H                                         Configuring TCP/IP Services 3-11           #         Configuring TCP/IP Services           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.   9         E   Exit the         Return to the system prompt.              configuration H         ____procedure___________________________________________________  F                 ________________________Note  ________________________  =                 If you do not have experience with the TCP/IP B                 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 software ?                 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, B               the Core Environment Configuration menu is displayedE               first. The sample output in the following sections show H               the progression of the procedure when you choose option A.  C               You are required to configure the Domain, Interfaces, C               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           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                 _____________________________________________________   H            HP TCP/IP Services for OpenVMS Core Environment Configuration            Menu   !            Configuration options:                       1 - Domain !                    2 - Interfaces                     3 - Routing$                    4 - BIND Resolver                     5 - Time Zone  /                    A  - Configure options 1 - 5 !                   [E] - Exit menu   .         Enter configuration option: A <Return>  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 the @                 Core Environment configuration options. For more+                 information, see Chapter 4.   :                                                - 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 in ;                    BIND/DNS for the changes to take effect.   E                 _____________________________________________________   G               The following sections include sample output for the core B               environment components. The samples reflect a TCP/IPB               Services product configuration for a system on whichD               other TCP/IP Services configurations are in place. TheG               output varies for a new TCP/IP Services installation (see                Appendix A).  H                                         Configuring TCP/IP Services 3-13           #         Configuring TCP/IP Services           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 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: 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.com >         Communication domain updated in configuration database  6         3.4.4.2 First-Time Configuration of Interfaces  E               The interface and address menus allow the configuration F               and management of both the permanent database as well asE               the live system. The menu supports multi-homed systems, B               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.   @               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 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 OpenVMS (                          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  -  Interfaces &                          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)   (                         [E] -  Exit menu  )               Enter configuration option:   H                                         Configuring TCP/IP Services 3-15           #         Configuring TCP/IP Services           3.4 Running TCPIP$CONFIG  H               In this example, no changes are made to the interface. TheE               systems TCP/IP hostname is displayed as Not Configured. C               This is automatically configured the first time an IP @               address is configured. The assigned systems TCP/IP@               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.   2         3.4.4.3 Interface IP Address Configuration  A               To configure an interface, select the option of the E               desired interface, then select Option 1 - Add a primary G               address on <chosen interface>, and answer the prompts for ?               the IP address, netmask and hostname information.                  For example:  U                 HP TCP/IP Services for OpenVMS Interface & Address Configuration Menu   R                 Hostname Details: Configured=Not Configured, Active=Not Configured  &                 Configuration options:  ;                 1  -  WE0 Menu (EWA0: TwistedPair 1000mbps) :                 2  -  IE0 Menu (EIA0: TwistedPair 100mbps)                  [E] -  Exit menu   +               Enter configuration option: 1   C               This menu allows the configuration of a primary or an D               alias address as well as giving control to DHCP-clientG               for address assignment. The primary address is considered E               the most often used address for this interface, whereas D               an alias address is considered a secondary address. ByG               default, data sent via an interface with a primary and an E               alias address is transmitted with the IP source address )               set to the primary address.   (         3-16 Configuring TCP/IP Services           H                                              Configuring TCP/IP ServicesH                                                 3.4 Running TCPIP$CONFIG  E               The following example shows that WE0 is configured with F               a primary IP address of 10.0.0.1 and an alias address ofH               10.0.1.1. The menus are 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 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.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 is 1               correct, press Return to accept it.   H               The following output is displayed, showing all informationF               entered and then the Interface and Address menu again toG               display the change you have just made, configuration, and                interface.                  H                                         Configuring TCP/IP Services 3-17           #         Configuring TCP/IP Services           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 database   
         NOTE:   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 database   <         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                  Configured 9                3  -  IE0 Menu (EIA0: TwistedPair 100mbps)                  [E] -  Exit menu  #         Enter configuration option:   >               In this example, Interface WE0 with 10.0.0.1 wasC               configured as the address, 16 CIDR bits (255.255.0.0) 7               as the netmask, and the hostname as LIAM.   E               The address may be entered with the number of CIDR bits D               or a netmask. This example used 16 CIDR-bits, which is5               equivalent to a netmask of 255.255.0.0.   A               Because this is the first address configured on the C               system, it automatically becomes the TCP/IP hostname, 3               as is displayed under the NOTE: text.   H               The address 10.0.0.1 with a name of LIAM has automaticallyA               been assigned as the system's TCP/IP hostname. This F               automatic assignment occurs only when no other addresses+               are configured on the system.   (         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 theG               Interface and Address Configuration menu. It now displays B               the address 10.0.0.1/16 configured on WE0. The newlyG               created address has its own menu option (2), which allows E               further modification of the specific address. Note that D               menu options for configuring the other interfaces haveD               been incremented compared to the first screen capture.  B               The state of the address is described as Configured.  1         3.4.4.4 failSAFE IP Address Configuration   D               To provide high availability of an IP address, you canG               configure it on multiple interfaces on a node or across a E               cluster, then enable the failSAFE IP service. Note that D               only one instance of the address is active; the othersF               are in standby mode. The failSAFE IP service continuallyB               monitors the health of interfaces and upon detectingE               an interface failure, the address is deactivated on the D               failed interface and a standby address becomes active.  E               When the failed interface recovers, failSAFE IP detects 1               this and can return its IP address.   :               Configure the standby IP address as follows:  E               1. From the Core Environment Configuration menu, select A                  option 2 (Interfaces). The Interface and Address ,                  Configuration menu appears.  C               2. From the Interface and Address Configuration menu, D                  select the menu item for the IP Address you want toC                  configure as an alias for failSAFE IP, then select @                  Option 4 - Add standby aliases to configurationC                  database (for failSAFE IP), then enter name of the /                  interface for the failSAFE IP.   @                  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 the                  failSAFE IP.     H                                         Configuring TCP/IP Services 3-19           #         Configuring TCP/IP Services           3.4 Running TCPIP$CONFIG  H                  This example uses 10.10.1.1 for the failSAFE IP and forH                  the IEO Interface. Select Option 3, then Option 4, then&                  enter IE0 as follows:  F                 ________________________Note  ________________________  <                 For information on configuring failSAFE IPv6+                 addresses, see Section 4.3.   E                 _____________________________________________________   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)              [E] -  Exit menu  %         Enter configuration option: 3   F              HP TCP/IP Services for OpenVMS Address Configuration Menu  3               WE0 10.10.1.1/16 abby Configured WEA0             Configuration options:   $                  1  - Change address8                  2  - Set "abby" as the default hostname8                  3  - Delete from configuration databaseD                  4  - Add standby aliases to configuration database '                       (for failSAFE IP)                    [E] - Exit menu   %         Enter configuration option: 4   8         Address 10.10.1.1/16 is currently configured on:              WE0  .         Interfaces available for failover are:  
           IE0   /         Enter an interface for failSAFE IP: IE0 D         Added alias address IEA0:10.10.1.1 to configuration database  (         3-20 Configuring TCP/IP Services           H                                              Configuring TCP/IP ServicesH                                                 3.4 Running TCPIP$CONFIG  N              The failSAFE IP service, which monitors the health of interfaces,M              is not currently enabled.  Refer to the Optional Components Menu &              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 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/26    abby                  Configured   5            4  -  IE0 Menu (EIA0: TwistedPair 100mbps) E            5  -  10.10.1.1/26        abby                  Configured              [E] -  Exit menu  #         Enter configuration option:   E               3. When you have started TCP/IP services, you return to G                  the Interface and Address Configuration menu to verify F                  that your selected address is now in standby mode, as*                  in the following example:  O           HP TCP/IP Services for OpenVMS Interface & Address Configuration Menu   7          Hostname Details: Configured=liam, Active=liam             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:   H                                         Configuring TCP/IP Services 3-21           #         Configuring TCP/IP Services           3.4 Running TCPIP$CONFIG  F                  Note that item 5 now has Configured,Active-Standby as                  its status.  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 address V                           2  - Set "abby.sqa.tcpip.zko.hp.com" as the default hostnameA                           3  - Delete from configuration database 6                           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 must A                  configure and enable the failSAFE IP service, as .                  explained in Section 3.4.7.2.  F                 ________________________Note  ________________________  ?                 You can also manually configure the failSAFE IP A                 address using the TCP/IP management SET INTERFACE =                 command or the ifconfig utility. The ifconfig ?                 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                 _____________________________________________________   -         3.4.4.5 Dynamic Routing Configuration   D               The following is sample output for configuring dynamic               routing:            (         3-22 Configuring TCP/IP Services           H                                              Configuring TCP/IP ServicesH                                                 3.4 Running TCPIP$CONFIG  %         DYNAMIC ROUTING Configuration   1          Dynamic routing has not been configured.   >             You may configure dynamic ROUTED or GATED routing.A             You cannot enable both at the same time.  If you 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 other 8             hosts to update its internal routing tables.=             It will also supply its own Internet addresses to 4             routing requests made from remote hosts.  D             If you enable dynamic GATED routing, you will be able toG             configure this host to use any combination of the following E             routing protocols to exchange dynamic routing information ,             with other hosts on the network:B                 Routing Information Protocol (RIP) - Version 1 & 21                 Router Discovery Protocol (RDISC) /                 Open Shortest Path First (OSPF) /                 Exterior Gateway Protocol (EGP) /                 Border Gateway Protocol (BGP-4)                  Static routes   U         * Do you want to configure dynamic ROUTED or GATED routing [NO]: YES <Return> J         * Do you want to enable GATED routing configuration [NO]: <Return>               ROUTED option   A             If you enable the 'supply' option of dynamic routing, @             this host will supply dynamic routing information toA             other hosts on the network whether it is acting as an (             internetwork gateway or not.  X         * Do you want this host to supply its dynamic routing information [NO]: <Return>              H                                         Configuring TCP/IP Services 3-23           #         Configuring TCP/IP Services           3.4 Running TCPIP$CONFIG  D               3.4.4.5.1 Default Route Configuration   If you need toB               configure a default route, press Return at the firstH               prompt, accepting the default of NO to the dynamic routingD               option, then press Return at the next prompt to acceptE               the default of YES to the default route, then enter the E               name of the gateway and its IP address, as shown in the                 following example:  Q         * Do you want to configure dynamic ROUTED or GATED routing [NO]: <Return>   8                 A default route has not been configured.B         * Do you want to configure a default route [YES]: [return]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 and 9               address, as shown in the following example:                                               (         3-24 Configuring TCP/IP Services           H                                              Configuring TCP/IP ServicesH                                                 3.4 Running TCPIP$CONFIG  M            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: 4   #         BIND RESOLVER Configuration   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 for                  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. A                 Press Return at the prompt to terminate the list.   +         Enter your BIND server name: odessy   9                 odessy is not in the local host database.   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  -  Domain )                          2  -  Interfaces &                          3  -  Routing,                          4  -  BIND ResolverH                          5  -  Time ZoneConfiguring TCP/IP Services 3-25  6                          A  -  Configure options 1 - 5(                         [E] -  Exit menu  #         Enter configuration option:            #         Configuring TCP/IP Services           3.4 Running TCPIP$CONFIG  E               To view the current BIND resolver configuration, select F               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:   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: 4   #         BIND RESOLVER Configuration   4         A BIND resolver has already been configured.  #         BIND Resolver Configuration              Transport:  UDP *           Domain:     sqa.tcpip.zko.hp.com           Retry:         2           Timeout:       5           Servers:    odessy'           Path:       No values defined   /         * Do you want to reconfigure BIND [NO]:   E               The following is sample output for configuring the BIND                resolver:   4         A BIND resolver has already been configured.  #         BIND Resolver Configuration              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>  (         3-26 Configuring TCP/IP Services           H                                              Configuring TCP/IP ServicesH                                                 3.4 Running TCPIP$CONFIG  >               In this example, no changes are made to the BIND               resolver.   '         3.4.4.7 Time Zone Configuration   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 display O           either the wrong time or a time inconsistent with other applications.   <         %TCPIP-I-INFO, Logical name SYS$TIMEZONE_RULE found.M         -TCPIP-I-INFO, Software for automatic Summer/Winter time (TDF) change "         -TCPIP-I-INFO, is present.L         -TCPIP-I-INFO, Further action to ensure TDF change is not necessary.  6         %TCPIP-I-NORMAL, timezone information verified  $         Press Return to continue ...  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.   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, H               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.   H                                         Configuring TCP/IP Services 3-27           #         Configuring TCP/IP Services           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 will A                 fail to start. For more information, refer to the .                 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. ?               Clients are enabled for startup if they have been C               enabled in the TCP/IP Services configuration database A               (TCPIP$CONFIGURATION.DAT). The enabled services are C               started the next time TCP/IP Services is started. You B               can also start (or stop) a specific service, withoutF               having to restart TCP/IP Services, by choosing the StartG               service option from that service's configuration menu. In   (         3-28 Configuring TCP/IP Services           H                                              Configuring TCP/IP ServicesH                                                 3.4 Running TCPIP$CONFIG  G               addition, you can use command procedures to start or stop A               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.   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.   D               To configure all the client services, choose option A.  G               The following is an example of the output for configuring G               an FTP client. The configuration output for other clients F               might vary. Note that after you configure a client (suchF               as FTP) that has an associated server, the configurationF               prompts you about whether to configure the corresponding               server.   .         Enter configuration option: 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.  H                                         Configuring TCP/IP Services 3-29           #         Configuring TCP/IP Services           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.          Service is stopped.   1                 FTP CLIENT configuration options:   8                          1 - Enable service on this node  @                          2 - Enable & Start service on this node  ;                         [E] - Exit FTP_CLIENT configuration   .         Enter configuration option: 2 <Return>  C               In this example, as with the previous one, the TCP/IP E               Services software has already been started, so you have G               the choice of starting the client as well as enabling it. H               If you choose option 1, the FTP service is enabled and FTPE               starts the next time TCP/IP Services is started. If you E               choose option 2, the FTP service is started immediately A               and then every time the TCP/IP Services is started.   E               If the TCP/IP Services software is not already started, E               then the FTP Client Components Configuration menu gives D               you only the option of enabling the service, as in the                following example:  7                         1 - Enable service on this node   :                        [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.    (         3-30 Configuring TCP/IP Services           H                                              Configuring TCP/IP ServicesH                                                 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 the                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 for D                 OpenVMS Guide to SSH and the TCP/IP Services release                 notes.  E                 _____________________________________________________   K         HP TCP/IP Services for OpenVMS Server Components Configuration Menu   P           1 - BIND         Enabled  Started    12 - NTP         Enabled  StartedP           2 - BOOTP        Disabled Stopped    13 - PC-NFS      Enabled  StartedP           3 - DHCP         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:         H                                         Configuring TCP/IP Services 3-31           #         Configuring TCP/IP Services           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 (or G               stop) a specific server, without having to restart TCP/IP F               Services, by choosing the Start service option from thatC               server's configuration menu. In addition, you can use G               command procedures to start or stop a specific server, as *               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 the D               server you are prompted about whether to configure the#               corresponding client.   F                 ________________________Note  ________________________  C                 TELNET and RLOGIN are enabled from the client menu. C                 If you want to disable the TELNET or RLOGIN server, ?                 then you must disable the service. To enable or C                 disable the TELNET server or the RLOGIN server, use D                 the Client Components Configuration menu, choose theD                 appropriate client, and disable and stop the service@                 by choosing the Disable and 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.             (         3-32 Configuring TCP/IP Services           H                                              Configuring TCP/IP ServicesH                                                 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. %               Service is not enabled. !               Service is stopped.   )                XDM configuration options:   0                  1 - Enable service on this node  ,                 [E] - Exit XDM configuration  )               Enter configuration option:   F                 ________________________Note  ________________________  C                 XDM requires the following DECwindows components to                  be installed:   6                 o  SYS$COMMON:[SYSLIB]DECW$XLIBSHR.EXE  9                 o  SYS$COMMON:[SYSLIB]DECW$XTLIBSHRR5.EXE   ?                 The TCPIP$CONFIG configuration procedure checks C                 whether these components are installed. If they are B                 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                 _____________________________________________________   E               After you configure the servers, press Return or choose G               option E to exit from the Server Components Configuration E               menu. If you chose option A from the Main Configuration C               menu to configure all the TCP/IP Services components, G               the Optional Components Configuration menu displays next; H               otherwise, the procedure returns to the Main Configuration               menu.   H                                         Configuring TCP/IP Services 3-33           #         Configuring TCP/IP Services           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 programming !                  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 interface A                  cards and, when an interface fails, to perform a B                  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 Main E               Configuration menu to configure all the TCP/IP Services D               components, the Optional Components Configuration menuE               displays automatically after you finish configuring the                servers.  E               The Optional Components Configuration menu displays the %               following menu options:                       (         3-34 Configuring TCP/IP Services           H                                              Configuring TCP/IP ServicesH                                                 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) =                 2 - Configure SRI QIO Interface (INET Driver) @                 3 - Set up Anonymous FTP Account and Directories3                 4 - Configure Kerberos Applications )                 5 - Configure failSAFE IP   +                 A - Configure options 1 - 5                 [E] - Exit menu  #         Enter configuration option:   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 for C               TELNET, and failSAFE IP (provides IP address failover G               capability for multiple interfaces on a host or cluster).   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.   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.   F               o  If you want to provide IP address failover capabilityE                  for multiple interfaces on a host or cluster, choose E                  option 5 to configure failSAFE IP. For details about F                  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.  H                                         Configuring TCP/IP Services 3-35           #         Configuring TCP/IP Services           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.   P          TCPIP Transport for DECnet and Pathworks Service configuration options:  ,             1 - Disable service on this node  /            [E] - Exit PWIP_DRIVER configuration   #         Enter configuration option:   9         3.4.7.1 Configuring and Enabling Kerberos Support   B               To configure the TELNET service to support Kerberos,A               follow these steps. For more details about Kerberos D               features, including prerequisites and instructions 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                 _____________________________________________________   K               1. From the the TCPIP$CONFIG.COM procedure Main Configuration ;                  menu, choose option 2 (Client components).   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 the 9                  TCPIP$TELNET user account and directory.   7               4. Return to the Main Configuration menu.   B               5. From the Main Configuration menu, choose option 4'                  (Optional components).   (         3-36 Configuring TCP/IP Services           H                                              Configuring TCP/IP ServicesH                                                 3.4 Running TCPIP$CONFIG  A               6. From the Optional Components Configuration menu, C                  choose option 4 (Configure Kerberos Applications). 1                  The following menu is displayed:   9                  Kerberos Applications Configuration Menu   N                  TELNET Kerberos is not defined in the TCPIP$SERVICE database.  -                        Configuration options:   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 TELNET F                  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.   <         3.4.7.2 Configuring and Enabling failSAFE IP Support  ?               Two steps are necessary to configure failSAFE IP:   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.  H                                         Configuring TCP/IP Services 3-37           #         Configuring TCP/IP Services           3.4 Running TCPIP$CONFIG  C               2. Configure failSAFE IP support by choosing option 5 E                  (Configure failSAFE IP) from the Optional Components $                  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, F               Option 1 (Enable service on all nodes) appears only in aG               cluster configuration. Choose Option 1 to enable failSAFE C               IP on all nodes in the cluster, or choose option 2 to 8               enable failSAFE IP on the local node only.  5                       failSAFE configuration options:   >                                1 - Enable service on all nodes>                                2 - Enable service on this node  F                                3 - Enable & Start service on this node  ?                               [E] - Exit FAILSAFE configuration   )               Enter configuration option:   H               For more details about failSAFE IP, refer to the HP TCP/IP5               Services for OpenVMS Management manual.   E         3.5 Using TCPIP$CONFIG Option Commands to Bypass TCPIP$CONFIG              Menus   A               If you are an experienced TCP/IP Services user, you E               may want to bypass the configuration menus to enable or 0               disable functionality, as follows:  .               1. Log in to the SYSTEM account.  C               2. Run the TCPIP$CONFIG command procedure and include F                  appropriate options and keywords in the command line,,                  using the following format:  P                  @SYS$MANAGER:TCPIP$CONFIG [option] {DISABLE | ENABLE} [CLUSTER]  A                  In this format, option can be one of the options A                  described in the following table. The table also C                  describes the function of the DISABLE, ENABLE, and "                  CLUSTER keywords.  (         3-38 Configuring TCP/IP Services           H                                              Configuring TCP/IP ServicesH      3.5 Using TCPIP$CONFIG Option Commands to Bypass TCPIP$CONFIG Menus  H                  _______________________________________________________H                  Option________Description______________________________  F                  ALL           Configures the core environment and all:                                client and server 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 optional *                                components.  A                  SERVER        Configures all servers and related (                                software.  H                  WORKSTATION   Configures the BIND resolver, the domain,D                                dynamic routing, Internet interfaces,E                                time zone, remote login, remote shell, H                                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 configure ,                                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:   B                  $ @SYS$MANAGER:TCPIP$CONFIG CLIENT ENABLE CLUSTER  F                 ________________________Note  ________________________  C                 The procedure implements two levels of enabling and @                 disabling: clusterwide and node specific (exceptA                 for SMTP, which is configured and enabled as node                  specific only).   E                 _____________________________________________________   H                                         Configuring TCP/IP Services 3-39           #         Configuring TCP/IP Services 4         3.6 Making Configuration Changes Take Effect  4         3.6 Making Configuration Changes Take Effect  G               Configuration changes made to TCP/IP Services software do G               not take effect until you start (or restart) the affected B               services. You may need to restart TCP/IP Services orC               simply the individual services affected, as explained                in Table 3-3.   H         Table_3-3_Making_Configuration_Changes_Take_Effect______________           When you change 6         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) or F         zone)                                            customize theE                                                          environment. C                                                          Methods to E                                                          start TCP/IP E                                                          Services are E                                                          described in E                                                          Sections 3.8 B                                                          and 3.11.                                      (         3-40 Configuring TCP/IP Services           H                                              Configuring TCP/IP ServicesH                             3.6 Making Configuration Changes Take Effect  H         Table_3-3_(Cont.)_Making_Configuration_Changes_Take_Effect______           When you change 6         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      procedures G                               only start or restart      for individual D                               each affected service      services isE                               individually. Do this      explained in H                               by choosing the Start      Section 3.11.3.3                               service option in the 5                               service's configuration 2                               menu. Alternatively,.                               you can use each7                               service's startup command (                               procedure.  6                               If you also made changes1                               to core environment 4                               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 software 7                 manually, as explained in Section 3.11.   E                 _____________________________________________________   7         3.7 Stopping TCP/IP Services Using TCPIP$CONFIG   F               Stop TCP/IP Services on your system by choosing option 5E               (Shutdown HP TCP/IP Services for OpenVMS) from the Main >               Configuration menu, as in the following example:            H                                         Configuring TCP/IP Services 3-41           #         Configuring TCP/IP Services 7         3.7 Stopping TCP/IP Services Using TCPIP$CONFIG   9         HP TCP/IP Services for OpenVMS Configuration Menu   "             Configuration options:  )                    1  -  Core environment *                    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 procedure   %         Enter configuration option: 5   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               %TCPIP-I-INFO, TCP/IP Services shutdown beginning at  5-SEP-2004               15:26:14.39 @               %TCPIP-S-SHUTDONE, TCPIP$FINGER shutdown completedD               %TCPIP-S-SHUTDONE, TCPIP$FTP_CLIENT shutdown completed=               %TCPIP-S-SHUTDONE, TCPIP$FTP shutdown completed E               %TCPIP-S-SHUTDONE, TCPIP$INET_DRIVER shutdown completed @               %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 completed E               %TCPIP-S-SHUTDONE, TCPIP$PWIP_DRIVER shutdown completed ?               %TCPIP-S-SHUTDONE, TCPIP$REXEC shutdown completed @               %TCPIP-S-SHUTDONE, TCPIP$RLOGIN shutdown completed=               %TCPIP-S-SHUTDONE, TCPIP$RSH shutdown completed >               %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   (         3-42 Configuring TCP/IP Services           H                                              Configuring TCP/IP ServicesH                          3.7 Stopping TCP/IP Services Using TCPIP$CONFIG  @               %TCPIP-S-SHUTDONE, TCPIP$TELNET shutdown completed>               %TCPIP-S-SHUTDONE, TCPIP$TFTP shutdown completed=               %TCPIP-S-SHUTDONE, TCPIP$XDM shutdown completed @               %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$CONFIG   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:  ?               HP TCP/IP Services for OpenVMS Configuration Menu   (                   Configuration options:  /                          1  -  Core environment 0                          2  -  Client components0                          3  -  Server components2                          4  -  Optional componentsF                          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: 6   H               The TCP/IP Services startup procedure displays a series ofE               messages similar to the following example (the messages 5               displayed depend on the configuration):            Begin Startup...          H                                         Configuring TCP/IP Services 3-43           #         Configuring TCP/IP Services 7         3.8 Starting TCP/IP Services Using TCPIP$CONFIG   F         %TCPIP-I-INFO, TCP/IP Services startup beginning at 5-SEP-2004         15:27:08.34 6         %TCPIP-I-NORMAL, timezone information verifiedE         %RUN-S-PROC_ID, identification of created process is 00000D42 ;         %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 5         %TCPIP-I-STARTDROUT, starting dynamic routing E         %RUN-S-PROC_ID, identification of created process is 00000C4E ;         %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 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 completed >         %TCPIP-S-STARTDONE, TCPIP$PORTMAPPER startup completed:         %TCPIP-S-STARTDONE, TCPIP$FINGER startup completed7         %TCPIP-S-STARTDONE, TCPIP$FTP startup completed >         %TCPIP-S-STARTDONE, TCPIP$FTP_CLIENT startup completed?         %TCPIP-S-STARTDONE, TCPIP$INET_DRIVER startup completed :         %TCPIP-S-STARTDONE, TCPIP$METRIC startup completedC         %TCPIP-I-NOMAP, no filesystem mapping information available 7         %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 completed E         %RUN-S-PROC_ID, identification of created process is 000002DC ?         %TCPIP-S-STARTDONE, TCPIP$PWIP_DRIVER startup completed 9         %TCPIP-S-STARTDONE, TCPIP$REXEC startup completed :         %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 completed7         %TCPIP-S-STARTDONE, TCPIP$XDM startup completed K         %TCPIP-S-STARTDONE, TCP/IP Services startup completed at 5-SEP-2004     (         3-44 Configuring TCP/IP Services           H                                              Configuring TCP/IP ServicesH                          3.8 Starting TCP/IP Services Using TCPIP$CONFIG           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, C                 set up mapping to a valid file system, as explained @                 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 prevent A                 recurrence of this message during future startups B                 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- 0               tion verification procedure (IVP).  C               You should run the IVP if any of the following apply:   H               o  You loaded the Product Authorization Key (PAK), and youE                  want to verify that the lower-layer software and the <                  Portmapper service are installed correctly.  F               o  You did not load the PAK, but you want to verify thatF                  TCP/IP Services is installed correctly for DECwindows=                  to display the TCP/IP Services applications.   C               o  You require the software to transfer device socket H                  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.  C               Before you run the IVP, make sure TCP/IP Services has C               started and you have SYSPRV, OPER, NETMBX, and TMPMBX                privileges.   H                                         Configuring TCP/IP Services 3-45           #         Configuring TCP/IP Services '         3.9 Verifying the Configuration   E               You can run the IVP from the TCPIP$CONFIG configuration E               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 Configuration G               menu, choose option 7 (Run tests). The Test menu appears, *               as in the following example:  6               HP TCP/IP Services for OpenVMS TEST Menu  #                       Test options:   1                                1  -  Internet IVP -                                2  -  SNMP IVP   0                                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.   #               $ @SYS$TEST:TCPIP$IVP   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$IVP F               command procedure at the command line, the IVP tests theE               basic TCP/IP Services software configuration, as in the G               following example. Here, the test completes successfully:     (         3-46 Configuring TCP/IP Services           H                                              Configuring TCP/IP ServicesH                                          3.9 Verifying the Configuration  +               Enter test option: 1 <Return>                Begin IVP...  (               %%% TCPIP IVP: started %%%  ;               UDP/IP test started at 5-SEP-2004 16:13:03.62 9               UDP/IP test ended at 5-SEP-2004 16:13:03.69 H               UDP/IP transferred successfully in 0 seconds 4198400 bytes  ;               TCP/IP test started at 5-SEP-2004 16:13:04.20 9               TCP/IP test ended at 5-SEP-2004 16:13:04:28 H               TCP/IP transferred successfully in 0 seconds 4198400 bytes  ;               RAW_IP test started at 5-SEP-2004 16:13:41.71 9               RAW_IP test ended at 5-SEP-2004 16:13:41.72 G               RAW_IP transferred successfully in 0 seconds 251000 bytes   7               %%% TCPIP IVP: completed successfully %%% $               IVP request completed.*               Press Return to continue ...  F               If the IVP does not complete successfully, the procedureB               displays error messages. All IVP errors use the same=               format as OpenVMS system messages. For example:   3               %TCPIP-E-IDENT, explanation of error.   G               Table 3-4 lists some common problems that cause IVP error F               messages. If the recommended action does not correct the>               problem, contact your HP support representative.                              H                                         Configuring TCP/IP Services 3-47           #         Configuring TCP/IP Services '         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:                  Begin SNMP IVP...   F               The SNMP IVP requires that TCPIP/IP Services be running.E               It performs the following startups and shutdowns on the I               SNMP service only (other TCP/IP services are not affected):   B               - If SNMP is running, shuts down SNMP before initial                 configuration *               - Starts SNMP and runs testsB               - Shuts down SNMP and restores initial configuration+               - Before exiting, starts SNMP   5               Shutting down the SNMP service... done.   C               Creating temporary read/write community SNMPIVP_6520.   &               Enabling SET operations.  3               Starting up the SNMP service... done.   5                     Saving sysContact: Ralph Nickleby 4                 Setting sysContact to: Julius Caesar4                  Retrieved sysContact: Julius Caesar2               (Retrieved value matches SET value.)5               Restoring sysContact to: Ralph Nickleby   (         3-48 Configuring TCP/IP Services           H                                              Configuring TCP/IP ServicesH                                          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.   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.   )               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 all C               SNMP components have started, or that SNMP tracing is E               enabled and needs to be disabled. For information about E               SNMP trace, refer to the HP TCP/IP Services for OpenVMS                 Management manual.  F                 ________________________Note  ________________________  C                 If options debug is listed in the resolv.conf file, B                 the SNMP ivp will fail. Refer to the Release Notes(                 for further information.  E                 _____________________________________________________       H                                         Configuring TCP/IP Services 3-49           #         Configuring TCP/IP Services +         3.10 Additional Configuration Tasks   +         3.10 Additional Configuration Tasks   E               After you run TCPIP$CONFIG and enable the functionality C               and components appropriate for your network, you need B               to complete additional configuration tasks to enableH               access to product applications. TCP/IP Services provides aH               management command interface and logical names you can useG               to modify or customize the software for your environment.   9               The additional configuration tasks include:   F               o  Populating databases (for example, for BIND and DHCP)  )               o  Setting up user accounts   9               o  Setting up communication and NFS proxies   &               o  Defining print queues  D               o  Setting up, exporting, and maintaining file systems  :               o  Tuning the system for optimum performance  F               Many of the services require additional configuration orG               optimization. For more information about how to configure G               each service, refer to the HP TCP/IP Services for OpenVMS                 Management manual.  2         3.11 Starting and Stopping TCP/IP Services  G               You can use commands in your OpenVMS startup file to have H               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/IP B               Services client or server services without affectingA               other TCP/IP Services components currently running. D               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.   (         3-50 Configuring TCP/IP Services           H                                              Configuring TCP/IP ServicesH                               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 the G               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 any D               definition of them from SYS$MANAGER:SYSTARTUP_VMS.COM.  C               If you want TCP/IP Services to start after you log in C               to your OpenVMS account, the OpenVMS systemwide login E               procedure (typically SYS$MANAGER:SYLOGIN.COM) must have 8               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 Manually   D               To start TCP/IP Services manually, enter the following               command:  *               $ @SYS$STARTUP:TCPIP$STARTUP  C               To stop TCP/IP Services manually, enter the following                command:  +               $ @SYS$STARTUP:TCPIP$SHUTDOWN           H                                         Configuring TCP/IP Services 3-51           #         Configuring TCP/IP Services 2         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. H               This is useful when you change parameters or logical names7               that require the service to be restarted.   /               The following files are provided:   D               o  SYS$STARTUP:TCPIP$service_STARTUP.COM allows you to+                  start the service service.   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:   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:   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 service   (         3-52 Configuring TCP/IP Services           H                                              Configuring TCP/IP ServicesH                               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 enclose ?                 the name in quotation marks. If you defined the C                 service using quotation marks to preserve the case, C                 be sure to use quotation marks when you specify the B                 service name with the startup or shutdown command.  E                 _____________________________________________________   G         3.12 Specifying TCP/IP Services as the Transport for DECwindows               Applications   B               To enable TCP/IP Services as the transport interfaceD               for DECwindows applications, add the following line toC               the SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM command                procedure:  >               $ DECW$SERVER_TRANSPORTS == "DECNET,LOCAL,TCPIP"  &               Then restart DECwindows:  1               $ @SYS$STARTUP:DECW$STARTUP RESTART   C               If DECnet or DECnet-Plus software runs on the system,                start it.   B               To display DECwindows applications from a DECwindows?               client (remote host) to a DECwindows server (your /               workstation), proceed as follows:   4               1. Set up security on the remote host.  C               2. Add the remote client to the local hosts database.   E               3. Add to SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM the                    following line:  A                  $ DECW$SERVER_TRANSPORTS == "DECNET,LOCAL,TCPIP"   C               4. Set the display for the applications to the remote                   host:  F                  $ SET DISPLAY/CREATE/NODE=remote-host/TRANSPORT=TCPIP  H                                         Configuring TCP/IP Services 3-53                       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 host E               or router, use the documentation in this chapter rather F               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.   H               __________________________________________________________E                                                     Replaces Guide to H               Section..._Describes....______________IPv6_Section_...____  9               4.1        How to configure your      2.5.1 0                          system as an IPv6 host.  9               4.2        How to configure your      2.6.1 2                          system as an IPv6 router.  7               4.3        How to configure failSAFE  N/A H               ___________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                    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 are %               started on your system.   F                 ________________________Note  ________________________  D                 Before running the TCPIP$IP6_SETUP.COM configuration=                 procedure, IPv4 must already be configured on @                 your system. (The TCPIP$CONFIG.COM configuration+                 procedure configures IPv4.)   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:   G               o  Whether the system is to be configured as an IPv6 host #                  or an IPv6 router.   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, you C                  must also specify the IPv4 address of the tunnel's                   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.              4-2 Configuring IPv6           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-compatible E                  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 each B                     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, and 3                     if so, the IPv6 address prefix.   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 configuration C               procedure to configure your system as an IPv6 host or H               router, you can optionally configure your system as a BINDE               server (see the HP TCP/IP Services for OpenVMS Guide to D               IPv6). In addition, you can configure failSAFE IP IPv65               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 your E               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 HP TCP/IP Services for OpenVMSB               Guide to IPv6 describes how to make further changes.  H                                                     Configuring IPv6 4-3                    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 procedure 3                  by entering the following command:   5                        $ @SYS$MANAGER:TCPIP$IP6_SETUP   B                  The procedure displays information about the IPv6C                  network configuration procedure and tells you that G                  you can configure the system as either an IPv6 host or                    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 connected A                  to an IPv4-only network and needs to communicate E                  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.            4-4 Configuring IPv6           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::/48   @               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]:   G                  To accept the IPv6 address prefix generated in step 4, "                  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 to C                  native IPv6 sites. If you do not configure a relay H                  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                    Configuring IPv6$         4.1 Configuring an IPv6 Host  7               7. Specify the address of a relay router:   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.   E               8. For each interface on your system, the configuration G                  procedure asks whether you want to enable IPv6 on that E                  interface, as in the following example, where ddn is 2                  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, D                  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 procedure 6                  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                 _____________________________________________________              4-6 Configuring IPv6           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).   E              11. The configuration procedure asks whether you want to <                  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:   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- A                  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                    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.   C                  If you do not want the host to use an IPv6 address =                  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]:   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 you "                  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:   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-IPv6 B                  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:   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 IPv6 =                  address in response to the following prompt:   F                      Enter the destination IPv6 address of tunnel ITn:           4-8 Configuring IPv6           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.   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 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.   C                  If you do not want the host to use an IPv6 address =                  prefix on the tunnel interface, press Enter.   E              20. The configuration procedure asks whether you want to A                  create another IPv6-over-IPv6 configured tunnel:   M                        Create another IPv6 over IPv6 configured tunnel? [NO]:   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 you "                  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.   :                        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:   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- E                  local address. If the next node is reachable through D                  an automatic tunnel, enter the IPv4-compatible IPv6C                  address. For all other connections, enter the IPv6                   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]:   G                  If you want to define another manual route, enter YES. E                  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:                         Daemons:   9                        ND6HOST   Dynamic Updates Disabled                          Interfaces:             4-10 Configuring IPv6            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:   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.   G               1. Invoke the TCPIP$IP6_SETUP.COM configuration procedure 3                  by entering the following command:   /                  $ @SYS$MANAGER:TCPIP$IP6_SETUP   B                  The procedure displays information about the IPv6C                  network configuration procedure and tells you that G                  you can configure the system as either an IPv6 host or                    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 6to4 D                  interface, press Enter. The configuration procedure%                  continues at step 7.   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.   A               4. Enter the node's IPv4 address in response to the "                  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 following                   example:   A                           Your 6to4 site prefix is: 2002:x:x::/48   ?                  This site prefix is advertised to hosts on the H                  interfaces attached to the IPv6 site. This address mustG                  be a valid, globally unique IPv4 address configured on <                  the router's interface to the IPv4 network.               4-12 Configuring IPv6            H                                                         Configuring IPv6H                                           4.2 Configuring an IPv6 Router  G               5. The configuration procedure asks whether you want this ;                  system to function as a 6to4 relay router:   ;                        Configure a 6to4 relay router? [NO]:   C                  If hosts in this border router's 6to4 site need to @                  communicate with native IPv6 sites (IPv6 only),D                  configure this system as a 6to4 relay router. Enter                  YES.   D                  If you do not want the system to function as a 6to4G                  relay router, press Enter. The configuration procedure %                  continues at step 7.   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]?   D                  If you want to enable IPv6 on this interface, press)                  Enter; if not, enter NO.   E                  For each interface on your system, the configuration 5                  procedure repeats steps 7 through 9.   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 to F                  run the RIPng protocol, press Enter; otherwise, enter                  NO.  H                                                    Configuring IPv6 4-13                    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.   C                  If you do not want the router to advertise an IPv6 H                  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, F                  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 next ;                  step 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                 _____________________________________________________   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 IPv6            H                                                         Configuring IPv6H                                           4.2 Configuring an IPv6 Router  @                  Enter the IPv4 address in dotted-decimal format                  (d.d.d.d).   E              12. The configuration procedure asks whether you want to <                  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 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:   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 IPv6 E                  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]:   H                                                    Configuring IPv6 4-15                    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 multiple F                  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.  E              17. 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]:   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 you "                  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- -                  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-IPv6 B                  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 IPv6 =                  address in response to the following prompt:   F                      Enter the destination IPv6 address of tunnel ITn:           4-16 Configuring IPv6            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.   E              22. 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]:   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 multiple F                  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- -                  over-IPv6 configured tunnel:   M                        Create another IPv6 over IPv6 configured tunnel? [NO]:   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 you "                  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                    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 specify ,                  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:   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:   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.   :                        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- E                  local address. If the next node is reachable through D                  an automatic tunnel, enter the IPv4-compatible IPv6C                  address. For all other connections, enter the IPv6                   address.   F              28. Indicate whether you want to configure another manual@                  IPv6 route to an adjacent router or remote IPv6                  network:   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 you E                  choose to configure. If you do not want to configure 3                  another manual route, press Enter.            4-18 Configuring IPv6            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:                         Daemons:                           IP6RTRD                         Interfaces:  ,                        WE0       RIP Enabled,                        IT0       RIP Enabled2                                  Tunnel Source ::17                                  Tunnel Destination ::2 1                                  Prefix AAAA::/64 1                                  Prefix BBBB::/64 E                        TN1       6to4 Tunneling Enabled using 1.2.3.4 >                                  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, 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 ?                  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 been D                        renamed to SYS$SYSTEM:TCPIP$IP6RTRD.CONF_OLD.  H                                                    Configuring IPv6 4-19                    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, follow                these steps:  G               1. Determine the link-local IPv6 addresses that have been C                  dynamically created on each interface by using the H                  ifconfig command, as in the following example. The lastE                  line for each interface contains the IPv6 link-local H                  address. Note that the IPv4 addresses have already beenE                  configured with standby addresses. (The instructions D                  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> ,                       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 IPv6            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:                    $! +                  $! IPv6 failSAFE Addresses                   $! D                  $ 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_shutdown 6                  $ @sys$startup:tcpip$failsafe_startup                  $!                                             H                                                    Configuring IPv6 4-21                       H                                                                        AH         ________________________________________________________________  H                Sample New TCP/IP Services Installation and Configuration      F               This appendix shows a sample installation and configura-F               tion of the TCP/IP Services product on a system on which3               the product has never been installed.   -         A.1 Sample New Installation Procedure   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 the D               product has not been installed. If TCP/IP Services hadG               been installed previously on the system, the installation ;               dialog would differ slightly (see Chapter 2).   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 DEC A                 AXPVMS TCPIP (as shown in the following example).   E                 _____________________________________________________   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.   H            Sample New TCP/IP Services Installation and Configuration A-1           A         Sample New TCP/IP Services Installation and Configuration -         A.1 Sample New Installation Procedure   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.   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. 	         %            Portion done: 100%  1         The following product has been installed: B             DEC VAXVMS TCPIP V5.6-xx               Layered Product  A         DEC VAXVMS TCPIP V5.6-xx: HP TCP/IP Services for OpenVMS.   F             Check the release notes for current status of the product.  	         $   .         A.2 Sample New Configuration Procedure  G               The following example shows a sample configuration dialog H               for the TCP/IP Services, in which the following components               are configured:   !               o  Core environment                  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/IP H               Services had been configured previously on the system, the@               dialog would differ significantly (see Chapter 3).    A                 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 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  -  Domain )                          2  -  Interfaces &                          3  -  Routing,                          4  -  BIND Resolver(                          5  -  Time Zone  6                          A  -  Configure options 1 - 5(                         [E] -  Exit menu  %         Enter configuration option: 1   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  H            Sample New TCP/IP Services Installation and Configuration A-3           A         Sample New TCP/IP Services Installation and Configuration .         A.2 Sample New Configuration Procedure  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: 2   S               HP TCP/IP Services for OpenVMS Interface & Address Configuration Menu   K          Hostname Details: Configured=Not Configured, Active=Not Configured             Configuration options:   5            1  -  WE0 Menu (EWA0: TwistedPair 100mbps)   5            2  -  IE0 Menu (EIA0: TwistedPair 100mbps)   5            3  -  IE1 Menu (EIB0: TwistedPair 100mbps)              [E] -  Exit menu  %         Enter configuration option: 1   M               HP TCP/IP Services for OpenVMS Interface WE0 Configuration Menu             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   E         A-4 Sample New TCP/IP Services Installation and Configuration            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 Menu             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). I           This can be changed later via the Interface Configuration Menu.   9         Updated system hostname in configuration database   <         Added address WE0:10.0.1.1 to configuration database  S               HP TCP/IP Services for OpenVMS Interface & Address Configuration Menu   H          Hostname Details: Configured=yourmachine, Active=Not Configured            Configuration options:   5            1  -  WE0 Menu (EWA0: TwistedPair 100mbps) E            2  -  10.0.1.1/16         yourmachine           Configured   5            3  -  IE0 Menu (EIA0: TwistedPair 100mbps)   5            4  -  IE1 Menu (EIB0: TwistedPair 100mbps)              [E] -  Exit menu  ,         Enter configuration option: <Return>  H            Sample New TCP/IP Services Installation and Configuration A-5           A         Sample New TCP/IP Services Installation and Configuration .         A.2 Sample New Configuration Procedure  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: 3   %         DYNAMIC ROUTING Configuration   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 want E                 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 other <                 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) 3                     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]: S         Enter your Default Gateway host name or address: yourgateway.yourdomain.com   E         A-6 Sample New TCP/IP Services Installation and Configuration            H                Sample New TCP/IP Services Installation and ConfigurationH                                   A.2 Sample New Configuration Procedure  M                 yourgateway.yourdomain.com is not in the local host database.   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  -  Domain )                          2  -  Interfaces &                          3  -  Routing,                          4  -  BIND Resolver(                          5  -  Time Zone  6                          A  -  Configure options 1 - 5(                         [E] -  Exit menu  %         Enter configuration option: 4   #         BIND RESOLVER Configuration   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 for                  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. A                 Press Return at the prompt to terminate the list.   /         Enter your BIND server name: yourserver   =                 yourserver is not in the local host database.   7         Enter Internet address for yourserver: 10.0.2.2   -         Enter next BIND server name: <Return>   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  -  Domain )                          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 OpenVMS (                          7  -  Run tests  6                          A  -  Configure options 1 - 4;                         [E] -  Exit configuration procedure   %         Enter configuration option: 2   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 Configuration            H                Sample New TCP/IP Services Installation and ConfigurationH                                   A.2 Sample New Configuration Procedure           TELNET Configuration  )         Service is defined in the SYSUAF. 9         Service is defined in the TCPIP$SERVICE database.          Service is not enabled.          Service is stopped.   -                 TELNET configuration options:   8                          1 - Enable service on this node  @                          2 - Enable & Start service on this node  7                         [E] - Exit TELNET configuration   %         Enter configuration option: 2   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 ...   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 Menu   &                 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 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: 3   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 Stopped U             3 - DHCP         Disabled Stopped      14 - POP          Disabled Stopped U             4 - FINGER       Disabled Stopped      15 - PORTMAPPER   Disabled Stopped U             5 - FTP          Disabled Stopped      16 - RLOGIN       Enabled  Started U             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  Started U            10 - NFS          Disabled Stopped      21 - TFTP         Disabled Stopped U            11 - LOCKD/STATD  Disabled Stopped      22 - XDM          Disabled Stopped   *             A  -  Configure options 1 - 22            [E] -  Exit menu   %         Enter configuration option: 5            FTP Configuration   )         Service is defined in the SYSUAF. 9         Service is defined in the TCPIP$SERVICE database.          Service is not enabled.          Service is stopped.   *                 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           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 installed F         %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 completed   )         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 Stopped U             3 - DHCP         Disabled Stopped      14 - POP          Disabled Stopped U             4 - FINGER       Disabled Stopped      15 - PORTMAPPER   Disabled Stopped U             5 - FTP          Enabled  Started      16 - RLOGIN       Enabled  Started U             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  Started U            10 - NFS          Disabled Stopped      21 - TFTP         Disabled Stopped U            11 - LOCKD/STATD  Disabled Stopped      22 - XDM          Disabled Stopped   *             A  -  Configure options 1 - 22            [E] -  Exit menu   ,         Enter configuration option: <Return>  A                 HP TCP/IP Services for OpenVMS Configuration Menu   &                 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           A         Sample New TCP/IP Services Installation and Configuration .         A.2 Sample New Configuration Procedure  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: 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 startup 8         %TCPIP-I-PROXYLOADED, loaded 0 NFS proxy recordsA         %TCPIP-I-LOADSERV, loading TCPIP server proxy information I         %TCPIP-I-SERVLOADED, auxiliary server loaded with 0 proxy 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 completed X         %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 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 OpenVMS (                          7  -  Run tests  F         A-12 Sample New TCP/IP Services Installation and Configuration           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                               E      ________________________________________________________________   E                                                                 Index     @      A                                    Configuration database1      ___________________________            files ?      Advanced Server for OpenVMS           creating,  3-10, A-3 A        configuring, 3-34                  Configuration procedure A      Anonymous FTP                         See Configuring TCP/IP D        configuring, 3-34                      Services; TCPIP$CONFIGE      Automatic configuration of               configuration procedure B         TCP/IP Services, 3-5              Configuration worksheet,  /      B                                      1-9 E      ___________________________          Configuring TCP/IP Services @      BG device message                     See also TCPIP$CONFIGE        during installation, 2-5               configuration procedure :      BIND resolver                         automatic,  3-5D        configuring, 3-24, A-3              client environment,  3-275      BIND server                              to 3-30 A        configuring, 3-31                   client services,  3-29 >      Booting OpenVMS,  1-6, 2-5            configuration filesA        precaution, 2-6                        creating new,  3-10 E      BOOTP server                          core environment,  3-12 to 2        configuring, 3-31                      3-27  ?      C                                     description of major 9      ___________________________              tasks,  1-1 5      CD distribution kit                   IPv6,  4-1 B        inspecting, 1-3                     new configuration,  1-1E      Client environment                    optional components,  3-34 C        configuring, 3-27, A-3              postconfiguration tasks, 2      Client services                          3-50B        starting and stopping               preliminary tasks,  3-1D          individually,  3-52               server environment,  3-31  5                                               to 3-33 ?                                            servers,  3-31, 3-33   E                                                               Index-1                  G         Configuring TCP/IP Services         Configuring TCP/IP Services A           (cont'd)                            TCPIP$CONFIG output A          tasks, recommended                      example (cont'd)   B             sequence,  3-2                       Server ComponentsG          TCPIP$CONFIG menus,  3-10,                 Configuration menu, =             3-12                                    3-31, A-3 :          TCPIP$CONFIG option                     time zoneA             commands,  3-38                         configuration B          TCPIP$CONFIG output                        example, 3-27,7             example,  A-3 to A-13                   A-3 B             beginning,  3-9                      XDM Configuration>             BIND resolver,  3-26                    menu, 3-32A             Client Environment                time required,  1-2 G                Configuration menu,            verifying services,  3-45 <                3-28, A-3                    Core EnvironmentB             Core Environment                   Configuration menu,8                Configuration menu,             3-13, A-3                3-13, A-3G             creating database               D__________________________ :                files,  3-10, A-3            Database filesB             Dynamic Routing                   creating,  3-10, A-3>                Configuration menu,          DECnet over TCP/IPD                3-22, A-3                      configuration example,5             failSAFE configuration               3-36 G                ,  3-22, A-3                   configuring to use,  3-34 6                options,  3-38               DECwindowsE             FTP Client                        components required for :                Configuration menu,               XDM, 3-33E                3-29                           defining TCP transport, 5             Interface                            3-53 F                Configuration menu,            requirements for productB                3-14                              installation, 1-47             Kerberos Applications           DHCP client @                Configuration menu,            configuring,  3-287                3-37                         DHCP server @             Main Configuration                configuring,  3-31@                menu,  3-10, A-3               configuring TCP/IP>             Optional Components                  Services, 3-50                Configuration menu,          DiskF                3-34, A-3                      space requirements,  1-5F             PWIP configuration                system, backing up,  1-4                  example,  3-36            Index-2                           Distribution kitG          inspecting,  1-3                   G__________________________ ?         Domain                              Global pagelets and 7          configuring,  3-14, A-3               sections >         Dynamic routing                       increasing,  1-6@          configuring,  3-22, A-3              requirements,  1-6  -         E__________________________         I G         EAK                                 ___________________________IG                                             Installing TCP/IP Services,89          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 phaseRD         Error messages                           sample output,  2-5C          at SNMP verification,                installed files,  2-6 ?             3-49                              major tasks,  1-1 D          IVP (installation                    new installation,  A-2F             verification procedure)           sample output,  2-4, A-1A             ,  3-47                           time required,  1-2r5          TCPIP-I-NOMAP,  3-45               Interface ?                                               configuring,  A-3 G         F__________________________           first-time configuration,e5         failSAFE IP                              3-14 C          configuration options              Interface Configuration 9             menu,  3-38                        menu, 3-14 .          configuring,  3-34, 3-35           IPF          configuring and enabling             configuring interface IP>             client,  3-37                        address, 3-160          configuring IP address,            IPv6?             3-19                              configuring,  4-1 7          configuring target IP                EAK,  1-8dD             address,  3-16, A-3               failSAFE IP addresses,5          defined,  3-35                          4-20_@          EAK,  1-9                            warning message inC          IPv6 addresses,  4-20                   TCPIP$CONFIG, 3-13 5         FINGER server                       IPv6 hostd?          configuring,  3-31                   configuring,  4-4A7         FTP client                          IPv6 router @          configuring,  3-29                   configuring,  4-11=         FTP server                          IVP (installationeF          configuring,  3-31, A-3               verification procedure)@                                               description,  3-45C                                               error messages,  3-47 <                                               example,  3-46  H                                                                  Index-3    o                     IVP (installationsG           verification procedure)           N__________________________o  6           (cont'd)                          NFS client  @          OpenVMS TEST menu,  3-46             configuring,  3-286          SNMP verification example          NFS server@             ,  3-48                           configuring,  3-31F                                             NOMAP error message,  3-45A         K__________________________         Nonpaged dynamic pool >         Kerberos                              increasing,  1-76          benefits,  3-35                    NTP server@          configuration menu,  3-37            configuring,  3-31  -          configuring and enabling,          O G             3-36                            ____________________________;          configuring to use,  3-34,         OpenVMS Cluster G             3-35                              configuring TCP/IP before.=                                                  joining, 3-5rG         L__________________________           joining as a TCP/IP host,r4         LBROKER server                           3-4=          configuring,  3-31                   running a newly-G         License Product                          configured TCP/IP host 8           Authorization Key                      in, 3-4F                                             OpenVMS License Management=          See PAK                               Facility (LMF).D         LOCKD/STATD server                    using to register PAK,4          configuring,  3-31                      1-4D         LPR/LPD client                      OpenVMS operating system?          configuring,  3-28                   reboot,  1-6, 2-5mA         LPR/LPD server                           precaution,  2-6P=          configuring,  3-31                   upgrading,  1-4e  D                                             OpenVMS TEST menu,  3-46?         M__________________________         Optional componentsi  A         Memory                                Advanced Server forv>          physical memory                         OpenVMS, 3-35B             requirements,  1-5                Anonymous FTP,  3-35H         Menus                                 configuration menu,  3-34,4          TCPIP$CONFIG,  3-10                     A-3@         METRIC server                         failSAFE IP,  3-35F          configuring,  3-31                   Kerberos authentication,5         Mixed-case service names,                3-35 A           3-52                                PATHWORKS (Advanced >                                                  Server), 3-35@                                               PWIP driver,  3-35F                                               SRI QIO interface,  3-35           Index-4o    n            9                                             RLOGIN serverf@         P__________________________           configuring,  3-316         PAK                                 RMT server@          registering,  1-4                    configuring,  3-313         PATHWORKS                           Routing D          configuring,  3-34, 3-36             default configuration,5          Internet Protocol driver                3-24   -             See PWIP                        S.G         PC-NFS server                       ___________________________ 8          configuring,  3-31                 Secure Shell5         POLYCENTER Software                   See SSH 3           Installation utility              Servers H          for installing or                    configuration menu,  3-31,4             upgrading,  2-1 to                   A-3C             2-7                               starting and stopping2C         Pool, nonpaged dynamic,                  individually, 3-52 9           1-7                               Service names ?         POP server                            for user-supplied.?          configuring,  3-31                      services, 3-52a?         PORTMAPPER server                     mixed-case,  3-52o4          configuring,  3-31                 Services:         Postconfiguration tasks,              user-written@           3-50                                   starting up andG         Preconfiguration tasks,                     shutting down, 3-52 F           3-1                               Shutdown command procedureC         PWIP                                  failure of,  1-6, 2-6 F          configuring,  3-35, 3-36             for individual services,5                                                  3-52oG         R__________________________           for user-written service,r5         Reboot, 2-6                              3-52.=          precaution,  2-6                     invoking,  3-51 C         Release notes                         output example,  3-42.B          extracting into a .TXT               version to use,  2-2  @             file,  1-4                      Shutting down TCP/IP7          location after                        Servicesi  A             installation,  2-6                See Stopping TCP/IP 9         REXEC and RSH client                     ServicesO7          configuring,  3-28                 SMTP client @         RIGHTSLIST database, 3-1              configuring,  3-280         RLOGIN client                       SNMP<          configuring,  3-28                   testing,  3-48@                                               verification error?                                                  messages, 3-49   H                                                                  Index-5 u  n                     SNMP (cont'd) G          verification example,              T__________________________   1             3-48                            TaskseC         SNMP server                           major, installing and.A          configuring,  3-31                      configuring, 1-1.;         SRI QIO                             TCP/IP ServicesTG          configuring to use,  3-34            and Anonymous FTP access,/5         SSH                                      3-35o=          configuration note,  3-28,           client servicesPF             3-31                                 configuring,  3-27 to8          EAK,  1-9                                  3-30F         SSH client                               starting and stoppingF          configuring,  3-28                         individually, 3-52D         SSH server                            configuration,  3-2 to5          configuring,  3-31                      3-49 :         Starting TCP/IP Services,                new,  A-2A           3-50                                configuration files @          after configuration,  3-43              converting from<          automatically,  3-51                       previousF          manually,  3-51                            configuration, 3-8G          using TCPIP$CONFIG,  3-43            configuration preparation 6         Startup command procedure                , 1-9>          failure of,  1-6, 2-6                core environmentF          for individual services,                configuring,  3-12 to8             3-52                                    3-27G          for user-written service,            installation,  2-1 to 2-7 :             3-52                                 new,  A-1G          invoking,  3-51                      installation preparation,-;          output example,  3-43,                  1-2 to 1-9 5             A-13                              servers F         Stopping TCP/IP Services,                configuring,  3-31 to8           3-50                                      3-33F          automatically,  3-51                    starting and stoppingF          manually,  3-51                            individually, 3-52<          using TCPIP$CONFIG,  3-41            starting afterD         System Authorization File                configuration, 3-40C           (SYSUAF),  3-1                      starting and stoppinggD          OpenVMS Cluster,  3-4                   automatically, 3-51C         System parameters                     starting and stopping           checking and changing?             before installing,  1-6              manually, 3-51.<             to 1-7                            starting usingC                                                  TCPIP$CONFIG, 3-43            Index-6                  F         TCP/IP Services (cont'd)            TCPIP$CONFIG configurationA          stopping using                        procedure (cont'd)   @             TCPIP$CONFIG,  3-41               PWIP configuration>          upgrading,  2-1 to 2-7                  example, 3-36?          verifying,  3-45                     Server ComponentsoD         TCPIP$CONFIG configuration               Configuration menu,:           procedure                              3-31, A-3  E          See also Configuring                 time zone configuration C             TCP/IP Services                      example, 3-27, A-3iE          BIND resolver                        XDM Configuration menu, 5             configuration,  3-26                 3-32IG          Client Environment                 TCPIP$IP6_SETUP.COM command 8             Configuration menu,                procedure@             3-28, A-3                         introduction,  4-1C          Core Environment                   TCPIP$IP6_SETUP commandh8             Configuration menu,                procedureA             3-13, A-3                         configuring an IPv6e=          Dynamic Routing                         router, 4-11dD             Configuration menu,               configuring IPv6 host,4             3-22, A-3                            4-4G          failSAFE configuration             TCPIP-I-NOMAP error message 5             example,  3-22, A-3                , 3-45d9          failSAFE configuration             TELNET clientfE             options menu,  3-38               configuring,  3-28, A-3 9          FTP Client Configuration           TELNET serverr@             menu,  3-29                       configuring,  3-317          Interface Configuration            TFTP server @             menu,  3-14                       configuring,  3-315          Kerberos Applications              Time zoneiE             Configuration menu,               configuring,  3-27, A-3s;             3-37                            Troubleshooting4E          Main Configuration menu,             configuration proceduren?             3-10, A-3                            problems, 3-47u  -          menus                              U G             description,  3-10              ___________________________ 5          Optional Components                UIC codest=             Configuration menu,               assigning,  1-7 F             3-34, A-3                       Upgrading TCP/IP Services,9          output example,  3-9 to               2-1 to 2-7i7             3-38, 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-34r  H                                                                  Index-7 n  o            @         User identification code            Verifying the TCP/IPF           (UIC)                                Services configuration,3          assigning,  1-7                       3-45s  G         V__________________________         X__________________________e  6         Verifying the SNMP                  XDM server<           configuration,  3-48                and DECwindowsC                                                  requirements, 3-33 @                                               configuring,  3-32                                                                               Index-8u