DIGITAL_TCP/IP_Services_for_OpenVMS___________ Installation and Configuration Order Number: AA-LU49L-TE January 1999 This manual explains how to install and configure the DIGITAL TCP/IP for OpenVMS layered application product on your OpenVMS host. Revision Information: This is a revised manual. Operating Systems: OpenVMS Alpha Versions 7.1, 7.2 OpenVMS VAX Versions 7.1, 7.2 Software Version: DIGITAL TCP/IP Services for OpenVMS Version 5.0 Compaq Computer Corporation Houston, Texas __________________________________________________________ January 1999 Compaq Computer Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from Compaq or an authorized sublicensor. Compaq conducts its business in a manner that conserves the environment and protects the safety and health of its employees, customers, and the community. © Compaq Computer Corporation 1999. All rights reserved. The following are trademarks of Compaq Computer Corporation: ACMS, Alpha, Compaq, DECdtm, DDCMP, DEC, DECnet, DECNIS, DECserver, DECsystem, DIGITAL, DIGITAL UNIX, DNA, InfoServer, LAT, OpenVMS, PATHWORKS, POLYCENTER, ULTRIX, VAX, VAXstation, VMS, VMScluster, and the Compaq logo. The following are third-party trademarks: Sun, NFS, and PC-NFS are registered trademarks of Sun Microsystems, Inc. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company Ltd. All other trademarks and registered trademarks are the property of their respective holders. ZK6524 This document is available on CD-ROM. 0 -3 ________________________________________________________________ Contents Preface.................................................. v 1 Preparing to Install and Configure TCP/IP Services 1.1 Understanding the Major Tasks Involved....... 1-1 1.2 Preinstallation Tasks........................ 1-2 1.2.1 Inspecting the Distribution Kit.......... 1-2 1.2.2 Extracting the Release Notes............. 1-2 1.2.3 Backing Up the System Disk and Upgrading OpenVMS.................................. 1-3 1.2.4 Registering the License Product Authorization Key........................ 1-3 1.2.5 Checking the Disk Space.................. 1-4 1.2.6 Checking the Physical Memory............. 1-4 1.2.7 Checking the System Parameters........... 1-5 1.2.7.1 Global Pagelets and Global Sections ... 1-5 1.2.7.2 Nonpaged Dynamic Pool.................. 1-5 1.2.7.3 Interrupt Stack Pages (OpenVMS VAX Only).................................. 1-6 1.2.8 Assigning a User Identification Code..... 1-6 1.3 Assembling Configuration Information......... 1-7 2 Installing TCP/IP Services 2.1 Installation Procedure....................... 2-1 v 3 Configuring TCP/IP Services 3.1 Recommended Order for Configuring TCP/IP Services..................................... 3-1 3.2 Running TCPIP$CONFIG......................... 3-2 3.2.1 Converting Existing TCP/IP Services Configuration Files (Upgrade Only)....... 3-2 3.2.2 Creating New TCP/IP Services Configuration Files...................... 3-3 3.2.3 Understanding the Configuration Menus.... 3-4 3.2.4 Configuring the Core Environment and the Client and Server Components............. 3-5 3.2.5 Configuring the Optional Components...... 3-11 3.3 Using TCPIP$CONFIG Option Commands........... 3-12 3.4 Starting TCP/IP Services..................... 3-14 3.5 Verifying the Configuration.................. 3-14 3.6 Additional Configuration Tasks............... 3-15 3.7 Automatically Starting and Stopping TCP/IP Services..................................... 3-16 3.8 Specifying TCP/IP Services as the Transport for DECwindows Applications.................. 3-17 Index Examples 2-1 TCP/IP Services Installation: Sample POLYCENTER Software Installation Utility Procedure................................ 2-3 Tables 1 DIGITAL TCP/IP Services for OpenVMS Documentation............................ vii 1-1 Major Tasks: Installing and Configuring.............................. 1-1 1-2 Configuration Planning Worksheet......... 1-8 3-1 Tasks: Configuring TCP/IP Services....... 3-1 3-2 Troubleshooting IVP Errors .............. 3-15 vi ________________________________________________________________ Preface The DIGITAL TCP/IP Services for OpenVMS product is Compaq's implementation of the TCP/IP networking protocol suite and internet services for OpenVMS Alpha and OpenVMS VAX systems. A layered software product, DIGITAL TCP/IP Services for OpenVMS 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 DIGITAL TCP/IP Services for OpenVMS (TCP/IP Services) networking software on an OpenVMS system. Intended Audience This manual is intended for OpenVMS system managers or network managers who install and configure networking software. The system managers using this manual should have an understanding of TCP/IP networks and terminology. New and Changed Features DIGITAL TCP/IP Services for OpenVMS Version 5.0 provides a new kernel based on the IPv4 kernel ported from DIGITAL UNIX Version 4.0D.[1] ___________________ [1] This kernel is based on the Berkeley Software Distribution (BSD) Versions 4.3 and 4.4 with enhance- ments from Compaq Computer Corporation. v Other new features include: o Dynamic Host Configuration Protocol (DHCP) that allows the system manager to provide dynamic allocation of IP addresses from a single OpenVMS host. o Gateway routing daemon (GATED) server and a comprehen- sive suite of interior and exterior routing protocols that offer advanced routing options. o Classless Inter-domain routing (CIDR) that allows networks to be built with variable-length subnetworks. o PathMTU discovery, a mechanism that allows an IP host to determine the most efficient packet size for use on a particular path between the source to the destination host. o UNIX management utilities to assist with the management of OpenVMS systems in a mixed UNIX and OpenVMS environment. o New implementations of NTP, SNMP, and BIND. o Improved online help and a new message database for use with the OpenVMS Help Message utility (MSGHLP). For information about the changes to information in this document, see the DIGITAL TCP/IP Services for OpenVMS Release Notes. This manual was revised to reflect the installation and configuration procedures for Version 5.0 of the DIGITAL TCP/IP Services for OpenVMS product. Document Structure This manual contains three chapters: 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. vi o Chapter 3 provides guidelines on how to configure the TCP/IP Services components and services after installation. Related Documentation Table 1 lists the manuals available with this version of DIGITAL TCP/IP Services for OpenVMS. Table_1_DIGITAL_TCP/IP_Services_for_OpenVMS_Documentation_______ Manual____________________Contents______________________________ DIGITAL TCP/IP Services This text file describes new features for OpenVMS Release and changes to the software including Notes installation, upgrade, configuration, and compatibility information. These notes also describe new and existing software problems and restrictions, and software and documentation corrections. Print this text file at the beginning of the installation procedure and read it before you install DIGITAL TCP/IP Services for OpenVMS. DIGITAL TCP/IP Services This manual explains how to install for OpenVMS Installation and configure the DIGITAL TCP/IP and Configuration Services for OpenVMS layered application product. DIGITAL TCP/IP Services This manual describes how to use the for OpenVMS User's Guide applications available with DIGITAL TCP/IP Services for OpenVMS such as remote file operations, e-mail, TELNET, TN3270, and network printing. This manual also explains how to use these services to communicate with systems on private internets or on the worldwide Internet. vii Table_1_(Cont.)_DIGITAL_TCP/IP_Services_for_OpenVMS_Documentation Manual____________________Contents______________________________ DIGITAL TCP/IP Services This manual describes how to configure for OpenVMS Management and manage the DIGITAL TCP/IP Services for OpenVMS product. Use this manual with the DIGITAL TCP/IP Services for OpenVMS Management Command Reference manual. DIGITAL TCP/IP Services This manual describes the DIGITAL for OpenVMS Management TCP/IP Services for OpenVMS management Command Reference commands. Use this manual with the DIGITAL TCP/IP Services for OpenVMS Management manual. DIGITAL 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 RPC). This manual also describes the RPC programming interface and how to use the RPCGEN protocol compiler to create applications. DIGITAL TCP/IP Services This manual describes how to use the for OpenVMS System OpenVMS system services and C Socket Services and C Socket programming interfaces to develop Programming network-based applications. DIGITAL TCP/IP Services This manual describes the Extensible for OpenVMS eSNMP Simple Network Management Protocol Programming and (eSNMP), the eSNMP application Reference programming interface (API), and how to build additional subagents __________________________to_manage_vendor-specific_equipment.__ For additional information about the DIGITAL TCP/IP Services for OpenVMS products and services, access the DIGITAL OpenVMS World Wide Web site at the following URL: http://www.openvms.digital.com viii You might find the Internetworking with TCP/IP: Principles, Protocols, and Architecture by Douglas Comer useful if you are looking for a comprehensive overview of the TCP/IP protocol suite. Terminology DIGITAL TCP/IP Services for OpenVMS Version 5.0 completes the change initiated several releases ago when the product name changed from "ULTRIX Connection (UCX)" to "DIGITAL TCP/IP Services for OpenVMS." To complete this change, the identifier "UCX" is replaced with "TCPIP" in the following cases: o Registered product facility code o Management command prompt o All messages, examples, and banners o All product file names, queues, and databases o All logical names, except those retained for compati- bility o All associated product documentation DIGITAL TCP/IP Services for OpenVMS is used to mean both: o DIGITAL TCP/IP Services for OpenVMS Alpha o DIGITAL TCP/IP Services for OpenVMS VAX The auxiliary server is the DIGITAL TCP/IP Services for OpenVMS implementation of the UNIX internet daemon (inetd). NFS is the DIGITAL TCP/IP Services for OpenVMS implementa- tion of the NFS protocols, including the NFS server, the NFS client, and PC-NFS. TN3270 means the TELNET client software that emulates IBM 3270 model terminals. The term UNIX refers to the DIGITAL UNIX operating system. DIGITAL UNIX is fully compatible with Version 4.3 and Version 4.4 of the Berkeley Software Distribution (BSD). Host and node both mean a system connected to an internet. ix The term Internet refers to the global interconnection of networks, as defined by RFC 1208, which consists of large networks using TCP/IP to provide universal connectivity, reaching the Defense Advanced Projects Research Internet, MILNET, NSFnet, CERN, and many worldwide universities, government research labs, military installations, and business enterprises. The term internet refers to private interconnected networks that use TCP/IP to connect together and function as one, virtual network. Conventions All IP addresses in this manual represent fictitious addresses. The following conventions apply to this manual. __________________________________________________________ Convention_______Meaning__________________________________ UPPERCASE TEXT Indicates names of OpenVMS and DIGITAL TCP/IP Services for OpenVMS commands, options, utilities, files, directories, hosts, and users. lowercase Indicates UNIX system output or user special type input, commands, options, files, directories, utilities, hosts, and users. bold text Indicates a new term. italic text Indicates a variable. Indicates that you press the Return key. Indicates that you press the Control key while you press the key noted by x. [ ] In command format descriptions, indicates the enclosed element is optional. You can enter as many as you want. x __________________________________________________________ Convention_______Meaning__________________________________ { } In command format descriptions, indicates you must enter at least one listed element. For readability, each element is either listed on a separate line or separated by vertical bars (|). Unless otherwise instructed, use a space to separate these elements when using them with commands. . . . Horizontal ellipsis points in examples indicate additional optional arguments have been omitted. Vertical ellipsis points indicate . omission of items from a code example . or display example; the items are omitted . because they are not important to the _________________topic_being_discussed.___________________ xi Reader's Comments Compaq welcomes your comments on this manual. Print or edit the online form SYS$HELP:OPENVMSDOC_ COMMENTS.TXT and send us your comments by: Internet openvmsdoc@zko.mts.dec.com Fax 603 884-0120, Attention: OSSG Documentation, ZKO3-4/U08 Mail Compaq Computer Corporation OSSG Documentation Group, ZKO3-4/U08 110 Spit Brook Rd. Nashua, NH 03062-2698 How To Order Additional Documentation Visit the OpenVMS Documentation World Wide Web site at the following URL to learn how to order additional documentation: http://www.openvms.digital.com:81/ If you need help deciding which documentation best meets your needs, call 800-DIGITAL (800-344-4825). xii 1 ________________________________________________________________ Preparing to Install and Configure TCP/IP Services This chapter explains how to prepare for installing and configuring DIGITAL TCP/IP Services for OpenVMS software. 1.1 Understanding the Major Tasks Involved 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 components and verify the configuration through the menu- driven TCPIP$CONFIG configuration procedure. This step generally takes about 15 minutes to complete. Table 1-1 lists the major tasks involved in installing and configuring TCP/IP Services. Table_1-1_Major_Tasks:_Installing_and_Configuring_________ Task_Action______________________________Go_to..._________ 1 Prepare for installation and Sections 1.2.1 - configuration. 1.3 2 Install TCP/IP Services. Chapter 2 3 Configure TCP/IP Services Chapter 3 according to your network needs. 4 Verify the configuration. Chapter 3 5 Complete additional configuration Chapter 3 _____and_setup_tasks,_as_appropriate._____________________ Preparing to Install and Configure TCP/IP Services 1-1 Preparing to Install and Configure TCP/IP Services 1.2 Preinstallation Tasks 1.2 Preinstallation Tasks You should complete the following tasks before you install TCP/IP Services on your system: o Inspect the distribution kit (Section 1.2.1) o Extract and read the TCP/IP Services release notes (Section 1.2.2) o Back up the system disk (Section 1.2.3) o Perform an OpenVMS operating system upgrade, if applicable (Section 1.2.3) o Register the TCP/IP Services license PAK (Section 1.2.4) o Check the disk space, memory, and system parameters (Sections 1.2.5 through 1.2.7) o Assign a User Identification Code (UIC), if necessary (Section 1.2.8) o Assemble information for configuration (Section 1.3) 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 distribution kit, check the CD master index for the kit location. If you have a magnetic tape or TK50 kit, supply the device name 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 Compaq representative. 1.2.2 Extracting the Release Notes The DIGITAL TCP/IP Services for OpenVMS Release Notes document contains important information you should know before you install the product. To extract the release notes to a text file, enter the following POLYCENTER Software Installation utility command: $ PRODUCT EXTRACT RELEASE_NOTES TCPIP/FILE=file_name.txt 1-2 Preparing to Install and Configure TCP/IP Services Preparing to Install and Configure TCP/IP Services 1.2 Preinstallation Tasks where file_name.txt is the file name you specify. If you do not specify a file name, the release notes are written to a file called DEFAULT.PCSI$RELEASE_NOTES in the current directory. 1.2.3 Backing Up the System Disk and Upgrading OpenVMS Before you install TCP/IP Services, Compaq 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 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 already 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. 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. Preparing to Install and Configure TCP/IP Services 1-3 Preparing to Install and Configure TCP/IP Services 1.2 Preinstallation Tasks 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 the system meets the following disk space requirements: __________________________________________________________ System_____________Minimum_Block_Size_____________________ OpenVMS Alpha 55,000 OpenVMS_VAX________40,000_________________________________ 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 the system meets the following physical memory requirements: __________________________________________________________ System_____________Minimum_Memory_________________________ OpenVMS Alpha 32 MB OpenVMS_VAX________24_MB__________________________________ To check the memory, enter: $ SHOW MEMORY/FULL 1-4 Preparing to Install and Configure TCP/IP Services Preparing to Install and Configure TCP/IP Services 1.2 Preinstallation Tasks 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 use AUTOGEN to reboot your system. 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. For example: $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLPAGES") 1234 $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLSECTS") 189 To increase the global pagelets and global sections, add statements to the MODPARAMS.DAT file that increase the values of the system parameters GBLPAGES and GBLSECTIONS. 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. 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 DIGITAL TCP/IP Services for OpenVMS. ! ADD_NPAGEDYN=500000 ADD_NPAGEVIR=500000 Preparing to Install and Configure TCP/IP Services 1-5 Preparing to Install and Configure TCP/IP Services 1.2 Preinstallation Tasks For more information about nonpaged dynamic pool, see the OpenVMS System Manager's Manual: Essentials. 1.2.7.3 Interrupt Stack Pages (OpenVMS VAX Only) If you are using PATHWORKS Internet Protocol (PWIP) on an OpenVMS VAX system, you should increase the number of interrupt stack pages (INTSTKPAGES) to 10 or more to help eliminate system startup warnings and crashes. For information about PATHWORKS, see the PATHWORKS documentation. To increase the number of interrupt stack pages, add a statement to the MODPARAMS.DAT file that increases the value of the INTSTKPAGES system parameter. 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 or alphanumeric 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 components. If a user-specified UIC is not in place from a pervious configuration, the octal number 3655 (the default UIC group number for service accounts) is used. If this is an initial product configuration but the procedure detects that number 3655 is in use, you are prompted for a new UIC group number when you run TCPIP$CONFIG. Before you assign a new group UIC, check that the number you chose is not already in use by entering the following commands: $ RUN SYS$SYSTEM:AUTHORIZE UAF> SHOW /BRIEF [your_group_number,*] UAF> SHOW /IDENTIFIER /VALUE=UIC:[your_group_number,*] 1-6 Preparing to Install and Configure TCP/IP Services Preparing to Install and Configure TCP/IP Services 1.2 Preinstallation Tasks To specify a new UIC group number, assign the value TRUE to the logical name TCPIP$ASK_GROUP_UIC. When you configure TCP/IP Services, TCPIP$CONFIG prompts you for the group UIC. 1.3 Assembling Configuration Information Use the worksheet in Table 1-2 to assemble configuration information. If you are configuring TCP/IP Services on the system for the first time, the TCPIP$CONFIG procedure prompts you for the information listed in Table 1-2. 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 DIGITAL TCP/IP Services for OpenVMS Management guide. Preparing to Install and Configure TCP/IP Services 1-7 Preparing to Install and Configure TCP/IP Services 1.3 Assembling Configuration Information Table_1-2_Configuration_Planning_Worksheet________________ Question__________________________________Answer__________ What is the system's host name (for ________________ example, MYNODE)? What is the system's Internet domain ________________ name (for example, widgets.com)? What are the system's addresses and masks? ________________ o IP address (for example, 19.112.139.14)________________ o Subnet (network mask) address (for example, 255.0.0.0) ________________ o Broadcast address (for example, 19.255.255.255) What is the system's network interface ________________ (for example, SE0)? What is the group UIC for TCP/IP ________________ Services (see Section 1.2.8)? For example, [GROUP1,JONES]. Do you want to grant nonprivileged ________________ users world READ access to the NFS proxy database (TCPIP$PROXY.DAT)? The NFS proxy database is a registry used to grant or deny access to your system and is shared by all OpenVMS cluster hosts running the TCP/IP Services product. To protect your system, set file protections to restrict access to the file itself. 1-8 Preparing to Install and Configure TCP/IP Services Preparing to Install and Configure TCP/IP Services 1.3 Assembling Configuration Information Table_1-2_(Cont.)_Configuration_Planning_Worksheet________ Question__________________________________Answer__________ Do you plan to enable SNMP? If yes: o Do you want to allow SNMP management clients to modify the MIBs by issuing ________________ Set requests? o Do you want to enable authentication ________________ traps when the master agent receives an SNMP request that specifies an unauthorized community string? ________________ o What is name of the system's contact person, and what is the location of ________________ the system (for example, Sam Spade; Falcon Building, Los Angeles, CA)? o Do you want to allow any network ________________ manager to remotely monitor your system? If so, you need to configure the "public" community name. o Do you want to provide additional community names and addresses (for implementing sets and traps)? 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-2_(Cont.)_Configuration_Planning_Worksheet________ Question__________________________________Answer__________ Which type of routing is appropriate for the network? ________________ o Static - For simple networks where routes do not change If static, what is the default gateway's host name and address (for ________________ example, GATWY1; 19.112.0.65)? ________________ o Dynamic - For complex networks where flexibility is required If dynamic, do you want to enable ROUTED or GATED routing? Do you plan to enable the BIND resolver? If yes: o What is the name of the BIND server ________________ you want the resolver to use (for example, MAINSV)? ________________ o What is the IP address of the BIND ________________ server (for example, 19.112.139.10)? o What is the domain name (for example, mainsv@widgets.com)? __________________________________________________________ 1-10 Preparing to Install and Configure TCP/IP Services 2 ________________________________________________________________ Installing TCP/IP Services This chapter explains how to install the DIGITAL TCP/IP Services for OpenVMS software as a layered product application 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 Upgrade and Installation Manual for OpenVMS Alpha. For information about the POLYCENTER Software Installation utility, refer to the OpenVMS System Manager's Manual: Essentials. 2.1 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 VAX or 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$MANAGER:SYSTARTUP_VMS.COM file and check to see if the command @SYS$STARTUP:UCX$STARTUP is defined. If defined, rename the file to TCPIP$STARTUP so that the new version of the product starts automatically when the system starts up. Installing TCP/IP Services 2-1 Installing TCP/IP Services 2.1 Installation Procedure 4. If a previous version of the software is installed on the system, shut it down. Enter: $ @SYS$MANAGER:UCX$SHUTDOWN Note: The shutdown procedure for TCP/IP Services Version 5.0 is SYS$STARTUP:TCPIP$SHUTDOWN.COM. 5. If you have DECnet configured on your system and you want to create a log of the installation procedure, enter the following command and then log in to the system account again: $ SET HOST 0/LOG=file-name where file-name is the name of the file to which you want the log written. 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=device-name where device-name is the directory path for the source drive that holds the TCP/IP Services kit. For example, /SOURCE=DKA1. 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. 7. The interactive installation procedure begins, and you are prompted for information. Example 2-1 shows a sample installation script on an OpenVMS Alpha system. Numbers identify the areas that require your response. The numbers are explained at the end of the script. The actual installation script that is displayed on your system might include additional questions and information, depending on your current configuration. 2-2 Installing TCP/IP Services Installing TCP/IP Services 2.1 Installation Procedure ________________________Note ________________________ To stop the installation at any time, press Ctrl/Y. The installation procedure deletes any files that were created, then exits. _____________________________________________________ Example 2-1 TCP/IP Services Installation: Sample POLYCENTER Software Installation Utility Procedure The following product has been selected: DEC AXPVMS TCPIP V5.0 Layered Product 1 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.0: DIGITAL TCP/IP Services for OpenVMS. (c) Compaq Computer Corporation 1999. All rights reserved. Compaq Computer Corporation DIGITAL TCP/IP Services for OpenVMS offers several license options. 2 Do you want the defaults for all options? [YES] 3 Do you want to review the options? [NO] YES DEC AXPVMS TCPIP V5.0: DIGITAL TCP/IP Services for OpenVMS. Applications: YES 4 Are you satisfied with these options? [YES] Execution phase starting ... The following product will be installed: DEC AXPVMS TCPIP V5.0 Layered Product Portion done: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90% Cont'd on next page Installing TCP/IP Services 2-3 Installing TCP/IP Services 2.1 Installation Procedure Example 2-1 (Cont.) TCP/IP Services Installation: Sample POLYCENTER Software Installation Utility Procedure Portion done: 100% The following product has been installed: DEC AXPVMS TCPIP V5.0 Layered Product 1 Press Return to continue with the installation procedure. 2 Answer YES to choose the POLYCENTER Software Installation utility defaults for the options or NO to choose other options. 3 Answer YES to review the POLYCENTER Software Installation utility options. 4 Press Return to accept the options as listed or answer NO to change the options. 8. After the installation completes, you can: - Read the DIGITAL TCP/IP Services for OpenVMS Release Notes on line or print the file from SYS$HELP:TCPIP050.RELEASE_NOTES. - Display a list of the TCP/IP Services files that were installed. Enter the following command: $ PRODUCT LIST TCPIP/VERSION=5.0 9. If you had a previous version of TCP/IP Services on your system: _____________________ 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 (Chapter 3). _____________________________________________________ 2-4 Installing TCP/IP Services Installing TCP/IP Services 2.1 Installation Procedure - Delete obsolete TCP/IP Services information from the OpenVMS Help file by running the TCPIP$CLEANUP_ HELPLIB.COM procedure and responding at the prompts. Enter: $ @SYS$UPDATE:TCPIP$CLEANUP_HELPLIB - Reboot your system for the new TCP/IP Services software to take effect. 10. Log out of the SYSTEM account. 11. Log back in to the SYSTEM account, and proceed to Chapter 3 to configure TCP/IP Services. Installing TCP/IP Services 2-5 3 ________________________________________________________________ Configuring TCP/IP Services After you install DIGITAL TCP/IP Services for OpenVMS, you need to enable (configure) the components and characteristics you require for your particular system using the menu-driven TCPIP$CONFIG procedure. This chapter explains the TCPIP$CONFIG menus, provides sample scripts, 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 the TCP/IP Services components and functionality. Table_3-1_Tasks:_Configuring_TCP/IP_Services______________ TaskAction___________________________________Go_to..._____ 1 Assemble system information to prepare Section 1.3 for running TCPIP$CONFIG. 2 Run TCPIP$CONFIG and answer prompts to Section 3.2 convert existing databases or create new ones. 3 Configure the major components and Section 3.2.4 functionality using TCPIP$CONFIG. 4 Configure the optional components using Section 3.2.5 TCPIP$CONFIG, as applicable. 5 Start TCP/IP Services. Section 3.4 6 Verify the configuration. Section 3.5 7 Reboot the system, then complete Section 3.6 additional configuration tasks, as ____appropriate.__________________________________________ Configuring TCP/IP Services 3-1 Configuring TCP/IP Services 3.2 Running TCPIP$CONFIG 3.2 Running TCPIP$CONFIG The TCPIP$CONFIG procedure displays menus from which you do the following: o Make selections that enable components for your system. o Start or stop TCP/IP Services software. o Verify the configuration. To get started, enter: $ @SYS$MANAGER:TCPIP$CONFIG 3.2.1 Converting Existing TCP/IP Services Configuration Files (Upgrade Only) If you have a TCP/IP Services configuration in place from a previous version of the product, the procedure begins by converting the existing configuration files to new configuration files unless you respond NO to the prompt Convert the old configuration files [Y]. The following sample script shows the start of the TCPIP$CONFIG procedure and a portion of the conversion of the previous configuration: TCP/IP Network Configuration Procedure This procedure helps you define the parameters required to run DIGITAL TCP/IP Services for OpenVMS on this system. 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... 3-2 Configuring TCP/IP Services Configuring TCP/IP Services 3.2 Running TCPIP$CONFIG 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, DIGITAL TCP/IP Services for OpenVMS configures LPD such that nonprivileged users cannot modify queue entries. Creating TCPIP$AUX identifier with a value of 3655 DIGITAL 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. . . . 3.2.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 script: Configuring TCP/IP Services 3-3 Configuring TCP/IP Services 3.2 Running TCPIP$CONFIG TCP/IP Network Configuration Procedure This procedure helps you define the parameters required to run DIGITAL 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 For security purposes, the Proxy Database is created with no world access. This denies nonprivileged users the use of commands that access the Proxy Database. Creating SYS$COMMON:[SYSEXE]TCPIP$PROXY.DAT * Do you want to grant world read access to nonprivileged users [NO]: Creating SYS$COMMON:[SYSEXE]TCPIP$CONFIGURATION.DAT DIGITAL 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. If you want to grant world access to the NFS proxy database, answer YES at the prompt. If not, press Return. 3.2.3 Understanding the Configuration Menus After the configuration files are converted or created, the main Configuration menu is displayed: DIGITAL TCP/IP Services for OpenVMS Configuration Menu Configuration options: 1 - Core environment 2 - Client components 3 - Server components 4 - Optional components 5 - Shut down DIGITAL TCP/IP Services for OpenVMS 6 - Start up DIGITAL TCP/IP Services for OpenVMS 7 - Run tests A - Configure options 1 - 3 [E] - Exit configuration procedure 3-4 Configuring TCP/IP Services Configuring TCP/IP Services 3.2 Running TCPIP$CONFIG Enter configuration option: The options are as follows: o Core Environment - Software associated with the Network, Internet, and Transport layers of the TCP/IP architecture o Client Components - Application software and related components o Server Components - Server software and related components o Optional Components o Shut down DIGITAL TCP/IP Services for OpenVMS o Start up DIGITAL TCP/IP Services for OpenVMS o Run Tests If you do not have experience with the TCP/IP Services product, you should use the configuration menus. However, if you have experience configuring the software and want to bypass the menus, you can add one or more command parameters when you run TCPIP$CONFIG. For information about the command parameters, see Section 3.3. 3.2.4 Configuring the Core Environment and the Client and Server Components From the main Configuration menu, enter option A to con- figure options 1 through 3. ________________________Note ________________________ The script examples in this section show the progression of the procedure when you choose to configure groups of components. Alternatively, you can configure one option at a time. _____________________________________________________ The Core environment menu is displayed first. Enter option A to configure options 1 through 5. You are required to configure the Domain, Routing, and Interfaces options; the BIND Resolver and Time Zone are optional. Configuring TCP/IP Services 3-5 Configuring TCP/IP Services 3.2 Running TCPIP$CONFIG DIGITAL TCP/IP Services for OpenVMS Core Environment Configuration Menu Configuration options: 1 - BIND Resolver 2 - Domain 3 - Routing 4 - Interfaces 5 - Time Zone A - Configure options 1 - 5 [E] - Exit menu Enter configuration option: A The following sample script reflects a new TCP/IP Services product installation. The script varies for systems that have an existing configuration in place. Enter your responses to the menu questions using the information from your configuration planning worksheet (Section 1.3). BIND RESOLVER Configuration A BIND resolver has not been configured. DIGITAL 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: MAINSV MAINSV is not in the local host database. Enter Internet address for MAINSV: 19.112.139.14 3-6 Configuring TCP/IP Services Configuring TCP/IP Services 3.2 Running TCPIP$CONFIG You must provide the domain name in order to run the BIND resolver. This information should be available from your Internet network administrator. DOMAIN Configuration Enter Internet domain: widgets.com INTERFACE Configuration The Ethernet device(s) on your system are: ESA0: * Not Configured. * Start of configuration questions for Internet interface SE0. SE0 is the Ethernet device ESA0: SE0 has not been configured. * Do you want to configure SE0 [YES]: Enter unqualified host name: WIDGTS Host WIDGTS exists in the database. Enter Internet address [19.112.139.15]: Enter Internet network mask for widgts [225.255.0.0]: Enter broadcast mask for widgts [19.225.225.225]: The following parameters will be used to define the Internet Interface SE0: Host name: widgets.com Internet address: 19.112.139.15 Network mask: 255.255.0.0 Broadcast mask: 19.225.225.225 * Is the above correct [YES]: End of configuration questions for Internet interface SE0. DYNAMIC ROUTING Configuration You can configure dynamic ROUTED or GATED routing. However, 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. Configuring TCP/IP Services 3-7 Configuring TCP/IP Services 3.2 Running TCPIP$CONFIG 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]: TIME ZONE Configuration TCPIP uses time zone information provided by the OpenVMS Operating System. No additional time zone configuration is needed for TCPIP when the operating system is configured correctly. This section verifies the current OpenVMS time zone 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, time zone information verified Press Return to continue ... After you configure options 1 through 5, the procedure returns to the Core Environment menu. Enter option E to exit. The Client Components menu is displayed. 3-8 Configuring TCP/IP Services Configuring TCP/IP Services 3.2 Running TCPIP$CONFIG Note that the menus in the following sample scripts show each component disabled (default). In fact, the procedure might show some of the components as enabled based on your past configuration or the selections you made from the Core Environment menu. DIGITAL TCP/IP Services for OpenVMS Client Components Configuration Menu Configuration options: 1 - FTP Disabled 2 - LPR/LPD Disabled 3 - NFS Client Disabled 4 - REXEC and RSH Disabled 5 - RLOGIN Disabled 6 - SMTP Disabled 7 - TELNET Disabled A - Configure options 1 - 7 [E] - Exit menu Enter configuration option: A Enable the client components you plan to use, or enter option A to configure options 1 through 7. The following FTP client script is an example of the display for each client component: FTP CLIENT Configuration Service is not enabled. FTP CLIENT configuration options: 1 - Enable 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] ? Configuring TCP/IP Services 3-9 Configuring TCP/IP Services 3.2 Running TCPIP$CONFIG After you configure the client components (and their related server components, if applicable), the Server Components menu is displayed: DIGITAL TCP/IP Services for OpenVMS Server Components Configuration Menu Configuration options: 1 - BIND Disabled 2 - BOOTP Disabled 3 - TFTP Disabled 4 - FTP Disabled 5 - LPR/LPD Disabled 6 - NFS Disabled 7 - PC-NFS Disabled 8 - PORTMAPPER Disabled 9 - TELNET/RLOGIN Disabled 10 - SNMP Disabled 11 - NTP Disabled 12 - METRIC Disabled 13 - POP Disabled 14 - FINGER Disabled 15 - RMT Disabled 16 - LBROKER Disabled 17 - DHCP Disabled A - Configure options 1 - 17 [E] - Exit menu Enter configuration option: A Enable the server components you plan to use, or enter option A to configure options 1 through 17. The following BIND server configuration script is an example of a display for server components, although some components prompt you for additional information. BIND SERVER Configuration Service is not defined in the SYSUAF. Service is not defined in the TCPIP$SERVICE database. Service is not enabled. BIND SERVER configuration options: 1 - Enable service on this node 3-10 Configuring TCP/IP Services Configuring TCP/IP Services 3.2 Running TCPIP$CONFIG [E] - Exit BIND configuration Enter configuration option: 1 The TCPIP$AUX identifier already exists with value 3655. Checking for BIND template files in SYS$SPECIFIC:[TCPIP$BIND] Creating template SYS$SPECIFIC:[TCPIP$BIND]TCPIP$BIND_CONF.TEMPLATE Creating file SYS$SPECIFIC:[TCPIP$BIND]127_0_0.DB Creating file SYS$SPECIFIC:[TCPIP$BIND]ROOT.HINT After you configure the server components, press Return to go to the main Configuration menu. Enter option 4, Optional Components. 3.2.5 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 PATHWORKS or DECnet over TCP/IP. o Run or develop applications that use the Stanford Research Institute's (SRI) QIO application programming interface (API). o Allow Anonymous FTP access. When you enter option 4 from the Main Configuration menu, the Optional Components menu displays the following menu options: DIGITAL 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 A - Configure options 1 - 3 [E] - Exit menu Enter the options that are appropriate for your system: the PWIP driver, the SRI QIO interface, or Anonymous FTP accounts or directories. o If you want to run PATHWORKS or DECnet over TCP/IP, configure the PWIP driver by entering option 1. Configuring TCP/IP Services 3-11 Configuring TCP/IP Services 3.2 Running TCPIP$CONFIG o If you run or develop applications that use the SRI QIO API, enter option 2. Alternatively, you can load the interface by entering the following command: $ @SYS$MANAGER:TCPIP$LOAD_INETDRIVER o If you want to allow Anonymous FTP access, enter 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. 3.3 Using TCPIP$CONFIG Option Commands 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 command procedure and include appropriate options and keywords in the command line: $ @SYS$MANAGER:TCPIP$CONFIG [option] {DISABLE | ENABLE} [CLUSTER] The options and keywords are: 3-12 Configuring TCP/IP Services Configuring TCP/IP Services 3.3 Using TCPIP$CONFIG Option Commands ALL Configures the core environment and all client and server components. CLUSTER Configures all specified components clusterwide (except for the BIND server and SMTP, which you cannot configure clusterwide). CLIENT Configures all client components and related software. ENABLE Enables the specified components. DISABLE Disables the specified components. MINIMUM Configures the domain, Internet interfaces, remote login, FTP client, FTP server, TELNET client, and TELNET server. SERVER Configures all server components 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. For example, the following command enables the client components for the entire cluster: $ @SYS$MANAGER:TCPIP$CONFIG CLIENT ENABLE CLUSTER ________________________Note ________________________ The procedure implements two levels of enabling and disabling: clusterwide and single node (except for the BIND server and SMTP, which are configured and enabled as node-specific only). _____________________________________________________ Configuring TCP/IP Services 3-13 Configuring TCP/IP Services 3.4 Starting TCP/IP Services 3.4 Starting TCP/IP Services You must start TCP/IP Services after you configure the standard software and optional components, but before you run tests or customize the environment. Start TCP/IP Services on your system as follows: 1. Access the main Configuration menu: $ @SYS$MANAGER:TCPIP$CONFIG 2. Enter option 6 (Startup DIGITAL TCP/IP Services for OpenVMS). 3.5 Verifying the Configuration You can verify the configuration by running the installa- tion verification procedure (IVP). You should run the IVP if 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. Before you run the IVP, make sure TCP/IP Services has started and you have SYSPRV, OPER, NETMBX, and TMPMBX privileges. Run the IVP as follows: 1. Run the command procedure: $ @SYS$MANAGER:TCPIP$CONFIG 3-14 Configuring TCP/IP Services Configuring TCP/IP Services 3.5 Verifying the Configuration 2. Enter option 7 (Run tests), and then enter option 1 (Internet IVP) from the Test menu. 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-2 lists some common problems that cause IVP error messages. If the recommended action does not correct the problem, contact your Compaq support representative. Table_3-2_Troubleshooting_IVP_Errors______________________ Problem_________________Corrective_Action_________________ 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.) Shut down and restart TCP/IP Services. The installation kit Request a replacement kit. is defective. The IVP fails because Register a DIGITAL TCP/IP Services the_PAK_is_missing._____for_OpenVMS_PAK.__________________ 3. To run the IVP any time after exiting the configuration procedure, run the IVP command procedure as follows: $ @SYS$TEST:TCPIP$IVP 3.6 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. Configuring TCP/IP Services 3-15 Configuring TCP/IP Services 3.6 Additional Configuration Tasks The additional configuration tasks include: o Populating databases (for example, for BIND and DHCP) o Setting up user accounts 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 For information about these and other configuration tasks, see the DIGITAL TCP/IP Services for OpenVMS Management guide. 3.7 Automatically Starting and Stopping TCP/IP Services To allow TCP/IP Services software to start automat- ically when the system starts up and to stop au- tomatically when the system shuts down, edit the SYS$COMMON[SYSMGR]:SYSTARTUP_VMS.COM file and include the following commands: @SYS$STARTUP:TCPIP$STARTUP @SYS$STARTUP:TCPIP$SHUTDOWN Because the UCX$STARTUP.COM and UCX$SHUTDOWN.COM files are no longer applicable, delete any definition of them from SYS$COMMON[SYSMGR]:SYSTARTUP_VMS.COM. For 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: $ DIRECTORY SYS$MANAGER:SYLOGIN.COM /PROTECTION If the protections are not W:RE, enter: $ SET PROTECTION=(W:RE) SYS$MANAGER:SYLOGIN.COM 3-16 Configuring TCP/IP Services Configuring TCP/IP Services Specifying TCP/IP Services as the Transport for DECwindows Applications 3.8 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 the following line to SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM: $ 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 Configuring TCP/IP Services 3-17 ________________________________________________________________ Index A__________________________ D__________________________ Anonymous FTP DECnet over TCP/IP configuring to use, 3-11 configuring to use, 3-11 DECwindows C__________________________ defining TCP transport, CD-ROM distribution kit 3-17 inspecting, 1-2 requirements for product Configuration worksheet, installation, 1-3 1-7 Disk Configuring TCP/IP Services space requirements, 1-4 client components, 3-8 system, backing up, 1-3 converting your existing Distribution kit configuration, 3-2 inspecting, 1-2 core environment, 3-5 to 3-8 G__________________________ description of major Global pagelets and tasks, 1-1 sections optional components, 3-11 increasing, 1-5 server components, 3-10, requirements, 1-5 3-11 tasks, recommended order I__________________________ of, 3-1 Installing TCP/IP Services, TCPIP$CONFIG menus, 2-1 to 2-5 description, 3-4 description of major time required, 1-1 tasks, 1-1 using TCPIP$CONFIG menus, listing the installed 3-5 files, 2-4 using TCPIP$CONFIG option time required, 1-1 commands, 3-12 verifying services, 3-14 Index-1 IVP (Installation Verification Procedure) P__________________________ description, 3-14 PAK registering, 1-3 L__________________________ PATHWORKS License Product configuring, 3-11 Authorization Key PWIP Driver See PAK requirements for installation, 1-3 M requirement, interrupt ___________________________ stack pages, 1-6 Magnetic tape distribution POLYCENTER Software kit Installation utility inspecting, 1-2 for installing or Memory upgrading (OpenVMS physical memory VAX or Alpha), 2-1 to requirements, 1-4 2-5 Menus understanding the R TCPIP$CONFIG menus, ___________________________ 3-4 Release notes extracting into a .TXT N__________________________ file, 1-2 Nonpaged dynamic pool location after increasing, 1-5 installation, 2-4 O S__________________________ ___________________________ SRI QIO OpenVMS License Management configuring to use, 3-11 Facility (LMF) System parameters using to register PAK, checking and changing 1-3 before installing, 1-5 OpenVMS operating system to 1-6 upgrading, 1-3 Optional components T Anonymous FTP, 3-11 ___________________________ PATHWORKS, 3-11 Tasks SRI QIO interface, 3-11 major, installing and configuring, 1-1 TCP/IP Services and Anonymous FTP access, 3-12 configuration, 3-1 to 3-15 Index-2 TCP/IP Services (cont'd) configuration procedure installation, 2-1 to 2-5 problems, 3-15 postconfiguration tasks, 3-15 U__________________________ preparing to configure, UIC codes 1-7 assigning, 1-6 preparing to install, 1-2 Upgrading TCP/IP Services, to 1-7 2-1 to 2-5 starting and stopping User access automatically, 3-16 configuring to allow upgrading, 2-1 to 2-5 Anonymous FTP access, verifying, 3-14 3-11 TCPIP$CONFIG menus description, 3-4 V__________________________ TK50 distribution kit Verifying the TCP/IP inspecting, 1-2 Troubleshooting Services configuration, 3-14 Index-3