HP TCP/IP Services for OpenVMS Installation and Configuration Order Number: AA-LU49P-TE September 2003 This manual explains how to install and configure the HP TCP/IP Services for OpenVMS product on your OpenVMS system. Revision Information: This guide supersedes the Compaq TCP/IP Services for OpenVMS Installation and Configuration manual, Version 5.3. Software Version: HP TCP/IP Services for OpenVMS Version 5.4 Operating Systems: HP OpenVMS Alpha Versions 7.3-1 and 7.3-2 Hewlett-Packard Company Palo Alto, California __________________________________________________________ © Copyright 2003 Hewlett-Packard Development Company, L.P. UNIX[R] is a registered trademark of The Open Group. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Proprietary computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. ZK6524 The HP TCP/IP Services for OpenVMS documentation is available on CD-ROM. ________________________________________________________________ Contents Preface.................................................. v 1 Preparing to Install and Configure TCP/IP Services 1.1 Understanding the Major Tasks................ 1-1 1.2 Preinstallation Tasks........................ 1-2 1.2.1 Inspecting the Distribution Kit.......... 1-3 1.2.2 Extracting the Release Notes............. 1-4 1.2.3 Backing Up the System Disk and Upgrading OpenVMS.................................. 1-4 1.2.4 Registering the License Product Authorization Key........................ 1-4 1.2.5 Checking the Disk Space.................. 1-5 1.2.6 Checking the Physical Memory............. 1-5 1.2.7 Checking the System Parameters........... 1-5 1.2.7.1 Global Pagelets and Global Sections ... 1-6 1.2.7.2 Nonpaged Dynamic Pool.................. 1-6 1.2.8 Assigning a User Identification Code..... 1-7 1.2.9 Remove Early Adopters Kits (EAKs)........ 1-8 1.3 Assembling Configuration Information......... 1-9 2 Installing TCP/IP Services 2.1 Invoking the Installation Procedure.......... 2-1 2.2 Stepping Through the Installation Procedure.................................... 2-3 2.3 Postinstallation Tasks....................... 2-5 iii 3 Configuring TCP/IP Services 3.1 Recommended Order for Configuring TCP/IP Services..................................... 3-1 3.2 Automatic Configuration of TCP/IP Services Using DHCP Client............................ 3-3 3.3 Running TCPIP$CONFIG......................... 3-4 3.3.1 Converting Existing TCP/IP Services Configuration Files (Upgrade Only)....... 3-4 3.3.2 Creating New TCP/IP Services Configuration Files...................... 3-6 3.3.3 Understanding the Configuration Menus.... 3-6 3.3.4 Configuring the Core Environment......... 3-8 3.3.4.1 Domain Configuration................... 3-10 3.3.4.2 Interface Configuration................ 3-10 3.3.4.3 failSAFE IP Target Address Configuration.......................... 3-11 3.3.4.4 Dynamic Routing Configuration.......... 3-14 3.3.4.5 BIND Resolver Configuration............ 3-16 3.3.4.6 Time Zone Configuration................ 3-16 3.3.5 Configuring the Client Environment....... 3-17 3.3.6 Configuring the Server Environment....... 3-20 3.3.7 Configuring the Optional Components...... 3-23 3.3.7.1 Configuring and Enabling Kerberos Support................................ 3-25 3.3.7.2 Configuring and Enabling failSAFE IP Support................................ 3-27 3.4 Using TCPIP$CONFIG Option Commands to Bypass TCPIP$CONFIG Menus........................... 3-27 3.5 Making Configuration Changes Take Effect..... 3-29 3.6 Stopping TCP/IP Services Using TCPIP$CONFIG................................. 3-30 3.7 Starting TCP/IP Services Using TCPIP$CONFIG................................. 3-32 3.8 Verifying the Configuration.................. 3-34 3.8.1 Running the IVP from the TCPIP$CONFIG Command Procedure........................ 3-35 3.8.2 Running the IVP from the OpenVMS DCL Prompt................................... 3-35 3.8.3 Verifying the TCP/IP Services Internet Configuration............................ 3-35 3.8.4 Verifying the SNMP Configuration......... 3-37 3.9 Additional Configuration Tasks............... 3-38 iv 3.10 Starting and Stopping TCP/IP Services........ 3-39 3.10.1 Automatically Starting and Stopping TCP/IP Services.......................... 3-39 3.10.2 Starting and Stopping TCP/IP Services Manually................................. 3-40 3.10.3 Starting and Stopping Individual Services ......................................... 3-40 3.10.4 Starting and Stopping User-Written Services................................. 3-41 3.11 Specifying TCP/IP Services as the Transport for DECwindows Applications.................. 3-42 A Sample New TCP/IP Services Installation and Configuration A.1 Sample New Installation Procedure............ A-1 A.2 Sample New Configuration Procedure........... A-2 Index Examples 2-1 TCP/IP Services Installation: Sample POLYCENTER Software Installation Utility Procedure................................ 2-3 Tables 1 TCP/IP Services Documentation............ vi 1-1 Major Tasks: Installing and Configuring.............................. 1-2 1-2 Preinstallation Tasks.................... 1-3 1-3 Configuration Planning Worksheet......... 1-10 3-1 Configuring TCP/IP Services.............. 3-2 3-2 Making Configuration Changes Take Effect................................... 3-29 3-3 Troubleshooting IVP Errors............... 3-37 v ________________________________________________________________ Preface The HP TCP/IP Services for OpenVMS product is the HP implementation of the TCP/IP networking protocol suite and internet services for OpenVMS Alpha systems. TCP/IP Services provides a comprehensive suite of functions and applications that support industry-standard protocols for heterogeneous network communications and resource sharing. This manual explains how to install and configure the HP TCP/IP Services for OpenVMS (TCP/IP Services) networking software on an OpenVMS system. This manual reflects the installation and configuration procedures for Version 5.4 of the TCP/IP Services product. For information about last-minute changes to these procedures, see the HP TCP/IP Services for OpenVMS Release Notes. Intended Audience This manual is for experienced OpenVMS and UNIX system managers and assumes a working knowledge of OpenVMS system management, TCP/IP networking, and TCP/IP terminology. Document Structure This manual contains three chapters and one appendix: o Chapter 1 explains how to prepare for installing and configuring TCP/IP Services. o Chapter 2 describes how to install TCP/IP Services on an OpenVMS system using the POLYCENTER Software Installation utility. v o Chapter 3 provides guidelines on how to configure the TCP/IP Services components after installation. o Appendix A provides a sample installation and configuration display as might appear on an OpenVMS system upon which TCP/IP Services has not been installed previously. The display examples in Chapter 3 show what might be seen when you upgrade TCP/IP Services software. Related Documents Table 1 lists the documents available with this version of TCP/IP Services. Table_1_TCP/IP_Services_Documentation___________________________ Manual Contents ________________________________________________________________ Compaq TCP/IP Services This manual provides conceptual for OpenVMS Concepts and information about TCP/IP networking Planning on OpenVMS systems, including general planning issues to consider before configuring your system to use the TCP/IP Services software. This manual also describes the manuals in the TCP/IP Services documentation set and provides a glossary of terms and acronyms for the TCP/IP Services software product. HP TCP/IP Services for The release notes provide version- OpenVMS Release Notes specific information that supersedes the information in the documentation set. The features, restrictions, and corrections in this version of the software are described in the release notes. Always read the release notes before installing the software. (continued on next page) vi Table_1_(Cont.)_TCP/IP_Services_Documentation___________________ Manual Contents ________________________________________________________________ HP TCP/IP Services for This manual explains how to install OpenVMS Installation and and configure the TCP/IP Services Configuration product. HP TCP/IP Services for This manual describes how to use OpenVMS User's Guide the applications available with TCP/IP Services such as remote file operations, email, TELNET, TN3270, and network printing. HP TCP/IP Services for This manual describes how to configure OpenVMS Management and manage the TCP/IP Services product. HP TCP/IP Services This manual describes the TCP/IP for OpenVMS Management Services management commands. Command Reference HP TCP/IP Services This reference card lists the TCP/IP for OpenVMS Management management commands by component and Command Quick Reference describes the purpose of each command. Card HP TCP/IP Services for This reference card contains OpenVMS UNIX Command information about commonly performed Equivalents Reference network management tasks and their Card corresponding TCP/IP management and Tru64 UNIX command formats. Compaq TCP/IP Services This manual presents an overview for OpenVMS ONC RPC of high-level programming using Programming open network computing remote procedure calls (ONC RPCs). This manual also describes the RPC programming interface and how to use the RPCGEN protocol compiler to create applications. HP TCP/IP Services for This manual describes how to OpenVMS Guide to SSH configure, set up, use, and manage the SSH for OpenVMS software. (continued on next page) vii Table_1_(Cont.)_TCP/IP_Services_Documentation___________________ Manual Contents ________________________________________________________________ Compaq TCP/IP Services This manual describes how to for OpenVMS Sockets use the Sockets API and OpenVMS API and System Services system services to develop network Programming applications. Compaq TCP/IP Services This manual describes the Simple for OpenVMS SNMP Network Management Protocol (SNMP) Programming and and the SNMP application programming Reference interface (eSNMP). It describes the subagents provided with TCP/IP Services, utilities provided for managing subagents, and how to build your own subagents. HP TCP/IP Services This manual provides information for OpenVMS Tuning and about how to isolate the causes of Troubleshooting network problems and how to tune the TCP/IP Services software for the best performance. HP TCP/IP Services for This manual describes the IPv6 OpenVMS Guide to IPv6 environment, the roles of systems in this environment, the types and function of the different IPv6 addresses, and how to configure TCP/IP __________________________Services_to_access_the_6bone_network._ For additional information about HP OpenVMS products and services, visit the following World Wide Web address: http://www.hp.com/go/openvms For a comprehensive overview of the TCP/IP protocol suite, refer to the book Internetworking with TCP/IP: Principles, Protocols, and Architecture, by Douglas Comer. viii Reader's Comments HP welcomes your comments on this manual. Please send comments to either of the following addresses: Internet openvmsdoc@hp.com Postal Hewlett-Packard Company Mail OSSG Documentation Group, ZKO3-4/U08 110 Spit Brook Rd. Nashua, NH 03062-2698 How to Order Additional Documentation For information about how to order additional documenta- tion, visit the following World Wide Web address: http://www.hp.com/go/openvms/doc/order Conventions The name TCP/IP Services means both: o HP TCP/IP Services for OpenVMS Alpha o HP TCP/IP Services for OpenVMS VAX The name UNIX refers to the HP Tru64 UNIX operating system. The following conventions are used in this manual. In addition, please note that all IP addresses are fictitious. Ctrl/x A sequence such as Ctrl/x indicates that you must hold down the key labeled Ctrl while you press another key or a pointing device button. PF1 x A sequence such as PF1 x indicates that you must first press and release the key labeled PF1 and then press and release another key or a pointing device button. ix In examples, a key name enclosed in a box indicates that you press a key on the keyboard. (In text, a key name is not enclosed in a box.) In the HTML version of this document, this convention appears as brackets, rather than a box. . . . A horizontal ellipsis in examples indi- cates one of the following possibilities: o Additional optional arguments in a statement have been omitted. o The preceding item or items can be repeated one or more times. o Additional parameters, values, or other information can be entered. . A vertical ellipsis indicates the . omission of items from a code example . or command format; the items are omitted because they are not important to the topic being discussed. ( ) In command format descriptions, parentheses indicate that you must enclose choices in parentheses if you specify more than one. [ ] In command format descriptions, brackets indicate optional choices. You can choose one or more items or no items. Do not type the brackets on the command line. However, you must include the brackets in the syntax for OpenVMS directory specifications and for a substring specification in an assignment statement. x | In command format descriptions, vertical bars separate choices within brackets or braces. Within brackets, the choices are optional; within braces, at least one choice is required. Do not type the vertical bars on the command line. { } In command format descriptions, braces indicate required choices; you must choose at least one of the items listed. Do not type the braces on the command line. bold type Bold type represents the introduction of a new term. It also represents the name of an argument, an attribute, or a reason. italic type Italic type indicates important information, complete titles of manuals, or variables. Variables include information that varies in system output (Internal error number), in command lines (/PRODUCER=name), and in command parameters in text (where dd represents the predefined code for the device type). UPPERCASE TYPE Uppercase type indicates a command, the name of a routine, the name of a file, or the abbreviation for a system privilege. Example This typeface indicates code examples, command examples, and interactive screen displays. In text, this type also identifies URLs, UNIX commands and pathnames, PC-based commands and folders, and certain elements of the C programming language. - A hyphen at the end of a command format description, command line, or code line indicates that the command or statement continues on the following line. xi numbers All numbers in text are assumed to be decimal unless otherwise noted. Nondecimal radixes-binary, octal, or hexadecimal-are explicitly indicated. xii 1 ________________________________________________________________ Preparing to Install and Configure TCP/IP Services This chapter explains how to prepare for installing and configuring HP TCP/IP Services for OpenVMS software. 1.1 Understanding the Major Tasks Installing the TCP/IP Services software takes just a few minutes to complete. You can install the software during the OpenVMS operating system installation procedure or as a layered product. After you install TCP/IP Services, you need to enable the services and verify the configuration through the menu- driven TCPIP$CONFIG configuration procedure. This step may take about 15 minutes to complete. Table 1-1 lists the major tasks involved in installing and configuring TCP/IP Services and the sections that describe these tasks. Preparing to Install and Configure TCP/IP Services 1-1 Preparing to Install and Configure TCP/IP Services 1.1 Understanding the Major Tasks Table_1-1_Major_Tasks:_Installing_and_Configuring_________ Step Task to perform... Described in... __________________________________________________________ 1 Prepare for installation and Sections 1.2 and configuration. 1.3 2 Shut down any previous versions Section 2.1 of TCP/IP Services running on the system. 3 Install TCP/IP Services. Chapter 2 4 Configure TCP/IP Services Chapter 3 according to your network needs. 5 Start TCP/IP Services. Section 3.5 6 Verify the configuration. Section 3.8 7 Complete additional configuration Section 3.9 _____and_setup_tasks,_as_appropriate._____________________ 1.2 Preinstallation Tasks Table 1-2 lists the tasks you should complete before you install TCP/IP Services on your system, and the sections that describe these tasks. 1-2 Preparing to Install and Configure TCP/IP Services Preparing to Install and Configure TCP/IP Services 1.2 Preinstallation Tasks Table_1-2_Preinstallation_Tasks___________________________ Step Task to perform... Described in... __________________________________________________________ 1 Inspect the distribution kit. Section 1.2.1 2 Extract and read the TCP/IP Section 1.2.2 Services release notes. 3 Back up the system disk. Section 1.2.3 4 Perform an OpenVMS operating Section 1.2.3 system upgrade, if applicable. 5 Register the TCP/IP Services Section 1.2.4 license PAK. 6 Check the disk space, memory, and Sections 1.2.5 system parameters. through 1.2.7 7 Assign a user identification code Section 1.2.8 (UIC), if necessary. 8 Assemble information for Section 1.3 configuration. 9 Remove any Version 5.0 IPv6 and Section 1.2.9 Version 5.3 SSH or failSAFE Early _____Adopters_Kits_(EAKs).________________________________ 1.2.1 Inspecting the Distribution Kit Make sure you have a complete software distribution kit. If you have the OpenVMS consolidated distribution CD-ROM kit, also known as the Software Products Library (SPL), check the CD master index for the location of the TCP/IP Services for OpenVMS kit. If you have an individual CD- ROM, supply the device name (such as DKAn) for the media when you issue the command to install TCP/IP Services. Check that the kit contains everything listed on the Bill of Materials (BOM). If anything is missing or damaged, contact your HP representative. 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 The HP TCP/IP Services for OpenVMS Release Notes document contains important information you should know before you install the product. You can have the POLYCENTER Software Installation utility extract the release notes as either a text file or a PostScript file. To extract the release notes as a text file, enter the following POLYCENTER Software Installation utility command: $ PRODUCT EXTRACT FILE TCPIP/SELECT=TCPIP054.RELEASE_NOTES To extract the release notes as a PostScript file, enter the following: $ PRODUCT EXTRACT FILE TCPIP/SELECT=TCPIP054_RELEASE_NOTES.PS 1.2.3 Backing Up the System Disk and Upgrading OpenVMS Before you install TCP/IP Services, HP recommends that you back up the system disk using the backup procedures established at your site. After the backup operation is complete, you should upgrade the OpenVMS operating system, if applicable. For information about backing up a system disk, see the HP OpenVMS System Manager's Manual: Essentials. For information about how to upgrade OpenVMS, refer to the appropriate OpenVMS upgrade and installation manual. 1.2.4 Registering the License Product Authorization Key Before you install TCP/IP Services on a newly licensed node or cluster, you must register a License Product Authorization Key (PAK) using the OpenVMS License Management Facility (LMF). Without a PAK, you can use only DECwindows TCP/IP Transport software. If you are upgrading TCP/IP Services on a node or cluster that is licensed for this software, you have already completed the License PAK registration requirements. If you ordered the license and the media together, the PAK is included with your distribution kit. Otherwise, the PAK is shipped separately to the location specified on the license order. 1-4 Preparing to Install and Configure TCP/IP Services Preparing to Install and Configure TCP/IP Services 1.2 Preinstallation Tasks If you are also installing prerequisite or optional software, review the PAK status and install the PAKs for any prerequisite or optional software before you install TCP/IP Services. To register a license, log in to the SYSTEM account and do one of the following: o Run the SYS$UPDATE:VMSLICENSE.COM file and enter the data from your License PAK. o At the DCL prompt, enter the LICENSE REGISTER command and the appropriate qualifiers. You must register a license for each node in an OpenVMS Cluster. For complete information about LMF, see the OpenVMS License Management Utility Manual. 1.2.5 Checking the Disk Space Make sure your system has at least 125,000 blocks of disk space available. The actual disk space needed varies depending on the system environment, configuration, and software options. To find out how many free blocks exist on the system disk, enter: $ SHOW DEVICE SYS$SYSDEVICE 1.2.6 Checking the Physical Memory Make sure your system's physical memory is at least 32 megabytes. To check the memory, enter: $ SHOW MEMORY/FULL 1.2.7 Checking the System Parameters Most systems have adequate system resources readily available to include the TCP/IP Services software. However, you should check the system parameters outlined in the following sections. Make any necessary changes to the MODPARAMS.DAT file, then run AUTOGEN, and reboot your system. 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.1 Global Pagelets and Global Sections The TCP/IP Services software requires 65 global sections and 8100 global pagelets. To check the number of available global pagelets and global sections, enter WRITE commands with the F$GETSYI 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 To increase the global pagelets and global sections, add statements to the SYS$SYSTEM:MODPARAMS.DAT file that increase the values of the system parameters GBLPAGES and GBLSECTIONS, as in the following example: ADD_GBLPAGES = 7500 ADD_GBLSECTIONS = 75 1.2.7.2 Nonpaged Dynamic Pool Add at least 500,000 bytes of nonpaged dynamic pool for the software, as follows: 1. Log in to the SYSTEM account. 2. Identify the amount of additional nonpaged pool your system requires. Use the estimated value of 500,000 bytes, and then increase the value depending on the maximum amount of sockets you have. For each socket, allow a value of 2,000 bytes. ________________________Note ________________________ On a system that uses FDDI, the default sizes for the TCP/IP socket buffer quotas are increased automatically. This increases throughput across the FDDI for local TCP connections. _____________________________________________________ 1-6 Preparing to Install and Configure TCP/IP Services Preparing to Install and Configure TCP/IP Services 1.2 Preinstallation Tasks 3. Refer to the following example, and then edit MODPARAMS.DAT to reflect the appropriate value for the NPAGEDYN and NPAGEVIR parameters: ! Add nonpaged pool for HP TCP/IP Services for OpenVMS. ! ADD_NPAGEDYN=500000 ADD_NPAGEVIR=500000 For more information about nonpaged dynamic pool, see the HP OpenVMS System Manager's Manual: Essentials. 1.2.8 Assigning a User Identification Code An OpenVMS user or group of users is identified by a unique, assigned user identification code (UIC) in the format [group,member], where group and member are numeric, alphanumeric, or alphabetic characters. For example, a UIC can be either [306,210], [GROUP1, JONES], or simply JONES. The UIC is linked to a system-defined rights database that determines user and group privileges. The TCPIP$CONFIG configuration procedure uses a group UIC to create accounts for services. If a user-specified UIC is not in place from a previous configuration, the procedure creates the following UIC group numbers: __________________________________________________________ Default UIC Group Number_____Description____________________________________ 3655 The default UIC group number for service accounts. If this is an initial product configuration but the procedure detects that number 3655 is in use, TCPIP$CONFIG prompts you for a new UIC group number. 3375 The default UIC group number for the TCPIP$NOBODY user account. 3376 The default UIC group number for the ANONYMOUS ___________account._______________________________________ Before you assign a new group UIC, check that the number you chose is not already in use by entering the following commands: Preparing to Install and Configure TCP/IP Services 1-7 Preparing to Install and Configure TCP/IP Services 1.2 Preinstallation Tasks $ RUN SYS$SYSTEM:AUTHORIZE UAF> SHOW /BRIEF [your-group-number,*] UAF> SHOW /IDENTIFIER /VALUE=UIC:[your-group-number,*] To force TCPIP$CONFIG to allow you to specify a new UIC group number, assign the value TRUE to the logical name TCPIP$ASK_GROUP_UIC, as in the following example. When you 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) If you have installed one or more of the following EAKs, you must use the PCSI REMOVE command to remove the EAKs before you install TCP/IP Services Version 5.4: o Version 5.0 IPv6 EAK ________________________Note ________________________ After you remove the Version 5.0 IPv6 EAK, you must do the following: 1. Run the TCPIP$IP6_SETUP.COM command procedure. For more information, refer to the HP TCP/IP Services for OpenVMS Guide to IPv6. 2. After you install the current version of TCP/IP Services, recompile and relink your applications. _____________________________________________________ o Version 5.3 SSH for OpenVMS EAK o Version 5.3 failSAFE IP EAK 1-8 Preparing to Install and Configure TCP/IP Services Preparing to Install and Configure TCP/IP Services 1.3 Assembling Configuration Information 1.3 Assembling Configuration Information Use the worksheet in Table 1-3 to assemble configuration information. If you are configuring TCP/IP Services on the system for the first time, the TCPIP$CONFIG configuration procedure prompts you for the information listed in Table 1-3. If you are reconfiguring after a product upgrade, the procedure uses the previous configuration information as the default for the new configuration. For information to help you answer the questions on the configuration worksheet, see appropriate chapters in the HP TCP/IP Services for OpenVMS Management manual. For information to help you answer SSH configuration options, see the HP TCP/IP Services for OpenVMS Guide to SSH. Preparing to Install and Configure TCP/IP Services 1-9 Preparing to Install and Configure TCP/IP Services 1.3 Assembling Configuration Information Table_1-3_Configuration_Planning_Worksheet______________________ Your answer will When the configuration procedure asks... be... ________________________________________________________________ What is the system's host name (for example, _________________ MYNODE)? What is the system's Internet domain name _________________ (for example, widgets.com)? Do you plan to have your IP interface under _________________ control of the DHCP client? If so, the next items on this worksheet (the system's addresses and masks, and the system's network interface), might be configured automatically by the DHCP server, in which case you do not need to specify them. Ask your network manager for details. What are the system's addresses and masks?[1] * IP address (for example, 19.112.139.14) _________________ * Subnet (network mask) address (for _________________ example, 255.0.0.0) * Broadcast address (for example, _________________ 19.255.255.255) What is the system's network interface (for _________________ example, WE0)?[1] _________________ _________________ [1]If the IP interface runs under control of the DHCP client, this information might be configured automatically. Check with your network manager. For more information, see the DHCP client documentation. (continued on next page) 1-10 Preparing to Install and Configure TCP/IP Services Preparing to Install and Configure TCP/IP Services 1.3 Assembling Configuration Information Table_1-3_(Cont.)_Configuration_Planning_Worksheet______________ Your answer will When the configuration procedure asks... be... _______________________________________________________________ For failSAFE IP, what are the interfaces that _________________ will be used for the IP address's standby? _________________ _________________ What is the UIC group number for TCP/IP _________________ Services (see Section 1.2.8)? For example, 3655. Which type of routing is appropriate for the _________________ network, Static or Dynamic? Static - For simple networks where routes do not change If static, enter the default gateway's host name and address (for example, GATWY1; 19.112.0.65). Dynamic - For complex networks where flexibility is required If dynamic, you must specify either ROUTED or GATED routing. Do you plan to enable the BIND resolver? If so: * What is the name of the BIND server you _________________ want the resolver to use (for example, MAINSV)? * What is the IP address of the BIND _________________ server (for example, 19.112.139.10)? (continued on next page) Preparing to Install and Configure TCP/IP Services 1-11 Preparing to Install and Configure TCP/IP Services 1.3 Assembling Configuration Information Table_1-3_(Cont.)_Configuration_Planning_Worksheet______________ Your answer will When the configuration procedure asks... be... _______________________________________________________________ * What is the domain name (for example, _________________ mainsv.widgets.com)? Do you plan to enable SNMP? If yes: * Do you want to allow SNMP management _________________ clients to modify the MIBs by issuing set requests? * Do you want to enable authentication _________________ traps when the master agent receives an SNMP request that specifies an unauthorized community string? * What is the name of the system's contact _________________ person? Specify text as in the following example: Sam Spade. * What is the location of the system? _________________ Specify one or two fields of text as in the following three examples: - Falcon Building, Los Angeles - Boston, MA - Northwest * Do you want to allow any network manager _________________ to remotely monitor your system? If so, you need to specify a public community name. The default is public. Specify a string consisting of alphanumeric characters only. Do not enclose the string in quotes; the case is preserved as entered. Example: Rw2. * Do you want to provide additional _________________ community names and addresses (for implementing traps and allowing access beyond the default read-only provided by the "public" community)? 1-12 Preparing to Install and Configure TCP/IP Services 2 ________________________________________________________________ Installing TCP/IP Services This chapter explains how to install the HP TCP/IP Services for OpenVMS software as a layered product using the POLYCENTER Software Installation utility. The instructions are appropriate for an initial installation or an upgrade. For information about how to install the product directly from the OpenVMS Alpha CD-ROM menu, refer to the HP OpenVMS Alpha Upgrade and Installation Manual. For information about the POLYCENTER Software Installation utility, refer to the HP OpenVMS System Manager's Manual: Essentials. 2.1 Invoking the Installation Procedure When you have completed the recommended preinstallation tasks outlined in Chapter 1 and have read the release notes (Section 1.2.2), you are ready to upgrade or install TCP/IP Services. During a product upgrade, existing configuration files are preserved in case you want to use them when you configure this version of the software. To install the TCP/IP Services software on an OpenVMS Alpha system, proceed as follows: 1. Log in to the SYSTEM account. 2. Check to make sure that other users are not logged in to the system. 3. Edit the SYS$STARTUP:SYSTARTUP_VMS.COM file and check to see if the command @SYS$STARTUP:UCX$STARTUP is defined. If this command is defined, edit the line, re- placing the command definition with @SYS$STARTUP:TCPIP$STARTUP Installing TCP/IP Services 2-1 Installing TCP/IP Services 2.1 Invoking the Installation Procedure so that the current version of the product starts automatically when the system starts up. 4. If a previous version of the TCP/IP Services software is installed on the system, shut it down by using the appropriate command: _______________________________________________________ If the software version_is..._________Use_this_command...______________ Version 4.x @SYS$MANAGER:UCX$SHUTDOWN.COM Version_5.x___________@SYS$STARTUP:TCPIP$SHUTDOWN.COM__ 5. HP recommends that you log the installation procedure. If you have DECnet configured on your system, you can create a log of the installation procedure by entering the following command and then log in to the system account again: $ SET HOST 0/LOG=file-specification In this command, file-specification is the name of the file to which you want the log written. The log file is written to the current directory. 6. Start the POLYCENTER Software Installation utility by entering the PRODUCT INSTALL command with the directory path appropriate for your system. For example: $ PRODUCT INSTALL TCPIP /SOURCE=directory-path In this command, directory-path specifies the disk and directory name for the source drive that holds the TCP/IP Services kit. For example, /SOURCE=DKA400:[TCPIPAXP054]. If you do not specify the source qualifier, the POLYCENTER Software Installation utility searches the location defined by the logical name PCSI$SOURCE. If not defined, the utility searches the current default directory. 2-2 Installing TCP/IP Services Installing TCP/IP Services 2.2 Stepping Through the Installation Procedure 2.2 Stepping Through the Installation Procedure After you invoke the installation procedure, you are prompted for information. Example 2-1 shows a sample installation on an OpenVMS Alpha system that has an earlier version of TCP/IP Services installed on it. Additional explanatory information follows each portion of the installation procedure. For a sample installation on a system on which the product has never been installed, see Appendix A. The actual installation output that is displayed on your system might vary, depending on your current configuration. ________________________Note ________________________ To stop the installation at any time, press Ctrl/Y. The installation procedure deletes any files that were created, then exits. The symbols xx in the following example and elsewhere in this document represent the product's two-digit update version number. _____________________________________________________ Example 2-1 TCP/IP Services Installation: Sample POLYCENTER Software Installation Utility Procedure 1 - DEC AXPVMS TCPIP V5.4-xx Layered Product 2 - DEC AXPVMS TCPIP V5.1-15 Layered Product 3 - DEC AXPVMS TCPIP V5.0-11 Layered Product 4 - All products listed above 5 - Exit Choose one or more items from the menu separated by commas: 1 The initial menu that is displayed includes the latest TCP/IP Services product and any versions of the product that are in place on the system. Install the latest version (option 1). Installing TCP/IP Services 2-3 Installing TCP/IP Services 2.2 Stepping Through the Installation Procedure The following product has been selected: DEC AXPVMS TCPIP V5.4-xx Layered Product Do you want to continue? [YES] Press Return to continue with the installation procedure. Configuration phase starting ... You will be asked to choose options, if any, for each selected product and for any products that may be installed to satisfy software dependency requirements. DEC AXPVMS TCPIP V5.4-xx: HP TCP/IP Services for OpenVMS. Copyright 1976, 2003 Hewlett-Packard Development Company, L.P. Hewlett-Packard Development Company, L.P. HP TCP/IP Services for OpenVMS offers several license options. Do you want the defaults for all options? [YES] Answer Yes to choose the POLYCENTER Software Installation utility defaults for the options or No to choose other options. Do you want to review the options? [NO] Answer Yes to review the POLYCENTER Software Installation utility options. In this example, the options are not reviewed. If you select Yes, the options are displayed and you are asked whether you are satisfied with the options. Press Return to accept the options as listed, or answer No to change the options. Execution phase starting ... The following product will be installed to destination: DEC AXPVMS TCPIP V5.4-xx DISK$ALPHASYS:[VMS$COMMON.] The following product will be removed from destination: DEC AXPVMS TCPIP V5.1-15 DISK$ALPHASYS:[VMS$COMMON.] Portion done: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90% 2-4 Installing TCP/IP Services Installing TCP/IP Services 2.2 Stepping Through the Installation Procedure The following message appears only if an earlier version of TCP/IP Services was configured on your system. A 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. % To use the version of HP TCP/IP Services that was just installed, % system must be rebooted. % Portion done: 100% The following product has been installed: DEC AXPVMS TCPIP V5.4-xx Layered Product The following product has been removed: DEC AXPVMS TCPIP V5.1-15 Layered Product DEC AXPVMS TCPIP V5.4-xx: HP TCP/IP Services for OpenVMS. Check the release notes for current status of the product. 2.3 Postinstallation Tasks After the installation completes, perform the following steps: 1. Optionally, you can: - Read the HP TCP/IP Services for OpenVMS Release Notes on line or print the file from SYS$HELP:TCPIP054_ RELEASE_NOTES.PS or SYS$HELP:TCPIP054.RELEASE_NOTES. - Display a list of the TCP/IP Services files that were installed. Enter the following command: $ PRODUCT LIST TCPIP /SOURCE=directory-path In this command, directory-path specifies the disk and directory name for the source drive that holds the TCP/IP Services kit (for example, /SOURCE=DKA400:[TCPIPAXP054]). If you do not specify the source qualifier, the POLYCENTER Software Installation utility searches the location defined Installing TCP/IP Services 2-5 Installing TCP/IP Services 2.3 Postinstallation Tasks by the logical name PCSI$SOURCE. If not defined, the utility searches the current default directory. 2. If you had a previous version of TCP/IP Services configured on your system and the software was previously started, reboot your system for the new TCP/IP Services software to take effect. Then proceed to step 4. _____________________ Important _____________________ Do not delete any files that remain from the previous version of the product. Many of these files are used by TCPIP$CONFIG for converting your existing configuration to the new configuration (described in Chapter 3). _____________________________________________________ 3. If you removed the Version 5.0 IPv6 EAK prior to this installation, recompile and relink your applications. 4. Proceed to Chapter 3 to configure TCP/IP Services. ________________________Note ________________________ With previous versions of TCP/IP Services, you were required to log out of the SYSTEM account and then log back in to the SYSTEM account to establish the TCPIP command environment. Starting with Version 5.4 of TCP/IP Services, this is no longer required. _____________________________________________________ 2-6 Installing TCP/IP Services 3 ________________________________________________________________ Configuring TCP/IP Services After you install HP TCP/IP Services for OpenVMS, you need to enable the components and characteristics you require for your particular system using the menu-driven TCPIP$CONFIG configuration procedure. This chapter explains the TCPIP$CONFIG menus, provides sample installation output, and summarizes additional configuration and setup tasks. 3.1 Recommended Order for Configuring TCP/IP Services Table 3-1 lists the tasks involved in configuring TCP/IP Services, and the sections that describe these tasks. Configuring TCP/IP Services 3-1 Configuring TCP/IP Services 3.1 Recommended Order for Configuring TCP/IP Services Table_3-1_Configuring_TCP/IP_Services_____________________ Described Step Task to perform... in... __________________________________________________________ 1 Assemble system information to prepare Section 1.3 for running TCPIP$CONFIG. 2 Run TCPIP$CONFIG. (Alternatively, Section 3.3 have TCP/IP Services configured automatically, as explained in step 3.) If you have a TCP/IP Services V4.x configuration on your system, answer prompts to convert existing databases or to create new ones. 3 If you prefer, have TCP/IP Services Section 3.2 software configured automatically by a DHCP server. 4 Manually configure the TCP/IP Services Sections core environment, clients, and servers 3.3.4 through using TCPIP$CONFIG. 3.3.6 5 Configure the optional components using Section 3.3.7 TCPIP$CONFIG, as applicable. 6 Start TCP/IP Services. Section 3.5 7 Verify the configuration. Section 3.8 8 Complete additional configuration Section 3.9 ____tasks,_as_appropriate.________________________________ ________________________Note ________________________ Configuration changes made to the TCP/IP Services software do not take effect until you start or restart the software. See Section 3.5. _____________________________________________________ 3-2 Configuring TCP/IP Services Configuring TCP/IP Services 3.2 Automatic Configuration of TCP/IP Services Using DHCP Client 3.2 Automatic Configuration of TCP/IP Services Using DHCP Client TCP/IP Services Version 5.4 supports the DHCP client, which allows you to have your system configured automati- cally by a DHCP server. You can achieve this in one of two ways: o If TCP/IP Services has never been configured on your system, you can run the TCP/IP Services startup procedure, SYS$STARTUP:TCPIP$STARTUP.COM. The startup procedure detects the fact that the TCP/IP Services software has not been configured and asks whether you want the DHCP client to configure the host for you. Answer Yes. The startup procedure invokes TCPIP$CONFIG, which sets up the environment for the DHCP client and designates any unconfigured interfaces to be under DHCP client control. The procedure enables the following set of services automatically: - FTP client - TELNET client - TELNET server - SMTP For more information about DHCP, see the HP TCP/IP Services for OpenVMS Management manual. o Run TCPIP$CONFIG. Choose option 2 from the Core Environment Configuration menu to configure the Internet interface, and then choose option 2 from the Interface Configuration menu: Configuration options: 1 - Configure interface manually (Current default) 2 - Let DHCP configure interface You can also use TCPIP$CONFIG to configure additional services and parameters, as needed. Configuring TCP/IP Services 3-3 Configuring TCP/IP Services 3.3 Running TCPIP$CONFIG 3.3 Running TCPIP$CONFIG The TCPIP$CONFIG configuration procedure displays menus from which you do the following: o Make selections that enable services for your system. To select the default, press the Return key. o Start or stop TCP/IP Services software. o Verify the configuration. To get started, enter: $ @SYS$MANAGER:TCPIP$CONFIG 3.3.1 Converting Existing TCP/IP Services Configuration Files (Upgrade Only) If you have a TCP/IP Services for OpenVMS (UCX) configura- tion in place (Version 4.x), and you have never configured a Version 5.x product on the system, the procedure begins by asking you whether to convert the Version 4.x (UCX) TCP/IP Services configuration files: Convert the old configuration files [Y] Unless you respond No to the prompt, the procedure converts existing configuration files to new configuration files. If you have already configured this product, the procedure indicates that no new configuration files are being created: Checking TCP/IP Services for OpenVMS configuration database files. No new database files were created. The following sample output shows the start of the TCPIP$CONFIG procedure and a portion of the conversion of a previous configuration: TCP/IP Network Configuration Procedure This procedure helps you define the parameters required to run HP TCP/IP Services for OpenVMS on this system. 3-4 Configuring TCP/IP Services Configuring TCP/IP Services 3.3 Running TCPIP$CONFIG NOTE: TCP/IP has been previously configured from an earlier version of this product. You can avoid a complete reconfiguration of TCP/IP by allowing this procedure to automatically convert the old configuration files. If you choose not to do this now, you will not be asked again. At the end of the conversion you will be able to further modify your configuration. Convert the old configuration files [Y]: Preparing files for conversion... UCX$SERVICE.DAT --> TCPIP$SERVICE.DAT UCX$HOST.DAT --> TCPIP$HOST.DAT UCX$NETWORK.DAT --> TCPIP$NETWORK.DAT UCX$ROUTE.DAT --> TCPIP$ROUTE.DAT UCX$PROXY.DAT --> TCPIP$PROXY.DAT UCX$CONFIGURATION.DAT --> TCPIP$CONFIGURATION.DAT UCX$EXPORT.DAT --> TCPIP$EXPORT.DAT UCX$PRINTCAP.DAT --> TCPIP$PRINTCAP.DAT No new database files were created. FTP SERVER Configuration LPD SERVER Configuration Service is not defined in the SYSUAF. Nonprivileged user access is not enabled. By default, HP TCP/IP Services for OpenVMS configures LPD such that nonprivileged users cannot modify queue entries. Creating TCPIP$AUX identifier with a value of 3655 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 host - Spooling directory for the local queue To add or delete printers in the TCPIP PRINTCAP database, use the $RUN SYS$SYSTEM:TCPIP$LPRSETUP command. . . . Configuring TCP/IP Services 3-5 Configuring TCP/IP Services 3.3 Running TCPIP$CONFIG 3.3.2 Creating New TCP/IP Services Configuration Files If you do not have an existing TCP/IP Services configura- tion in place from a previous version of the product, the procedure begins by creating configuration database files, as shown in the following sample output: TCP/IP Network Configuration Procedure This procedure helps you define the parameters required to run HP TCP/IP Services for OpenVMS on this system. Checking TCP/IP Services for OpenVMS configuration database files. Creating SYS$COMMON:[SYSEXE]TCPIP$SERVICE.DAT Creating SYS$COMMON:[SYSEXE]TCPIP$HOST.DAT Creating SYS$COMMON:[SYSEXE]TCPIP$NETWORK.DAT Creating SYS$COMMON:[SYSEXE]TCPIP$ROUTE.DAT Creating SYS$COMMON:[SYSEXE]TCPIP$PROXY.DAT Creating SYS$COMMON:[SYSEXE]TCPIP$CONFIGURATION.DAT HP TCP/IP Services for OpenVMS requires a definition for at least one interface. There are no interfaces defined on this system. Please select the Interface option from the Core Environment Menu. 3.3.3 Understanding the Configuration Menus After the configuration files are converted or created, 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 5 - Shutdown HP TCP/IP Services for OpenVMS 6 - Startup HP TCP/IP Services for OpenVMS 7 - Run tests A - Configure options 1 - 4 [E] - Exit configuration procedure Enter configuration option: 3-6 Configuring TCP/IP Services Configuring TCP/IP Services 3.3 Running TCPIP$CONFIG The options are as follows: ________________________________________________________________ Option_______________Description________________________________ 1 Core environ- Configure software associated with the ment Network, Internet, and Transport layers of the TCP/IP architecture (Section 3.3.4). 2 Client Configure application software and related components services (Section 3.3.5). 3 Server Configure server software and related components services (Section 3.3.6). 4 Optional Configure software necessary if you plan to components allow Anonymous FTP access, enable Kerberos authentication for the TELNET server, enable failSAFE IP support, or run such products as PATHWORKS for OpenVMS (Advanced Server), Advanced Server for OpenVMS, DECnet over TCP/IP, or any applications that use the Stanford Research Institute (SRI) QIO application programming interface (Section 3.3.7) 5 Shutdown TCP/IP Stop TCP/IP Services (Section 3.6). Services for OpenVMS 6 Startup TCP/IP Start TCP/IP Services (Section 3.7). Services for OpenVMS 7 Run tests Run the installation verification procedure (Section 3.8). A Configure Configure all the TCP/IP Services options 1 - components (the core, client, server, and 4 optional services). The procedure takes you through each of the configuration options. E Exit the Return to the system prompt. configuration ____procedure___________________________________________________ ________________________Note ________________________ If you do not have experience with the TCP/IP Services product, you should use the configuration Configuring TCP/IP Services 3-7 Configuring TCP/IP Services 3.3 Running TCPIP$CONFIG menus provided by the TCPIP$CONFIG configuration 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 run TCPIP$CONFIG. For information about the command parameters, see Section 3.4. _____________________________________________________ 3.3.4 Configuring the Core Environment To display the Core Environment Configuration menu, choose option 1 (Core environment) from the Main Configuration menu. If you chose option A from the Main Configuration menu to configure all the TCP/IP Services components, the Core Environment Configuration menu is displayed first. The sample output in the following sections show the progression of the procedure when you choose option A. You are required to configure the Domain, Interfaces, and Routing services; BIND Resolver and Time Zone are optional. ________________________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 might not need to set up the other Core Environment components. Ask your network manager whether these components are configured by DHCP. For more information, see the DHCP client documentation. _____________________________________________________ 3-8 Configuring TCP/IP Services Configuring TCP/IP Services 3.3 Running TCPIP$CONFIG 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 ________________________Note ________________________ If you have run the TCPIP$IP6_SETUP.COM procedure to enable IPv6, and then you run the TCPIP$CONFIG.COM command procedure, TCPIP$CONFIG.COM displays the following warning message prior to displaying the Core Environment configuration options. For more information, refer to the HP TCP/IP Services for OpenVMS Guide to IPv6. - WARNING - This node has been configured for IPv6. If you make any additional changes to the configuration of the interfaces, you must run TCPIP$IP6_SETUP again and update your host name information in BIND/DNS for the changes to take effect. _____________________________________________________ The following sections include sample output for the core environment components. The samples reflect a TCP/IP Services product configuration for a system on which other TCP/IP Services configurations are in place. The output varies for a new TCP/IP Services installation (see Appendix A). Enter your responses to the menu questions using the information from your configuration planning worksheet (Section 1.3). Configuring TCP/IP Services 3-9 Configuring TCP/IP Services 3.3 Running TCPIP$CONFIG 3.3.4.1 Domain Configuration The following is sample output for configuring the domain: DOMAIN Configuration Enter Internet domain [budget.acme.com]: 3.3.4.2 Interface Configuration The following is sample output for configuring the Internet interface: INTERFACE Configuration The Ethernet device(s) on your system are: EWA0: Start of configuration questions for Internet interface WE0. WE0 is the Ethernet device EWA0: Interface: WE0 IP_Addr: 10.10.1.1 NETWRK: 255.0.0.0 BRDCST: 10.10.2.255 C_Addr: C_NETWRK: C_BRDCST: Flags: Receive buffer: 0 HP TCP/IP Services for OpenVMS Interface WE0 Reconfiguration Menu Reconfiguration options: 1 - Configure interface manually (Current default) 2 - Let DHCP configure interface [E] - Exit menu (Do not reconfigure interface WE0) Enter configuration option: In this example, no changes are made to the interface. If you want to configure a standby interface IP address for failSAFE IP failover support, see Section 3.3.4.3; otherwise, skip to Section 3.3.4.4. 3-10 Configuring TCP/IP Services Configuring TCP/IP Services 3.3 Running TCPIP$CONFIG 3.3.4.3 failSAFE IP Target Address Configuration You can configure a standby failover target IP address that failSAFE IP assigns to multiple interfaces on a node or across a cluster. When, for example, a Network Interface Controller fails or a cable breaks or disconnects, failSAFE IP activates the standby IP address so that an alternate interface can take over to maintain the network connection. If an address is not preconfigured with a standby, then failSAFE IP removes the address from the failed interface until it recovers. When the failed interface recovers, failSAFE IP detects this and can return its IP address. Configure the standby failover IP address as follows: 1. From the Core Environment Configuration menu, select option 2 (Interfaces). The Interface Configuration menu appears. 2. From the Interface Configuration menu, select option 1 (Configure interface manually). Configure your interface by responding to the prompts that ask for interface-specific information, including the host name, the Internet address, the network mask, and the broadcast mask. In the following example, IP address 10.10.1.1 is configured for interface WE0. Configuring TCP/IP Services 3-11 Configuring TCP/IP Services 3.3 Running TCPIP$CONFIG HP TCP/IP Services for OpenVMS Interface WE0 Configuration Menu Configuration options: 1 - Configure interface manually 2 - Let DHCP configure interface [E] - Exit menu (Do not configure interface WE0) Enter configuration option: 1 Enter fully qualified host name [delite.budget.acme.com]: Enter Internet address for delite [10.10.1.1]: Enter Internet network mask for delite [255.0.0.0]: Enter broadcast mask for delite [10.10.2.255]: The following parameters will be used to define the Internet interface WE0: Host name: delite Internet address: 10.10.1.1 Network mask: 255.0.0.0 Broadcast mask: 10.10.2.255 * Is the above correct [YES]: As shown in the preceding example, the configuration procedure displays the interface information you entered and lets you verify that it is correct. Answer Yes to the prompt that asks if the information is correct. 3. Next, the configuration procedure displays information about failSAFE IP, as in the following example, and prompts you whether you want to configure a target for failSAFE IP. Answer Yes. 3-12 Configuring TCP/IP Services Configuring TCP/IP Services 3.3 Running TCPIP$CONFIG failSAFE IP failSAFE IP uses multiple Network Interface Controllers (NICs) to provide high availability of IP addresses. In the event of a NIC failure, (e.g. any event preventing the NIC from receiving data), all IP addresses associated with the failed NIC are reassigned to a preconfigured failover target. In a cluster configuration, the IP address may be preconfigured on NICs across other cluster members. This provides cluster-wide failover for the IP address. See the management guide for more configuration options. You will be asked what other NICs on this node will act as failover targets. * Configure failover target for failSAFE IP [NO]: YES 4. The configuration procedure then lists other interfaces available for failover and allows you to specify them as an interface for failSAFE IP. In the following example, interfaces IEO and IE1 are configured with the standby address for failSAFE IP failover: Interfaces available for failover are: IE0 IE1 Enter an interface for failSAFE IP: IE0 Interfaces available for failover are: IE1 Enter an interface for failSAFE IP: IE1 Interfaces available for failover are: Enter an interface for failSAFE IP: * Continue configuring interfaces for failSAFE IP [NO]: Configuring TCP/IP Services 3-13 Configuring TCP/IP Services 3.3 Running TCPIP$CONFIG 5. After configuring the standby IP address, you must configure and enable the failSAFE IP service, as explained in Section 3.3.7.2. ________________________Note ________________________ You can also manually configure the failSAFE IP 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, see the HP TCP/IP Services for OpenVMS Management manual. _____________________________________________________ 3.3.4.4 Dynamic Routing Configuration The following is sample output for configuring dynamic routing: 3-14 Configuring TCP/IP Services Configuring TCP/IP Services 3.3 Running TCPIP$CONFIG DYNAMIC ROUTING Configuration Dynamic routing has not been configured. You may configure dynamic ROUTED or GATED routing. You cannot enable both at the same time. If you want to change from one to the other, you must disable the current routing first, then enable the desired routing. If you enable dynamic ROUTED routing, this host will use the Routing Information Protocol (RIP) - Version 1 to listen for all dynamic routing information coming from other hosts to update its internal routing tables. It will also supply its own Internet addresses to routing requests made from remote hosts. If you enable dynamic GATED routing, you will be able to configure this host to use any combination of the following routing protocols to exchange dynamic routing information with other hosts on the network: Routing Information Protocol (RIP) - Version 1 & 2 Router Discovery Protocol (RDISC) Open Shortest Path First (OSPF) Exterior Gateway Protocol (EGP) Border Gateway Protocol (BGP-4) Static routes * Do you want to configure dynamic ROUTED or GATED routing [NO]: YES * Do you want to enable GATED routing configuration [NO]: ROUTED option If you enable the 'supply' option of dynamic routing, this host will supply dynamic routing information to other hosts on the network whether it is acting as an internetwork gateway or not. * Do you want this host to supply its dynamic routing information [NO]: Configuring TCP/IP Services 3-15 Configuring TCP/IP Services 3.3 Running TCPIP$CONFIG 3.3.4.5 BIND Resolver Configuration The following is sample output for configuring the BIND resolver: 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 * Do you want to reconfigure BIND [NO]: In this example, no changes are made to the BIND resolver. 3.3.4.6 Time Zone Configuration The following is sample output for configuring the time zone: TCPIP uses timezone information provided by the OpenVMS Operating System. No additional timezone configuration is needed for TCPIP when the operating system is configured correctly. This section verifies the current OpenVMS timezone configuration. A warning message (TCPIP-W-) indicates that corrective action should be taken. TCPIP will appear to operate but components may display either the wrong time or a time inconsistent with other applications. %TCPIP-I-INFO, Logical name SYS$TIMEZONE_RULE found. -TCPIP-I-INFO, Software for automatic Summer/Winter time (TDF) change -TCPIP-I-INFO, is present. -TCPIP-I-INFO, Further action to ensure TDF change is not necessary. %TCPIP-I-NORMAL, timezone information verified Press Return to continue ... After you configure the core environment, press Return or choose option E to exit from the Core Environment menu. If you chose option A from the Main Configuration menu to configure all the TCP/IP Services components, the Client Components Configuration menu displays next; otherwise, the procedure returns to the the Main Configuration menu. 3-16 Configuring TCP/IP Services Configuring TCP/IP Services 3.3 Running TCPIP$CONFIG 3.3.5 Configuring the Client Environment To display the Client Components Configuration menu, choose option 2 (Client components) from the Main Configuration menu. If you chose option A from the Main Configuration menu to configure all the TCP/IP Services components, the Client Components Configuration menu displays automatically after you finish configuring the core environment services. From the Client Components Configuration menu, choose op- tion A to configure all the client services. Alternatively, you can configure one client service at a time. The sample output in the following sections show the progression of the procedure when you choose option A. ________________________Note ________________________ Starting with Version 5.4 of TCP/IP Services, you can configure and use Secure Shell (SSH) to 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. _____________________________________________________ HP TCP/IP Services for OpenVMS Client Components Configuration Menu Configuration options: 1 - DHCP Client Disabled Stopped 2 - FTP Client Enabled Stopped 3 - NFS Client Enabled Started 4 - REXEC and RSH Enabled Started 5 - RLOGIN Enabled Started 6 - SMTP Enabled Started 7 - SSH Client Enabled Stopped 8 - TELNET Enabled Started 9 - TELNETSYM Disabled Stopped A - Configure options 1 - 9 [E] - Exit menu Configuring TCP/IP Services 3-17 Configuring TCP/IP Services 3.3 Running TCPIP$CONFIG Note that the sample Client Components Configuration menu shows most clients enabled and all of them stopped. Clients are enabled for startup if they have been enabled in the TCP/IP Services configuration database (TCPIP$CONFIGURATION.DAT). The enabled services are started the next time TCP/IP Services is started. You can also start (or stop) a specific service, without having to restart TCP/IP Services, by choosing the "Start service" option from that service's configuration menu. In addition, you can use command procedures to start or stop a specific service, as explained in Section 3.10.3. The initial status of the services depends on whether you have other TCP/IP Services installations in place on the system, and whether the software or individual services have been started. On a new system, all the services would be disabled (the default). The status of services is also affected by the selections you made from the Core Environment menu. To minimize resource consumption, enable and start only those services that you are sure to use. Disable those you do not plan to use. To configure all the client services, choose option A. The following is an example of the output for configuring an FTP client. The configuration output for other clients might vary. Note that after you configure a client (such as FTP) that has an associated server, the configuration prompts you about whether to configure the corresponding server. 3-18 Configuring TCP/IP Services Configuring TCP/IP Services 3.3 Running TCPIP$CONFIG Enter configuration option: 2 FTP CLIENT Configuration Service is enabled on specific node. Service is stopped. FTP CLIENT configuration options: 1 - Disable service on this node 2 - Start service on this node [E] - Exit FTP_CLIENT configuration Enter configuration option: 1 The FTP SERVER is enabled. * Do you want to configure the FTP SERVER [NO] ? In the preceding example, the FTP client was originally enabled, and option 1 disables it. The configuration procedure indicates that the FTP server is enabled and asks whether you want to configure it as well. The following example shows the configuration output that 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. FTP CLIENT configuration options: 1 - Enable service on this node 2 - Enable & Start service on this node [E] - Exit FTP_CLIENT configuration Enter configuration option: 2 In this example, as with the previous one, the TCP/IP Services software has already been started, so you have the choice of starting the client as well as enabling it. If you choose option 1, the FTP service is enabled and FTP starts the next time TCP/IP Services is started. If you choose option 2, the FTP service is started immediately and then every time the TCP/IP Services is started. Configuring TCP/IP Services 3-19 Configuring TCP/IP Services 3.3 Running TCPIP$CONFIG If the TCP/IP Services software is not already started, then the FTP Client Components Configuration menu gives you only the option of enabling the service, as in the following example: 1 - Enable service on this node [E] - Exit FTP_CLIENT configuration After you configure the client service environment, press Return or choose option E to exit from the Client Components menu. If you chose option A from the Main Configuration menu to configure all the TCP/IP Services components, the Server Components Configuration menu displays next; otherwise, the procedure returns to the the Main Configuration menu. 3.3.6 Configuring the Server Environment To display the Server Components Configuration menu, choose option 3 (Server components) from the Main Configuration menu. If you chose option A from the Main Configuration menu to configure all the TCP/IP Services components, the Server Components Configuration menu displays automatically after you finish configuring the client services. ________________________Note ________________________ Starting with Version 5.4 of the TCP/IP Services, you can configure and use Secure Shell (SSH) to 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. _____________________________________________________ 3-20 Configuring TCP/IP Services Configuring TCP/IP Services 3.3 Running TCPIP$CONFIG HP TCP/IP Services for OpenVMS Server Components Configuration Menu 1 - BIND Enabled Started 12 - NTP Enabled Started 2 - BOOTP Disabled Stopped 13 - PC-NFS Enabled Started 3 - DHCP Disabled Stopped 14 - POP Enabled Started 4 - FINGER Enabled Started 15 - PORTMAPPER Enabled Started 5 - FTP Enabled Started 16 - RLOGIN Enabled Started 6 - IMAP Disabled Stopped 17 - RMT Disabled Stopped 7 - LBROKER Disabled Stopped 18 - SNMP Enabled Stopped 8 - LPR/LPD Disabled Stopped 19 - SSH Enabled Started 9 - METRIC Enabled Started 20 - TELNET Enabled Started 10 - NFS Enabled Started 21 - TFTP Enabled Started 11 - LOCKD/STATD Disabled Stopped 22 - XDM Enabled Started A - Configure options 1 - 22 [E] - Exit menu Enter configuration option: Servers are enabled for startup if they have been added to the TCP/IP Services configuration database (TCPIP$CONFIGURATION.DAT), and they are started the next time TCP/IP Services is started. You can also start (or stop) a specific server, without having to restart TCP/IP Services, by choosing the "Start service" option from that server's configuration menu. In addition, you can use command procedures to start or stop a specific server, as explained in Section 3.10.3. The initial status of the servers depends on whether you have other TCP/IP Services installations in place on the system, and whether the software or individual servers have been started. To minimize resource consumption, enable and start the specific servers you plan to use, and disable those you do not plan to use. You can choose option A to configure all the servers. For servers that have associated client services (such as the FTP server and client), when you configure the server you are prompted about whether to configure the corresponding client. ________________________Note ________________________ TELNET and RLOGIN are enabled from the client menu. If you want to disable the TELNET or RLOGIN server, Configuring TCP/IP Services 3-21 Configuring TCP/IP Services 3.3 Running TCPIP$CONFIG then you must disable the service. To enable or disable the TELNET server or the RLOGIN server, use the Client Components Configuration menu, choose the appropriate client, and disable and stop the service by choosing the "Disable & Stop service on this node" option. _____________________________________________________ The following is an example of an XDM server configuration output. The configuration displays for other servers might vary. Enter configuration option: 21 XDM Configuration Service is defined in the SYSUAF. Service is not defined in the TCPIP$SERVICE database. Service is not enabled. Service is stopped. XDM configuration options: 1 - Enable service on this node [E] - Exit XDM configuration Enter configuration option: ________________________Note ________________________ XDM requires the following DECwindows components to be installed: o SYS$COMMON:[SYSLIB]DECW$XLIBSHR.EXE o SYS$COMMON:[SYSLIB]DECW$XTLIBSHRR5.EXE The TCPIP$CONFIG configuration procedure checks whether these components are installed. If they are not found, TCPIP$CONFIG notifies you and gives you the option of configuring XDM and installing the DECwindows components later before you attempt to activate XDM. The notification and prompt are as follows: 3-22 Configuring TCP/IP Services Configuring TCP/IP Services 3.3 Running TCPIP$CONFIG XDM requires DECwindows components that are not installed. Attempts to activate XDM will fail. Type C to continue with XDM configuration, or E to exit [ E ]: _____________________________________________________ After you configure the servers, press Return or choose option E to exit from the Server Components Configuration menu. If you chose option A from the Main Configuration menu to configure all the TCP/IP Services components, the Optional Components Configuration menu displays next; otherwise, the procedure returns to the Main Configuration menu. 3.3.7 Configuring the Optional Components You may need to configure optional product components if you plan to do one or more of the following: o Run the PATHWORKS for OpenVMS (Advanced Server), the Advanced Server for OpenVMS, or DECnet over TCP/IP software. o Run or develop applications that use the Stanford Research Institute's (SRI) QIO application programming interface (API). o Allow Anonymous FTP access. o Initialize Kerberos authentication for the TELNET server. o Where a node or cluster has multiple interfaces, enable failSAFE IP to monitor the health of network interface cards and, when an interface fails, to perform a failover to another interface to maintain network connectivity. To display the Optional Components Configuration menu, choose option 4 (Optional components) from the Main Configuration menu. If you chose option A from the Main Configuration menu to configure all the TCP/IP Services components, the Optional Components Configuration menu displays automatically after you finish configuring the servers. Configuring TCP/IP Services 3-23 Configuring TCP/IP Services 3.3 Running TCPIP$CONFIG The Optional Components Configuration menu displays the following menu options: HP TCP/IP Services for OpenVMS Optional Components Configuration Menu Configuration options: 1 - Configure PWIP Driver (for DECnet-Plus and PATHWORKS) 2 - Configure SRI QIO Interface (INET Driver) 3 - Set up Anonymous FTP Account and Directories 4 - Configure Kerberos Applications 5 - Configure failSAFE IP A - Configure options 1 - 5 [E] - Exit menu Enter configuration option: Choose the options that are appropriate for your system: the PWIP Driver, the SRI QIO Interface, Anonymous FTP Accounts and Directories, Kerberos authentication for TELNET, and failSAFE IP (provides IP address failover capability for multiple interfaces on a host or cluster). o If you want to run PATHWORKS for OpenVMS (Advanced Server), Advanced Server for OpenVMS, or DECnet over TCP/IP, configure the PWIP driver by choosing option 1. In addition, refer to the appropriate documentation for the layered product. o If you run or develop applications that use the SRI QIO API, choose option 2. 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 necessary user information code (UIC) (see Section 1.2.8) and determine guest user privileges. o If you want to provide the security benefits of Kerberos authentication for the TELNET server, choose option 4 to configure Kerberos. For details about configuring Kerberos support, see Section 3.3.7.1. 3-24 Configuring TCP/IP Services Configuring TCP/IP Services 3.3 Running TCPIP$CONFIG o If you want to provide IP address failover capability for multiple interfaces on a host or cluster, choose option 5 to configure failSAFE IP. For details about configuring failSAFE IP support, see Section 3.3.7.2. More information is available also in the HP TCP/IP Services for OpenVMS Management manual. The following example shows the output for configuring the PWIP driver: Enter configuration option: 1 TCPIP Transport for DECnet and Pathworks Service Configuration Service is enabled on specific node. Service is stopped. TCPIP Transport for DECnet and Pathworks Service configuration options: 1 - Disable service on this node [E] - Exit PWIP_DRIVER configuration Enter configuration option: 3.3.7.1 Configuring and Enabling Kerberos Support To configure the TELNET service to support Kerberos, follow these steps. For more details about Kerberos features, including prerequisites and instructions for using Kerberos, see the HP TCP/IP Services for OpenVMS Management manual. ________________________Note ________________________ Before you begin the following steps, make sure the TELNET service is stopped. _____________________________________________________ 1. From the the TCPIP$CONFIG.COM procedure Main Configuration menu, choose option 2 (Client components). 2. From the list of client services, choose option 6 (TELNET). 3. From the TELNET Configuration menu, choose option 1 (Enable service on all nodes). This step creates the TCPIP$TELNET user account and directory. 4. Return to the Main Configuration menu. Configuring TCP/IP Services 3-25 Configuring TCP/IP Services 3.3 Running TCPIP$CONFIG 5. From the Main Configuration menu, choose option 4 (Optional components). 6. From the Optional Components Configuration menu, choose option 4 (Configure Kerberos Applications). The following menu is displayed: Kerberos Applications Configuration Menu TELNET Kerberos is not defined in the TCPIP$SERVICE database. Configuration options: 1 - Add Kerberos for TELNET server 2 - Remove Kerberos for TELNET server [E] - Exit menu Enter configuration option: 7. From the Kerberos Applications Configuration menu, choose option 1 (Add Kerberos for TELNET Server). 8. Exit the command procedure. 9. When you are prompted to start the TELNET service, enter N. 10. Start the TELNET service by executing the TELNET startup procedure, as shown in the following example: $ @SYS$STARTUP:TCPIP$TELNET_STARTUP.COM %TCPIP-I-INFO, image SYS$SYSTEM:TCPIP$TELNET_SERVER.EXE installed %TCPIP-I-INFO, image SYS$SYSTEM:TCPIP$TELNET.EXE installed %TCPIP-I-INFO, logical names created %TCPIP-I-INFO, telnet service enabled %TCPIP-I-INFO, telnet (kerberos) service enabled %TCPIP-S-STARTDONE, TCPIP$TELNET startup completed The information message confirms that the TELNET Kerberos service has been enabled. 3-26 Configuring TCP/IP Services Configuring TCP/IP Services 3.3 Running TCPIP$CONFIG 3.3.7.2 Configuring and Enabling failSAFE IP Support Two steps are necessary to configure failSAFE IP: 1. Configure the standby IP address on the interfaces for which failover is desired, as explained in Section 3.3.4.3; these are the failover target interfaces for each home interface. 2. Configure failSAFE IP support by choosing option 5 (Configure failSAFE IP) from the Optional Components Configuration menu. Choosing option 5 from the Optional Components Configuration menu displays the following menu. Note that in this menu, Option 1 (Enable service on all nodes) appears only in a cluster configuration. Choose Option 1 to enable failSAFE IP on all nodes in the cluster, or choose option 2 to enable failSAFE IP on the local node only. failSAFE configuration options: 1 - Enable service on all nodes 2 - Enable service on this node 3 - Enable & Start service on this node [E] - Exit FAILSAFE configuration Enter configuration option: For more details about failSAFE IP, see the HP TCP/IP Services for OpenVMS Management manual. 3.4 Using TCPIP$CONFIG Option Commands to Bypass TCPIP$CONFIG Menus If you are an experienced TCP/IP Services user, you may want to bypass the configuration menus to enable or disable functionality, as follows: 1. Log in to the SYSTEM account. 2. Run the TCPIP$CONFIG command procedure and include appropriate options and keywords in the command line, as shown: @SYS$MANAGER:TCPIP$CONFIG [option] {DISABLE | ENABLE} [CLUSTER] Configuring TCP/IP Services 3-27 Configuring TCP/IP Services 3.4 Using TCPIP$CONFIG Option Commands to Bypass TCPIP$CONFIG Menus In this format, option can be one of the options described in the following table. The table also describes the function of the DISABLE, ENABLE, and CLUSTER keywords. _______________________________________________________ Option________Description______________________________ ALL Configures the core environment and all client and server services. CLIENT Configures all client services and related software. MINIMUM Configures the domain, Internet interfaces, Rlogin client, FTP client, FTP server, TELNET client, and TELNET server. Prompts you for optional components. SERVER Configures all servers and related software. WORKSTATION Configures the BIND resolver, the domain, dynamic routing, Internet interfaces, time zone, remote login, remote shell, remote executive, FTP client, FTP server, TELNET client, TELNET server, and SMTP. _______________________________________________________ Keyword_______Description______________________________ CLUSTER Configures all specified components clusterwide (except for the BIND server and SMTP, which you cannot configure clusterwide). ENABLE Enables the specified components. DISABLE_______Disables_the_specified_components._______ For example, the following command enables the client services for the entire cluster: $ @SYS$MANAGER:TCPIP$CONFIG CLIENT ENABLE CLUSTER ________________________Note ________________________ The procedure implements two levels of enabling and disabling: clusterwide and node-specific (except 3-28 Configuring TCP/IP Services Configuring TCP/IP Services 3.4 Using TCPIP$CONFIG Option Commands to Bypass TCPIP$CONFIG Menus for SMTP, which is configured and enabled as node- specific only). _____________________________________________________ 3.5 Making Configuration Changes Take Effect Configuration changes made to TCP/IP Services software do not take effect until you start (or restart) the affected services. You may need to restart TCP/IP Services or simply the individual services affected, as explained in Table 3-2. Table_3-2_Making_Configuration_Changes_Take_Effect______________ When you change the following Do the following to make services... the changes take effect Comments _______________________________________________________________ Core environment Start or restart the Do this before (domain, Internet TCP/IP Services software. you run tests interface, routing, (verification BIND resolver, time procedures) or zone). customize the environment. Methods to start TCP/IP Services are described in Sections 3.7 and 3.10. (continued on next page) Configuring TCP/IP Services 3-29 Configuring TCP/IP Services 3.5 Making Configuration Changes Take Effect Table_3-2_(Cont.)_Making_Configuration_Changes_Take_Effect______ When you change the following Do the following to make services... the changes take effect Comments ________________________________________________________________ Client, server, or If you did not make Usage of optional services changes to the core startup command only. environment, you need procedures only start or restart for individual each affected service services is individually. Do this explained in by choosing the "Start Section 3.10.3. service" option in the service's configuration menu. Alternatively, you can use each service's startup command procedure. If you also made changes to core environment services, start TCP/IP ______________________Services._________________________________ ________________________Note ________________________ You can have the TCP/IP Services software started automatically each time the OpenVMS operating system is rebooted, or you can restart the software manually, as explained in Section 3.10. _____________________________________________________ 3.6 Stopping TCP/IP Services Using TCPIP$CONFIG Stop TCP/IP Services on your system by choosing option 5 (Shutdown HP TCP/IP Services for OpenVMS) from the Main Configuration menu, as in the following example: 3-30 Configuring TCP/IP Services Configuring TCP/IP Services 3.6 Stopping TCP/IP Services Using TCPIP$CONFIG 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 A - Configure options 1 - 4 [E] - Exit configuration procedure Enter configuration option: 5 The TCP/IP Services shutdown procedure displays a series of messages similar to the following example (the messages displayed depend on the configuration): Begin Shutdown... %TCPIP-I-INFO, TCP/IP Services shutdown beginning at 5-SEP-2003 15:26:14.39 %TCPIP-S-SHUTDONE, TCPIP$FINGER shutdown completed %TCPIP-S-SHUTDONE, TCPIP$FTP_CLIENT shutdown completed %TCPIP-S-SHUTDONE, TCPIP$FTP shutdown completed %TCPIP-S-SHUTDONE, TCPIP$INET_DRIVER shutdown completed %TCPIP-S-SHUTDONE, TCPIP$METRIC shutdown completed %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 %TCPIP-S-SHUTDONE, TCPIP$PORTMAPPER shutdown completed %TCPIP-S-SHUTDONE, TCPIP$PROXY shutdown completed %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 completed %TCPIP-S-SHUTDONE, TCPIP$SSH_CLIENT shutdown completed %TCPIP-S-SHUTDONE, TCPIP$SSH shutdown completed Configuring TCP/IP Services 3-31 Configuring TCP/IP Services 3.6 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 completed %TCPIP-S-SHUTDONE, TCP/IP Kernel shutdown completed %TCPIP-S-SHUTDONE, TCP/IP Services shutdown completed at 5-SEP-2003 15:26:17.78 Shutdown request completed. 3.7 Starting TCP/IP Services Using TCPIP$CONFIG After configuring the core environment, start TCP/IP Services on your system by choosing option 6 (Startup HP TCP/IP Services for OpenVMS) from the Main Configuration menu, as in the following example: 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 A - Configure options 1 - 4 [E] - Exit configuration procedure Enter configuration option: 6 The TCP/IP Services startup procedure displays a series of messages similar to the following example (the messages displayed depend on the configuration): Begin Startup... 3-32 Configuring TCP/IP Services Configuring TCP/IP Services 3.7 Starting TCP/IP Services Using TCPIP$CONFIG %TCPIP-I-INFO, TCP/IP Services startup beginning at 5-SEP-2003 15:27:08.34 %TCPIP-I-NORMAL, timezone information verified %RUN-S-PROC_ID, identification of created process is 00000D42 %TCPIP-I-SETLOCAL, setting domain and/or local host %TCPIP-I-STARTCOMM, starting communication %TCPIP-I-SETPROTP, setting protocol parameters %TCPIP-I-DEFINTE, defining interfaces %TCPIP-I-STARTNAME, starting name service %TCPIP-I-STARTDROUT, starting dynamic routing %RUN-S-PROC_ID, identification of created process is 00000C4E %TCPIP-S-STARTDONE, TCP/IP Kernel startup completed %TCPIP-S-STARTDONE, TCPIP$BIND startup completed %TCPIP-I-PROXYLOADED, loaded 0 NFS proxy records %TCPIP-I-LOADSERV, loading TCPIP server proxy information %TCPIP-I-SERVLOADED, auxiliary server loaded with 0 proxy records -TCPIP-I-SERVSKIP, skipped 0 communication proxy records -TCPIP-I-SERVTOTAL, total of 0 proxy records read %TCPIP-S-STARTDONE, TCPIP$PROXY startup completed %TCPIP-S-STARTDONE, TCPIP$PORTMAPPER startup completed %TCPIP-S-STARTDONE, TCPIP$FINGER startup completed %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 completed %TCPIP-I-NOMAP, no filesystem mapping information available %TCPIP-S-STARTDONE, TCPIP$NFS startup completed %TCPIP-S-STARTDONE, TCPIP$NFS_CLIENT startup completed %TCPIP-S-STARTDONE, TCPIP$NTP startup completed %TCPIP-S-STARTDONE, TCPIP$PCNFS startup completed %TCPIP-S-STARTDONE, TCPIP$POP startup completed %RUN-S-PROC_ID, identification of created process is 000002DC %TCPIP-S-STARTDONE, TCPIP$PWIP_DRIVER startup completed %TCPIP-S-STARTDONE, TCPIP$REXEC startup completed %TCPIP-S-STARTDONE, TCPIP$RLOGIN startup completed %TCPIP-S-STARTDONE, TCPIP$RSH startup completed %TCPIP-S-STARTDONE, TCPIP$SMTP startup completed %TCPIP-S-STARTDONE, TCPIP$SSH startup completed %TCPIP-S-STARTDONE, TCPIP$SSH_CLIENT startup completed %TCPIP-S-STARTDONE, TCPIP$TELNET startup completed %TCPIP-S-STARTDONE, TCPIP$TFTP startup completed %TCPIP-S-STARTDONE, TCPIP$XDM startup completed %TCPIP-S-STARTDONE, TCP/IP Services startup completed at 5-SEP-2003 Configuring TCP/IP Services 3-33 Configuring TCP/IP Services 3.7 Starting TCP/IP Services Using TCPIP$CONFIG 15:27:50.47 Startup request completed. Press Return to continue ... ________________________Note ________________________ The TCPIP-I-NOMAP message in this example appears only if no file systems are mapped in the TCP/IP configuration database. If you need NFS services, 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 recurrence of this message during future startups by disabling the NFS server using the TCPIP$CONFIG configuration procedure. _____________________________________________________ 3.8 Verifying the Configuration You can verify the configuration by running the installa- tion verification procedure (IVP). You should run the IVP if any of the following apply: o You loaded the Product Authorization Key (PAK), and you want to verify that the lower-layer software and the Portmapper service are installed correctly. o You did not load the PAK, but you want to verify that TCP/IP Services is installed correctly for DECwindows to display the TCP/IP Services applications. o You require the software to transfer device socket packets that continuously vary in size between a sender and a receiver. o You need to test the Portmapper service with a pair of client/server programs. The IVP reports the time it took to run the test to SYS$OUTPUT. o You need to test your SNMP service. Before you run the IVP, make sure TCP/IP Services has started and you have SYSPRV, OPER, NETMBX, and TMPMBX privileges. 3-34 Configuring TCP/IP Services Configuring TCP/IP Services 3.8 Verifying the Configuration You can run the IVP from the TCPIP$CONFIG configuration procedure or by command line at the OpenVMS DCL prompt. When you run the IVP from TCPIP$CONFIG, you have the option of running an additional test that verifies the SNMP configuration. 3.8.1 Running the IVP from the TCPIP$CONFIG Command Procedure In the TCP/IP Services for OpenVMS Main Configuration menu, choose option 7 (Run tests). The Test menu appears, as in the following example: HP TCP/IP Services for OpenVMS TEST Menu Test options: 1 - Internet IVP 2 - SNMP IVP A - Tests 1 - 2 [E] - Exit menu Enter test option: Choose the appropriate option for the test you want to perform. 3.8.2 Running the IVP from the OpenVMS DCL Prompt To run the IVP at the DCL prompt, any time after exiting 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 3.8.3 Verifying the TCP/IP Services Internet Configuration When you choose either option 1 or option A from the TCPIP$CONFIG Test menu, or if you run the TCPIP$IVP command procedure at the command line, the IVP tests the basic TCP/IP Services software configuration, as in the following example. Here, the test completes successfully. Configuring TCP/IP Services 3-35 Configuring TCP/IP Services 3.8 Verifying the Configuration Enter test option: 1 Begin IVP... %%% TCPIP IVP: started %%% UDP/IP test started at 5-SEP-2003 16:13:03.62 UDP/IP test ended at 5-SEP-2003 16:13:03.69 UDP/IP transferred successfully in 0 seconds 4198400 bytes TCP/IP test started at 5-SEP-2003 16:13:04.20 TCP/IP test ended at 5-SEP-2003 16:13:04:28 TCP/IP transferred successfully in 0 seconds 4198400 bytes RAW_IP test started at 5-SEP-2003 16:13:41.71 RAW_IP test ended at 5-SEP-2003 16:13:41.72 RAW_IP transferred successfully in 0 seconds 251000 bytes %%% TCPIP IVP: completed successfully %%% IVP request completed. Press Return to continue ... If the IVP does not complete successfully, the procedure displays error messages. All IVP errors use the same format as OpenVMS system messages. For example: %TCPIP-E-IDENT, explanation of error. Table 3-3 lists some common problems that cause IVP error messages. If the recommended action does not correct the problem, contact your HP support representative. 3-36 Configuring TCP/IP Services Configuring TCP/IP Services 3.8 Verifying the Configuration Table_3-3_Troubleshooting_IVP_Errors______________________ If the problem is... Do the following... __________________________________________________________ Network configuration Shut down TCP/IP Services and is incorrect. rerun the configuration procedure. Startup fails. Check the system parameters in the MODPARAMS.DAT file and adjust them if necessary. (See Section 1.2.7.) Then shut down and restart TCP/IP Services. Installation kit is Request a replacement kit. defective. IVP fails because the Register a HP TCP/IP Services for PAK_is_missing._________OpenVMS_PAK.______________________ 3.8.4 Verifying the SNMP Configuration If you choose either option 2 or option A from the TCPIP$CONFIG Test menu, the IVP tests the SNMP service, as in the following example: Begin SNMP IVP... The SNMP IVP requires that TCPIP/IP Services be running. It performs the following startups and shutdowns on the SNMP service only (other TCP/IP services are not affected): - If SNMP is running, shuts down SNMP before initial configuration - Starts SNMP and runs tests - Shuts down SNMP and restores initial configuration - Before exiting, starts SNMP Shutting down the SNMP service... done. Creating temporary read/write community SNMPIVP_6520. Enabling SET operations. Starting up the SNMP service... done. Saving sysContact: Ralph Nickleby Setting sysContact to: Julius Caesar Retrieved sysContact: Julius Caesar (Retrieved value matches SET value.) Restoring sysContact to: Ralph Nickleby Configuring TCP/IP Services 3-37 Configuring TCP/IP Services 3.8 Verifying the Configuration Saving snmpEnableAuthenTraps: 2 (disabled) Setting snmpEnableAuthenTraps to: 1 (enabled) Retrieved snmpEnableAuthenTraps: 1 (enabled) (Retrieved value matches SET value.) Restoring snmpEnableAuthenTraps: 2 (disabled) Disabling SET operations. Deleting temporary read/write community SNMPIVP_6520. Shutting down and restarting the SNMP service... Shutting down the SNMP service... done. Starting up the SNMP service... done. SNMP IVP request completed. Press Return to continue ... 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." See file SYS$SYSDEVICE:[TCPIP$SNMP]TCPIP$SNMP_REQUEST.DAT for more details. Verify that SNMP trace is not enabled. sysContact could not be retrieved. Status = 0 The SNMP IVP has NOT completed successfully. In this case, the error could indicate that not all SNMP components have started, or that SNMP tracing is enabled and needs to be disabled. For information about SNMP trace, see the HP TCP/IP Services for OpenVMS Management manual. 3.9 Additional Configuration Tasks After you run TCPIP$CONFIG and enable the functionality and components appropriate for your network, you need to complete additional configuration tasks to enable access to product applications. TCP/IP Services provides a management command interface and logical names you can use to modify or customize the software for your environment. The additional configuration tasks include: o Populating databases (for example, for BIND and DHCP) o Setting up user accounts 3-38 Configuring TCP/IP Services Configuring TCP/IP Services 3.9 Additional Configuration Tasks o Setting up communication and NFS proxies o Defining print queues o Setting up, exporting, and maintaining file systems o Tuning the system for optimum performance Many of the services require additional configuration or optimization. For more information about how to configure each service, refer to the HP TCP/IP Services for OpenVMS Management manual. 3.10 Starting and Stopping TCP/IP Services You can use commands in your OpenVMS startup file to have TCP/IP Services started and stopped automatically when the OpenVMS system starts up or shuts down, as explained in Section 3.10.1. These commands start and stop all the TCP/IP Services components installed on your system. Alternatively, you can start and stop individual TCP/IP Services client or server services without affecting other TCP/IP Services components currently running. For information about starting and stopping individual services, see Section 3.10.3. If necessary, you can start and stop TCP/IP Services manually, as explained in Section 3.10.2. You can also start and stop user-written services, as explained in Section 3.10.4. 3.10.1 Automatically Starting and Stopping TCP/IP Services To allow TCP/IP Services software to start auto- matically when the system starts up, and to stop automatically when the system shuts down, edit the SYS$COMMON:[SYSMGR]SYSTARTUP_VMS.COM file and include the following command: @SYS$STARTUP:TCPIP$STARTUP If your system had earlier versions of TCP/IP Services, UCX$STARTUP.COM and UCX$SHUTDOWN.COM files might be present. These are no longer applicable; delete any definition of them from SYS$MANAGER:SYSTARTUP_VMS.COM. Configuring TCP/IP Services 3-39 Configuring TCP/IP Services 3.10 Starting and Stopping TCP/IP Services If you want TCP/IP Services to start after you log in to your OpenVMS account, the OpenVMS systemwide login procedure (typically SYS$MANAGER:SYLOGIN.COM) must have world read and execute protections (W:RE). To display the current protections, enter the following command: $ DIR/PROTECTION SYS$MANAGER:SYLOGIN.COM For information about protections, refer to the OpenVMS documentation. 3.10.2 Starting and Stopping TCP/IP Services Manually To start TCP/IP Services manually, enter the following command: $ @SYS$STARTUP:TCPIP$STARTUP To stop TCP/IP Services manually, enter the following command: $ @SYS$STARTUP:TCPIP$SHUTDOWN 3.10.3 Starting and Stopping Individual Services On a system already running TCP/IP Services, you can configure an individual server or client component without affecting the other TCP/IP Services components running on your system and without having to restart TCP/IP Services. Most services can be shut down and started independently. This is useful when you change parameters or logical names that require the service to be restarted. The following files are provided: o SYS$STARTUP:TCPIP$service_STARTUP.COM allows you to start the service service. o SYS$STARTUP:TCPIP$service_SHUTDOWN.COM allows you to shut down the service service. To preserve site-specific parameter settings and commands, create the following files. These files are not overwritten when you reinstall TCP/IP Services: 3-40 Configuring TCP/IP Services Configuring TCP/IP Services 3.10 Starting and Stopping TCP/IP Services o SYS$STARTUP:TCPIP$service_SYSTARTUP.COM can be used as a repository for site-specific definitions and parameters to be invoked when service is started. o SYS$STARTUP:TCPIP$service_SYSHUTDOWN.COM can be used as a repository for site-specific definitions and parameters to be invoked when service is shut down. In these file names, service is the name of the service to be started or shut down. For example, use TCPIP$NTP_ SHUTDOWN to shut down the NTP service. For more information, see the HP TCP/IP Services for OpenVMS Management manual. 3.10.4 Starting and Stopping User-Written Services TCP/IP Services supplies command procedures for starting and stopping user-written services. To start a user- written service, enter the following command: $ SYS$STARTUP:TCPIP$CUSTOMER_SERVICE_STARTUP service To stop the user-written service, enter the following command: $ SYS$STARTUP:TCPIP$CUSTOMER_SERVICE_SHUTDOWN service In either command, specify the name of the service as defined using the TCP/IP management command SET SERVICE. ________________________Note ________________________ Remember that any service name with lowercase characters is interpreted by the startup and shutdown procedures as uppercase unless you enclose the name in quotation marks. If you defined the service using quotation marks to preserve the case, be sure to use quotation marks when you specify the service name with the startup or shutdown command. _____________________________________________________ Configuring TCP/IP Services 3-41 Configuring TCP/IP Services 3.11 Specifying TCP/IP Services as the Transport for DECwindows Applications 3.11 Specifying TCP/IP Services as the Transport for DECwindows Applications To enable TCP/IP Services as the transport interface for DECwindows applications, add the following line to the SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM command procedure: $ DECW$SERVER_TRANSPORTS == "DECNET,LOCAL,TCPIP" Then restart DECwindows: $ @SYS$STARTUP:DECW$STARTUP RESTART If DECnet or DECnet-Plus software runs on the system, start it. To display DECwindows applications from a DECwindows client (remote host) to a DECwindows server (your workstation), proceed as follows: 1. Set up security on the remote host. 2. Add the remote client to the local hosts database. 3. Add to SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM the following line: $ DECW$SERVER_TRANSPORTS == "DECNET,LOCAL,TCPIP" 4. Set the display for the applications to the remote host: $ SET DISPLAY/CREATE/NODE=remote-host/TRANSPORT=TCPIP 3-42 Configuring TCP/IP Services A ________________________________________________________________ Sample New TCP/IP Services Installation and Configuration This appendix shows a sample installation and configura- tion of the TCP/IP Services product on a system on which the product has never been installed. A.1 Sample New Installation Procedure The following example shows a sample installation dialog for the TCP/IP Services. In this example, the installation takes place on a system where the product has not been installed. If TCP/IP Services had been installed previously on the system, the installation dialog would differ slightly (see Chapter 2). ________________________Note ________________________ The symbols xx in the following example represent the product's two-digit update version number. _____________________________________________________ Choose one or more items from the menu separated by commas: 1 The following product has been selected: DEC AXPVMS TCPIP V5.4-xx Layered Product Do you want to continue? [YES] Configuration phase starting ... You will be asked to choose options, if any, for each selected product and for any products that may be installed to satisfy software dependency requirements. DEC AXPVMS TCPIP V5.4-xx: HP TCP/IP Services for OpenVMS. Copyright 1976, 2003 Hewlett-Packard Development Company, L.P. Hewlett-Packard Development Company, L.P. Sample New TCP/IP Services Installation and Configuration A-1 Sample New TCP/IP Services Installation and Configuration A.1 Sample New Installation Procedure HP TCP/IP Services for OpenVMS offers several license options. Do you want the defaults for all options? [YES] Do you want to review the options? [NO] Execution phase starting ... The following product will be installed to destination: DEC AXPVMS TCPIP V5.4-xx DISK$ALPHASYS:[VMS$COMMON.] Portion done: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90% %PCSI-I-PRCOUTPUT, output from subprocess follows ... % TCPIP-W-PCSI_INSTALL % - Execute SYS$MANAGER:TCPIP$CONFIG.COM to proceed with configuration of % HP TCP/IP Services. % Portion done: 100% The following product has been installed: DEC VAXVMS TCPIP V5.4-xx Layered Product DEC VAXVMS TCPIP T5.4-xx: HP TCP/IP Services for OpenVMS. Check the release notes for current status of the product. $ A.2 Sample New Configuration Procedure The following example shows a sample configuration dialog for the TCP/IP Services, in which the following components are configured: o Core environment o TELNET client o FTP server In this example, the configuration takes place on a system where the product has never been configured. If TCP/IP Services had been configured previously on the system, the dialog would differ significantly (see Chapter 3). A-2 Sample New TCP/IP Services Installation and Configuration Sample New TCP/IP Services Installation and Configuration A.2 Sample New Configuration Procedure TCP/IP Network Configuration Procedure This procedure helps you define the parameters required to run HP TCP/IP Services for OpenVMS on this system. Checking TCP/IP Services for OpenVMS configuration database files. Creating SYS$COMMON:[SYSEXE]TCPIP$SERVICE.DAT Creating SYS$COMMON:[SYSEXE]TCPIP$HOST.DAT Creating SYS$COMMON:[SYSEXE]TCPIP$NETWORK.DAT Creating SYS$COMMON:[SYSEXE]TCPIP$ROUTE.DAT Creating SYS$COMMON:[SYSEXE]TCPIP$PROXY.DAT Creating SYS$COMMON:[SYSEXE]TCPIP$CONFIGURATION.DAT HP TCP/IP Services for OpenVMS requires a definition for at least one interface. There are no interfaces defined on this system. Please select the Interface option from the Core Environment Menu. 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 A - Configure options 1 - 4 [E] - Exit configuration procedure Enter configuration option: 1 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 Sample New TCP/IP Services Installation and Configuration A-3 Sample New TCP/IP Services Installation and Configuration A.2 Sample New Configuration Procedure Enter configuration option: A DOMAIN Configuration Enter Internet domain: acme.com INTERFACE Configuration The Ethernet device(s) on your system are: EWA0: * Not Configured * Start of configuration questions for Internet interface WE0. WE0 is the Ethernet device ESA0: WE0 has not been configured HP TCP/IP Services for OpenVMS Interface WE0 Configuration Menu Configuration options: 1 - Configure interface manually 2 - Let DHCP configure interface [E] - Exit menu (Do not configure interface WE0) Enter configuration option: 1 Enter fully qualified host name: HEARTS.BUDGET.ACME.COM Enter Internet address: 10.0.2.4 Enter Internet network mask for hearts [255.0.1.0]: 255.1.12.1 Enter broadcast mask for hearts [10.0.2.255]: The following parameters will be used to define the Internet interface WE0: Host name: hearts Internet address: 10.0.2.4 Network mask: 255.0.0.0 Broadcast mask: 10.0.2.255 * Is the above correct [YES]: failSAFE IP failSAFE IP uses multiple Network Interface Controllers (NICs) to provide high availability of IP addresses. In the event of a NIC failure, (e.g. any event preventing the NIC from receiving data), all IP addresses associated with the failed NIC are reassigned to a preconfigured failover target. A-4 Sample New TCP/IP Services Installation and Configuration Sample New TCP/IP Services Installation and Configuration A.2 Sample New Configuration Procedure In a cluster configuration, the IP address may be preconfigured on NICs across other cluster members. This provides cluster-wide failover for the IP address. See the management guide for more configuration options. You will be asked what other NICs on this node will act as failover targets. * Configure failover target for failSAFE IP [NO]: End of configuration questions for Internet interface WE0 DYNAMIC ROUTING Configuration Dynamic routing has not been configured. You may configure dynamic ROUTED or GATED routing. You cannot enable both at the same time. If you want to change from one to the other, you must disable the current routing first, then enable the desired routing. If you enable dynamic ROUTED routing, this host will use the Routing Information Protocol (RIP) - Version 1 to listen for all dynamic routing information coming from other hosts to update its internal routing tables. It will also supply its own Internet addresses to routing requests made from remote hosts. If you enable dynamic GATED routing, you will be able to configure this host to use any combination of the following routing protocols to exchange dynamic routing information with other hosts on the network: Routing Information Protocol (RIP) - Version 1 & 2 Router Discovery Protocol (RDISC) Open Shortest Path First (OSPF) Exterior Gateway Protocol (EGP) Border Gateway Protocol (BGP-4) Static routes * Do you want to configure dynamic ROUTED or GATED routing [NO]: A default route has not been configured. * Do you want to configure a default route [YES]: Enter your Default Gateway host name or address: GATE1.BUDGET.ACME.COM gate1.budget.acme.com is not in the local host database. Enter Internet address for gate1.budget.acme.com: 10.0.2.66 Sample New TCP/IP Services Installation and Configuration A-5 Sample New TCP/IP Services Installation and Configuration A.2 Sample New Configuration Procedure BIND RESOLVER Configuration A BIND resolver has not been configured. HP TCP/IP Services for OpenVMS supports the Berkeley Internet Name Domain (BIND) resolver. BIND is a network service that enables clients to name resources or objects and share information with other objects on the network. Before configuring your system as a BIND resolver, you should first be sure that there is at least one system on the network configured as either a BIND primary or secondary server for this domain. You can specify a BIND server by its address or name; however, if specified by name, an entry for it must exist in the TCPIP$HOST database. You will be asked one question for each server. Press Return at the prompt to terminate the list. Enter your BIND server name: NUMB9.BUDGET.ACME.COM numb9.budget.acme.com is not in the local host database. Enter Internet address for numb9.budget.acme.com: 10.0.2.11 Enter your BIND server name: Creating file TCPIP$ETC:IPNODES.DAT Creating file TCPIP$ETC:SERVICES.DAT TCPIP uses timezone information provided by the OpenVMS Operating System. No additonal timezone configuration is needed for TCPIP when the operating system is configured correctly. This section verifies the current OpenVMS timezone configuration. A warning message (TCPIP-W-) indicates that corrective action should be taken. TCPIP will appear to operate but components may display either the wrong time or a time inconsistent with other applications. %TCPIP-I-INFO, Logical name SYS$TIMEZONE_RULE found. -TCPIP-I-INFO, Software for automatic Summer/Winter time (TDF) change -TCPIP-I-INFO, is present. -TCPIP-I-INFO, Further action to ensure TDF change is not necessary. %TCPIP-I-NORMAL, timezone information verified Press Return to continue ... HP TCP/IP Services for OpenVMS Core Environment Configuration Menu A-6 Sample New TCP/IP Services Installation and Configuration 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 A - Configure options 1 - 5 [E] - Exit menu Enter configuration option: 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 A - Configure options 1 - 4 [E] - Exit configuration procedure Enter configuration option: 2 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 A - Configure options 1 - 9 [E] - Exit menu Enter configuration option: 8 Sample New TCP/IP Services Installation and Configuration A-7 Sample New TCP/IP Services Installation and Configuration A.2 Sample New Configuration Procedure TELNET Configuration Service is not defined in the TCPIP$SERVICE database. Service is not enabled. Service is stopped. TELNET configuration options: 1 - Enable service on this node [E] - Exit TELNET configuration Enter configuration option: 1 Creating TELNET Service Entry 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 A - Configure options 1 - 9 [E] - Exit menu Enter configuration option: 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 A - Configure options 1 - 4 [E] - Exit configuration procedure Enter configuration option: 3 A-8 Sample New TCP/IP Services Installation and Configuration Sample New TCP/IP Services Installation and Configuration A.2 Sample New Configuration Procedure HP TCP/IP Services for OpenVMS Server Components Configuration Menu Configuration options: 1 - BIND Disabled Stopped 12 - NTP Disabled Stopped 2 - BOOTP Disabled Stopped 13 - PC-NFS Disabled Stopped 3 - DHCP Disabled Stopped 14 - POP Disabled Stopped 4 - FINGER Disabled Stopped 15 - PORTMAPPER Disabled Stopped 5 - FTP Disabled Stopped 16 - RLOGIN Enabled Stopped 6 - IMAP Disabled Stopped 17 - RMT Disabled Stopped 7 - LBROKER Disabled Stopped 18 - SNMP Disabled Stopped 8 - LPR/LPD Disabled Stopped 19 - SSH Disabled Stopped 9 - METRIC Disabled Stopped 20 - TELNET Enabled Stopped 10 - NFS Disabled Stopped 21 - TFTP Disabled Stopped 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 not defined in the SYSUAF. Service is not defined in the TCPIP$SERVICE database. Service is not enabled. Service is stopped. FTP configuration options: 1 - Enable service on this node [E] - Exit FTP configuration Enter configuration option: 1 The FTP CLIENT is enabled. * Do you want to configure FTP CLIENT [NO]: HP TCP/IP Services for OpenVMS Server Components Configuration Menu Configuration options: Sample New TCP/IP Services Installation and Configuration A-9 Sample New TCP/IP Services Installation and Configuration A.2 Sample New Configuration Procedure 1 - BIND Disabled Stopped 12 - NTP Disabled Stopped 2 - BOOTP Disabled Stopped 13 - PC-NFS Disabled Stopped 3 - DHCP Disabled Stopped 14 - POP Disabled Stopped 4 - FINGER Disabled Stopped 15 - PORTMAPPER Disabled Stopped 5 - FTP Enabled Stopped 16 - RLOGIN Enabled Stopped 6 - IMAP Disabled Stopped 17 - RMT Disabled Stopped 7 - LBROKER Disabled Stopped 18 - SNMP Disabled Stopped 8 - LPR/LPD Disabled Stopped 19 - SSH Disabled Stopped 9 - METRIC Disabled Stopped 20 - TELNET Enabled Stopped 10 - NFS Disabled Stopped 21 - TFTP Disabled Stopped 11 - LOCKD/STATD Disabled Stopped 22 - XDM Disabled Stopped A - Configure options 1 - 22 [E] - Exit menu Enter configuration option: 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 A - Configure options 1 - 4 [E] - Exit configuration procedure Enter configuration option: 6 Begin Startup... A-10 Sample New TCP/IP Services Installation and Configuration Sample New TCP/IP Services Installation and Configuration A.2 Sample New Configuration Procedure %TCPIP-I-INFO, TCP/IP Services startup beginning at 5-SEP-2003 13:22:27 .82 %TCPIP-I-NORMAL, timezone information verified %RUN-S-PROC_ID, identification of created process is 00000058 %TCPIP-I-SETLOCAL, setting domain and/or local host %TCPIP-I-STARTCOMM, starting communication %TCPIP-I-SETPROTP, setting protocol parameters %TCPIP-I-DEFINTE, defining interfaces %TCPIP-I-STARTNAME, starting name service %TCPIP-S-STARTDONE, TCP/IP Kernel startup completed %TCPIP-I-PROXYLOADED, loaded 0 NFS proxy records %TCPIP-I-LOADSERV, loading TCPIP server proxy information %TCPIP-I-SERVLOADED, auxiliary server loaded with 0 proxy records -TCPIP-I-SERVSKIP, skipped 0 communication proxy records -TCPIP-I-SERVTOTAL, total of 0 proxy records read %TCPIP-S-STARTDONE, TCPIP$PROXY startup completed %TCPIP-S-STARTDONE, TCPIP$FTP startup completed %TCPIP-S-STARTDONE, TCPIP$INET_DRIVER startup completed %TCPIP-I-NOMAP, no filesystem mapping information available %TCPIP-S-STARTDONE, TCPIP$RLOGIN startup completed %TCPIP-S-STARTDONE, TCPIP$TELNET startup completed %TCPIP-S-STARTDONE, TCP/IP Services startup completed at 5-SEP-2003 13: 23:00.49 Startup request completed. Press Return to continue ... Sample New TCP/IP Services Installation and Configuration A-11 ________________________________________________________________ Index A Configuration database ___________________________ files Advanced Server for OpenVMS creating, 3-6, A-2 configuring, 3-23 Configuration procedure Anonymous FTP See Configuring TCP/IP configuring, 3-23 Services; TCPIP$CONFIG Automatic configuration of configuration procedure TCP/IP Services, 3-3 Configuration worksheet, B 1-9 ___________________________ Configuring TCP/IP Services BG device message See also TCPIP$CONFIG during installation, 2-5 configuration procedure BIND resolver automatic, 3-3 configuration example, client environment, 3-17 3-16 to 3-20 configuring, 3-16, A-2 client services, 3-18 BIND server configuration files configuring, 3-20 creating new, 3-6 BOOTP server core environment, 3-8 to configuring, 3-20 3-16 C description of major ___________________________ tasks, 1-1 CD-ROM distribution kit new configuration, 1-1 inspecting, 1-3 optional components, 3-23 Client environment postconfiguration tasks, configuration menu, 3-17, 3-38 A-2 server environment, 3-20 configuring, 3-17 to 3-23 Client services servers, 3-20, 3-23 starting and stopping tasks, recommended individually, 3-40 sequence, 3-1 TCPIP$CONFIG menus, 3-8 Index-1 Configuring TCP/IP Services Configuring TCP/IP Services (cont'd) TCPIP$CONFIG output TCPIP$CONFIG menus, example (cont'd) description, 3-6 Server Components TCPIP$CONFIG option Configuration menu, commands, 3-27 3-20, A-2 TCPIP$CONFIG output time zone example, A-2 to A-11 configuration beginning, 3-4 example, 3-16, Bind resolver, 3-16 A-2 Client Environment XDM Configuration Configuration menu, menu, 3-22 3-17, A-2 time required, 1-2 Core Environment verifying services, 3-34 Configuration menu, Core Environment 3-8, A-2 Configuration menu, 3-8, creating database A-2 files, 3-6, A-2 Dynamic Routing D__________________________ Configuration menu, Database files 3-14, A-2 creating, 3-6, A-2 failSAFE configuration DECnet over TCP/IP , 3-12, A-2 configuration example, failSAFE configuration 3-25 options, 3-27 configuring to use, 3-23 FTP Client DECwindows Configuration menu, components required for 3-18 XDM, 3-22 Interface defining TCP transport, Configuration menu, 3-42 3-10 requirements for product Kerberos Applications installation, 1-4 Configuration menu, DHCP client 3-26 configuring, 3-17 Main Configuration DHCP server menu, 3-6, A-2 configuring, 3-20 Optional Components configuring TCP/IP Configuration menu, Services, 3-3 3-24, A-2 Disk PWIP configuration space requirements, 1-5 example, 3-25 system, backing up, 1-4 Index-2 Distribution kit inspecting, 1-3 G__________________________ Domain Global pagelets and configuring, 3-10, A-2 sections Dynamic routing increasing, 1-6 configuring, 3-14, A-2 requirements, 1-6 E__________________________ I EAK ___________________________ Installing TCP/IP Services, See Early Adopters Kits 2-1 to 2-6 (EAKs) configuration phase Early Adopters Kits (EAKs), sample output, 2-4 1-8 execution phase Error messages sample output, 2-4 at SNMP verification, installed files, 2-6 3-38 major tasks, 1-1 IVP (installation new installation, A-2 verification procedure) sample output, 2-3, A-1 , 3-36 time required, 1-2 TCPIP-I-NOMAP, 3-34 Interface configuring, 3-10, A-2 F__________________________ Interface Configuration failSAFE IP menu, 3-10 configuration options IPv6 menu, 3-27 EAK, 1-8 configuring, 3-23, 3-24 warning message in configuring and enabling TCPIP$CONFIG, 3-9 client, 3-27 IVP (installation configuring target IP verification procedure) address, 3-10, 3-11, description, 3-34 A-2 error messages, 3-36 defined, 3-24 example, 3-35 EAK, 1-8 OpenVMS TEST menu, 3-35 FINGER server SNMP verification example configuring, 3-20 , 3-37 FTP client K configuring, 3-18 ___________________________ FTP server Kerberos configuring, 3-20, A-2 benefits, 3-24 configuration menu, 3-26 configuring and enabling, 3-25 Index-3 Kerberos (cont'd) configuring to use, 3-23, O__________________________ 3-24 OpenVMS License Management Facility (LMF) L__________________________ using to register PAK, LBROKER server 1-4 configuring, 3-20 OpenVMS operating system License Product reboot, 2-5 Authorization Key upgrading, 1-4 See PAK OpenVMS TEST menu, 3-35 LOCKD/STATD server Optional components configuring, 3-20 Advanced Server for LPR/LPD client OpenVMS, 3-24 configuring, 3-17 Anonymous FTP, 3-24 LPR/LPD server configuration menu, 3-24, configuring, 3-20 A-2 failSAFE IP, 3-24 M Kerberos authentication, ___________________________ 3-24 Memory PATHWORKS (Advanced physical memory Server), 3-24 requirements, 1-5 PWIP driver, 3-24 Menus SRI QIO interface, 3-24 TCPIP$CONFIG, 3-6 METRIC server P__________________________ configuring, 3-20 PAK Mixed-case service names, registering, 1-4 3-41 PATHWORKS N configuration example, ___________________________ 3-25 NFS client configuring, 3-23 configuring, 3-17 Internet Protocol driver NFS server See PWIP configuring, 3-20 PC-NFS server NOMAP error message, 3-34 configuring, 3-20 Nonpaged dynamic pool POLYCENTER Software increasing, 1-6 Installation utility NTP server for installing or configuring, 3-20 upgrading, 2-1 to 2-6 Index-4 Pool, nonpaged dynamic, Shutting down TCP/IP 1-6 Services POP server See Stopping TCP/IP configuring, 3-20 Services PORTMAPPER server SMTP client configuring, 3-20 configuring, 3-17 Postconfiguration tasks, SNMP 3-38 testing, 3-37 PWIP verification error configuration example, messages, 3-38 3-25 verification example, configuring, 3-24 3-37 SNMP server R__________________________ configuring, 3-20 Reboot, 2-6 SRI QIO Release notes configuring to use, 3-23 extracting into a .TXT SSH file, 1-4 configuration note, 3-17, location after 3-20 installation, 2-6 EAK, 1-8 REXEC and RSH client SSH client configuring, 3-17 configuring, 3-17 RLOGIN client SSH server configuring, 3-17 configuring, 3-20 RLOGIN server Starting TCP/IP Services, configuring, 3-20 3-39 RMT server after configuration, 3-32 configuring, 3-20 automatically, 3-39 manually, 3-40 S__________________________ using TCPIP$CONFIG, 3-32 Secure Shell Stopping TCP/IP Services, 3-39 See SSH automatically, 3-39 Servers manually, 3-40 configuration menu, 3-20, using TCPIP$CONFIG, 3-30 A-2 System parameters starting and stopping checking and changing individually, 3-40 before installing, 1-5 Service names to 1-7 for user-supplied services, 3-41 Index-5 TCP/IP Services (cont'd) T__________________________ stopping using Tasks TCPIP$CONFIG, 3-30 major, installing and upgrading, 2-1 to 2-6 configuring, 1-1 verifying, 3-34 TCP/IP Services TCPIP$CONFIG configuration and Anonymous FTP access, procedure 3-24 See also Configuring client services TCP/IP Services configuring, 3-17 to BIND resolver 3-20 configuration, 3-16 starting and stopping Client Environment individually, 3-40 Configuration menu, configuration, 3-1 to 3-17, A-2 3-38 Core Environment new, A-2 Configuration menu, configuration files 3-8, A-2 converting from Dynamic Routing previous Configuration menu, configuration, 3-4 3-14, A-2 configuration preparation failSAFE configuration , 1-9 example, 3-12, A-2 core environment failSAFE configuration configuring, 3-8 to options menu, 3-27 3-16 FTP Client Configuration installation, 2-1 to 2-6 menu, 3-18 new, A-1 Interface Configuration installation preparation, menu, 3-10 1-2 to 1-8 Kerberos Applications servers Configuration menu, configuring, 3-20 to 3-26 3-23 Main Configuration menu, starting and stopping 3-6, A-2 individually, 3-40 menus starting after description, 3-6 configuration, 3-29 Optional Components starting and stopping Configuration menu, automatically, 3-39 3-24, A-2 starting and stopping output example, 3-4 to manually, 3-40 3-27, A-2 to A-11 starting using output example, creating TCPIP$CONFIG, 3-32 database files, 3-6, A-2 Index-6 TCPIP$CONFIG configuration procedure (cont'd) U__________________________ PWIP configuration UIC codes example, 3-25 assigning, 1-7 Server Components Upgrading TCP/IP Services, Configuration menu, 2-1 to 2-6 3-20, A-2 User access time zone configuration configuring to allow example, 3-16, A-2 Anonymous FTP access, XDM Configuration menu, 3-23 3-22 User identification code TCPIP-I-NOMAP error message (UIC) , 3-34 assigning, 1-7 TELNET client configuring, 3-17, A-2 V__________________________ TELNET server Verifying the SNMP configuring, 3-20 configuration, 3-37 TFTP server Verifying the TCP/IP configuring, 3-20 Services configuration, Time zone 3-34 configuration example, 3-16, A-2 X configuring, 3-16, A-2 ___________________________ Troubleshooting XDM server configuration procedure and DECwindows problems, 3-36 requirements, 3-22 configuring, 3-22 Index-7