DECnet-Plus_for_OpenVMS_____________________________ Applications Installation and Advanced Configuration Order Number: AA-QPSVB-TE November 1996 This book explains how to install and configure the layered application products on the DECnet-Plus for OpenVMS software. Revision/Update Information: This is a revised manual. Operating Systems: OpenVMS Alpha Version 7.1 OpenVMS VAX Version 7.1 Software Versions: DECnet-Plus for OpenVMS Version 7.1 X.25 for OpenVMS Alpha Version 7.1 Digital Equipment Corporation Maynard, Massachusetts ________________________________________________________________ November 1996 Digital Equipment 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 DIGITAL or an authorized sublicensor. DIGITAL conducts its business in a manner that conserves the environment and protects the safety and health of its employees, customers, and the community. © Digital Equipment Corporation 1996. All rights reserved. The following are trademarks of Digital Equipment Corporation: Bookreader, DDCMP, DEC, DECdirect, DECnet, DECNIS, DECserver, DECsystem, DECwindows, DIGITAL, DNA, InfoServer, OpenVMS, PATHWORKS, ULTRIX, VAX, VAX DOCUMENT, VAXcluster, VAXstation, VMS, VMScluster, and the DIGITAL logo. The following are third party trademarks: Macintosh is a registered trademark of Apple Computer, Inc. MS-DOS is a registered trademark of Microsoft Corporation. Multinet is a registered trademark of TGV, Inc. OS/2 is a registered trademark of International Business Machines Corporation. OSF/1 is a registered trademark of Open Software Foundation, Inc. PATHways is a registered trademark of The Wollongong Group. SCO is a trademark of Santa Cruz Operations, Inc. TCPware is a registered trademark of Process Software Corporation. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Co. Ltd. All other trademarks and registered trademarks are the property of their respective holders. 0 -3 _________________________________________________________________ Contents Preface................................................... xi Part I ADVANCED Configuration for DECnet-Plus for OpenVMS 1 Using the ADVANCED Configuration Option 1.1 Invoking the ADVANCED Configuration Option.... 1-1 1.2 Directory Name Services....................... 1-4 1.2.1 Node Full Name............................ 1-5 1.2.2 Node Synonym.............................. 1-6 1.2.3 Naming Cache Timeout Value................ 1-6 1.2.4 Session Control Address Update Interval... 1-7 1.2.5 Naming Cache Checkpoint Interval.......... 1-7 1.2.6 Specifying the Node Type.................. 1-7 1.2.7 Configuring Time Zone Differential Factors................................... 1-7 1.2.8 Specifying Routing Information............ 1-8 1.2.9 Specifying a Phase IV-Compatible Address................................... 1-8 1.2.10 Specifying a Phase IV Prefix.............. 1-9 1.2.11 Specifying End Node Information........... 1-9 1.2.11.1 Configuring Network Addresses........... 1-9 1.2.11.2 DNA Address Format...................... 1-11 1.2.11.3 Segregated Mode Routing and Integrated Mode Routing............................ 1-11 1.2.11.4 ESHello Timer........................... 1-13 1.3 Configuring Devices........................... 1-13 1.3.1 Configuring Asynchronous Connections...... 1-13 v 1.3.2 Configuring Data Links and Routing Circuits.................................. 1-14 1.3.2.1 Specifying Circuit Cost and Routing Priority................................ 1-14 1.3.3 Enabling Phase IV Addressing on Routing Circuits.................................. 1-14 1.3.4 FDDI Large Packet Support................. 1-14 1.3.5 Configuring an Alpha System............... 1-15 1.3.6 Configuring a VAX System.................. 1-19 1.4 Configuring the Network Service Protocol (NSP) Transport .................................... 1-21 1.5 Configuring the OSI Transport................. 1-22 1.5.1 Congestion Avoidance...................... 1-24 1.5.2 Setting Up the OSI Loopback Test Application Account....................... 1-25 1.5.3 Creating Additional OSI Templates......... 1-25 1.5.3.1 CLNS Network Service.................... 1-26 1.5.3.2 CONS Network Service.................... 1-27 1.5.3.3 RFC 1006 Network Service................ 1-28 1.6 Configuring an Event Dispatcher .............. 1-29 1.7 Configuring an Application Database........... 1-29 1.8 Configuring a Cluster Alias .................. 1-30 1.9 Configuration Summary and Network Startup..... 1-32 2 Managing Name Services 2.1 Names Services Overview....................... 2-1 2.1.1 The Local Namespace ...................... 2-1 2.1.1.1 Creating a Local Namespace.............. 2-2 2.1.1.2 Managing the Local Namespace............ 2-2 2.1.2 The DIGITAL Distributed Name Service (DECdns).................................. 2-2 2.1.2.1 Creating a New Namespace................ 2-3 2.1.2.2 Creating a DECdns Namespace............. 2-4 2.1.3 Domain Name System........................ 2-7 2.1.4 Namespace Management...................... 2-8 2.2 Name Service Search Path...................... 2-8 2.2.1 Configuring the Search Path Information... 2-9 2.2.1.1 Naming Search Path in a Cluster......... 2-10 2.2.2 Displaying the Search Path Information.... 2-10 2.2.3 Modifying the Search Path Information..... 2-10 2.2.4 Creating a Site-Specific Search Path NCL Script.................................... 2-11 vi 2.2.5 Using the Search Path to Ease Migration... 2-12 2.2.6 Setting Up Naming Templates............... 2-12 2.3 Domain Synonyms............................... 2-13 2.3.1 Search Path Naming Template Support for Domain Synonyms........................... 2-14 2.3.2 Local Aliases............................. 2-14 2.4 Node Synonym Directories...................... 2-15 2.4.1 Defining an Alternate Node Synonym Directory................................. 2-15 2.4.2 When to Use the Logical Name.............. 2-15 2.5 Using a DNS Version 1 Namespace with DECdns Version 2..................................... 2-16 2.5.1 Preparing a DNS Version 1 Namespace for Use by DECdns Version 2................... 2-17 2.5.2 Using the DNS Version 1 Namespace......... 2-18 2.6 Registering a Node in the Namespace........... 2-19 2.6.1 Export/Import File Format................. 2-19 2.6.2 Problems Registering a Node............... 2-19 3 Modifying a Current Configuration 3.1 Steps for Changing the Configuration.......... 3-1 3.2 Steps for Changing a Current Configuration.... 3-3 3.3 Changing an Entire Configuration.............. 3-6 3.4 Changing the Node Name/Namespace Name......... 3-7 3.4.1 Changing Directory Name Services.......... 3-7 3.4.2 Changing Node Name or Namespace........... 3-8 3.4.3 Changing Node Synonym..................... 3-8 3.4.4 Configuring a DECdns Clerk System to Use a WAN DECdns Server......................... 3-10 3.4.5 Configuring a DECdns Server System in an Existing Namespace........................ 3-12 3.4.5.1 Configuring a DECdns Server in a DNS Version 1 Namespace..................... 3-12 3.5 Reconfiguring Devices......................... 3-13 3.6 Reconfiguring the NSP and OSI transports...... 3-14 3.7 Reconfiguring the Time Zone Differential Factor (DECdts)............................... 3-20 3.7.1 Selecting the DECdts Configuration Option.................................... 3-20 vii 3.7.2 Configuring Your System's Local Time...... 3-21 3.7.2.1 Configuring Your System's Local Time Using Menus (Menu Option 1)............. 3-22 3.7.2.2 Configuring Your System's Local Time as UTC (Menu Option 2)..................... 3-25 3.7.2.3 Customizing Your System's Time Zone Rule (Menu Option 3)......................... 3-26 3.8 Reconfiguring the Event Dispatcher............ 3-33 3.9 Reconfiguring the Application Database........ 3-39 3.10 Reconfiguring the MOP Client Database......... 3-44 3.11 Reconfiguring Event, MOP Client, Application Entities, and the Naming Search Path.......... 3-47 3.12 Reconfiguring the Cluster Alias............... 3-48 3.12.1 Specifying an Address..................... 3-49 3.12.2 Determining Selection Weight.............. 3-50 3.13 Replace MOP Client Configuration.............. 3-50 3.14 Configuring Satellite Nodes................... 3-51 3.15 Configuring Cluster Script Locations.......... 3-54 3.16 Completing Configuration Changes.............. 3-57 Part II Configuring VAX P.S.I. and VAX P.S.I. Access for OpenVMS VAX Systems 4 Configuring VAX P.S.I. and VAX P.S.I. Access 4.1 Steps in Configuring VAX P.S.I................ 4-1 4.2 Planning Your VAX P.S.I. Configuration........ 4-1 4.2.1 Configuring Access, Native, and Multihost Systems................................... 4-1 4.2.2 The VAX P.S.I. Configuration Program...... 4-4 4.2.3 Sections in the VAX P.S.I. Configuration Program................................... 4-6 4.3 Recording the Information You Need for VAX P.S.I. Configuration.......................... 4-10 4.4 Running the VAX P.S.I. Configuration Program....................................... 4-33 4.4.1 Starting the VAX P.S.I. Configuration Program................................... 4-33 4.4.2 Using the VAX P.S.I. Configuration Program................................... 4-34 4.4.2.1 Entering Information.................... 4-34 4.4.2.2 Moving Within a Section................. 4-35 4.4.3 Options Menu.............................. 4-35 viii 4.4.4 Creating NCL Script....................... 4-37 4.4.5 Exiting the Program....................... 4-37 4.4.6 Requirement to Complete VAX P.S.I. Configuration ............................ 4-38 4.4.7 Getting Help.............................. 4-38 4.4.7.1 Getting Help on a Specific Field or Menu Choice.................................. 4-38 4.4.7.2 Getting General Help.................... 4-38 4.4.7.3 Getting Help on the Program............. 4-39 4.5 Testing VAX P.S.I............................. 4-39 4.5.1 Preparing to Run the CTP.................. 4-40 4.5.2 Running the CTP........................... 4-41 4.5.2.1 Running the CTP Interactively........... 4-41 4.5.2.2 Running the CTP as a Network Object..... 4-41 4.6 Changing Your VAX P.S.I. Configuration........ 4-42 4.7 Creating a New VAX P.S.I. Configuration ...... 4-42 Part III Installing and Configuring X.25 for OpenVMS Alpha Systems 5 Planning to Install X.25 for OpenVMS Alpha 5.1 Product Description........................... 5-1 5.2 Required Hardware............................. 5-1 5.3 Required Software............................. 5-2 5.4 Kit Location.................................. 5-2 5.5 Time Required to Install...................... 5-3 6 Preparing to Install X.25 for OpenVMS Alpha 6.1 Inspecting the Distribution Kit............... 6-1 6.2 Logging In to a Privileged Account............ 6-1 6.3 Accessing the Online Release Notes............ 6-2 6.4 Determining Process Account Quotas............ 6-3 6.5 Determining Disk Space........................ 6-4 ix 7 Installing X.25 for OpenVMS Alpha 7.1 Registering the X.25 Software License......... 7-1 7.2 Installing X.25 Using the DCL Interface....... 7-4 7.3 Files Installed on Your System................ 7-4 7.4 X.25 Installation and De-Installation Sample........................................ 7-4 7.4.1 X.25 Installation Example................. 7-5 7.4.2 X.25 De-Installation Example.............. 7-7 8 X.25 Post-Installation and Configuration Tasks 8.1 Configuring X.25.............................. 8-1 8.2 Restart DECnet-Plus........................... 8-2 8.3 Rebooting the System.......................... 8-3 8.4 De-installing X.25............................ 8-3 8.5 Sample X.25 Configuration .................... 8-4 Part IV Installing OSI Applications for OpenVMS Systems 9 Planning for the Installation 9.1 Product Descriptions.......................... 9-1 9.2 Required Hardware............................. 9-2 9.3 Required Software............................. 9-2 9.4 Kit Location.................................. 9-2 9.5 Time Required to Install...................... 9-3 10 Preparing to Install the OSI Applications 10.1 Inspecting the Distribution Kit............... 10-1 10.2 Logging In to a Privileged Account............ 10-1 10.3 Accessing the Online Release Notes............ 10-2 10.4 Memory Requirements........................... 10-3 10.4.1 Changing System Parameter Values with AUTOGEN................................... 10-4 10.5 Process Quotas................................ 10-4 10.6 Determining Disk Space........................ 10-6 10.7 Notifying Users............................... 10-7 x 11 Installing the OSI Applications 11.1 Prerequisite Steps............................ 11-1 11.2 Register the OSI Applications Software License....................................... 11-1 11.3 Starting the Installation of the OSI Applications.................................. 11-2 11.4 Installing the OSI Applications............... 11-2 11.5 Starting Up and Shutting Down OSI Applications.................................. 11-6 11.6 The OSAK Installation Verification Procedure..................................... 11-6 11.7 Running the OSIF$CONFIGURE.COM Procedure...... 11-7 11.8 The FTAM Installation Verification Procedure..................................... 11-8 11.8.1 Preparing for the FTAM IVP................ 11-8 11.8.2 Running the FTAM IVP...................... 11-9 11.9 The VT Installation Verification Procedure.... 11-11 11.10 De-installing OSI Applications................ 11-11 11.11 Files Installed on Your System................ 11-12 11.12 Sample OSI Application Installations.......... 11-12 11.12.1 Sample OSAK Installation.................. 11-13 11.12.2 Sample Virtual Terminal Installation...... 11-14 11.12.3 Sample FTAM Installation.................. 11-15 11.13 Sample OSI Application De-installations....... 11-16 11.13.1 Sample Virtual Terminal De-installation... 11-16 11.13.2 Sample FTAM De-installation............... 11-17 11.13.3 Sample OSAK De-installation............... 11-18 12 Configuring the OSI Applications 12.1 FTAM and Virtual Terminal Terminology......... 12-1 12.2 About the OSI Application Entity Database..... 12-1 12.3 Getting Started Configuring Initiating and Responding Entities........................... 12-2 12.3.1 Setting Up Responding Entities............ 12-2 12.3.2 Setting Up Initiating Entities............ 12-2 12.3.3 Example: Performing An FTAM File Copy..... 12-4 12.3.4 Example: Performing A Virtual Terminal Login..................................... 12-5 12.4 About Responding Entities..................... 12-6 12.5 Configuring Addresses for Remote FTAM and VT Applications.................................. 12-7 12.5.1 Adding Address Format Entries............. 12-12 xi 12.5.2 Adding Distinguished Name Format Entries................................... 12-12 12.5.3 Adding Pattern Format Entries............. 12-12 12.6 Registering Responders To X.500 Directory..... 12-13 Part V Appendixes A Configuring Asynchronous Connections A.1 Asynchronous DECnet Connections............... A-1 A.1.1 Establishing a Static Asynchronous Connection................................ A-5 A.1.1.1 Terminating a Static Asynchronous Connection.............................. A-8 A.1.1.2 Reasons for Failure of Static Asynchronous Connections................ A-9 A.1.2 Establishing a Dynamic Asynchronous Connection................................ A-10 A.1.2.1 Setting Up Dynamic Asynchronous Connections............................. A-11 A.1.2.2 Switching on Dynamic Asynchronous Connections............................. A-15 A.1.2.3 Managing Dynamic Asynchronous Resources............................... A-19 A.1.2.4 Terminating a Dynamic Asynchronous Connection.............................. A-19 A.1.2.5 Reasons for Failure of Dynamic Asynchronous Connections................ A-20 B Configuring Transports B.1 Overview...................................... B-1 B.2 Manually Configuring NSP...................... B-1 B.2.1 Transmit and Receive Window............... B-3 B.3 Manually Configuring the OSI Transport Service....................................... B-3 B.3.1 Transmit and Receive Window............... B-5 xii B.3.2 Configuring the Connection-Oriented Network Service........................... B-6 B.3.2.1 Establishing Outbound Connections Using CONS.................................... B-7 B.3.2.2 Establishing Inbound Connections Using CONS.................................... B-7 B.3.2.3 Manually Configuring Support for CONS... B-8 B.3.3 Manually Configuring the Connectionless-Mode Network Service....... B-13 B.3.3.1 Establishing Outbound Connections Using CLNS.................................... B-13 B.3.3.2 Establishing Inbound Connections Using CLNS.................................... B-14 B.3.3.3 Steps for Configuring CLNS.............. B-14 B.3.3.4 Providing Communications Between OSI Transport Systems and VOTS Systems Using CLNS.................................... B-21 B.4 Manually Configuring OSI Transport Network Applications.................................. B-22 B.4.1 Customizing End Selector for OSI Transport................................. B-24 B.4.2 Enabling Use of CLNS Error Reports........ B-24 B.5 Using DECnet over TCP/IP (RFC 1859) and OSI over TCP/IP (RFC 1006)........................ B-24 B.5.1 Configuring RFC 1006 and/or RFC 1859...... B-25 B.5.2 Creating Additional OSI Transport Templates for RFC 1006 and RFC 1859....... B-26 B.5.3 Disabling DECnet-Plus over TCP/IP......... B-26 Index Figures 4-1 Installation and Configuration Flowchart................................. 4-3 7-1 Installation and Configuration Flowchart................................. 7-3 A-1 Dynamic Switching of Asynchronous DDCMP Lines..................................... A-15 xiii Tables 3-1 Choosing Your Configuration Option........ 3-2 3-2 Time Zone Rules........................... 3-29 3-3 Object Type Numbers....................... 3-41 4-1 VAX P.S.I. Configurations and License Requirements.............................. 4-4 4-2 VAX P.S.I. Configuration Sections Required for Access, Native and Multihost Systems................................... 4-5 4-3 VAX P.S.I. Configuration Information: Lines and DTEs (Native and Multihost Systems Only)............................. 4-11 4-4 VAX P.S.I. Configuration Information: PVCs (Native and Multihost Systems Only)....... 4-13 4-5 VAX P.S.I. Configuration Information: Groups (Native and Multihost Systems Only)..................................... 4-15 4-6 VAX P.S.I. Configuration Information: LLC2 (Native and Multihost Systems Only)....... 4-16 4-7 VAX P.S.I. Configuration Information: Remote DTE Classes (Access Systems Only)..................................... 4-17 4-8 VAX P.S.I. Configuration Information: X.29 and P.S.I. Mail Support (All Systems) .... 4-18 4-9 VAX P.S.I. Configuration Information: Gateway Client Nodes (Multihost Systems Only)..................................... 4-19 4-10 VAX P.S.I. Configuration Information: Applications (All Systems)................ 4-19 4-11 VAX P.S.I. Configuration Information: Declaring a Network Process (All Systems).................................. 4-20 4-12 VAX P.S.I. Configuration Information: Filters-for Applications and Network Processes (All Systems) and gateway clients (Multihost Systems Only) ......... 4-21 4-13 VAX P.S.I. Configuration Information: Templates (All Systems) .................. 4-23 xiv 4-14 VAX P.S.I. Configuration Information: Incoming Security for Applications (All Systems).................................. 4-26 4-15 VAX P.S.I. Configuration Information: Outgoing Security for Local Processes (All Systems).................................. 4-28 4-16 VAX P.S.I. Configuration Information: Incoming Security for Network Processes (All Systems)............................. 4-30 4-17 VAX P.S.I. Configuration Information: Incoming Security for Gateway Clients (Multihost Systems Only) ................. 4-31 4-18 VAX P.S.I. Configuration Information: Outgoing Security for Client Systems (Multihost Systems Only) ................. 4-32 6-1 Process Quotas for the Installing Account................................... 6-3 10-1 Required Global Pages, Global Pagelets and Sections.................................. 10-3 10-2 Process Quotas for the Installing Account................................... 10-4 10-3 OSAK$SERVER_V3 Process Account Quotas..... 10-5 10-4 Account Quotas for Processes that use OSAK Software.................................. 10-5 10-5 Minimum Disk Space Requirements........... 10-7 12-1 Default Addresses......................... 12-7 12-2 X.500 Configuration Checklist............. 12-9 12-3 Address Format Worksheet.................. 12-11 B-1 Additional Routing Circuit Characteristics for CLNS.................................. B-19 xv _________________________________________________________________ Preface This is the second book you should read in order to successfully install and configure: o X.25 for OpenVMS Alpha o VAX P.S.I. and VAX P.S.I. Access for OpenVMS VAX o OSI layered software applications - File Transfer, Access, and Management (FTAM) - Virtual Terminal (VT) - OSI Applications Kernel (OSAK) It also describes how to configure DECnet-Plus for OpenVMS using the ADVANCED configuration option and information about name services. ________________________ Note ________________________ This book assumes you have already installed DECnet- Plus which is a prerequisite for installing the applications discussed in this book. Refer to (DNPLUS_OVMS_INSTALL_BASIC) for information on installing DECnet-Plus. ______________________________________________________ Intended Audience This book is written for: o Network planners and managers o OpenVMS system managers o DECnet-Plus software installers xi Structure of This Book This book has five parts: Part I Describes how to run an ADVANCED configuration for DECnet-Plus for OpenVMS, as well as steps to change a current configuration. Part Describes how to configure VAX P.S.I. and VAX II P.S.I. Access for a DECnet-Plus for OpenVMS VAX system. Part Describes the pre-installation, installation, and III configuration steps necessary to install X.25 for a DECnet-Plus for OpenVMS Alpha system. Part Describes the pre-installation, installation, and IV configuration steps necessary to install the OSI applications: FTAM, VT, and OSAK. Part V Describes how to configure asynchronous connections and transports. Terminology The following terms are used interchangeably in this book. o Alpha and AXP o Transition and migration o Phase IV and DECnet Phase IV o End system and end node o Intermediate system and router o DECnet-Plus and Phase V Related Documents The following books provide additional information. o (DNPLUS_OVMS_INSTALL_BASIC) The first book to read in order to successfully install DECnet-Plus for OpenVMS. It also includes how to configure DECnet-Plus using the BASIC configuration and information about name services. o (DNPLUS_OVMS_USER) xii Introduces the DECnet-Plus for OpenVMS features and tools, and how to use and manage a DECnet-Plus for OpenVMS end system. Also provides a comprehensive glossary of DECnet-Plus terminology. o (DNPLUS_PLANNING) Explains in detail the transition from DECnet Phase IV to DECnet-Plus, providing configuration guidelines and planning tasks. o (DNPLUS_DNS_MGMT) o (DNPLUS_DTS_MGMT) o (DNPLUS_OVMS_NET_MGMT) o X.25 for OpenVMS Configuration Guide o (DNPLUS_FTAM_VT_MGMT) o OpenVMS License Management Utility Manual o OpenVMS System Management Utilities For additional information on the DECnet-Plus products and services, access the DIGITAL OpenVMS World Wide Web site. Use the following URL: http://www.openvms.digital.com Reader's Comments DIGITAL welcomes your comments on this manual or any of the DECnet-Plus documents. Send us your comments through any of the following channels: Internet openvmsdoc@zko.mts.dec.com Fax 603 881-0120, Attention: OSSG Documentation, ZKO3-4/U08 Mail OSSG Documentation Group, ZKO3-4/U08 110 Spit Brook Rd. Nashua, NH 03062-2698 xiii How To Order Additional Documentation Use the following table to order additional documentation or information. If you need help deciding which documentation best meets your needs, call 800-DIGITAL (800-344-4825). xiv Conventions The following conventions are used in this book. ___________________________________________________________ Convention_______Meaning___________________________________ special type Indicates a literal example of system output or user input. In text, indicates command names, keywords, node names, file names, directories, utilities and tools. UPPERCASE Indicates keywords that you enter. You can type the characters in uppercase or lowercase. You can abbreviate command keywords to the smallest number of characters that OpenVMS, NCP, NCL, or the other tools accept. Uppercase also indicates the names of files, directories, utilities, tools, commands, parameters, and procedures. italic type Indicates a variable. bold Indicates a new term defined in the text or important information. Indicates that you press the Return key. Ctrl/x Indicates that you press the Control key while you press the key noted by x. [YES] Brackets indicate that the enclosed item is a default value in an installation prompt. { } In command format descriptions, indicates you must enter at least one listed _________________element.__________________________________ xv Part I _________________________________________________________________ ADVANCED Configuration for DECnet-Plus for OpenVMS Part I describes the steps necessary to use the ADVANCED configuration option for DECnet-Plus for OpenVMS. It includes the following chapters: o Chapter 1 - Using the ADVANCED Configuration Option o Chapter 2 - Managing Name Services o Chapter 3 - Modifying a Current Configuration 1 _________________________________________________________________ Using the ADVANCED Configuration Option This chapter describes how to configure the DECnet-Plus for OpenVMS base components using the ADVANCED configuration option so that the system becomes a DECnet-Plus end system on a network. The ADVANCED configuration option allows you to customize your system's network configuration. If you have already configured the DECnet-Plus for OpenVMS software and you want to modify the configuration, see Chapter 3. 1.1 Invoking the ADVANCED Configuration Option To invoke the net$configure.com procedure using the ADVANCED configuration option, enter the following command: $ @sys$manager:net$configure advanced The procedure starts: Copyright (c) Digital Equipment Corporation 1993, 1996. All rights reserved. DECnet-Plus for OpenVMS ADVANCED network configuration procedure This procedure will help you create or modify the management scripts needed to operate DECnet on this machine. You may receive help about most questions by answering with a question mark '?'. You have chosen the ADVANCED configuration option. This option enables you to do some specific tailoring of your system's network configuration by answering some specific questions. If you do not want to do specific tailoring of your system's network configuration but instead want to quickly configure your system using most of the default answers, you should invoke NET$CONFIGURE.COM with the BASIC configuration option, ie: @SYS$MANAGER:NET$CONFIGURE BASIC * Do you want to continue? [YES] : Using the ADVANCED Configuration Option 1-1 Using the ADVANCED Configuration Option 1.1 Invoking the ADVANCED Configuration Option Press Return to continue with the net$configure ADVANCED configuration option. 1-2 Using the ADVANCED Configuration Option Using the ADVANCED Configuration Option 1.1 Invoking the ADVANCED Configuration Option The following illustrates the main menu options from which you can choose: Configuration Options: [0] Exit this procedure [1] Perform an entire configuration [2] Change naming information [3] Configure Devices on this machine [4] Configure Transports [5] Configure Timezone Differential Factor [6] Configure Event Dispatcher [7] Configure Application database [8] Configure MOP Client database [9] Configure Cluster Alias [10] Replace MOP Client configuration [11] Configure satellite nodes [12] Configure cluster script locations * Which configuration option to perform? [1] : 1 If you select Option 1, the procedure informs you that this is the first time you are configuring your system to use DECnet-Plus for OpenVMS: %NET$CONFIGURE-I-SETUPNEW, setting up for new configuration If a Phase IV database exists on the system, the following message displays: %NET$CONFIGURE-I-PHASEIVDATA, Phase IV DECnet database found You have the option of using the existing Phase IV database to generate the Network Control Language (NCL) scripts and configure the system. If you do not want to use the existing Phase IV database to generate the NCL scripts and configure the system, then net$configure configures the system based on your answers to the configuration questions. * Do you want to convert Phase IV databases? [NO] : yes If you answer YES, the procedure prompts you for the Phase IV prefix (see Section 1.2.10 for more information): * Enter Phase IV Prefix [49::] : Using the ADVANCED Configuration Option 1-3 Using the ADVANCED Configuration Option 1.1 Invoking the ADVANCED Configuration Option The net$configure procedure uses the system's existing Phase IV database to generate NCL scripts and configure the system. If you answer NO, the net$configure procedure does not use the system's existing Phase IV database to generate NCL scripts and proceeds to ask all the configuration questions. If you need more information to answer a question, you can type a question mark (?) at the prompts. To configure DECnet, you need to know your node's full name and network address or addresses. 1.2 Directory Name Services DECnet-Plus provides access to the node name and addressing information stored in one or more name services. DECnet- Plus supports the following directory name services: o Local namespace - A discrete, nondistributed namespace that stores name and address information locally in database files, the Local namespace replaces the DECdns Local Naming Option (LNO). It also has the ability to hold 100,000 nodes, and can scale beyond that number. The actual number of nodes that the Local namespace can hold depends on the space available on your system. For more detailed information on namespaces, see Section 2.1. o DECdns distributed namespace - DIGITAL's Distributed Name Service, DECdns is a distributed, global name service. For more information, see Section 2.1.2. o Domain Name System - The Domain Name System (DNS/BIND) is supported for storage of IP addresses. For more information see Section 2.1.3. If you choose to enter more than one directory name service for your system, enter them in order of priority. The ordering of this list is very important: the first directory service entered in this list is considered the primary directory service to use on the system. The primary directory service is considered the first choice to use when looking up naming information for the system. 1-4 Using the ADVANCED Configuration Option Using the ADVANCED Configuration Option 1.2 Directory Name Services Enter an ordered list of the directory services you want to use on the system. If you enter more than one directory service, separate each service with a comma. * Enter the directory services to use on the system [LOCAL,DECDNS,DOMAIN] : For example, if you enter LOCAL,DECDNS,DOMAIN at the prompt, this means the following: o You want to use the name services DECdns, Local, and DNS/BIND. o The primary name service is DECdns. o The secondary name services are Local and DNS/BIND, in that order. ________________________ Note ________________________ If your node is also a DECdns server, the primary name service must be DECdns. ______________________________________________________ 1.2.1 Node Full Name Enter a node full name for each directory service chosen. The node full name is the name of your system's node object in the directory service. It includes the namespace nickname and the full list of directories leading to the node object name. Examples of node full names include: Local namespace - LOCAL:.TomThumb DECdns - ACME:.wabbit.Elmer Domain - elmer.wabbit.acme.edu For the Local namespace, the namespace nickname LOCAL is prepended to the full name and is terminated with a colon (:). The namespace nickname LOCAL means that the Local namespace is used. The node object name must begin with a dot (.), and no element of the name (namespace name, directory, or node object name) can be a null string. Note that the namespace nickname LOCAL is reserved, and indicates that the Local namespace is used on this system. For example, if you enter "Local, DECdns, Domain" at the previous prompt, you will be asked for a DECdns full name, a Local full name, and a fully qualified host name for DNS/BIND. Using the ADVANCED Configuration Option 1-5 Using the ADVANCED Configuration Option 1.2 Directory Name Services * Enter the full name for directory service LOCAL : LOCAL:.ELMER * Enter the full name for directory service DECDNS : ACME:.WABBIT.ELMER * Enter the fully qualified host name for DNS/BIND : ELMER.WABBIT.ACME.EDU 1.2.2 Node Synonym The node synonym is an alphanumeric character string between one and six characters long. The first character must be an alphabetic character; after the first character, the string can contain either alphabetic or numeric characters. If this system had previously been running DECnet Phase IV software, then you should use the old Phase IV node name as the synonym. If this system is joining a DECnet network for the first time, you can use any name for the synonym, as long as it meets the criteria listed above, and is unique within the network. * What is the synonym name for this node? [ELMER] : For more information on node synonym directories, see Section 2.4. 1.2.3 Naming Cache Timeout Value A naming cache is used to improve the performance of node name address resolution. This cache supersedes the existing DECdns cache and is used when looking for addresses in the Domain and Local services, in addition to DECdns. Note that other applications that directly use DECdns continue to use the DECdns cache. The naming cache includes a mechanism to "time out" old entries. In this way, these entries are refreshed periodically to accurately reflect the actual network environment. * Naming cache timeout value? [30-00:00:00] : You have the option to set a value for the naming cache timeout interval. Enter any legal OpenVMS delta time value (the default is 30 days). 1-6 Using the ADVANCED Configuration Option Using the ADVANCED Configuration Option 1.2 Directory Name Services 1.2.4 Session Control Address Update Interval The session control address update interval is the time, in seconds, between updates of local tower address information. * Session Control Address Update Interval ? [10] : To choose a ten second interval, press Return. Otherwise, enter your own interval and press Return. 1.2.5 Naming Cache Checkpoint Interval Periodically, DECnet-Plus saves a snapshot of the in- memory naming cache to disk. This allows systems, during startup, to have a naming cache that is already populated with entries, thereby preserving the contents of the naming cache across system reboots. * Naming cache checkpoint interval? [08:00:00] : You have the option of setting the naming cache checkpoint interval. Enter any legal OpenVMS delta time value (the default is 8 hours). 1.2.6 Specifying the Node Type Prior to DECnet-Plus Version 7.1, DECnet-Plus systems were end nodes. Dedicated routers on the network performed routing functions for the end nodes as necessary. With the Version 7.1 release, DECnet-Plus allows a system to run Integrated IS-IS, thus providing host-based routing functionality. The default is to be an end node. * What type of node (Endnode or Router)? [ENDNODE] : 1.2.7 Configuring Time Zone Differential Factors The UTC (Coordinated Universal Time) is calculated automatically by using the OpenVMS UTC. The procedure displays the following message: Determining DTSS timezone rules from OpenVMS information... After the initial system configuration, you can choose to reconfigure the system's time zone rule (TZR) by selecting Option 5 in the top-level net$configure menu in either the BASIC or ADVANCED configuration procedure. Using the ADVANCED Configuration Option 1-7 Using the ADVANCED Configuration Option 1.2 Directory Name Services 1.2.8 Specifying Routing Information This section only applies if your DECnet-Plus system is a router. * Type of routing node (L1 or L2)? [L1] : Enter L1 if your DECnet-Plus system will provide intra-area level 1 routing capability. Enter L2 if your DECnet-Plus system will provide inter-area level 2 routing capability. The default is to be a level 1 router. * Maximum path splits [2] : This specifies the maximum number of equal cost paths to split between. * PhaseIV Maximum Address [1023] : Specifies the maximum node number within a Phase IV area. * PhaseIV Maximum Area [63] : This question only applies if your DECnet-Plus system is a level 2 router. It indicates the maximum Phase IV area number. 1.2.9 Specifying a Phase IV-Compatible Address If you want your system to communicate with Phase IV nodes, you must specify a Phase IV address and a Phase IV prefix. These will be used to construct a DECnet Phase IV-compatible address. A DECnet Phase IV-compatible address is a DECnet-Plus address (NSAP) that conforms to the Phase IV area and node limits; that is, the area number is from 1 to 63, and the node number is from 1 to 1023. If there are no Phase IV systems on your network or you do not want to communicate with Phase IV systems, you do not need a Phase IV-compatible address. Entering a Phase IV address of 0.0 at configuration time indicates that this DECnet-Plus system will not have a Phase IV-compatible address, and will not communicate with Phase IV nodes. * Enter PhaseIV Address [15.27] : Enter the Phase IV address you want to use, or enter 0.0 if you do not want to communicate with Phase IV nodes. 1-8 Using the ADVANCED Configuration Option Using the ADVANCED Configuration Option 1.2 Directory Name Services 1.2.10 Specifying a Phase IV Prefix The default value for the Phase IV prefix is 49:: which represents the private network initial domain part (IDP). This is appropriate for a Phase IV DECnet network that contains some DECnet-Plus systems. All nodes within a single addressing domain contain the same IDP in their network addresses. If you are using a Phase IV prefix other than 49::, it must be assigned by an authorized standards organization, such as ANSI, or you must construct a Phase IV prefix that you know will be globally unique (based on your telephone number, for instance). If your organization has allocated its own Phase IV prefix, you can enter that value instead of 49::. The (DNPLUS_PLANNING) contains a detailed description of how to construct an IDP and how to apply to a standards organization for an IDP. 1.2.11 Specifying End Node Information This section applies only if your DECnet-Plus system is an end node. 1.2.11.1 Configuring Network Addresses Your system must have at least one unique network address in order to use DECnet-Plus communications features. DECnet-Plus systems can be multihomed; that is, they can have more than one network address. You can assign up to three network addresses to your system. Having multiple addresses allows you to have both a DECnet- Plus extended address and a Phase IV-compatible address, so you can communicate with both Phase IV and DECnet-Plus systems on the same network. It also allows you to belong to more than one OSI network. This feature is particularly useful when you want to combine two (or more) networks. Rather than assign new addresses to all systems in both networks to reflect the new combined network, those systems that participate in both networks can have an address in each one. Network addresses are sometimes referred to in OSI terminology as network entity titles (NETs). NETs are network service access points (NSAPs) with a selector of 00. There are two ways to configure NETs: Using the ADVANCED Configuration Option 1-9 Using the ADVANCED Configuration Option 1.2 Directory Name Services by autoconfiguring addresses or by manually configuring addresses. ________________________ Note ________________________ If you have an OSI router from a supplier other than Digital Equipment Corporation adjacent to your system, do not choose autoconfiguration unless you know that the router uses NETs with a selector of 00. This restriction applies even if you have a Digital Equipment Corporation WANrouter as well as another supplier's OSI router on the same LAN. OSI routers that specify NETs differently can cause you to autoconfigure your network addresses incorrectly. If you have such a router, you must choose to manually configure your NETs by answering NO to the autoconfiguration question. ______________________________________________________ Choice 1: Autoconfiguring Addresses ________________________ Note ________________________ To use this option, you must be using only Phase V (OSI) addressing. ______________________________________________________ If you want to have your network address autoconfigured for you, answer YES to the following question during network configuration when using the net$configure tool: * Autoconfigure network addresses? [YES] : Choice 2: Manually Configuring Addresses You can assign a maximum of three network addresses to the system including the Phase IV network address. To create a NET manually, you need to know your system's network IDP, network local area, and node ID. For example, given the following information: A network IDP of 41:45436192: A network local area of 43 A node ID of 258 1-10 Using the ADVANCED Configuration Option Using the ADVANCED Configuration Option 1.2 Directory Name Services The NET is constructed as follows: IDP and selector = 41:45436192:local-area:node-id:00 43 decimal = 2B hexadecimal (local area) (43 * 1024) + 258 = 44290 decimal 44290 decimal = AD02 hexadecimal AD02 swapped = 02AD hexadecimal (node ID) The resulting NET is 41:45436192:00-2B:AA-00-04-00-02-AD:00 ________________________ Note ________________________ NETs can be entered in OSI format, DNA format, or hexadecimal format. Make sure you include the 00 selector when you manually specify a NET. ______________________________________________________ For more information on how to construct DNA and OSI NETs, see the chapter on NSAPs in the (DNPLUS_ PLANNING). 1.2.11.2 DNA Address Format You have the option of setting the value of the routing characteristic "DNA Address Format" to either TRUE or FALSE. * DNA Address Format [TRUE] : The DIGITAL Network Architecture (DNA) Address Format attribute controls the interpretation of address structuring. It does not control autoconfiguration. To control autoconfiguration, you need to use the Manual Network Entity Titles attribute by manually adding or removing NETs. 1.2.11.3 Segregated Mode Routing and Integrated Mode Routing You have the option of using integrated mode routing or segregated mode routing. If you answer NO to this question, you will default to integrated mode. * Do you want to use segregated mode routing? [NO] : Integrated mode routing works in the following way: It sends DECnet Phase IV messages across the network using DECnet Phase V Network layer protocols. Routers receiving DECnet Phase IV packets translate them to OSI CLNP format before forwarding them. Messages destined for DECnet Phase Using the ADVANCED Configuration Option 1-11 Using the ADVANCED Configuration Option 1.2 Directory Name Services IV systems are translated to Phase IV format only on the last hop of their journey. Integrated mode routing allows routers to route both DECnet Phase IV and Phase V traffic while storing a single network topology in their internal databases. Under integrated mode, DECnet-Plus systems attempt to send packets in DECnet Phase V format unless one of the following is true: o They are communicating directly to an adjacent DECnet Phase IV system. o No DECnet Phase V routers exist on the network to forward the packets. Integrated mode routing is the only mode supported on OpenVMS systems preceding DECnet/OSI for OpenVMS Version 6.0. Segregated mode routing handles DECnet Phase IV and Phase V as independent protocols. Routers do not translate messages between DECnet Phase IV and Phase V formats. The routers must maintain separate network topologies in their internal databases to handle each type of protocol. Under segregated mode, DECnet-Plus end systems transmit messages in the Phase IV address format if they have a DECnet Phase IV translatable destination address. All other messages are sent in DECnet Phase V format. If you use non- DIGITAL routers that do not support DIGITAL's technique of translating DECnet Phase V addresses to DECnet Phase IV, you may want to use segregated mode routing. On OpenVMS systems, integrated mode is the default routing mode. Use integrated routing mode in an integrated routing environment where the routers can handle Phase-IV-to-Phase- V or Phase-V-to-Phase-IV packet format conversions. Use segregated routing mode when the adjacent router(s) cannot perform Phase-IV-to-Phase-V or Phase-V-to-Phase-IV packet conversions. ________________________ Note ________________________ If your OpenVMS system is running cluster alias, you must use integrated mode. ______________________________________________________ 1-12 Using the ADVANCED Configuration Option Using the ADVANCED Configuration Option 1.2 Directory Name Services 1.2.11.4 ESHello Timer The default ESHello Timer attribute determines the interval, in seconds, when the end system (ES) sends out its hello. This interval multiplied by 3 is the amount of time the other end of a routing adjacency will wait before determining that this system is no longer able to accept connections. * Routing default ESHello Timer? [600] : To select the default of 600, press Return. Otherwise, choose your own value and press Return. 1.3 Configuring Devices The net$configure procedure checks for network devices on the system that are supported by net$configure and then configures them. If the procedure finds that you have WANDD or X.25 installed but not configured, you will see the following information: You have installed wide area device support, but it has not been configured. You may configure it now if you want. * Do you want to configure Wide Area devices? [YES] : N %NET$CONFIGURE-I-SCANCONFIG, scanning device configuration - please wait Answer YES if you want to configure WANDD. ________________________ Note ________________________ If you answer NO to configuring wide area devices, you will not see any information regarding X.25 or P.S.I. configurations. ______________________________________________________ 1.3.1 Configuring Asynchronous Connections If you have installed and configured WANDD software on this system, you have the option of configuring it to support asynchronous connections. * Do you want asynchronous datalink support? [NO] : For more information on configuring asynchronous connections, see Appendix A. Using the ADVANCED Configuration Option 1-13 Using the ADVANCED Configuration Option 1.3 Configuring Devices 1.3.2 Configuring Data Links and Routing Circuits You now need to supply names for the data links and routing circuits you have on your system. Specify the simple name that you want to use for each data link and routing circuit. * Data Link name to use for ESA0 (DESVA)? [CSMACD-0] : * Routing Circuit Name for Data Link 'CSMACD-0'? [CSMACD-0] : 1.3.2.1 Specifying Circuit Cost and Routing Priority The following applies only if your DECnet-Plus is a routing node. For each data link and routing circuit pair entered, specify the circuit cost and router priority at level 1. If your node is also a level 2 router, you will be asked for level 2 cost and router priority. Cost indicates the cost of traffic on a particular circuit. Priority refers to the priority for becoming a designated router on a LAN at level 1 or level 2. * Level 1 Cost for Routing Circuit 'CSMACD-0'? [8] : * Level 1 Router Priority for Routing Circuit 'CSMACD-0'? [64] : * Level 2 Cost for Routing Circuit 'CSMACD-0'? [8] : * Level 2 Router Priority for Routing Circuit 'CSMACD-0'? [64] : 1.3.3 Enabling Phase IV Addressing on Routing Circuits If you previously specified a Phase IV-compatible address in order to communicate with Phase IV nodes (as in Section 1.2.6), entering YES to the following question allows Phase IV messages to be transmitted on the circuit. Answering NO to this question means that no Phase IV messages will be transmitted on the circuit. * Enable Phase-IV Addressing on Routing Circuit 'CSMACD-0'? [YES] : 1.3.4 FDDI Large Packet Support If you have an FDDI-type circuit on your system, you have the option of enabling FDDI large packet support. (A large packet is 4 KB in size, where an Ethernet packet is 1500 bytes in size.) FDDI large packet support allows you to fully use the bandwidth of FDDI. (A DECnet-Plus router on the LAN, preferably on the FDDI, is required to enable large packet support.) 1-14 Using the ADVANCED Configuration Option Using the ADVANCED Configuration Option 1.3 Configuring Devices If you choose not to enable FDDI large packet support on the system, the FDDI circuit uses the bandwidth of Carrier Sense, Multiple Access with Collision Detection (CSMA-CD) instead. If there is an FDDI-type circuit on the system, the procedure displays the following message: An FDDI-type circuit has been found on the system. You have the option of enabling FDDI large packet support on the system. Note that a DECnet-Plus router on the LAN (preferably on the FDDI) is required in order to use FDDI large packet support. * Enable FDDI large packet support? [NO] : If you want to enable FDDI large packet support, answer YES. 1.3.5 Configuring an Alpha System 1. For an Alpha system, the procedure displays the following information: DEC X.25 software has been installed on this system. You have the option of configuring DECnet to run over X.25. * Do you want to configure DECnet over X.25? [NO] : Answer YES if you want to configure DECnet over X.25. If you answer YES, you will see a list of choices for the type of X.25 circuit to use: Types of X.25 circuits: [1] - X.25 Dynamic Assigned (DA) [2] - X.25 Static Incoming (IN) [3] - X.25 Static Outgoing (OUT) [4] - X.25 Permanent (PVC) * Which type of X.25 circuit do you want to use? : 4 This prompt allows you to select the type of routing circuit you want to use over X.25. The menu offers four choices: o A dynamically assigned routing circuit (menu option 1) operates over a number of X.25 switched virtual circuits (SVCs), both incoming and outgoing. Using the ADVANCED Configuration Option 1-15 Using the ADVANCED Configuration Option 1.3 Configuring Devices o A static incoming routing circuit (menu option 2) operates over a single incoming X.25 switched virtual circuit (SVC). o A static outgoing routing circuit (menu option 3) operates over a single outgoing X.25 switched virtual circuit (SVC). o A permanent routing circuit (menu option 4) uses a permanent virtual circuit (PVC) instead of an SVC. Enter the number for the type of circuit you want. 2. The procedure then asks for information about the routing circuit. * Routing Circuit Name to use? [X25-PVC-0] : Specify the simple name you want to use for the routing circuit. You can use the default or you can supply a name (for example, X25-PSI-0). 3. The procedure then asks for a template name to use for the circuit you just specified. * Template name? [X25-PVC-0] : Specify the simple name of an X25 Access template. A default name is provided or you may enter your own name (for example, X25-DA-1). All X.25 routing circuits use an X25 Access template to either make or accept a network connection. o For a static outgoing (OUT) circuit, the X25 Access template must specify DTE class, destination DTE address, and call data. The X25 Access template can also specify other call characteristics to make the outbound network connection. o For a static incoming (IN) routing circuit, the X25 Access template can specify call characteristics to accept the inbound network connection. o For a dynamically assigned (DA) routing circuit, the X25 Access template must specify DTE class and call data. The X25 Access template can also specify other call characteristics to make the outbound or accept the inbound network connections. 1-16 Using the ADVANCED Configuration Option Using the ADVANCED Configuration Option 1.3 Configuring Devices Use the X.25 configuration program to configure X25 Access templates. 4. If you chose to configure an X.25 dynamically assigned (DA) circuit or an X.25 static incoming (IN) circuit, the procedure asks for a filter name. * Filter name? [X25-DA-0] : Specify the simple name of an X25 Access filter. You may accept the default or you may enter your own name (for example, X25-IN-0). Static incoming and dynamically assigned X.25 circuits use an X25 Access filter to receive inbound network connections. For a static incoming circuit, the X25 Access filter must specify inbound DTE class, sending DTE address, call data value, and call data mask. For a dynamically assigned circuit, the X25 Access filter must specify inbound DTE class, call data value, and call data mask. Use the X.25 configuration program to configure X25 Access filters. 5. If you choose to configure an X.25 dynamic assigned (DA) circuit, the procedure displays this prompt: * Do you want to configure any reachable addresses? [NO] : If you answer NO, the procedure skips to the question, "Configure another PSI routing circuit for DECnet?". If you want to configure any reachable address subentities, answer YES. The procedure displays the following prompt: * Reachable address name? : Specify the simple name of the reachable address subentity that you want to create (for example, ACCOUNTS_DEPT). 6. The procedure then asks for the reachable address prefix: * Reachable address prefix : Using the ADVANCED Configuration Option 1-17 Using the ADVANCED Configuration Option 1.3 Configuring Devices The reachable address subentity name is used to select the remote DTE address to where a routing packet is sent. The selection is done by finding a reachable address subentity that has an address prefix matching the beginning of the remote NSAP in the routing packet. Specify the address prefix for this reachable address entity. The address prefix is a string of characters that is a valid beginning of an NSAP (for example, 41:45436192:). The address prefix matches all NSAPs. 7. The procedure then prompts for the reachable address data terminal equipment (DTE) list: * Reachable address dte list? : You can configure a reachable address subentity with one or more DTE addresses. If more than one DTE address is configured, then only one is selected each time a packet is sent. All the remote DTE addresses must be accessible by the DTE class configured in the X25 Access template already configured for the associated dynamic assigned circuit. Specify the list of remote DTE addresses for this reachable address entity. A DTE address consists of 1 to 15 decimal characters. The DTE addresses in the list should be separated by commas (for example, 2,3,4). 8. The procedure then prompts for additional reachable addresses: * Any more reachable addresses you wish to configure? [NO] : If you want to configure another reachable address subentity for this circuit, answer YES. 9. When you have entered the circuit, template, and filter names and you have specified the appropriate reachable address information, the procedure asks if you want to configure any other circuits. * Configure another PSI routing circuit for DECnet? [NO] : If you do not want to configure any other PSI routing circuits, press Return for the default ([NO]). The configuration procedure continues with the next series of questions (such as FDDI large packet support or transports, for example). 1-18 Using the ADVANCED Configuration Option Using the ADVANCED Configuration Option 1.3 Configuring Devices 10. If no devices are found on the Alpha system, the procedure displays the following prompt: * Should a SYSMAN IO AUTO be executed? : If you answer YES, the net$configure procedure invokes the SYSMAN IO AUTO command to find devices on the system. If you answer NO, there are no devices to configure. 1.3.6 Configuring a VAX System If you answer YES to the question, "Do you want to configure Wide Area devices?" and you are using a VAX system, the procedure displays the following information: * Do you want to configure Wide Area devices? [YES] : Answer YES if you want to configure DECnet over P.S.I. If you answer YES, the procedure displays the following: This is the Configuration Procedure for the =========================================== VAX Wan Device Drivers for DECnet/OSI for VMS ============================================= The Wide Area Network Datalinks and Drivers are a prerequisite for DECnet/OSI. They also provide synchronous datalinks in systems that do not use DECnet/OSI for networking. Access to DECnet/OSI datalinks (created by NCL) is possible via the QIO interface to the WAN pseudo-driver, WANDRIVER. Layered products that use synchronous devices do not normally require programming access to WANDRIVER. For further information, see the "DECnet/OSI for VMS WANDD Programming" guide. Do you wish to use WANDRIVER [N] ? y Will you use DEC HDLC [Y] ? Will you use LAPB/E (VAX P.S.I. requires LAPB/E) [Y] ? The DSV11 (Q-bus), DIV32 (Q-bus), DSB32 (BI-bus), DSF32 (MI-bus) and DSW devices are soft-loadable. The WANDD startup procedure will load the microcode for these devices if required. Do you have any soft-loadable microcode devices on this system [N] ? Will you use the VAXft DSF32 device driver [N] ? y Using the ADVANCED Configuration Option 1-19 Using the ADVANCED Configuration Option 1.3 Configuring Devices The VAXft DSF32 software supports the pairing of physical controllers to provide a fault-tolerant configuration. Such a pairing is called a Failover Set. The DSF32 device does not automatically create the failover sets, so you will need to pair controllers using the Failover Set Manager software. This management software can be invoked during system startup from within the command procedure WANDD$STARTUP_SF.COM, which is placed in the SYS$STARTUP directory by the kit installation procedure. If you want to have these Failover Sets automatically configured when the system starts up you will need to modify WANDD$STARTUP_SF.COM to include Failover Set Manager commands that you require. Are you satisfied with the answers you have given [Y] ? If you have already started up the WAN Drivers and Datalinks (that is, if you have already successfully run SYS$STARTUP:WANDD$STARTUP.COM since your system was last booted), then you will need to reboot your system for your new configuration to take effect. %NET$CONFIGURE-I-SCANCONFIG, scanning device configuration - please wait * Do you want to configure DECnet over X.25? [NO] : yes Types of X.25 circuits: [1] - X.25 Dynamic Assigned (DA) [2] - X.25 Static Incoming (IN) [3] - X.25 Static Outgoing (OUT) [4] - X.25 Permanent (PVC) * Which type of X.25 circuit do you want to use? : 1 * Routing Circuit Name to use? [X25-DA-0] : * Template name? [X25-DA-0] : * Filter name? [X25-DA-0] : * Do you want to configure any reachable addresses? [NO] : * Configure another X.25 routing circuit for DECnet? [NO] : The procedure continues to ask for information. See Section 1.3.5 for the types of questions you will see and possible responses you can enter. If no devices are found on the VAX system, the procedure displays the following prompt: * Should a SYSGEN AUTOCONFIGURE ALL be executed? : 1-20 Using the ADVANCED Configuration Option Using the ADVANCED Configuration Option 1.3 Configuring Devices If you answer YES, the net$configure procedure invokes the SYSGEN AUTOCONFIGURE ALL command to find devices on the system. If you answer NO, there are no devices to configure. 1.4 Configuring the Network Service Protocol (NSP) Transport If you want the system to communicate with DECnet Phase IV nodes, answer YES to the following question. * Configure the NSP Transport? [YES] : If you answer NO, the procedure still loads the NSP Transport image. However, NSP Transport is not configured or usable until you run the net$configure procedure and answer YES to the question, "Configure the NSP Transport?" To determine the maximum number of active transport connections allowed at any one time to this transport, the procedure displays the following prompt: * Maximum number of logical links? [200] : You are then prompted to set the following values: * Maximum transmit and receive window? [20] : * Maximum receive buffers? [4000] : DIGITAL recommends setting a value of 20 for the maximum transmit and receive window option. The recommended value to set the maximum receive buffers is no more than maximum window multiplied by maximum transport connections for normal network operation in a typical network environment. Selecting other values than these can significantly alter the behavior of your system and network and should only be done after a thorough analysis of your network traffic and application requirements. High values of maximum receive buffers may require considerable buffering capacity on your node; therefore, a non-paged pool should be allocated accordingly. If your node does not have enough non-paged pool, maximum receive buffers should be set to a smaller value than maximum window multiplied by maximum transport connections. Using the ADVANCED Configuration Option 1-21 Using the ADVANCED Configuration Option 1.4 Configuring the Network Service Protocol (NSP) Transport The transport receiver's window is determined by a combination of maximum transport connections, maximum receive buffers, and maximum window. During the life of the connection, the receiver quota fluctuates according to the value of maximum receive buffers divided by currently active connections. The credit window sent to the remote transmitter may or may not be this quota value, depending on the value of maximum window. If maximum window is set to less than the determined receiver quota, this value is used instead for the credit granted to the remote transmitter. The transmitter of a transport connection uses the credit sent by the remote receiver as its transmit window, unless its maximum window is a lower value. In that case, maximum window is used for the transmitter window. 1.5 Configuring the OSI Transport If you want the system to communicate with DECnet-Plus nodes, OSI nodes of other vendors, or if you plan to install the OSAK, FTAM, or VT software, answer YES. If you want to use the DECnet over TCP/IP and/or OSI applications over TCP/IP, answer YES. * Configure the OSI Transport? [YES] : If you answer NO, the procedure still loads the OSI transport images. However, OSI transport is not configured or usable until you run the net$configure procedure and answer YES to the OSI transport question. To determine the maximum number of active transport connections allowed at any one time to this transport, the procedure displays the following prompt: * Maximum number of logical links? [200] : You are then prompted to set the following values: * Maximum transmit and receive window? [20] : * Maximum receive buffers? [4000] : DIGITAL recommends setting a value of 20 for the maximum transmit and receive window option. The recommended value to set the maximum receive buffers is no more than maximum window multiplied by maximum transport connections for normal network operation in a typical network environment. 1-22 Using the ADVANCED Configuration Option Using the ADVANCED Configuration Option 1.5 Configuring the OSI Transport Selecting other values than these can significantly alter the behavior of your system and network and should only be done after a thorough analysis of your network traffic and application requirements. High values of maximum receive buffers may require considerable buffering capacity on your node; therefore, a non-paged pool should be allocated accordingly. If your node does not have enough non-paged pool, maximum receive buffers should be set to a smaller value than maximum window multiplied by maximum transport connections. The transport receiver's window is determined by a combination of maximum transport connections, maximum receive buffers, and maximum window. During the life of the connection, the receiver quota fluctuates according to the value of maximum receive buffers divided currently active connections. The credit window sent to the remote transmitter may or may not be this quota value, depending on the value of maximum window. If maximum window is set to less than the determined receiver quota, this value is used instead for the credit granted to the remote transmitter. The transmitter of a transport connection uses the credit sent by the remote receiver as its transmit window, unless its maximum window is a lower value. In that case, maximum window is used for the transmitter window. You are then prompted: * Run OSI Applications over TCP/IP? [YES] : Answer YES to this question if you want to run any of your OSI applications over TCP/IP. This causes the configuration utility to build the appropriate RFC 1006 template and establish a listener port for port 102. * Run DECnet over TCP/IP? [YES] : Answering YES to this question enables DECnet-Plus to run over a TCP/IP network to any system that has enabled this same feature. The configuration utility builds the appropriate RFC 1859 template and establishes a listener port for Port 399. (The default name for the RFC 1859 template is osit$rfc1006plus.) Using the ADVANCED Configuration Option 1-23 Using the ADVANCED Configuration Option 1.5 Configuring the OSI Transport 1.5.1 Congestion Avoidance One feature of OSI transport is the ability to use the Congestion Experienced field in the Connectionless-mode Network Service (CLNS) routing header, and to implement a Congestion Avoidance scheme in heavily congested networks. The CLNS Congestion Experienced field is used by routers that support this feature (such as DECNIS) to give an early indication of congestion. When OSI transport receives data that passed through a network path where the Congestion Experienced bit is set, OSI transport reduces the transmit rate of the sending end system to help alleviate network congestion. This feature works well in networks where all protocols support Congestion Avoidance mechanisms. However, it has been noted that in some heavily congested multi- protocol networks, this feature can negatively impact the performance of DECnet compared to other protocols. DIGITAL recognizes that most of its customers have multi- protocol networks. In this environment, not all network protocols have Congestion Avoidance mechanisms. Therefore, the default of this characteristic is disabled. If you operate in an environment where you can take advantage of Congestion Avoidance mechanisms, DIGITAL recommends that you enable the feature again. You are asked a new question about multi-protocol networks: * Is this system operating in a multi-protocol network? [YES] : If you take the default answer of YES, then the OSI transport Congestion Avoidance characteristic is set to FALSE. A NO answer to this question sets the characteristic to TRUE. To change transport Congestion Avoidance values, you must invoke net$configure in ADVANCED mode and use Option 4 (Configure Transports) and answer NO to the question. 1-24 Using the ADVANCED Configuration Option Using the ADVANCED Configuration Option 1.5 Configuring the OSI Transport 1.5.2 Setting Up the OSI Loopback Test Application Account If you answered YES to the "Configure the OSI Transport?" question described earlier, the procedure displays the following prompt: * Username for OSI loopback test application to use? [SYSTEST] : Press Return to accept the default user name for the application loopback test account. The procedure displays a message stating that the default OSI templates have been created. %NET$CONFIGURE-I-CREDEFOSITEMPLATE, created default OSI templates 1.5.3 Creating Additional OSI Templates If you configure OSI transport, net$configure automatically creates the default OSI templates required by the OSAK and FTAM installation and verification procedures (IVPs). * Do you want to create additional OSI templates? [NO] : yes If you answer YES to the previous prompt, the procedure displays prompts to obtain the information required to configure the OSI template; otherwise, the procedure skips to the Event Dispatcher question (see Section 1.6). * Type of network service (CLNS/CONS/RFC1006)? [CLNS] : If you want to use Connectionless-mode Network Service (CLNS), press Return. If you want to use Connection Oriented Network Service (CONS), enter CONS. If you want to use DECnet over TCP/IP and/or OSI applications over TCP/IP enter RFC1006. For more information about types of network service, refer to the (DNPLUS_OVMS_NET_MGMT) guide or type a question mark (?) at the prompt. Depending on which network service you select, you will see one of the following prompts: * Name of the OSI template? [OSIT$CLNS_Default0] : * Name of the OSI template? [OSIT$CONS_Default0] : * Name of the OSI template? [OSIT$RFC1006_Default0] : Using the ADVANCED Configuration Option 1-25 Using the ADVANCED Configuration Option 1.5 Configuring the OSI Transport Enter the name you want to use for the OSI template (for example, OSI_TEMPLATE_1) or press Return to accept the default OSI template name. * Will this template be used for inbound packets? : If you want this template to be used for inbound connections, enter YES. If you want this template to be used for outbound connections, enter NO. * Transport Classes to support? [4] : Enter the number of the transport protocol class you want to use for this template. DECnet-Plus for OpenVMS supports three transport protocol classes: 0, 2, and 4. If you select CONS as the network service type, the default is 0, 2, 4. If you select CLNS, the default is 4. If you select RFC 1006, the default is 0, 2. You can also configure multiple OSI templates. For more information about transport protocol classes, refer to the (DNPLUS_OVMS_NET_MGMT) guide or type a question mark (?) at the prompt. 1.5.3.1 CLNS Network Service If you select the network service CLNS, you will see the following prompt: * Use full CLNP or Null Internet? [Full CLNP] : A CLNS OSI transport template can specify use of Internet/ES-IS routing protocols or Null Internet routing protocol. The Null Internet protocol only operates over LAN routing circuits. A CLNS OSI transport template for use with Internet/ES-IS routing protocols can use any routing circuits configured; the Routing module determines the most suitable circuit to use. A CLNS OSI transport template for use with Null Internet routing protocol can only use one routing circuit; routing circuit selection is based on its inactive area address. If you want to create additional OSI templates and you answer Null Internet to the "Use full CLNP or Null Internet?" prompt, the procedure displays the following prompt: 1-26 Using the ADVANCED Configuration Option Using the ADVANCED Configuration Option 1.5 Configuring the OSI Transport * Which routing circuit is this Null Internet template for? [CSMACD-0] : Enter the routing circuit you want to use for the CLNS OSI transport template (for use with Null Internet routing protocol). * Which CLNS Inactive Area to use? [49::FF-00] : A CLNS OSI transport template that specifies the Null Internet routing protocol selects the routing circuit based on the inactive area address of the routing circuit. If you plan to support Null Internet routing, you must configure an inactive area address for the circuit. The inactive area address for the circuit must be different than any area addresses used by DECnet-Plus routers on the same LAN. If you plan to configure more than one LAN routing circuit on this system, and you need Null Internet on each circuit, then each circuit should have a different inactive area address. The CLNS inactive area must be the same as the inactive area set in routing for Null Internet to be used. 1.5.3.2 CONS Network Service If you selected CONS as the network service type, the procedure displays the following prompt: * CONS template name? : Enter the CONS template name you want to use. The CONS template name must be the same as the name used for the X25 Access template for you to make any CONS connections. If the CONS template is used for inbound packets, you will see the following prompt: * CONS filter name? : Enter the CONS filter name you want to use. The CONS filter name should be the same as the name being used for the X25 Access filter. If it is not, you will not be able to make any CONS connections. Using the ADVANCED Configuration Option 1-27 Using the ADVANCED Configuration Option 1.5 Configuring the OSI Transport For the network services CLNS, CONS, and RFC 1006, the following prompts are displayed: * Allow use of expedited data? [YES] : If you want to support the use of expedited data, answer YES. * Allow use of Checksums? [YES] : If you want to use the error correction feature, answer YES. 1.5.3.3 RFC 1006 Network Service If you select the network service RFC 1006, you will see the following prompt: * Local RFC1006 port number? [102] : Enter the outgoing port number to use when establishing a transport connection at the TCP level. For pure RFC 1006, use 102 as the port number. If you want to use DECnet over TCP/IP, use 399 as the port number. If the RFC 1006 template is used for inbound packets, you will see the following prompt: * RFC1006 listener port number? [102] : Enter the incoming port number to use when establishing a transport connection at the TCP level. This number must be the same as the local RFC 1006 port number for the template to be used for inbound traffic. * Do you want to create additional OSI templates? [NO] : This prompt allows you to create additional customized OSI templates. If you answer YES to this prompt, the template questions are repeated. If you answer NO, the procedure proceeds to the Event Dispatcher question. For more information on configuring DECnet-Plus over TCP/IP, and the OSI applications over TCP/IP, refer to Section B.5.1. 1-28 Using the ADVANCED Configuration Option Using the ADVANCED Configuration Option 1.6 Configuring an Event Dispatcher 1.6 Configuring an Event Dispatcher The Event Dispatcher is a utility to receive and display event messages. You can either take the default Event Dispatcher configuration, or you can choose to customize the Event Dispatcher configuration. * Do you want to customize the Event Dispatcher? [NO] : Answer YES if you want to customize the Event Dispatcher configuration. Answer NO if you want the default Event Dispatcher configuration only. If you answer YES, the procedure displays prompts that allow you to customize the Event Dispatcher. The specific prompts are listed and explained in Section 3.8. If you answer NO, the procedure displays: %NET$CONFIGURE-I-EVDDEFAULT, providing default Event Dispatcher configuration If you chose the default Event Dispatcher configuration, you have the option of displaying the events that are logged to the console of this machine. If you do not want to see the events logged to the console of this machine, net$configure will block the events for you. * Display the events logged to the console of this machine? [YES] : 1.7 Configuring an Application Database The following questions determine if you want to set up and use a default account for application objects. You can create default accounts for the following applications: FAL, CML, MAIL, VPM, MIRROR, and PHONE. * Do you want to use a default account for the 'FAL' application? [NO] : File access listener (FAL) is an image that provides authorized access to the file system of a DECnet node on behalf of processes executing on any DECnet node in the network. FAL communicates with the initiating node by means of the Data Access Protocol (DAP). If you want an account set up or used for FAL, answer YES. * Do you want to use a default account for the 'CML' application? [YES] : Using the ADVANCED Configuration Option 1-29 Using the ADVANCED Configuration Option 1.7 Configuring an Application Database CMIP Management Listener (CML) is the DECnet-Plus management module that implements the Common Management Information Protocol (CMIP). It is a utility that provides access to CMIP. If you want an account set up and used for CML, answer YES. %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account CML$SERVER * Do you want to use a default account for the 'MAIL' application? [YES] : If you want to use the OpenVMS MAIL utility, answer YES. %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account MAIL$SERVER * Do you want to use a default account for the 'VPM' application? [YES] : If you want the system to be an OpenVMS Cluster node, answer YES. The VMScluster Performance Monitor (VPM) needs an account on your system to support the OpenVMS Monitor utility command monitor cluster. Answer NO if the system is to be a non-cluster end system. If you answer YES, you will see the following message: %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account VPM$SERVER * Do you want to use a default account for the 'MIRROR' application? [YES] : MIRROR is used for some forms of loopback testing. If you want to use MIRROR, answer YES. %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account MIRRO$SERVER * Do you want to use a default account for the 'PHONE' application? [YES] : The PHONE utility allows users on the same or different OpenVMS systems to communicate interactively. If you intend to use the OpenVMS PHONE utility, answer YES. %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account PHONE$SERVER 1.8 Configuring a Cluster Alias The following steps describe how to configure a cluster alias. 1. If the node is an OpenVMS Cluster member or if net$configure finds an alias NCL script on the system, the procedure prompts you to enter the full name of a cluster alias. 1-30 Using the ADVANCED Configuration Option Using the ADVANCED Configuration Option 1.8 Configuring a Cluster Alias * Full name of Cluster Alias : ACME:.WABBIT.HELP If you do not want the node to participate in a cluster alias, press Return. If you want the node to participate in a cluster alias, specify the full name that uniquely identifies the cluster alias node (for example, ACME:.WABBIT.HELP). 2. If you entered a cluster alias full name in response to the previous prompt, the procedure displays the following prompt: * Cluster Alias Phase IV Address (aa.nnnn OR AA-00-04-00-xx-xx) : 12.139 Specify either the DECnet Phase IV node address or Ethernet physical address of the alias. The Phase IV node address has the format area- number.node-number (for example, 12.139). The Ethernet physical address has the format AA-00- 04-00-xx-xx, where xx-xx is calculated from the Phase IV node address. To determine the Ethernet physical address, proceed as follows: a. Convert the Phase IV node address to its decimal equivalent as follows: (area-number * 1024) + node-number = decimal equivalent (For example, (12 * 1024) + 139 = 12427 decimal) b. Convert the decimal node address to its hexadecimal equivalent and reverse the order of the bytes to form the hexadecimal node address. For example: (12427 decimal = 308B hex, reversed = 8B30 hexnodeaddress) c. Incorporate the hexadecimal node address in the following format: AA-00-04-00-hexnodeaddress (For example, AA-00-04-00-8B-30) 3. If you entered a cluster alias full name and a Phase IV address, the procedure displays the following prompt: * Selection weight for this cluster node [0 for satellites] : Using the ADVANCED Configuration Option 1-31 Using the ADVANCED Configuration Option 1.8 Configuring a Cluster Alias The selection weight determines the number of sequential incoming connects passed to this alias member node in the round-robin sequence before proceeding to the next member node in the sequence. A value of zero means this node is not eligible to receive incoming connections to this alias address. Selection weight apportions incoming alias connections according to the capacity of each alias member. For example, nodes with greater capacity should have larger values of selection weight, while OpenVMS Cluster satellites should generally have a value of zero. Specify a nonzero selection weight if this node is connected locally to a dual-ported disk, or if it will be serving any multihost disks, such as RFxx or HSC-connected disks, to other cluster members. DIGITAL recommends values between 0 and 10. 1.9 Configuration Summary and Network Startup The following describes the configuration summary and the network startup. 1. The procedure then displays: Summary of Configuration Node Information Node Type: L2ROUTER Directory Services Chosen: DECDNS,LOCAL,DOMAIN Primary Directory Service: DECDNS DECdns Full name: ACME:.WABBIT.ELMER Local Full name: LOCAL:.ELMER Fully Qualified Host name: ELMER.WABBIT.ACME.EDU Node Synonym: ELMER Phase IV Address: 15.27 Phase IV Prefix: 49:: Autoconfiguration of Network Addresses: Disabled Session Control Address Update Interval: 10 Routing ESHello Timer: 600 1-32 Using the ADVANCED Configuration Option Using the ADVANCED Configuration Option 1.9 Configuration Summary and Network Startup Device Information: Device: ESA0 (DESVA): Data Link name: CSMACD-0 Routing Circuit Name: CSMACD-0 L1 circuit cost: 8 L2 circuit cost: 8 L1 router priority: 64 L2 router priority: 64 Transport Information: NSP Transport: Configured Maximum number of logical links: 200 Maximum Transmit and Receive Window: 20 Maximum Receive Buffers: 4000 OSI Transport: Configured Maximum number of logical links: 200 Maximum Transmit and Receive Window: 20 Maximum Receive Buffers: 4000 Congestion Avoidance Disabled Event Dispatcher Configuration: Sinks: local_sink Outbound Streams: local_stream Phase IV Relay: Enabled * Do you want to generate NCL configuration scripts? [YES] : Answer YES to accept the configuration you just specified. The procedure automatically generates the NCL scripts and then configures the system according to the information you supplied. %NET$CONFIGURE-I-CHECKSUM, checksumming NCL management scripts ________________________ Note ________________________ The net$configure procedure only provides checksums of those NCL management scripts it creates or modifies. It does not provide checksums of user-modified NCL scripts. ______________________________________________________ Using the ADVANCED Configuration Option 1-33 Using the ADVANCED Configuration Option 1.9 Configuration Summary and Network Startup 2. The procedure displays the following prompt: * Do you want to start the network? [YES] : Answer YES if you want to start the network and complete your system's network configuration. If you want to postpone starting the network, answer NO. When you answer NO, the procedure displays the following message: ******************************************************************** You have decided not to start the network. NET$CONFIGURE.COM cannot complete your system's network configuration since it needs the network to be partially started in order to perform certain operations. As a result, your system may be left in an inconsistent state if you try to startup the network manually or if you decide to reboot your system. Once you are ready to start the network, please invoke the NET$CONFIGURE.COM procedure, choose menu option 2 (Change node name/namespace name), and respond YES to starting the network so that the configuration procedure can finish your system's network configuration. ******************************************************************** Network Startup Incomplete DIGITAL recommends that you answer YES and start the network. 3. When you choose to start the network, the procedure displays information similar to the following: Copyright (c) Digital Equipment Corporation 1996. All rights reserved. . . . %NET$STARTUP-I-OPERSTATUS, DECnet-Plus for OpenVMS operational status is RUNNING-MAJOR sys$manager:net$dns_clerk_startup.ncl changed to use the new default namespac Your default namespace nickname is ACME. Your default namespace NSCTS is 08-00-2B-0D-2E-89-23-5B-15-9E-F1-85-95-00. Node 0 at 1996-01-26-14:12:24.170-04:00I0.404 1-34 Using the ADVANCED Configuration Option Using the ADVANCED Configuration Option 1.9 Configuration Summary and Network Startup %NET$CONFIGURE-I-NODERENAMED, node successfully renamed to ACME:.WABBIT.ELMER Directory Service: DECdns 4. You can ignore the Error - Node name lookup failure message during startup. Error - Node name lookup failure ACME:.WABBIT.ELMER Number of nodes reported on: 0 %NET$CONFIGURE-W-NODENOTREG, node is not completely registered yet in the DECdns directory service Directory Service: Local name file Error - Node name lookup failure LOCAL:.ELMER Number of nodes reported on: 0 %NET$CONFIGURE-W-NODENOTREG, node is not completely registered yet in the LOCAL directory service %NET$CONFIGURE-I-IMPORTFILECREATED, created the DECNET_REGISTER import file Directory Service: DECdns Updating nodes listed in SYS$MANAGER:DECNET_REGISTER_IMPORT_FILE_ELMER.TXT Number of nodes registered: 1 Number of nodes modified: 0 %NET$CONFIGURE-I-REGSUCCESS, node has been successfully registered in the DECdns directory service Directory Service: Local name file Updating nodes listed in SYS$MANAGER:DECNET_REGISTER_IMPORT_FILE_ELMER.TXT Number of nodes registered: 1 Number of nodes modified: 0 %NET$CONFIGURE-I-REGSUCCESS, node has been successfully registered in the LOCAL directory service Node 0 at 1996-01-26-14:13:25.980-04:00I0.411 %NET$CONFIGURE-I-NODERENAMED, node successfully renamed to ACME:.WABBIT.ELMER Using the ADVANCED Configuration Option 1-35 Using the ADVANCED Configuration Option 1.9 Configuration Summary and Network Startup Node 0 Session Control Tower Maintenance ACME:.WABBIT.ELMER at 1996-01-26-14:13:35.360-04:00I0.411 %NET$CONFIGURE-I-TOWERSUPDATED, updated address towers for node Node 0 Session Control Backtranslation Softlink * at 1996-01-26-14:13:43.360-04:00I0.412 Node 0 Session Control Backtranslation Softlink * at 1996-01-26-14:13:43.370-04:00I0.412 %NET$CONFIGURE-I-BCKTRNUPDATED, updated backtranslation softlink for node %NET$CONFIGURE-I-CONFIGCOMPLETED, DECnet-Plus for OpenVMS configuration completed $ You have just completed the initial configuration of a DECnet-Plus for OpenVMS system. It should now be operational on the network. You can now use the SET HOST command to connect to other network nodes. 1-36 Using the ADVANCED Configuration Option 2 _________________________________________________________________ Managing Name Services If this is the first time you are configuring the DECnet- Plus for OpenVMS software on your system, the information in this chapter further explains some of the topics that appear as you run the configuration procedure. 2.1 Names Services Overview While configuring DECnet-Plus, the system administrator specifies one or more of the following directory name services to use on the node: the Local namespace, DECdns, or Domain Name System (for DNS/BIND). o Local namespace - A discrete, nondistributed namespace that stores name and address information locally in database files. DECnet-Plus includes a Local namespace. o DECdns - DIGITAL's Distributed Name Service, a distributed, global name service. o Domain Name System - The Domain Name System (DNS/BIND) supported for storage of IP addresses. For more information on name services, refer to the (DNPLUS_PLANNING). 2.1.1 The Local Namespace DECnet-Plus includes a Local namespace, independent of DECdns, that is designed to scale to at least 100,000 nodes. The Local namespace is a discrete, nondistributed namespace that exists on a single node and provides that node with a local database of name and address information. The prefix LOCAL: (or local:) is reserved to indicate that the information for the node is stored in the Local namespace. Managing Name Services 2-1 Managing Name Services 2.1 Names Services Overview DECnet-Plus recognizes that when a node full name begins with LOCAL:, information for that node is stored in a Local namespace. Unlike DECdns, the Local namespace does not employ backtranslation directories for address-to-node-name translation. 2.1.1.1 Creating a Local Namespace If you want to create a Local namespace, enter LOCAL:.DirectoryPath.NodeObject at the following prompt: * Enter the full name for directory service LOCAL: The directory path identifies the namespace subdirectory (if any). The node object is the system's node name. The following are typical node full names properly formatted for the Local namespace: LOCAL:.xyz.abc and local:.maximum. 2.1.1.2 Managing the Local Namespace The DECdns distributed namespace is not a requirement for DECnet-Plus, and the Local namespace does not depend on DECdns. However, the DECdns clerk software is still required on each node. You cannot use the DECdns Control Program (DNSCP) to manage information stored in the Local namespace. Instead, use decnet_register. The decnet_ register tool is described in the (DNPLUS_OVMS_ NET_MGMT) guide. 2.1.2 The DIGITAL Distributed Name Service (DECdns) DECdns is a networkwide service that makes it possible to use network resources without knowing their physical location. Users and applications can assign DECnet-Plus names to resources such as nodes. The creator of a name also supplies other relevant information for DECdns to store, such as the resource's network address. Users then need to remember only the name, and DECdns acts as a lookup service, providing the rest of the data when necessary. 2-2 Managing Name Services Managing Name Services 2.1 Names Services Overview 2.1.2.1 Creating a New Namespace You need to create a new DECdns namespace only if you are configuring the first DECdns server for the network or if you are creating an additional namespace. If you already have a DECdns namespace, you do not need to create a new namespace to be able to run DECnet-Plus. However, if this is the first system in a network where no namespace exists and you do not intend to use the Local namespace, you must create (and populate) a DECdns namespace. If you are unsure whether you need to create a new namespace or configure your system as a server, see your network manager. For information about namespace planning, refer to the (DNPLUS_PLANNING). To create a new namespace while configuring a DECnet-Plus for OpenVMS system: o The DECdns server software must be installed on the system. o DECdns must be specified as one of the naming services configured on the system. When you create a namespace, you need a namespace nickname and clearinghouse name. The namespace nickname is part of the full name of every subsequent system in the network and should be unique to your network. The namespace nickname that you specify becomes the actual name of the namespace. A clearinghouse is a collection of directory replicas that contains the names and addresses of objects (for example, servers, clerks, files). DIGITAL recommends that you create namespace directories before using the configuration procedure (net$configure.com) to create the namespace. Follow these steps to create namespace directories: 1. Invoke decnet_register and select option 10 ("Manage the directory service"). 2. Follow directions. Be sure to specify DECdns as the directory service to manage (the Local namespace is the default). The decnet_register procedure invokes sys$manager:decnet_register_decdns.com to create the namespace directories. Managing Name Services 2-3 Managing Name Services 2.1 Names Services Overview 3. When finished, invoke the configuration procedure to create the new namespace. For more information on decnet_register, refer to (DNPLUS_OVMS_NET_MGMT). 2.1.2.2 Creating a DECdns Namespace If you select DECdns as a directory service, net$configure prompts you for the full name you want to use: