DECnet-Plus_for_OpenVMS_____________________________ Installation and Basic Configuration Order Number: AA-QPSUB-TE November 1996 This book explains how to install and configure the DECnet-Plus for OpenVMS software and how to perform the postinstallation steps. 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 by X/Open Co. Ltd. All other trademarks and registered trademarks are the property of their respective holders. _________________________________________________________________ Contents Preface................................................... vii Part I DECnet-Plus for OpenVMS Installation 1 Preparing to Install DECnet-Plus for OpenVMS 1.1 The POLYCENTER Software Installation Utility....................................... 1-1 1.2 Inspecting the Distribution Kit............... 1-1 1.3 Time Required for Installation and Configuration................................. 1-3 1.4 Prerequisite Software and Licenses............ 1-3 1.4.1 Software and Licenses..................... 1-3 1.4.1.1 DECnet and OSI Applications over TCP/IP.................................. 1-4 1.4.2 Checking Licenses......................... 1-5 1.5 System Requirements........................... 1-5 1.5.1 Disk Space................................ 1-5 1.5.2 Required Memory........................... 1-7 1.5.3 Required System Parameters................ 1-7 1.5.3.1 SYSGEN Parameters for OpenVMS Cluster Members................................. 1-8 1.6 Privileges and Rights Identifiers............. 1-8 1.7 Backing Up the System Disk.................... 1-9 1.8 Notifying Users............................... 1-9 iii 2 Pre-Installation Tasks 2.1 Information Required to Complete the Installation Planning Checklist............... 2-1 2.2 Installation Planning Checklist............... 2-1 3 Installing DECnet-Plus for OpenVMS 3.1 Recommended Order for Installing Software..... 3-3 3.1.1 Installing DECnet-Plus for an OpenVMS Alpha System.............................. 3-3 3.1.2 Installing DECnet-Plus for a VAX System... 3-6 3.2 Installing DECnet-Plus Using the POLYCENTER Software Installation Utility................. 3-8 3.2.1 Sample DECnet-Plus for OpenVMS Alpha Installation ............................. 3-8 3.2.2 Sample DECnet-Plus for OpenVMS VAX Installation.............................. 3-9 3.3 Files Installed on Your System................ 3-11 Part II DECnet-Plus for OpenVMS BASIC Configuration 4 Configuration Options 4.1 Selecting a Configuration Option.............. 4-2 4.2 How to Run NET$CONFIGURE ..................... 4-4 4.2.1 Local and Global Symbols.................. 4-5 4.2.2 Running the Procedure from Different Processes................................. 4-6 5 Using the FAST Configuration Option 5.1 Invoking the FAST Configuration Option........ 5-1 5.2 Changing a Current DECnet-Plus System Configuration................................. 5-6 iv 6 Using the BASIC Configuration Option 6.1 Invoking the BASIC Configuration Option....... 6-1 6.2 Directory Name Services....................... 6-2 6.2.1 Node Full Name............................ 6-3 6.2.2 Specifying the Node Type.................. 6-5 6.2.3 Specifying Routing Information............ 6-5 6.2.4 Node Synonym.............................. 6-6 6.2.5 Specifying a DECnet Phase IV-Compatible Address................................... 6-6 6.2.6 Specifying a Phase IV Prefix.............. 6-7 6.2.7 Configuring Network Addresses............. 6-7 6.2.8 DNA Address Format........................ 6-7 6.3 Configuring Devices........................... 6-7 6.3.1 Configuring an Alpha System .............. 6-8 6.3.2 Configuring a VAX System.................. 6-9 6.4 Configuring Transports........................ 6-11 6.5 Configuring Time Zone Differential Factors.... 6-11 6.6 Configuring an Event Dispatcher............... 6-11 6.7 Configuring an Application Database........... 6-11 6.8 Configuring a Cluster Alias .................. 6-12 6.9 Changing a Current DECnet-Plus System Configuration................................. 6-18 7 Managing Name Services 7.1 Names Services Overview....................... 7-1 7.1.1 The Local Namespace ...................... 7-1 7.1.1.1 Creating a Local Namespace.............. 7-2 7.1.1.2 Managing the Local Namespace............ 7-2 7.1.2 The Digital Distributed Name Service (DECdns).................................. 7-2 7.1.2.1 Creating a New Namespace................ 7-3 7.1.2.2 Creating a DECdns Namespace............. 7-4 7.1.3 Domain Name System........................ 7-7 7.1.4 Namespace Management...................... 7-8 7.2 Name Service Search Path...................... 7-8 7.2.1 Configuring the Search Path Information... 7-9 7.2.1.1 Naming Search Path in a Cluster......... 7-10 7.2.2 Displaying the Search Path Information.... 7-10 7.2.3 Modifying the Search Path Information..... 7-10 7.2.4 Creating a Site-Specific Search Path NCL Script.................................... 7-11 7.2.5 Using the Search Path to Ease Migration... 7-12 v 7.2.6 Setting Up Naming Templates............... 7-12 7.3 Domain Synonyms............................... 7-13 7.3.1 Search Path Naming Template Support for Domain Synonyms........................... 7-14 7.3.2 Local Aliases............................. 7-14 7.4 Node Synonym Directories...................... 7-15 7.4.1 Defining an Alternate Node Synonym Directory................................. 7-15 7.4.2 When to Use the Logical Name.............. 7-15 7.5 Using a DNS Version 1 Namespace with DECdns Version 2..................................... 7-16 7.5.1 Preparing a DNS Version 1 Namespace for Use by DECdns Version 2................... 7-17 7.5.2 Using the DNS Version 1 Namespace......... 7-18 7.6 Registering a Node in the Namespace........... 7-19 7.6.1 Export/Import File Format................. 7-19 7.6.2 Problems Registering a Node............... 7-19 Part III Additional Installation Information A The POLYCENTER Software Installation Utility A.1 DCL Help with POLYCENTER...................... A-2 A.1.1 DCL Command Summary....................... A-3 A.2 Creating and Using a Product Configuration File.......................................... A-6 A.2.1 Responding to Installation Questions...... A-8 A.3 Verifying Pre-installation Tasks.............. A-8 A.4 Resolving Conflicts........................... A-9 A.5 Determining Installation Progress............. A-9 A.6 Possible Installation Errors.................. A-10 A.7 Reporting Problems............................ A-10 B Installing DECnet-Plus for OpenVMS from an InfoServer B.1 Steps to Installing the Software from an InfoServer.................................... B-1 B.2 Install Commands.............................. B-2 vi C System Files Loaded During Installation Index Figures 3-1 Installation and Configuration Flowchart (Alpha Only).............................. 3-5 3-2 Installation and Configuration Flowchart (VAX Only) ............................... 3-8 Tables 1-1 Disk Space Requirements - Optional Software.................................. 1-6 1-2 Minimum System Parameters Required - Base Software Installation..................... 1-7 2-1 Installation Planning Checklist........... 2-2 4-1 Choosing Your Configuration Option........ 4-3 A-1 DCL PRODUCT Commands and Qualifiers....... A-3 vii _________________________________________________________________ Preface This is the first installation book you should read in order to successfully install DECnet-Plus for OpenVMS. It also includes how to configure DECnet-Plus for OpenVMS using the FAST and BASIC configuration options, and information about name services. The second installation book (DECnet-Plus for OpenVMS Applications Installation and Advanced Configuration) describes using the ADVANCED configuration option, and how to 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) ________________________ Note ________________________ DECnet-Plus for OpenVMS must be installed on your system before you can install X.25, FTAM, VT, or OSAK software. ______________________________________________________ vii Intended Audience This book is written for: o OpenVMS system managers o DECnet-Plus software installers o Network planners and managers Structure of This Book This book has three parts: Part I Describes the pre-installation and installation steps necessary to install DECnet-Plus for OpenVMS. Part Provides help to determine which configuration II option to use: FAST, BASIC or ADVANCED. Describes how to run a FAST configuration, and a BASIC configuration including examples for an Alpha and a VAX system. Also includes an overview of the naming services you can select during configuration. Part Includes a basic overview on the POLYCENTER III Software Installation utility, an example of installing DECnet-Plus for OpenVMS from an InfoServer, and a list of system files loaded during installation. 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 viii Related Documents The following books provide additional information: o DECnet-Plus for OpenVMS Applications Installation and Advanced Configuration The second installation book to read in order to successfully install and configure X.25 for OpenVMS Alpha, P.S.I and P.S.I. Access for OpenVMS VAX, FTAM, VT, and OSAK. It also includes how to configure DECnet- Plus for OpenVMS using the ADVANCED configuration option and how to modify a configuration. o DECnet-Plus for OpenVMS Introduction and User's Guide 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 DECnet-Plus Planning Guide Explains in detail the transition from DECnet Phase IV to DECnet-Plus, providing configuration guidelines and planning tasks. o DECnet-Plus DECdns Management o DECnet-Plus DECdts Management o DECnet-Plus for OpenVMS Network Management o X.25 for OpenVMS Configuration Guide o OpenVMS License Management Utility Manual o OpenVMS System Management Utilities Reference Manual 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 ix 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 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). x 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.__________________________________ xi Part I _________________________________________________________________ DECnet-Plus for OpenVMS Installation Part I describes the prerequisite steps necessary to install DECnet-Plus for OpenVMS, and how to install it. o Chapter 1 - Preparing to Install DECnet-Plus for OpenVMS o Chapter 2 - Pre-Installation Tasks o Chapter 3 - Installing DECnet-Plus for OpenVMS 1 _________________________________________________________________ Preparing to Install DECnet-Plus for OpenVMS This chapter describes the tasks you must perform before installing and configuring the DECnet-Plus for OpenVMS distribution kit. 1.1 The POLYCENTER Software Installation Utility The POLYCENTER Software Installation utility replaces VMSINSTAL as the method of installing layered products for OpenVMS systems. It allows you to install several software products with a single command. Full details for using the POLYCENTER Software Installation utility to install and manage software products on your system are provided in the OpenVMS System Management Utilities Reference Manual. This manual also provides information on removing products along with other POLYCENTER Software Installation utility features. See Appendix A for a basic overview of the POLYCENTER Software Installation utility. 1.2 Inspecting the Distribution Kit Before you install the DECnet-Plus for OpenVMS software, make sure you have a complete software distribution kit. If you have the OpenVMS condist CD-ROM distribution kit, check the CD master index for the kit location. If you have a magtape or TK50 kit, supply the device name when requested by the POLYCENTER Software Installation utility. Check that the kit contains everything listed on the bill of materials (BOM). If anything is missing or damaged, contact your Digital representative. Preparing to Install DECnet-Plus for OpenVMS 1-1 Preparing to Install DECnet-Plus for OpenVMS 1.2 Inspecting the Distribution Kit The distribution kit contains the following component kit files: o Base components software - DECnet-Plus for OpenVMS base kit o Optional software - OSI remote file operations support kit (FTAM software) - OSI applications support kit (OSAK software) - Virtual Terminal (VT) software kit For a more detailed list, see Chapter 3. 1-2 Preparing to Install DECnet-Plus for OpenVMS Preparing to Install DECnet-Plus for OpenVMS 1.2 Inspecting the Distribution Kit ________________________ Note ________________________ Before installing any of the software, read the DECnet-Plus Planning Guide (included with your DECnet- Plus for OpenVMS core documentation set). This guide contains installation planning information, including namespace planning instructions. ______________________________________________________ 1.3 Time Required for Installation and Configuration The time required to complete the DECnet-Plus installation and configuration procedures depends on the following: o Configuration option used (FAST, BASIC, or ADVANCED) o Optional software installed o CPU on the system o Type of distribution media The time required to install and configure DECnet-Plus can vary from 30 minutes to 2 hours, depending on the combination of choices you make from the above list. 1.4 Prerequisite Software and Licenses Before you can install and configure the software, the system must have the required operating system software and license(s). 1.4.1 Software and Licenses The prerequisites for installing DECnet-Plus for OpenVMS software are as follows: o OpenVMS operating system Version 7.0 or 7.1 o One of the available DECnet-Plus licenses The specific license required on your system is determined by the functions you want to use: o Basic function license (DVNETEND) - provides end system support. Preparing to Install DECnet-Plus for OpenVMS 1-3 Preparing to Install DECnet-Plus for OpenVMS 1.4 Prerequisite Software and Licenses o Extended function license (DVNETEXT) for Alpha systems - provides end system support, DECdts server, cluster alias, and OSI applications gateways. o Extended function license (DVNETRTG) for VAX systems - provides end system support, DECdns server, DECdts server, cluster alias, and OSI applications gateways. For the extended function licenses, the TELNET/VT gateway also requires the Digital TCP/IP Services for OpenVMS product. o X.25 license (Alpha systems only) - provides functionality over a wide area network link. At least one node of an OpenVMS Cluster system requires the extended function license to use cluster alias. 1.4.1.1 DECnet and OSI Applications over TCP/IP If you plan to use the DECnet-Plus over TCP/IP feature, then TCP/IP software is a prerequisite. Your end system will be able to operate over TCP/IP if and only if the TCP/IP product used on your system supports the PATHWORKS Internet Protocol (PWIP) interface. The PWIP interface is currently supported by the products listed below. Contact the vendor for the required versions of their product. o Digital TCP/IP Services for OpenVMS o TCPware Process Software Corporation 959 Concord Street Framingham, MA 01701 800-722-7770 info@process.com o MultiNet for OpenVMS Cisco Systems, Inc. (formerly TGV, Inc.) 101 Cooper Street Santa Cruz, CA 95060 408-457-5200 sales@tgv.cisco.com o PATHway for OpenVMS 1-4 Preparing to Install DECnet-Plus for OpenVMS Preparing to Install DECnet-Plus for OpenVMS 1.4 Prerequisite Software and Licenses The Attachmate Corp. (formerly The Wollongong Group, Inc.) 1129 San Antonio Road Palo Alto, California 94303 800-872-8649 (800-962-8649 in CA) sales@twg.com ________________________ Note ________________________ For more information on using DECnet over TCP/IP or the OSI applications over TCP/IP, refer to the DECnet- Plus for OpenVMS Network Management guide. ______________________________________________________ 1.4.2 Checking Licenses To determine the OpenVMS operating system version number, enter the following DCL command: $ show system To determine whether a DECnet-Plus license is registered, enter the following DCL command: $ show license dvnet* If the system does not have the required license(s), obtain the Product Authorization Key (PAK) and register the license. For instructions on registering a license, refer to the OpenVMS License Management Utility Manual. 1.5 System Requirements Before you install the DECnet-Plus for OpenVMS software, make sure that your system meets the following requirements. 1.5.1 Disk Space If this is the first time you are installing DECnet-Plus on a particular system, ensure that you have enough free space on the system disk. You need enough space to install the DECnet-Plus Base components and any options you select. If you already have DECnet-Plus installed, you need considerably less free space for the installation because the earlier installation allocated most of the space that a subsequent installation needs. Preparing to Install DECnet-Plus for OpenVMS 1-5 Preparing to Install DECnet-Plus for OpenVMS 1.5 System Requirements Required Disk Space - Base Components The total amount of disk space required to install the software for base components is 77,000 blocks for VAX systems and 85,000 blocks for Alpha systems. Disk Space - Optional Software Table 1-1 shows the amount of disk space needed to install the optional software. Make sure you have enough free space to install the required software and the optional software. Table_1-1_Disk_Space_Requirements_-_Optional_Software______ Blocks for Component__________Alpha____________Blocks_for_VAX_________ DECdts server 1400 1800 DECdns server N/A 3000[1] VAX P.S.I. N/A 7000 VAX WANDD N/A 5500 X.25 12144 N/A FTAM 28000 12000 Virtual Terminal 4000 2000 OSAK 6900 6000 [1]Approximate_amount_-_actual_amount_depends_on_the_size__ of the namespace, the number of logs created, and so forth. The amount of required disk space could double when running tests, then return to original amount when duplicate files are deleted. ___________________________________________________________ To find out how many free blocks exist on the system disk, enter the following command: $ show device sys$sysdevice If the number of required blocks exceeds the number of free blocks, you must clear space on the system disk. 1-6 Preparing to Install DECnet-Plus for OpenVMS Preparing to Install DECnet-Plus for OpenVMS 1.5 System Requirements 1.5.2 Required Memory The minimum amount of memory required is 24 MB for VAX systems and 64 MB for Alpha systems. To check memory on your system, enter the following command: $ show memory/full 1.5.3 Required System Parameters This section provides information about the system parameters, their values, and how to modify them. Table 1-2 lists the minimum system parameters required for the base software. Table 1-2 Minimum System Parameters Required - Base __________Software_Installation____________________________ Minimum Value for Minimum Value Parameter__________________Alpha_______for_VAX_____________ MIN_GBLSECTIONS 512 400 MIN_GBLPAGES 100000 60000 MIN_GBLPAGFIL 1024 4096 MIN_CLISYMTBL 750 500 MIN_KSTACKPAGES 2 N/A MIN_VIRTUALPAGES___________N/A_________35000_______________ To check these parameters, invoke the SYSGEN utility and enter the following command: $ mcr sysgen SYSGEN> show gblsections If any of the system parameters need to be modified, follow these steps: 1. Edit the modparams.dat file by entering: $ edit sys$system:modparams.dat Preparing to Install DECnet-Plus for OpenVMS 1-7 Preparing to Install DECnet-Plus for OpenVMS 1.5 System Requirements 2. Enter the values into the file in the following format: SCSSYSTEMID=65187 SCSNODE="SUPER1" MIN_GBLSECTIONS=512 . . . MIN_GBLPAGFIL=1024 3. Exit from the editor. 4. Run AUTOGEN by entering the following command: $ @sys$update:autogen getdata reboot ________________________ Note ________________________ Run AUTOGEN to ensure that your system is tuned with the appropriate parameters. ______________________________________________________ 1.5.3.1 SYSGEN Parameters for OpenVMS Cluster Members When installing DECnet-Plus for OpenVMS on an OpenVMS Cluster, make sure that all cluster members have the suggested SYSGEN parameters set correctly. If a node in the cluster does not have the required minimum parameters, startup of the network will fail. If the network fails to start for this reason, the logical NET$STARTUP_STATUS is set to OFF-AUTOGENREQ. Set the parameters to the recommended values before you run net$configure. 1.6 Privileges and Rights Identifiers Digital recommends that you install and configure DECnet- Plus from the SYSTEM account. If you are configuring from another account, make sure the account has the following privileges and rights identifiers in place before you begin. Required account privileges are as follows: o CMKRNL o NETMBX o SYSPRV 1-8 Preparing to Install DECnet-Plus for OpenVMS Preparing to Install DECnet-Plus for OpenVMS 1.6 Privileges and Rights Identifiers o TMPMBX o OPER o SYSNAM o WORLD ________________________ Note ________________________ The account cannot have the locked password (LOCKPWD) flag set. ______________________________________________________ Required rights identifiers are as follows: o NET$MANAGE o NET$SECURITY o NET$REGISTERDNSOBJECT ________________________ Note ________________________ If your account has the BYPASS privilege, then you do not need to grant these rights identifiers. ______________________________________________________ 1.7 Backing Up the System Disk Use the OpenVMS BACKUP utility to make a copy of the system disk. 1.8 Notifying Users Inform users on the system that you plan to install a product and that they must log out. Use the reply/all command and be sure to indicate the exact time you plan to begin running the POLYCENTER Software Installation utility. For example: $ set logins/interactive=0 $ reply/all "Installing software at 18:00; Please log out." If possible, give users an estimated time when they will be able to log in to the system. Preparing to Install DECnet-Plus for OpenVMS 1-9 2 _________________________________________________________________ Pre-Installation Tasks Before installing the software, complete the installation planning checklist in this chapter. This ensures that you have the information you need to complete the installation and configuration in the minimum amount of time. In addition to identifying necessary information and directing you to sources of help, the checklist also assists you in choosing optional software. 2.1 Information Required to Complete the Installation Planning Checklist Determine the following information before you begin the installation and configuration procedure. Enter this information on your installation planning checklist: o System's full name (you may have a DECdns full name, a Local namespace full name, and a fully qualified host name for the Domain Name System [DNS/BIND]) o Node synonym o Phase IV-compatible address to interface with Phase IV nodes o Phase IV prefix o Network address 2.2 Installation Planning Checklist Complete the checklist in Table 2-1 before continuing with the installation process. Pre-Installation Tasks 2-1 Pre-Installation Tasks 2.2 Installation Planning Checklist Table_2-1_Installation_Planning_Checklist__________________ Question_____________________Yes__No___For_More_Information Have you backed up your < > < > system disk? If not, then do so before you start the installation. ___________________________________________________________ Will the system get network < > < > See Section 6.2 addresses from a DECdns name server? If yes, what is the system's DECdns node name (for example, ACME:.BOSTON)? ___________________________________________________________ Will the system store < > < > See Section 6.2 network addresses in a Local database? If yes, what is the system's Local node name (for example, LOCAL:.BOSTON)? ___________________________________________________________ Is TCP/IP installed on the < > < > See Section 6.2 system? Will the system store network addresses in the DNS/BIND database? If yes, what is the system's DNS/BIND name (for example, BOSTON.ACME.COM)? ___________________________________________________________ What is the system's node See Section 6.2.4 synonym (for example, BOSTON)? (continued on next page) 2-2 Pre-Installation Tasks Pre-Installation Tasks 2.2 Installation Planning Checklist Table_2-1_(Cont.)_Installation_Planning_Checklist__________ Question_____________________Yes__No___For_More_Information ___________________________________________________________ Will the system communicate < > < > See Section 6.2.5 with Phase IV nodes? and Section 6.2.6 o Phase IV-compatible address (for example, 2.38) o Phase IV Prefix (the default is 49::) ___________________________________________________________ Will the system < > < > See Section 6.2.7 autoconfigure its network addresses? If not, you'll need network entity titles (for example, 47:24:02-01-0A-04:08-00-2B-93-ED-99:00). ___________________________________________________________ Do you want to install < > < > Refer to the DECnet- DECdts server software? Plus Planning Guide. ___________________________________________________________ (continued on next page) Pre-Installation Tasks 2-3 Pre-Installation Tasks 2.2 Installation Planning Checklist Table_2-1_(Cont.)_Installation_Planning_Checklist__________ Question_____________________Yes__No___For_More_Information (For VAX only.) Do you < > < > Refer to the DECnet- want to install VAX WANDD Plus for OpenVMS software for VAX? Applications You must install this Installation software if you want to and Advanced use any of the following: Configuration guide. - Non-LAN connections to the network - Routing over synchronous connections - X.25 software over synchronous lines ___________________________________________________________ (For Alpha only.) Do < > < > Refer to the DECnet- you want to install X.25 Plus for OpenVMS software for Alpha? Applications You must install this Installation software if you want to and Advanced use any of the following: Configuration guide. - X.25 communications via DEC X25gateway - X.25 communications via X.25 Multihost - X.25 communications on local system (X.25 Native) - LAN X.25 (LLC Class 2) - DECnet over X.25 ___________________________________________________________ (continued on next page) 2-4 Pre-Installation Tasks Pre-Installation Tasks 2.2 Installation Planning Checklist Table_2-1_(Cont.)_Installation_Planning_Checklist__________ Question_____________________Yes__No___For_More_Information Do you want to install < > < > Refer to the DECnet- DECnet-Plus for OpenVMS Plus for OpenVMS OSAK software? Applications If you plan to use an OSI Installation application such as FTAM or and Advanced Virtual Terminal, you must Configuration guide. install this software. ___________________________________________________________ Do you want to install < > < > Refer to the DECnet- DECnet-Plus for OpenVMS Plus for OpenVMS FTAM software? Applications If you plan to copy files Installation to and from other OSI- and Advanced compliant systems or Configuration guide. manage such files, you must install this software. ___________________________________________________________ Do you want to install < > < > Refer to the DECnet- DECnet-Plus for OpenVMS Plus for OpenVMS Virtual Terminal (VT) Applications software? Installation If you plan to support and Advanced remote logins and access Configuration guide. to remote applications on OSI-compliant systems, you must_install_this_software.________________________________ Pre-Installation Tasks 2-5 3 _________________________________________________________________ Installing DECnet-Plus for OpenVMS The DECnet-Plus for OpenVMS distribution software is provided on compact disc (CD-ROM). The software consists of the following components: Components for Alpha Systems o Base Components - DECnet-Plus for OpenVMS base kit - DECdts server o Optional Components (included with the base kit but must be installed separately) - FTAM - Virtual Terminal (VT) - OSAK o X.25 for Alpha (requires a separate license) Components for VAX Systems o Base Components - DECnet-Plus for OpenVMS base kit - VAX P.S.I. - WANDD for VAX - DECdns server - DECdts server o Optional Components (included with the base kit but must be installed separately) - FTAM - VT Installing DECnet-Plus for OpenVMS 3-1 Installing DECnet-Plus for OpenVMS - OSAK 3-2 Installing DECnet-Plus for OpenVMS Installing DECnet-Plus for OpenVMS ________________________ Note ________________________ The DECnet-Plus base components, FTAM, OSAK, and VT, are all packaged as separate installation kits on the distribution medium. They are usually located in the same directory. The X.25 for OpenVMS Alpha kit, however, is a separately licensed product and as such is in a different directory on the distribution medium. Consult the documentation with your distribution medium for the location of the kits you desire. ______________________________________________________ Use the POLYCENTER Software Installation utility to install the base components and any combination of optional components. See Appendix A for information on using the DCL interface with the POLYCENTER Software Installation utility. 3.1 Recommended Order for Installing Software The following sections describe the order in which you should install the DECnet-Plus for OpenVMS software for either an Alpha or VAX system. 3.1.1 Installing DECnet-Plus for an OpenVMS Alpha System If you choose to install all the software products at the same time, install and configure the OpenVMS operating system and layered products in the following order, referring to the appropriate documentation. For a quick reference, see Figure 3-1. After OpenVMS has been installed, perform the following steps: 1. Inspect the distribution kit. 2. Verify that all prerequisite software and licenses are installed. Refer to the OpenVMS system documentation set. 3. Shut down all network-related applications and tell users to log out. 4. Install DECnet-Plus for OpenVMS. See Section 3.2. Installing DECnet-Plus for OpenVMS 3-3 Installing DECnet-Plus for OpenVMS 3.1 Recommended Order for Installing Software 5. Set the system parameters. 6. Reboot the system. 7. Install X.25 for OpenVMS Alpha and WANDD, if necessary. Refer to the DECnet-Plus for OpenVMS Applications Installation and Advanced Configuration guide. 8. Configure DECnet-Plus for OpenVMS. First, see Chapter 4 to determine which configuration option to choose: FAST, BASIC, or ADVANCED. For a FAST configuration, see Chapter 5. For a BASIC configuration, see Chapter 6. For an ADVANCED configuration, refer to the DECnet-Plus for OpenVMS Applications Installation and Advanced Configuration guide. 9. Configure X.25 for OpenVMS Alpha. Refer to the DECnet-Plus for OpenVMS Applications Installation and Advanced Configuration guide. 10.Install and configure the OSI Applications (FTAM, VT, OSAK). Refer to the DECnet-Plus for OpenVMS Applications Installation and Advanced Configuration guide. 3-4 Installing DECnet-Plus for OpenVMS Installing DECnet-Plus for OpenVMS 3.1 Recommended Order for Installing Software Figure 3-1 Installation and Configuration Flowchart (Alpha Only) Installing DECnet-Plus for OpenVMS 3-5 Installing DECnet-Plus for OpenVMS 3.1 Recommended Order for Installing Software 3.1.2 Installing DECnet-Plus for a VAX System If you choose to install all the software products at the same time, install and configure the OpenVMS operating system and layered products in the following order, referring to the appropriate documentation. For a quick reference, see Figure 3-2. After OpenVMS has been installed, perform the following: 1. Inspect the distribution kit. 2. Verify that all prerequisite software and licenses are installed. Refer to the OpenVMS system documentation set. 3. Shut down all network-related applications and tell users to log out. 4. Install DECnet-Plus for OpenVMS. See Section 3.2. ________________________ Note ________________________ If you want to install VAX P.S.I., select the option now while installing DECnet-Plus for OpenVMS. ______________________________________________________ 5. Set the system parameters. 6. Reboot the system. 7. Configure DECnet-Plus for OpenVMS. First, review Chapter 4 to determine which configuration option to choose: FAST, BASIC, or ADVANCED. For a FAST configuration, see Chapter 5. For a BASIC configuration, see Chapter 6. For an ADVANCED configuration, refer to the DECnet-Plus for OpenVMS Applications Installation and Advanced Configuration guide. 8. Configure VAX P.S.I. Refer to the DECnet-Plus for OpenVMS Applications Installation and Advanced Configuration guide. 9. Install and configure the OSI applications (FTAM, VT, OSAK). 3-6 Installing DECnet-Plus for OpenVMS Installing DECnet-Plus for OpenVMS 3.1 Recommended Order for Installing Software Refer to the DECnet-Plus for OpenVMS Applications Installation and Advanced Configuration guide. Installing DECnet-Plus for OpenVMS 3-7 Installing DECnet-Plus for OpenVMS 3.1 Recommended Order for Installing Software Figure 3-2 Installation and Configuration Flowchart (VAX Only) 3.2 Installing DECnet-Plus Using the POLYCENTER Software Installation Utility This section describes the steps for installing DECnet-Plus software using the POLYCENTER Software Installation utility (for more information on this utility, see Appendix A). You must have SYSPRV privileges on the local or remote node where you want to run this utility. 3.2.1 Sample DECnet-Plus for OpenVMS Alpha Installation To start the installation, follow these steps: 1. Log in to the SYSTEM account. 2. Mount the software CD-ROM. Refer to the OpenVMS Layered Products Compact Disc User's Guide for instructions on mounting and removing a compact disc. 3. Enter the following command, substituting the name of your device for the devicename parameter: $ product install decnet_osi /source=devicename:[dnvosi071.kit] You are then prompted for installation information as in the following example. In this example, numbered callouts (1, 2, 3, . . . ) guide you through the sequence of steps that require your response. For Alpha systems, you will see AXPVMS as product information on your screen. The following product has been selected: DEC AXPVMS DECNET_OSI V7.1 [Available] 1 Do you want to continue? [YES] DEC AXPVMS DECNET_OSI V7.1: DECnet-Plus V7.1 for OpenVMS AXP Copyright © Digital Equipment Corporation 1996. All rights reserved. Digital Equipment Corporation 3-8 Installing DECnet-Plus for OpenVMS Installing DECnet-Plus for OpenVMS DECnet-Plus Using the POLYCENTER Software Installation Utility This product requires one of two PAKS: DVNETEND or DVNETEXT. 2 Do you want the defaults for all product options? [YES] 3 Do you want to view the options? [NO] Execution phase starting ... The following product will be installed: DEC AXPVMS DECNET_OSI V7.1 Portion Done: 0%...10%...20%...30%...40%...50%...80%...90%...100% The following product has been installed: DEC AXPVMS DECNET_OSI V7.1 1 At this point, you can stop the installation process. If you want to continue, press Return. If you want to stop, type NO, then press Return. 2 This question allows you to select which optional parts of the DECnet-Plus product you want to install. If you want to install just the base software, press Return. If you want to select the optional software, type NO and press Return. The procedure then displays a list of choices for you. 3 This question allows you to review and change your current selections. Type YES if you are satisfied with the current selected options. Type NO if you want to make changes. 3.2.2 Sample DECnet-Plus for OpenVMS VAX Installation To start the installation, follow these steps: 1. Log in to the SYSTEM account. 2. Mount the software CD-ROM. Refer to the OpenVMS Layered Products Compact Disc User's Guide for instructions on mounting and removing a compact disc. 3. Enter the following command, substituting the name of your device for the devicename parameter: $ product install decnet_osi /source=devicename:[dnvosi071.kit] Installing DECnet-Plus for OpenVMS 3-9 Installing DECnet-Plus for OpenVMS 3.2 Installing DECnet-Plus Using the POLYCENTER Software Installation Utility The installation prompts you for information as in the following example. In this example, numbered callouts (1, 2, 3, . . . ) guide you through the sequence of steps that require your response. For VAX systems, you will see DEC VAXVMS as product information on your screen. The following product has been selected: DEC VAXVMS DECNET_OSI V7.1 [Available] 1 Do you want to continue? [YES] DEC VAXVMS DECNET_OSI V7.1: DECnet-Plus V7.1 for OpenVMS VAX Copyright © Digital Equipment Corporation 1996. All rights reserved. Digital Equipment Corporation This product requires one of two PAKS: DVNETEND or DVNETRTG. 2 Do you want the defaults for all product options? [YES] 3 Do you want to view the options? [NO] y DEC VAXVMS DECNET_OSI V7.1: DECnet-Plus V7.1 for OpenVMS VAX DEC VAXVMS VMS V7.1 [Available] VAX P.S.I. or P.S.I. Access software: NO VAX Wide Area Device Drivers: NO DECdns Server software: NO DECdts Server software: NO Are you satisfied with these options? [YES] Execution phase starting ... The following product will be installed: DEC VAXVMS DECNET_OSI V7.1 Portion Done: 0%...10%...20%...30%...40%...80%...90%...100% The following product has been installed: DEC VAXVMS DECNET_OSI V7.1 1 At this point, you can stop the installation process. If you want to continue, press Return. If you want to stop, type NO, then press Return. 3-10 Installing DECnet-Plus for OpenVMS Installing DECnet-Plus for OpenVMS DECnet-Plus Using the POLYCENTER Software Installation Utility 2 This question allows you to select which optional parts of the DECnet-Plus product you want to install. If you want to install just the base software, press Return. If you want to select the optional software, type NO and press Return. (For example, if you want to configure wide area devices such as WANDD, X.25, or P.S.I, answer NO to this question. The procedure then displays a list of choices for you.) 3 This question allows you to review and change your current selections. Type YES if you are satisfied with the current selected options. Type NO if you want to make changes. 3.3 Files Installed on Your System The DECnet-Plus installation procedure installs a number of files on your system. To list the files, enter the following command: $ product show object /product=decnet_osi Installing DECnet-Plus for OpenVMS 3-11 Part II _________________________________________________________________ DECnet-Plus for OpenVMS BASIC Configuration Part II describes how to configure DECnet-Plus for OpenVMS using the FAST and BASIC configuration options. It includes the following chapters: o Chapter 4 - Configuration Options o Chapter 5 - Using the FAST Configuration Option o Chapter 6 - Using the BASIC Configuration Option o Chapter 7 - Managing Name Services 4 _________________________________________________________________ Configuration Options This chapter explains the three configuration options you can use to configure your system for DECnet-Plus. These configuration options enable you to configure the DECnet- Plus for OpenVMS base components so that the system becomes a DECnet-Plus end system on a network. The procedure you use to configure your system for DECnet- Plus is sys$manager:net$configure.com. You can use any of the following net$configure configuration options: o FAST configuration option (Chapter 5) The FAST configuration allows you to quickly upgrade a non-clustered system from DECnet Phase IV to DECnet Phase V. o BASIC configuration option (Chapter 6) The BASIC configuration allows you to configure your system for DECnet-Plus by answering a few questions and using the default answers on others. o ADVANCED configuration option (DECnet-Plus for OpenVMS Applications Installation and Advanced Configuration guide) The ADVANCED configuration allows you to customize your system's network configuration. This chapter presents additional information about the following topics: o Selecting a configuration option o Running net$configure See Section 1.6 for a list of account privileges you need to run net$configure. Configuration Options 4-1 Configuration Options 4.1 Selecting a Configuration Option 4.1 Selecting a Configuration Option If you installed the required software, you can configure your system using the net$configure configuration option for the FAST configuration, using the net$configure basic configuration option for the BASIC configuration, or using the net$configure advanced configuration option for the ADVANCED configuration. Table 4-1 provides some guidelines for making your configuration choice. If you choose to use either the FAST configuration option or the BASIC configuration option, continue with this section. If you prefer to customize your system's network configuration with the ADVANCED configuration option, refer to the DECnet-Plus for OpenVMS Applications Installation and Advanced Configuration guide. 4-2 Configuration Options Configuration Options 4.1 Selecting a Configuration Option Table_4-1_Choosing_Your_Configuration_Option_____________________ Option..._Choose_if...___________________________________________ FAST You are upgrading from a DECnet Phase IV node and you plan to use the existing Phase IV configuration. The node is not in a cluster. You are running the configuration procedure for the first time. _________________________________________________________________ BASIC The node is in a cluster. You are upgrading or reconfiguring DECnet-Plus. You need to access a DECdns server for network addresses. You want to run DECnet over TCP/IP (RFC 1859) and/or OSI applications over TCP/IP (RFC 1006). You only have one communications device, or you have multiple devices, all of which will be used for DECnet-Plus communications. You want to use the default names for all devices and routing circuits. You want to autoconfigure your network addresses only. You want to configure both the NSP and OSI transports and only want to create default OSI templates. You want to enable both DECnet over TCP/IP or OSI applications over TCP/IP. You do not want to enable FDDI large packet support (if you have an FDDI-type circuit). You want to set the routing characteristic DNA Address Format to TRUE (this attribute controls the interpretation of address structuring). You want to use integrated mode routing. _________________________________________________________________ (continued on next page) Configuration Options 4-3 Configuration Options 4.1 Selecting a Configuration Option Table_4-1_(Cont.)_Choosing_Your_Configuration_Option_____________ Option..._Choose_if...___________________________________________ ADVANCED Your configuration is complex. You need to customize your network's configuration. Your system has multiple communication devices, and you want them to run a mix of protocols. You want to configure a cluster with both DECnet Phase IV and DECnet Phase V nodes. You want the option to give specific names to all devices and routing circuits. You also want the option of not configuring all of your devices for DECnet-Plus. You want the option of manually entering your network addresses. You want to configure either the NSP transport or the OSI transport (or both). You want the option to create additional OSI templates. You want the option of enabling/disabling DECnet over TCP/IP or OSI applications over TCP/IP. You want the option of enabling FDDI large packet support (if you have an FDDI-type circuit). You want the option of setting the routing characteristic DNA Address Format to TRUE or FALSE (to control the interpretation of address structuring). You want the option of using either integrated mode routing or segregated mode routing. You want the option to provide default accounts for __________FAL.___________________________________________________ 4.2 How to Run NET$CONFIGURE The net$configure.com procedure configures the DECnet-Plus for OpenVMS software. This command creates or modifies the Network Control Language (NCL) scripts required to run DECnet-Plus for OpenVMS on your node. The net$configure.com procedure is an interactive procedure that displays a series of questions. After each question, the default response, if there is one, appears in brackets 4-4 Configuration Options Configuration Options 4.2 How to Run NET$CONFIGURE ([ ]). At the end of each question, a colon (:) appears. Respond in one of the following ways: o To get help after a question, type a question mark (?). After the help display, the same question reappears. o To select the default response, press Return. o To enter information, type it immediately after the colon or question mark; then press Return. o Type Y for YES and N for NO. o To terminate the procedure, press Ctrl/Y. If you execute net$configure.com without specifying BASIC or ADVANCED, the BASIC configuration option is invoked by default. ________________________ Note ________________________ If you are running the configuration procedure for the first time on a system that was previously configured for Phase IV and you do not specify BASIC or ADVANCED, the initial default is the FAST configuration procedure. However, the FAST configuration procedure can only be run once on a system, and after that the BASIC configuration procedure automatically becomes the default. ______________________________________________________ To invoke net$configure.com with the default BASIC option, enter the following: $ @sys$manager:net$configure 4.2.1 Local and Global Symbols The net$configure.com procedure deletes all of your local and global symbols at the beginning of the procedure in order to free the symbol table. This happens because net$configure.com creates and uses a large number of symbols. If the symbols were not deleted at the beginning of the procedure, net$configure would often run out of symbol table space to use while configuring the system. Configuration Options 4-5 Configuration Options 4.2 How to Run NET$CONFIGURE 4.2.2 Running the Procedure from Different Processes Although net$configure.com can be run simultaneously on different nodes in a cluster, it should not be run simultaneously from different processes on the same node. 4-6 Configuration Options 5 _________________________________________________________________ Using the FAST Configuration Option This chapter describes how to configure the DECnet-Plus for OpenVMS base components using the FAST configuration option so that the system becomes a DECnet-Plus for OpenVMS end system on a network. ________________________ Note ________________________ If you have already run the FAST configuration procedure once on your system, the configuration procedure automatically defaults to the BASIC configuration procedure. ______________________________________________________ 5.1 Invoking the FAST Configuration Option To invoke the net$configure.com procedure using the FAST configuration option, enter the following command: $ @sys$manager:net$configure The procedure starts: Copyright (c) Digital Equipment Corporation 1996. All rights reserved. DECnet-Plus for OpenVMS 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 '?'. %NET$CONFIGURE-I-SETUPNEW, setting up for new configuration %NET$CONFIGURE-I-PHASEIVDATA, Phase IV DECnet database found FAST CONFIGURATION OPTION Using the FAST Configuration Option 5-1 Using the FAST Configuration Option 5.1 Invoking the FAST Configuration Option You have the option of using the existing Phase IV information to quickly configure DECnet-Plus. This provides full network access and uses a local file to hold naming information. Very few questions will be asked. If you want to use the fast configuration option, answer YES to the next question. If you are running a DNS Server on this system, or plan to run a DNS Server on this system, you *must* answer NO to the next question. If you want more flexibility when configuring DECnet-Plus, also answer NO. Answering NO will cause some additional questions to be asked regarding configuration. * Do you want the fast default configuration? [YES] : Press Return to continue with the FAST configuration option. The procedure informs you that the Phase IV database conversion has completed. %NET$CONFIGURE-I-PHASEIVCOMPL, Phase IV database conversion complete Determining DTSS timezone rules from OpenVMS information... %NET$CONFIGURE-I-CREDEFOSITEMPLATE, created default OSI templates %NET$CONFIGURE-I-EVDDEFAULT, providing default Event Dispatcher configuration %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account CML$SERVER Summary of Configuration Node Information: Node Type: ENDNODE Directory Services Chosen: LOCAL Primary Directory Service: LOCAL Node Synonym: NCLGUI Phase IV Address: 4.260 Phase IV Prefix: 49:: Autoconfiguration of Network Addresses: Enabled Session Control Address Update Interval: 10 Routing ESHello Timer: 600 Device Information: Device: EWA (TULIP): Data Link name: EWA-0 Routing Circuit Name: EWA-0 5-2 Using the FAST Configuration Option Using the FAST Configuration Option 5.1 Invoking the FAST Configuration Option Transport Information: NSP 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 apply this configuration? [YES] : Answer YES to apply this configuration. If you answer NO, the procedure defaults to the BASIC configuration procedure. If you answer YES, the following message displays: %NET$CONFIGURE-I-CHECKSUM, checksumming NCL management scripts * 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 Using the FAST Configuration Option 5-3 Using the FAST Configuration Option 5.1 Invoking the FAST Configuration Option Digital recommends that you answer YES and start the network. 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 namespace. 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 1995-05-26-14:12:24.170-04:00I0.404 %NET$CONFIGURE-I-NODERENAMED, node successfully renamed to ACME:.WABBIT.ELMER Directory Service: DECdns 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 5-4 Using the FAST Configuration Option Using the FAST Configuration Option 5.1 Invoking the FAST Configuration Option 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 1995-05-26-14:13:25.980-04:00I0.411 %NET$CONFIGURE-I-NODERENAMED, node successfully renamed to ACME:.WABBIT.ELMER Node 0 Session Control Tower Maintenance ACME:.WABBIT.ELMER at 1995-05-26-14:13:35.360-04:00I0.411 %NET$CONFIGURE-I-TOWERSUPDATED, updated address towers for node Node 0 Session Control Backtranslation Softlink * at 1995-05-26-14:13:43.360-04:00I0.412 Node 0 Session Control Backtranslation Softlink * at 1995-05-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 as an end system on the network. See Figure 3-1 and Figure 3-2 to determine your next step. According to the flowcharts, you have just completed configuring the base components. Using the FAST Configuration Option 5-5 Using the FAST Configuration Option 5.2 Changing a Current DECnet-Plus System Configuration 5.2 Changing a Current DECnet-Plus System Configuration You can use the net$configure procedure to modify the current configuration. Depending on which menu option you select, net$configure either modifies the configuration automatically or produces modified NCL scripts that you can use to modify the system's configuration. See Chapter 4 to determine whether you want to use the BASIC or ADVANCED configuration option to change your configuration. Refer to the DECnet-Plus for OpenVMS Applications Installation and Advanced Configuration for instructions on how to run the ADVANCED configuration. 5-6 Using the FAST Configuration Option 6 _________________________________________________________________ Using the BASIC Configuration Option This chapter describes how to configure the DECnet-Plus for OpenVMS base components using the BASIC configuration option so that the system becomes a DECnet-Plus for OpenVMS end system on a network. The BASIC configuration option allows you to configure your system by answering a few questions and using the default answers on others. If you have already configured the DECnet-Plus for OpenVMS software and you want to customize the configuration, see Chapter 4 to determine if you want to use the BASIC or ADVANCED option. 6.1 Invoking the BASIC Configuration Option To invoke the net$configure.com procedure using the BASIC configuration option, enter the following command: $ @sys$manager:net$configure basic The procedure starts: Copyright (c) Digital Equipment Corporation 1993, 1996. All rights reserved. DECnet-Plus for OpenVMS BASIC 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 BASIC configuration option. This option enables you to quickly configure your system by answering a few questions and using most of the default answers. If you would rather do some specific tailoring of your system's network configuration, you should invoke NET$CONFIGURE.COM with the ADVANCED configuration option, ie: @SYS$MANAGER:NET$CONFIGURE ADVANCED * Do you want to continue? [YES] : Using the BASIC Configuration Option 6-1 Using the BASIC Configuration Option 6.1 Invoking the BASIC Configuration Option Press Return to continue with the BASIC configuration option. 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 procedure displays the following message: %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 database? [YES] : If you answer YES, 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, starting with the directory services to use on the system. If you need more information to answer a question, you can type a question mark (?) at the prompts. Review the installation planning checklist in Chapter 2 before continuing. 6.2 Directory Name Services DECnet-Plus provides access to the node name and addressing information stored in one or more name services. This release of 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. 6-2 Using the BASIC Configuration Option Using the BASIC Configuration Option 6.2 Directory Name Services 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 7.1.1. o DECdns distributed namespace - Digital's Distributed Name Service, DECdns is a distributed, global name service. For more information, see Section 7.1.2. o Domain Name System - The Domain Name System (DNS/BIND) is supported for storage of IP addresses. For more information, see Section 7.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. 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] : 6.2.1 Node Full Name The DECnet-Plus for OpenVMS configuration procedure net$configure.com prompts you for the system's full name. You can enter a DECdns full name, a Local namespace full name, a fully qualified host name for the Domain Name System (DNS/BIND), or all three. For DECdns and Local namespace full names, you must specify a node full name that includes a namespace nickname (this complies with DECdns distributed namespace requirements). The full name format is the same for distributed namespaces and Local namespaces. The full name uses the following form: NamespaceNickname:.DirectoryPath.NodeObject The following are the guidelines for selecting a full name: o For DECdns and Local, the node full name must begin with the namespace nickname and a colon (:). The nickname for the Local namespace is always LOCAL: (or local:). Using the BASIC Configuration Option 6-3 Using the BASIC Configuration Option 6.2 Directory Name Services o For DECdns and Local, the directory path must begin with a dot (.). o The full name can be up to 511 characters long: the namespace nickname can be up to 255 characters, and the directory path and node object can be up to 255 characters. o The full name can be any combination of letters, digits, and certain punctuation characters from the ISO Latin- 1 character set. Some other characters are allowed as long as they are enclosed in quotation marks. For a list of all allowable characters, refer to the DECnet-Plus DECdns Management guide. o For DNS/BIND, enter a fully qualified IP host name. The following are some examples of suitable node full names: AU:.chemistry$lab.Sunil$Sethi XYZ_CORP:.sales.east_coast.BrianMacKrill Mbi:.MIS.Europe.Monaco_headquarters.F_Riviera local:.bryan smilee.mass.acme.edu ________________________ Note ________________________ If you plan to use a Local namespace and you are converting a Phase IV system to DECnet-Plus, Digital recommends that you use the system's Phase IV node name in the DECnet-Plus full name (for example, LOCAL:.PASTRY). ______________________________________________________ You should plan node full names carefully and make sure they are unique within the namespace. If your network administrator has not assigned a unique node full name for your system, be sure to read the DECnet-Plus Planning Guide before you assign a node name for your system. For more information on name services, see Chapter 7. At the prompt, 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 6-4 Using the BASIC Configuration Option Using the BASIC Configuration Option 6.2 Directory Name Services 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. * 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 6.2.2 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] : 6.2.3 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. Using the BASIC Configuration Option 6-5 Using the BASIC Configuration Option 6.2 Directory Name Services 6.2.4 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. The node synonym is primarily a transition tool that allows you to use a Phase IV-style node name for your DECnet- Plus node. Other users can then find your node by using this synonym rather than your full name. If you were using DECnet Phase IV, consider using your Phase IV node name as your synonym. The synonym is required for Phase IV applications that can only handle Phase IV-style node names. If your network has only DECnet-Plus or OSI (Open Systems Interconnection) systems, you may not need a node synonym. The default node synonym is the first six characters of the system's last simple name. The last simple name is the string that follows the last period of your full name. For example, if you specify XYZ_CORP:.sales.east_ coast.BrianMacKrill as a node full name, the default node synonym is BrianM. 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 7.4. 6.2.5 Specifying a DECnet 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. 6-6 Using the BASIC Configuration Option Using the BASIC Configuration Option 6.2 Directory Name Services A DECnet Phase IV-compatible address is a DECnet-Plus address (NSAP - network service access point) 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. 6.2.6 Specifying a Phase IV Prefix The net$configure basic configuration option provides 49:: as the default value for the Phase IV prefix. If you do not enter a Phase IV-compatible address, you will not have a Phase IV prefix. 6.2.7 Configuring Network Addresses The net$configure basic configuration option autoconfigures one network address for you. 6.2.8 DNA Address Format The net$configure basic configuration sets the routing characteristic DNA address format to TRUE. 6.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 Using the BASIC Configuration Option 6-7 Using the BASIC Configuration Option 6.3 Configuring Devices 6.3.1 Configuring an Alpha System 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 * Routing Circuit Name to use? [X25-PVC-0] : * Template name? [X25-PVC-0] : * Configure another X.25 routing circuit for DECnet? [NO] : Enter the number for the type of circuit you want, then enter a routing circuit name and a template name to use for that circuit. If you do not want to configure any other X.25 routing circuits, press Return for the default. The configuration procedure continues with the next series of questions (such as time zone or transports, for example). 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. 6-8 Using the BASIC Configuration Option Using the BASIC Configuration Option 6.3 Configuring Devices 6.3.2 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 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. Using the BASIC Configuration Option 6-9 Using the BASIC Configuration Option 6.3 Configuring Devices 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 6.3.1 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? : 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. 6-10 Using the BASIC Configuration Option Using the BASIC Configuration Option 6.4 Configuring Transports 6.4 Configuring Transports Next, the NSP transport and the OSI transport are configured. The procedure displays the following message to indicate that the default OSI templates have been created: %NET$CONFIGURE-I-CREDEFOSITEMPLATE, created default OSI templates The default OSI templates are used by the OSAK and FTAM installation verification procedures (IVPs) for loopback testing. You will not be able to use OSI applications to make connections to other OSI systems unless you use the net$configure advanced configuration option to create additional OSI templates. You can do this at a later time. 6.5 Configuring Time Zone Differential Factors The UTC (Coordinated Universal Time) is calculated automatically by using the OpenVMS UTC, and 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. 6.6 Configuring an Event Dispatcher The procedure then provides the default Event Dispatcher configuration: %NET$CONFIGURE-I-EVDDEFAULT, providing default Event Dispatcher configuration 6.7 Configuring an Application Database The procedure creates the DECnet-Plus default applications to include in the application database. The procedure creates default user accounts for the CML, MAIL, VPM, MIRROR, and PHONE applications (no account is created for FAL): Using the BASIC Configuration Option 6-11 Using the BASIC Configuration Option 6.7 Configuring an Application Database %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account CML$SERVER %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account MAIL$SERVER %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account VPM$SERVER %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account MIRRO$SERVER %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account PHONE$SERVER o CMIP Management Listener (CML) is the DECnet-Plus management module that implements DNA Common Management Information Protocol (DNA CMIP). CML provides access to CMIP. o MAIL allows users to send and receive messages. o VMScluster Performance Monitor (VPM) needs an account for your system to support the OpenVMS Monitor utility command MONITOR CLUSTER. o MIRROR is needed for particular forms of loopback testing. o PHONE allows users on the same or different OpenVMS systems to communicate interactively. 6.8 Configuring a Cluster Alias The following steps describe how to configure a cluster alias. 1. If the node is a 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. * 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 6-12 Using the BASIC Configuration Option Using the BASIC Configuration Option 6.8 Configuring a Cluster Alias Do not use your address for the cluster alias. If you are unsure which address to enter, consult your network manager. 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] : 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 Using the BASIC Configuration Option 6-13 Using the BASIC Configuration Option 6.8 Configuring a Cluster Alias will be serving any multihost disks, such as RFxx or HSC-connected disks, to other cluster members. Digital recommends values between 0 and 10. 4. The procedure then displays: Summary of Configuration Node Information 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: Enabled Alias Name: ACME:.WABBIT.HELP Device Information: Device: ESA0 (DESVA): Data Link name: CSMACD-0 Routing Circuit Name: CSMACD-0 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] : 6-14 Using the BASIC Configuration Option Using the BASIC Configuration Option 6.8 Configuring a Cluster Alias 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. ______________________________________________________ 5. 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. Using the BASIC Configuration Option 6-15 Using the BASIC Configuration Option 6.8 Configuring a Cluster Alias 6. When you choose to start the network, the procedure displays information similar to the following: Copyright (c) Digital Equipment Corporation 1995. 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 namespace. 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 1995-05-26-14:12:24.170-04:00I0.404 %NET$CONFIGURE-I-NODERENAMED, node successfully renamed to ACME:.WABBIT.ELMER Directory Service: DECdns 7. 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 6-16 Using the BASIC Configuration Option Using the BASIC Configuration Option 6.8 Configuring a Cluster Alias 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 1995-05-26-14:13:25.980-04:00I0.411 %NET$CONFIGURE-I-NODERENAMED, node successfully renamed to ACME:.WABBIT.ELMER Node 0 Session Control Tower Maintenance ACME:.WABBIT.ELMER at 1995-05-26-14:13:35.360-04:00I0.411 %NET$CONFIGURE-I-TOWERSUPDATED, updated address towers for node Node 0 Session Control Backtranslation Softlink * at 1995-05-26-14:13:43.360-04:00I0.412 Node 0 Session Control Backtranslation Softlink * at 1995-05-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 as an end system on the network. See Figure 3-1 and Figure 3-2 to determine your next step. According to the flowcharts, you have just completed configuring the base components. Using the BASIC Configuration Option 6-17 Using the BASIC Configuration Option 6.9 Changing a Current DECnet-Plus System Configuration 6.9 Changing a Current DECnet-Plus System Configuration You can use the net$configure procedure to modify the current configuration. Depending on which menu option you select, net$configure either modifies the configuration automatically or produces modified NCL scripts that you can use to modify the system's configuration. See Chapter 4 to determine whether you want to use the FAST, BASIC or ADVANCED configuration option to change your configuration. Refer to the DECnet-Plus for OpenVMS Applications Installation and Advanced Configuration for instructions on how to run the ADVANCED configuration. 6-18 Using the BASIC Configuration Option 7 _________________________________________________________________ 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. 7.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). See Section 6.2 for more information. 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 DECnet- Plus Planning Guide. 7.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 7-1 Managing Name Services 7.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. The following are typical node full names properly formatted for the Local namespace: LOCAL:.xyz.abc and local:.maximum. Unlike DECdns, the Local namespace does not employ backtranslation directories for address-to-node-name translation. 7.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. 7.1.1.2 Managing the Local Namespace The DECdns distributed namespace is not a requirement for DECnet-Plus and the Local namespace